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