idnits 2.17.1 draft-ietf-capwap-base-mib-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.i or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 28, 2009) is 5537 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC3168' is mentioned on line 2372, but not defined -- Looks like a reference, but probably isn't: '5' on line 3305 ** Obsolete normative reference: RFC 4133 (Obsoleted by RFC 6933) -- Obsolete informational reference (is this intentional?): RFC 4347 (Obsoleted by RFC 6347) == Outdated reference: A later version (-06) exists of draft-ietf-capwap-802dot11-mib-02 Summary: 2 errors (**), 0 flaws (~~), 4 warnings (==), 4 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 H3C Tech. Co., Ltd 4 Intended status: Standards Track D. Perkins, Ed. 5 Expires: September 1, 2009 SNMPinfo 6 C. Elliott, Ed. 7 Cisco Systems, Inc. 8 Y. Zhang, Ed. 9 Fortinet, Inc. 10 February 28, 2009 12 CAPWAP Protocol Base MIB 13 draft-ietf-capwap-base-mib-04 15 Status of This Memo 17 This Internet-Draft is submitted to IETF in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 This Internet-Draft will expire on September 1, 2009. 38 Copyright Notice 40 Copyright (c) 2009 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents in effect on the date of 45 publication of this document (http://trustee.ietf.org/license-info). 46 Please review these documents carefully, as they describe your rights 47 and restrictions with respect to this document. 49 Abstract 51 This memo defines a portion of the Management Information Base (MIB) 52 for use with network management protocols. In particular, it 53 describes managed objects for modeling the Control And Provisioning 54 of Wireless Access Points (CAPWAP) Protocol. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 2. The Internet-Standard Management Framework . . . . . . . . . . 3 60 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4 62 5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 5.1. Requirements and Constraints . . . . . . . . . . . . . . . 5 64 5.2. Wireless Binding MIB Modules . . . . . . . . . . . . . . . 5 65 5.3. Design Objectives . . . . . . . . . . . . . . . . . . . . 5 66 5.4. Design Idea . . . . . . . . . . . . . . . . . . . . . . . 6 67 5.5. Mechanism of Reusing Wireless Binding MIB Modules . . . . 6 68 5.6. CAPWAP Protocol Wireless Binding MIB Module . . . . . . . 7 69 6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 7 70 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 8 71 7.1. Relationship to SNMPv2-MIB Module . . . . . . . . . . . . 8 72 7.2. Relationship to IF-MIB Module . . . . . . . . . . . . . . 8 73 7.3. Relationship to ENTITY-MIB Module . . . . . . . . . . . . 9 74 7.4. Relationship to Wireless Binding MIB Modules . . . . . . . 9 75 7.5. MIB Modules Required for IMPORTS . . . . . . . . . . . . . 10 76 8. Example of CAPWAP-BASE-MIB Module Usage . . . . . . . . . . . 10 77 9. CAPWAP Message Element Extension . . . . . . . . . . . . . . . 12 78 9.1. CAPWAP Protocol Timers . . . . . . . . . . . . . . . . . . 13 79 9.2. CAPWAP Protocol Variables . . . . . . . . . . . . . . . . 16 80 9.3. CAPWAP Messages for CAPWAP Control Message Extension . . . 16 81 9.3.1. Configuration Status Response Message . . . . . . . . 16 82 9.3.2. Configuration Update Response Message . . . . . . . . 17 83 10. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 17 84 11. Security Considerations . . . . . . . . . . . . . . . . . . . 65 85 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 67 86 12.1. IANA Considerations for CAPWAP-BASE-MIB module . . . . . . 67 87 12.2. IANA Considerations for ifType . . . . . . . . . . . . . . 67 88 13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 67 89 14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 67 90 15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 67 91 15.1. Normative References . . . . . . . . . . . . . . . . . . . 67 92 15.2. Informative References . . . . . . . . . . . . . . . . . . 69 93 Appendix A. Appendix A. Changes between -04 and -03 . . . . . . . 71 95 1. Introduction 97 The CAPWAP Protocol [I-D.ietf-capwap-protocol-specification] defines 98 a standard, interoperable protocol, which enables an Access 99 Controller (AC) to manage a collection of Wireless Termination 100 Points(WTPs). 102 This document defines a MIB module that can be used to manage CAPWAP 103 implementations. This MIB module covers both configuration and WTP 104 status-monitoring aspects of CAPWAP, and provides a way to reuse MIB 105 modules for any wireless technology. 107 2. The Internet-Standard Management Framework 109 For a detailed overview of the documents that describe the current 110 Internet-Standard Management Framework, please refer to section 7 of 111 RFC 3410 [RFC3410]. 113 Managed objects are accessed via a virtual information store, termed 114 the Management Information Base or MIB. MIB objects are generally 115 accessed through the Simple Network Management Protocol (SNMP). 116 Objects in the MIB are defined using the mechanisms defined in the 117 Structure of Management Information (SMI). This memo specifies a MIB 118 module that is compliant to the SMIv2, which is described in STD 58, 119 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 120 [RFC2580]. 122 3. Terminology 124 This document uses terminology from the CAPWAP Protocol specification 125 [I-D.ietf-capwap-protocol-specification] and the Architecture 126 Taxonomy for CAPWAP [RFC4118]. 128 Access Controller (AC): The network entity that provides WTP access 129 to the network infrastructure in the data plane, control plane, 130 management plane, or a combination therein. 132 Wireless Termination Point (WTP): The physical or network entity that 133 contains an RF antenna and wireless PHY to transmit and receive 134 station traffic for wireless access networks. 136 Control And Provisioning of Wireless Access Points (CAPWAP): It is a 137 generic protocol defining AC and WTP control and data plane 138 communication via a CAPWAP protocol transport mechanism. CAPWAP 139 control messages, and optionally CAPWAP data messages, are secured 140 using Datagram Transport Layer Security (DTLS) [RFC4347]. 142 CAPWAP Control Channel: A bi-directional flow defined by the AC IP 143 Address, WTP IP Address, AC control port, WTP control port and the 144 transport-layer protocol (UDP or UDP-Lite) over which CAPWAP control 145 packets are sent and received. 147 CAPWAP Data Channel: A bi-directional flow defined by the AC IP 148 Address, WTP IP Address, AC data port, WTP data port, and the 149 transport-layer protocol (UDP or UDP-Lite) over which CAPWAP data 150 packets are sent and received. 152 Station (STA): A device that contains an interface to a wireless 153 medium (WM). 155 Split and Local MAC: The CAPWAP protocol supports two modes of 156 operation: Split and Local MAC. In Split MAC mode all L2 wireless 157 data and management frames are encapsulated via the CAPWAP protocol 158 and exchanged between the AC and the WTPs. The Local MAC mode of 159 operation allows for the data frames to be either locally bridged, or 160 tunneled as 802.3 frames. 162 Wireless Binding: The CAPWAP protocol is independent of a specific 163 WTP radio technology, as well its associated wireless link layer 164 protocol. Elements of the CAPWAP protocol are designed to 165 accommodate the specific needs of each wireless technology in a 166 standard way. Implementation of the CAPWAP protocol for a particular 167 wireless technology MUST defining a binding protocol for it, e.g., 168 the binding for IEEE 802.11, provided in 169 [I-D.ietf-capwap-protocol-binding-ieee80211]. 171 Autonomous WLAN Architecture: It is the traditional autonomous WLAN 172 architecture, in which each WTP is a single physical device that 173 implements all the wireless services. 175 Centralized WLAN Architecture: It is an emerging hierarchical 176 architecture utilizing one or more centralized controllers for 177 managing a large number of WTP devices. It can be said that the full 178 wireless functions are implemented across multiple physical network 179 devices, namely, the WTPs and ACs. 181 4. Conventions 183 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 184 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 185 document are to be interpreted as described in RFC 2119 [RFC2119]. 187 5. Overview 188 5.1. Requirements and Constraints 190 The CAPWAP Protocol MIB module (CAPWAP-BASE-MIB) is designed to 191 satisfy the following requirements and constraints: 193 - From AC to centrally manage and monitor WTPs; 195 - Supports CAPWAP protocol parameters queries; 197 - Supports showing WTPs current state; 199 - Provides the information of AC, WTP, radio and station objects' 200 basic property and their relationship; 202 - Supports indicating the 'WTP Virtual Radio Interface' and PHY 203 radio's mapping relationship; 205 - Provides counters for WTP, radio's reboot event, hardware event 206 failure and so on; 208 - Provides the various notifications like channel up, join failure 209 and so on. 211 5.2. Wireless Binding MIB Modules 213 Other Standards Developing Organizations (SDOs), such as IEEE, have 214 already defined MIB modules for a specific wireless technology, e.g., 215 the MIB module in IEEE 802.11 standard [IEEE.802-11.2007]. Such MIB 216 modules are called as wireless binding MIB module. 218 5.3. Design Objectives 220 This document brings forward a mechanism to avoid redefining MIB 221 objects in the existing MIB modules for a specific wireless 222 technology, in another words, a mechanism to reuse wireless binding 223 MIB modules defined by other SDOs. 225 In summary, the CAPWAP-BASE-MIB module have the following design 226 objectives: 228 - To implement an architecture that uses SNMP for the management and 229 control of wireless networks, answering the operators requirements 230 for centralized management, whatever the deployment or configuration 231 of the network devices (centralized, distributed, or some mix); 233 - To be consistent with CAPWAP protocol; 235 - To be independent of any wireless technologies and have ability to 236 reuse wireless binding MIB modules defined by other SDOs; 238 - To enable interoperability between vendors; 240 - To meet operator requirements for centralized wireless 241 architectures. 243 5.4. Design Idea 245 The basic design idea of CAPWAP-BASE-MIB module is: 247 - The CAPWAP-BASE-MIB module MUST be run on the AC devices and is NOT 248 REQUIRED on the WTP devices. It follows same idea as CAPWAP 249 protocol: Centralized Control; 251 - It is designed to accommodate the specific needs of each wireless 252 technology in a standard way. It is independent of any wireless 253 technologies; 255 - ifIndex [RFC2863] will be used as common handler for corresponding 256 interfaces in the CAPWAP-BASE-MIB and specific wireless technologies 257 MIB modules; 259 - The operator could manage and control the centralized wireless 260 architectures using multiple MIB modules defined by multiple SDOs, 261 while keeping them loosely coupled. 263 5.5. Mechanism of Reusing Wireless Binding MIB Modules 265 Before coming to details of CAPWAP-BASE-MIB module, it will introduce 266 how CAPWAP-BASE-MIB module is able to be independent of any wireless 267 technologies and reuse wireless binding MIB modules defined by other 268 SDOs. As centralized Wireless architecture, the operator has to 269 prepare configuration on the AC before WTPs connects to AC. For any 270 wireless technology, the configuration and management of radio is 271 very important. Under centralized WLAN architecture, according to 272 [I-D.ietf-capwap-protocol-specification], a specific PHY radio could 273 be identified by identifier of a WTP and radio (WTP id + radio id). 274 As usual, wireless binding MIB modules support radio management on 275 its own. For example, the MIB tables such as Dot11OperationTable 276 [IEEE.802-11.2007] are able to support WTP radio configuration. 277 These tables use ifIndex as the index, and work well under autonomous 278 WLAN architecture. 280 To reuse such wireless binding MIB modules is very important, and the 281 key point is to reuse the idea of ifIndex. So it is required a way 282 to maintain the mapping relationship between 'WTP id + radio id' and 283 'ifIndex'. As a generic mechanism, ifIndex can identify an interface 284 in abstract way, and it does NOT care for an interface's PHY location 285 (either on the WTP or AC). AC can have interfaces of 'WTP Virtual 286 Radio Interface' ifType, which will logically represent PHY radios on 287 the WTP. It looks like that PHY radios are located on the AC, and 288 PHY location of WTP (radio) is hidden to the operator. Operator can 289 operate radios by MIB tables with ifIndex of 'WTP Virtual Radio 290 Interface'. As an abstract interface, 'WTP Virtual Radio Interface' 291 could be used by any wireless technology such as IEEE 802.11 and 292 802.16. The table of capwapBaseWirelessBindingTable in the CAPWAP- 293 BASE-MIB module is used to indicate the such mapping relationship 294 between 'WTP id + Radio id' and IfIndex. 296 5.6. CAPWAP Protocol Wireless Binding MIB Module 298 According to the CAPWAP Protocol specification 299 [I-D.ietf-capwap-protocol-specification], when defining a binding for 300 wireless technologies, the authors MUST include any necessary 301 definitions for technology-specific messages and all technology- 302 specific message elements for those messages. A CAPWAP binding 303 protocol is required for a specific wireless binding technology, 304 e.g., the protocol of [I-D.ietf-capwap-protocol-binding-ieee80211] 305 for IEEE 802.11 binding. 307 Sometimes, not all the technology-specific message elements in a 308 CAPWAP binding protocol have MIB objects defined by other SDOs. For 309 example, the protocol of [I-D.ietf-capwap-protocol-binding-ieee80211] 310 defines WLAN conception. The WLAN refers to a logical component 311 instantiated on a WTP device. A single physical WTP may operate a 312 number of WLANs. Also, Local or Split MAC modes could be specified 313 for a WLAN. The MAC mode for a WLAN is not in the scope of IEEE 314 802.11 [IEEE.802-11.2007]. In such cases, in addition to the 315 existing wireless binding MIB modules defined by other SDOs, a CAPWAP 316 protocol wireless binding MIB module is required to be defined for a 317 wireless binding, e.g, the CAPWAP Protocol Binding MIB for IEEE 318 802.11 [I-D.ietf-capwap-802dot11-mib]. 320 6. Structure of the MIB Module 322 The MIB objects were derived from the CAPWAP protocol document 323 [I-D.ietf-capwap-protocol-specification]. 325 1) capwapBaseAcNameListTable 327 The AC name list table is used to configure AC name list. 329 2) capwapBaseMacAclTable 331 The ACL table is used to configure stations' Access Control 332 List(ACL). 334 3) capwapBaseWtpStateTable 336 The WTPs status table is used to indicate each WTP's CAPWAP FSM 337 state. 339 4) capwapBaseWtpTable 341 The WTPs table is used for providing property and configuration 342 information in details for WTPs in running state. 344 5) capwapBaseWirelessBindingTable 346 The wireless binding table is used to indicate the mapping 347 relationship between logical interface of 'WTP Virtual Radio 348 Interface' ifType and PHY radio. 350 6) capwapBaseStationTable 352 The station table is used for providing stations' basic property 353 information. 355 7) capwapBaseWtpEventsStatsTable 357 The WTP events statistic table is used for collecting WTP reboot 358 count, link failure count, hardware failure count and so on. 360 8) capwapBaseRadioEventsStatsTable 362 The radio events statistic table is used for collecting radio reset 363 count, channel change count, hardware failure count and so on. 365 7. Relationship to Other MIB Modules 367 7.1. Relationship to SNMPv2-MIB Module 369 The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being 370 mandatory for all systems, and the objects apply to the entity as a 371 whole. The 'system' group provides identification of the management 372 entity and certain other system-wide data. The CAPWAP-BASE-MIB 373 module does not duplicate those objects. 375 7.2. Relationship to IF-MIB Module 377 The Interfaces Group [RFC2863] defines generic managed objects for 378 managing interfaces. This memo contains the media-specific 379 extensions to the Interfaces Group for managing WTP radio object that 380 are modeled as interfaces. 382 IF-MIB module is required to support on the AC. For each PHY radio 383 on the WTP, it will have a logical interface of 'WTP Virtual Radio 384 Interface' ifType on the AC. 'WTP Virtual Radio Interface' provides 385 a way to configure radio's parameters and query radio's traffic 386 statistics, and reuse wireless binding modules defined by other SDOs. 387 The interface MUST be modeled as an ifEntry and provide appropriate 388 interface information. 390 Also, as ifIndex [RFC2863] will be used as common handler for 391 corresponding interfaces in the CAPWAP-BASE-MIB and specific wireless 392 technologies MIB modules, the system (AC) MUST have a mechanism that 393 preserves the values of ifIndex in the ifTable at AC reboot. 395 7.3. Relationship to ENTITY-MIB Module 397 The ENTITY-MIB module [RFC4133] meets need for a standardized way of 398 representing a single agent, which supports multiple instances of one 399 MIB. It could express a certain relationship between multiple 400 entities, and provide entity properties for each entity. 402 Under the wireless centralized architectures, the SNMP agent will run 403 on the AC, and not required on the WTP. By the ENTITY-MIB module on 404 the AC, it could keep entity information such as firmware revision 405 and software revision of AC and WTPs. From the ENTITY-MIB module 406 perspective, the overall physical entity (AC) is a 'compound' of 407 multiple physical entities (WTPs which connects to AC), all entities 408 are identified by Physical index. In the capwapBaseWtpTable of 409 CAPWAP-BASE-MIB module, it uses capwapBaseWtpPhyIndex object to keep 410 the mapping relationship of WTP object between CAPWAP-BASE-MIB and 411 ENTITY-MIB module. 413 By combining the MIB modules, operators could query AC and WTP's 414 status and properties. For example, they could get WTP's current 415 status through CAPWAP-BASE-MIB module, and WTP's software revision 416 information through ENTITY-MIB module. The CAPWAP-BASE-MIB module 417 does not duplicate those objects defined in the ENTITY-MIB module. 419 7.4. Relationship to Wireless Binding MIB Modules 421 The wireless binding MIB module of a wireless technology (such as 422 [IEEE.802-11.2007]) is required to support on the AC. The CAPWAP- 423 BASE-MIB module is able to support any wireless binding. Through 424 ifIndex of 'WTP Virtual Radio Interface' ifType, it provides 425 consistent and abstract way of reusing MIB objects in the wireless 426 binding MIB modules. The CAPWAP-BASE-MIB module does not duplicate 427 those objects defined in the wireless binding MIB modules. 429 7.5. MIB Modules Required for IMPORTS 431 The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], 432 SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863], SNMP- 433 FRAMEWORK-MIB [RFC3411], INET-ADDRESS-MIB [RFC4001] and ENTITY-MIB 434 [RFC4133]. 436 8. Example of CAPWAP-BASE-MIB Module Usage 438 With the idea of 'WTP Virtual Radio Interface' in the mind, the usage 439 of the MIB modules will be easily understood. Here takes IEEE 802.11 440 binding as an example. 442 1) Identify the PHY radio by 'WTP Virtual Radio Interface' 444 According to [I-D.ietf-capwap-protocol-specification], each radio on 445 a WTP will be identified by a radio Id. Each WTP could be identified 446 by its serial number. 448 Suppose a WTP's serial number is '12345678', and first radio id is 1. 449 On the AC, the ifIndex of interface in 'WTP Virtual Radio Interface' 450 ifType is 10 which represents the PHY radio 1. The following 451 information is obtained in the CapwapBaseWirelessBindingTable. 453 In CapwapBaseWirelessBindingTable 454 { 455 capwapBaseWtpStateWtpId = '12345678', 456 capwapBaseWirelessBindingRadioId = 1, 457 capwapBaseWirelessBindingVirtualRadioIfIndex = 10, 458 capwapBaseWirelessBindingType = dot11(2) 459 } 461 By the mechanism of 'WTP Virtual Radio Interface', it seems WTP PHY 462 radios are located on the AC. The interface of 'WTP Virtual Radio 463 Interface' ifType is modeled by ifTable [RFC2863]. 465 In ifTable 466 { 467 ifIndex = 10, 468 ifDescr = 'WTP Virtual Radio Interface', 469 ifType = xxx, 470 RFC Editor - please replace xxx with the value 471 allocated by IANA for IANAifType of 'WTP Virtual Radio Interface' 472 ifMtu = 0, 473 ifSpeed = 0, 474 ifPhysAddress = '000000', 475 ifAdminStatus = true, 476 ifOperStatus = false, 477 ifLastChange = 0, 478 ifInOctets = 0, 479 ifInUcastPkts = 0, 480 ifInDiscards = 0, 481 ifInErrors = 0, 482 ifInUnknownProtos = 0, 483 ifOutOctets = 0, 484 ifOutUcastPkts = 0, 485 ifOutDiscards = 0, 486 ifOutErrors = 0 487 } 489 2) Configure specific wireless binding parameters for 'WTP Virtual 490 Radio Interface' 492 It will be done on the AC through specific wireless binding MIB 493 module such as IEEE 802.11 MIB module. 495 For example, to configure parameter for 'WTP Virtual Radio Interface' 496 by IEEE 802.11 Dot11OperationTable [IEEE.802-11.2007]. 498 In Dot11OperationTable 499 { 500 ifIndex = 10, 501 dot11MACAddress = '000000', 502 dot11RTSThreshold = 2347, 503 dot11ShortRetryLimit = 7, 504 dot11LongRetryLimit = 4, 505 dot11FragmentationThreshold = 256, 506 dot11MaxTransmitMSDULifetime = 512, 507 dot11MaxReceiveLifetime = 512, 508 dot11ManufacturerID = 'capwap', 509 dot11ProductID = 'capwap' 510 } 512 In the example, it suppose ifIndex of an interface in 'WTP Virtual 513 Radio Interface' ifType is 10. 515 3) WTP reports its current configuration status 517 According to [I-D.ietf-capwap-protocol-specification], after join 518 phase and before WTP get configuration from AC, it will report its 519 current configuration status to AC through configuration status 520 request message. The data of MIB objects will be updated on the AC. 521 For example, for IEEE 802.11 binding, WTP will update data in the 522 ifTable and IEEE 802.11 MIB module so on according to message 523 content. As an example for ifIndex 10, its ifOperStatus in ifTable 524 will be updated according to current radio operational status in the 525 CAPWAP message. 527 4) Query WTP and radio statistics data 529 After WTPs come to run status, operator could query WTP and radio 530 statistics data through CAPWAP-BASE-MIB and specific binding MIB 531 module. For example, through dot11CountersTable in the IEEE 802.11 532 MIB module, operator could query counter data for radio which is 533 identified by ifIndex of a virtual radio interface. With 534 capwapBaseWtpTable table in the CAPWAP-BASE-MIB module, operator 535 could query configuration and properties of WTPs which are in run 536 status. 538 5) MIB operations through a CAPWAP protocol wireless binding MIB 539 module 541 For example, for CAPWAP IEEE 802.11 binding protocol 542 [I-D.ietf-capwap-protocol-binding-ieee80211], Some MIB operations 543 such as MAC mode configuration for a WLAN depend on the CAPWAP 544 Protocol Binding MIB for IEEE 802.11 [I-D.ietf-capwap-802dot11-mib]. 545 In the [I-D.ietf-capwap-802dot11-mib], it will give more explain. 547 6) Query other properties of WTP 549 Operator could query MIB objects in the ENTITY-MIB module by 550 capwapBaseWtpPhyIndex in the capwapBaseWtpTable of CAPWAP-BASE-MIB 551 module. The properties of WTP such as software version, hardware 552 version and so on are available in the ENTITY-MIB module. 554 9. CAPWAP Message Element Extension 556 This section describes the CAPWAP control message extension for 557 CAPWAP protocol to support CAPWAP-BASE-MIB module. 559 To enable CAPWAP protocol timers and variables 560 [I-D.ietf-capwap-protocol-specification] manageable through CAPWAP 561 protocol, the following capwap message element extensions are defined 562 using Vendor Specific Payload message element in this section. These 563 message elements are used by WTP to report extra configuration 564 information to AC. 566 CAPWAP Message Element Vendor Identifier Element ID 568 CAPWAP Protocol Timers Id assigned by IANA 1 569 CAPWAP Protocol Variables Id assigned by IANA 2 571 9.1. CAPWAP Protocol Timers 573 0 1 2 3 574 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 575 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 576 | Vendor Identifier | 577 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 578 | Element ID | DataChannelKeepAlive | 579 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 580 | DataChannelDeadInterval | DiscoveryInterval | 581 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 582 | DTLSSessionDelete | EchoInterval | 583 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 584 | IdleTimeout | 585 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 586 | ImageDataStartTimer | MaxDiscoveryInterval | 587 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 588 | ReportInterval | RetransmitInterval | 589 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 590 | SilentInterval | StatisticsTimer | 591 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 592 | WaitDTLS | 593 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 594 Type: 37 for Vendor Specific Payload 596 Length: 34 598 Vendor Identifier: A 32-bit value containing the IANA assigned "SMI 599 Network Management Private Enterprise Codes". 601 Element ID: The Element ID field is set to 1 for CAPWAP Protocol 602 Timers. 604 DataChannelKeepAlive: A 16-bit value representing the time, 605 in seconds, that is used by the WTP to determine the next 606 must transmit the Data Channel Keep Alive. (see section 4.7.2 of 607 [I-D.ietf-capwap-protocol-specification]). 609 DataChannelDeadInterval: A 16-bit value representing the minimum 610 time, in seconds, a WTP MUST wait without having received a Data 611 Channel Alive packets may be considered dead. The value of this 612 timer MUST be no less than 2*DataChannelKeepAlive seconds and 613 no greater that 240 seconds (see section 4.7.3 of [I-D.ietf- 614 capwap-protocol-specification]). 616 DiscoveryInterval: A 16-bit value representing the minimum time, in 617 seconds, that a WTP MUST wait after receiving a Discovery Response 618 message, before initiating a DTLS handshake (see section 4.7.5 of 619 [I-D.ietf-capwap-protocol-specification]). 621 DTLSSessionDelete: A 16-bit value representing the minimum time, in 622 seconds, a WTP MUST wait for DTLS session deletion (see section 623 4.7.6 of [I-D.ietf-capwap-protocol-specification]). 625 EchoInterval: A 16-bit value representing the minimum time, in 626 seconds, between sending Echo Request messages to the AC with 627 which the WTP has joined (see section 4.7.7 of [I-D.ietf-capwap- 628 protocol-specification]). 630 IdleTimeout: A 32-bit value representing the idle timeout value that 631 the WTP SHOULD enforce for its active station. The default Idle 632 Timeout is 300 seconds (see section 4.7.8 of [I-D.ietf-capwap- 633 protocol-specification]). 635 ImageDataStartTimer: A 16-bit value representing the number of 636 seconds the WTP will wait for its peer to transmit the Image 637 Data Request (see section 4.7.9 of [I-D.ietf-capwap-protocol- 638 specification]). 640 MaxDiscoveryInterval: A 16-bit value representing the maximum time 641 allowed between sending Discovery Request messages, in seconds. 642 This value MUST be no less than 2 seconds and no greater than 180 643 seconds (see section 4.7.10 of [I-D.ietf-capwap-protocol- 644 specification]). 646 ReportInterval: A 16-bit value representing the time, in seconds, 647 that is used by the WTP to determine the interval the WTP uses 648 between sending the Decryption Error message elements to inform 649 the AC of decryption errors (see section 4.7.11 of [I-D.ietf- 650 capwap-protocol-specification]). 652 RetransmitInterval: A 16-bit value representing the minimum time, 653 in seconds, in which a non-acknowledged CAPWAP packet will be 654 retransmitted (see section 4.7.12 of [I-D.ietf-capwap-protocol- 655 specification]). 657 SilentInterval: The minimum time, in seconds, a WTP MUST wait before 658 it MAY again send Discovery Request messages or attempt to 659 establish DTLS session (see section 4.7.13 of [I-D.ietf-capwap- 660 protocol-specification]). 662 StatisticsTimer: A 16-bit value representing the time, in seconds, 663 that is used by the WTP to determine the interval the WTP uses 664 between the WTP Events Requests it transmits to the AC to 665 communicate its statistics (see section 4.7.14 of [I-D.ietf- 666 capwap-protocol-specification]). 668 WaitDTLS: A 16-bit value representing the maximum time, in seconds, 669 a WTP MUST wait without having received a DTLS Handshake message 670 from an AC. This timer MUST be greater than 30 seconds (see 671 section 4.7.15 of [I-D.ietf-capwap-protocol- 672 specification]). 674 9.2. CAPWAP Protocol Variables 676 0 1 2 3 677 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 678 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 679 | Vendor Identifier | 680 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 681 | Element ID | MaxDiscoveries | 682 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 683 | MaxFailedDTLSSessionRetry | MaxRetransmit | 684 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 686 Type: 37 for Vendor Specific Payload 688 Length: 12 690 Vendor Identifier: A 32-bit value containing the IANA assigned "SMI 691 Network Management Private Enterprise Codes". 693 Element ID: The Element ID field is set to 2 for CAPWAP Protocol 694 Variables. 696 MaxDiscoveries: A 16-bit value representing the maximum number of 697 Discovery Request messages that will be sent after a WTP boots 698 (see section 4.8.5 of [-D.ietf-capwap-protocol-specification]). 700 MaxFailedDTLSSessionRetry: A 16-bit value representing the maximum 701 number of failed DTLS session establishment attempts before the 702 CAPWAP device enters a silent period (see section 4.8.6 of 703 [I-D.ietf-capwap-protocol-specification]). 705 MaxRetransmit: A 16-bit value representing the maximum number of 706 retransmissions for a given CAPWAP packet before the link layer 707 considers the peer dead (see section 4.8.7 of [I-D.ietf-capwap- 708 protocol-specification]). 710 9.3. CAPWAP Messages for CAPWAP Control Message Extension 712 For CAPWAP Control Message Extension, the following CAPWAP messages 713 will be used. 715 9.3.1. Configuration Status Response Message 717 The following message elements MAY be included in the CAPWAP 718 Configuration Status Response Message. 720 - CAPWAP Protocol Timers, see Section Section 9.1 721 - CAPWAP Protocol Variables, see Section Section 9.2 723 9.3.2. Configuration Update Response Message 725 The following message elements MAY be included in the CAPWAP 726 Configuration Update Response Message. 728 - CAPWAP Protocol Timers, see Section Section 9.1 730 - CAPWAP Protocol Variables, see Section Section 9.2 732 10. Definitions 734 CAPWAP-BASE-MIB DEFINITIONS ::= BEGIN 736 IMPORTS 738 PhysAddress, TEXTUAL-CONVENTION, TruthValue, 739 DateAndTime, RowStatus 740 FROM SNMPv2-TC 741 InterfaceIndex 742 FROM IF-MIB 743 PhysicalIndex 744 FROM ENTITY-MIB 745 SnmpAdminString 746 FROM SNMP-FRAMEWORK-MIB 747 NOTIFICATION-GROUP, OBJECT-GROUP, MODULE-COMPLIANCE 748 FROM SNMPv2-CONF 749 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2, 750 Integer32, Unsigned32, Counter32 751 FROM SNMPv2-SMI 752 InetAddressType, InetAddress 753 FROM INET-ADDRESS-MIB; 755 capwapBaseMIB MODULE-IDENTITY 756 LAST-UPDATED "200902280000Z" -- Feb 28th, 2009 757 ORGANIZATION "IETF Control And Provisioning of Wireless Access 758 Points (CAPWAP) Working Group 759 http://www.ietf.org/html.charters/capwap-charter.html" 760 CONTACT-INFO 761 "General Discussion: capwap@frascone.com 762 To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap 764 Yang Shi 765 H3C, Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian 766 District,Beijing,China(100085) 767 Email: young@h3c.com 768 David T. Perkins 769 228 Bayview Dr 770 San Carlos, CA 94070 771 USA 772 Phone: +1 408 394-8702 773 Email: dperkins@snmpinfo.com 775 Chris Elliott 776 Cisco Systems, Inc. 777 7025 Kit Creek Rd., P.O. Box 14987 778 Research Triangle Park 27709 779 USA 780 Phone: +1 919-392-2146 781 Email: chelliot@cisco.com 783 Yong Zhang 784 Fortinet, Inc. 785 1090 Kifer Road 786 Sunnyvale, CA 94086 787 USA 788 Email: yzhang@fortinet.com" 790 DESCRIPTION 791 "Copyright (C) 2009 The Internet Society. This version of 792 the MIB module is part of RFC xxx; see the RFC itself 793 for full legal notices. 795 This MIB module contains managed object definitions for 796 the CAPWAP Protocol." 797 REVISION "200902280000Z" 798 DESCRIPTION 799 "Initial version published as RFC xxx" 800 ::= { mib-2 xxx } 802 -- Textual Conventions 804 CapwapBaseWtpIdTC ::= TEXTUAL-CONVENTION 805 DISPLAY-HINT "32a" 806 STATUS current 807 DESCRIPTION 808 "Represents an unique identifier of a WTP instance. 809 As usual, a serial number of WTP will be used." 810 SYNTAX OCTET STRING (SIZE (0..32)) 812 CapwapBaseStationIdTC ::= TEXTUAL-CONVENTION 813 DISPLAY-HINT "1x:" 814 STATUS current 815 DESCRIPTION 816 "Represents an unique identifier of a station instance. 817 As usual, the MAC address of station will be used." 818 SYNTAX OCTET STRING (SIZE (6)) 820 CapwapBaseRadioIdTC ::= TEXTUAL-CONVENTION 821 DISPLAY-HINT "d" 822 STATUS current 823 DESCRIPTION 824 "Represents an unique identifier of a radio on a WTP." 825 SYNTAX Unsigned32 (1..31) 827 CapwapBaseTunnelModeTC ::= TEXTUAL-CONVENTION 828 STATUS current 829 DESCRIPTION 830 "Represents the tunneling modes of operation that are 831 supported by the WTP. 832 The WTP MAY support more than one option, represented by 833 the bit field below: 834 localBridging(0) - Local Bridging Mode 835 dot3Tunnel(1) - 802.3 Frame Tunnel Mode 836 nativeTunnel(2) - Native Frame Tunnel Mode" 837 REFERENCE 838 "Section 4.6.43. of CAPWAP Protocol Specification, RFC xxx." 839 SYNTAX BITS { 840 localBridging(0), 841 dot3Tunnel(1), 842 nativeTunnel(2) 843 } 845 CapwapBaseMacTypeTC ::= TEXTUAL-CONVENTION 846 STATUS current 847 DESCRIPTION 848 "Represents the MAC mode of operation supported by the WTP. 849 The following enumerated values are supported: 850 localMAC(0) - Local-MAC Mode 851 splitMAC(1) - Split-MAC Mode 852 both(2) - Both Local-MAC and Split-MAC" 853 REFERENCE 854 "Section 4.6.44. of CAPWAP Protocol Specification, RFC xxx." 855 SYNTAX INTEGER { 856 localMAC(0), 857 splitMAC(1), 858 both(2) 859 } 861 CapwapBaseChannelTypeTC::= TEXTUAL-CONVENTION 862 STATUS current 863 DESCRIPTION 864 "Represents the channel type for CAPWAP protocol. 865 The following enumerated values are supported: 866 data(1) - data Channel 867 control(2) - control Channel" 868 SYNTAX INTEGER { 869 data(1), 870 control(2) 871 } 873 CapwapBaseAuthenMethodTC ::= TEXTUAL-CONVENTION 874 STATUS current 875 DESCRIPTION 876 "Represents the authentication credential type 877 for WTP. 878 The following enumerated values are supported: 879 other(1) - Other method, for example, vendor specific 880 clear(2) - Clear text and no authentication 881 x509(3) - X.509 Certificate authentication 882 psk(4) - Pre-Shared Secret authentication 883 As mandatory requirement, CAPWAP control channel 884 authentication should use DTLS, and either by certificate or 885 PSK. For data channel, DTLS is optional." 886 SYNTAX INTEGER { 887 other(1), 888 clear(2), 889 x509(3), 890 psk(4) 891 } 893 -- Top level components of this MIB module 895 -- Notifications 896 capwapBaseNotifications OBJECT IDENTIFIER 897 ::= { capwapBaseMIB 0 } 898 -- Tables, Scalars 899 capwapBaseObjects OBJECT IDENTIFIER 900 ::= { capwapBaseMIB 1 } 901 -- Conformance 902 capwapBaseConformance OBJECT IDENTIFIER 903 ::= { capwapBaseMIB 2 } 905 -- AC Objects Group 907 capwapBaseAc OBJECT IDENTIFIER 908 ::= { capwapBaseObjects 1 } 910 capwapBaseWtpSessions OBJECT-TYPE 911 SYNTAX Unsigned32 (0..65535) 912 MAX-ACCESS read-only 913 STATUS current 914 DESCRIPTION 915 "Represents the total number of WTPs which are connecting to 916 AC." 917 REFERENCE 918 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 919 ::= { capwapBaseAc 1 } 921 capwapBaseWtpSessionsLimit OBJECT-TYPE 922 SYNTAX Unsigned32 (0..65535) 923 MAX-ACCESS read-write 924 STATUS current 925 DESCRIPTION 926 "Represents the maximum number of WTP sessions configured for 927 the AC." 928 REFERENCE 929 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 930 ::= { capwapBaseAc 2 } 932 capwapBaseStationSessions OBJECT-TYPE 933 SYNTAX Unsigned32 (0..65535) 934 MAX-ACCESS read-only 935 STATUS current 936 DESCRIPTION 937 "Represents the total number of stations which are accessing 938 the wireless service provided by the AC." 939 REFERENCE 940 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 941 ::= { capwapBaseAc 3 } 943 capwapBaseStationSessionsLimit OBJECT-TYPE 944 SYNTAX Unsigned32 (0..65535) 945 MAX-ACCESS read-write 946 STATUS current 947 DESCRIPTION 948 "Represents the maximum number of station sessions configured 949 on the AC. 950 The value of the object is persistent at restart/reboot." 951 REFERENCE 952 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 953 ::= { capwapBaseAc 4 } 955 capwapBaseDataChannelDTLSPolicyOptions OBJECT-TYPE 956 SYNTAX BITS { 957 other(0), 958 clear(1), 959 dtls(2) 960 } 961 MAX-ACCESS read-only 962 STATUS current 963 DESCRIPTION 964 "The AC communicates its policy on the use of DTLS for 965 the CAPWAP data channel. 966 The AC MAY support more than one option, represented by the bit 967 field below: 968 other(0) - Other method, for example, vendor specific 969 clear(1) - Clear Text 970 dtls(2) - DTLS" 971 REFERENCE 972 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 973 ::= { capwapBaseAc 5 } 975 capwapBaseDataChannelDTLSPolicyConfig OBJECT-TYPE 976 SYNTAX INTEGER { 977 other(0), 978 clear(1), 979 dtls(2) 980 } 981 MAX-ACCESS read-write 982 STATUS current 983 DESCRIPTION 984 "Represents the security policy configured on the AC for 985 CAPWAP data channel. 986 The following enumerated values are supported: 987 other(0) - Other method, for example, vendor specific 988 clear(1) - Clear Text 989 dtls(2) - DTLS" 990 REFERENCE 991 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 992 ::= { capwapBaseAc 6 } 994 capwapBaseControlChannelAuthenOptions OBJECT-TYPE 995 SYNTAX BITS { 996 x509(0), 997 psk(1) 998 } 999 MAX-ACCESS read-only 1000 STATUS current 1001 DESCRIPTION 1002 "Represents the authentication credential type supported by the 1003 AC for control channel. 1004 The AC MAY support more than one option, represented by the bit 1005 field below: 1006 x509(0) - X.509 Certificate Based 1007 psk(1) - Pre-Shared Secret" 1008 REFERENCE 1009 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 1010 ::= { capwapBaseAc 7 } 1012 capwapBaseControlChannelAuthenConfig OBJECT-TYPE 1013 SYNTAX INTEGER { 1014 x509(1), 1015 psk(2) 1016 } 1017 MAX-ACCESS read-write 1018 STATUS current 1019 DESCRIPTION 1020 "Represents the authentication credential type configured for 1021 the AC for control channel. 1022 The following enumerated values are supported: 1023 x509(1) - X.509 Certificate Based 1024 psk(2) - Pre-Shared Secret" 1025 REFERENCE 1026 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 1027 ::= { capwapBaseAc 8 } 1029 -- capwapBaseAcNameListTable table 1031 capwapBaseAcNameListTable OBJECT-TYPE 1032 SYNTAX SEQUENCE OF CapwapBaseAcNameListEntry 1033 MAX-ACCESS not-accessible 1034 STATUS current 1035 DESCRIPTION 1036 "A table of objects that display AC name list." 1037 REFERENCE 1038 "Section 4.6.5. of CAPWAP Protocol Specification, RFC xxx." 1039 ::= { capwapBaseAc 9 } 1041 capwapBaseAcNameListEntry OBJECT-TYPE 1042 SYNTAX CapwapBaseAcNameListEntry 1043 MAX-ACCESS not-accessible 1044 STATUS current 1045 DESCRIPTION 1046 "A set of objects that configure AC name list. 1047 Values of all read-create objects in this table are persistent 1048 at restart/reboot." 1049 INDEX { capwapBaseAcNameListId } 1050 ::= { capwapBaseAcNameListTable 1 } 1052 CapwapBaseAcNameListEntry ::= SEQUENCE { 1053 capwapBaseAcNameListId Unsigned32, 1054 capwapBaseAcNameListName OCTET STRING, 1055 capwapBaseAcNameListPriority Unsigned32, 1056 capwapBaseAcNameListRowStatus RowStatus 1057 } 1059 capwapBaseAcNameListId OBJECT-TYPE 1060 SYNTAX Unsigned32 (1..255) 1061 MAX-ACCESS not-accessible 1062 STATUS current 1063 DESCRIPTION 1064 "Represents a unique id for a AC Name list." 1065 ::= { capwapBaseAcNameListEntry 1 } 1067 capwapBaseAcNameListName OBJECT-TYPE 1068 SYNTAX OCTET STRING(SIZE(512)) 1069 MAX-ACCESS read-create 1070 STATUS current 1071 DESCRIPTION 1072 "Represents the name of an AC, and it is expected to be 1073 an UTF-8 encoded string." 1074 REFERENCE 1075 "Section 4.6.5. of CAPWAP Protocol Specification, RFC xxx." 1076 ::= { capwapBaseAcNameListEntry 2 } 1078 capwapBaseAcNameListPriority OBJECT-TYPE 1079 SYNTAX Unsigned32 (1..255) 1080 MAX-ACCESS read-create 1081 STATUS current 1082 DESCRIPTION 1083 "Represents the priority order of the preferred AC. 1084 For instance, the value of one (1) is used to set the primary 1085 AC, the value of two (2) is used to set the secondary, etc." 1086 REFERENCE 1087 "Section 4.6.5. of CAPWAP Protocol Specification, RFC xxx." 1088 ::= { capwapBaseAcNameListEntry 3 } 1090 capwapBaseAcNameListRowStatus OBJECT-TYPE 1091 SYNTAX RowStatus 1092 MAX-ACCESS read-create 1093 STATUS current 1094 DESCRIPTION 1095 "This variable is used to create, modify, and/or delete a row 1096 in this table." 1097 ::= { capwapBaseAcNameListEntry 4 } 1099 -- End of capwapBaseAcNameListTable table 1101 -- capwapBaseMacAclTable table 1102 capwapBaseMacAclTable OBJECT-TYPE 1103 SYNTAX SEQUENCE OF CapwapBaseMacAclEntry 1104 MAX-ACCESS not-accessible 1105 STATUS current 1106 DESCRIPTION 1107 "A table of objects that configure station Access Control 1108 List (ACL). 1109 WTP will not provide service to the MAC addresses configured 1110 in this table." 1111 REFERENCE 1112 "Section 4.6.7. of CAPWAP Protocol Specification, RFC xxx." 1113 ::= { capwapBaseAc 10 } 1115 capwapBaseMacAclEntry OBJECT-TYPE 1116 SYNTAX CapwapBaseMacAclEntry 1117 MAX-ACCESS not-accessible 1118 STATUS current 1119 DESCRIPTION 1120 "A set of objects that configure station Access Control 1121 List (ACL). 1122 Values of all read-create objects in this table are persisten 1123 at AC restart/reboot." 1124 INDEX { capwapBaseMacAclId } 1125 ::= { capwapBaseMacAclTable 1 } 1127 CapwapBaseMacAclEntry ::= SEQUENCE { 1128 capwapBaseMacAclId Unsigned32, 1129 capwapBaseMacAclStationId CapwapBaseStationIdTC, 1130 capwapBaseMacAclRowStatus RowStatus 1131 } 1133 capwapBaseMacAclId OBJECT-TYPE 1134 SYNTAX Unsigned32 1135 MAX-ACCESS not-accessible 1136 STATUS current 1137 DESCRIPTION 1138 "Represents a unique id for a ACL." 1139 ::= { capwapBaseMacAclEntry 1 } 1141 capwapBaseMacAclStationId OBJECT-TYPE 1142 SYNTAX CapwapBaseStationIdTC 1143 MAX-ACCESS read-create 1144 STATUS current 1145 DESCRIPTION 1146 "Represents a station's MAC address which WTPs will no longer 1147 provides service to it." 1148 REFERENCE 1149 "Section 4.6.7. of CAPWAP Protocol Specification, RFC xxx." 1151 ::= { capwapBaseMacAclEntry 2 } 1153 capwapBaseMacAclRowStatus OBJECT-TYPE 1154 SYNTAX RowStatus 1155 MAX-ACCESS read-create 1156 STATUS current 1157 DESCRIPTION 1158 "This variable is used to create, modify, and/or delete a row 1159 in this table." 1160 ::= { capwapBaseMacAclEntry 3 } 1162 -- End of capwapBaseMacAclTable table 1164 -- End of AC Objects Group 1166 -- WTP Objects Group 1168 capwapBaseWtps OBJECT IDENTIFIER 1169 ::= { capwapBaseObjects 2 } 1171 -- capwapBaseWtpStateTable table 1173 capwapBaseWtpStateTable OBJECT-TYPE 1174 SYNTAX SEQUENCE OF CapwapBaseWtpStateEntry 1175 MAX-ACCESS not-accessible 1176 STATUS current 1177 DESCRIPTION 1178 "A table of objects that display WTP CAPWAP FSM state." 1179 ::= { capwapBaseWtps 1 } 1181 capwapBaseWtpStateEntry OBJECT-TYPE 1182 SYNTAX CapwapBaseWtpStateEntry 1183 MAX-ACCESS not-accessible 1184 STATUS current 1185 DESCRIPTION 1186 "A set of objects that display WTP CAPWAP FSM state." 1187 INDEX { capwapBaseWtpStateWtpId } 1188 ::= { capwapBaseWtpStateTable 1 } 1190 CapwapBaseWtpStateEntry ::= SEQUENCE { 1191 capwapBaseWtpStateWtpId CapwapBaseWtpIdTC, 1192 capwapBaseWtpStateWtpIpAddressType InetAddressType, 1193 capwapBaseWtpStateWtpIpAddress InetAddress, 1194 capwapBaseWtpStateWtpPhyAddress PhysAddress, 1195 capwapBaseWtpState INTEGER 1196 } 1198 capwapBaseWtpStateWtpId OBJECT-TYPE 1199 SYNTAX CapwapBaseWtpIdTC 1200 MAX-ACCESS not-accessible 1201 STATUS current 1202 DESCRIPTION 1203 "Represents the unique identifier of a WTP." 1204 ::= { capwapBaseWtpStateEntry 1 } 1206 capwapBaseWtpStateWtpIpAddressType OBJECT-TYPE 1207 SYNTAX InetAddressType 1208 MAX-ACCESS read-only 1209 STATUS current 1210 DESCRIPTION 1211 "Represents the type of IP address of a WTP." 1212 ::= { capwapBaseWtpStateEntry 2 } 1214 capwapBaseWtpStateWtpIpAddress OBJECT-TYPE 1215 SYNTAX InetAddress 1216 MAX-ACCESS read-only 1217 STATUS current 1218 DESCRIPTION 1219 "Represents the IP address of a WTP." 1220 ::= { capwapBaseWtpStateEntry 3 } 1222 capwapBaseWtpStateWtpPhyAddress OBJECT-TYPE 1223 SYNTAX PhysAddress 1224 MAX-ACCESS read-only 1225 STATUS current 1226 DESCRIPTION 1227 "Represents the PHY address of a WTP." 1228 ::= { capwapBaseWtpStateEntry 4 } 1230 capwapBaseWtpState OBJECT-TYPE 1231 SYNTAX INTEGER { 1232 dtls(1), 1233 join(2), 1234 image(3), 1235 configure(4), 1236 dataCheck(5), 1237 run(6), 1238 clear(7), 1239 unknown(8) 1240 } 1241 MAX-ACCESS read-only 1242 STATUS current 1243 DESCRIPTION 1244 "Represents the various possible CAPWAP FSM states of WTP 1245 The following enumerated values are supported: 1247 dtls(1) - DTLS negotiation states, which include 1248 DTLS Setup, Authorize, DTLS Connect 1249 join(2) - WTP is joining with AC 1250 image(3) - WTP is downloading software 1251 configure(4) - WTP is getting configuration from AC 1252 dataCheck(5) - AC is waiting for the Data Channel Keep 1253 Alive Packet 1254 run(6) - WTP comes to run state 1255 clear(7) - WTP recoveries default configuration 1256 unknown(8) - Operator already prepare configuration 1257 for WTP, while WTP has not contact with AC 1258 till now" 1259 REFERENCE 1260 "Section 2.3.1. of CAPWAP Protocol Specification, RFC xxx." 1261 ::= { capwapBaseWtpStateEntry 5 } 1263 -- End of capwapBaseWtpStateTable Table 1265 -- capwapBaseWtpTable Table 1267 capwapBaseWtpTable OBJECT-TYPE 1268 SYNTAX SEQUENCE OF CapwapBaseWtpEntry 1269 MAX-ACCESS not-accessible 1270 STATUS current 1271 DESCRIPTION 1272 "A table of objects that display and control WTPs in 1273 running state. Values of all read-write objects in this 1274 table are persistent at restart/reboot." 1275 ::= { capwapBaseWtps 2 } 1277 capwapBaseWtpEntry OBJECT-TYPE 1278 SYNTAX CapwapBaseWtpEntry 1279 MAX-ACCESS not-accessible 1280 STATUS current 1281 DESCRIPTION 1282 "A set of objects that display and control a WTP in 1283 running state." 1284 INDEX { capwapBaseWtpCurrId } 1285 ::= { capwapBaseWtpTable 1 } 1287 CapwapBaseWtpEntry ::= SEQUENCE { 1288 capwapBaseWtpCurrId CapwapBaseWtpIdTC, 1289 capwapBaseWtpPhyIndex PhysicalIndex, 1290 capwapBaseWtpName OCTET STRING, 1291 capwapBaseWtpLocation OCTET STRING, 1292 capwapBaseWtpBaseMacAddress PhysAddress, 1293 capwapBaseWtpTunnelModeOptions CapwapBaseTunnelModeTC, 1294 capwapBaseWtpMacTypeOptions CapwapBaseMacTypeTC, 1295 capwapBaseWtpDiscoveryType INTEGER, 1296 capwapBaseWtpRadiosInUseNum Unsigned32, 1297 capwapBaseWtpRadioNumLimit Unsigned32, 1298 capwapBaseWtpStaticIpEnable TruthValue, 1299 capwapBaseWtpStaticIpType InetAddressType, 1300 capwapBaseWtpStaticIp InetAddress, 1301 capwapBaseWtpNetmask InetAddress, 1302 capwapBaseWtpGateway InetAddress, 1303 capwapBaseWtpFallbackEnable INTEGER, 1304 capwapBaseWtpRetransmitCount Counter32, 1305 capwapBaseWtpMaxDiscoveries Unsigned32, 1306 capwapBaseWtpMaxFailedDTLSSessionRetry Unsigned32, 1307 capwapBaseWtpMaxRetransmit Unsigned32, 1308 capwapBaseWtpDataChannelKeepAliveTimer Unsigned32, 1309 capwapBaseWtpDataChannelDeadInterval Unsigned32, 1310 capwapBaseWtpDiscoveryInterval Unsigned32, 1311 capwapBaseWtpDTLSSessionDeleteTimer Unsigned32, 1312 capwapBaseWtpEchoInterval Unsigned32, 1313 capwapBaseWtpIdleTimeout Unsigned32, 1314 capwapBaseWtpImageDataStartTimer Unsigned32, 1315 capwapBaseWtpMaxDiscoveryInterval Unsigned32, 1316 capwapBaseWtpReportInterval Unsigned32, 1317 capwapBaseWtpRetransmitInterval Unsigned32, 1318 capwapBaseWtpSilentInterval Unsigned32, 1319 capwapBaseWtpStatisticsTimer Unsigned32, 1320 capwapBaseWtpWaitDTLSTimer Unsigned32, 1321 capwapBaseWtpEcnSupport INTEGER 1322 } 1324 capwapBaseWtpCurrId OBJECT-TYPE 1325 SYNTAX CapwapBaseWtpIdTC 1326 MAX-ACCESS not-accessible 1327 STATUS current 1328 DESCRIPTION 1329 "Represents the unique identifier of a WTP which is 1330 in running state." 1331 ::= { capwapBaseWtpEntry 1 } 1333 capwapBaseWtpPhyIndex OBJECT-TYPE 1334 SYNTAX PhysicalIndex 1335 MAX-ACCESS read-only 1336 STATUS current 1337 DESCRIPTION 1338 "Represents the unique physical index of a physical entity 1339 in the ENTITY-MIB module. The information such as software 1340 version of specific WTP could be accessed through the index." 1341 ::= { capwapBaseWtpEntry 2 } 1343 capwapBaseWtpName OBJECT-TYPE 1344 SYNTAX OCTET STRING(SIZE(512)) 1345 MAX-ACCESS read-write 1346 STATUS current 1347 DESCRIPTION 1348 "Represents the name of a WTP." 1349 REFERENCE 1350 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 1351 ::= { capwapBaseWtpEntry 3 } 1353 capwapBaseWtpLocation OBJECT-TYPE 1354 SYNTAX OCTET STRING(SIZE(1024)) 1355 MAX-ACCESS read-write 1356 STATUS current 1357 DESCRIPTION 1358 "Represents the location of a WTP." 1359 REFERENCE 1360 "Section 4.6.30. of CAPWAP Protocol Specification, RFC xxx." 1361 ::= { capwapBaseWtpEntry 4 } 1363 capwapBaseWtpBaseMacAddress OBJECT-TYPE 1364 SYNTAX PhysAddress 1365 MAX-ACCESS read-only 1366 STATUS current 1367 DESCRIPTION 1368 "Represents the WTP's Base MAC Address, which MAY be assigned 1369 to the primary Ethernet interface." 1370 REFERENCE 1371 "Section 4.6.40. of CAPWAP Protocol Specification, RFC xxx." 1372 ::= { capwapBaseWtpEntry 5 } 1374 capwapBaseWtpTunnelModeOptions OBJECT-TYPE 1375 SYNTAX CapwapBaseTunnelModeTC 1376 MAX-ACCESS read-only 1377 STATUS current 1378 DESCRIPTION 1379 "Represents the tunneling modes of operation supported by 1380 the WTP." 1381 REFERENCE 1382 "Section 4.6.43. of CAPWAP Protocol Specification, RFC xxx." 1383 ::= { capwapBaseWtpEntry 6 } 1385 capwapBaseWtpMacTypeOptions OBJECT-TYPE 1386 SYNTAX CapwapBaseMacTypeTC 1387 MAX-ACCESS read-only 1388 STATUS current 1389 DESCRIPTION 1390 "Represents the MAC mode of operation supported by the WTP." 1392 REFERENCE 1393 "Section 4.6.44. of CAPWAP Protocol Specification, RFC xxx." 1394 ::= { capwapBaseWtpEntry 7 } 1396 capwapBaseWtpDiscoveryType OBJECT-TYPE 1397 SYNTAX INTEGER { 1398 unknown(0), 1399 staticConfig(1), 1400 dhcp(2), 1401 dns(3), 1402 acRef(4) 1403 } 1404 MAX-ACCESS read-only 1405 STATUS current 1406 DESCRIPTION 1407 "Represents how WTP discovers the AC. 1408 The following enumerated values are supported: 1409 unknown(0) - Unknown 1410 staticConfig(1) - Static Configuration 1411 dhcp(2) - DHCP 1412 dns(3) - DNS 1413 acRef(4) - AC Referral" 1414 REFERENCE 1415 "Section 4.6.21. of CAPWAP Protocol Specification, RFC xxx." 1416 ::= { capwapBaseWtpEntry 8 } 1418 capwapBaseWtpRadiosInUseNum OBJECT-TYPE 1419 SYNTAX Unsigned32 (0..255) 1420 MAX-ACCESS read-only 1421 STATUS current 1422 DESCRIPTION 1423 "Represents the number of radios in use on the WTP." 1424 REFERENCE 1425 "Section 4.6.41. of CAPWAP Protocol Specification, RFC xxx." 1426 ::= { capwapBaseWtpEntry 9 } 1428 capwapBaseWtpRadioNumLimit OBJECT-TYPE 1429 SYNTAX Unsigned32 (0..255) 1430 MAX-ACCESS read-only 1431 STATUS current 1432 DESCRIPTION 1433 "Represents the maximum radio number supported by the WTP." 1434 REFERENCE 1435 "Section 4.6.41. of CAPWAP Protocol Specification, RFC xxx." 1436 ::= { capwapBaseWtpEntry 10 } 1438 capwapBaseWtpStaticIpEnable OBJECT-TYPE 1439 SYNTAX TruthValue 1440 MAX-ACCESS read-write 1441 STATUS current 1442 DESCRIPTION 1443 "Represents whether the WTP should use a static IP address 1444 or not. A value of false disables the static IP address, 1445 while a value of true enables it." 1446 REFERENCE 1447 "Section 4.6.48. of CAPWAP Protocol Specification, RFC xxx." 1448 ::= { capwapBaseWtpEntry 11 } 1450 capwapBaseWtpStaticIpType OBJECT-TYPE 1451 SYNTAX InetAddressType 1452 MAX-ACCESS read-write 1453 STATUS current 1454 DESCRIPTION 1455 "Represents whether WTP uses IPv4 or IPv6 static IP address." 1456 ::= { capwapBaseWtpEntry 12 } 1458 capwapBaseWtpStaticIp OBJECT-TYPE 1459 SYNTAX InetAddress 1460 MAX-ACCESS read-write 1461 STATUS current 1462 DESCRIPTION 1463 "When capwapBaseWtpStaticIpEnable is true, it represents the 1464 static IP address to assign to the WTP." 1465 REFERENCE 1466 "Section 4.6.48. of CAPWAP Protocol Specification, RFC xxx." 1467 ::= { capwapBaseWtpEntry 13 } 1469 capwapBaseWtpNetmask OBJECT-TYPE 1470 SYNTAX InetAddress 1471 MAX-ACCESS read-write 1472 STATUS current 1473 DESCRIPTION 1474 "When capwapBaseWtpStaticIpEnable is true, it represents the 1475 netmask to assign to the WTP." 1476 REFERENCE 1477 "Section 4.6.48. of CAPWAP Protocol Specification, RFC xxx." 1478 ::= { capwapBaseWtpEntry 14 } 1480 capwapBaseWtpGateway OBJECT-TYPE 1481 SYNTAX InetAddress 1482 MAX-ACCESS read-write 1483 STATUS current 1484 DESCRIPTION 1485 "When capwapBaseWtpStaticIpEnable is true, it represents the 1486 gateway to assign to the WTP." 1487 REFERENCE 1488 "Section 4.6.48. of CAPWAP Protocol Specification, RFC xxx." 1489 ::= { capwapBaseWtpEntry 15 } 1491 capwapBaseWtpFallbackEnable OBJECT-TYPE 1492 SYNTAX INTEGER { 1493 enabled(1), 1494 disabled(2) 1495 } 1496 MAX-ACCESS read-write 1497 STATUS current 1498 DESCRIPTION 1499 "Represents whether to enable or disable automatic CAPWAP 1500 fallback in the event that a WTP detects its preferred AC, and 1501 is not currently connected to it. 1502 The following enumerated values are supported: 1503 enabled(1) - The fallback mode is enabled 1504 disabled(2) - The fallback mode is disabled" 1505 REFERENCE 1506 "Section 4.6.42. of CAPWAP Protocol Specification, RFC xxx." 1507 DEFVAL { enabled } 1508 ::= { capwapBaseWtpEntry 16 } 1510 capwapBaseWtpRetransmitCount OBJECT-TYPE 1511 SYNTAX Counter32 1512 MAX-ACCESS read-only 1513 STATUS current 1514 DESCRIPTION 1515 "Represents the number of retransmissions for a given 1516 CAPWAP packet." 1517 REFERENCE 1518 "Section 4.8.8. of CAPWAP Protocol Specification, RFC xxx." 1519 ::= { capwapBaseWtpEntry 17 } 1521 capwapBaseWtpMaxDiscoveries OBJECT-TYPE 1522 SYNTAX Unsigned32 1523 MAX-ACCESS read-only 1524 STATUS current 1525 DESCRIPTION 1526 "Represent the maximum number of Discovery Request messages 1527 that will be sent after a WTP boots." 1528 REFERENCE 1529 "Section 4.8.5. of CAPWAP Protocol Specification, RFC xxx." 1530 DEFVAL { 10 } 1531 ::= { capwapBaseWtpEntry 18 } 1533 capwapBaseWtpMaxFailedDTLSSessionRetry OBJECT-TYPE 1534 SYNTAX Unsigned32 1535 MAX-ACCESS read-only 1536 STATUS current 1537 DESCRIPTION 1538 "Represent the maximum number of failed DTLS session 1539 establishment attempts before the CAPWAP device enters a 1540 silent period." 1541 REFERENCE 1542 "Section 4.8.6. of CAPWAP Protocol Specification, RFC xxx." 1543 DEFVAL { 3 } 1544 ::= { capwapBaseWtpEntry 19 } 1546 capwapBaseWtpMaxRetransmit OBJECT-TYPE 1547 SYNTAX Unsigned32 1548 MAX-ACCESS read-only 1549 STATUS current 1550 DESCRIPTION 1551 "Represent the maximum number of retransmission for a given 1552 CAPWAP packet before the link layer considers the peer dead." 1553 REFERENCE 1554 "Section 4.8.7. of CAPWAP Protocol Specification, RFC xxx." 1555 DEFVAL { 5 } 1556 ::= { capwapBaseWtpEntry 20 } 1558 capwapBaseWtpDataChannelKeepAliveTimer OBJECT-TYPE 1559 SYNTAX Unsigned32 1560 UNITS "second" 1561 MAX-ACCESS read-only 1562 STATUS current 1563 DESCRIPTION 1564 "Represents the next opportunity, in seconds, the WTP must 1565 transmit the Data Channel Keep Alive message." 1566 REFERENCE 1567 "Section 4.7.2. of CAPWAP Protocol Specification, RFC xxx." 1568 DEFVAL { 30 } 1569 ::= { capwapBaseWtpEntry 21 } 1571 capwapBaseWtpDataChannelDeadInterval OBJECT-TYPE 1572 SYNTAX Unsigned32 (0..240) 1573 UNITS "second" 1574 MAX-ACCESS read-only 1575 STATUS current 1576 DESCRIPTION 1577 "Represents the minimum time, in seconds, a WTP MUST wait 1578 without having received a Data Channel Keep Alive packet 1579 before the destination for the Data Channel Keep Alive 1580 packets may be considered dead." 1581 REFERENCE 1582 "Section 4.7.3. of CAPWAP Protocol Specification, RFC xxx." 1583 DEFVAL { 60 } 1584 ::= { capwapBaseWtpEntry 22 } 1586 capwapBaseWtpDiscoveryInterval OBJECT-TYPE 1587 SYNTAX Unsigned32 1588 UNITS "second" 1589 MAX-ACCESS read-only 1590 STATUS current 1591 DESCRIPTION 1592 "Represents the minimum time, in seconds, that a WTP MUST 1593 wait after receiving a Discovery Response message, before 1594 initiating a DTLS handshake." 1595 REFERENCE 1596 "Section 4.7.5. of CAPWAP Protocol Specification, RFC xxx." 1597 DEFVAL { 5 } 1598 ::= { capwapBaseWtpEntry 23 } 1600 capwapBaseWtpDTLSSessionDeleteTimer OBJECT-TYPE 1601 SYNTAX Unsigned32 1602 UNITS "second" 1603 MAX-ACCESS read-only 1604 STATUS current 1605 DESCRIPTION 1606 "Represents the minimum time, in seconds, a WTP MUST wait 1607 for DTLS session deletion." 1608 REFERENCE 1609 "Section 4.7.6. of CAPWAP Protocol Specification, RFC xxx." 1610 DEFVAL { 5 } 1611 ::= { capwapBaseWtpEntry 24 } 1613 capwapBaseWtpEchoInterval OBJECT-TYPE 1614 SYNTAX Unsigned32 1615 UNITS "second" 1616 MAX-ACCESS read-write 1617 STATUS current 1618 DESCRIPTION 1619 "Represents the minimum time, in seconds, between sending Echo 1620 Request messages to the AC with which the WTP has joined." 1621 REFERENCE 1622 "Section 4.7.7. of CAPWAP Protocol Specification, RFC xxx." 1623 DEFVAL { 30 } 1624 ::= { capwapBaseWtpEntry 25 } 1626 capwapBaseWtpIdleTimeout OBJECT-TYPE 1627 SYNTAX Unsigned32 1628 UNITS "second" 1629 MAX-ACCESS read-write 1630 STATUS current 1631 DESCRIPTION 1632 "Represents the idle timeout value that the WTP SHOULD enforce 1633 for its active stations." 1634 REFERENCE 1635 "Section 4.7.8. of CAPWAP Protocol Specification, RFC xxx." 1636 DEFVAL { 300 } 1637 ::= { capwapBaseWtpEntry 26 } 1639 capwapBaseWtpImageDataStartTimer OBJECT-TYPE 1640 SYNTAX Unsigned32 1641 UNITS "second" 1642 MAX-ACCESS read-only 1643 STATUS current 1644 DESCRIPTION 1645 "Represents the number of seconds the WTP will wait for its peer 1646 to transmit the Image Data Request." 1647 REFERENCE 1648 "Section 4.7.9. of CAPWAP Protocol Specification, RFC xxx." 1649 DEFVAL { 30 } 1650 ::= { capwapBaseWtpEntry 27 } 1652 capwapBaseWtpMaxDiscoveryInterval OBJECT-TYPE 1653 SYNTAX Unsigned32 (2..180) 1654 UNITS "second" 1655 MAX-ACCESS read-write 1656 STATUS current 1657 DESCRIPTION 1658 "Represents the maximum time allowed between sending Discovery 1659 Request messages, in seconds. This value MUST be no less than 1660 2 seconds and no greater than 180 seconds." 1661 REFERENCE 1662 "Section 4.7.10. of CAPWAP Protocol Specification, RFC xxx." 1663 DEFVAL { 20 } 1664 ::= { capwapBaseWtpEntry 28 } 1666 capwapBaseWtpReportInterval OBJECT-TYPE 1667 SYNTAX Unsigned32 1668 UNITS "second" 1669 MAX-ACCESS read-write 1670 STATUS current 1671 DESCRIPTION 1672 "Represents the interval for WTP to send Decryption Error 1673 report." 1674 REFERENCE 1675 "Section 4.7.11. of CAPWAP Protocol Specification, RFC xxx." 1676 DEFVAL { 120 } 1677 ::= { capwapBaseWtpEntry 29 } 1679 capwapBaseWtpRetransmitInterval OBJECT-TYPE 1680 SYNTAX Unsigned32 1681 UNITS "second" 1682 MAX-ACCESS read-only 1683 STATUS current 1684 DESCRIPTION 1685 "Represents the minimum time, in seconds, in which a 1686 non-acknowledged CAPWAP packet will be retransmitted." 1687 REFERENCE 1688 "Section 4.7.12. of CAPWAP Protocol Specification, RFC xxx." 1689 DEFVAL { 3 } 1690 ::= { capwapBaseWtpEntry 30 } 1692 capwapBaseWtpSilentInterval OBJECT-TYPE 1693 SYNTAX Unsigned32 1694 UNITS "second" 1695 MAX-ACCESS read-write 1696 STATUS current 1697 DESCRIPTION 1698 "Represents the minimum time, in seconds, a WTP MUST wait 1699 before it MAY again send Discovery Request messages or attempt 1700 to a establish DTLS session." 1701 REFERENCE 1702 "Section 4.7.13. of CAPWAP Protocol Specification, RFC xxx." 1703 DEFVAL { 30 } 1704 ::= { capwapBaseWtpEntry 31 } 1706 capwapBaseWtpStatisticsTimer OBJECT-TYPE 1707 SYNTAX Unsigned32 1708 UNITS "second" 1709 MAX-ACCESS read-write 1710 STATUS current 1711 DESCRIPTION 1712 "Represents the interval the WTP uses between the WTP Events 1713 Requests it transmits to the AC to communicate its statistics, 1714 in seconds." 1715 REFERENCE 1716 "Section 4.7.14. of CAPWAP Protocol Specification, RFC xxx." 1717 DEFVAL { 120 } 1718 ::= { capwapBaseWtpEntry 32 } 1720 capwapBaseWtpWaitDTLSTimer OBJECT-TYPE 1721 SYNTAX Unsigned32 (30..4294967295) 1722 UNITS "second" 1723 MAX-ACCESS read-write 1724 STATUS current 1725 DESCRIPTION 1726 "Represents the maximum time, in seconds, an AC MUST wait 1727 without having received a DTLS Handshake message from an AC. 1729 This timer MUST be greater than 30 seconds." 1730 REFERENCE 1731 "Section 4.7.15. of CAPWAP Protocol Specification, RFC xxx." 1732 DEFVAL { 60 } 1733 ::= { capwapBaseWtpEntry 33 } 1735 capwapBaseWtpEcnSupport OBJECT-TYPE 1736 SYNTAX INTEGER { 1737 limited(0), 1738 fullAndLimited(1) 1739 } 1740 MAX-ACCESS read-write 1741 STATUS current 1742 DESCRIPTION 1743 "Represents the support for the Explicit Congestion Notification 1744 (ECN) bits, as defined in [RFC3168]." 1745 REFERENCE 1746 "Section 4.7.25. of CAPWAP Protocol Specification, RFC xxx." 1747 ::= { capwapBaseWtpEntry 34 } 1749 -- End of capwapBaseWtpTable table 1751 -- capwapBaseWirelessBindingTable Table 1753 capwapBaseWirelessBindingTable OBJECT-TYPE 1754 SYNTAX SEQUENCE OF CapwapBaseWirelessBindingEntry 1755 MAX-ACCESS not-accessible 1756 STATUS current 1757 DESCRIPTION 1758 "A table of objects that display the mapping relationship 1759 between specific interface of 'WTP Virtual Radio Interface' 1760 ifType and PHY radio, and wireless binding type for 1761 a specific radio. The mapping relationship in this table 1762 is persistent at restart/reboot." 1763 ::= { capwapBaseWtps 3 } 1765 capwapBaseWirelessBindingEntry OBJECT-TYPE 1766 SYNTAX CapwapBaseWirelessBindingEntry 1767 MAX-ACCESS not-accessible 1768 STATUS current 1769 DESCRIPTION 1770 "A set of objects that display the mapping relationship 1771 between 'WTP Virtual Radio Interface' and PHY radio, and 1772 wireless binding type for a specific radio." 1773 INDEX { 1774 capwapBaseWtpStateWtpId, 1775 capwapBaseWirelessBindingRadioId 1777 } 1778 ::= { capwapBaseWirelessBindingTable 1 } 1780 CapwapBaseWirelessBindingEntry ::= SEQUENCE { 1781 capwapBaseWirelessBindingRadioId CapwapBaseRadioIdTC, 1782 capwapBaseWirelessBindingVirtualRadioIfIndex InterfaceIndex, 1783 capwapBaseWirelessBindingType INTEGER 1784 } 1786 capwapBaseWirelessBindingRadioId OBJECT-TYPE 1787 SYNTAX CapwapBaseRadioIdTC 1788 MAX-ACCESS not-accessible 1789 STATUS current 1790 DESCRIPTION 1791 "Represents the identifier of a PHY radio on a WTP, and only 1792 requires unique on a WTP. 1793 For example, WTP A and WTP B will use same value of 1794 capwapBaseWirelessBindingRadioId for their first radio." 1795 REFERENCE 1796 "Section 4.3. of CAPWAP Protocol Specification, RFC xxx." 1797 ::= { capwapBaseWirelessBindingEntry 1 } 1799 capwapBaseWirelessBindingVirtualRadioIfIndex OBJECT-TYPE 1800 SYNTAX InterfaceIndex 1801 MAX-ACCESS read-only 1802 STATUS current 1803 DESCRIPTION 1804 "Represents the index value that uniquely identifies a 1805 'WLAN Virtual Radio Interface'. The interface identified by 1806 a particular value of this index is the same interface as 1807 identified by the same value of ifIndex. 1808 Before WTPs connect to AC and get configuration, operator 1809 will prepare configuration for them. On the AC, there are 1810 interfaces of 'WTP Virtual Radio Interface' ifType which 1811 represent PHY radio interfaces on the WTP. 1812 As most MIB modules use ifIndex to identify an interface for 1813 configuration and statistic data, for example, IEEE 802.11 MIB 1814 module. It will be very easy to reuse other wireless binding 1815 MIB modules through 'WTP Virtual Radio Interface'." 1816 ::= { capwapBaseWirelessBindingEntry 2 } 1818 capwapBaseWirelessBindingType OBJECT-TYPE 1819 SYNTAX INTEGER { 1820 dot11(1), 1821 epc(3) 1822 } 1823 MAX-ACCESS read-only 1824 STATUS current 1825 DESCRIPTION 1826 "Represents the wireless binding type for radio. 1827 The following enumerated values are supported: 1828 dot11(1) - IEEE 802.11 1829 epc(3) - EPCGlobal" 1830 REFERENCE 1831 "Section 4.3. of CAPWAP Protocol Specification, RFC xxx." 1832 ::= { capwapBaseWirelessBindingEntry 3 } 1834 -- End of capwapBaseWirelessBindingTable Table 1836 -- capwapBaseStationTable Table 1838 capwapBaseStationTable OBJECT-TYPE 1839 SYNTAX SEQUENCE OF CapwapBaseStationEntry 1840 MAX-ACCESS not-accessible 1841 STATUS current 1842 DESCRIPTION 1843 "A table of objects that display stations which are accessing 1844 the wireless service provided by the AC." 1845 REFERENCE 1846 "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." 1847 ::= { capwapBaseWtps 4 } 1849 capwapBaseStationEntry OBJECT-TYPE 1850 SYNTAX CapwapBaseStationEntry 1851 MAX-ACCESS not-accessible 1852 STATUS current 1853 DESCRIPTION 1854 "A set of objects that display a station which is 1855 associated with the specific radio on the WTP." 1856 INDEX { 1857 capwapBaseWtpCurrId, 1858 capwapBaseWirelessBindingRadioId, 1859 capwapBaseStationId 1860 } 1861 ::= { capwapBaseStationTable 1 } 1863 CapwapBaseStationEntry ::= SEQUENCE { 1864 capwapBaseStationId CapwapBaseStationIdTC, 1865 capwapBaseStationAddedTime DateAndTime, 1866 capwapBaseStationVlanName SnmpAdminString 1867 } 1869 capwapBaseStationId OBJECT-TYPE 1870 SYNTAX CapwapBaseStationIdTC 1871 MAX-ACCESS not-accessible 1872 STATUS current 1873 DESCRIPTION 1874 "Represents the unique identifier of the station." 1875 REFERENCE 1876 "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." 1877 ::= { capwapBaseStationEntry 1 } 1879 capwapBaseStationAddedTime OBJECT-TYPE 1880 SYNTAX DateAndTime 1881 MAX-ACCESS read-only 1882 STATUS current 1883 DESCRIPTION 1884 "Represents the time when the station is added." 1885 REFERENCE 1886 "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." 1887 ::= { capwapBaseStationEntry 2 } 1889 capwapBaseStationVlanName OBJECT-TYPE 1890 SYNTAX SnmpAdminString (SIZE (0..32)) 1891 MAX-ACCESS read-only 1892 STATUS current 1893 DESCRIPTION 1894 "Represents VLAN name to which the station is associated." 1895 REFERENCE 1896 "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." 1897 ::= { capwapBaseStationEntry 3 } 1899 -- End of capwapBaseStationTable Table 1901 -- capwapBaseWtpEventsStatsTable 1903 capwapBaseWtpEventsStatsTable OBJECT-TYPE 1904 SYNTAX SEQUENCE OF CapwapBaseWtpEventsStatsEntry 1905 MAX-ACCESS not-accessible 1906 STATUS current 1907 DESCRIPTION 1908 "A table of objects that display WTPs' events statistics." 1909 REFERENCE 1910 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1911 ::= { capwapBaseWtps 5 } 1913 capwapBaseWtpEventsStatsEntry OBJECT-TYPE 1914 SYNTAX CapwapBaseWtpEventsStatsEntry 1915 MAX-ACCESS not-accessible 1916 STATUS current 1917 DESCRIPTION 1918 "A set of objects that display the events statistic data 1919 of a WTP." 1920 REFERENCE 1921 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1922 INDEX { capwapBaseWtpCurrId } 1923 ::= { capwapBaseWtpEventsStatsTable 1 } 1925 CapwapBaseWtpEventsStatsEntry ::= SEQUENCE { 1926 capwapBaseWtpEventsStatsRebootCount Counter32, 1927 capwapBaseWtpEventsStatsInitCount Counter32, 1928 capwapBaseWtpEventsStatsLinkFailureCount Counter32, 1929 capwapBaseWtpEventsStatsSwFailureCount Counter32, 1930 capwapBaseWtpEventsStatsHwFailureCount Counter32, 1931 capwapBaseWtpEventsStatsOtherFailureCount Counter32, 1932 capwapBaseWtpEventsStatsUnknownFailureCount Counter32, 1933 capwapBaseWtpEventsStatsLastFailureType INTEGER 1934 } 1936 capwapBaseWtpEventsStatsRebootCount OBJECT-TYPE 1937 SYNTAX Counter32 1938 MAX-ACCESS read-only 1939 STATUS current 1940 DESCRIPTION 1941 "Represents the number of reboots that have occurred due to a 1942 WTP crash. A value of 65535 implies that this information is 1943 not available on the WTP." 1944 REFERENCE 1945 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1946 ::= { capwapBaseWtpEventsStatsEntry 1 } 1948 capwapBaseWtpEventsStatsInitCount OBJECT-TYPE 1949 SYNTAX Counter32 1950 MAX-ACCESS read-only 1951 STATUS current 1952 DESCRIPTION 1953 "Represents the number of reboots that have occurred at the 1954 request of a CAPWAP protocol message, such as a change in 1955 configuration that required a reboot or an explicit CAPWAP 1956 protocol reset request. A value of 65535 implies that this 1957 information is not available on the WTP." 1958 REFERENCE 1959 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1960 ::= { capwapBaseWtpEventsStatsEntry 2 } 1962 capwapBaseWtpEventsStatsLinkFailureCount OBJECT-TYPE 1963 SYNTAX Counter32 1964 MAX-ACCESS read-only 1965 STATUS current 1966 DESCRIPTION 1967 "Represents the number of times that a CAPWAP protocol 1968 connection with an AC has failed due to link failure." 1969 REFERENCE 1970 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1971 ::= { capwapBaseWtpEventsStatsEntry 3 } 1973 capwapBaseWtpEventsStatsSwFailureCount OBJECT-TYPE 1974 SYNTAX Counter32 1975 MAX-ACCESS read-only 1976 STATUS current 1977 DESCRIPTION 1978 "Represents the number of times that a CAPWAP protocol 1979 connection with an AC has failed due to software related 1980 reasons." 1981 REFERENCE 1982 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1983 ::= { capwapBaseWtpEventsStatsEntry 4 } 1985 capwapBaseWtpEventsStatsHwFailureCount OBJECT-TYPE 1986 SYNTAX Counter32 1987 MAX-ACCESS read-only 1988 STATUS current 1989 DESCRIPTION 1990 "Represents the number of times that a CAPWAP protocol 1991 connection with an AC has failed due to hardware related 1992 reasons." 1993 REFERENCE 1994 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1995 ::= { capwapBaseWtpEventsStatsEntry 5 } 1997 capwapBaseWtpEventsStatsOtherFailureCount OBJECT-TYPE 1998 SYNTAX Counter32 1999 MAX-ACCESS read-only 2000 STATUS current 2001 DESCRIPTION 2002 "Represents the number of times that a CAPWAP protocol 2003 connection with an AC has failed due to known reasons, other 2004 than AC initiated, link, software or hardware failure." 2005 REFERENCE 2006 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 2007 ::= { capwapBaseWtpEventsStatsEntry 6 } 2009 capwapBaseWtpEventsStatsUnknownFailureCount OBJECT-TYPE 2010 SYNTAX Counter32 2011 MAX-ACCESS read-only 2012 STATUS current 2013 DESCRIPTION 2014 "Represents the number of times that a CAPWAP protocol 2015 connection with an AC has failed for unknown reasons." 2016 REFERENCE 2017 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 2018 ::= { capwapBaseWtpEventsStatsEntry 7 } 2020 capwapBaseWtpEventsStatsLastFailureType OBJECT-TYPE 2021 SYNTAX INTEGER { 2022 notSupport(0), 2023 acInit(1), 2024 linkFailure(2), 2025 swFailure(3), 2026 hwFailure(4), 2027 otherFailure(5), 2028 unknown(255) 2029 } 2030 MAX-ACCESS read-only 2031 STATUS current 2032 DESCRIPTION 2033 "Represents the failure type of the most recent WTP failure. 2034 The following enumerated values are supported: 2035 notSupport(0) - Not Supported 2036 acInit(1) - AC Initiated 2037 linkFailure(2) - Link Failure 2038 swFailure(3) - Software Failure 2039 hwFailure(4) - Hardware Failure 2040 otherFailure(5) - Other Failure 2041 unknown(255) - Unknown (e.g., WTP doesn't keep track 2042 of info)" 2043 REFERENCE 2044 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 2045 ::= { capwapBaseWtpEventsStatsEntry 8 } 2047 -- End of capwapBaseWtpEventsStatsTable table 2049 -- capwapBaseRadioEventsStatsTable table 2051 capwapBaseRadioEventsStatsTable OBJECT-TYPE 2052 SYNTAX SEQUENCE OF CapwapBaseRadioEventsStatsEntry 2053 MAX-ACCESS not-accessible 2054 STATUS current 2055 DESCRIPTION 2056 "A table of objects that display statistics on radios behavior, 2057 and reasons why the WTP radio has been reset." 2058 REFERENCE 2059 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 2060 ::= { capwapBaseWtps 6 } 2062 capwapBaseRadioEventsStatsEntry OBJECT-TYPE 2063 SYNTAX CapwapBaseRadioEventsStatsEntry 2064 MAX-ACCESS not-accessible 2065 STATUS current 2066 DESCRIPTION 2067 "A set of objects that display the statistic data of 2068 events happened on a specific radio of a WTP." 2069 INDEX { capwapBaseWtpCurrId, capwapBaseWirelessBindingRadioId } 2070 ::= { capwapBaseRadioEventsStatsTable 1 } 2072 CapwapBaseRadioEventsStatsEntry ::= SEQUENCE { 2073 capwapBaseRadioEventsStatsResetCount Counter32, 2074 capwapBaseRadioEventsStatsSwFailCount Counter32, 2075 capwapBaseRadioEventsStatsHwFailCount Counter32, 2076 capwapBaseRadioEventsStatsOtherFailCount Counter32, 2077 capwapBaseRadioEventsStatsUnknownFailCount Counter32, 2078 capwapBaseRadioEventsStatsConfigUpdateCount Counter32, 2079 capwapBaseRadioEventsStatsChannelChangeCount Counter32, 2080 capwapBaseRadioEventsStatsBandChangeCount Counter32, 2081 capwapBaseRadioEventsStatsCurrentNoiseFloor Integer32, 2082 capwapBaseRadioEventsStatsDecryptErrorCount Counter32, 2083 capwapBaseRadioEventsStatsLastFailType INTEGER 2084 } 2086 capwapBaseRadioEventsStatsResetCount OBJECT-TYPE 2087 SYNTAX Counter32 2088 MAX-ACCESS read-only 2089 STATUS current 2090 DESCRIPTION 2091 "Represents the number of times that that the radio has been 2092 reset." 2093 REFERENCE 2094 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 2095 ::= { capwapBaseRadioEventsStatsEntry 1 } 2097 capwapBaseRadioEventsStatsSwFailCount OBJECT-TYPE 2098 SYNTAX Counter32 2099 MAX-ACCESS read-only 2100 STATUS current 2101 DESCRIPTION 2102 "Represents the number of times that the radio has failed due 2103 to software related reasons." 2104 REFERENCE 2105 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 2106 ::= { capwapBaseRadioEventsStatsEntry 2 } 2108 capwapBaseRadioEventsStatsHwFailCount OBJECT-TYPE 2109 SYNTAX Counter32 2110 MAX-ACCESS read-only 2111 STATUS current 2112 DESCRIPTION 2113 "Represents the number of times that the radio has failed due 2114 to hardware related reasons." 2115 REFERENCE 2116 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 2117 ::= { capwapBaseRadioEventsStatsEntry 3 } 2119 capwapBaseRadioEventsStatsOtherFailCount OBJECT-TYPE 2120 SYNTAX Counter32 2121 MAX-ACCESS read-only 2122 STATUS current 2123 DESCRIPTION 2124 "Represents the number of times that the radio has failed due to 2125 known reasons, other than software or hardware failure." 2126 REFERENCE 2127 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 2128 ::= { capwapBaseRadioEventsStatsEntry 4 } 2130 capwapBaseRadioEventsStatsUnknownFailCount OBJECT-TYPE 2131 SYNTAX Counter32 2132 MAX-ACCESS read-only 2133 STATUS current 2134 DESCRIPTION 2135 "Represents the number of times that the radio has failed for 2136 unknown reasons." 2137 REFERENCE 2138 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 2139 ::= { capwapBaseRadioEventsStatsEntry 5 } 2141 capwapBaseRadioEventsStatsConfigUpdateCount OBJECT-TYPE 2142 SYNTAX Counter32 2143 MAX-ACCESS read-only 2144 STATUS current 2145 DESCRIPTION 2146 "Represents the number of times that the radio configuration has 2147 been updated." 2148 REFERENCE 2149 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 2150 ::= { capwapBaseRadioEventsStatsEntry 6 } 2152 capwapBaseRadioEventsStatsChannelChangeCount OBJECT-TYPE 2153 SYNTAX Counter32 2154 MAX-ACCESS read-only 2155 STATUS current 2156 DESCRIPTION 2157 "Represents the number of times that the radio channel has 2158 been changed." 2159 REFERENCE 2160 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 2161 ::= { capwapBaseRadioEventsStatsEntry 7 } 2163 capwapBaseRadioEventsStatsBandChangeCount OBJECT-TYPE 2164 SYNTAX Counter32 2165 MAX-ACCESS read-only 2166 STATUS current 2167 DESCRIPTION 2168 "Represents the number of times that the radio has changed 2169 frequency bands." 2170 REFERENCE 2171 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 2172 ::= { capwapBaseRadioEventsStatsEntry 8 } 2174 capwapBaseRadioEventsStatsCurrentNoiseFloor OBJECT-TYPE 2175 SYNTAX Integer32 2176 UNITS "dBm" 2177 MAX-ACCESS read-only 2178 STATUS current 2179 DESCRIPTION 2180 "Represents the noise floor of the radio receiver in units of 2181 dBm." 2182 REFERENCE 2183 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 2184 ::= { capwapBaseRadioEventsStatsEntry 9 } 2186 capwapBaseRadioEventsStatsDecryptErrorCount OBJECT-TYPE 2187 SYNTAX Counter32 2188 MAX-ACCESS read-only 2189 STATUS current 2190 DESCRIPTION 2191 "Represents the number of decryption errors that occurred on the 2192 WTP. Note that this field is only valid in cases where the WTP 2193 provides encryption/decryption services." 2194 REFERENCE 2195 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 2196 ::= { capwapBaseRadioEventsStatsEntry 10 } 2198 capwapBaseRadioEventsStatsLastFailType OBJECT-TYPE 2199 SYNTAX INTEGER { 2200 notSupport(0), 2201 swFailure(1), 2202 hwFailure(2), 2203 otherFailure(3), 2204 unknown(255) 2205 } 2207 MAX-ACCESS read-only 2208 STATUS current 2209 DESCRIPTION 2210 "Represents the failure type of the most recent radio failure. 2211 The following enumerated values are supported: 2212 notSupport(0) - Not Supported 2213 swFailure(1) - Software Failure 2214 hwFailure(2) - Hardware Failure 2215 otherFailure(3) - Other Failure 2216 unknown(255) - Unknown" 2217 REFERENCE 2218 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 2219 ::= { capwapBaseRadioEventsStatsEntry 11 } 2221 -- End of capwapBaseRadioEventsStatsTable table 2222 -- End of WTP Objects Group 2224 -- CAPWAP Base Parameters Group 2226 capwapBaseParameters OBJECT IDENTIFIER 2227 ::= { capwapBaseObjects 3 } 2229 capwapBaseAcMaxRetransmit OBJECT-TYPE 2230 SYNTAX Unsigned32 2231 MAX-ACCESS read-write 2232 STATUS current 2233 DESCRIPTION 2234 "Represent the maximum number of retransmission for a given 2235 CAPWAP packet before the link layer considers the peer dead. 2236 The value of the object is persistent at restart/reboot." 2237 REFERENCE 2238 "Section 4.8.7. of CAPWAP Protocol Specification, RFC xxx." 2239 DEFVAL { 5 } 2240 ::= { capwapBaseParameters 1 } 2242 capwapBaseAcChangeStatePendingTimer OBJECT-TYPE 2243 SYNTAX Unsigned32 2244 UNITS "second" 2245 MAX-ACCESS read-write 2246 STATUS current 2247 DESCRIPTION 2248 "Represents the maximum time, in seconds, the AC will wait 2249 for the Change State Event Request from the WTP after having 2250 transmitted a successful Configuration Status Response 2251 message. 2252 The value of the object is persistent at restart/reboot." 2253 REFERENCE 2254 "Section 4.7.1. of CAPWAP Protocol Specification, RFC xxx." 2255 DEFVAL { 25 } 2256 ::= { capwapBaseParameters 2 } 2258 capwapBaseAcDataCheckTimer OBJECT-TYPE 2259 SYNTAX Unsigned32 2260 UNITS "second" 2261 MAX-ACCESS read-write 2262 STATUS current 2263 DESCRIPTION 2264 "Represents The number of seconds the AC will wait for 2265 the Data Channel Keep Alive, which is required by the 2266 CAPWAP state machine's Data Check state. 2267 The AC resets the state machine if this timer expires 2268 prior to transitioning to the next state. 2269 The value of the object is persistent at restart/reboot." 2270 REFERENCE 2271 "Section 4.7.4. of CAPWAP Protocol Specification, RFC xxx." 2272 DEFVAL { 30 } 2273 ::= { capwapBaseParameters 3 } 2275 capwapBaseAcDTLSSessionDeleteTimer OBJECT-TYPE 2276 SYNTAX Unsigned32 2277 UNITS "second" 2278 MAX-ACCESS read-write 2279 STATUS current 2280 DESCRIPTION 2281 "Represents the minimum time, in seconds, an AC MUST wait 2282 for DTLS session deletion. 2283 The value of the object is persistent at restart/reboot." 2284 REFERENCE 2285 "Section 4.7.6. of CAPWAP Protocol Specification, RFC xxx." 2286 DEFVAL { 5 } 2287 ::= { capwapBaseParameters 4 } 2289 capwapBaseAcEchoInterval OBJECT-TYPE 2290 SYNTAX Unsigned32 2291 UNITS "second" 2292 MAX-ACCESS read-write 2293 STATUS current 2294 DESCRIPTION 2295 "Represents the minimum time, in seconds, between sending Echo 2296 Request messages to the AC with which the WTP has joined. 2297 The value of the object is persistent at restart/reboot." 2298 REFERENCE 2299 "Section 4.7.7. of CAPWAP Protocol Specification, RFC xxx." 2300 DEFVAL { 30 } 2301 ::= { capwapBaseParameters 5 } 2303 capwapBaseAcRetransmitInterval OBJECT-TYPE 2304 SYNTAX Unsigned32 2305 UNITS "second" 2306 MAX-ACCESS read-write 2307 STATUS current 2308 DESCRIPTION 2309 "Represents the minimum time, in seconds, in which a 2310 non-acknowledged CAPWAP packet will be retransmitted. 2311 The value of the object is persistent at restart/reboot." 2312 REFERENCE 2313 "Section 4.7.12. of CAPWAP Protocol Specification, RFC xxx." 2314 DEFVAL { 3 } 2315 ::= { capwapBaseParameters 6 } 2317 capwapBaseAcSilentInterval OBJECT-TYPE 2318 SYNTAX Unsigned32 2319 UNITS "second" 2320 MAX-ACCESS read-write 2321 STATUS current 2322 DESCRIPTION 2323 "Represents the minimum time, in seconds, during which the AC 2324 SHOULD ignore all CAPWAP and DTLS packets received from the 2325 WTP that is in the Sulking state. 2326 The value of the object is persistent at restart/reboot." 2327 REFERENCE 2328 "Section 4.7.13. of CAPWAP Protocol Specification, RFC xxx." 2329 DEFVAL { 30 } 2330 ::= { capwapBaseParameters 7 } 2332 capwapBaseAcWaitDTLSTimer OBJECT-TYPE 2333 SYNTAX Unsigned32 (30..4294967295) 2334 UNITS "second" 2335 MAX-ACCESS read-write 2336 STATUS current 2337 DESCRIPTION 2338 "Represents the maximum time, in seconds, an AC MUST wait 2339 without having received a DTLS Handshake message from an AC. 2340 This timer MUST be greater than 30 seconds. 2341 The value of the object is persistent at restart/reboot." 2342 REFERENCE 2343 "Section 4.7.15. of CAPWAP Protocol Specification, RFC xxx." 2344 DEFVAL { 60 } 2345 ::= { capwapBaseParameters 8 } 2347 capwapBaseAcWaitJoinTimer OBJECT-TYPE 2348 SYNTAX Unsigned32 (20..4294967295) 2349 UNITS "second" 2350 MAX-ACCESS read-write 2351 STATUS current 2352 DESCRIPTION 2353 "Represents the maximum time, in seconds, an AC will wait after 2354 the DTLS session has been established until it receives the 2355 Join Request from the WTP. This timer MUST be greater than 20 2356 seconds. 2357 The value of the object is persistent at restart/reboot." 2358 REFERENCE 2359 "Section 4.7.16. of CAPWAP Protocol Specification, RFC xxx." 2360 DEFVAL { 60 } 2361 ::= { capwapBaseParameters 9 } 2363 capwapBaseAcEcnSupport OBJECT-TYPE 2364 SYNTAX INTEGER { 2365 limited(0), 2366 fullAndLimited(1) 2367 } 2368 MAX-ACCESS read-write 2369 STATUS current 2370 DESCRIPTION 2371 "Represents the support for the Explicit Congestion Notification 2372 (ECN) bits, as defined in [RFC3168]. 2373 The value of the object is persistent at restart/reboot." 2374 REFERENCE 2375 "Section 4.7.25. of CAPWAP Protocol Specification, RFC xxx." 2376 ::= { capwapBaseParameters 10 } 2378 -- End of CAPWAP Base Parameters Group 2380 -- CAPWAP Statistics Group 2382 capwapBaseStats OBJECT IDENTIFIER 2383 ::= { capwapBaseObjects 4 } 2385 capwapBaseFailedDTLSAuthFailCount OBJECT-TYPE 2386 SYNTAX Counter32 2387 MAX-ACCESS read-only 2388 STATUS current 2389 DESCRIPTION 2390 "Represents the number of failed DTLS session 2391 establishment attempts due to authentication failures." 2392 REFERENCE 2393 "Section 4.8.3. of CAPWAP Protocol Specification, RFC xxx." 2394 ::= { capwapBaseStats 1 } 2396 capwapBaseFailedDTLSSessionCount OBJECT-TYPE 2397 SYNTAX Counter32 2398 MAX-ACCESS read-only 2399 STATUS current 2400 DESCRIPTION 2401 "Represents the number of failed DTLS session 2402 establishment attempts." 2403 REFERENCE 2404 "Section 4.8.4. of CAPWAP Protocol Specification, RFC xxx." 2405 ::= { capwapBaseStats 2 } 2407 -- Notifications 2409 capwapBaseChannelUp NOTIFICATION-TYPE 2410 OBJECTS { 2411 capwapBaseNtfWtpId, 2412 capwapBaseNtfChannelType, 2413 capwapBaseNtfAuthenMethod 2414 } 2415 STATUS current 2416 DESCRIPTION 2417 "This notification is sent by AC when a CAPWAP channel 2418 established. The notification is separated for data or control 2419 channel." 2420 ::= { capwapBaseNotifications 1 } 2422 capwapBaseChannelDown NOTIFICATION-TYPE 2423 OBJECTS { 2424 capwapBaseNtfWtpId, 2425 capwapBaseNtfChannelType, 2426 capwapBaseNtfChannelDownReason 2427 } 2428 STATUS current 2429 DESCRIPTION 2430 "This notification is sent by AC when CAPWAP channel becomes 2431 down. The notification is separated for data or control 2432 channel." 2433 ::= { capwapBaseNotifications 2 } 2435 capwapBaseDecryptErrorReport NOTIFICATION-TYPE 2436 OBJECTS { 2437 capwapBaseNtfWtpId, 2438 capwapBaseNtfRadioId, 2439 capwapBaseNtfStationIdList 2440 } 2441 STATUS current 2442 DESCRIPTION 2443 "This notification is generated when a WTP that has occurred 2444 decryption error since the last report." 2445 REFERENCE 2446 "Section 4.6.17. of CAPWAP Protocol Specification, RFC xxx." 2447 ::= { capwapBaseNotifications 3 } 2449 capwapBaseJoinFailure NOTIFICATION-TYPE 2450 OBJECTS { 2451 capwapBaseNtfWtpId, 2452 capwapBaseNtfJoinFailureReason 2453 } 2454 STATUS current 2455 DESCRIPTION 2456 "This notification is generated when a WTP fails to join." 2457 REFERENCE 2458 "Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx." 2459 ::= { capwapBaseNotifications 4 } 2461 capwapBaseImageUpgradeFailure NOTIFICATION-TYPE 2462 OBJECTS { 2463 capwapBaseNtfWtpId, 2464 capwapBaseNtfImageFailureReason 2465 } 2466 STATUS current 2467 DESCRIPTION 2468 "This notification is generated when a WTP fails to update 2469 firmware image." 2470 REFERENCE 2471 "Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx." 2472 ::= { capwapBaseNotifications 5 } 2474 capwapBaseConfigMsgError NOTIFICATION-TYPE 2475 OBJECTS { 2476 capwapBaseNtfWtpId, 2477 capwapBaseNtfConfigMsgErrorType, 2478 capwapBaseNtfMsgErrorElements 2479 } 2480 STATUS current 2481 DESCRIPTION 2482 "This notification is generated when a WTP received message 2483 elements in the configuration management messages which it was 2484 unable to apply locally." 2485 REFERENCE 2486 "Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx." 2487 ::= { capwapBaseNotifications 6 } 2489 capwapBaseRadioOperableStatus NOTIFICATION-TYPE 2490 OBJECTS { 2491 capwapBaseNtfWtpId, 2492 capwapBaseNtfRadioId, 2493 capwapBaseNtfRadioOperStatusFlag, 2494 capwapBaseNtfRadioStatusCause 2495 } 2496 STATUS current 2497 DESCRIPTION 2498 "The notification is generated when a radio's operational state 2499 is changed." 2500 REFERENCE 2501 "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." 2502 ::= { capwapBaseNotifications 7 } 2504 capwapBaseAuthenticationFailure NOTIFICATION-TYPE 2505 OBJECTS { 2506 capwapBaseNtfWtpId, 2507 capwapBaseNtfChannelType, 2508 capwapBaseNtfAuthenMethod, 2509 capwapBaseNtfAuthenFailureReason 2510 } 2511 STATUS current 2512 DESCRIPTION 2513 "The notification will notify the authentication failure event, 2514 and provides the reason for it." 2515 ::= { capwapBaseNotifications 8 } 2517 -- Objects used only in notifications 2519 -- for notifications 2520 capwapBaseNotifyVarObjects OBJECT IDENTIFIER 2521 ::= { capwapBaseObjects 5 } 2523 capwapBaseNtfWtpId OBJECT-TYPE 2524 SYNTAX CapwapBaseWtpIdTC 2525 MAX-ACCESS accessible-for-notify 2526 STATUS current 2527 DESCRIPTION 2528 "Represents the unique identifier of a WTP." 2529 ::= { capwapBaseNotifyVarObjects 1 } 2531 capwapBaseNtfRadioId OBJECT-TYPE 2532 SYNTAX CapwapBaseRadioIdTC 2533 MAX-ACCESS accessible-for-notify 2534 STATUS current 2535 DESCRIPTION 2536 "Represents the identifier of a PHY radio on a WTP, and only 2537 requires unique on a WTP. 2538 For example, WTP A and WTP B will use same value of 2539 capwapBaseNtfRadioId for their first radio." 2540 REFERENCE 2541 "Section 4.3. of CAPWAP Protocol Specification, RFC xxx." 2542 ::= { capwapBaseNotifyVarObjects 2 } 2544 capwapBaseNtfChannelType OBJECT-TYPE 2545 SYNTAX CapwapBaseChannelTypeTC 2546 MAX-ACCESS accessible-for-notify 2547 STATUS current 2548 DESCRIPTION 2549 "Represents the channel type for CAPWAP protocol." 2550 ::= { capwapBaseNotifyVarObjects 3 } 2552 capwapBaseNtfAuthenMethod OBJECT-TYPE 2553 SYNTAX CapwapBaseAuthenMethodTC 2554 MAX-ACCESS accessible-for-notify 2555 STATUS current 2556 DESCRIPTION 2557 "Represents authentication method for Channel." 2558 ::= { capwapBaseNotifyVarObjects 4 } 2560 capwapBaseNtfChannelDownReason OBJECT-TYPE 2561 SYNTAX INTEGER { 2562 timeout(1), 2563 rekeyfailure(2), 2564 acRebootWtp(3), 2565 dtlsError(4), 2566 maxRetransmit(5) 2567 } 2568 MAX-ACCESS accessible-for-notify 2569 STATUS current 2570 DESCRIPTION 2571 "Represents the reason for Channel down. 2572 The following enumerated values are supported: 2573 timeout(1) - The keep alive is timeout 2574 rekeyfailure(2) - Rekey process is failed, channel will be 2575 broken 2576 acRebootWtp(3) - AC reboot WTP 2577 dtlsError(4) - DTLS notifications: DTLSAborted, 2578 DTLSReassemblyFailure, DTLSPeerDisconnect, 2579 or frequent DTLSDecapFailure 2580 maxRetransmit(5) - The underlying reliable transport's 2581 RetransmitCount counter has reached the 2582 MaxRetransmit variable" 2583 ::= { capwapBaseNotifyVarObjects 5 } 2585 capwapBaseNtfStationIdList OBJECT-TYPE 2586 SYNTAX OCTET STRING 2587 MAX-ACCESS accessible-for-notify 2588 STATUS current 2589 DESCRIPTION 2590 "Represents the list of station id which use semicolons to 2591 separate each station id." 2592 REFERENCE 2593 "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." 2594 ::= { capwapBaseNotifyVarObjects 6 } 2596 capwapBaseNtfAuthenFailureReason OBJECT-TYPE 2597 SYNTAX INTEGER { 2598 keyMismatch(1), 2599 invalidCA(2), 2600 micError(3), 2601 timeout(4), 2602 unknown(8) 2603 } 2604 MAX-ACCESS accessible-for-notify 2605 STATUS current 2606 DESCRIPTION 2607 "Represents reason for WTP authorization failure. 2608 The following enumerated values are supported: 2609 keyMismatch(1) - WTP's and AC's key is not matched 2610 invalidCA(2) - ca is not valid 2611 micError(3) - detect MIC error 2612 timeout(4) - WaitDTLS Timer is timeout 2613 unknown(8) - Unknown reason" 2614 REFERENCE 2615 "Section 2.3.1. of CAPWAP Protocol Specification, RFC xxx." 2616 ::= { capwapBaseNotifyVarObjects 7 } 2618 capwapBaseNtfRadioOperStatusFlag OBJECT-TYPE 2619 SYNTAX INTEGER { 2620 operable(0), 2621 inoperable(1) 2622 } 2623 MAX-ACCESS accessible-for-notify 2624 STATUS current 2625 DESCRIPTION 2626 "Represents the operation status of a radio. 2627 The following enumerated values are supported: 2628 operable(0) - To indicate radio is operable 2629 inoperable(1) - To indicate radio is inoperable, and 2630 capwapBaseNtfRadioStatusCause object will 2631 give reason in details" 2632 REFERENCE 2633 "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." 2634 ::= { capwapBaseNotifyVarObjects 8 } 2636 capwapBaseNtfRadioStatusCause OBJECT-TYPE 2637 SYNTAX INTEGER { 2638 normal(0), 2639 hwError(1), 2640 swError(2), 2641 adminSet(3) 2642 } 2643 MAX-ACCESS accessible-for-notify 2644 STATUS current 2645 DESCRIPTION 2646 "Represents the reason the radio is out of service. 2647 The following enumerated values are supported: 2648 normal(0) - Normal Status 2649 hwError(1) - Radio Failure 2650 swError(2) - Software Failure 2651 adminSet(3) - Administratively Set" 2652 REFERENCE 2653 "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." 2654 ::= { capwapBaseNotifyVarObjects 9 } 2656 capwapBaseNtfJoinFailureReason OBJECT-TYPE 2657 SYNTAX INTEGER { 2658 unspecified(1), 2659 resDepletion(2), 2660 unknownSource(3), 2661 incorrectData(4), 2662 sessionIdInUse(5), 2663 notSupportHw(6), 2664 notSupportBinding(7) 2665 } 2666 MAX-ACCESS accessible-for-notify 2667 STATUS current 2668 DESCRIPTION 2669 "Represents the reason of join failure. 2670 The following enumerated values are supported: 2671 unspecified(1) - unspecified failure reason 2672 resDepletion(2) - Resource Depletion 2673 unknownSource(3) - Unknown Source 2674 incorrectData(4) - Incorrect Data 2675 sessionIdInUse(5) - Session ID already in use 2676 notSupportHw(6) - WTP Hardware not supported 2677 notSupportBinding(7) - Binding Not Supported" 2678 REFERENCE 2679 "Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx." 2680 ::= { capwapBaseNotifyVarObjects 10 } 2682 capwapBaseNtfImageFailureReason OBJECT-TYPE 2683 SYNTAX INTEGER { 2684 invalidChecksum(1), 2685 invalidLength(2), 2686 other(3), 2687 inStorage(4) 2688 } 2689 MAX-ACCESS accessible-for-notify 2690 STATUS current 2691 DESCRIPTION 2692 "Represents the reason of image failure. 2693 The following enumerated values are supported: 2694 invalidChecksum(1) - Invalid Checksum 2695 invalidLength(2) - Invalid Data Length 2696 other(3) - Other Error 2697 inStorage(4) - Image Already Present" 2698 REFERENCE 2699 "Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx." 2700 ::= { capwapBaseNotifyVarObjects 11 } 2702 capwapBaseNtfConfigMsgErrorType OBJECT-TYPE 2703 SYNTAX INTEGER { 2704 unknownElement(1), 2705 unsupportedElement(2), 2706 unknownValue(3), 2707 unsupportedValue(4) 2708 } 2709 MAX-ACCESS accessible-for-notify 2710 STATUS current 2711 DESCRIPTION 2712 "Represents the type of configuration message error. 2713 The following enumerated values are supported: 2714 unknownElement(1) - Unknown Message Element 2715 unsupportedElement(2) - Unsupported Message Element 2716 unknownValue(3) - Unknown Message Element Value 2717 unsupportedValue(4) - Unsupported Message Element Value" 2718 REFERENCE 2719 "Section 4.6.36. of CAPWAP Protocol Specification, RFC xxx." 2720 ::= { capwapBaseNotifyVarObjects 12 } 2722 capwapBaseNtfMsgErrorElements OBJECT-TYPE 2723 SYNTAX SnmpAdminString 2724 MAX-ACCESS accessible-for-notify 2725 STATUS current 2726 DESCRIPTION 2727 "Represents the message elements sent by the AC in the 2728 Configuration Status Response message that caused the error." 2729 REFERENCE 2730 "Section 4.6.36. of CAPWAP Protocol Specification, RFC xxx." 2731 ::= { capwapBaseNotifyVarObjects 13 } 2733 -- Module compliance 2735 capwapBaseCompliances OBJECT IDENTIFIER 2736 ::= { capwapBaseConformance 1 } 2738 capwapBaseGroups OBJECT IDENTIFIER 2739 ::= { capwapBaseConformance 2 } 2741 capwapBaseCompliance MODULE-COMPLIANCE 2742 STATUS current 2743 DESCRIPTION 2744 "Describes the requirements for conformance to the 2745 CAPWAP-BASE-MIB module." 2747 MODULE -- this module 2748 MANDATORY-GROUPS { 2749 capwapBaseAcNodeGroup, 2750 capwapBaseWtpStateGroup, 2751 capwapBaseWtpsGroup, 2752 capwapBaseRadiosGroup, 2753 capwapBaseStationsGroup 2754 } 2756 GROUP capwapBaseAcNodeGroup2 2757 DESCRIPTION 2758 "The capwapBaseAcNodeGroup2 group is optional." 2760 GROUP capwapBaseAcNameListGroup 2761 DESCRIPTION 2762 "The capwapBaseAcNameListGroup group is optional." 2764 GROUP capwapBaseMacAclsGroup 2765 DESCRIPTION 2766 "The capwapBaseMacAclsGroup group is optional." 2768 GROUP capwapBaseWtpsGroup2 2769 DESCRIPTION 2770 "The capwapBaseWtpsGroup2 group is optional." 2772 GROUP capwapBaseWtpEventsStatsGroup 2773 DESCRIPTION 2774 "The capwapBaseWtpEventsStatsGroup group is optional." 2776 GROUP capwapBaseRadioEventsStatsGroup 2777 DESCRIPTION 2778 "The capwapBaseRadioEventsStatsGroup group is optional." 2780 GROUP capwapBaseParametersGroup 2781 DESCRIPTION 2782 "The capwapBaseParametersGroup group is optional." 2784 GROUP capwapBaseStatsGroup 2785 DESCRIPTION 2786 "The capwapBaseStatsGroup group is optional." 2788 GROUP capwapBaseNotificationGroup 2789 DESCRIPTION 2790 "The group capwapBaseNotificationGroup is optional." 2792 GROUP capwapBaseNotifyVarGroup 2793 DESCRIPTION 2794 "The capwapBaseNotifyVarGroup group is optional. 2795 If capwapBaseNotificationGroup is supported, 2796 this group must be implemented." 2797 ::= { capwapBaseCompliances 1 } 2799 capwapBaseAcNodeGroup OBJECT-GROUP 2800 OBJECTS { 2801 capwapBaseWtpSessions, 2802 capwapBaseWtpSessionsLimit, 2803 capwapBaseStationSessions, 2804 capwapBaseStationSessionsLimit 2805 } 2806 STATUS current 2807 DESCRIPTION 2808 "The collection of objects which are used to represent 2809 basic properties for AC from CAPWAP protocol perspective." 2810 ::= { capwapBaseGroups 1 } 2812 capwapBaseAcNodeGroup2 OBJECT-GROUP 2813 OBJECTS { 2814 capwapBaseDataChannelDTLSPolicyOptions, 2815 capwapBaseDataChannelDTLSPolicyConfig, 2816 capwapBaseControlChannelAuthenOptions, 2817 capwapBaseControlChannelAuthenConfig 2818 } 2819 STATUS current 2820 DESCRIPTION 2821 "The collection of objects which are used to represent 2822 other properties such as security for AC from 2823 CAPWAP protocol perspective." 2824 ::= { capwapBaseGroups 2 } 2826 capwapBaseAcNameListGroup OBJECT-GROUP 2827 OBJECTS { 2828 capwapBaseAcNameListName, 2829 capwapBaseAcNameListPriority, 2830 capwapBaseAcNameListRowStatus 2831 } 2832 STATUS current 2833 DESCRIPTION 2834 "The collection of objects which are used to configure 2835 AC name list." 2836 ::= { capwapBaseGroups 3 } 2838 capwapBaseMacAclsGroup OBJECT-GROUP 2839 OBJECTS { 2840 capwapBaseMacAclStationId, 2841 capwapBaseMacAclRowStatus 2842 } 2843 STATUS current 2844 DESCRIPTION 2845 "The collection of objects which are used to configure 2846 stations ACL." 2847 ::= { capwapBaseGroups 4 } 2849 capwapBaseWtpStateGroup OBJECT-GROUP 2850 OBJECTS { 2851 capwapBaseWtpStateWtpIpAddressType, 2852 capwapBaseWtpStateWtpIpAddress, 2853 capwapBaseWtpStateWtpPhyAddress, 2854 capwapBaseWtpState 2855 } 2856 STATUS current 2857 DESCRIPTION 2858 "The collection of objects which are used to represent 2859 WTP state information." 2860 ::= { capwapBaseGroups 5 } 2862 capwapBaseWtpsGroup OBJECT-GROUP 2863 OBJECTS { 2864 capwapBaseWtpName, 2865 capwapBaseWtpLocation, 2866 capwapBaseWtpBaseMacAddress, 2867 capwapBaseWtpTunnelModeOptions, 2868 capwapBaseWtpMacTypeOptions, 2869 capwapBaseWtpRadiosInUseNum, 2870 capwapBaseWtpRadioNumLimit, 2871 capwapBaseWtpEcnSupport 2872 } 2873 STATUS current 2874 DESCRIPTION 2875 "The collection of objects which are used to represent 2876 configuration and properties information for WTP 2877 in running state." 2878 ::= { capwapBaseGroups 6 } 2880 capwapBaseWtpsGroup2 OBJECT-GROUP 2881 OBJECTS { 2882 capwapBaseWtpPhyIndex, 2883 capwapBaseWtpDiscoveryType, 2884 capwapBaseWtpStaticIpEnable, 2885 capwapBaseWtpStaticIpType, 2886 capwapBaseWtpStaticIp, 2887 capwapBaseWtpNetmask, 2888 capwapBaseWtpGateway, 2889 capwapBaseWtpFallbackEnable, 2890 capwapBaseWtpRetransmitCount, 2891 capwapBaseWtpMaxDiscoveries, 2892 capwapBaseWtpMaxFailedDTLSSessionRetry, 2893 capwapBaseWtpMaxRetransmit, 2894 capwapBaseWtpDataChannelKeepAliveTimer, 2895 capwapBaseWtpDataChannelDeadInterval, 2896 capwapBaseWtpDiscoveryInterval, 2897 capwapBaseWtpDTLSSessionDeleteTimer, 2898 capwapBaseWtpEchoInterval, 2899 capwapBaseWtpIdleTimeout, 2900 capwapBaseWtpImageDataStartTimer, 2901 capwapBaseWtpMaxDiscoveryInterval, 2902 capwapBaseWtpReportInterval, 2903 capwapBaseWtpRetransmitInterval, 2904 capwapBaseWtpSilentInterval, 2905 capwapBaseWtpStatisticsTimer, 2906 capwapBaseWtpWaitDTLSTimer 2907 } 2908 STATUS current 2909 DESCRIPTION 2910 "The collection of objects which are used to represent 2911 configuration and properties information for WTP 2912 in running state." 2913 ::= { capwapBaseGroups 7 } 2915 capwapBaseRadiosGroup OBJECT-GROUP 2916 OBJECTS { 2917 capwapBaseWirelessBindingVirtualRadioIfIndex, 2918 capwapBaseWirelessBindingType 2919 } 2920 STATUS current 2921 DESCRIPTION 2922 "The collection of objects which are used to represent 2923 wireless binding type, the mapping relationship between 2924 'WLAN Virtual Radio Interface' and PHY radio." 2926 ::= { capwapBaseGroups 8 } 2928 capwapBaseStationsGroup OBJECT-GROUP 2929 OBJECTS { 2930 capwapBaseStationAddedTime, 2931 capwapBaseStationVlanName 2932 } 2933 STATUS current 2934 DESCRIPTION 2935 "The collection of objects which are used to represent 2936 stations' basic property." 2937 ::= { capwapBaseGroups 9 } 2939 capwapBaseWtpEventsStatsGroup OBJECT-GROUP 2940 OBJECTS { 2941 capwapBaseWtpEventsStatsRebootCount, 2942 capwapBaseWtpEventsStatsInitCount, 2943 capwapBaseWtpEventsStatsLinkFailureCount, 2944 capwapBaseWtpEventsStatsSwFailureCount, 2945 capwapBaseWtpEventsStatsHwFailureCount, 2946 capwapBaseWtpEventsStatsOtherFailureCount, 2947 capwapBaseWtpEventsStatsUnknownFailureCount, 2948 capwapBaseWtpEventsStatsLastFailureType 2949 } 2950 STATUS current 2951 DESCRIPTION 2952 "The collection of objects which are used for collecting 2953 WTP reboot count, link failure count, hardware failure 2954 count and so on." 2955 ::= { capwapBaseGroups 10 } 2957 capwapBaseRadioEventsStatsGroup OBJECT-GROUP 2958 OBJECTS { 2959 capwapBaseRadioEventsStatsResetCount, 2960 capwapBaseRadioEventsStatsSwFailCount, 2961 capwapBaseRadioEventsStatsHwFailCount, 2962 capwapBaseRadioEventsStatsOtherFailCount, 2963 capwapBaseRadioEventsStatsUnknownFailCount, 2964 capwapBaseRadioEventsStatsConfigUpdateCount, 2965 capwapBaseRadioEventsStatsChannelChangeCount, 2966 capwapBaseRadioEventsStatsBandChangeCount, 2967 capwapBaseRadioEventsStatsCurrentNoiseFloor, 2968 capwapBaseRadioEventsStatsDecryptErrorCount, 2969 capwapBaseRadioEventsStatsLastFailType 2970 } 2971 STATUS current 2972 DESCRIPTION 2973 "The collection of objects which are used for collecting 2974 radio reset count, channel change count, hardware failure 2975 count and so on" 2976 ::= { capwapBaseGroups 11 } 2978 capwapBaseParametersGroup OBJECT-GROUP 2979 OBJECTS { 2980 capwapBaseAcMaxRetransmit, 2981 capwapBaseAcChangeStatePendingTimer, 2982 capwapBaseAcDataCheckTimer, 2983 capwapBaseAcDTLSSessionDeleteTimer, 2984 capwapBaseAcEchoInterval, 2985 capwapBaseAcRetransmitInterval, 2986 capwapBaseAcSilentInterval, 2987 capwapBaseAcWaitDTLSTimer, 2988 capwapBaseAcWaitJoinTimer, 2989 capwapBaseAcEcnSupport 2990 } 2991 STATUS current 2992 DESCRIPTION 2993 "Objects used for CAPWAP protocol." 2994 ::= { capwapBaseGroups 12 } 2996 capwapBaseStatsGroup OBJECT-GROUP 2997 OBJECTS { 2998 capwapBaseFailedDTLSAuthFailCount, 2999 capwapBaseFailedDTLSSessionCount 3000 } 3001 STATUS current 3002 DESCRIPTION 3003 "Objects used for CAPWAP protocol." 3004 ::= { capwapBaseGroups 13 } 3006 capwapBaseNotificationGroup NOTIFICATION-GROUP 3007 NOTIFICATIONS { 3008 capwapBaseChannelUp, 3009 capwapBaseChannelDown, 3010 capwapBaseDecryptErrorReport, 3011 capwapBaseJoinFailure, 3012 capwapBaseImageUpgradeFailure, 3013 capwapBaseConfigMsgError, 3014 capwapBaseRadioOperableStatus, 3015 capwapBaseAuthenticationFailure 3016 } 3017 STATUS current 3018 DESCRIPTION 3019 "The Collection of notifications in this MIB module." 3020 ::= { capwapBaseGroups 14 } 3022 capwapBaseNotifyVarGroup OBJECT-GROUP 3023 OBJECTS { 3024 capwapBaseNtfWtpId, 3025 capwapBaseNtfRadioId, 3026 capwapBaseNtfChannelType, 3027 capwapBaseNtfAuthenMethod, 3028 capwapBaseNtfChannelDownReason, 3029 capwapBaseNtfStationIdList, 3030 capwapBaseNtfAuthenFailureReason, 3031 capwapBaseNtfRadioOperStatusFlag, 3032 capwapBaseNtfRadioStatusCause, 3033 capwapBaseNtfJoinFailureReason, 3034 capwapBaseNtfImageFailureReason, 3035 capwapBaseNtfConfigMsgErrorType, 3036 capwapBaseNtfMsgErrorElements 3037 } 3038 STATUS current 3039 DESCRIPTION 3040 "Objects used for notification." 3041 ::= { capwapBaseGroups 15 } 3043 END 3045 11. Security Considerations 3047 There are a number of management objects defined in this MIB module 3048 with a MAX-ACCESS clause of read-write and/or read-create. Such 3049 objects may be considered sensitive or vulnerable in some network 3050 environments. The support for SET operations in a non-secure 3051 environment without proper protection can have a negative effect on 3052 network operations. The followings are the tables and objects and 3053 their sensitivity/vulnerability: 3055 - Unauthorized changes to the capwapBaseWtpTable, writable objects 3056 under capwapBaseAcs group may disrupt allocation of resources in the 3057 network. For example, a WTP's static IP address could be changed by 3058 set capwapBaseWtpStaticIp object. 3060 - Unauthorized changes to writable objects under the capwapBaseAc 3061 group, it may disrupt allocation of resources in the network. For 3062 example, a invalid value for capwapBaseWtpSessionsLimit object will 3063 increase AC's traffic burden. Also, some objects such as 3064 capwapBaseDataChannelDTLSPolicyConfig may cause network unsafe. 3066 - Unauthorized changes to the capwapBaseMacAclTable, it may cause 3067 legal stations could not access network any more while illegal 3068 stations have chance to access network. 3070 - Unauthorized changes to writable objects under the 3071 capwapBaseParameters group, it may influence CAPWAP protocol 3072 behaviour and status. For example, the invalid value for 3073 capwapBaseAcDataCheckTimer may influence CAPWAP state machine. 3075 Some of the readable objects in this MIB module (i.e., objects with a 3076 MAX-ACCESS other than not-accessible) may be considered sensitive or 3077 vulnerable in some network environments. It is thus important to 3078 control even GET and/or NOTIFY access to these objects and possibly 3079 to even encrypt the values of these objects when sending them over 3080 the network via SNMP. The followings are the tables and objects and 3081 their sensitivity/vulnerability: 3083 - The capwapBaseDataChannelDTLSPolicyOptions and 3084 capwapBaseControlChannelAuthenOptions under the capwapBaseAc group 3085 exposes the current security option for CAPWAP data and control 3086 channel. 3088 - The capwapBaseWtpTable exposes WTP's important information like IP 3089 address, MAC type and so on. 3091 - The capwapBaseWtpEventsStatsTable exposes WTP's failure 3092 information. 3094 - The capwapBaseRadioEventsStatsTable exposes radio's failure 3095 information. 3097 SNMP versions prior to SNMPv3 did not include adequate security. 3098 Even if the network itself is secure (for example by using IPSec), 3099 even then, there is no control as to who on the secure network is 3100 allowed to access and GET/SET (read/change/create/delete) the objects 3101 in this MIB module. 3103 It is RECOMMENDED that implementers consider the security features as 3104 provided by the SNMPv3 framework (see [RFC3410], section 8), 3105 including full support for the SNMPv3 cryptographic mechanisms (for 3106 authentication and privacy). 3108 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3109 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3110 enable cryptographic security. It is then a customer/operator 3111 responsibility to ensure that the SNMP entity giving access to an 3112 instance of this MIB module is properly configured to give access to 3113 the objects only to those principals (users) that have legitimate 3114 rights to indeed GET or SET (change/create/delete) them. 3116 12. IANA Considerations 3118 12.1. IANA Considerations for CAPWAP-BASE-MIB module 3120 The MIB module in this document uses the following IANA-assigned 3121 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 3123 Descriptor OBJECT IDENTIFIER value 3124 ---------- ----------------------- 3126 capwapBaseMIB { mib-2 XXX } 3128 12.2. IANA Considerations for ifType 3130 Require IANA to assign a ifType for 'WTP Virtual Radio Interface' 3131 type. 3133 13. Contributors 3135 This MIB module is based on contributions from Long Gao. 3137 14. Acknowledgements 3139 The authors wish to thank David Harrington, Fei Fang, Yu Liu, Sachin 3140 Dutta, Ju Wang, Yujin Zhao, Haitao Zhang. 3142 15. References 3144 15.1. Normative References 3146 [RFC2119] Bradner, S., "Key words 3147 for use in RFCs to 3148 Indicate Requirement 3149 Levels", BCP 14, 3150 RFC 2119, March 1997. 3152 [RFC2578] McCloghrie, K., Ed., 3153 Perkins, D., Ed., and 3154 J. Schoenwaelder, Ed., 3155 "Structure of 3156 Management Information 3157 Version 2 (SMIv2)", 3158 STD 58, RFC 2578, 3159 April 1999. 3161 [RFC2579] McCloghrie, K., Ed., 3162 Perkins, D., Ed., and 3163 J. Schoenwaelder, Ed., 3164 "Textual Conventions 3165 for SMIv2", STD 58, 3166 RFC 2579, April 1999. 3168 [RFC2580] McCloghrie, K., 3169 Perkins, D., and J. 3170 Schoenwaelder, 3171 "Conformance Statements 3172 for SMIv2", STD 58, 3173 RFC 2580, April 1999. 3175 [RFC2863] McCloghrie, K. and F. 3176 Kastenholz, "The 3177 Interfaces Group MIB", 3178 RFC 2863, June 2000. 3180 [RFC3411] Harrington, D., 3181 Presuhn, R., and B. 3182 Wijnen, "An 3183 Architecture for 3184 Describing Simple 3185 Network Management 3186 Protocol (SNMP) 3187 Management Frameworks", 3188 STD 62, RFC 3411, 3189 December 2002. 3191 [RFC3418] Presuhn, R., 3192 "Management Information 3193 Base (MIB) for the 3194 Simple Network 3195 Management Protocol 3196 (SNMP)", STD 62, 3197 RFC 3418, 3198 December 2002. 3200 [RFC4001] Daniele, M., Haberman, 3201 B., Routhier, S., and 3202 J. Schoenwaelder, 3203 "Textual Conventions 3204 for Internet Network 3205 Addresses", RFC 4001, 3206 February 2005. 3208 [RFC4133] Bierman, A. and K. 3209 McCloghrie, "Entity MIB 3210 (Version 3)", RFC 4133, 3211 August 2005. 3213 [I-D.ietf-capwap-protocol-specification] Montemurro, M., 3214 Stanley, D., and P. 3215 Calhoun, "CAPWAP 3216 Protocol 3217 Specification", draft- 3218 ietf-capwap-protocol- 3219 specification-15 (work 3220 in progress), 3221 November 2008. 3223 15.2. Informative References 3225 [RFC3410] Case, J., Mundy, R., 3226 Partain, D., and B. 3227 Stewart, "Introduction 3228 and Applicability 3229 Statements for 3230 Internet-Standard 3231 Management Framework", 3232 RFC 3410, 3233 December 2002. 3235 [RFC4118] Yang, L., Zerfos, P., 3236 and E. Sadot, 3237 "Architecture Taxonomy 3238 for Control and 3239 Provisioning of 3240 Wireless Access Points 3241 (CAPWAP)", RFC 4118, 3242 June 2005. 3244 [RFC4347] Rescorla, E. and N. 3245 Modadugu, "Datagram 3246 Transport Layer 3247 Security", RFC 4347, 3248 April 2006. 3250 [IEEE.802-11.2007] "Information technology 3251 - Telecommunications 3252 and information 3253 exchange between 3254 systems - Local and 3255 metropolitan area 3256 networks - Specific 3257 requirements - Part 11: 3258 Wireless LAN Medium 3259 Access Control (MAC) 3260 and Physical Layer 3261 (PHY) specifications", 3262 IEEE Standard 802.11, 3263 2007, . 3268 [I-D.ietf-capwap-protocol-binding-ieee80211] Montemurro, M., 3269 Stanley, D., and P. 3270 Calhoun, "CAPWAP 3271 Protocol Binding for 3272 IEEE 802.11", draft- 3273 ietf-capwap-protocol- 3274 binding-ieee80211-12 3275 (work in progress), 3276 November 2008. 3278 [I-D.ietf-capwap-802dot11-mib] Shi, Y., Perkins, D., 3279 Elliott, C., and Y. 3280 Zhang, "CAPWAP Protocol 3281 Binding MIB for IEEE 3282 802.11", draft-ietf- 3283 capwap-802dot11-mib-02 3284 (work in progress), 3285 October 2008. 3287 Appendix A. Appendix A. Changes between -04 and -03 3289 T1. Running smilint results in the following errors: 3290 mibs/CAPWAP-BASE-MIB:480: [5] {index-exceeds-too-large} warning: index 3291 of row `capwapBaseWtpStateEntry' can exceed OID size limit by 6 3292 subidentifier(s) 3293 mibs/CAPWAP-BASE-MIB:582: [5] {index-exceeds-too-large} warning: index 3294 of row `capwapBaseWtpEntry' can exceed OID size limit by 6 3295 subidentifier(s) 3296 mibs/CAPWAP-BASE-MIB:1090: [5] {index-exceeds-too-large} warning: index 3297 of row `capwapBaseRadioBindEntry' can exceed OID size limit by 7 3298 subidentifier(s) 3299 mibs/CAPWAP-BASE-MIB:1181: [5] {index-exceeds-too-large} warning: index 3300 of row `capwapBaseStationEntry' can exceed OID size limit by 13 3301 subidentifier(s) 3302 mibs/CAPWAP-BASE-MIB:1249: [5] {index-exceeds-too-large} warning: index 3303 of row `capwapBaseWtpRebootStatsEntry' can exceed OID size limit by 6 3304 subidentifier(s) 3305 mibs/CAPWAP-BASE-MIB:1408: [5] {index-exceeds-too-large} warning: index 3306 of row `capwapBaseRadioStatsEntry' can exceed OID size limit by 7 3307 subidentifier(s) 3309 The reason is that these tables are indexed with objects of SYNTAX of 3310 CapwapBaseWtpIdTC which has a maximal size of 128, equal to the maximal 3311 size allowed for the whole OID. Reducing the maximal size of the TC to 3312 anything less or equal than 115 solves the problem. 3314 -------------------------------------------------------------- 3316 Refer to entPhysicalSerialNum in RFC4133 and Dan's comment, define 3317 CapwapBaseWtpIdTC with OCTET STRING (SIZE (0..32)) 3319 IF we use SnmpAdminString (SIZE (0..32)), libsmi would generate 3320 error: textual convention `CapwapBaseWtpIdTC' can not be derived from 3321 the textual convention `SnmpAdminString' 3323 T2. Section 5 - ' To reuse current MIB standards and future 3324 extensions for a wireless binding technology' - it is not clear what 3325 'future extensions' may be and I would not commit to using them in 3326 advance, so I would suggest to drop this 3328 ------------------------------------------------------------- 3330 Change it into " To be independent of any wireless technologies and 3331 have ability to reuse wireless binding MIB modules defined by other 3332 SDOs;" 3334 T3 What are the 'MIB standards of other SDOs' that need to be reused? 3335 Please refer to them specifically at least by providing one example - 3336 for instance where does Dot11OperationTable come from? 3338 -------------------------------------------------------------- 3340 It is changed into: 3342 The text give a definition of " 5.2. Wireless Binding MIB Modules" 3344 For Dot11OperationTable, the chang is: 3346 For example, the MIB tables such as Dot11OperationTable [IEEE.802- 3347 11.2007] are able to support WTP radio configuration. 3349 T4. In order for ifIndex to be used as a common handler for the 3350 CAPWAP MIB and for the interface specific MIB modules like a dot11 3351 MIB from IEEE one needs to ensure that the same numbering scheme and 3352 mapping is used by all MIB modules, and that it behaves identically 3353 for events like interface card swapping, reset or power loss. I do 3354 not see how this can happen, I am not sure that this is possible at 3355 all, and in any case there is no text in the CAPWAP MIB that explains 3356 this mechanism. 3358 -------------------------------------------------------------- 3360 in the Capwap Digest, Vol 39, Issue 4, we gave the text to explain a 3361 mechanism that preserves the values of ifIndex, Request mailing list 3362 to confirm it. 3364 In the section of "Relationship to the IF-MIB", add text "Also, as 3365 ifIndex[RFC2863] will be used as common handler for corresponding 3366 interfaces in the CAPWAP-BASE-MIB and specific wireless technologies 3367 MIB modules, the system (AC) MUST have a mechanisms that preserves 3368 the values of ifIndex in the ifTable at AC reboot." 3370 T5. Section 7.2 - 'The interface SHOULD be modeled as an ifEntry' - 3371 Is a SHOULD enough or rather a MUST is required here taking into 3372 account the requirements in Section 5. 3374 ----------------------------------------------------------------- 3376 It is changed into:MUST be 3378 T6. The documents that define the MIB modules required for IMPORTs 3379 must be listed in the Normative References section. 3381 ----------------------------------------------------------------- 3382 add reference to RFC3411 in the section of "MIB modules required for 3383 IMPORTS", add "SNMP-FRAMEWORK-MIB [RFC3411]," 3385 T7. In the example in Section 8 capwapBaseWtpId equals the 3386 representation of the OCTET STRING '12345678' and not the number 3387 12345678 3389 ---------------------------------------------------------------- 3391 Yes, it is change into '12345678' 3393 T8. In the example in Section 8 ifPhysicalAddress should have six 3394 zeros. 3396 ----------------------------------------------------------------- 3398 Yes, it is change into '000000' 3400 T9. What is the Vendor Identifier mentioned in Section 9 as being 3401 assigned by IANA? Is this something specific for this MIB document - 3402 in this case it needs to be mentioned in the IANA considerations 3403 section? 3405 ----------------------------------------------------------------- 3407 The description of Vendor Identifie is changed into: Vendor 3408 Identifier: A 32-bit value containing the IANA assigned "SMI Network 3409 Management Private Enterprise Codes" 3411 T10. Why does one need a special TC for CapwapBaseWtpIdTC? If this 3412 is typically a serial number, then SnmpAdminString SIZE (1..128) 3413 should do. 3415 ----------------------------------------------------------------- 3417 Station, radio, WTP are main objects to management by MIB drafts. 3418 They would appear in the serval table and notification. Suggest to 3419 have a TC for them. 3421 T11. In any case why is the SIZE in this TC fixed at 128? 3422 ----------------------------------------------------------------- 3424 Refer to entPhysicalSerialNum in RFC4133 and Dan's comment, define 3425 CapwapBaseWtpIdTC with OCTET STRING (SIZE (0..32)) 3427 T12. A number of read-write objects do not have the persistency 3428 behavior defined in case of agent reboot - 3429 capwapBaseStationSessionsLimit, capwapBaseDataChannelSecConfig, 3430 capwapBaseControlChannelAuthenConfig 3432 ----------------------------------------------------------------- 3434 Add the "The value of the object is persistent at restart/reboot." in 3435 the description of 3436 capwapBaseAcMaxRetransmit,capwapBaseAcChangeStatePendingTimer, capwap 3437 BaseAcDataCheckTimer,capwapBaseAcDTLSSessionDeleteTimer,capwapBaseAcE 3438 choInterval, capwapBaseAcWaitJoinTimer, 3439 capwapBaseAcWaitDTLSTimer,capwapBaseAcSilentInterval, 3440 capwapBaseAcRetransmitInterval 3442 T13 - Is more than one security policy possible to be configured on a 3443 given AC? If not, then why is capwapBaseDataChannelSecConfig a BIT? 3445 ----------------------------------------------------------------- 3447 Yes, the data type of capwapBaseDataChannelSecConfig should be 3448 INTEGER 3450 T14 - the name of capwapBaseDataChannelSecOptions should better be 3451 something that includes DTLSPolicy to make clear to what fields in 3452 the AC Descriptor it corresponds. The DESCRIPTION should also be 3453 consistent with the text in the protocol document 3455 ----------------------------------------------------------------- 3457 To make it consistent with protocol, change 3458 capwapBaseDataChannelSecOptions with 3459 capwapBaseDataChannelDTLSPolicyOptions. Change 3460 capwapBaseDataChannelSecConfig with 3461 capwapBaseDataChannelDTLSPolicyConfig Also, the DESCRIPTION should 3462 also be consistent with the text in the protocol document 3464 T15 - is more than one credential type possible to be configured on a 3465 given AC? If not then why is capwapBaseControlChannelAuthenConfig a 3466 BIT? 3467 ----------------------------------------------------------------- 3469 Yes, the data type of capwapBaseControlChannelSecConfig should be 3470 INTEGER 3472 T16 - it would be good for management applications writers to mention 3473 in the DESCRIPTION clause thatcapwapBaseAcnameListName is expected to 3474 be a UTF-8 encoded string 3476 ----------------------------------------------------------------- 3477 Yes, it is added 3479 T17 - Object names in capwapBaseWtpStateTable do not respect the 3480 naming conditions relative to capwapBaseWtpStateEntry 3482 --------------------------------------------------------------- 3484 Add one more WtpState in the object name. For example, 3485 capwapBaseWtpId is to changed into capwapBaseWtpStateWtpId, other 3486 objects are similiar. 3488 all objects with new name: 3490 CapwapBaseWtpStateEntry ::= SEQUENCE { 3491 capwapBaseWtpStateWtpId CapwapBaseWtpIdTC, 3492 capwapBaseWtpStateWtpIpAddressType InetAddressType, 3493 capwapBaseWtpStateWtpIpAddress InetAddress, 3494 capwapBaseWtpStateWtpPhyAddress PhysAddress, 3495 capwapBaseWtpState INTEGER 3496 } 3498 T18 - same for capwapBaseWtpStateTable 3500 ----------------------------------------------------------------- 3502 Same as above 3504 T19 - capwapBaseWtpName is of SYNTAX AsnmpAdminString which is 3505 limited to SIZE 255, while the WTP name can be up to 512 characters 3507 -------------------------------------------------------------- 3509 change with OCTET STRING(SIZE(512)) 3511 T20 - same about capwapbaseWtpLocation which can be up to 1024 3512 characters in length 3514 ----------------------------------------------------------------- 3516 change with OCTET STRING(SIZE(1024)) 3518 T21 - Section 4.8 defines default value for a number of variables. 3519 However, these are not reflected in the MIB - for example why is 3520 there not a DEFAULT clause that will set capwapBaseWtpFallbackEnable 3521 to enabled(1) as per 4.8.9? Or capwapBaseWtpMaxDiscoveries which has 3522 a default of 10 defined in 4.8.5 3524 ------------------------------------------------------------------- 3525 Added DEFVAL { enabled } for capwapBaseWtpFallbackEnable. 3526 capwapBaseWtpMaxDiscoveries already has DEFVAL { 10 }. 3528 T22 - why does the MIB support reserved(0) for 3529 capwapBaseWtpFallbackEnable. Does setting to reserved(0) by the 3530 management application have any significance? 3532 ----------------------------------------------------------------- 3534 The reserved(0) is removed for capwapBaseWtpFallbackEnable 3536 T23 - According to 4.8.8 capwapBaseWtpRetransmitCount is a monotonous 3537 increasing counter. The appropriate SYNTAX for such an object is 3538 Counter32 and not Unsigned32 3540 ----------------------------------------------------------------- 3542 Yes, capwapBaseWtpRetransmitCount should use Counter32 3544 T24 - it would be useful to define UNITS clauses for objects like 3545 capwapBaseWtpRetransmitCount 3547 ----------------------------------------------------------------- 3549 It seemed capwapBaseWtpRetransmitCount does not require a UNIT. 3551 T25 - define a range (2..180) for capwapBaseWtpMaxDiscoveryInterval 3553 ---------------------------------------------------------------- 3555 add value scope of (0..24) to capwapBaseWtpDataChannelDeadInterval 3556 add value scope of (2..180) to capwapBaseWtpMaxDiscoveryInterval 3557 add value scope of (30..4294967295) to capwapBaseWtpWaitDTLSTimer 3558 add value scope of (30..4294967295) to capwapBaseAcWaitDTLSTimer 3559 add value scope of (20..4294967295) to capwapBaseAcWaitJoinTimer 3561 T27 - Object names in capwapBaseRadioBindTable do not respect the 3562 naming conditions relative to capwapBaseRadioBindEntry 3564 -------------------------------------------------------------------- 3566 Change all objects (entry, table)'s prefix from capwapBaseRadioBind 3567 to capwapBaseWirelessBinding. 3569 change CapwapBaseRadioBindTable to CapwapBaseWirelessBindingTable 3571 The Objects with new name: 3573 CapwapBaseWirelessBindingEntry ::= SEQUENCE { 3574 capwapBaseWirelessBindingRadioId CapwapBaseRadioIdTC, 3575 capwapBaseWirelessBindingVirtualRadioIfIndex InterfaceIndex, 3576 capwapBaseWirelessBindingType INTEGER 3577 } 3579 T28 - What do the values reserved(0) and reserved(2) in 3580 capwapBaseRadioWirelessBinding mean? Are they ever returned by an 3581 agent? 3583 ----------------------------------------------------------------- 3585 removed the reserved(0) and reserved(2) from the object definition. 3587 T29 - in other IETF documents (like RFC 4363) VLAN names are defined 3588 as SnmpAdminString (SIZE (0..32)). I suggest the same for 3589 capwapBaseStationVlanName. I am aware that section 4.6.8 allows for 3590 names up to 512, but I do not find this justified. In any case, if 3591 the full size defined in 4.6.8 is to be accommodated, then 3592 SnmpAdminString would not be sufficient as its size is limited to 3593 256. 3595 ----------------------------------------------------------------- 3597 capwapBaseStationVlanName use SnmpAdminString (SIZE (0..32)) 3599 T30 - Object names in capwapBaseWtpRebootStatsTable do not respect 3600 the naming conditions relative to capwapBaseWtpRebootStatsEntry 3602 ------------------------------------------------------------------ 3604 Change table name from capwapBaseWtpRebootStatTable to 3605 capwapBaseWtpEventsStatsTable. 3607 The objects also do similar changes, for example, change 3608 capwapBaseWtpRebootCount to capwapBaseWtpEventsStatsRebootCount 3610 The objects with new name: 3612 CapwapBaseWtpEventsStatsEntry ::= SEQUENCE { 3613 capwapBaseWtpEventsStatsRebootCount Counter32, 3614 capwapBaseWtpEventsStatsInitCount Counter32, 3615 capwapBaseWtpEventsStatsLinkFailureCount Counter32, 3616 capwapBaseWtpEventsStatsSwFailureCount Counter32, 3617 capwapBaseWtpEventsStatsHwFailureCount Counter32, 3618 capwapBaseWtpEventsStatsOtherFailureCount Counter32, 3619 capwapBaseWtpEventsStatsUnknownFailureCount Counter32, 3620 capwapBaseWtpEventsStatsLastFailureType INTEGER 3622 } 3624 T31 - Object names in capwapBaseWtpRadioStatsTable do not respect the 3625 naming conditions relative to capwapBaseWtpRadioStatsEntry 3627 ---------------------------------------------------------------- 3629 Change table name from capwapBaseWtpRadioStatsTable to 3630 capwapBaseRadioEventsStatsTable. The objects also do similar 3631 changes, for example, change capwapBaseRadioSwFailCount to 3632 capwapBaseRadioEventsStatsSwFailCount. 3634 The objects with new name: 3636 CapwapBaseRadioEventsStatsEntry ::= SEQUENCE { 3637 capwapBaseRadioEventsStatsResetCount Counter32, 3638 capwapBaseRadioEventsStatsSwFailCount Counter32, 3639 capwapBaseRadioEventsStatsHwFailCount Counter32, 3640 capwapBaseRadioEventsStatsOtherFailCount Counter32, 3641 capwapBaseRadioEventsStatsUnknownFailCount Counter32, 3642 capwapBaseRadioEventsStatsConfigUpdateCount Counter32, 3643 capwapBaseRadioEventsStatsChannelChangeCount Counter32, 3644 capwapBaseRadioEventsStatsBandChangeCount Counter32, 3645 capwapBaseRadioEventsStatsCurrentNoiseFloor Integer32, 3646 capwapBaseRadioEventsStatsDecryptErrorCount Counter32, 3647 capwapBaseRadioEventsStatsLastFailType INTEGER 3648 } 3650 E1. Even if this document uses terminology borrowed from other 3651 CAPWAP documents, acronyms like WTP, AC, etc. should be expanded at 3652 the first occurrence. 3654 ----------------------------------------------------------------- 3656 The Terminology section is updated with more Terminology such as 3657 Autonomous WLAN Architecture, Centralized WLAN Architecture, Wireless 3658 Binding,Split and Local MAC and so on. 3660 E2. It would be good for the document to be grammar and spelling 3661 checked by a native English speaker. 3663 E3. No need for sections 6.1, 6.2, 6.3 - these are standard in any 3664 MIB module and their content is well known 3666 ----------------------------------------------------------------- 3668 Ok, there are removed 3669 E4. In Section 7.2 there is no need to mention information that is 3670 not specific to the CAPWAP MIB 3672 -------------------------------------------------------------------- 3674 Removed the "Some specific interpretations of ifTable for CAPWAP- 3675 BASE-MIB are as follow." and the interpretations followed it. 3677 E5. In the example in Section 8 ifType should be equal with the 3678 value assigned by IANA for the ifType - you may mark it xxx and enter 3679 an editor note saying 'RFC Editor - please replace xxx with the value 3680 allocated by IANA for IANAifType of 'WTP Virtual Radio Interface') 3682 ----------------------------------------------------------------- 3684 It is done according to the comment 3686 E6. Please indicate specifically for each field for the protocols 3687 timers message the exact reference in than CAPWAP protocol document. 3689 ----------------------------------------------------------------- 3691 The section was updated according to protocol 3693 E7. The numbering of referred paragraphs in the REFERENCE clauses 3694 are not synchronized with the latest version of the CAPWAP protocol 3695 document as per http://www.rfc-editor.org/rfc/rfc3411.txt 3697 ------------------------------------------------------------------- 3699 The REFERENCE clauses for the following TCs or objects are changed 3700 with new id: 3702 CapwapBaseTunnelModeTC 3703 Section 4.6.42 to Section 4.6.43 3705 CapwapBaseMacTypeTC 3706 Section 4.6.43 to Section 4.6.44 3708 capwapBaseWtpName 3709 Section 4.6.44 to Section 4.6.45 3711 capwapBaseWtpLocation 3712 Section 4.6.29 to Section 4.6.30 3714 capwapBaseWtpBaseMacAddress 3715 Section 4.6.39 to Section 4.6.40 3716 capwapBaseTunnelModeOptions 3717 Section 4.6.42 to Section 4.6.43 3719 capwapBaseMacTypeOptions 3720 Section 4.6.43 to Section 4.6.44 3722 capwapBaseWtpRadiosInUseNum and capwapBaseWtpRadioNumLimit 3723 Section 4.6.40 to Section 4.6.41 3725 capwapBaseWtpStaticIpEnable, capwapBaseWtpStaticIp, 3726 capwapBaseWtpNetmask,capwapBaseWtpGateway 3727 Section 4.6.47 to Section 4.6.48 3729 capwapBaseWtpFallbackEnable 3730 Section 4.6.41 to Section 4.6.42 3732 all the objects in the capwapBaseWtpRebootStatsTable 3733 Section 4.6.46 to Section 4.6.47 3734 all the objects in the capwapBaseRadioStatsTable 3735 Section 4.6.45 to Section 4.6.46 3737 capwapBaseJoinFailure,capwapBaseImageUpgradeFailure, 3738 capwapBaseConfigMsgError 3739 Section 4.6.34 to Section 4.6.35 3741 capwapBaseRadioOperableStatus,capwapBaseNtfRadioOperStatusFlag, 3742 capwapBaseNtfRadioStatusCause 3743 Section 4.6.33 to Section 4.6.34 3745 capwapBaseNtfJoinFailureReason,capwapBaseNtfImageFailureReason 3746 Section 4.6.34 to Section 4.6.35 3748 capwapBaseNtfConfigMsgErrorType,capwapBaseNtfMsgErrorElements 3749 Section 4.6.35 to Section 4.6.36 3751 E8. No need to repeat the text in the DESCRIPTION clause if a TC is 3752 used (e.g. capwapBaseTunnelModeOption, capwapBaseMacTypeOptions) 3754 ---------------------------------------------------------------- 3756 Change the description of them, and only talk about the function of 3757 objects. 3759 E9 - capwapBaseWtpMaxRetransmitCnt is not a counter so the suffix Cnt 3760 should be dropped from the name. 3762 ------------------------------------------------------------------- 3763 Change capwapBaseWtpMaxRetransmitCnt into capwapBaseWtpMaxRetransmit 3765 E10 - capwapBaseAcMaxRetransmitCnt is not a counter so the suffix Cnt 3766 should be dropped from the name. 3768 ------------------------------------------------------------------- 3770 Change capwapBaseAcMaxRetransmitCnt into capwapBaseAcMaxRetransmit 3772 Other changes made by authors: 3773 1) To keep Terminology consistent 3774 change "MIBs" with "MIB modules", change "MIB standards" with "MIB 3775 modules". 3776 2) Replace "As a generic mechanism, it is independent of any wireless 3777 technologies and defined by an independent MIB file" with 3778 "It is designed to accommodate the specific needs of each wireless 3779 technology in a standard way. It is independent of any wireless 3780 technologies;" 3781 3) add reference to [IEEE.802-11.2007],[I-D.ietf-capwap-protocol-binding 3782 -ieee80211] and [I-D.ietf-capwap-802dot11-mib] 3783 4) Respect the naming conditions to capwapBaseWtpTable, 3784 change capwapBaseMacTypeOptions to capwapBaseWtpMacTypeOptions 3785 change capwapBaseTunnelModeOptions to capwapBaseWtpTunnelModeOptions 3786 5) Change IPV6 to IPv6, IPV4 to IPv4 3787 6) remove redundant "the" in the R"Represents the the next" 3788 7) reorganized the section of overview, and divided it into the 3789 following sub sections: 3790 5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3791 5.1. Requirements and Constraints . . . . . . . . . . . . . . . 5 3792 5.2. Wireless Binding MIB Modules . . . . . . . . . . . . . . . 5 3793 5.3. Design Objectives . . . . . . . . . . . . . . . . . . . . 5 3794 5.4. Design Idea . . . . . . . . . . . . . . . . . . . . . . . 6 3795 5.5. Mechanism of Reusing Wireless Binding MIB Modules . . . . 6 3796 5.6. CAPWAP Protocol Wireless Binding MIB Module . . . . . . . 7 3797 Especially, add the Terminology of "CAPWAP Protocol Wireless Binding 3798 MIB Module" and "Wireless Binding MIB Module". 3800 8) Remove unused(0) from CapwapBaseTunnelModeTC, 3801 capwapBaseControlChannelAuthenOptions 3802 and capwapBaseControlChannelAuthenConfig 3803 9) Update some words in the section of" Example of CAPWAP-BASE-MIB 3804 Module Usage" 3805 10) Added capwapBaseAcEcnSupport, capwapBaseWtpEcnSupport 3806 Authors' Addresses 3808 Yang Shi (editor) 3809 H3C Tech. Co., Ltd 3810 Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian District, 3811 Beijing 3812 China(100085) 3814 Phone: +86 010 82775276 3815 EMail: young@h3c.com 3817 David Perkins (editor) 3818 SNMPinfo 3819 288 Quailbrook Ct San Carlos, 3820 CA 94070 3821 USA 3823 Phone: +1 408 394-8702 3824 EMail: dperkins@snmpinfo.com 3826 Chris Elliott (editor) 3827 Cisco Systems, Inc. 3828 7025 Kit Creek Rd., P.O. Box 14987 Research Triangle Park 3829 27709 3830 USA 3832 Phone: +1 919-392-2146 3833 EMail: chelliot@cisco.com 3835 Yong Zhang (editor) 3836 Fortinet, Inc. 3837 1090 Kifer Road 3838 Sunnyvale, CA 94086 3839 USA 3841 EMail: yzhang@fortinet.com