idnits 2.17.1 draft-ietf-capwap-base-mib-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 20. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 3216. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 3227. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 3234. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 3240. ** The document seems to lack an RFC 3978 Section 5.4 (updated by RFC 4748) Copyright Line. 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 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 (November 1, 2008) is 5648 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 4133 (Obsoleted by RFC 6933) Summary: 3 errors (**), 0 flaws (~~), 1 warning (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force Y. Shi, Ed. 3 Internet-Draft H3C Tech. Co., Ltd 4 Intended status: Standards Track D. Perkins, Ed. 5 Expires: May 5, 2009 SNMPinfo 6 C. Elliott, Ed. 7 Cisco Systems, Inc. 8 Y. Zhang, Ed. 9 Fortinet, Inc. 10 November 1, 2008 12 CAPWAP Protocol Base MIB 13 draft-ietf-capwap-base-mib-03 15 Status of This Memo 17 By submitting this Internet-Draft, each author represents that any 18 applicable patent or other IPR claims of which he or she is aware 19 have been or will be disclosed, and any of which he or she becomes 20 aware will be disclosed, in accordance with Section 6 of BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF), its areas, and its working groups. Note that 24 other groups may also distribute working documents as Internet- 25 Drafts. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt. 35 The list of Internet-Draft Shadow Directories can be accessed at 36 http://www.ietf.org/shadow.html. 38 This Internet-Draft will expire on May 5, 2009. 40 Abstract 42 This memo defines a portion of the Management Information Base (MIB) 43 for use with network management protocols. In particular, it 44 describes managed objects for modeling the Control And Provisioning 45 of Wireless Access Points (CAPWAP) Protocol. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 50 2. The Internet-Standard Management Framework . . . . . . . . . . 3 51 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 54 6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 5 55 6.1. The capwapBaseObjects Subtree . . . . . . . . . . . . . . 6 56 6.2. The capwapBaseConformance Subtree . . . . . . . . . . . . 6 57 6.3. The capwapBaseNotifications Subtree . . . . . . . . . . . 6 58 6.4. Brief Description of MIB Objects . . . . . . . . . . . . . 6 59 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7 60 7.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 7 61 7.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 7 62 7.3. Relationship to the ENTITY-MIB . . . . . . . . . . . . . . 8 63 7.4. Relationship to MIB standards of other SDOs . . . . . . . 9 64 7.5. MIB modules required for IMPORTS . . . . . . . . . . . . . 9 65 8. Example of CAPWAP-BASE-MIB Usage . . . . . . . . . . . . . . . 9 66 9. CAPWAP Message Element Extension . . . . . . . . . . . . . . . 12 67 9.1. CAPWAP Protocol Timers . . . . . . . . . . . . . . . . . . 12 68 9.2. CAPWAP Protocol Variables . . . . . . . . . . . . . . . . 15 69 9.3. CAPWAP Messages for CAPWAP Control Message Extension . . . 15 70 9.3.1. Configuration Status Response Message . . . . . . . . 15 71 9.3.2. Configuration Update Response Message . . . . . . . . 16 72 10. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 16 73 11. Security Considerations . . . . . . . . . . . . . . . . . . . 64 74 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 65 75 12.1. IANA Considerations for CAPWAP-BASE-MIB . . . . . . . . . 65 76 12.2. IANA Considerations for ifType . . . . . . . . . . . . . . 65 77 13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 65 78 14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 65 79 15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 66 80 15.1. Normative References . . . . . . . . . . . . . . . . . . . 66 81 15.2. Informative References . . . . . . . . . . . . . . . . . . 67 82 Appendix A. Appendix A. Changes from -02 . . . . . . . . . . . . 67 84 1. Introduction 86 The CAPWAP Protocol [I-D.ietf-capwap-protocol-specification] defines 87 a standard, interoperable protocol, which enables an Access 88 Controller (AC) to manage a collection of Wireless Termination 89 Points(WTPs) 91 This document defines a MIB module that can be used to manage CAPWAP 92 implementations. This MIB module covers both configuration and WTP 93 status-monitoring aspects of CAPWAP, and provides a way to reuse 94 current MIB standards and future extensions for any wireless binding 95 technology. 97 2. The Internet-Standard Management Framework 99 For a detailed overview of the documents that describe the current 100 Internet-Standard Management Framework, please refer to section 7 of 101 RFC 3410 [RFC3410]. 103 Managed objects are accessed via a virtual information store, termed 104 the Management Information Base or MIB. MIB objects are generally 105 accessed through the Simple Network Management Protocol (SNMP). 106 Objects in the MIB are defined using the mechanisms defined in the 107 Structure of Management Information (SMI). This memo specifies a MIB 108 module that is compliant to the SMIv2, which is described in STD 58, 109 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 110 [RFC2580]. 112 3. Terminology 114 This document uses terminology from the document describing the 115 CAPWAP Protocol specification [I-D.ietf-capwap-protocol- 116 specification]. WTPs are viewed as remote RF interfaces controlled 117 by the AC via CAPWAP protocol. The CAPWAP protocol supports two 118 modes of operation: Split and Local MAC. In Split MAC mode all L2 119 wireless data and management frames are encapsulated via the CAPWAP 120 protocol and exchanged between the AC and the WTPs. The Local MAC 121 mode of operation allows for the data frames to be either locally 122 bridged, or tunneled as 802.3 frames. From AC, operator could 123 centrally control WTPs configuration and monitor their status. 124 CAPWAP use DTLS protocol to implement control channel security. 126 4. Conventions 128 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 129 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 130 document are to be interpreted as described in RFC 2119 [RFC2119]. 132 5. Overview 134 The CAPWAP Protocol MIB module (CAPWAP-BASE-MIB) have the following 135 design objectives: 137 - To implement an architecture that uses SNMP for the management and 138 control of wireless networks, answering the operators requirements 139 for centralized management, whatever the deployment or configuration 140 of the network devices (centralized, distributed, or some mix) 142 - To be consistent with CAPWAP protocol 144 - To reuse current MIB standards and future extensions for a wireless 145 binding technology 147 - To enable interoperability between vendors 149 - To meet operator requirements for centralized architectures 151 The basic idea of CAPWAP-BASE-MIB is: 153 - The CAPWAP-BASE-MIB MUST be run on the AC devices and is NOT 154 REQUIRED on the WTP devices. It follows same idea as CAPWAP 155 protocol: Centralized Control 157 - As a generic mechanism, it is independent of any wireless binding 158 technologies and defined by an independent MIB file 160 - To be independent of any wireless binding technologies and have 161 ability to reuse MIB standards of other SDOs, is the main challenge 162 for design of the MIB 164 - ifIndex [RFC2863] will be used as common handler for corresponding 165 interfaces in the CAPWAP-BASE-MIB and specific wireless technologies 166 MIB modules 168 - The operator could manage and control the centralized wireless 169 architectures using multiple MIB standards defined by multiple SDOs, 170 while keeping them loosely coupled 172 It is designed to satisfy the following requirements and constraints: 174 - From AC to centrally manage and monitor WTPs 176 - The MIB module supports CAPWAP protocol parameters queries 178 - The MIB module supports showing WTPs current state 179 - The MIB module provides the information of AC, WTPs, radio and 180 station objects' basic property and their relationship 182 - The MIB module supports indicating the 'WTP Virtual Radio 183 Interface' and PHY radio's mapping relationship 185 - The counters are provided for WTP, radio's reboot event, hardware 186 event failure and so on 188 - The MIB module provides the various notification like channel up, 189 join failure and so on 191 Before coming to details of CAPWAP-BASE-MIB module, it will introduce 192 how CAPWAP-BASE-MIB is able to be independent of any wireless binding 193 technologies and reuse MIB standards of other SDOs. As centralized 194 Wireless architecture, the operator has to prepare configuration on 195 the AC before WTPs connects to AC. For any wireless binding 196 technology, the configuration and management of radio is very 197 important. Under centralized Wireless architecture, according to 198 [I-D.ietf-capwap-protocol-specification], a specific PHY radio could 199 be identified by identifier of a WTP and radio (WTP id + radio id). 200 As usual, the standard of a binding technology provides MIB standard 201 for radio management on its own. For example, according to IEEE 202 802.11 WG MIB standards, the MIB tables such as Dot11OperationTable 203 are able to support WTP radio configuration. These tables use 204 ifIndex as the index, and work well under standalone Wireless 205 architecture. 207 To reuse MIB objects (defined by SDOs such as IEEE) for radio is very 208 important, and the key point is to reuse the idea of ifIndex. So it 209 is required a way to maintain the mapping relationship between 'WTP 210 id + radio id' and 'ifIndex'. As a generic mechanism, ifIndex can 211 identify an interface in abstract way, and it does NOT care for an 212 interface's PHY location (either on the WTP or AC). AC can have 213 interfaces of 'WTP Virtual Radio Interface' ifType, which will 214 logically represent PHY radios on the WTP. It looks like that PHY 215 radios are located on the AC, and PHY location of WTP (radio) is 216 hidden to the operator. Operator can operate radios by MIB tables 217 (such as IEEE 802.11 WG's) with ifIndex of 'WTP Virtual Radio 218 Interface'. As an Abstract interface, 'WTP Virtual Radio Interface' 219 could be used by any wireless binding technology such as IEEE 802.11 220 and 802.16. The table of capwapRadioBindTable will indicate the 221 mapping relationship between 'WTP id + Radio id' and IfIndex. 223 6. Structure of the MIB Module 224 6.1. The capwapBaseObjects Subtree 226 The subtree provides information for statistic data and configuration 227 parameters of WTP and radio. 229 6.2. The capwapBaseConformance Subtree 231 The subtree provides conformance information of MIB objects. 233 6.3. The capwapBaseNotifications Subtree 235 The subtree describes the notifications defined in the MIB module, 236 and their purpose. 238 6.4. Brief Description of MIB Objects 240 The MIB objects were derived from the CAPWAP protocol document 241 [I-D.ietf- capwap-protocol-specification]. 243 1) capwapBaseAcNameListTable 245 The AC name list table is used to configure AC name list. 247 2) capwapBaseMacAclTable 249 The ACL table is used to configure stations' Access Control 250 List(ACL). 252 3) capwapBaseWtpStateTable 254 The WTPs status table is used to indicate each WTP's CAPWAP FSM 255 state. 257 4) capwapBaseWtpTable 259 The WTPs table is used for providing property and configuration 260 information in details for WTPs in running state. 262 5) capwapBaseRadioBindTable 264 The radio bind table is used to indicate the mapping relationship 265 between logical interface of 'WTP Virtual Radio Interface' ifType and 266 PHY radio. 268 6) capwapBaseStationTable 270 The station table is used for providing stations' basic property 271 information. 273 7) capwapBaseWtpRebootStatsTable 275 The WTP reboot statistic table is used for collecting WTP reboot 276 count, link failure count, hardware failure count and so on. 278 8) capwapBaseRadioStatsTable 280 The WTP radio statistic table is used for collecting radio reset 281 count, channel change count, hardware failure count and so on. 283 7. Relationship to Other MIB Modules 285 7.1. Relationship to the SNMPv2-MIB 287 The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being 288 mandatory for all systems, and the objects apply to the entity as a 289 whole. The 'system' group provides identification of the management 290 entity and certain other system-wide data. The CAPWAP-BASE-MIB does 291 not duplicate those objects. 293 7.2. Relationship to the IF-MIB 295 The Interfaces Group [RFC2863] defines generic managed objects for 296 managing interfaces. This memo contains the media-specific 297 extensions to the Interfaces Group for managing WTP radio object that 298 are modeled as interfaces. 300 IF-MIB is required to support on the AC. For each PHY radio on the 301 WTP, it will have a logical interface of 'WTP Virtual Radio 302 Interface' ifType on the AC. 'WTP Virtual Radio Interface' provides 303 a way to configure radio's parameters and query radio's traffic 304 statistics, and reuse the MIBs defined by a specific wireless binding 305 technology. The interface SHOULD be modeled as an ifEntry and 306 provide appropriate interface information. 308 Some specific interpretations of ifTable for CAPWAP-BASE-MIB are as 309 follow. 311 Object Use for the CAPWAP-BASE-MIB. 313 ifIndex Each interface of 'WTP Virtual Radio Interface' 314 ifType maybe be represented by an ifEntry. 316 ifDescr Description of the interface of 'WTP Virtual Radio 317 Interface' ifType. 319 ifType IANAifType of 'WTP Virtual Radio Interface'. 321 ifName Textual name (unique on this system) of the interface 322 or an octet string of zero length. 324 ifAlias The nonvolatile 'alias' name for the interface, as 325 specified by a network manager. 327 ifPhysAddress The physical address of the interface, such as the 328 BSSID of a 802.11 radio. 330 ifAdminStatus This variable indicates the operator's intent as 331 to whether PHY should be enabled, disabled, or 332 running in some diagnostic testing mode on this 333 interface. 334 Also see [RFC2863]. 336 ifOperStatus This value reflects the actual or operational status 337 of radio. 338 Also see [RFC2863]. 340 ifLastChange The value of sysUpTime at the time the interface 341 entered its current operational state. 342 Also see [RFC2863]. 344 ifInOctets The number of received octets over the interface; 345 such as the number of octets received as 802.11 346 frames. 348 ifOutOctets The number of transmitted octets over the interface; 349 such as the number of octets transmitted as 802.11 350 frames. 352 ifInErrors The number of inbound frames dropped due to 353 uncorrectable errors. 355 ifInUnknownProtos 356 The number of received frame discarded during 357 frame header validation, including frames with 358 unrecognized label values. 360 ifOutErrors The number of outbound frames dropped due to 361 uncorrectable errors. 363 7.3. Relationship to the ENTITY-MIB 365 The ENTITY-MIB [RFC4133] meets need for a standardized way of 366 representing a single agent, which supports multiple instances of one 367 MIB. It could express a certain relationship between multiple 368 entities, and provide entity properties for each entity. 370 Under the wireless centralized architectures, the SNMP agent will run 371 on the AC, and not required on the WTP. By the ENTITY-MIB on the AC, 372 it could keep entity information such as firmware revision and 373 software revision of AC and WTPs. From the ENTITY-MIB perspective, 374 the overall physical entity (AC) is a 'compound' of multiple physical 375 entities (WTPs which connects to AC), all entities are identified by 376 Physical index. In the capwapBaseWtpTable of CAPWAP-BASE-MIB, it 377 uses capwapBaseWtpPhyIndex object to keep the mapping relationship of 378 WTP object between CAPWAP-BASE-MIB and ENTITY-MIB. 380 By combining the MIBs, operators could query AC and WTP's status and 381 properties. For example, they could get WTP's current status through 382 CAPWAP-BASE-MIB, and WTP's software revision information through 383 ENTITY-MIB. 385 7.4. Relationship to MIB standards of other SDOs 387 The MIB standards (such as IEEE 802.11 MIB) of a wireless binding is 388 required to support on the AC. The CAPWAP-BASE-MIB module is able to 389 support any wireless binding technology. Through ifIndex of 'WTP 390 Virtual Radio Interface' ifType, it provides consistent and abstract 391 way of reusing MIB objects of a wireless binding technology. 393 7.5. MIB modules required for IMPORTS 395 The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], 396 SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863], INET- 397 ADDRESS-MIB [RFC4001] and ENTITY-MIB [RFC4133]. 399 8. Example of CAPWAP-BASE-MIB Usage 401 With the idea of 'WTP Virtual Radio Interface' in the mind, the 402 usage of MIB will be easily understood. Here takes IEEE 802.11 403 binding technology as an example. 405 1) Identify each PHY radio by 'WTP Virtual Radio Interface' 407 According to [I-D.ietf-capwap-protocol-specification], each radio on 408 a WTP will be identified by a radio Id. Each WTP could be identified 409 by its serial number. 411 When configuration for a WTP is prepared before a WTP connects to AC, 412 the following information is available in the 413 CapwapBaseRadioBindTable. 415 In CapwapBaseRadioBindTable 416 { 417 capwapBaseWtpId = 12345678, 418 capwapBaseRadioId = 1, 419 capwapBaseWtpVirtualRadioifIndex = 10, 420 capwapBaseRadioWirelessBinding = dot11(2) 421 } 423 Suppose WTP's serial number is 12345678, and first radio id is 1. 424 On the AC, the ifIndex of interface in 'WTP Virtual Radio Interface' 425 ifType is 10 which represents the PHY radio 1. 427 By the mechanism of 'WTP Virtual Radio Interface', it seems WTP 428 PHY radios are located on the AC. The interface of 'WTP Virtual 429 Radio Interface' ifType is modeled by ifTable. 431 In ifTable 432 { 433 ifIndex = 10, 434 ifDescr = 'WTP Virtual Radio Interface', 435 ifType = IANAifType of 'WTP Virtual 436 Radio Interface', 437 ifMtu = 0, 438 ifSpeed = 0, 439 ifPhysAddress = 0.0.0.0.0.0, 440 ifAdminStatus = true, 441 ifOperStatus = false, 442 ifLastChange = 0, 443 ifInOctets = 0, 444 ifInUcastPkts = 0, 445 ifInDiscards = 0, 446 ifInErrors = 0, 447 ifInUnknownProtos = 0, 448 ifOutOctets = 0, 449 ifOutUcastPkts = 0, 450 ifOutDiscards = 0, 451 ifOutErrors = 0 452 } 454 2) Configure specific wireless binding parameters for 'WTP Virtual 455 Radio Interface' 456 It will be done on the AC through specific wireless binding MIB 457 such as IEEE 802.11 MIB. 458 For example, to configure parameter for 'WTP Virtual Radio Interface' 459 by 802.11 Dot11OperationTable. 461 In Dot11OperationTable 462 { 463 ifIndex = 10, 464 dot11MACAddress = 0.0.0.0.0.0, 465 dot11RTSThreshold = 2347, 466 dot11ShortRetryLimit = 7, 467 dot11LongRetryLimit = 4, 468 dot11FragmentationThreshold = 256, 469 dot11MaxTransmitMSDULifetime = 512, 470 dot11MaxReceiveLifetime = 512, 471 dot11ManufacturerID = 'capwap', 472 dot11ProductID = 'capwap' 473 } 475 In the example, it suppose ifIndex of an interface in 476 'WTP Virtual Radio Interface' ifType is 10. 478 3) Other configurations for a specific wireless binding 479 For example, WLAN service configuration will be done through CAPWAP 480 binding MIB and IEEE 802.11 MIB. In the CAPWAP 802.11 binding MIB 481 draft, it will give more explain. 483 4) WTP reports its current configuration status 484 After join phase and before WTP get configuration from AC, it will 485 report its current configuration status to AC through configuration 486 status request message. The data of MIB objects will be updated on 487 the AC. For example, for 802.11 binding, WTP will update data in the 488 ifTable and IEEE 802.11 MIB so on according to message content. 489 As an example for ifIndex 10, its ifOperStatus in ifTable will be 490 updated according to current radio operational status in the 491 CAPWAP message. 493 5) Query WTP and radio statistics data 494 After WTPs come to run status, operator could query WTP and 495 radio statistics data through CAPWAP-BASE-MIB and specific binding 496 MIB. For example, through dot11CountersTable in the IEEE 802.11 MIB, 497 operator could query counter data for radio which is identified 498 by ifIndex of a virtual radio interface. With capwapBaseAcState table 499 in the MIB, operator could query configuration and properties of 500 WTPs which are in run status. 502 6) Query other statistics data of a specific wireless binding 503 For example, operator could query the statistics data of 504 WLAN service through 802.11 binding MIB and IEEE 802.11 MIB. 505 In the CAPWAP 802.11 binding MIB draft, it will give more explain. 507 7) Query other properties of WTP 508 Operator could query MIB objects in the ENTITY-MIB by 509 capwapBaseWtpPhyIndex in the capwapBaseWtpTable of CAPWAP-BASE-MIB. 510 The properties of WTP such as software version, hardware version 511 and so on are available in the ENTITY-MIB. 513 9. CAPWAP Message Element Extension 515 This section describes the CAPWAP control message extension for 516 CAPWAP protocol to support CAPWAP-BASE-MIB. 518 To enable CAPWAP protocol timers and variables[I-D.ietf-capwap- 519 protocol-specification] manageable through CAPWAP protocol, the 520 following capwap message element extensions are defined using Vendor 521 Specific Payload message element in this section. These message 522 elements are used by WTP to report extra configuration information to 523 AC. 525 CAPWAP Message Element Vendor Identifier Element ID 527 CAPWAP Protocol Timers Id assigned by IANA 1 528 CAPWAP Protocol Variables Id assigned by IANA 2 530 9.1. CAPWAP Protocol Timers 532 0 1 2 3 533 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 534 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 535 | Vendor Identifier | 536 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 537 | Element ID | DataChannelKeepAlive | 538 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 539 | DataChannelDeadInterval | DiscoveryInterval | 540 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 541 | DTLSSessionDelete | EchoInterval | 542 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 543 | IdleTimeout | 544 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 545 | ImageDataStartTimer | MaxDiscoveryInterval | 546 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 547 | ReportInterval | RetransmitInterval | 548 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 549 | SilentInterval | StatisticsTimer | 550 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 551 | WaitDTLS | 552 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 553 Type: 37 for Vendor Specific Payload 555 Length: 34 557 Vendor Identifier: The Vendor Identifier field is assigned by IANA. 559 Element ID: The Element ID field is set to 1 for CAPWAP Protocol 560 Timers. 562 DataChannelKeepAlive: A 16-bit value representing the time, 563 in seconds, that is used by the WTP to determine the next 564 must transmit the Data Channel KeepAlive. (see [I-D.ietf-capwap- 565 protocol-specification]). 567 DataChannelDeadInterval: A 16-bit value representing the minimum 568 time, in seconds, a WTP MUST wait without having received a Data 569 Channel Alive packets may be considered dead. The value of this 570 timer MUST be no less than 2*DataChannelKeepAlive seconds and 571 no greater that 240 seconds (see [I-D.ietf-capwap-protocol- 572 specification]). 574 DiscoveryInterval: A 16-bit value representing the minimum time, in 575 seconds, that a WTP MUST wait after receiving a Discovery Response 576 message, before initiating a DTLS handshake (see [I-D.ietf-capwap- 577 protocol-specification]). 579 DTLSSessionDelete: A 16-bit value representing the minimum time, in 580 seconds, a WTP MUST wait for DTLS session deletion (see [I-D.ietf- 581 capwap-protocol-specification]). 583 EchoInterval: A 16-bit value representing the minimum time, in 584 seconds, between sending Echo Request messages to the AC with 585 which the WTP has joined (see [I-D.ietf-capwap-protocol- 586 specification]). 588 IdleTimeout: A 32-bit value representing the idle timeout value that 589 the WTP SHOULD enforce for its active station. The default Idle 590 Timeout is 300 seconds (see [I-D.ietf-capwap-protocol- 591 specification]). 593 ImageDataStartTimer: A 16-bit value representing the number of 594 seconds the WTP will wait for its peer to transmit the Image 595 Data Request (see [I-D.ietf-capwap-protocol-specification]). 597 MaxDiscoveryInterval: A 16-bit value representing the maximum time 598 allowed between sending Discovery Request messages, in seconds. 599 This value MUST be no less than 2 seconds and no greater than 180 600 seconds (see [I-D.ietf-capwap-protocol-specification]). 602 ReportInterval: A 16-bit value representing the time, in seconds, 603 that is used by the WTP to determine the interval the WTP uses 604 between sending the Decryption Error message elements to inform 605 the AC of decryption errors (see [I-D.ietf-capwap-protocol- 606 specification]). 608 RetransmitInterval: A 16-bit value representing the minimum time, 609 in seconds, in which a non-acknowledged CAPWAP packet will be 610 retransmitted (see [I-D.ietf-capwap-protocol-specification]). 612 SilentInterval: The minimum time, in seconds, a WTP MUST wait before 613 it MAY again send Discovery Request messages or attempt to 614 establish DTLS session (see [I-D.ietf-capwap-protocol- 615 specification]). 617 StatisticsTimer: A 16-bit value representing the time, in seconds, 618 that is used by the WTP to determine the interval the WTP uses 619 between the WTP Events Requests it transmits to the AC to 620 communicate its statistics (see [I-D.ietf-capwap-protocol- 621 specification]). 623 WaitDTLS: A 16-bit value representing the maximum time, in seconds, 624 a WTP MUST wait without having received a DTLS Handshake message 625 from an AC. This timer MUST be greater than 30 seconds (see 626 [I-D.ietf-capwap-protocol-specification]). 628 9.2. CAPWAP Protocol Variables 630 0 1 2 3 631 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 632 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 633 | Vendor Identifier | 634 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 635 | Element ID | MaxDiscoveries | 636 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 637 | MaxFailedDTLSSessionRetry | MaxRetransmit | 638 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 640 Type: 37 for Vendor Specific Payload 642 Length: 12 644 Vendor Identifier: The Vendor Identifier field is assigned by IANA. 646 Element ID: The Element ID field is set to 2 for CAPWAP Protocol 647 Variables. 649 MaxDiscoveries: A 16-bit value representing the maximum number of 650 Discovery Request messages that will be sent after a WTP boots 651 (see [I-D.ietf-capwap-protocol-specification]). 653 MaxFailedDTLSSessionRetry: A 16-bit value representing the maximum 654 number of failed DTLS session establishment attempts before the 655 CAPWAP device enters a silent period (see [I-D.ietf-capwap- 656 protocol-specification]). 658 MaxRetransmit: A 16-bit value representing the maximum number of 659 retransmissions for a given CAPWAP packet before the link layer 660 considers the peer dead (see [I-D.ietf-capwap-protocol- 661 specification]). 663 9.3. CAPWAP Messages for CAPWAP Control Message Extension 665 For CAPWAP Control Message Extension, the following CAPWAP messages 666 will be used. 668 9.3.1. Configuration Status Response Message 670 The following message elements MAY be included in the CAPWAP 671 Configuration Status Response Message. 673 - CAPWAP Protocol Timers, see Section Section 9.1 675 - CAPWAP Protocol Variables, see Section Section 9.2 677 9.3.2. Configuration Update Response Message 679 The following message elements MAY be included in the CAPWAP 680 Configuration Update Response Message. 682 - CAPWAP Protocol Timers, see Section Section 9.1 684 - CAPWAP Protocol Variables, see Section Section 9.2 686 10. Definitions 688 CAPWAP-BASE-MIB DEFINITIONS ::= BEGIN 690 IMPORTS 692 PhysAddress, TEXTUAL-CONVENTION, TruthValue, 693 DateAndTime, RowStatus 694 FROM SNMPv2-TC 695 InterfaceIndex 696 FROM IF-MIB 697 PhysicalIndex 698 FROM ENTITY-MIB 699 SnmpAdminString 700 FROM SNMP-FRAMEWORK-MIB 701 NOTIFICATION-GROUP, OBJECT-GROUP, MODULE-COMPLIANCE 702 FROM SNMPv2-CONF 703 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2, 704 Integer32, Unsigned32, Counter32 705 FROM SNMPv2-SMI 706 InetAddressType, InetAddress 707 FROM INET-ADDRESS-MIB; 709 capwapBaseMIB MODULE-IDENTITY 710 LAST-UPDATED "200811010000Z" -- Nov 01th, 2008 711 ORGANIZATION "IETF Control And Provisioning of Wireless Access 712 Points (CAPWAP) Working Group 713 http://www.ietf.org/html.charters/capwap-charter.html" 714 CONTACT-INFO 715 "General Discussion: capwap@frascone.com 716 To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap 718 Yang Shi 719 H3C, Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian 720 District,Beijing,China(100085) 721 Email: young@h3c.com 723 David T. Perkins 724 228 Bayview Dr 725 San Carlos, CA 94070 726 USA 727 Phone: +1 408 394-8702 728 Email: dperkins@snmpinfo.com 730 Chris Elliott 731 Cisco Systems, Inc. 732 7025 Kit Creek Rd., P.O. Box 14987 733 Research Triangle Park 27709 734 USA 735 Phone: +1 919-392-2146 736 Email: chelliot@cisco.com 738 Yong Zhang 739 Fortinet, Inc. 740 1090 Kifer Road 741 Sunnyvale, CA 94086 742 USA 743 Email: yzhang@fortinet.com" 745 DESCRIPTION 746 "Copyright (C) 2008 The Internet Society. This version of 747 the MIB module is part of RFC xxx; see the RFC itself 748 for full legal notices. 750 This MIB module contains managed object definitions for 751 the CAPWAP Protocol." 752 REVISION "200811010000Z" 753 DESCRIPTION 754 "Initial version published as RFC xxx" 755 ::= { mib-2 xxx } 757 -- Textual Conventions 759 CapwapBaseWtpIdTC ::= TEXTUAL-CONVENTION 760 DISPLAY-HINT "128a" 761 STATUS current 762 DESCRIPTION 763 "Represents an unique identifier of a WTP instance. 764 As usual, a serial number of WTP will be used." 765 SYNTAX OCTET STRING(SIZE(128)) 767 CapwapBaseStationIdTC ::= TEXTUAL-CONVENTION 768 DISPLAY-HINT "1x:" 769 STATUS current 770 DESCRIPTION 771 "Represents an unique identifier of a station instance. 772 As usual, the MAC address of station will be used." 774 SYNTAX OCTET STRING (SIZE (6)) 776 CapwapBaseRadioIdTC ::= TEXTUAL-CONVENTION 777 DISPLAY-HINT "d" 778 STATUS current 779 DESCRIPTION 780 "Represents an unique identifier of a radio on a WTP." 781 SYNTAX Unsigned32 (1..31) 783 CapwapBaseTunnelModeTC ::= TEXTUAL-CONVENTION 784 STATUS current 785 DESCRIPTION 786 "Represents the tunneling modes of operation that are 787 supported by the WTP. 788 The WTP MAY support more than one option, represented by 789 the bit field below. 790 unused(0) - This bit is unused 791 localBridging(1) - Local Bridging Mode, 792 dot3Tunnel(2) - 802.3 Frame Tunnel Mode, 793 nativeTunnel(3) - Native Frame Tunnel Mode." 794 REFERENCE 795 "Section 4.6.42. of CAPWAP Protocol Specification, RFC xxx." 796 SYNTAX BITS { 797 unused(0), 798 localBridging(1), 799 dot3Tunnel(2), 800 nativeTunnel(3) 801 } 803 CapwapBaseMacTypeTC ::= TEXTUAL-CONVENTION 804 STATUS current 805 DESCRIPTION 806 "Represents the MAC mode of operation supported by the WTP. 807 The following enumerated values are supported: 808 localMAC(0) - Local-MAC Mode, 809 splitMAC(1) - Split-MAC Mode, 810 both(2) - Both Local-MAC and Split-MAC." 811 REFERENCE 812 "Section 4.6.43. of CAPWAP Protocol Specification, RFC xxx." 813 SYNTAX INTEGER { 814 localMAC(0), 815 splitMAC(1), 816 both(2) 817 } 819 CapwapBaseChannelTypeTC::= TEXTUAL-CONVENTION 820 STATUS current 821 DESCRIPTION 822 "Represents the channel type for CAPWAP protocol. 823 The following enumerated values are supported: 824 data(1) - data Channel 825 control(2) - control Channel." 826 SYNTAX INTEGER { 827 data(1), 828 control(2) 829 } 831 CapwapBaseAuthenMethodTC ::= TEXTUAL-CONVENTION 832 STATUS current 833 DESCRIPTION 834 "Represents the authentication credential type 835 for WTP. 836 The following enumerated values are supported: 837 other(1) - Other method, for example, vendor specific. 838 clear(2) - Clear text and no authentication, 839 x509(3) - X.509 Certificate authentication, 840 psk(4) - Pre-Shared Secret authentication, 841 As mandatory requirement, CAPWAP control channel 842 authentication should use DTLS, and either by certificate or 843 PSK. For data channel, DTLS is optional." 844 SYNTAX INTEGER { 845 other(1), 846 clear(2), 847 x509(3), 848 psk(4) 849 } 851 -- Top level components of this MIB 853 -- Notifications 854 capwapBaseNotifications OBJECT IDENTIFIER 855 ::= { capwapBaseMIB 0 } 856 -- Tables, Scalars 857 capwapBaseObjects OBJECT IDENTIFIER 858 ::= { capwapBaseMIB 1 } 859 -- Conformance 860 capwapBaseConformance OBJECT IDENTIFIER 861 ::= { capwapBaseMIB 2 } 863 -- AC Objects Group 865 capwapBaseAc OBJECT IDENTIFIER 866 ::= { capwapBaseObjects 1 } 868 capwapBaseWtpSessions OBJECT-TYPE 869 SYNTAX Unsigned32 (0..65535) 870 MAX-ACCESS read-only 871 STATUS current 872 DESCRIPTION 873 "Represents the total number of WTPs which are connecting to 874 AC." 875 REFERENCE 876 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 877 ::= { capwapBaseAc 1 } 879 capwapBaseWtpSessionsLimit OBJECT-TYPE 880 SYNTAX Unsigned32 (0..65535) 881 MAX-ACCESS read-write 882 STATUS current 883 DESCRIPTION 884 "Represents the maximum number of WTP sessions configured for 885 the AC." 886 REFERENCE 887 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 888 ::= { capwapBaseAc 2 } 890 capwapBaseStationSessions OBJECT-TYPE 891 SYNTAX Unsigned32 (0..65535) 892 MAX-ACCESS read-only 893 STATUS current 894 DESCRIPTION 895 "Represents the total number of stations which are accessing 896 the wireless service provided by the AC." 897 REFERENCE 898 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 899 ::= { capwapBaseAc 3 } 901 capwapBaseStationSessionsLimit OBJECT-TYPE 902 SYNTAX Unsigned32 (0..65535) 903 MAX-ACCESS read-write 904 STATUS current 905 DESCRIPTION 906 "Represents the maximum number of station sessions configured 907 for the AC." 908 REFERENCE 909 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 910 ::= { capwapBaseAc 4 } 912 capwapBaseDataChannelSecOptions OBJECT-TYPE 913 SYNTAX BITS { 914 other(0), 915 clear(1), 916 dtls(2) 918 } 919 MAX-ACCESS read-only 920 STATUS current 921 DESCRIPTION 922 "Represents the security policy supported for CAPWAP data 923 channel. 924 The AC MAY support more than one option, represented by the bit 925 field below. 926 other(0) - Other method, for example, vendor specific. 927 clear(1) - Clear Text, 928 dtls(2) - DTLS." 929 REFERENCE 930 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 931 ::= { capwapBaseAc 5 } 933 capwapBaseDataChannelSecConfig OBJECT-TYPE 934 SYNTAX BITS { 935 other(0), 936 clear(1), 937 dtls(2) 938 } 939 MAX-ACCESS read-write 940 STATUS current 941 DESCRIPTION 942 "Represents the security policy configured for the AC for 943 CAPWAP data channel. 944 The configuration is represented by one of the bit 945 fields below. 946 other(0) - Other method, for example, vendor specific. 947 clear(1) - Clear Text, 948 dtls(2) - DTLS." 949 REFERENCE 950 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 951 ::= { capwapBaseAc 6 } 953 capwapBaseControlChannelAuthenOptions OBJECT-TYPE 954 SYNTAX BITS { 955 unused(0), 956 x509(1), 957 psk(2) 958 } 959 MAX-ACCESS read-only 960 STATUS current 961 DESCRIPTION 962 "Represents the authentication credential type supported by the 963 AC for control channel. 964 The AC MAY support more than one option, represented by the bit 965 field below. 967 unused(0) - This bit is unused 968 x509(1) - X.509 Certificate Based 969 psk(2) - Pre-Shared Secret." 970 REFERENCE 971 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 972 ::= { capwapBaseAc 7 } 974 capwapBaseControlChannelAuthenConfig OBJECT-TYPE 975 SYNTAX BITS { 976 unused(0), 977 x509(1), 978 psk(2) 979 } 980 MAX-ACCESS read-write 981 STATUS current 982 DESCRIPTION 983 "Represents the authentication credential type configured for 984 the AC for control channel. 985 The configuration is represented by one of the bit 986 fields below. 987 unused(0) - This bit is unused 988 x509(1) - X.509 Certificate Based 989 psk(2) - Pre-Shared Secret." 990 REFERENCE 991 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 992 ::= { capwapBaseAc 8 } 994 -- capwapBaseAcNameListTable table 996 capwapBaseAcNameListTable OBJECT-TYPE 997 SYNTAX SEQUENCE OF CapwapBaseAcNameListEntry 998 MAX-ACCESS not-accessible 999 STATUS current 1000 DESCRIPTION 1001 "A table of objects that display AC name list." 1002 ::= { capwapBaseAc 9 } 1004 capwapBaseAcNameListEntry OBJECT-TYPE 1005 SYNTAX CapwapBaseAcNameListEntry 1006 MAX-ACCESS not-accessible 1007 STATUS current 1008 DESCRIPTION 1009 "A set of objects that configure AC name list. 1010 Values of all read-create objects in this 1011 table are persistent at restart/reboot." 1012 INDEX { capwapBaseAcNameListId } 1013 ::= { capwapBaseAcNameListTable 1 } 1015 CapwapBaseAcNameListEntry ::= SEQUENCE { 1016 capwapBaseAcNameListId Unsigned32, 1017 capwapBaseAcNameListName OCTET STRING, 1018 capwapBaseAcNameListPriority Unsigned32, 1019 capwapBaseAcNameListRowStatus RowStatus 1020 } 1022 capwapBaseAcNameListId OBJECT-TYPE 1023 SYNTAX Unsigned32 (1..255) 1024 MAX-ACCESS not-accessible 1025 STATUS current 1026 DESCRIPTION 1027 "Represents a unique id for a AC Name list." 1028 ::= { capwapBaseAcNameListEntry 1 } 1030 capwapBaseAcNameListName OBJECT-TYPE 1031 SYNTAX OCTET STRING(SIZE(512)) 1032 MAX-ACCESS read-create 1033 STATUS current 1034 DESCRIPTION 1035 "Represents the name of an AC." 1036 REFERENCE 1037 "Section 4.6.5. of CAPWAP Protocol Specification, RFC xxx." 1038 ::= { capwapBaseAcNameListEntry 2 } 1040 capwapBaseAcNameListPriority OBJECT-TYPE 1041 SYNTAX Unsigned32 (1..255) 1042 MAX-ACCESS read-create 1043 STATUS current 1044 DESCRIPTION 1045 "Represents the priority order of the preferred AC. 1046 For instance, the value of one (1) is used to set the primary 1047 AC, the value of two (2) is used to set the secondary, etc." 1048 REFERENCE 1049 "Section 4.6.5. of CAPWAP Protocol Specification, RFC xxx." 1050 ::= { capwapBaseAcNameListEntry 3 } 1052 capwapBaseAcNameListRowStatus OBJECT-TYPE 1053 SYNTAX RowStatus 1054 MAX-ACCESS read-create 1055 STATUS current 1056 DESCRIPTION 1057 "This variable is used to create, modify, and/or delete a row 1058 in this table." 1059 ::= { capwapBaseAcNameListEntry 4 } 1061 -- End of capwapBaseAcNameListTable table 1062 -- capwapBaseMacAclTable table 1064 capwapBaseMacAclTable OBJECT-TYPE 1065 SYNTAX SEQUENCE OF CapwapBaseMacAclEntry 1066 MAX-ACCESS not-accessible 1067 STATUS current 1068 DESCRIPTION 1069 "A table of objects that configure station Access Control 1070 List (ACL). 1071 WTP will not provide service to the MAC addresses configured 1072 in this table." 1073 ::= { capwapBaseAc 10 } 1075 capwapBaseMacAclEntry OBJECT-TYPE 1076 SYNTAX CapwapBaseMacAclEntry 1077 MAX-ACCESS not-accessible 1078 STATUS current 1079 DESCRIPTION 1080 "A set of objects that configure station Access Control 1081 List (ACL). 1082 Values of all read-create objects in this 1083 table are persistent at AC restart/reboot." 1084 INDEX { capwapBaseMacAclId } 1085 ::= { capwapBaseMacAclTable 1 } 1087 CapwapBaseMacAclEntry ::= SEQUENCE { 1088 capwapBaseMacAclId Unsigned32, 1089 capwapBaseMacAclStationId CapwapBaseStationIdTC, 1090 capwapBaseMacAclRowStatus RowStatus 1091 } 1093 capwapBaseMacAclId OBJECT-TYPE 1094 SYNTAX Unsigned32 1095 MAX-ACCESS not-accessible 1096 STATUS current 1097 DESCRIPTION 1098 "Represents a unique id for a ACL." 1099 ::= { capwapBaseMacAclEntry 1 } 1101 capwapBaseMacAclStationId OBJECT-TYPE 1102 SYNTAX CapwapBaseStationIdTC 1103 MAX-ACCESS read-create 1104 STATUS current 1105 DESCRIPTION 1106 "Represents a station's MAC address which WTPs will no longer 1107 provides service to it." 1108 REFERENCE 1109 "Section 4.6.7. of CAPWAP Protocol Specification, RFC xxx." 1111 ::= { capwapBaseMacAclEntry 2 } 1113 capwapBaseMacAclRowStatus OBJECT-TYPE 1114 SYNTAX RowStatus 1115 MAX-ACCESS read-create 1116 STATUS current 1117 DESCRIPTION 1118 "This variable is used to create, modify, and/or delete a row 1119 in this table." 1120 ::= { capwapBaseMacAclEntry 3 } 1122 -- End of capwapBaseMacAclTable table 1124 -- End of AC Objects Group 1126 -- WTP Objects Group 1128 capwapBaseWtps OBJECT IDENTIFIER 1129 ::= { capwapBaseObjects 2 } 1131 -- capwapBaseWtpStateTable table 1133 capwapBaseWtpStateTable OBJECT-TYPE 1134 SYNTAX SEQUENCE OF CapwapBaseWtpStateEntry 1135 MAX-ACCESS not-accessible 1136 STATUS current 1137 DESCRIPTION 1138 "A table of objects that display WTP CAPWAP FSM state." 1139 ::= { capwapBaseWtps 1 } 1141 capwapBaseWtpStateEntry OBJECT-TYPE 1142 SYNTAX CapwapBaseWtpStateEntry 1143 MAX-ACCESS not-accessible 1144 STATUS current 1145 DESCRIPTION 1146 "A set of objects that display WTP CAPWAP FSM state." 1147 INDEX { capwapBaseWtpId } 1148 ::= { capwapBaseWtpStateTable 1 } 1150 CapwapBaseWtpStateEntry ::= SEQUENCE { 1151 capwapBaseWtpId CapwapBaseWtpIdTC, 1152 capwapBaseWtpIpAddressType InetAddressType, 1153 capwapBaseWtpIpAddress InetAddress, 1154 capwapBaseWtpPhyAddress PhysAddress, 1155 capwapBaseWtpState INTEGER 1156 } 1158 capwapBaseWtpId OBJECT-TYPE 1159 SYNTAX CapwapBaseWtpIdTC 1160 MAX-ACCESS not-accessible 1161 STATUS current 1162 DESCRIPTION 1163 "Represents the unique identifier of a WTP." 1164 ::= { capwapBaseWtpStateEntry 1 } 1166 capwapBaseWtpIpAddressType OBJECT-TYPE 1167 SYNTAX InetAddressType 1168 MAX-ACCESS read-only 1169 STATUS current 1170 DESCRIPTION 1171 "Represents the type of IP address of a WTP." 1172 ::= { capwapBaseWtpStateEntry 2 } 1174 capwapBaseWtpIpAddress OBJECT-TYPE 1175 SYNTAX InetAddress 1176 MAX-ACCESS read-only 1177 STATUS current 1178 DESCRIPTION 1179 "Represents the IP address of a WTP." 1180 ::= { capwapBaseWtpStateEntry 3 } 1182 capwapBaseWtpPhyAddress OBJECT-TYPE 1183 SYNTAX PhysAddress 1184 MAX-ACCESS read-only 1185 STATUS current 1186 DESCRIPTION 1187 "Represents the PHY address of a WTP." 1188 ::= { capwapBaseWtpStateEntry 4 } 1190 capwapBaseWtpState OBJECT-TYPE 1191 SYNTAX INTEGER { 1192 dtls(1), 1193 join(2), 1194 image(3), 1195 configure(4), 1196 dataCheck(5), 1197 run(6), 1198 clear(7), 1199 unknown(8) 1200 } 1201 MAX-ACCESS read-only 1202 STATUS current 1203 DESCRIPTION 1204 "Represents the various possible CAPWAP FSM states of WTP 1205 The following enumerated values are supported: 1207 dtls(1) - DTLS negotiation states, which include 1208 DTLS Setup, Authorize, DTLS Connect. 1209 join(2) - WTP is joining with AC, 1210 image(3) - WTP is downloading software, 1211 configure(4) - WTP is getting configuration from AC, 1212 dataCheck(5) - AC is waiting for the Data Channel Keep 1213 Alive Packet. 1214 run(6) - WTP comes to run state, 1215 clear(7) - WTP recoveries default configuration. 1216 unknown(8) - Operator already prepare configuration 1217 for WTP, while WTP has not contact with AC 1218 till now." 1219 REFERENCE 1220 "Section 2.3.1. of CAPWAP Protocol Specification, RFC xxx." 1221 ::= { capwapBaseWtpStateEntry 5 } 1223 -- End of capwapBaseWtpStateTable Table 1225 -- capwapBaseWtpTable Table 1227 capwapBaseWtpTable OBJECT-TYPE 1228 SYNTAX SEQUENCE OF CapwapBaseWtpEntry 1229 MAX-ACCESS not-accessible 1230 STATUS current 1231 DESCRIPTION 1232 "A table of objects that display and control WTPs in 1233 running state. Values of all read-write objects in this 1234 table are persistent at restart/reboot." 1235 ::= { capwapBaseWtps 2 } 1237 capwapBaseWtpEntry OBJECT-TYPE 1238 SYNTAX CapwapBaseWtpEntry 1239 MAX-ACCESS not-accessible 1240 STATUS current 1241 DESCRIPTION 1242 "A set of objects that display and control a WTP in 1243 running state." 1244 INDEX { capwapBaseWtpCurrId } 1245 ::= { capwapBaseWtpTable 1 } 1247 CapwapBaseWtpEntry ::= SEQUENCE { 1248 capwapBaseWtpCurrId CapwapBaseWtpIdTC, 1249 capwapBaseWtpPhyIndex PhysicalIndex, 1250 capwapBaseWtpName SnmpAdminString, 1251 capwapBaseWtpLocation SnmpAdminString, 1252 capwapBaseWtpBaseMacAddress PhysAddress, 1253 capwapBaseTunnelModeOptions CapwapBaseTunnelModeTC, 1254 capwapBaseMacTypeOptions CapwapBaseMacTypeTC, 1255 capwapBaseWtpDiscoveryType INTEGER, 1256 capwapBaseWtpRadiosInUseNum Unsigned32, 1257 capwapBaseWtpRadioNumLimit Unsigned32, 1258 capwapBaseWtpStaticIpEnable TruthValue, 1259 capwapBaseWtpStaticIpType InetAddressType, 1260 capwapBaseWtpStaticIp InetAddress, 1261 capwapBaseWtpNetmask InetAddress, 1262 capwapBaseWtpGateway InetAddress, 1263 capwapBaseWtpFallbackEnable INTEGER, 1264 capwapBaseWtpRetransmitCount Unsigned32, 1265 capwapBaseWtpMaxDiscoveries Unsigned32, 1266 capwapBaseWtpMaxFailedDTLSSessionRetry Unsigned32, 1267 capwapBaseWtpMaxRetransmitCnt Unsigned32, 1268 capwapBaseWtpDataChannelKeepAliveTimer Unsigned32, 1269 capwapBaseWtpDataChannelDeadInterval Unsigned32, 1270 capwapBaseWtpDiscoveryInterval Unsigned32, 1271 capwapBaseWtpDTLSSessionDeleteTimer Unsigned32, 1272 capwapBaseWtpEchoInterval Unsigned32, 1273 capwapBaseWtpIdleTimeout Unsigned32, 1274 capwapBaseWtpImageDataStartTimer Unsigned32, 1275 capwapBaseWtpMaxDiscoveryInterval Unsigned32, 1276 capwapBaseWtpReportInterval Unsigned32, 1277 capwapBaseWtpRetransmitInterval Unsigned32, 1278 capwapBaseWtpSilentInterval Unsigned32, 1279 capwapBaseWtpStatisticsTimer Unsigned32, 1280 capwapBaseWtpWaitDTLSTimer Unsigned32 1281 } 1283 capwapBaseWtpCurrId OBJECT-TYPE 1284 SYNTAX CapwapBaseWtpIdTC 1285 MAX-ACCESS not-accessible 1286 STATUS current 1287 DESCRIPTION 1288 "Represents the unique identifier of a WTP Which is 1289 in running state." 1290 ::= { capwapBaseWtpEntry 1 } 1292 capwapBaseWtpPhyIndex OBJECT-TYPE 1293 SYNTAX PhysicalIndex 1294 MAX-ACCESS read-only 1295 STATUS current 1296 DESCRIPTION 1297 "Represents the unique physical index of a physical entity 1298 in the ENTITY-MIB. The information such as software version 1299 of specific WTP could be accessed through the index." 1300 ::= { capwapBaseWtpEntry 2 } 1302 capwapBaseWtpName OBJECT-TYPE 1303 SYNTAX SnmpAdminString 1304 MAX-ACCESS read-write 1305 STATUS current 1306 DESCRIPTION 1307 "Represents the name of a WTP." 1308 REFERENCE 1309 "Section 4.6.44. of CAPWAP Protocol Specification, RFC xxx." 1310 ::= { capwapBaseWtpEntry 3 } 1312 capwapBaseWtpLocation OBJECT-TYPE 1313 SYNTAX SnmpAdminString 1314 MAX-ACCESS read-write 1315 STATUS current 1316 DESCRIPTION 1317 "Represents the location of a WTP." 1318 REFERENCE 1319 "Section 4.6.29. of CAPWAP Protocol Specification, RFC xxx." 1320 ::= { capwapBaseWtpEntry 4 } 1322 capwapBaseWtpBaseMacAddress OBJECT-TYPE 1323 SYNTAX PhysAddress 1324 MAX-ACCESS read-only 1325 STATUS current 1326 DESCRIPTION 1327 "Represents the WTP's Base MAC Address, which MAY be assigned 1328 to the primary Ethernet interface." 1329 REFERENCE 1330 "Section 4.6.39. of CAPWAP Protocol Specification, RFC xxx." 1331 ::= { capwapBaseWtpEntry 5 } 1333 capwapBaseTunnelModeOptions OBJECT-TYPE 1334 SYNTAX CapwapBaseTunnelModeTC 1335 MAX-ACCESS read-only 1336 STATUS current 1337 DESCRIPTION 1338 "Represents the tunneling modes of operation supported by 1339 the WTP. 1340 The WTP MAY support more than one option, represented by the 1341 bit field below. 1342 localBridging(1) - Local Bridging Mode, 1343 dot3Tunnel(2) - 802.3 Frame Tunnel Mode, 1344 nativeTunnel(3) - Native Frame Tunnel Mode." 1345 REFERENCE 1346 "Section 4.6.42. of CAPWAP Protocol Specification, RFC xxx." 1347 ::= { capwapBaseWtpEntry 6 } 1349 capwapBaseMacTypeOptions OBJECT-TYPE 1350 SYNTAX CapwapBaseMacTypeTC 1351 MAX-ACCESS read-only 1352 STATUS current 1353 DESCRIPTION 1354 "Represents the MAC mode of operation supported by the WTP. 1355 The following enumerated values are supported: 1356 localMAC(0) - Local-MAC Mode, 1357 splitMAC(1) - Split-MAC Mode, 1358 both(2) - Both Local-MAC Mode and Split-MAC Mode." 1359 REFERENCE 1360 "Section 4.6.43. of CAPWAP Protocol Specification, RFC xxx." 1361 ::= { capwapBaseWtpEntry 7 } 1363 capwapBaseWtpDiscoveryType OBJECT-TYPE 1364 SYNTAX INTEGER { 1365 unknown(0), 1366 staticConfig(1), 1367 dhcp(2), 1368 dns(3), 1369 acRef(4) 1370 } 1371 MAX-ACCESS read-only 1372 STATUS current 1373 DESCRIPTION 1374 "Represents how WTP discovers the AC. 1375 The following enumerated values are supported: 1376 unknown(0) - Unknown, 1377 staticConfig(1) - Static Configuration, 1378 dhcp(2) - DHCP, 1379 dns(3) - DNS, 1380 acRef(4) - AC Referral." 1381 REFERENCE 1382 "Section 4.6.21. of CAPWAP Protocol Specification, RFC xxx." 1383 ::= { capwapBaseWtpEntry 8 } 1385 capwapBaseWtpRadiosInUseNum OBJECT-TYPE 1386 SYNTAX Unsigned32 (0..255) 1387 MAX-ACCESS read-only 1388 STATUS current 1389 DESCRIPTION 1390 "Represents the number of radios in use in the WTP." 1391 REFERENCE 1392 "Section 4.6.40. of CAPWAP Protocol Specification, RFC xxx." 1393 ::= { capwapBaseWtpEntry 9 } 1395 capwapBaseWtpRadioNumLimit OBJECT-TYPE 1396 SYNTAX Unsigned32 (0..255) 1397 MAX-ACCESS read-only 1398 STATUS current 1399 DESCRIPTION 1400 "Represents the maximum radio number supported by the WTP." 1401 REFERENCE 1402 "Section 4.6.40. of CAPWAP Protocol Specification, RFC xxx." 1403 ::= { capwapBaseWtpEntry 10 } 1405 capwapBaseWtpStaticIpEnable OBJECT-TYPE 1406 SYNTAX TruthValue 1407 MAX-ACCESS read-write 1408 STATUS current 1409 DESCRIPTION 1410 "Represents whether the WTP should use a static IP address 1411 or not. A value of false disables the static IP address, 1412 while a value of true enables it." 1413 REFERENCE 1414 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1415 ::= { capwapBaseWtpEntry 11 } 1417 capwapBaseWtpStaticIpType OBJECT-TYPE 1418 SYNTAX InetAddressType 1419 MAX-ACCESS read-write 1420 STATUS current 1421 DESCRIPTION 1422 "Represents whether WTP uses IPV4 or IPV6 static IP address." 1423 ::= { capwapBaseWtpEntry 12 } 1425 capwapBaseWtpStaticIp OBJECT-TYPE 1426 SYNTAX InetAddress 1427 MAX-ACCESS read-write 1428 STATUS current 1429 DESCRIPTION 1430 "When capwapBaseWtpStaticIpEnable is true, it represents the 1431 static IP address to assign to the WTP." 1432 REFERENCE 1433 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1434 ::= { capwapBaseWtpEntry 13 } 1436 capwapBaseWtpNetmask OBJECT-TYPE 1437 SYNTAX InetAddress 1438 MAX-ACCESS read-write 1439 STATUS current 1440 DESCRIPTION 1441 "When capwapBaseWtpStaticIpEnable is true, it represents the 1442 netmask to assign to the WTP." 1443 REFERENCE 1444 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1445 ::= { capwapBaseWtpEntry 14 } 1447 capwapBaseWtpGateway OBJECT-TYPE 1448 SYNTAX InetAddress 1449 MAX-ACCESS read-write 1450 STATUS current 1451 DESCRIPTION 1452 "When capwapBaseWtpStaticIpEnable is true, it represents the 1453 gateway to assign to the WTP." 1454 REFERENCE 1455 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1456 ::= { capwapBaseWtpEntry 15 } 1458 capwapBaseWtpFallbackEnable OBJECT-TYPE 1459 SYNTAX INTEGER { 1460 reserved(0), 1461 enabled(1), 1462 disabled(2) 1463 } 1464 MAX-ACCESS read-write 1465 STATUS current 1466 DESCRIPTION 1467 "Represents whether to enable or disable automatic CAPWAP 1468 fallback in the event that a WTP detects its preferred AC, and 1469 is not currently connected to it. 1470 The following enumerated values are supported: 1471 reserved(0) - The value is reserved, 1472 enabled(1) - The fallback mode is enabled, 1473 disabled(2) - The fallback mode is disabled." 1474 REFERENCE 1475 "Section 4.6.41. of CAPWAP Protocol Specification, RFC xxx." 1476 ::= { capwapBaseWtpEntry 16 } 1478 capwapBaseWtpRetransmitCount OBJECT-TYPE 1479 SYNTAX Unsigned32 1480 MAX-ACCESS read-only 1481 STATUS current 1482 DESCRIPTION 1483 "Represents the number of retransmissions for a given 1484 CAPWAP packet." 1485 REFERENCE 1486 "Section 4.8.8. of CAPWAP Protocol Specification, RFC xxx." 1487 ::= { capwapBaseWtpEntry 17 } 1489 capwapBaseWtpMaxDiscoveries OBJECT-TYPE 1490 SYNTAX Unsigned32 1491 MAX-ACCESS read-only 1492 STATUS current 1493 DESCRIPTION 1494 "Represent the maximum number of Discovery Request messages 1495 that will be sent after a WTP boots." 1496 REFERENCE 1497 "Section 4.8.5. of CAPWAP Protocol Specification, RFC xxx." 1498 DEFVAL { 10 } 1499 ::= { capwapBaseWtpEntry 18 } 1501 capwapBaseWtpMaxFailedDTLSSessionRetry OBJECT-TYPE 1502 SYNTAX Unsigned32 1503 MAX-ACCESS read-only 1504 STATUS current 1505 DESCRIPTION 1506 "Represent the maximum number of failed DTLS session 1507 establishment attempts before the CAPWAP device enters a 1508 silent period." 1509 REFERENCE 1510 "Section 4.8.6. of CAPWAP Protocol Specification, RFC xxx." 1511 DEFVAL { 3 } 1512 ::= { capwapBaseWtpEntry 19 } 1514 capwapBaseWtpMaxRetransmitCnt OBJECT-TYPE 1515 SYNTAX Unsigned32 1516 MAX-ACCESS read-only 1517 STATUS current 1518 DESCRIPTION 1519 "Represent the maximum number of retransmission for a given 1520 CAPWAP packet before the link layer considers the peer dead." 1521 REFERENCE 1522 "Section 4.8.7. of CAPWAP Protocol Specification, RFC xxx." 1523 DEFVAL { 5 } 1524 ::= { capwapBaseWtpEntry 20 } 1526 capwapBaseWtpDataChannelKeepAliveTimer OBJECT-TYPE 1527 SYNTAX Unsigned32 1528 UNITS "second" 1529 MAX-ACCESS read-only 1530 STATUS current 1531 DESCRIPTION 1532 "Represents the the next opportunity, in seconds, the WTP must 1533 transmit the Data Channel KeepAlive message." 1534 REFERENCE 1535 "Section 4.7.2. of CAPWAP Protocol Specification, RFC xxx." 1536 DEFVAL { 30 } 1537 ::= { capwapBaseWtpEntry 21 } 1539 capwapBaseWtpDataChannelDeadInterval OBJECT-TYPE 1540 SYNTAX Unsigned32 1541 UNITS "second" 1542 MAX-ACCESS read-only 1543 STATUS current 1544 DESCRIPTION 1545 "Represents the minimum time, in seconds, a WTP MUST wait 1546 without having received a Data Channel Keep Alive packet 1547 before the destination for the Data Channel Keep Alive 1548 packets may be considered dead." 1549 REFERENCE 1550 "Section 4.7.3. of CAPWAP Protocol Specification, RFC xxx." 1551 DEFVAL { 60 } 1552 ::= { capwapBaseWtpEntry 22 } 1554 capwapBaseWtpDiscoveryInterval OBJECT-TYPE 1555 SYNTAX Unsigned32 1556 UNITS "second" 1557 MAX-ACCESS read-only 1558 STATUS current 1559 DESCRIPTION 1560 "Represents the minimum time, in seconds, that a WTP MUST 1561 wait after receiving a Discovery Response message, before 1562 initiating a DTLS handshake." 1563 REFERENCE 1564 "Section 4.7.5. of CAPWAP Protocol Specification, RFC xxx." 1565 DEFVAL { 5 } 1566 ::= { capwapBaseWtpEntry 23 } 1568 capwapBaseWtpDTLSSessionDeleteTimer OBJECT-TYPE 1569 SYNTAX Unsigned32 1570 UNITS "second" 1571 MAX-ACCESS read-only 1572 STATUS current 1573 DESCRIPTION 1574 "Represents the minimum time, in seconds, a WTP MUST wait 1575 for DTLS session deletion." 1576 REFERENCE 1577 "Section 4.7.6. of CAPWAP Protocol Specification, RFC xxx." 1578 DEFVAL { 5 } 1579 ::= { capwapBaseWtpEntry 24 } 1581 capwapBaseWtpEchoInterval OBJECT-TYPE 1582 SYNTAX Unsigned32 1583 UNITS "second" 1584 MAX-ACCESS read-write 1585 STATUS current 1586 DESCRIPTION 1587 "Represents the minimum time, in seconds, between sending Echo 1588 Request messages to the AC with which the WTP has joined." 1589 REFERENCE 1590 "Section 4.7.7. of CAPWAP Protocol Specification, RFC xxx." 1592 DEFVAL { 30 } 1593 ::= { capwapBaseWtpEntry 25 } 1595 capwapBaseWtpIdleTimeout OBJECT-TYPE 1596 SYNTAX Unsigned32 1597 UNITS "second" 1598 MAX-ACCESS read-write 1599 STATUS current 1600 DESCRIPTION 1601 "Represents the idle timeout value that the WTP SHOULD enforce 1602 for its active stations." 1603 REFERENCE 1604 "Section 4.7.8. of CAPWAP Protocol Specification, RFC xxx." 1605 DEFVAL { 300 } 1606 ::= { capwapBaseWtpEntry 26 } 1608 capwapBaseWtpImageDataStartTimer OBJECT-TYPE 1609 SYNTAX Unsigned32 1610 UNITS "second" 1611 MAX-ACCESS read-only 1612 STATUS current 1613 DESCRIPTION 1614 "Represents the number of seconds the WTP will wait for its peer 1615 to transmit the Image Data Request." 1616 REFERENCE 1617 "Section 4.7.9. of CAPWAP Protocol Specification, RFC xxx." 1618 DEFVAL { 30 } 1619 ::= { capwapBaseWtpEntry 27 } 1621 capwapBaseWtpMaxDiscoveryInterval OBJECT-TYPE 1622 SYNTAX Unsigned32 1623 UNITS "second" 1624 MAX-ACCESS read-write 1625 STATUS current 1626 DESCRIPTION 1627 "Represents the maximum time allowed between sending Discovery 1628 Request messages, in seconds. This value MUST be no less than 1629 2 seconds and no greater than 180 seconds." 1630 REFERENCE 1631 "Section 4.7.10. of CAPWAP Protocol Specification, RFC xxx." 1632 DEFVAL { 20 } 1633 ::= { capwapBaseWtpEntry 28 } 1635 capwapBaseWtpReportInterval OBJECT-TYPE 1636 SYNTAX Unsigned32 1637 UNITS "second" 1638 MAX-ACCESS read-write 1639 STATUS current 1640 DESCRIPTION 1641 "Represents the interval for WTP to send Decryption Error 1642 report." 1643 REFERENCE 1644 "Section 4.7.11. of CAPWAP Protocol Specification, RFC xxx." 1645 DEFVAL { 120 } 1646 ::= { capwapBaseWtpEntry 29 } 1648 capwapBaseWtpRetransmitInterval OBJECT-TYPE 1649 SYNTAX Unsigned32 1650 UNITS "second" 1651 MAX-ACCESS read-only 1652 STATUS current 1653 DESCRIPTION 1654 "Represents the minimum time, in seconds, in which a 1655 non-acknowledged CAPWAP packet will be retransmitted." 1656 REFERENCE 1657 "Section 4.7.12. of CAPWAP Protocol Specification, RFC xxx." 1658 DEFVAL { 3 } 1659 ::= { capwapBaseWtpEntry 30 } 1661 capwapBaseWtpSilentInterval OBJECT-TYPE 1662 SYNTAX Unsigned32 1663 UNITS "second" 1664 MAX-ACCESS read-write 1665 STATUS current 1666 DESCRIPTION 1667 "Represents the minimum time, in seconds, a WTP MUST wait 1668 before it MAY again send Discovery Request messages or attempt 1669 to a establish DTLS session." 1670 REFERENCE 1671 "Section 4.7.13. of CAPWAP Protocol Specification, RFC xxx." 1672 DEFVAL { 30 } 1673 ::= { capwapBaseWtpEntry 31 } 1675 capwapBaseWtpStatisticsTimer OBJECT-TYPE 1676 SYNTAX Unsigned32 1677 UNITS "second" 1678 MAX-ACCESS read-write 1679 STATUS current 1680 DESCRIPTION 1681 "Represents the interval the WTP uses between the WTP Events 1682 Requests it transmits to the AC to communicate its statistics, 1683 in seconds." 1684 REFERENCE 1685 "Section 4.7.14. of CAPWAP Protocol Specification, RFC xxx." 1686 DEFVAL { 120 } 1687 ::= { capwapBaseWtpEntry 32 } 1689 capwapBaseWtpWaitDTLSTimer OBJECT-TYPE 1690 SYNTAX Unsigned32 1691 UNITS "second" 1692 MAX-ACCESS read-write 1693 STATUS current 1694 DESCRIPTION 1695 "Represents the maximum time, in seconds, an AC MUST wait 1696 without having received a DTLS Handshake message from an AC. 1697 This timer MUST be greater than 30 seconds." 1698 REFERENCE 1699 "Section 4.7.15. of CAPWAP Protocol Specification, RFC xxx." 1700 DEFVAL { 60 } 1701 ::= { capwapBaseWtpEntry 33 } 1702 -- End of capwapBaseWtpTable table 1704 -- capwapBaseRadioBindTable Table 1706 capwapBaseRadioBindTable OBJECT-TYPE 1707 SYNTAX SEQUENCE OF CapwapBaseRadioBindEntry 1708 MAX-ACCESS not-accessible 1709 STATUS current 1710 DESCRIPTION 1711 "A table of objects that display the mapping relationship 1712 between specific interface of 'WTP Virtual Radio Interface' 1713 ifType and PHY radio. The mapping relationship in this table 1714 is persistent at restart/reboot." 1715 ::= { capwapBaseWtps 3 } 1717 capwapBaseRadioBindEntry OBJECT-TYPE 1718 SYNTAX CapwapBaseRadioBindEntry 1719 MAX-ACCESS not-accessible 1720 STATUS current 1721 DESCRIPTION 1722 "A set of objects that display the mapping relationship 1723 between 'WTP Virtual Radio' and PHY radio." 1724 INDEX { 1725 capwapBaseWtpId, 1726 capwapBaseRadioId 1727 } 1728 ::= { capwapBaseRadioBindTable 1 } 1730 CapwapBaseRadioBindEntry ::= SEQUENCE { 1731 capwapBaseRadioId CapwapBaseRadioIdTC, 1732 capwapBaseVirtualRadioIfIndex InterfaceIndex, 1733 capwapBaseRadioWirelessBinding INTEGER 1734 } 1736 capwapBaseRadioId OBJECT-TYPE 1737 SYNTAX CapwapBaseRadioIdTC 1738 MAX-ACCESS not-accessible 1739 STATUS current 1740 DESCRIPTION 1741 "Represents the identifier of a PHY radio on a WTP, and only 1742 requires unique on a WTP. 1743 For example, WTP A and WTP B will use same value of 1744 capwapBaseRadioId for their first radio." 1745 REFERENCE 1746 "Section 4.3. of CAPWAP Protocol Specification, RFC xxx." 1747 ::= { capwapBaseRadioBindEntry 1 } 1749 capwapBaseVirtualRadioIfIndex OBJECT-TYPE 1750 SYNTAX InterfaceIndex 1751 MAX-ACCESS read-only 1752 STATUS current 1753 DESCRIPTION 1754 "Represents the index value that uniquely identifies a 1755 'WLAN Virtual Radio Interface'. The interface identified by a 1756 particular value of this index is the same interface as 1757 identified by the same value of ifIndex. 1758 Before WTPs connect to AC and get configuration, operator 1759 will prepare configuration for them. On the AC, there are 1760 interfaces of 'WTP Virtual Radio Interface' ifType which 1761 represent PHY radio interfaces on the WTP. 1762 As most MIBs use ifIndex to identify an interface for 1763 configuration and statistic data, for example, IEEE 802.11 MIB. 1764 It will be very easy to reuse other MIBs such as IEEE 802.11 1765 MIB by 'WTP Virtual Radio Interface'." 1766 ::= { capwapBaseRadioBindEntry 2 } 1768 capwapBaseRadioWirelessBinding OBJECT-TYPE 1769 SYNTAX INTEGER { 1770 reserved0(0), 1771 dot11(1), 1772 reserved2(2), 1773 epc(3) 1774 } 1775 MAX-ACCESS read-only 1776 STATUS current 1777 DESCRIPTION 1778 "Represents the wireless binding type for radio. 1779 The following enumerated values are supported: 1780 reserved0(0) - Reserved, 1781 dot11(1) - IEEE 802.11, 1782 reserved2(2) - Reserved, 1783 epc(3) - EPCGlobal." 1785 REFERENCE 1786 "Section 4.3. of CAPWAP Protocol Specification, RFC xxx." 1787 ::= { capwapBaseRadioBindEntry 3 } 1789 -- End of capwapBaseRadioBindTable Table 1791 -- capwapBaseStationTable Table 1793 capwapBaseStationTable OBJECT-TYPE 1794 SYNTAX SEQUENCE OF CapwapBaseStationEntry 1795 MAX-ACCESS not-accessible 1796 STATUS current 1797 DESCRIPTION 1798 "A table of objects that display stations which are accessing 1799 the wireless service provided by the AC." 1800 ::= { capwapBaseWtps 4 } 1802 capwapBaseStationEntry OBJECT-TYPE 1803 SYNTAX CapwapBaseStationEntry 1804 MAX-ACCESS not-accessible 1805 STATUS current 1806 DESCRIPTION 1807 "A set of objects that display a station which is 1808 associated with the specific radio on the WTP." 1809 INDEX { 1810 capwapBaseWtpCurrId, 1811 capwapBaseRadioId, 1812 capwapBaseStationId 1813 } 1814 ::= { capwapBaseStationTable 1 } 1816 CapwapBaseStationEntry ::= SEQUENCE { 1817 capwapBaseStationId CapwapBaseStationIdTC, 1818 capwapBaseStationAddedTime DateAndTime, 1819 capwapBaseStationVlanName SnmpAdminString 1820 } 1822 capwapBaseStationId OBJECT-TYPE 1823 SYNTAX CapwapBaseStationIdTC 1824 MAX-ACCESS not-accessible 1825 STATUS current 1826 DESCRIPTION 1827 "Represents the unique identifier of the station." 1828 REFERENCE 1829 "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." 1830 ::= { capwapBaseStationEntry 1 } 1832 capwapBaseStationAddedTime OBJECT-TYPE 1833 SYNTAX DateAndTime 1834 MAX-ACCESS read-only 1835 STATUS current 1836 DESCRIPTION 1837 "Represents the time when the station is added." 1838 REFERENCE 1839 "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." 1840 ::= { capwapBaseStationEntry 2 } 1842 capwapBaseStationVlanName OBJECT-TYPE 1843 SYNTAX SnmpAdminString 1844 MAX-ACCESS read-only 1845 STATUS current 1846 DESCRIPTION 1847 "Represents VLAN name to which the station is associated." 1848 REFERENCE 1849 "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." 1850 ::= { capwapBaseStationEntry 3 } 1852 -- End of capwapBaseStationTable Table 1854 -- capwapBaseWtpRebootStatTable 1856 capwapBaseWtpRebootStatsTable OBJECT-TYPE 1857 SYNTAX SEQUENCE OF CapwapBaseWtpRebootStatsEntry 1858 MAX-ACCESS not-accessible 1859 STATUS current 1860 DESCRIPTION 1861 "A table of objects that display WTPs' reboot statistics." 1862 REFERENCE 1863 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1864 ::= { capwapBaseWtps 5 } 1866 capwapBaseWtpRebootStatsEntry OBJECT-TYPE 1867 SYNTAX CapwapBaseWtpRebootStatsEntry 1868 MAX-ACCESS not-accessible 1869 STATUS current 1870 DESCRIPTION 1871 "A set of objects that display the reboot statistic data 1872 of a WTP." 1873 REFERENCE 1874 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1875 INDEX { capwapBaseWtpCurrId } 1876 ::= { capwapBaseWtpRebootStatsTable 1 } 1878 CapwapBaseWtpRebootStatsEntry ::= SEQUENCE { 1879 capwapBaseWtpRebootCount Counter32, 1880 capwapBaseWtpInitCount Counter32, 1881 capwapBaseWtpLinkFailureCount Counter32, 1882 capwapBaseWtpSwFailureCount Counter32, 1883 capwapBaseWtpHwFailureCount Counter32, 1884 capwapBaseWtpOtherFailureCount Counter32, 1885 capwapBaseWtpUnknownFailureCount Counter32, 1886 capwapBaseWtpLastFailureType INTEGER 1887 } 1889 capwapBaseWtpRebootCount OBJECT-TYPE 1890 SYNTAX Counter32 1891 MAX-ACCESS read-only 1892 STATUS current 1893 DESCRIPTION 1894 "Represents the number of reboots that have occurred due to a 1895 WTP crash. A value of 65535 implies that this information is 1896 not available on the WTP." 1897 REFERENCE 1898 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1899 ::= { capwapBaseWtpRebootStatsEntry 1 } 1901 capwapBaseWtpInitCount OBJECT-TYPE 1902 SYNTAX Counter32 1903 MAX-ACCESS read-only 1904 STATUS current 1905 DESCRIPTION 1906 "Represents the number of reboots that have occurred at the 1907 request of a CAPWAP protocol message, such as a change in 1908 configuration that required a reboot or an explicit CAPWAP 1909 protocol reset request. A value of 65535 implies that this 1910 information is not available on the WTP." 1911 REFERENCE 1912 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1913 ::= { capwapBaseWtpRebootStatsEntry 2 } 1915 capwapBaseWtpLinkFailureCount OBJECT-TYPE 1916 SYNTAX Counter32 1917 MAX-ACCESS read-only 1918 STATUS current 1919 DESCRIPTION 1920 "Represents the number of times that a CAPWAP protocol 1921 connection with an AC has failed due to link failure." 1922 REFERENCE 1923 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1924 ::= { capwapBaseWtpRebootStatsEntry 3 } 1926 capwapBaseWtpSwFailureCount OBJECT-TYPE 1927 SYNTAX Counter32 1928 MAX-ACCESS read-only 1929 STATUS current 1930 DESCRIPTION 1931 "Represents the number of times that a CAPWAP protocol 1932 connection with an AC has failed due to software related 1933 reasons." 1934 REFERENCE 1935 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1936 ::= { capwapBaseWtpRebootStatsEntry 4 } 1938 capwapBaseWtpHwFailureCount OBJECT-TYPE 1939 SYNTAX Counter32 1940 MAX-ACCESS read-only 1941 STATUS current 1942 DESCRIPTION 1943 "Represents the number of times that a CAPWAP protocol 1944 connection with an AC has failed due to hardware related 1945 reasons." 1946 REFERENCE 1947 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1948 ::= { capwapBaseWtpRebootStatsEntry 5 } 1950 capwapBaseWtpOtherFailureCount OBJECT-TYPE 1951 SYNTAX Counter32 1952 MAX-ACCESS read-only 1953 STATUS current 1954 DESCRIPTION 1955 "Represents the number of times that a CAPWAP protocol 1956 connection with an AC has failed due to known reasons, other 1957 than AC initiated, link, software or hardware failure." 1958 REFERENCE 1959 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1960 ::= { capwapBaseWtpRebootStatsEntry 6 } 1962 capwapBaseWtpUnknownFailureCount OBJECT-TYPE 1963 SYNTAX Counter32 1964 MAX-ACCESS read-only 1965 STATUS current 1966 DESCRIPTION 1967 "Represents the number of times that a CAPWAP protocol 1968 connection with an AC has failed for unknown reasons." 1969 REFERENCE 1970 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1971 ::= { capwapBaseWtpRebootStatsEntry 7 } 1973 capwapBaseWtpLastFailureType OBJECT-TYPE 1974 SYNTAX INTEGER { 1975 notSupport(0), 1976 acInit(1), 1977 linkFailure(2), 1978 swFailure(3), 1979 hwFailure(4), 1980 otherFailure(5), 1981 unknown(255) 1982 } 1983 MAX-ACCESS read-only 1984 STATUS current 1985 DESCRIPTION 1986 "Represents the failure type of the most recent WTP failure. 1987 The following enumerated values are supported: 1988 notSupport(0) - Not Supported, 1989 acInit(1) - AC Initiated, 1990 linkFailure(2) - Link Failure, 1991 swFailure(3) - Software Failure, 1992 hwFailure(4) - Hardware Failure, 1993 otherFailure(5) - Other Failure, 1994 unknown(255) - Unknown (e.g., WTP doesn't keep track 1995 of info)." 1996 REFERENCE 1997 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1998 ::= { capwapBaseWtpRebootStatsEntry 8 } 2000 -- End of capwapBaseWtpRebootStatsTable table 2002 -- capwapBaseRadioStatsTable table 2004 capwapBaseRadioStatsTable OBJECT-TYPE 2005 SYNTAX SEQUENCE OF CapwapBaseRadioStatsEntry 2006 MAX-ACCESS not-accessible 2007 STATUS current 2008 DESCRIPTION 2009 "A table of objects that display statistics on radios behavior, 2010 and reasons why the WTP radio has been reset." 2011 REFERENCE 2012 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 2013 ::= { capwapBaseWtps 6 } 2015 capwapBaseRadioStatsEntry OBJECT-TYPE 2016 SYNTAX CapwapBaseRadioStatsEntry 2017 MAX-ACCESS not-accessible 2018 STATUS current 2019 DESCRIPTION 2020 "A set of objects that display the statistic data of 2021 events happened on a specific radio of a WTP." 2023 INDEX { capwapBaseWtpCurrId, capwapBaseRadioId } 2024 ::= { capwapBaseRadioStatsTable 1 } 2026 CapwapBaseRadioStatsEntry ::= SEQUENCE { 2027 capwapBaseRadioResetCount Counter32, 2028 capwapBaseRadioSwFailCount Counter32, 2029 capwapBaseRadioHwFailCount Counter32, 2030 capwapBaseRadioOtherFailCount Counter32, 2031 capwapBaseRadioUnknownFailCount Counter32, 2032 capwapBaseRadioConfigUpdateCount Counter32, 2033 capwapBaseRadioChannelChangeCount Counter32, 2034 capwapBaseRadioBandChangeCount Counter32, 2035 capwapBaseRadioCurrentNoiseFloor Integer32, 2036 capwapBaseRadioDecryptErrorCount Counter32, 2037 capwapBaseRadioLastFailType INTEGER 2038 } 2040 capwapBaseRadioResetCount OBJECT-TYPE 2041 SYNTAX Counter32 2042 MAX-ACCESS read-only 2043 STATUS current 2044 DESCRIPTION 2045 "Represents the number of times that that the radio has been 2046 reset." 2047 REFERENCE 2048 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 2049 ::= { capwapBaseRadioStatsEntry 1 } 2051 capwapBaseRadioSwFailCount OBJECT-TYPE 2052 SYNTAX Counter32 2053 MAX-ACCESS read-only 2054 STATUS current 2055 DESCRIPTION 2056 "Represents the number of times that the radio has failed due 2057 to software related reasons." 2058 REFERENCE 2059 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 2060 ::= { capwapBaseRadioStatsEntry 2 } 2062 capwapBaseRadioHwFailCount OBJECT-TYPE 2063 SYNTAX Counter32 2064 MAX-ACCESS read-only 2065 STATUS current 2066 DESCRIPTION 2067 "Represents the number of times that the radio has failed due 2068 to hardware related reasons." 2069 REFERENCE 2070 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 2072 ::= { capwapBaseRadioStatsEntry 3 } 2074 capwapBaseRadioOtherFailCount OBJECT-TYPE 2075 SYNTAX Counter32 2076 MAX-ACCESS read-only 2077 STATUS current 2078 DESCRIPTION 2079 "Represents the number of times that the radio has failed due to 2080 known reasons, other than software or hardware failure." 2081 REFERENCE 2082 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 2083 ::= { capwapBaseRadioStatsEntry 4 } 2085 capwapBaseRadioUnknownFailCount OBJECT-TYPE 2086 SYNTAX Counter32 2087 MAX-ACCESS read-only 2088 STATUS current 2089 DESCRIPTION 2090 "Represents the number of times that the radio has failed for 2091 unknown reasons." 2092 REFERENCE 2093 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 2094 ::= { capwapBaseRadioStatsEntry 5 } 2096 capwapBaseRadioConfigUpdateCount OBJECT-TYPE 2097 SYNTAX Counter32 2098 MAX-ACCESS read-only 2099 STATUS current 2100 DESCRIPTION 2101 "Represents the number of times that the radio configuration has 2102 been updated." 2103 REFERENCE 2104 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 2105 ::= { capwapBaseRadioStatsEntry 6 } 2107 capwapBaseRadioChannelChangeCount OBJECT-TYPE 2108 SYNTAX Counter32 2109 MAX-ACCESS read-only 2110 STATUS current 2111 DESCRIPTION 2112 "Represents the number of times that the radio channel has 2113 been changed." 2114 REFERENCE 2115 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 2116 ::= { capwapBaseRadioStatsEntry 7 } 2118 capwapBaseRadioBandChangeCount OBJECT-TYPE 2119 SYNTAX Counter32 2120 MAX-ACCESS read-only 2121 STATUS current 2122 DESCRIPTION 2123 "Represents the number of times that the radio has changed 2124 frequency bands." 2125 REFERENCE 2126 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 2127 ::= { capwapBaseRadioStatsEntry 8 } 2129 capwapBaseRadioCurrentNoiseFloor OBJECT-TYPE 2130 SYNTAX Integer32 2131 UNITS "dBm" 2132 MAX-ACCESS read-only 2133 STATUS current 2134 DESCRIPTION 2135 "Represents the noise floor of the radio receiver in units of 2136 dBm." 2137 REFERENCE 2138 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 2139 ::= { capwapBaseRadioStatsEntry 9 } 2141 capwapBaseRadioDecryptErrorCount OBJECT-TYPE 2142 SYNTAX Counter32 2143 MAX-ACCESS read-only 2144 STATUS current 2145 DESCRIPTION 2146 "Represents the number of decryption errors that occurred on the 2147 WTP. Note that this field is only valid in cases where the WTP 2148 provides encryption/decryption services." 2149 REFERENCE 2150 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 2151 ::= { capwapBaseRadioStatsEntry 10 } 2153 capwapBaseRadioLastFailType OBJECT-TYPE 2154 SYNTAX INTEGER { 2155 notSupport(0), 2156 swFailure(1), 2157 hwFailure(2), 2158 otherFailure(3), 2159 unknown(255) 2160 } 2161 MAX-ACCESS read-only 2162 STATUS current 2163 DESCRIPTION 2164 "Represents the failure type of the most recent radio failure. 2165 The following enumerated values are supported: 2166 notSupport(0) - Not Supported, 2167 swFailure(1) - Software Failure, 2168 hwFailure(2) - Hardware Failure, 2169 otherFailure(3) - Other Failure, 2170 unknown(255) - Unknown." 2171 REFERENCE 2172 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 2173 ::= { capwapBaseRadioStatsEntry 11 } 2175 -- End of capwapBaseRadioStatsTable table 2176 -- End of WTP Objects Group 2178 -- CAPWAP Base Parameters Group 2180 capwapBaseParameters OBJECT IDENTIFIER 2181 ::= { capwapBaseObjects 3 } 2183 capwapBaseAcMaxRetransmitCnt OBJECT-TYPE 2184 SYNTAX Unsigned32 2185 MAX-ACCESS read-write 2186 STATUS current 2187 DESCRIPTION 2188 "Represent the maximum number of retransmission for a given 2189 CAPWAP packet before the link layer considers the peer dead." 2190 REFERENCE 2191 "Section 4.8.7. of CAPWAP Protocol Specification, RFC xxx." 2192 DEFVAL { 5 } 2193 ::= { capwapBaseParameters 1 } 2195 capwapBaseAcChangeStatePendingTimer OBJECT-TYPE 2196 SYNTAX Unsigned32 2197 UNITS "second" 2198 MAX-ACCESS read-write 2199 STATUS current 2200 DESCRIPTION 2201 "Represents the maximum time, in seconds, the AC will wait 2202 for the Change State Event Request from the WTP after having 2203 transmitted a successful Configuration Status Response 2204 message." 2205 REFERENCE 2206 "Section 4.7.1. of CAPWAP Protocol Specification, RFC xxx." 2207 DEFVAL { 25 } 2208 ::= { capwapBaseParameters 2 } 2210 capwapBaseAcDataCheckTimer OBJECT-TYPE 2211 SYNTAX Unsigned32 2212 UNITS "second" 2213 MAX-ACCESS read-write 2214 STATUS current 2215 DESCRIPTION 2216 "Represents The number of seconds the AC will wait for 2217 the Data Channel Keep Alive, which is required by the 2218 CAPWAP state machine's Data Check state. 2219 The AC resets the state machine if this timer expires 2220 prior to transitioning to the next state." 2221 REFERENCE 2222 "Section 4.7.4. of CAPWAP Protocol Specification, RFC xxx." 2223 DEFVAL { 30 } 2224 ::= { capwapBaseParameters 3 } 2226 capwapBaseAcDTLSSessionDeleteTimer OBJECT-TYPE 2227 SYNTAX Unsigned32 2228 UNITS "second" 2229 MAX-ACCESS read-write 2230 STATUS current 2231 DESCRIPTION 2232 "Represents the minimum time, in seconds, an AC MUST wait 2233 for DTLS session deletion." 2234 REFERENCE 2235 "Section 4.7.6. of CAPWAP Protocol Specification, RFC xxx." 2236 DEFVAL { 5 } 2237 ::= { capwapBaseParameters 4 } 2239 capwapBaseAcEchoInterval OBJECT-TYPE 2240 SYNTAX Unsigned32 2241 UNITS "second" 2242 MAX-ACCESS read-write 2243 STATUS current 2244 DESCRIPTION 2245 "Represents the minimum time, in seconds, between sending Echo 2246 Request messages to the AC with which the WTP has joined." 2247 REFERENCE 2248 "Section 4.7.7. of CAPWAP Protocol Specification, RFC xxx." 2249 DEFVAL { 30 } 2250 ::= { capwapBaseParameters 5 } 2252 capwapBaseAcRetransmitInterval OBJECT-TYPE 2253 SYNTAX Unsigned32 2254 UNITS "second" 2255 MAX-ACCESS read-write 2256 STATUS current 2257 DESCRIPTION 2258 "Represents the minimum time, in seconds, in which a 2259 non-acknowledged CAPWAP packet will be retransmitted." 2260 REFERENCE 2261 "Section 4.7.12. of CAPWAP Protocol Specification, RFC xxx." 2262 DEFVAL { 3 } 2263 ::= { capwapBaseParameters 6 } 2265 capwapBaseAcSilentInterval OBJECT-TYPE 2266 SYNTAX Unsigned32 2267 UNITS "second" 2268 MAX-ACCESS read-write 2269 STATUS current 2270 DESCRIPTION 2271 "Represents the minimum time, in seconds, during which the AC 2272 SHOULD ignore all CAPWAP and DTLS packets received from the 2273 WTP that is in the Sulking state." 2274 REFERENCE 2275 "Section 4.7.13. of CAPWAP Protocol Specification, RFC xxx." 2276 DEFVAL { 30 } 2277 ::= { capwapBaseParameters 7 } 2279 capwapBaseAcWaitDTLSTimer OBJECT-TYPE 2280 SYNTAX Unsigned32 2281 UNITS "second" 2282 MAX-ACCESS read-write 2283 STATUS current 2284 DESCRIPTION 2285 "Represents the maximum time, in seconds, an AC MUST wait 2286 without having received a DTLS Handshake message from an AC. 2287 This timer MUST be greater than 30 seconds." 2288 REFERENCE 2289 "Section 4.7.15. of CAPWAP Protocol Specification, RFC xxx." 2290 DEFVAL { 60 } 2291 ::= { capwapBaseParameters 8 } 2293 capwapBaseAcWaitJoinTimer OBJECT-TYPE 2294 SYNTAX Unsigned32 2295 UNITS "second" 2296 MAX-ACCESS read-write 2297 STATUS current 2298 DESCRIPTION 2299 "Represents the maximum time, in seconds, an AC will wait after 2300 the DTLS session has been established until it receives the 2301 Join Request from the WTP. This timer MUST be greater than 20 2302 seconds." 2303 REFERENCE 2304 "Section 4.7.16. of CAPWAP Protocol Specification, RFC xxx." 2305 DEFVAL { 60 } 2306 ::= { capwapBaseParameters 9 } 2308 -- End of CAPWAP Base Parameters Group 2309 -- CAPWAP Statistics Group 2311 capwapBaseStats OBJECT IDENTIFIER 2312 ::= { capwapBaseObjects 4 } 2314 capwapBaseFailedDTLSAuthFailCount OBJECT-TYPE 2315 SYNTAX Counter32 2316 MAX-ACCESS read-only 2317 STATUS current 2318 DESCRIPTION 2319 "Represents the number of failed DTLS session 2320 establishment attempts due to authentication failures." 2321 REFERENCE 2322 "Section 4.8.3. of CAPWAP Protocol Specification, RFC xxx." 2323 ::= { capwapBaseStats 1 } 2325 capwapBaseFailedDTLSSessionCount OBJECT-TYPE 2326 SYNTAX Counter32 2327 MAX-ACCESS read-only 2328 STATUS current 2329 DESCRIPTION 2330 "Represents the number of failed DTLS session 2331 establishment attempts." 2332 REFERENCE 2333 "Section 4.8.4. of CAPWAP Protocol Specification, RFC xxx." 2334 ::= { capwapBaseStats 2 } 2336 -- Notifications 2338 capwapBaseChannelUp NOTIFICATION-TYPE 2339 OBJECTS { 2340 capwapBaseNtfWtpId, 2341 capwapBaseNtfChannelType, 2342 capwapBaseNtfAuthenMethod 2343 } 2344 STATUS current 2345 DESCRIPTION 2346 "This notification is sent by AC when a CAPWAP channel 2347 established. The notification is separated for data or control 2348 channel." 2349 ::= { capwapBaseNotifications 1 } 2351 capwapBaseChannelDown NOTIFICATION-TYPE 2352 OBJECTS { 2353 capwapBaseNtfWtpId, 2354 capwapBaseNtfChannelType, 2355 capwapBaseNtfChannelDownReason 2356 } 2358 STATUS current 2359 DESCRIPTION 2360 "This notification is sent by AC when CAPWAP channel becomes 2361 down. The notification is separated for data or control 2362 channel." 2363 ::= { capwapBaseNotifications 2 } 2365 capwapBaseDecryptErrorReport NOTIFICATION-TYPE 2366 OBJECTS { 2367 capwapBaseNtfWtpId, 2368 capwapBaseNtfRadioId, 2369 capwapBaseNtfStationIdList 2370 } 2371 STATUS current 2372 DESCRIPTION 2373 "This notification is generated when a WTP that has occurred 2374 decryption error since the last report." 2375 REFERENCE 2376 "Section 4.6.17. of CAPWAP Protocol Specification, RFC xxx." 2377 ::= { capwapBaseNotifications 3 } 2379 capwapBaseJoinFailure NOTIFICATION-TYPE 2380 OBJECTS { 2381 capwapBaseNtfWtpId, 2382 capwapBaseNtfJoinFailureReason 2383 } 2384 STATUS current 2385 DESCRIPTION 2386 "This notification is generated when a WTP fails to join." 2387 REFERENCE 2388 "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." 2389 ::= { capwapBaseNotifications 4 } 2391 capwapBaseImageUpgradeFailure NOTIFICATION-TYPE 2392 OBJECTS { 2393 capwapBaseNtfWtpId, 2394 capwapBaseNtfImageFailureReason 2395 } 2396 STATUS current 2397 DESCRIPTION 2398 "This notification is generated when a WTP fails to update 2399 firmware image." 2400 REFERENCE 2401 "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." 2402 ::= { capwapBaseNotifications 5 } 2404 capwapBaseConfigMsgError NOTIFICATION-TYPE 2405 OBJECTS { 2406 capwapBaseNtfWtpId, 2407 capwapBaseNtfConfigMsgErrorType, 2408 capwapBaseNtfMsgErrorElements 2409 } 2410 STATUS current 2411 DESCRIPTION 2412 "This notification is generated when a WTP received message 2413 elements in the configuration management messages which it was 2414 unable to apply locally." 2415 REFERENCE 2416 "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." 2417 ::= { capwapBaseNotifications 6 } 2419 capwapBaseRadioOperableStatus NOTIFICATION-TYPE 2420 OBJECTS { 2421 capwapBaseNtfWtpId, 2422 capwapBaseNtfRadioId, 2423 capwapBaseNtfRadioOperStatusFlag, 2424 capwapBaseNtfRadioStatusCause 2425 } 2426 STATUS current 2427 DESCRIPTION 2428 "The notification is generated when a radio's operational state 2429 is changed." 2430 REFERENCE 2431 "Section 4.6.33. of CAPWAP Protocol Specification, RFC xxx." 2432 ::= { capwapBaseNotifications 7 } 2434 capwapBaseAuthenticationFailure NOTIFICATION-TYPE 2435 OBJECTS { 2436 capwapBaseNtfWtpId, 2437 capwapBaseNtfChannelType, 2438 capwapBaseNtfAuthenMethod, 2439 capwapBaseNtfAuthenFailureReason 2440 } 2441 STATUS current 2442 DESCRIPTION 2443 "The notification will notify the authentication failure event, 2444 and provides the reason for it." 2445 ::= { capwapBaseNotifications 8 } 2447 -- Objects used only in notifications 2449 -- for notifications 2450 capwapBaseNotifyVarObjects OBJECT IDENTIFIER 2451 ::= { capwapBaseObjects 5 } 2453 capwapBaseNtfWtpId OBJECT-TYPE 2454 SYNTAX CapwapBaseWtpIdTC 2455 MAX-ACCESS accessible-for-notify 2456 STATUS current 2457 DESCRIPTION 2458 "Represents the unique identifier of a WTP." 2459 ::= { capwapBaseNotifyVarObjects 1 } 2461 capwapBaseNtfRadioId OBJECT-TYPE 2462 SYNTAX CapwapBaseRadioIdTC 2463 MAX-ACCESS accessible-for-notify 2464 STATUS current 2465 DESCRIPTION 2466 "Represents the identifier of a PHY radio on a WTP, and only 2467 requires unique on a WTP. 2468 For example, WTP A and WTP B will use same value of 2469 capwapBaseNtfRadioId for their first radio." 2470 REFERENCE 2471 "Section 4.3. of CAPWAP Protocol Specification, RFC xxx." 2472 ::= { capwapBaseNotifyVarObjects 2 } 2474 capwapBaseNtfChannelType OBJECT-TYPE 2475 SYNTAX CapwapBaseChannelTypeTC 2476 MAX-ACCESS accessible-for-notify 2477 STATUS current 2478 DESCRIPTION 2479 "Represents the channel type for CAPWAP protocol." 2480 ::= { capwapBaseNotifyVarObjects 3 } 2482 capwapBaseNtfAuthenMethod OBJECT-TYPE 2483 SYNTAX CapwapBaseAuthenMethodTC 2484 MAX-ACCESS accessible-for-notify 2485 STATUS current 2486 DESCRIPTION 2487 "Represents authentication method for Channel." 2488 ::= { capwapBaseNotifyVarObjects 4 } 2490 capwapBaseNtfChannelDownReason OBJECT-TYPE 2491 SYNTAX INTEGER { 2492 timeout(1), 2493 rekeyfailure(2), 2494 acRebootWtp(3), 2495 dtlsError(4), 2496 maxRetransmit(5) 2497 } 2498 MAX-ACCESS accessible-for-notify 2499 STATUS current 2500 DESCRIPTION 2501 "Represents the reason for Channel down. 2502 The following enumerated values are supported: 2503 timeout(1) - The keep alive is timeout, 2504 rekeyfailure(2) - Rekey process is failed, channel will be 2505 broken. 2506 acRebootWtp(3) - AC reboot WTP. 2507 dtlsError(4) - DTLS notifications: DTLSAborted, 2508 DTLSReassemblyFailure, DTLSPeerDisconnect, 2509 or frequent DTLSDecapFailure. 2510 maxRetransmit(5) - The underlying reliable transport's 2511 RetransmitCount counter has reached the 2512 MaxRetransmit variable" 2513 ::= { capwapBaseNotifyVarObjects 5 } 2515 capwapBaseNtfStationIdList OBJECT-TYPE 2516 SYNTAX OCTET STRING 2517 MAX-ACCESS accessible-for-notify 2518 STATUS current 2519 DESCRIPTION 2520 "Represents the list of station id which use semicolons to 2521 separate each station id." 2522 REFERENCE 2523 "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." 2524 ::= { capwapBaseNotifyVarObjects 6 } 2526 capwapBaseNtfAuthenFailureReason OBJECT-TYPE 2527 SYNTAX INTEGER { 2528 keyMismatch(1), 2529 invalidCA(2), 2530 micError(3), 2531 timeout(4), 2532 unknown(8) 2533 } 2534 MAX-ACCESS accessible-for-notify 2535 STATUS current 2536 DESCRIPTION 2537 "Represents reason for WTP authorization failure. 2538 The following enumerated values are supported: 2539 keyMismatch(1) - WTP's and AC's key is not matched, 2540 invalidCA(2) - ca is not valid, 2541 micError(3) - detect MIC error, 2542 timeout(4) - WaitDTLS Timer is timeout, 2543 unknown(8) - Unknown reason." 2544 REFERENCE 2545 "Section 2.3.1. of CAPWAP Protocol Specification, RFC xxx." 2546 ::= { capwapBaseNotifyVarObjects 7 } 2548 capwapBaseNtfRadioOperStatusFlag OBJECT-TYPE 2549 SYNTAX INTEGER { 2550 reserved(0), 2551 operable(1), 2552 inoperable(2) 2553 } 2554 MAX-ACCESS accessible-for-notify 2555 STATUS current 2556 DESCRIPTION 2557 "Represents the operation status of a radio. 2558 The following enumerated values are supported: 2559 reserved(0) - Reserved 2560 operable(1) - To indicate radio is operable, 2561 inoperable(2) - To indicate radio is inoperable, and 2562 capwapBaseNtfRadioStatusCause object will 2563 give reason in details." 2564 REFERENCE 2565 "Section 4.6.33. of CAPWAP Protocol Specification, RFC xxx." 2566 ::= { capwapBaseNotifyVarObjects 8 } 2568 capwapBaseNtfRadioStatusCause OBJECT-TYPE 2569 SYNTAX INTEGER { 2570 normal(0), 2571 hwError(1), 2572 swError(2), 2573 adminSet(3) 2574 } 2575 MAX-ACCESS accessible-for-notify 2576 STATUS current 2577 DESCRIPTION 2578 "Represents the reason the radio is out of service. 2579 The following enumerated values are supported: 2580 normal(0) - Normal Status, 2581 hwError(1) - Radio Failure, 2582 swError(2) - Software Failure, 2583 adminSet(3) - Administratively Set." 2584 REFERENCE 2585 "Section 4.6.33. of CAPWAP Protocol Specification, RFC xxx." 2586 ::= { capwapBaseNotifyVarObjects 9 } 2588 capwapBaseNtfJoinFailureReason OBJECT-TYPE 2589 SYNTAX INTEGER { 2590 unspecified(1), 2591 resDepletion(2), 2592 unknownSource(3), 2593 incorrectData(4), 2594 sessionIdInUse(5), 2595 notSupportHw(6), 2596 notSupportBinding(7) 2598 } 2599 MAX-ACCESS accessible-for-notify 2600 STATUS current 2601 DESCRIPTION 2602 "Represents the reason of join failure. 2603 The following enumerated values are supported: 2604 unspecified(1) - unspecified failure reason, 2605 resDepletion(2) - Resource Depletion, 2606 unknownSource(3) - Unknown Source, 2607 incorrectData(4) - Incorrect Data, 2608 sessionIdInUse(5) - Session ID already in use, 2609 notSupportHw(6) - WTP Hardware not supported, 2610 notSupportBinding(7) - Binding Not Supported." 2611 REFERENCE 2612 "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." 2613 ::= { capwapBaseNotifyVarObjects 10 } 2615 capwapBaseNtfImageFailureReason OBJECT-TYPE 2616 SYNTAX INTEGER { 2617 invalidChecksum(1), 2618 invalidLength(2), 2619 other(3), 2620 inStorage(4) 2621 } 2622 MAX-ACCESS accessible-for-notify 2623 STATUS current 2624 DESCRIPTION 2625 "Represents the reason of image failure. 2626 The following enumerated values are supported: 2627 invalidChecksum(1) - Invalid Checksum, 2628 invalidLength(2) - Invalid Data Length, 2629 other(3) - Other Error, 2630 inStorage(4) - Image Already Present." 2631 REFERENCE 2632 "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." 2633 ::= { capwapBaseNotifyVarObjects 11 } 2635 capwapBaseNtfConfigMsgErrorType OBJECT-TYPE 2636 SYNTAX INTEGER { 2637 unknownElement(1), 2638 unsupportedElement(2), 2639 unknownValue(3), 2640 unsupportedValue(4) 2641 } 2642 MAX-ACCESS accessible-for-notify 2643 STATUS current 2644 DESCRIPTION 2645 "Represents the type of configuration message error. 2647 The following enumerated values are supported: 2648 unknownElement(1) - Unknown Message Element, 2649 unsupportedElement(2) - Unsupported Message Element, 2650 unknownValue(3) - Unknown Message Element Value, 2651 unsupportedValue(4) - Unsupported Message Element Value." 2652 REFERENCE 2653 "Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx." 2654 ::= { capwapBaseNotifyVarObjects 12 } 2656 capwapBaseNtfMsgErrorElements OBJECT-TYPE 2657 SYNTAX SnmpAdminString 2658 MAX-ACCESS accessible-for-notify 2659 STATUS current 2660 DESCRIPTION 2661 "Represents the message elements sent by the AC in the 2662 Configuration Status Response message that caused the error." 2663 REFERENCE 2664 "Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx." 2665 ::= { capwapBaseNotifyVarObjects 13 } 2667 -- Module compliance 2669 capwapBaseCompliances OBJECT IDENTIFIER 2670 ::= { capwapBaseConformance 1 } 2672 capwapBaseGroups OBJECT IDENTIFIER 2673 ::= { capwapBaseConformance 2 } 2675 capwapBaseCompliance MODULE-COMPLIANCE 2676 STATUS current 2677 DESCRIPTION 2678 "Describes the requirements for conformance to the 2679 CAPWAP-BASE-MIB." 2681 MODULE -- this module 2682 MANDATORY-GROUPS { 2683 capwapBaseAcNodeGroup, 2684 capwapBaseWtpStateGroup, 2685 capwapBaseWtpsGroup, 2686 capwapBaseRadiosGroup, 2687 capwapBaseStationsGroup 2688 } 2690 GROUP capwapBaseAcNodeGroup2 2691 DESCRIPTION 2692 "The capwapBaseAcNodeGroup2 group is optional." 2694 GROUP capwapBaseAcNameListGroup 2695 DESCRIPTION 2696 "The capwapBaseAcNameListGroup group is optional." 2698 GROUP capwapBaseMacAclsGroup 2699 DESCRIPTION 2700 "The capwapBaseMacAclsGroup group is optional." 2702 GROUP capwapBaseWtpsGroup2 2703 DESCRIPTION 2704 "The capwapBaseWtpsGroup2 group is optional." 2706 GROUP capwapBaseWtpRebootStatsGroup 2707 DESCRIPTION 2708 "The capwapBaseWtpRebootStatsGroup group is optional." 2710 GROUP capwapBaseRadioStatsGroup 2711 DESCRIPTION 2712 "The capwapBaseRadioStatsGroup group is optional." 2714 GROUP capwapBaseParametersGroup 2715 DESCRIPTION 2716 "The capwapBaseParametersGroup group is optional." 2718 GROUP capwapBaseStatsGroup 2719 DESCRIPTION 2720 "The capwapBaseStatsGroup group is optional." 2722 GROUP capwapBaseNotificationGroup 2723 DESCRIPTION 2724 "The group capwapBaseNotificationGroup is optional." 2726 GROUP capwapBaseNotifyVarGroup 2727 DESCRIPTION 2728 "The capwapBaseNotifyVarGroup group is optional. 2729 If capwapBaseNotificationGroup is supported, 2730 this group must be implemented." 2732 OBJECT capwapBaseRadioWirelessBinding 2733 SYNTAX INTEGER { reserved0(0), reserved2(2) } 2734 DESCRIPTION 2735 "A value other than reserved0(0), reserved2(2) need not be 2736 supported if there is no wireless binding defined for 2737 technologies used." 2738 ::= { capwapBaseCompliances 1 } 2740 capwapBaseAcNodeGroup OBJECT-GROUP 2741 OBJECTS { 2742 capwapBaseWtpSessions, 2743 capwapBaseWtpSessionsLimit, 2744 capwapBaseStationSessions, 2745 capwapBaseStationSessionsLimit 2746 } 2747 STATUS current 2748 DESCRIPTION 2749 "The collection of objects which are used to represent 2750 basic properties for AC from CAPWAP protocol perspective." 2751 ::= { capwapBaseGroups 1 } 2753 capwapBaseAcNodeGroup2 OBJECT-GROUP 2754 OBJECTS { 2755 capwapBaseDataChannelSecOptions, 2756 capwapBaseDataChannelSecConfig, 2757 capwapBaseControlChannelAuthenOptions, 2758 capwapBaseControlChannelAuthenConfig 2759 } 2760 STATUS current 2761 DESCRIPTION 2762 "The collection of objects which are used to represent 2763 other properties such as security for AC from 2764 CAPWAP protocol perspective." 2765 ::= { capwapBaseGroups 2 } 2767 capwapBaseAcNameListGroup OBJECT-GROUP 2768 OBJECTS { 2769 capwapBaseAcNameListName, 2770 capwapBaseAcNameListPriority, 2771 capwapBaseAcNameListRowStatus 2772 } 2773 STATUS current 2774 DESCRIPTION 2775 "The collection of objects which are used to configure 2776 AC name list." 2777 ::= { capwapBaseGroups 3 } 2779 capwapBaseMacAclsGroup OBJECT-GROUP 2780 OBJECTS { 2781 capwapBaseMacAclStationId, 2782 capwapBaseMacAclRowStatus 2783 } 2784 STATUS current 2785 DESCRIPTION 2786 "The collection of objects which are used to configure 2787 stations ACL." 2788 ::= { capwapBaseGroups 4 } 2790 capwapBaseWtpStateGroup OBJECT-GROUP 2791 OBJECTS { 2792 capwapBaseWtpIpAddressType, 2793 capwapBaseWtpIpAddress, 2794 capwapBaseWtpPhyAddress, 2795 capwapBaseWtpState 2796 } 2797 STATUS current 2798 DESCRIPTION 2799 "The collection of objects which are used to represent 2800 WTP state information." 2801 ::= { capwapBaseGroups 5 } 2803 capwapBaseWtpsGroup OBJECT-GROUP 2804 OBJECTS { 2805 capwapBaseWtpName, 2806 capwapBaseWtpLocation, 2807 capwapBaseWtpBaseMacAddress, 2808 capwapBaseTunnelModeOptions, 2809 capwapBaseMacTypeOptions, 2810 capwapBaseWtpRadiosInUseNum, 2811 capwapBaseWtpRadioNumLimit 2812 } 2813 STATUS current 2814 DESCRIPTION 2815 "The collection of objects which are used to represent 2816 configuration and properties information for WTP 2817 in running state." 2818 ::= { capwapBaseGroups 6 } 2820 capwapBaseWtpsGroup2 OBJECT-GROUP 2821 OBJECTS { 2822 capwapBaseWtpPhyIndex, 2823 capwapBaseWtpDiscoveryType, 2824 capwapBaseWtpStaticIpEnable, 2825 capwapBaseWtpStaticIpType, 2826 capwapBaseWtpStaticIp, 2827 capwapBaseWtpNetmask, 2828 capwapBaseWtpGateway, 2829 capwapBaseWtpFallbackEnable, 2830 capwapBaseWtpRetransmitCount, 2831 capwapBaseWtpMaxDiscoveries, 2832 capwapBaseWtpMaxFailedDTLSSessionRetry, 2833 capwapBaseWtpMaxRetransmitCnt, 2834 capwapBaseWtpDataChannelKeepAliveTimer, 2835 capwapBaseWtpDataChannelDeadInterval, 2836 capwapBaseWtpDiscoveryInterval, 2837 capwapBaseWtpDTLSSessionDeleteTimer, 2838 capwapBaseWtpEchoInterval, 2839 capwapBaseWtpIdleTimeout, 2840 capwapBaseWtpImageDataStartTimer, 2841 capwapBaseWtpMaxDiscoveryInterval, 2842 capwapBaseWtpReportInterval, 2843 capwapBaseWtpRetransmitInterval, 2844 capwapBaseWtpSilentInterval, 2845 capwapBaseWtpStatisticsTimer, 2846 capwapBaseWtpWaitDTLSTimer 2847 } 2848 STATUS current 2849 DESCRIPTION 2850 "The collection of objects which are used to represent 2851 configuration and properties information for WTP 2852 in running state." 2853 ::= { capwapBaseGroups 7 } 2855 capwapBaseRadiosGroup OBJECT-GROUP 2856 OBJECTS { 2857 capwapBaseVirtualRadioIfIndex, 2858 capwapBaseRadioWirelessBinding 2859 } 2860 STATUS current 2861 DESCRIPTION 2862 "The collection of objects which are used to represent 2863 wireless binding type, the mapping relationship between 2864 'WLAN Virtual Radio Interface' and PHY radio." 2865 ::= { capwapBaseGroups 8 } 2867 capwapBaseStationsGroup OBJECT-GROUP 2868 OBJECTS { 2869 capwapBaseStationAddedTime, 2870 capwapBaseStationVlanName 2871 } 2872 STATUS current 2873 DESCRIPTION 2874 "The collection of objects which are used to represent 2875 stations' basic property." 2876 ::= { capwapBaseGroups 9 } 2878 capwapBaseWtpRebootStatsGroup OBJECT-GROUP 2879 OBJECTS { 2880 capwapBaseWtpRebootCount, 2881 capwapBaseWtpInitCount, 2882 capwapBaseWtpLinkFailureCount, 2883 capwapBaseWtpSwFailureCount, 2884 capwapBaseWtpHwFailureCount, 2885 capwapBaseWtpOtherFailureCount, 2886 capwapBaseWtpUnknownFailureCount, 2887 capwapBaseWtpLastFailureType 2888 } 2889 STATUS current 2890 DESCRIPTION 2891 "The collection of objects which are used for collecting 2892 WTP reboot count, link failure count, hardware failure 2893 count and so on." 2894 ::= { capwapBaseGroups 10 } 2896 capwapBaseRadioStatsGroup OBJECT-GROUP 2897 OBJECTS { 2898 capwapBaseRadioResetCount, 2899 capwapBaseRadioSwFailCount, 2900 capwapBaseRadioHwFailCount, 2901 capwapBaseRadioOtherFailCount, 2902 capwapBaseRadioUnknownFailCount, 2903 capwapBaseRadioConfigUpdateCount, 2904 capwapBaseRadioChannelChangeCount, 2905 capwapBaseRadioBandChangeCount, 2906 capwapBaseRadioCurrentNoiseFloor, 2907 capwapBaseRadioDecryptErrorCount, 2908 capwapBaseRadioLastFailType 2909 } 2910 STATUS current 2911 DESCRIPTION 2912 "The collection of objects which are used for collecting 2913 radio reset count, channel change count, hardware failure 2914 count and so on" 2915 ::= { capwapBaseGroups 11 } 2917 capwapBaseParametersGroup OBJECT-GROUP 2918 OBJECTS { 2919 capwapBaseAcMaxRetransmitCnt, 2920 capwapBaseAcChangeStatePendingTimer, 2921 capwapBaseAcDataCheckTimer, 2922 capwapBaseAcDTLSSessionDeleteTimer, 2923 capwapBaseAcEchoInterval, 2924 capwapBaseAcRetransmitInterval, 2925 capwapBaseAcSilentInterval, 2926 capwapBaseAcWaitDTLSTimer, 2927 capwapBaseAcWaitJoinTimer 2928 } 2929 STATUS current 2930 DESCRIPTION 2931 "Objects used for CAPWAP protocol." 2932 ::= { capwapBaseGroups 12 } 2934 capwapBaseStatsGroup OBJECT-GROUP 2935 OBJECTS { 2936 capwapBaseFailedDTLSAuthFailCount, 2937 capwapBaseFailedDTLSSessionCount 2938 } 2939 STATUS current 2940 DESCRIPTION 2941 "Objects used for CAPWAP protocol." 2942 ::= { capwapBaseGroups 13 } 2944 capwapBaseNotificationGroup NOTIFICATION-GROUP 2945 NOTIFICATIONS { 2946 capwapBaseChannelUp, 2947 capwapBaseChannelDown, 2948 capwapBaseDecryptErrorReport, 2949 capwapBaseJoinFailure, 2950 capwapBaseImageUpgradeFailure, 2951 capwapBaseConfigMsgError, 2952 capwapBaseRadioOperableStatus, 2953 capwapBaseAuthenticationFailure 2954 } 2955 STATUS current 2956 DESCRIPTION 2957 "Collection of notifications in this MIB." 2958 ::= { capwapBaseGroups 14 } 2960 capwapBaseNotifyVarGroup OBJECT-GROUP 2961 OBJECTS { 2962 capwapBaseNtfWtpId, 2963 capwapBaseNtfRadioId, 2964 capwapBaseNtfChannelType, 2965 capwapBaseNtfAuthenMethod, 2966 capwapBaseNtfChannelDownReason, 2967 capwapBaseNtfStationIdList, 2968 capwapBaseNtfAuthenFailureReason, 2969 capwapBaseNtfRadioOperStatusFlag, 2970 capwapBaseNtfRadioStatusCause, 2971 capwapBaseNtfJoinFailureReason, 2972 capwapBaseNtfImageFailureReason, 2973 capwapBaseNtfConfigMsgErrorType, 2974 capwapBaseNtfMsgErrorElements 2975 } 2976 STATUS current 2977 DESCRIPTION 2978 "Objects used for notification." 2979 ::= { capwapBaseGroups 15 } 2981 END 2982 11. Security Considerations 2984 There are a number of management objects defined in this MIB module 2985 with a MAX-ACCESS clause of read-write and/or read-create. Such 2986 objects may be considered sensitive or vulnerable in some network 2987 environments. The support for SET operations in a non-secure 2988 environment without proper protection can have a negative effect on 2989 network operations. The followings are the tables and objects and 2990 their sensitivity/vulnerability: 2992 - Unauthorized changes to the capwapBaseWtpTable, writable objects 2993 under capwapBaseAcs group may disrupt allocation of resources in the 2994 network. For example, a WTP's static Ip address could be changed by 2995 set capwapBaseWtpStaticIp object. 2997 - Unauthorized changes to writable objects under the capwapBaseAc 2998 group, it may disrupt allocation of resources in the network. For 2999 example, a invalid value for capwapBaseWtpSessionsLimit object will 3000 increase AC's traffic burden. Also, some objects such as 3001 capwapBaseDataChannelSecConfig may cause network unsafe. 3003 - Unauthorized changes to the capwapBaseMacAclTable, it may cause 3004 legal stations could not access network any more while illegal 3005 stations have chance to access network. 3007 - Unauthorized changes to writable objects under the 3008 capwapBaseParameters group, it may influence CAPWAP protocol 3009 behaviour and status. For example, the invalid value for 3010 capwapBaseAcDataCheckTimer may influence CAPWAP state machine. 3012 Some of the readable objects in this MIB module (i.e., objects with a 3013 MAX-ACCESS other than not-accessible) may be considered sensitive or 3014 vulnerable in some network environments. It is thus important to 3015 control even GET and/or NOTIFY access to these objects and possibly 3016 to even encrypt the values of these objects when sending them over 3017 the network via SNMP. The followings are the tables and objects and 3018 their sensitivity/vulnerability: 3020 - The capwapBaseDataChannelSecOptions and 3021 capwapBaseControlChannelAuthenOptions under the capwapBaseAc group 3022 exposes the current security option for CAPWAP data and control 3023 channel. 3025 - The capwapBaseWtpTable exposes WTP's important information like IP 3026 address, MAC type and so on. 3028 - The capwapBaseWtpRebootStatTable exposes WTP's failure information. 3030 - The capwapBaseRadioStatsTable exposes radio's failure information. 3032 SNMP versions prior to SNMPv3 did not include adequate security. 3033 Even if the network itself is secure (for example by using IPSec), 3034 even then, there is no control as to who on the secure network is 3035 allowed to access and GET/SET (read/change/create/delete) the objects 3036 in this MIB module. 3038 It is RECOMMENDED that implementers consider the security features as 3039 provided by the SNMPv3 framework (see [RFC3410], section 8), 3040 including full support for the SNMPv3 cryptographic mechanisms (for 3041 authentication and privacy). 3043 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3044 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3045 enable cryptographic security. It is then a customer/operator 3046 responsibility to ensure that the SNMP entity giving access to an 3047 instance of this MIB module is properly configured to give access to 3048 the objects only to those principals (users) that have legitimate 3049 rights to indeed GET or SET (change/create/delete) them. 3051 12. IANA Considerations 3053 12.1. IANA Considerations for CAPWAP-BASE-MIB 3055 The MIB module in this document uses the following IANA-assigned 3056 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 3058 Descriptor OBJECT IDENTIFIER value 3059 ---------- ----------------------- 3061 capwapBaseMIB { mib-2 XXX } 3063 12.2. IANA Considerations for ifType 3065 Require IANA to assign a ifType for 'WTP Virtual Radio Interface' 3066 type. 3068 13. Contributors 3070 This MIB is based on contributions from Long Gao. 3072 14. Acknowledgements 3074 The authors wish to thank David Harrington, Yu Liu, Xi Yao, Sachin 3075 Dutta, Ju Wang, Yujin Zhao, Haitao Zhang. 3077 15. References 3078 15.1. Normative References 3080 [RFC2119] Bradner, S., "Key words for 3081 use in RFCs to Indicate 3082 Requirement Levels", 3083 BCP 14, RFC 2119, 3084 March 1997. 3086 [RFC2578] McCloghrie, K., Ed., 3087 Perkins, D., Ed., and J. 3088 Schoenwaelder, Ed., 3089 "Structure of Management 3090 Information Version 2 3091 (SMIv2)", STD 58, RFC 2578, 3092 April 1999. 3094 [RFC2579] McCloghrie, K., Ed., 3095 Perkins, D., Ed., and J. 3096 Schoenwaelder, Ed., 3097 "Textual Conventions for 3098 SMIv2", STD 58, RFC 2579, 3099 April 1999. 3101 [RFC2580] McCloghrie, K., Perkins, 3102 D., and J. Schoenwaelder, 3103 "Conformance Statements for 3104 SMIv2", STD 58, RFC 2580, 3105 April 1999. 3107 [RFC2863] McCloghrie, K. and F. 3108 Kastenholz, "The Interfaces 3109 Group MIB", RFC 2863, 3110 June 2000. 3112 [RFC3418] Presuhn, R., "Management 3113 Information Base (MIB) for 3114 the Simple Network 3115 Management Protocol 3116 (SNMP)", STD 62, RFC 3418, 3117 December 2002. 3119 [RFC4001] Daniele, M., Haberman, B., 3120 Routhier, S., and J. 3121 Schoenwaelder, "Textual 3122 Conventions for Internet 3123 Network Addresses", 3124 RFC 4001, February 2005. 3126 [RFC4133] Bierman, A. and K. 3127 McCloghrie, "Entity MIB 3128 (Version 3)", RFC 4133, 3129 August 2005. 3131 [I-D.ietf-capwap-protocol-specification] Montemurro, M., Stanley, 3132 D., and P. Calhoun, "CAPWAP 3133 Protocol Specification", dr 3134 aft-ietf-capwap-protocol- 3135 specification-14 (work in 3136 progress), October 2008. 3138 15.2. Informative References 3140 [RFC3410] Case, J., Mundy, R., 3141 Partain, D., and B. 3142 Stewart, "Introduction and 3143 Applicability Statements 3144 for Internet-Standard 3145 Management Framework", 3146 RFC 3410, December 2002. 3148 Appendix A. Appendix A. Changes from -02 3150 1) Section 9 is added to describe CAPWAP Message Element Extension 3152 2) In the Section 10, the MIB objects (such as 3153 capwapBaseWtpSilentInterval) are added into capwapBaseWtpTable and 3154 capwapBaseParameters to manage CAPWAP protocol timers and variables. 3155 Rename object capwapBaseMaxStationSessionsConfig as 3156 capwapBaseStationSessionsLimit and capwapBaseMaxWtpSessionsConfig as 3157 capwapBaseWtpSessionsLimit. 3159 3) Section 11 is updated for capwapBaseParameters group, capwapBaseAc 3160 group and capwapBaseMacAclTable to describe the security 3161 considerations for them. 3163 4) Appendix is added to log the changes happened between versions. 3165 Authors' Addresses 3167 Yang Shi (editor) 3168 H3C Tech. Co., Ltd 3169 Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian District, 3170 Beijing 3171 China(100085) 3173 Phone: +86 010 82775276 3174 EMail: young@h3c.com 3176 David Perkins (editor) 3177 SNMPinfo 3178 288 Quailbrook Ct San Carlos, 3179 CA 94070 3180 USA 3182 Phone: +1 408 394-8702 3183 EMail: dperkins@snmpinfo.com 3185 Chris Elliott (editor) 3186 Cisco Systems, Inc. 3187 7025 Kit Creek Rd., P.O. Box 14987 Research Triangle Park 3188 27709 3189 USA 3191 Phone: +1 919-392-2146 3192 EMail: chelliot@cisco.com 3194 Yong Zhang (editor) 3195 Fortinet, Inc. 3196 1090 Kifer Road 3197 Sunnyvale, CA 94086 3198 USA 3200 EMail: yzhang@fortinet.com 3202 Full Copyright Statement 3204 Copyright (C) The IETF Trust (2008). 3206 This document is subject to the rights, licenses and restrictions 3207 contained in BCP 78, and except as set forth therein, the authors 3208 retain all their rights. 3210 This document and the information contained herein are provided on an 3211 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 3212 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 3213 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 3214 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 3215 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 3216 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 3218 Intellectual Property 3220 The IETF takes no position regarding the validity or scope of any 3221 Intellectual Property Rights or other rights that might be claimed to 3222 pertain to the implementation or use of the technology described in 3223 this document or the extent to which any license under such rights 3224 might or might not be available; nor does it represent that it has 3225 made any independent effort to identify any such rights. Information 3226 on the procedures with respect to rights in RFC documents can be 3227 found in BCP 78 and BCP 79. 3229 Copies of IPR disclosures made to the IETF Secretariat and any 3230 assurances of licenses to be made available, or the result of an 3231 attempt made to obtain a general license or permission for the use of 3232 such proprietary rights by implementers or users of this 3233 specification can be obtained from the IETF on-line IPR repository at 3234 http://www.ietf.org/ipr. 3236 The IETF invites any interested party to bring to its attention any 3237 copyrights, patents or patent applications, or other proprietary 3238 rights that may cover technology that may be required to implement 3239 this standard. Please address the information to the IETF at 3240 ietf-ipr@ietf.org.