idnits 2.17.1 draft-ietf-capwap-base-mib-02.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 2745. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2756. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2763. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2769. ** 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 : ---------------------------------------------------------------------------- ** There is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. 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 (October 27, 2008) is 5654 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: 4 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: April 30, 2009 SNMPinfo 6 C. Elliott, Ed. 7 Cisco Systems, Inc. 8 Y. Zhang, Ed. 9 Fortinet, Inc. 10 October 27, 2008 12 CAPWAP Protocol Base MIB 13 draft-ietf-capwap-base-mib-02 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 April 30, 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. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 12 67 10. Security Considerations . . . . . . . . . . . . . . . . . . . 54 68 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 55 69 11.1. IANA Considerations for CAPWAP-BASE-MIB . . . . . . . . . 55 70 11.2. IANA Considerations for ifType . . . . . . . . . . . . . . 55 71 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 55 72 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 56 73 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 56 74 14.1. Normative References . . . . . . . . . . . . . . . . . . . 56 75 14.2. Informative References . . . . . . . . . . . . . . . . . . 57 77 1. Introduction 79 The CAPWAP Protocol [I-D.ietf-capwap-protocol-specification] defines 80 a standard, interoperable protocol, which enables an Access 81 Controller (AC) to manage a collection of Wireless Termination 82 Points(WTPs) 84 This document defines a MIB module that can be used to manage CAPWAP 85 implementations. This MIB module covers both configuration and WTP 86 status-monitoring aspects of CAPWAP, and provides a way to reuse 87 current MIB standards and future extensions for any wireless binding 88 technology. 90 2. The Internet-Standard Management Framework 92 For a detailed overview of the documents that describe the current 93 Internet-Standard Management Framework, please refer to section 7 of 94 RFC 3410 [RFC3410]. 96 Managed objects are accessed via a virtual information store, termed 97 the Management Information Base or MIB. MIB objects are generally 98 accessed through the Simple Network Management Protocol (SNMP). 99 Objects in the MIB are defined using the mechanisms defined in the 100 Structure of Management Information (SMI). This memo specifies a MIB 101 module that is compliant to the SMIv2, which is described in STD 58, 102 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 103 [RFC2580]. 105 3. Terminology 107 This document uses terminology from the document describing the 108 CAPWAP Protocol specification [I-D.ietf-capwap-protocol- 109 specification]. WTPs are viewed as remote RF interfaces controlled 110 by the AC via CAPWAP protocol. The CAPWAP protocol supports two 111 modes of operation: Split and Local MAC. In Split MAC mode all L2 112 wireless data and management frames are encapsulated via the CAPWAP 113 protocol and exchanged between the AC and the WTPs. The Local MAC 114 mode of operation allows for the data frames to be either locally 115 bridged, or tunneled as 802.3 frames. From AC, operator could 116 centrally control WTPs configuration and monitor their status. 117 CAPWAP use DTLS protocol to implement control channel security. 119 4. Conventions 121 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 122 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 123 document are to be interpreted as described in RFC 2119 [RFC2119]. 125 5. Overview 127 The CAPWAP Protocol MIB module (CAPWAP-BASE-MIB) have the following 128 design objectives: 130 - To implement an architecture that uses SNMP for the management and 131 control of wireless networks, answering the operators requirements 132 for centralized management, whatever the deployment or configuration 133 of the network devices (centralized, distributed, or some mix) 135 - To be consistent with CAPWAP protocol 137 - To reuse current MIB standards and future extensions for a wireless 138 binding technology 140 - To enable interoperability between vendors 142 - To meet operator requirements for centralized architectures 144 The basic idea of CAPWAP-BASE-MIB is: 146 - The CAPWAP-BASE-MIB MUST be run on the AC devices and is NOT 147 REQUIRED on the WTP devices. It follows same idea as CAPWAP 148 protocol: Centralized Control 150 - As a generic mechanism, it is independent of any wireless binding 151 technologies and defined by an independent MIB file 153 - To be independent of any wireless binding technologies and have 154 ability to reuse MIB standards of other SDOs, is the main challenge 155 for design of the MIB 157 - ifIndex [RFC2863] will be used as common handler for corresponding 158 interfaces in the CAPWAP-BASE-MIB and specific wireless technologies 159 MIB modules 161 - The operator could manage and control the centralized wireless 162 architectures using multiple MIB standards defined by multiple SDOs, 163 while keeping them loosely coupled 165 It is designed to satisfy the following requirements and constraints: 167 - From AC to centrally manage and monitor WTPs 169 - The MIB module supports CAPWAP protocol parameters queries 171 - The MIB module supports showing WTPs current state 172 - The MIB module provides the information of AC, WTPs, radio and 173 station objects' basic property and their relationship 175 - The MIB module supports indicating the 'WTP Virtual Radio 176 Interface' and PHY radio's mapping relationship 178 - The counters are provided for WTP, radio's reboot event, hardware 179 event failure and so on 181 - The MIB module provides the various notification like channel up, 182 join failure and so on 184 Before coming to details of CAPWAP-BASE-MIB module, it will introduce 185 how CAPWAP-BASE-MIB is able to be independent of any wireless binding 186 technologies and reuse MIB standards of other SDOs. As centralized 187 Wireless architecture, the operator has to prepare configuration on 188 the AC before WTPs connects to AC. For any wireless binding 189 technology, the configuration and management of radio is very 190 important. Under centralized Wireless architecture, according to 191 [I-D.ietf-capwap-protocol-specification], a specific PHY radio could 192 be identified by identifier of a WTP and radio (WTP id + radio id). 193 As usual, the standard of a binding technology provides MIB standard 194 for radio management on its own. For example, according to IEEE 195 802.11 WG MIB standards, the MIB tables such as Dot11OperationTable 196 are able to support WTP radio configuration. These tables use 197 ifIndex as the index, and work well under standalone Wireless 198 architecture. 200 To reuse MIB objects (defined by SDOs such as IEEE) for radio is very 201 important, and the key point is to reuse the idea of ifIndex. So it 202 is required a way to maintain the mapping relationship between 'WTP 203 id + radio id' and 'ifIndex'. As a generic mechanism, ifIndex can 204 identify an interface in abstract way, and it does NOT care for an 205 interface's PHY location (either on the WTP or AC). AC can have 206 interfaces of 'WTP Virtual Radio Interface' ifType, which will 207 logically represent PHY radios on the WTP. It looks like that PHY 208 radios are located on the AC, and PHY location of WTP (radio) is 209 hidden to the operator. Operator can operate radios by MIB tables 210 (such as IEEE 802.11 WG's) with ifIndex of 'WTP Virtual Radio 211 Interface'. As an Abstract interface, 'WTP Virtual Radio Interface' 212 could be used by any wireless binding technology such as IEEE 802.11 213 and 802.16. The table of capwapRadioBindTable will indicate the 214 mapping relationship between 'WTP id + Radio id' and IfIndex. 216 6. Structure of the MIB Module 217 6.1. The capwapBaseObjects Subtree 219 The subtree provides information for statistic data and configuration 220 parameters of WTP and radio. 222 6.2. The capwapBaseConformance Subtree 224 The subtree provides conformance information of MIB objects. 226 6.3. The capwapBaseNotifications Subtree 228 The subtree describes the notifications defined in the MIB module, 229 and their purpose. 231 6.4. Brief Description of MIB Objects 233 The MIB objects were derived from the CAPWAP protocol document 234 [I-D.ietf- capwap-protocol-specification]. 236 1) capwapBaseAcNameListTable 238 The AC name list table is used to configure AC name list. 240 2) capwapBaseMacAclTable 242 The ACL table is used to configure stations' Access Control 243 List(ACL). 245 3) capwapBaseWtpStateTable 247 The WTPs status table is used to indicate each WTP's CAPWAP FSM 248 state. 250 4) capwapBaseWtpTable 252 The WTPs table is used for providing property and configuration 253 information in details for WTPs in running state. 255 5) capwapBaseRadioBindTable 257 The radio bind table is used to indicate the mapping relationship 258 between logical interface of 'WTP Virtual Radio Interface' ifType and 259 PHY radio. 261 6) capwapBaseStationTable 263 The station table is used for providing stations' basic property 264 information. 266 7) capwapBaseWtpRebootStatsTable 268 The WTP reboot statistic table is used for collecting WTP reboot 269 count, link failure count, hardware failure count and so on. 271 8) capwapBaseRadioStatsTable 273 The WTP radio statistic table is used for collecting radio reset 274 count, channel change count, hardware failure count and so on. 276 7. Relationship to Other MIB Modules 278 7.1. Relationship to the SNMPv2-MIB 280 The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being 281 mandatory for all systems, and the objects apply to the entity as a 282 whole. The 'system' group provides identification of the management 283 entity and certain other system-wide data. The CAPWAP-BASE-MIB does 284 not duplicate those objects. 286 7.2. Relationship to the IF-MIB 288 The Interfaces Group [RFC2863] defines generic managed objects for 289 managing interfaces. This memo contains the media-specific 290 extensions to the Interfaces Group for managing WTP radio object that 291 are modeled as interfaces. 293 IF-MIB is required to support on the AC. For each PHY radio on the 294 WTP, it will have a logical interface of 'WTP Virtual Radio 295 Interface' ifType on the AC. 'WTP Virtual Radio Interface' provides 296 a way to configure radio's parameters and query radio's traffic 297 statistics, and reuse the MIBs defined by a specific wireless binding 298 technology. The interface SHOULD be modeled as an ifEntry and 299 provide appropriate interface information. 301 Some specific interpretations of ifTable for CAPWAP-BASE-MIB are as 302 follow. 304 Object Use for the CAPWAP-BASE-MIB. 306 ifIndex Each interface of 'WTP Virtual Radio Interface' 307 ifType maybe be represented by an ifEntry. 309 ifDescr Description of the interface of 'WTP Virtual Radio 310 Interface' ifType. 312 ifType IANAifType of 'WTP Virtual Radio Interface'. 314 ifName Textual name (unique on this system) of the interface 315 or an octet string of zero length. 317 ifAlias The nonvolatile 'alias' name for the interface, as 318 specified by a network manager. 320 ifPhysAddress The physical address of the interface, such as the 321 BSSID of a 802.11 radio. 323 ifAdminStatus This variable indicates the operator's intent as 324 to whether PHY should be enabled, disabled, or 325 running in some diagnostic testing mode on this 326 interface. 327 Also see [RFC2863]. 329 ifOperStatus This value reflects the actual or operational status 330 of radio. 331 Also see [RFC2863]. 333 ifLastChange The value of sysUpTime at the time the interface 334 entered its current operational state. 335 Also see [RFC2863]. 337 ifInOctets The number of received octets over the interface; 338 such as the number of octets received as 802.11 339 frames. 341 ifOutOctets The number of transmitted octets over the interface; 342 such as the number of octets transmitted as 802.11 343 frames. 345 ifInErrors The number of inbound frames dropped due to 346 uncorrectable errors. 348 ifInUnknownProtos 349 The number of received frame discarded during 350 frame header validation, including frames with 351 unrecognized label values. 353 ifOutErrors The number of outbound frames dropped due to 354 uncorrectable errors. 356 7.3. Relationship to the ENTITY-MIB 358 The ENTITY-MIB [RFC4133] meets need for a standardized way of 359 representing a single agent, which supports multiple instances of one 360 MIB. It could express a certain relationship between multiple 361 entities, and provide entity properties for each entity. 363 Under the wireless centralized architectures, the SNMP agent will run 364 on the AC, and not required on the WTP. By the ENTITY-MIB on the AC, 365 it could keep entity information such as firmware revision and 366 software revision of AC and WTPs. From the ENTITY-MIB perspective, 367 the overall physical entity (AC) is a 'compound' of multiple physical 368 entities (WTPs which connects to AC), all entities are identified by 369 Physical index. In the capwapBaseWtpTable of CAPWAP-BASE-MIB, it 370 uses capwapBaseWtpPhyIndex object to keep the mapping relationship of 371 WTP object between CAPWAP-BASE-MIB and ENTITY-MIB. 373 By combining the MIBs, operators could query AC and WTP's status and 374 properties. For example, they could get WTP's current status through 375 CAPWAP-BASE-MIB, and WTP's software revision information through 376 ENTITY-MIB. 378 7.4. Relationship to MIB standards of other SDOs 380 The MIB standards (such as IEEE 802.11 MIB) of a wireless binding is 381 required to support on the AC. The CAPWAP-BASE-MIB module is able to 382 support any wireless binding technology. Through ifIndex of 'WTP 383 Virtual Radio Interface' ifType, it provides consistent and abstract 384 way of reusing MIB objects of a wireless binding technology. 386 7.5. MIB modules required for IMPORTS 388 The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], 389 SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863], INET- 390 ADDRESS-MIB [RFC4001] and ENTITY-MIB [RFC4133]. 392 8. Example of CAPWAP-BASE-MIB Usage 394 With the idea of 'WTP Virtual Radio Interface' in the mind, the 395 usage of MIB will be easily understood. Here takes IEEE 802.11 396 binding technology as an example. 398 1) Identify each PHY radio by 'WTP Virtual Radio Interface' 400 According to [I-D.ietf-capwap-protocol-specification], each radio on 401 a WTP will be identified by a radio Id. Each WTP could be identified 402 by its serial number. 404 When configuration for a WTP is prepared before a WTP connects to AC, 405 the following information is available in the 406 CapwapBaseRadioBindTable. 408 In CapwapBaseRadioBindTable 409 { 410 capwapBaseWtpId = 12345678, 411 capwapBaseRadioId = 1, 412 capwapBaseWtpVirtualRadioifIndex = 10, 413 capwapBaseRadioWirelessBinding = dot11(2) 414 } 416 Suppose WTP's serial number is 12345678, and first radio id is 1. 417 On the AC, the ifIndex of interface in 'WTP Virtual Radio Interface' 418 ifType is 10 which represents the PHY radio 1. 420 By the mechanism of 'WTP Virtual Radio Interface', it seems WTP 421 PHY radios are located on the AC. The interface of 'WTP Virtual 422 Radio Interface' ifType is modeled by ifTable. 424 In ifTable 425 { 426 ifIndex = 10, 427 ifDescr = 'WTP Virtual Radio Interface', 428 ifType = IANAifType of 'WTP Virtual 429 Radio Interface', 430 ifMtu = 0, 431 ifSpeed = 0, 432 ifPhysAddress = 0.0.0.0.0.0, 433 ifAdminStatus = true, 434 ifOperStatus = false, 435 ifLastChange = 0, 436 ifInOctets = 0, 437 ifInUcastPkts = 0, 438 ifInDiscards = 0, 439 ifInErrors = 0, 440 ifInUnknownProtos = 0, 441 ifOutOctets = 0, 442 ifOutUcastPkts = 0, 443 ifOutDiscards = 0, 444 ifOutErrors = 0 445 } 447 2) Configure specific wireless binding parameters for 'WTP Virtual 448 Radio Interface' 449 It will be done on the AC through specific wireless binding MIB 450 such as IEEE 802.11 MIB. 451 For example, to configure parameter for 'WTP Virtual Radio Interface' 452 by 802.11 Dot11OperationTable. 454 In Dot11OperationTable 455 { 456 ifIndex = 10, 457 dot11MACAddress = 0.0.0.0.0.0, 458 dot11RTSThreshold = 2347, 459 dot11ShortRetryLimit = 7, 460 dot11LongRetryLimit = 4, 461 dot11FragmentationThreshold = 256, 462 dot11MaxTransmitMSDULifetime = 512, 463 dot11MaxReceiveLifetime = 512, 464 dot11ManufacturerID = 'capwap', 465 dot11ProductID = 'capwap' 466 } 468 In the example, it suppose ifIndex of an interface in 469 'WTP Virtual Radio Interface' ifType is 10. 471 3) Other configurations for a specific wireless binding 472 For example, WLAN service configuration will be done through CAPWAP 473 binding MIB and IEEE 802.11 MIB. In the CAPWAP 802.11 binding MIB 474 draft, it will give more explain. 476 4) WTP reports its current configuration status 477 After join phase and before WTP get configuration from AC, it will 478 report its current configuration status to AC through configuration 479 status request message. The data of MIB objects will be updated on 480 the AC. For example, for 802.11 binding, WTP will update data in the 481 ifTable and IEEE 802.11 MIB so on according to message content. 482 As an example for ifIndex 10, its ifOperStatus in ifTable will be 483 updated according to current radio operational status in the 484 CAPWAP message. 486 5) Query WTP and radio statistics data 487 After WTPs come to run status, operator could query WTP and 488 radio statistics data through CAPWAP-BASE-MIB and specific binding 489 MIB. For example, through dot11CountersTable in the IEEE 802.11 MIB, 490 operator could query counter data for radio which is identified 491 by ifIndex of a virtual radio interface. With capwapBaseAcState table 492 in the MIB, operator could query configuration and properties of 493 WTPs which are in run status. 495 6) Query other statistics data of a specific wireless binding 496 For example, operator could query the statistics data of 497 WLAN service through 802.11 binding MIB and IEEE 802.11 MIB. 498 In the CAPWAP 802.11 binding MIB draft, it will give more explain. 500 7) Query other properties of WTP 501 Operator could query MIB objects in the ENTITY-MIB by 502 capwapBaseWtpPhyIndex in the capwapBaseWtpTable of CAPWAP-BASE-MIB. 503 The properties of WTP such as software version, hardware version 504 and so on are available in the ENTITY-MIB. 506 9. Definitions 508 CAPWAP-BASE-MIB DEFINITIONS ::= BEGIN 510 IMPORTS 512 PhysAddress, TEXTUAL-CONVENTION, TruthValue, 513 DateAndTime, RowStatus 514 FROM SNMPv2-TC 515 InterfaceIndex 516 FROM IF-MIB 517 PhysicalIndex 518 FROM ENTITY-MIB 519 SnmpAdminString 520 FROM SNMP-FRAMEWORK-MIB 521 NOTIFICATION-GROUP, OBJECT-GROUP, MODULE-COMPLIANCE 522 FROM SNMPv2-CONF 523 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2, 524 Integer32, Unsigned32, Counter32 525 FROM SNMPv2-SMI 526 InetAddressType, InetAddress 527 FROM INET-ADDRESS-MIB; 529 capwapBaseMIB MODULE-IDENTITY 530 LAST-UPDATED "200810270000Z" -- Oct 27th, 2008 531 ORGANIZATION "IETF Control And Provisioning of Wireless Access 532 Points (CAPWAP) Working Group 533 http://www.ietf.org/html.charters/capwap-charter.html" 534 CONTACT-INFO 535 "General Discussion: capwap@frascone.com 536 To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap 538 Yang Shi 539 H3C, Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian 540 District,Beijing,China(100085) 541 Email: young@h3c.com 543 David T. Perkins 544 228 Bayview Dr 545 San Carlos, CA 94070 546 USA 547 Phone: +1 408 394-8702 548 Email: dperkins@snmpinfo.com 550 Chris Elliott 551 Cisco Systems, Inc. 552 7025 Kit Creek Rd., P.O. Box 14987 553 Research Triangle Park 27709 554 USA 555 Phone: +1 919-392-2146 556 Email: chelliot@cisco.com 558 Yong Zhang 559 Fortinet, Inc. 560 1090 Kifer Road 561 Sunnyvale, CA 94086 562 USA 563 Email: yzhang@fortinet.com" 565 DESCRIPTION 566 "Copyright (C) 2008 The Internet Society. This version of 567 the MIB module is part of RFC xxx; see the RFC itself 568 for full legal notices. 570 This MIB module contains managed object definitions for 571 the CAPWAP Protocol." 572 REVISION "200810270000Z" 573 DESCRIPTION 574 "Initial version published as RFC xxx" 575 ::= { mib-2 xxx } 577 -- Textual Conventions 579 CapwapBaseWtpIdTC ::= TEXTUAL-CONVENTION 580 DISPLAY-HINT "128a" 581 STATUS current 582 DESCRIPTION 583 "Represents an unique identifier of a WTP instance. 584 As usual, a serial number of WTP will be used." 585 SYNTAX OCTET STRING(SIZE(128)) 587 CapwapBaseStationIdTC ::= TEXTUAL-CONVENTION 588 DISPLAY-HINT "1x:" 589 STATUS current 590 DESCRIPTION 591 "Represents an unique identifier of a station instance. 592 As usual, the MAC address of station will be used." 593 SYNTAX OCTET STRING (SIZE (6)) 595 CapwapBaseRadioIdTC ::= TEXTUAL-CONVENTION 596 DISPLAY-HINT "d" 597 STATUS current 598 DESCRIPTION 599 "Represents an unique identifier of a radio on a WTP." 600 SYNTAX Unsigned32 (1..31) 602 CapwapBaseTunnelModeTC ::= TEXTUAL-CONVENTION 603 STATUS current 604 DESCRIPTION 605 "Represents the tunneling modes of operation that are 606 supported by the WTP. 607 The WTP MAY support more than one option, represented by 608 the bit field below. 609 unused(0) - This bit is unused 610 localBridging(1) - Local Bridging Mode, 611 dot3Tunnel(2) - 802.3 Frame Tunnel Mode, 612 nativeTunnel(3) - Native Frame Tunnel Mode." 613 REFERENCE 614 "Section 4.6.42. of CAPWAP Protocol Specification, RFC xxx." 615 SYNTAX BITS { 616 unused(0), 617 localBridging(1), 618 dot3Tunnel(2), 619 nativeTunnel(3) 620 } 622 CapwapBaseMacTypeTC ::= TEXTUAL-CONVENTION 623 STATUS current 624 DESCRIPTION 625 "Represents the MAC mode of operation supported by the WTP. 626 The following enumerated values are supported: 627 localMAC(0) - Local-MAC Mode, 628 splitMAC(1) - Split-MAC Mode, 629 both(2) - Both Local-MAC and Split-MAC." 630 REFERENCE 631 "Section 4.6.43. of CAPWAP Protocol Specification, RFC xxx." 632 SYNTAX INTEGER { 633 localMAC(0), 634 splitMAC(1), 635 both(2) 636 } 638 CapwapBaseChannelTypeTC::= TEXTUAL-CONVENTION 639 STATUS current 640 DESCRIPTION 641 "Represents the channel type for CAPWAP protocol. 642 The following enumerated values are supported: 643 data(1) - data Channel 644 control(2) - control Channel." 645 SYNTAX INTEGER { 646 data(1), 647 control(2) 648 } 650 CapwapBaseAuthenMethodTC ::= TEXTUAL-CONVENTION 651 STATUS current 652 DESCRIPTION 653 "Represents the authentication credential type 654 for WTP. 655 The following enumerated values are supported: 656 other(1) - Other method, for example, vendor specific. 657 clear(2) - Clear text and no authentication, 658 x509(3) - X.509 Certificate authentication, 659 psk(4) - Pre-Shared Secret authentication, 660 As mandatory requirement, CAPWAP control channel 661 authentication should use DTLS, and either by certificate or 662 PSK. For data channel, DTLS is optional." 663 SYNTAX INTEGER { 664 other(1), 665 clear(2), 666 x509(3), 667 psk(4) 668 } 670 -- Top level components of this MIB 672 -- Notifications 673 capwapBaseNotifications OBJECT IDENTIFIER 674 ::= { capwapBaseMIB 0 } 675 -- Tables, Scalars 676 capwapBaseObjects OBJECT IDENTIFIER 677 ::= { capwapBaseMIB 1 } 678 -- Conformance 679 capwapBaseConformance OBJECT IDENTIFIER 680 ::= { capwapBaseMIB 2 } 682 -- AC Objects Group 684 capwapBaseAc OBJECT IDENTIFIER 685 ::= { capwapBaseObjects 1 } 687 capwapBaseWtpSessions OBJECT-TYPE 688 SYNTAX Unsigned32 (0..65535) 689 MAX-ACCESS read-only 690 STATUS current 691 DESCRIPTION 692 "Represents the total number of WTPs which are connecting to 693 AC." 694 REFERENCE 695 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 696 ::= { capwapBaseAc 1 } 698 capwapBaseMaxWtpSessionsConfig OBJECT-TYPE 699 SYNTAX Unsigned32 (0..65535) 700 MAX-ACCESS read-write 701 STATUS current 702 DESCRIPTION 703 "Represents the maximum number of WTP sessions configured for 704 the AC." 705 REFERENCE 706 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 707 ::= { capwapBaseAc 2 } 709 capwapBaseStationSessions OBJECT-TYPE 710 SYNTAX Unsigned32 (0..65535) 711 MAX-ACCESS read-only 712 STATUS current 713 DESCRIPTION 714 "Represents the total number of stations which are accessing 715 the wireless service provided by the AC." 716 REFERENCE 717 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 718 ::= { capwapBaseAc 3 } 720 capwapBaseMaxStationSessionsConfig OBJECT-TYPE 721 SYNTAX Unsigned32 (0..65535) 722 MAX-ACCESS read-write 723 STATUS current 724 DESCRIPTION 725 "Represents the maximum number of station sessions configured for 726 the AC." 727 REFERENCE 728 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 729 ::= { capwapBaseAc 4 } 731 capwapBaseDataChannelSecOptions OBJECT-TYPE 732 SYNTAX BITS { 733 other(0), 734 clear(1), 735 dtls(2) 736 } 737 MAX-ACCESS read-only 738 STATUS current 739 DESCRIPTION 740 "Represents the security policy supported for CAPWAP data 741 channel. 742 The AC MAY support more than one option, represented by the bit 743 field below. 744 other(0) - Other method, for example, vendor specific. 745 clear(1) - Clear Text, 746 dtls(2) - DTLS." 747 REFERENCE 748 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 749 ::= { capwapBaseAc 5 } 751 capwapBaseDataChannelSecConfig OBJECT-TYPE 752 SYNTAX BITS { 753 other(0), 754 clear(1), 755 dtls(2) 756 } 757 MAX-ACCESS read-write 758 STATUS current 759 DESCRIPTION 760 "Represents the security policy configured for the AC for 761 CAPWAP data channel. 762 The configuration is represented by one of the bit 763 fields below. 764 other(0) - Other method, for example, vendor specific. 765 clear(1) - Clear Text, 766 dtls(2) - DTLS." 767 REFERENCE 768 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 769 ::= { capwapBaseAc 6 } 771 capwapBaseControlChannelAuthenOptions OBJECT-TYPE 772 SYNTAX BITS { 773 unused(0), 774 x509(1), 775 psk(2) 776 } 777 MAX-ACCESS read-only 778 STATUS current 779 DESCRIPTION 780 "Represents the authentication credential type supported by the 781 AC for control channel. 782 The AC MAY support more than one option, represented by the bit 783 field below. 784 unused(0) - This bit is unused 785 x509(1) - X.509 Certificate Based 786 psk(2) - Pre-Shared Secret." 787 REFERENCE 788 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 789 ::= { capwapBaseAc 7 } 791 capwapBaseControlChannelAuthenConfig OBJECT-TYPE 792 SYNTAX BITS { 793 unused(0), 794 x509(1), 795 psk(2) 796 } 797 MAX-ACCESS read-write 798 STATUS current 799 DESCRIPTION 800 "Represents the authentication credential type configured for 801 the AC for control channel. 802 The configuration is represented by one of the bit 803 fields below. 804 unused(0) - This bit is unused 805 x509(1) - X.509 Certificate Based 806 psk(2) - Pre-Shared Secret." 807 REFERENCE 808 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 809 ::= { capwapBaseAc 8 } 811 -- capwapBaseAcNameListTable table 813 capwapBaseAcNameListTable OBJECT-TYPE 814 SYNTAX SEQUENCE OF CapwapBaseAcNameListEntry 815 MAX-ACCESS not-accessible 816 STATUS current 817 DESCRIPTION 818 "A table of objects that display AC name list." 819 ::= { capwapBaseAc 9 } 821 capwapBaseAcNameListEntry OBJECT-TYPE 822 SYNTAX CapwapBaseAcNameListEntry 823 MAX-ACCESS not-accessible 824 STATUS current 825 DESCRIPTION 826 "A set of objects that configure AC name list. 827 Values of all read-create objects in this 828 table are persistent at restart/reboot." 829 INDEX { capwapBaseAcNameListId } 830 ::= { capwapBaseAcNameListTable 1 } 832 CapwapBaseAcNameListEntry ::= SEQUENCE { 833 capwapBaseAcNameListId Unsigned32, 834 capwapBaseAcNameListName OCTET STRING, 835 capwapBaseAcNameListPriority Unsigned32, 836 capwapBaseAcNameListRowStatus RowStatus 837 } 839 capwapBaseAcNameListId OBJECT-TYPE 840 SYNTAX Unsigned32 (1..255) 841 MAX-ACCESS not-accessible 842 STATUS current 843 DESCRIPTION 844 "Represents a unique id for a AC Name list." 845 ::= { capwapBaseAcNameListEntry 1 } 847 capwapBaseAcNameListName OBJECT-TYPE 848 SYNTAX OCTET STRING(SIZE(512)) 849 MAX-ACCESS read-create 850 STATUS current 851 DESCRIPTION 852 "Represents the name of an AC." 853 REFERENCE 854 "Section 4.6.5. of CAPWAP Protocol Specification, RFC xxx." 855 ::= { capwapBaseAcNameListEntry 2 } 857 capwapBaseAcNameListPriority OBJECT-TYPE 858 SYNTAX Unsigned32 (1..255) 859 MAX-ACCESS read-create 860 STATUS current 861 DESCRIPTION 862 "Represents the priority order of the preferred AC. 863 For instance, the value of one (1) is used to set the primary 864 AC, the value of two (2) is used to set the secondary, etc." 865 REFERENCE 866 "Section 4.6.5. of CAPWAP Protocol Specification, RFC xxx." 867 ::= { capwapBaseAcNameListEntry 3 } 869 capwapBaseAcNameListRowStatus OBJECT-TYPE 870 SYNTAX RowStatus 871 MAX-ACCESS read-create 872 STATUS current 873 DESCRIPTION 874 "This variable is used to create, modify, and/or delete a row 875 in this table." 876 ::= { capwapBaseAcNameListEntry 4 } 878 -- End of capwapBaseAcNameListTable table 880 -- capwapBaseMacAclTable table 882 capwapBaseMacAclTable OBJECT-TYPE 883 SYNTAX SEQUENCE OF CapwapBaseMacAclEntry 884 MAX-ACCESS not-accessible 885 STATUS current 886 DESCRIPTION 887 "A table of objects that configure station Access Control 888 List (ACL). 889 WTP will not provide service to the MAC addresses configured 890 in this table." 891 ::= { capwapBaseAc 10 } 893 capwapBaseMacAclEntry OBJECT-TYPE 894 SYNTAX CapwapBaseMacAclEntry 895 MAX-ACCESS not-accessible 896 STATUS current 897 DESCRIPTION 898 "A set of objects that configure station Access Control 899 List (ACL). 900 Values of all read-create objects in this 901 table are persistent at AC restart/reboot." 902 INDEX { capwapBaseMacAclId } 903 ::= { capwapBaseMacAclTable 1 } 905 CapwapBaseMacAclEntry ::= SEQUENCE { 906 capwapBaseMacAclId Unsigned32, 907 capwapBaseMacAclStationId CapwapBaseStationIdTC, 908 capwapBaseMacAclsRowStatus RowStatus 909 } 911 capwapBaseMacAclId OBJECT-TYPE 912 SYNTAX Unsigned32 (1..255) 913 MAX-ACCESS not-accessible 914 STATUS current 915 DESCRIPTION 916 "Represents a unique id for a ACL." 917 ::= { capwapBaseMacAclEntry 1 } 919 capwapBaseMacAclStationId OBJECT-TYPE 920 SYNTAX CapwapBaseStationIdTC 921 MAX-ACCESS read-create 922 STATUS current 923 DESCRIPTION 924 "Represents a station's MAC address which WTPs will no longer 925 provides service to it." 926 REFERENCE 927 "Section 4.6.7. of CAPWAP Protocol Specification, RFC xxx." 928 ::= { capwapBaseMacAclEntry 2 } 930 capwapBaseMacAclsRowStatus OBJECT-TYPE 931 SYNTAX RowStatus 932 MAX-ACCESS read-create 933 STATUS current 934 DESCRIPTION 935 "This variable is used to create, modify, and/or delete a row 936 in this table." 937 ::= { capwapBaseMacAclEntry 3 } 939 -- End of capwapBaseMacAclTable table 941 -- End of AC Objects Group 943 -- WTP Objects Group 945 capwapBaseWtps OBJECT IDENTIFIER 946 ::= { capwapBaseObjects 2 } 948 -- capwapBaseWtpStateTable table 950 capwapBaseWtpStateTable OBJECT-TYPE 951 SYNTAX SEQUENCE OF CapwapBaseWtpStateEntry 952 MAX-ACCESS not-accessible 953 STATUS current 954 DESCRIPTION 955 "A table of objects that display WTP CAPWAP FSM state." 956 ::= { capwapBaseWtps 1 } 958 capwapBaseWtpStateEntry OBJECT-TYPE 959 SYNTAX CapwapBaseWtpStateEntry 960 MAX-ACCESS not-accessible 961 STATUS current 962 DESCRIPTION 963 "A set of objects that display WTP CAPWAP FSM state." 964 INDEX { capwapBaseWtpId } 965 ::= { capwapBaseWtpStateTable 1 } 967 CapwapBaseWtpStateEntry ::= SEQUENCE { 968 capwapBaseWtpId CapwapBaseWtpIdTC, 969 capwapBaseWtpIpAddressType InetAddressType, 970 capwapBaseWtpIpAddress InetAddress, 971 capwapBaseWtpPhyAddress PhysAddress, 972 capwapBaseWtpState INTEGER 973 } 975 capwapBaseWtpId OBJECT-TYPE 976 SYNTAX CapwapBaseWtpIdTC 977 MAX-ACCESS not-accessible 978 STATUS current 979 DESCRIPTION 980 "Represents the unique identifier of a WTP." 981 ::= { capwapBaseWtpStateEntry 1 } 983 capwapBaseWtpIpAddressType OBJECT-TYPE 984 SYNTAX InetAddressType 985 MAX-ACCESS read-only 986 STATUS current 987 DESCRIPTION 988 "Represents the type of IP address of a WTP." 989 ::= { capwapBaseWtpStateEntry 2 } 991 capwapBaseWtpIpAddress OBJECT-TYPE 992 SYNTAX InetAddress 993 MAX-ACCESS read-only 994 STATUS current 995 DESCRIPTION 996 "Represents the IP address of a WTP." 997 ::= { capwapBaseWtpStateEntry 3 } 999 capwapBaseWtpPhyAddress OBJECT-TYPE 1000 SYNTAX PhysAddress 1001 MAX-ACCESS read-only 1002 STATUS current 1003 DESCRIPTION 1004 "Represents the PHY address of a WTP." 1005 ::= { capwapBaseWtpStateEntry 4 } 1007 capwapBaseWtpState OBJECT-TYPE 1008 SYNTAX INTEGER { 1009 dtls(1), 1010 join(2), 1011 image(3), 1012 configure(4), 1013 dataCheck(5), 1014 run(6), 1015 clear(7), 1016 unknown(8) 1017 } 1018 MAX-ACCESS read-only 1019 STATUS current 1020 DESCRIPTION 1021 "Represents the various possible CAPWAP FSM states of WTP 1022 The following enumerated values are supported: 1023 dtls(1) - DTLS negotiation states, which include 1024 DTLS Setup, Authorize, DTLS Connect. 1025 join(2) - WTP is joining with AC, 1026 image(3) - WTP is downloading software, 1027 configure(4) - WTP is getting configuration from AC, 1028 dataCheck(5) - AC is waiting for the Data Channel Keep 1029 Alive Packet. 1030 run(6) - WTP comes to run state, 1031 clear(7) - WTP recoveries default configuration. 1032 unknown(8) - Operator already prepare configuration 1033 for WTP, while WTP has not contact with AC 1034 till now." 1035 REFERENCE 1036 "Section 2.3.1. of CAPWAP Protocol Specification, RFC xxx." 1037 ::= { capwapBaseWtpStateEntry 5 } 1039 -- End of capwapBaseWtpStateTable Table 1041 -- capwapBaseWtpTable Table 1043 capwapBaseWtpTable OBJECT-TYPE 1044 SYNTAX SEQUENCE OF CapwapBaseWtpEntry 1045 MAX-ACCESS not-accessible 1046 STATUS current 1047 DESCRIPTION 1048 "A table of objects that display and control WTPs in 1049 running state. Values of all read-write objects in this 1050 table are persistent at restart/reboot." 1051 ::= { capwapBaseWtps 2 } 1053 capwapBaseWtpEntry OBJECT-TYPE 1054 SYNTAX CapwapBaseWtpEntry 1055 MAX-ACCESS not-accessible 1056 STATUS current 1057 DESCRIPTION 1058 "A set of objects that display and control a WTP in 1059 running state." 1060 INDEX { capwapBaseWtpCurrId } 1061 ::= { capwapBaseWtpTable 1 } 1063 CapwapBaseWtpEntry ::= SEQUENCE { 1064 capwapBaseWtpCurrId CapwapBaseWtpIdTC, 1065 capwapBaseWtpPhyIndex PhysicalIndex, 1066 capwapBaseWtpName SnmpAdminString, 1067 capwapBaseWtpLocation SnmpAdminString, 1068 capwapBaseWtpBaseMacAddress PhysAddress, 1069 capwapBaseTunnelModeOptions CapwapBaseTunnelModeTC, 1070 capwapBaseMacTypeOptions CapwapBaseMacTypeTC, 1071 capwapBaseWtpDiscoveryType INTEGER, 1072 capwapBaseWtpRadiosInUseNum Unsigned32, 1073 capwapBaseWtpRadioNumLimit Unsigned32, 1074 capwapBaseWtpStaticIpEnable TruthValue, 1075 capwapBaseWtpStaticIpType InetAddressType, 1076 capwapBaseWtpStaticIp InetAddress, 1077 capwapBaseWtpNetmask InetAddress, 1078 capwapBaseWtpGateway InetAddress, 1079 capwapBaseWtpFallbackEnable INTEGER, 1080 capwapBaseWtpRetransmitCount Unsigned32 1082 } 1084 capwapBaseWtpCurrId OBJECT-TYPE 1085 SYNTAX CapwapBaseWtpIdTC 1086 MAX-ACCESS not-accessible 1087 STATUS current 1088 DESCRIPTION 1089 "Represents the unique identifier of a WTP Which is 1090 in running state." 1091 ::= { capwapBaseWtpEntry 1 } 1093 capwapBaseWtpPhyIndex OBJECT-TYPE 1094 SYNTAX PhysicalIndex 1095 MAX-ACCESS read-only 1096 STATUS current 1097 DESCRIPTION 1098 "Represents the unique physical index of a physical entity 1099 in the ENTITY-MIB. The information such as software version 1100 of specific WTP could be accessed through the index." 1101 ::= { capwapBaseWtpEntry 2 } 1103 capwapBaseWtpName OBJECT-TYPE 1104 SYNTAX SnmpAdminString 1105 MAX-ACCESS read-write 1106 STATUS current 1107 DESCRIPTION 1108 "Represents the name of a WTP." 1109 REFERENCE 1110 "Section 4.6.44. of CAPWAP Protocol Specification, RFC xxx." 1111 ::= { capwapBaseWtpEntry 3 } 1113 capwapBaseWtpLocation OBJECT-TYPE 1114 SYNTAX SnmpAdminString 1115 MAX-ACCESS read-write 1116 STATUS current 1117 DESCRIPTION 1118 "Represents the location of a WTP." 1119 REFERENCE 1120 "Section 4.6.29. of CAPWAP Protocol Specification, RFC xxx." 1121 ::= { capwapBaseWtpEntry 4 } 1123 capwapBaseWtpBaseMacAddress OBJECT-TYPE 1124 SYNTAX PhysAddress 1125 MAX-ACCESS read-only 1126 STATUS current 1127 DESCRIPTION 1128 "Represents the WTP's Base MAC Address, which MAY be assigned 1129 to the primary Ethernet interface." 1131 REFERENCE 1132 "Section 4.6.39. of CAPWAP Protocol Specification, RFC xxx." 1133 ::= { capwapBaseWtpEntry 5 } 1135 capwapBaseTunnelModeOptions OBJECT-TYPE 1136 SYNTAX CapwapBaseTunnelModeTC 1137 MAX-ACCESS read-only 1138 STATUS current 1139 DESCRIPTION 1140 "Represents the tunneling modes of operation supported by 1141 the WTP. 1142 The WTP MAY support more than one option, represented by the 1143 bit field below. 1144 localBridging(1) - Local Bridging Mode, 1145 dot3Tunnel(2) - 802.3 Frame Tunnel Mode, 1146 nativeTunnel(3) - Native Frame Tunnel Mode." 1147 REFERENCE 1148 "Section 4.6.42. of CAPWAP Protocol Specification, RFC xxx." 1149 ::= { capwapBaseWtpEntry 6 } 1151 capwapBaseMacTypeOptions OBJECT-TYPE 1152 SYNTAX CapwapBaseMacTypeTC 1153 MAX-ACCESS read-only 1154 STATUS current 1155 DESCRIPTION 1156 "Represents the MAC mode of operation supported by the WTP. 1157 The following enumerated values are supported: 1158 localMAC(0) - Local-MAC Mode, 1159 splitMAC(1) - Split-MAC Mode, 1160 both(2) - Both Local-MAC Mode and Split-MAC Mode." 1161 REFERENCE 1162 "Section 4.6.43. of CAPWAP Protocol Specification, RFC xxx." 1163 ::= { capwapBaseWtpEntry 7 } 1165 capwapBaseWtpDiscoveryType OBJECT-TYPE 1166 SYNTAX INTEGER { 1167 unknown(0), 1168 staticConfig(1), 1169 dhcp(2), 1170 dns(3), 1171 acRef(4) 1172 } 1173 MAX-ACCESS read-only 1174 STATUS current 1175 DESCRIPTION 1176 "Represents how WTP discovers the AC. 1177 The following enumerated values are supported: 1178 unknown(0) - Unknown, 1179 staticConfig(1) - Static Configuration, 1180 dhcp(2) - DHCP, 1181 dns(3) - DNS, 1182 acRef(4) - AC Referral." 1183 REFERENCE 1184 "Section 4.6.21. of CAPWAP Protocol Specification, RFC xxx." 1185 ::= { capwapBaseWtpEntry 8 } 1187 capwapBaseWtpRadiosInUseNum OBJECT-TYPE 1188 SYNTAX Unsigned32 (0..255) 1189 MAX-ACCESS read-only 1190 STATUS current 1191 DESCRIPTION 1192 "Represents the number of radios in use in the WTP." 1193 REFERENCE 1194 "Section 4.6.40. of CAPWAP Protocol Specification, RFC xxx." 1195 ::= { capwapBaseWtpEntry 9 } 1197 capwapBaseWtpRadioNumLimit OBJECT-TYPE 1198 SYNTAX Unsigned32 (0..255) 1199 MAX-ACCESS read-only 1200 STATUS current 1201 DESCRIPTION 1202 "Represents the maximum radio number supported by the WTP." 1203 REFERENCE 1204 "Section 4.6.40. of CAPWAP Protocol Specification, RFC xxx." 1205 ::= { capwapBaseWtpEntry 10 } 1207 capwapBaseWtpStaticIpEnable OBJECT-TYPE 1208 SYNTAX TruthValue 1209 MAX-ACCESS read-write 1210 STATUS current 1211 DESCRIPTION 1212 "Represents whether the WTP should use a static IP address 1213 or not. A value of false disables the static IP address, 1214 while a value of true enables it." 1215 REFERENCE 1216 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1217 ::= { capwapBaseWtpEntry 11 } 1219 capwapBaseWtpStaticIpType OBJECT-TYPE 1220 SYNTAX InetAddressType 1221 MAX-ACCESS read-write 1222 STATUS current 1223 DESCRIPTION 1224 "Represents whether WTP uses IPV4 or IPV6 static IP address." 1225 ::= { capwapBaseWtpEntry 12 } 1227 capwapBaseWtpStaticIp OBJECT-TYPE 1228 SYNTAX InetAddress 1229 MAX-ACCESS read-write 1230 STATUS current 1231 DESCRIPTION 1232 "When capwapBaseWtpStaticIpEnable is true, it represents the 1233 static IP address to assign to the WTP." 1234 REFERENCE 1235 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1236 ::= { capwapBaseWtpEntry 13 } 1238 capwapBaseWtpNetmask OBJECT-TYPE 1239 SYNTAX InetAddress 1240 MAX-ACCESS read-write 1241 STATUS current 1242 DESCRIPTION 1243 "When capwapBaseWtpStaticIpEnable is true, it represents the 1244 netmask to assign to the WTP." 1245 REFERENCE 1246 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1247 ::= { capwapBaseWtpEntry 14 } 1249 capwapBaseWtpGateway OBJECT-TYPE 1250 SYNTAX InetAddress 1251 MAX-ACCESS read-write 1252 STATUS current 1253 DESCRIPTION 1254 "When capwapBaseWtpStaticIpEnable is true, it represents the 1255 gateway to assign to the WTP." 1256 REFERENCE 1257 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1258 ::= { capwapBaseWtpEntry 15 } 1260 capwapBaseWtpFallbackEnable OBJECT-TYPE 1261 SYNTAX INTEGER { 1262 reserved(0), 1263 enabled(1), 1264 disabled(2) 1265 } 1266 MAX-ACCESS read-write 1267 STATUS current 1268 DESCRIPTION 1269 "Represents whether to enable or disable automatic CAPWAP 1270 fallback in the event that a WTP detects its preferred AC, and 1271 is not currently connected to it. 1272 The following enumerated values are supported: 1273 reserved(0) - The value is reserved, 1274 enabled(1) - The fallback mode is enabled, 1275 disabled(2) - The fallback mode is disabled." 1276 REFERENCE 1277 "Section 4.6.41. of CAPWAP Protocol Specification, RFC xxx." 1278 ::= { capwapBaseWtpEntry 16 } 1280 capwapBaseWtpRetransmitCount OBJECT-TYPE 1281 SYNTAX Unsigned32 1282 MAX-ACCESS read-only 1283 STATUS current 1284 DESCRIPTION 1285 "Represents the number of retransmissions for a given 1286 CAPWAP packet." 1287 REFERENCE 1288 "Section 4.8.8. of CAPWAP Protocol Specification, RFC xxx." 1289 ::= { capwapBaseWtpEntry 17 } 1291 -- End of capwapBaseWtpTable table 1293 -- capwapBaseRadioBindTable Table 1295 capwapBaseRadioBindTable OBJECT-TYPE 1296 SYNTAX SEQUENCE OF CapwapBaseRadioBindEntry 1297 MAX-ACCESS not-accessible 1298 STATUS current 1299 DESCRIPTION 1300 "A table of objects that display the mapping relationship 1301 between specific interface of 'WTP Virtual Radio Interface' 1302 ifType and PHY radio. The mapping relationship in this table 1303 is persistent at restart/reboot." 1304 ::= { capwapBaseWtps 3 } 1306 capwapBaseRadioBindEntry OBJECT-TYPE 1307 SYNTAX CapwapBaseRadioBindEntry 1308 MAX-ACCESS not-accessible 1309 STATUS current 1310 DESCRIPTION 1311 "A set of objects that display the mapping relationship 1312 between 'WTP Virtual Radio' and PHY radio." 1313 INDEX { 1314 capwapBaseWtpId, 1315 capwapBaseRadioId 1316 } 1317 ::= { capwapBaseRadioBindTable 1 } 1319 CapwapBaseRadioBindEntry ::= SEQUENCE { 1320 capwapBaseRadioId CapwapBaseRadioIdTC, 1321 capwapBaseVirtualRadioIfIndex InterfaceIndex, 1322 capwapBaseRadioWirelessBinding INTEGER 1323 } 1325 capwapBaseRadioId OBJECT-TYPE 1326 SYNTAX CapwapBaseRadioIdTC 1327 MAX-ACCESS not-accessible 1328 STATUS current 1329 DESCRIPTION 1330 "Represents the identifier of a PHY radio on a WTP, and only 1331 requires unique on a WTP. 1332 For example, WTP A and WTP B will use same value of 1333 capwapBaseRadioId for their first radio." 1334 REFERENCE 1335 "Section 4.3. of CAPWAP Protocol Specification, RFC xxx." 1336 ::= { capwapBaseRadioBindEntry 1 } 1338 capwapBaseVirtualRadioIfIndex OBJECT-TYPE 1339 SYNTAX InterfaceIndex 1340 MAX-ACCESS read-only 1341 STATUS current 1342 DESCRIPTION 1343 "Represents the index value that uniquely identifies a 1344 'WLAN Virtual Radio Interface'. The interface identified by a 1345 particular value of this index is the same interface as 1346 identified by the same value of ifIndex. 1347 Before WTPs connect to AC and get configuration, operator 1348 will prepare configuration for them. On the AC, there are 1349 interfaces of 'WTP Virtual Radio Interface' ifType which 1350 represent PHY radio interfaces on the WTP. 1351 As most MIBs use ifIndex to identify an interface for 1352 configuration and statistic data, for example, IEEE 802.11 MIB. 1353 It will be very easy to reuse other MIBs such as IEEE 802.11 1354 MIB by 'WTP Virtual Radio Interface'." 1355 ::= { capwapBaseRadioBindEntry 2 } 1357 capwapBaseRadioWirelessBinding OBJECT-TYPE 1358 SYNTAX INTEGER { 1359 reserved0(0), 1360 dot11(1), 1361 reserved2(2), 1362 epc(3) 1363 } 1364 MAX-ACCESS read-only 1365 STATUS current 1366 DESCRIPTION 1367 "Represents the wireless binding type for radio. 1368 The following enumerated values are supported: 1369 reserved0(0) - Reserved, 1370 dot11(1) - IEEE 802.11, 1371 reserved2(2) - Reserved, 1372 epc(3) - EPCGlobal." 1373 REFERENCE 1374 "Section 4.3. of CAPWAP Protocol Specification, RFC xxx." 1375 ::= { capwapBaseRadioBindEntry 3 } 1377 -- End of capwapBaseRadioBindTable Table 1379 -- capwapBaseStationTable Table 1381 capwapBaseStationTable OBJECT-TYPE 1382 SYNTAX SEQUENCE OF CapwapBaseStationEntry 1383 MAX-ACCESS not-accessible 1384 STATUS current 1385 DESCRIPTION 1386 "A table of objects that display stations which are accessing 1387 the wireless service provided by the AC." 1388 ::= { capwapBaseWtps 4 } 1390 capwapBaseStationEntry OBJECT-TYPE 1391 SYNTAX CapwapBaseStationEntry 1392 MAX-ACCESS not-accessible 1393 STATUS current 1394 DESCRIPTION 1395 "A set of objects that display a station which is 1396 associated with the specific radio on the WTP." 1397 INDEX { 1398 capwapBaseWtpCurrId, 1399 capwapBaseRadioId, 1400 capwapBaseStationId 1401 } 1402 ::= { capwapBaseStationTable 1 } 1404 CapwapBaseStationEntry ::= SEQUENCE { 1405 capwapBaseStationId CapwapBaseStationIdTC, 1406 capwapBaseStationAddedTime DateAndTime, 1407 capwapBaseStationVlanName SnmpAdminString 1408 } 1410 capwapBaseStationId OBJECT-TYPE 1411 SYNTAX CapwapBaseStationIdTC 1412 MAX-ACCESS not-accessible 1413 STATUS current 1414 DESCRIPTION 1415 "Represents the unique identifier of the station." 1416 REFERENCE 1417 "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." 1418 ::= { capwapBaseStationEntry 1 } 1420 capwapBaseStationAddedTime OBJECT-TYPE 1421 SYNTAX DateAndTime 1422 MAX-ACCESS read-only 1423 STATUS current 1424 DESCRIPTION 1425 "Represents the time when the station is added." 1426 REFERENCE 1427 "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." 1428 ::= { capwapBaseStationEntry 2 } 1430 capwapBaseStationVlanName OBJECT-TYPE 1431 SYNTAX SnmpAdminString 1432 MAX-ACCESS read-only 1433 STATUS current 1434 DESCRIPTION 1435 "Represents VLAN name to which the station is associated." 1436 REFERENCE 1437 "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." 1438 ::= { capwapBaseStationEntry 3 } 1440 -- End of capwapBaseStationTable Table 1442 -- capwapBaseWtpRebootStatTable 1444 capwapBaseWtpRebootStatsTable OBJECT-TYPE 1445 SYNTAX SEQUENCE OF CapwapBaseWtpRebootStatsEntry 1446 MAX-ACCESS not-accessible 1447 STATUS current 1448 DESCRIPTION 1449 "A table of objects that display WTPs' reboot statistics." 1450 REFERENCE 1451 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1452 ::= { capwapBaseWtps 5 } 1454 capwapBaseWtpRebootStatsEntry OBJECT-TYPE 1455 SYNTAX CapwapBaseWtpRebootStatsEntry 1456 MAX-ACCESS not-accessible 1457 STATUS current 1458 DESCRIPTION 1459 "A set of objects that display the reboot statistic data 1460 of a WTP." 1461 REFERENCE 1462 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1463 INDEX { capwapBaseWtpCurrId } 1464 ::= { capwapBaseWtpRebootStatsTable 1 } 1466 CapwapBaseWtpRebootStatsEntry ::= SEQUENCE { 1467 capwapBaseWtpRebootCount Counter32, 1468 capwapBaseWtpInitCount Counter32, 1469 capwapBaseWtpLinkFailureCount Counter32, 1470 capwapBaseWtpSwFailureCount Counter32, 1471 capwapBaseWtpHwFailureCount Counter32, 1472 capwapBaseWtpOtherFailureCount Counter32, 1473 capwapBaseWtpUnknownFailureCount Counter32, 1474 capwapBaseWtpLastFailureType INTEGER 1475 } 1477 capwapBaseWtpRebootCount OBJECT-TYPE 1478 SYNTAX Counter32 1479 MAX-ACCESS read-only 1480 STATUS current 1481 DESCRIPTION 1482 "Represents the number of reboots that have occurred due to a 1483 WTP crash. A value of 65535 implies that this information is 1484 not available on the WTP." 1485 REFERENCE 1486 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1487 ::= { capwapBaseWtpRebootStatsEntry 1 } 1489 capwapBaseWtpInitCount OBJECT-TYPE 1490 SYNTAX Counter32 1491 MAX-ACCESS read-only 1492 STATUS current 1493 DESCRIPTION 1494 "Represents the number of reboots that have occurred at the 1495 request of a CAPWAP protocol message, such as a change in 1496 configuration that required a reboot or an explicit CAPWAP 1497 protocol reset request. A value of 65535 implies that this 1498 information is not available on the WTP." 1499 REFERENCE 1500 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1501 ::= { capwapBaseWtpRebootStatsEntry 2 } 1503 capwapBaseWtpLinkFailureCount OBJECT-TYPE 1504 SYNTAX Counter32 1505 MAX-ACCESS read-only 1506 STATUS current 1507 DESCRIPTION 1508 "Represents the number of times that a CAPWAP protocol 1509 connection with an AC has failed due to link failure." 1510 REFERENCE 1511 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1513 ::= { capwapBaseWtpRebootStatsEntry 3 } 1515 capwapBaseWtpSwFailureCount OBJECT-TYPE 1516 SYNTAX Counter32 1517 MAX-ACCESS read-only 1518 STATUS current 1519 DESCRIPTION 1520 "Represents the number of times that a CAPWAP protocol 1521 connection with an AC has failed due to software related 1522 reasons." 1523 REFERENCE 1524 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1525 ::= { capwapBaseWtpRebootStatsEntry 4 } 1527 capwapBaseWtpHwFailureCount OBJECT-TYPE 1528 SYNTAX Counter32 1529 MAX-ACCESS read-only 1530 STATUS current 1531 DESCRIPTION 1532 "Represents the number of times that a CAPWAP protocol 1533 connection with an AC has failed due to hardware related 1534 reasons." 1535 REFERENCE 1536 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1537 ::= { capwapBaseWtpRebootStatsEntry 5 } 1539 capwapBaseWtpOtherFailureCount OBJECT-TYPE 1540 SYNTAX Counter32 1541 MAX-ACCESS read-only 1542 STATUS current 1543 DESCRIPTION 1544 "Represents the number of times that a CAPWAP protocol 1545 connection with an AC has failed due to known reasons, other 1546 than AC initiated, link, software or hardware failure." 1547 REFERENCE 1548 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1549 ::= { capwapBaseWtpRebootStatsEntry 6 } 1551 capwapBaseWtpUnknownFailureCount OBJECT-TYPE 1552 SYNTAX Counter32 1553 MAX-ACCESS read-only 1554 STATUS current 1555 DESCRIPTION 1556 "Represents the number of times that a CAPWAP protocol 1557 connection with an AC has failed for unknown reasons." 1558 REFERENCE 1559 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1560 ::= { capwapBaseWtpRebootStatsEntry 7 } 1562 capwapBaseWtpLastFailureType OBJECT-TYPE 1563 SYNTAX INTEGER { 1564 notSupport(0), 1565 acInit(1), 1566 linkFailure(2), 1567 swFailure(3), 1568 hwFailure(4), 1569 otherFailure(5), 1570 unknown(255) 1571 } 1572 MAX-ACCESS read-only 1573 STATUS current 1574 DESCRIPTION 1575 "Represents the failure type of the most recent WTP failure. 1576 The following enumerated values are supported: 1577 notSupport(0) - Not Supported, 1578 acInit(1) - AC Initiated, 1579 linkFailure(2) - Link Failure, 1580 swFailure(3) - Software Failure, 1581 hwFailure(4) - Hardware Failure, 1582 otherFailure(5) - Other Failure, 1583 unknown(255) - Unknown (e.g., WTP doesn't keep track 1584 of info)." 1585 REFERENCE 1586 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1587 ::= { capwapBaseWtpRebootStatsEntry 8 } 1589 -- End of capwapBaseWtpRebootStatsTable table 1591 -- capwapBaseRadioStatsTable table 1593 capwapBaseRadioStatsTable OBJECT-TYPE 1594 SYNTAX SEQUENCE OF CapwapBaseRadioStatsEntry 1595 MAX-ACCESS not-accessible 1596 STATUS current 1597 DESCRIPTION 1598 "A table of objects that display statistics on radios behavior, 1599 and reasons why the WTP radio has been reset." 1600 REFERENCE 1601 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 1602 ::= { capwapBaseWtps 6 } 1604 capwapBaseRadioStatsEntry OBJECT-TYPE 1605 SYNTAX CapwapBaseRadioStatsEntry 1606 MAX-ACCESS not-accessible 1607 STATUS current 1608 DESCRIPTION 1609 "A set of objects that display the statistic data of 1610 events happened on a specific radio of a WTP." 1611 INDEX { capwapBaseWtpCurrId, capwapBaseRadioId } 1612 ::= { capwapBaseRadioStatsTable 1 } 1614 CapwapBaseRadioStatsEntry ::= SEQUENCE { 1615 capwapBaseRadioResetCount Counter32, 1616 capwapBaseRadioSwFailCount Counter32, 1617 capwapBaseRadioHwFailCount Counter32, 1618 capwapBaseRadioOtherFailCount Counter32, 1619 capwapBaseRadioUnknownFailCount Counter32, 1620 capwapBaseRadioConfigUpdateCount Counter32, 1621 capwapBaseRadioChannelChangeCount Counter32, 1622 capwapBaseRadioBandChangeCount Counter32, 1623 capwapBaseRadioCurrentNoiseFloor Integer32, 1624 capwapBaseRadioDecryptErrorCount Counter32, 1625 capwapBaseRadioLastFailType INTEGER 1626 } 1628 capwapBaseRadioResetCount OBJECT-TYPE 1629 SYNTAX Counter32 1630 MAX-ACCESS read-only 1631 STATUS current 1632 DESCRIPTION 1633 "Represents the number of times that that the radio has been 1634 reset." 1635 REFERENCE 1636 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 1637 ::= { capwapBaseRadioStatsEntry 1 } 1639 capwapBaseRadioSwFailCount OBJECT-TYPE 1640 SYNTAX Counter32 1641 MAX-ACCESS read-only 1642 STATUS current 1643 DESCRIPTION 1644 "Represents the number of times that the radio has failed due 1645 to software related reasons." 1646 REFERENCE 1647 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 1648 ::= { capwapBaseRadioStatsEntry 2 } 1650 capwapBaseRadioHwFailCount OBJECT-TYPE 1651 SYNTAX Counter32 1652 MAX-ACCESS read-only 1653 STATUS current 1654 DESCRIPTION 1655 "Represents the number of times that the radio has failed due 1656 to hardware related reasons." 1658 REFERENCE 1659 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 1660 ::= { capwapBaseRadioStatsEntry 3 } 1662 capwapBaseRadioOtherFailCount OBJECT-TYPE 1663 SYNTAX Counter32 1664 MAX-ACCESS read-only 1665 STATUS current 1666 DESCRIPTION 1667 "Represents the number of times that the radio has failed due to 1668 known reasons, other than software or hardware failure." 1669 REFERENCE 1670 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 1671 ::= { capwapBaseRadioStatsEntry 4 } 1673 capwapBaseRadioUnknownFailCount OBJECT-TYPE 1674 SYNTAX Counter32 1675 MAX-ACCESS read-only 1676 STATUS current 1677 DESCRIPTION 1678 "Represents the number of times that the radio has failed for 1679 unknown reasons." 1680 REFERENCE 1681 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 1682 ::= { capwapBaseRadioStatsEntry 5 } 1684 capwapBaseRadioConfigUpdateCount OBJECT-TYPE 1685 SYNTAX Counter32 1686 MAX-ACCESS read-only 1687 STATUS current 1688 DESCRIPTION 1689 "Represents the number of times that the radio configuration has 1690 been updated." 1691 REFERENCE 1692 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 1693 ::= { capwapBaseRadioStatsEntry 6 } 1695 capwapBaseRadioChannelChangeCount OBJECT-TYPE 1696 SYNTAX Counter32 1697 MAX-ACCESS read-only 1698 STATUS current 1699 DESCRIPTION 1700 "Represents the number of times that the radio channel has 1701 been changed." 1702 REFERENCE 1703 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 1704 ::= { capwapBaseRadioStatsEntry 7 } 1706 capwapBaseRadioBandChangeCount OBJECT-TYPE 1707 SYNTAX Counter32 1708 MAX-ACCESS read-only 1709 STATUS current 1710 DESCRIPTION 1711 "Represents the number of times that the radio has changed 1712 frequency bands." 1713 REFERENCE 1714 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 1715 ::= { capwapBaseRadioStatsEntry 8 } 1717 capwapBaseRadioCurrentNoiseFloor OBJECT-TYPE 1718 SYNTAX Integer32 1719 UNITS "dBm" 1720 MAX-ACCESS read-only 1721 STATUS current 1722 DESCRIPTION 1723 "Represents the noise floor of the radio receiver in units of 1724 dBm." 1725 REFERENCE 1726 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 1727 ::= { capwapBaseRadioStatsEntry 9 } 1729 capwapBaseRadioDecryptErrorCount OBJECT-TYPE 1730 SYNTAX Counter32 1731 MAX-ACCESS read-only 1732 STATUS current 1733 DESCRIPTION 1734 "Represents the number of decryption errors that occurred on the 1735 WTP. Note that this field is only valid in cases where the WTP 1736 provides encryption/decryption services." 1737 REFERENCE 1738 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 1739 ::= { capwapBaseRadioStatsEntry 10 } 1741 capwapBaseRadioLastFailType OBJECT-TYPE 1742 SYNTAX INTEGER { 1743 notSupport(0), 1744 swFailure(1), 1745 hwFailure(2), 1746 otherFailure(3), 1747 unknown(255) 1748 } 1749 MAX-ACCESS read-only 1750 STATUS current 1751 DESCRIPTION 1752 "Represents the failure type of the most recent radio failure. 1753 The following enumerated values are supported: 1755 notSupport(0) - Not Supported, 1756 swFailure(1) - Software Failure, 1757 hwFailure(2) - Hardware Failure, 1758 otherFailure(3) - Other Failure, 1759 unknown(255) - Unknown." 1760 REFERENCE 1761 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 1762 ::= { capwapBaseRadioStatsEntry 11 } 1764 -- End of capwapBaseRadioStatsTable table 1765 -- End of WTP Objects Group 1767 -- CAPWAP Base Parameters Group 1769 capwapBaseParameters OBJECT IDENTIFIER 1770 ::= { capwapBaseObjects 3 } 1772 capwapBaseMaxRetransmitNum OBJECT-TYPE 1773 SYNTAX Unsigned32 1774 MAX-ACCESS read-write 1775 STATUS current 1776 DESCRIPTION 1777 "Represent the maximum number of retransmission for a given 1778 CAPWAP packet before the link layer considers the peer dead." 1779 REFERENCE 1780 "Section 4.8.7. of CAPWAP Protocol Specification, RFC xxx." 1781 ::= { capwapBaseParameters 1 } 1783 capwapBaseChangeStatePendingTimer OBJECT-TYPE 1784 SYNTAX Unsigned32 1785 UNITS "second" 1786 MAX-ACCESS read-write 1787 STATUS current 1788 DESCRIPTION 1789 "Represents the maximum time, in seconds, the AC will wait 1790 for the Change State Event Request from the WTP after having 1791 transmitted a successful Configuration Status Response 1792 message." 1793 REFERENCE 1794 "Section 4.7.1. of CAPWAP Protocol Specification, RFC xxx." 1795 ::= { capwapBaseParameters 2 } 1797 capwapBaseDataCheckTimer OBJECT-TYPE 1798 SYNTAX Unsigned32 1799 UNITS "second" 1800 MAX-ACCESS read-write 1801 STATUS current 1802 DESCRIPTION 1803 "Represents The number of seconds the AC will wait for 1804 the Data Channel Keep Alive, which is required by the 1805 CAPWAP state machine's Data Check state. 1806 The AC resets the state machine if this timer expires 1807 prior to transitioning to the next state." 1808 REFERENCE 1809 "Section 4.7.4. of CAPWAP Protocol Specification, RFC xxx." 1810 ::= { capwapBaseParameters 3 } 1812 capwapBaseMinDTLSSessionDeleteTimer OBJECT-TYPE 1813 SYNTAX Unsigned32 1814 UNITS "second" 1815 MAX-ACCESS read-write 1816 STATUS current 1817 DESCRIPTION 1818 "Represents the minimum time, in seconds, an AC MUST wait 1819 for DTLS session deletion." 1820 REFERENCE 1821 "Section 4.7.6. of CAPWAP Protocol Specification, RFC xxx." 1822 ::= { capwapBaseParameters 4 } 1824 capwapBaseEchoInterval OBJECT-TYPE 1825 SYNTAX Unsigned32 1826 UNITS "second" 1827 MAX-ACCESS read-write 1828 STATUS current 1829 DESCRIPTION 1830 "Represents the minimum time, in seconds, between sending Echo 1831 Request messages to the AC with which the WTP has joined." 1832 REFERENCE 1833 "Section 4.7.7. of CAPWAP Protocol Specification, RFC xxx." 1834 ::= { capwapBaseParameters 5 } 1836 capwapBaseRetransmitInterval OBJECT-TYPE 1837 SYNTAX Unsigned32 1838 UNITS "second" 1839 MAX-ACCESS read-write 1840 STATUS current 1841 DESCRIPTION 1842 "Represents the minimum time, in seconds, in which a 1843 non-acknowledged CAPWAP packet will be retransmitted." 1844 REFERENCE 1845 "Section 4.7.12. of CAPWAP Protocol Specification, RFC xxx." 1846 ::= { capwapBaseParameters 6 } 1848 capwapBaseSilentInterval OBJECT-TYPE 1849 SYNTAX Unsigned32 1850 UNITS "second" 1851 MAX-ACCESS read-write 1852 STATUS current 1853 DESCRIPTION 1854 "Represents the minimum time, in seconds, during which the AC 1855 SHOULD ignore all CAPWAP and DTLS packets received from the 1856 WTP that is in the Sulking state." 1857 REFERENCE 1858 "Section 4.7.13. of CAPWAP Protocol Specification, RFC xxx." 1859 ::= { capwapBaseParameters 7 } 1861 capwapBaseWaitDTLSTimer OBJECT-TYPE 1862 SYNTAX Unsigned32 1863 UNITS "second" 1864 MAX-ACCESS read-write 1865 STATUS current 1866 DESCRIPTION 1867 "Represents the maximum time, in seconds, an AC MUST wait 1868 without having received a DTLS Handshake message from an AC. 1869 This timer MUST be greater than 30 seconds." 1870 REFERENCE 1871 "Section 4.7.15. of CAPWAP Protocol Specification, RFC xxx." 1872 ::= { capwapBaseParameters 8 } 1874 capwapBaseWaitJoinTimer OBJECT-TYPE 1875 SYNTAX Unsigned32 1876 UNITS "second" 1877 MAX-ACCESS read-write 1878 STATUS current 1879 DESCRIPTION 1880 "Represents the maximum time, in seconds, an AC will wait after 1881 the DTLS session has been established until it receives the 1882 Join Request from the WTP. This timer MUST be greater than 20 1883 seconds." 1884 REFERENCE 1885 "Section 4.7.16. of CAPWAP Protocol Specification, RFC xxx." 1886 ::= { capwapBaseParameters 9 } 1888 -- End of CAPWAP Base Parameters Group 1890 -- CAPWAP Statistics Group 1892 capwapBaseStats OBJECT IDENTIFIER 1893 ::= { capwapBaseObjects 4 } 1895 capwapBaseFailedDTLSAuthFailCount OBJECT-TYPE 1896 SYNTAX Counter32 1897 MAX-ACCESS read-only 1898 STATUS current 1899 DESCRIPTION 1900 "Represents the number of failed DTLS session 1901 establishment attempts due to authentication failures." 1902 REFERENCE 1903 "Section 4.8.3. of CAPWAP Protocol Specification, RFC xxx." 1904 ::= { capwapBaseStats 1 } 1906 capwapBaseFailedDTLSSessionCount OBJECT-TYPE 1907 SYNTAX Counter32 1908 MAX-ACCESS read-only 1909 STATUS current 1910 DESCRIPTION 1911 "Represents the number of failed DTLS session 1912 establishment attempts." 1913 REFERENCE 1914 "Section 4.8.4. of CAPWAP Protocol Specification, RFC xxx." 1915 ::= { capwapBaseStats 2 } 1917 -- Notifications 1919 capwapBaseChannelUp NOTIFICATION-TYPE 1920 OBJECTS { 1921 capwapBaseNtfWtpId, 1922 capwapBaseNtfChannelType, 1923 capwapBaseNtfAuthenMethod 1924 } 1925 STATUS current 1926 DESCRIPTION 1927 "This notification is sent by AC when a CAPWAP channel 1928 established. The notification is separated for data or control 1929 channel." 1930 ::= { capwapBaseNotifications 1 } 1932 capwapBaseChannelDown NOTIFICATION-TYPE 1933 OBJECTS { 1934 capwapBaseNtfWtpId, 1935 capwapBaseNtfChannelType, 1936 capwapBaseNtfChannelDownReason 1937 } 1938 STATUS current 1939 DESCRIPTION 1940 "This notification is sent by AC when CAPWAP channel becomes 1941 down. The notification is separated for data or control 1942 channel." 1943 ::= { capwapBaseNotifications 2 } 1945 capwapBaseDecryptErrorReport NOTIFICATION-TYPE 1946 OBJECTS { 1947 capwapBaseNtfWtpId, 1948 capwapBaseNtfRadioId, 1949 capwapBaseNtfStationIdList 1950 } 1951 STATUS current 1952 DESCRIPTION 1953 "This notification is generated when a WTP that has occurred 1954 decryption error since the last report." 1955 REFERENCE 1956 "Section 4.6.17. of CAPWAP Protocol Specification, RFC xxx." 1957 ::= { capwapBaseNotifications 3 } 1959 capwapBaseJoinFailure NOTIFICATION-TYPE 1960 OBJECTS { 1961 capwapBaseNtfWtpId, 1962 capwapBaseNtfJoinFailureReason 1963 } 1964 STATUS current 1965 DESCRIPTION 1966 "This notification is generated when a WTP fails to join." 1967 REFERENCE 1968 "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." 1969 ::= { capwapBaseNotifications 4 } 1971 capwapBaseImageUpgradeFailure NOTIFICATION-TYPE 1972 OBJECTS { 1973 capwapBaseNtfWtpId, 1974 capwapBaseNtfImageFailureReason 1975 } 1976 STATUS current 1977 DESCRIPTION 1978 "This notification is generated when a WTP fails to update 1979 firmware image." 1980 REFERENCE 1981 "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." 1982 ::= { capwapBaseNotifications 5 } 1984 capwapBaseConfigMsgError NOTIFICATION-TYPE 1985 OBJECTS { 1986 capwapBaseNtfWtpId, 1987 capwapBaseNtfConfigMsgErrorType, 1988 capwapBaseNtfMsgErrorElements 1989 } 1990 STATUS current 1991 DESCRIPTION 1992 "This notification is generated when a WTP received message 1993 elements in the configuration management messages which it was 1994 unable to apply locally." 1995 REFERENCE 1996 "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." 1997 ::= { capwapBaseNotifications 6 } 1999 capwapBaseRadioOperableStatus NOTIFICATION-TYPE 2000 OBJECTS { 2001 capwapBaseNtfWtpId, 2002 capwapBaseNtfRadioId, 2003 capwapBaseNtfRadioOperStatusFlag, 2004 capwapBaseNtfRadioStatusCause 2005 } 2006 STATUS current 2007 DESCRIPTION 2008 "The notification is generated when a radio's operational state 2009 is changed." 2010 REFERENCE 2011 "Section 4.6.33. of CAPWAP Protocol Specification, RFC xxx." 2012 ::= { capwapBaseNotifications 7 } 2014 capwapBaseAuthenticationFailure NOTIFICATION-TYPE 2015 OBJECTS { 2016 capwapBaseNtfWtpId, 2017 capwapBaseNtfChannelType, 2018 capwapBaseNtfAuthenMethod, 2019 capwapBaseNtfAuthenFailureReason 2020 } 2021 STATUS current 2022 DESCRIPTION 2023 "The notification will notify the authentication failure event, 2024 and provides the reason for it." 2025 ::= { capwapBaseNotifications 8 } 2027 -- Objects used only in notifications 2029 -- for notifications 2030 capwapBaseNotifyVarObjects OBJECT IDENTIFIER 2031 ::= { capwapBaseObjects 5 } 2033 capwapBaseNtfWtpId OBJECT-TYPE 2034 SYNTAX CapwapBaseWtpIdTC 2035 MAX-ACCESS accessible-for-notify 2036 STATUS current 2037 DESCRIPTION 2038 "Represents the unique identifier of a WTP." 2039 ::= { capwapBaseNotifyVarObjects 1 } 2041 capwapBaseNtfRadioId OBJECT-TYPE 2042 SYNTAX CapwapBaseRadioIdTC 2043 MAX-ACCESS accessible-for-notify 2044 STATUS current 2045 DESCRIPTION 2046 "Represents the identifier of a PHY radio on a WTP, and only 2047 requires unique on a WTP. 2048 For example, WTP A and WTP B will use same value of 2049 capwapBaseNtfRadioId for their first radio." 2050 REFERENCE 2051 "Section 4.3. of CAPWAP Protocol Specification, RFC xxx." 2052 ::= { capwapBaseNotifyVarObjects 2 } 2054 capwapBaseNtfChannelType OBJECT-TYPE 2055 SYNTAX CapwapBaseChannelTypeTC 2056 MAX-ACCESS accessible-for-notify 2057 STATUS current 2058 DESCRIPTION 2059 "Represents the channel type for CAPWAP protocol." 2060 ::= { capwapBaseNotifyVarObjects 3 } 2062 capwapBaseNtfAuthenMethod OBJECT-TYPE 2063 SYNTAX CapwapBaseAuthenMethodTC 2064 MAX-ACCESS accessible-for-notify 2065 STATUS current 2066 DESCRIPTION 2067 "Represents authentication method for Channel." 2068 ::= { capwapBaseNotifyVarObjects 4 } 2070 capwapBaseNtfChannelDownReason OBJECT-TYPE 2071 SYNTAX INTEGER { 2072 timeout(1), 2073 rekeyfailure(2), 2074 acRebootWtp(3), 2075 dtlsError(4), 2076 maxRetransmit(5) 2077 } 2078 MAX-ACCESS accessible-for-notify 2079 STATUS current 2080 DESCRIPTION 2081 "Represents the reason for Channel down. 2082 The following enumerated values are supported: 2083 timeout(1) - The keep alive is timeout, 2084 rekeyfailure(2) - Rekey process is failed, channel will be 2085 broken. 2086 acRebootWtp(3) - AC reboot WTP. 2087 dtlsError(4) - DTLS notifications: DTLSAborted, 2088 DTLSReassemblyFailure, DTLSPeerDisconnect, 2089 or frequent DTLSDecapFailure. 2090 maxRetransmit(5) - The underlying reliable transport's 2091 RetransmitCount counter has reached the 2092 MaxRetransmit variable" 2093 ::= { capwapBaseNotifyVarObjects 5 } 2095 capwapBaseNtfStationIdList OBJECT-TYPE 2096 SYNTAX OCTET STRING 2097 MAX-ACCESS accessible-for-notify 2098 STATUS current 2099 DESCRIPTION 2100 "Represents the list of station id which use semicolons to 2101 separate each station id." 2102 REFERENCE 2103 "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." 2104 ::= { capwapBaseNotifyVarObjects 6 } 2106 capwapBaseNtfAuthenFailureReason OBJECT-TYPE 2107 SYNTAX INTEGER { 2108 keyMismatch(1), 2109 invalidCA(2), 2110 micError(3), 2111 timeout(4), 2112 unknown(8) 2113 } 2114 MAX-ACCESS accessible-for-notify 2115 STATUS current 2116 DESCRIPTION 2117 "Represents reason for WTP authorization failure. 2118 The following enumerated values are supported: 2119 keyMismatch(1) - WTP's and AC's key is not matched, 2120 invalidCA(2) - ca is not valid, 2121 micError(3) - detect MIC error, 2122 timeout(4) - WaitDTLS Timer is timeout, 2123 unknown(8) - Unknown reason." 2124 REFERENCE 2125 "Section 2.3.1. of CAPWAP Protocol Specification, RFC xxx." 2126 ::= { capwapBaseNotifyVarObjects 7 } 2128 capwapBaseNtfRadioOperStatusFlag OBJECT-TYPE 2129 SYNTAX INTEGER { 2130 reserved(0), 2131 operable(1), 2132 inoperable(2) 2133 } 2134 MAX-ACCESS accessible-for-notify 2135 STATUS current 2136 DESCRIPTION 2137 "Represents the operation status of a radio. 2138 The following enumerated values are supported: 2139 reserved(0) - Reserved 2140 operable(1) - To indicate radio is operable, 2141 inoperable(2) - To indicate radio is inoperable, and 2142 capwapBaseNtfRadioStatusCause object will 2143 give reason in details." 2144 REFERENCE 2145 "Section 4.6.33. of CAPWAP Protocol Specification, RFC xxx." 2146 ::= { capwapBaseNotifyVarObjects 8 } 2148 capwapBaseNtfRadioStatusCause OBJECT-TYPE 2149 SYNTAX INTEGER { 2150 normal(0), 2151 hwError(1), 2152 swError(2), 2153 adminSet(3) 2154 } 2155 MAX-ACCESS accessible-for-notify 2156 STATUS current 2157 DESCRIPTION 2158 "Represents the reason the radio is out of service. 2159 The following enumerated values are supported: 2160 normal(0) - Normal Status, 2161 hwError(1) - Radio Failure, 2162 swError(2) - Software Failure, 2163 adminSet(3) - Administratively Set." 2164 REFERENCE 2165 "Section 4.6.33. of CAPWAP Protocol Specification, RFC xxx." 2166 ::= { capwapBaseNotifyVarObjects 9 } 2168 capwapBaseNtfJoinFailureReason OBJECT-TYPE 2169 SYNTAX INTEGER { 2170 unspecified(1), 2171 resDepletion(2), 2172 unknownSource(3), 2173 incorrectData(4), 2174 sessionIdInUse(5), 2175 notSupportHw(6), 2176 notSupportBinding(7) 2177 } 2178 MAX-ACCESS accessible-for-notify 2179 STATUS current 2180 DESCRIPTION 2181 "Represents the reason of join failure. 2182 The following enumerated values are supported: 2183 unspecified(1) - unspecified failure reason, 2184 resDepletion(2) - Resource Depletion, 2185 unknownSource(3) - Unknown Source, 2186 incorrectData(4) - Incorrect Data, 2187 sessionIdInUse(5) - Session ID already in use, 2188 notSupportHw(6) - WTP Hardware not supported, 2189 notSupportBinding(7) - Binding Not Supported." 2190 REFERENCE 2191 "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." 2192 ::= { capwapBaseNotifyVarObjects 10 } 2194 capwapBaseNtfImageFailureReason OBJECT-TYPE 2195 SYNTAX INTEGER { 2196 invalidChecksum(1), 2197 invalidLength(2), 2198 other(3), 2199 inStorage(4) 2200 } 2201 MAX-ACCESS accessible-for-notify 2202 STATUS current 2203 DESCRIPTION 2204 "Represents the reason of image failure. 2205 The following enumerated values are supported: 2206 invalidChecksum(1) - Invalid Checksum, 2207 invalidLength(2) - Invalid Data Length, 2208 other(3) - Other Error, 2209 inStorage(4) - Image Already Present." 2210 REFERENCE 2211 "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." 2212 ::= { capwapBaseNotifyVarObjects 11 } 2214 capwapBaseNtfConfigMsgErrorType OBJECT-TYPE 2215 SYNTAX INTEGER { 2216 unknownElement(1), 2217 unsupportedElement(2), 2218 unknownValue(3), 2219 unsupportedValue(4) 2220 } 2221 MAX-ACCESS accessible-for-notify 2222 STATUS current 2223 DESCRIPTION 2224 "Represents the type of configuration message error. 2225 The following enumerated values are supported: 2226 unknownElement(1) - Unknown Message Element, 2227 unsupportedElement(2) - Unsupported Message Element, 2228 unknownValue(3) - Unknown Message Element Value, 2229 unsupportedValue(4) - Unsupported Message Element Value." 2230 REFERENCE 2231 "Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx." 2232 ::= { capwapBaseNotifyVarObjects 12 } 2234 capwapBaseNtfMsgErrorElements OBJECT-TYPE 2235 SYNTAX SnmpAdminString 2236 MAX-ACCESS accessible-for-notify 2237 STATUS current 2238 DESCRIPTION 2239 "Represents the message elements sent by the AC in the 2240 Configuration Status Response message that caused the error." 2241 REFERENCE 2242 "Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx." 2243 ::= { capwapBaseNotifyVarObjects 13 } 2245 -- Module compliance 2247 capwapBaseCompliances OBJECT IDENTIFIER 2248 ::= { capwapBaseConformance 1 } 2250 capwapBaseGroups OBJECT IDENTIFIER 2251 ::= { capwapBaseConformance 2 } 2253 capwapBaseCompliance MODULE-COMPLIANCE 2254 STATUS current 2255 DESCRIPTION 2256 "Describes the requirements for conformance to the 2257 CAPWAP-BASE-MIB." 2259 MODULE -- this module 2260 MANDATORY-GROUPS { 2261 capwapBaseAcNodeGroup, 2262 capwapBaseWtpStateGroup, 2263 capwapBaseWtpsGroup, 2264 capwapBaseRadiosGroup, 2265 capwapBaseStationsGroup 2266 } 2268 GROUP capwapBaseAcNodeGroup2 2269 DESCRIPTION 2270 "The capwapBaseAcNodeGroup2 group is optional." 2272 GROUP capwapBaseAcNameListGroup 2273 DESCRIPTION 2274 "The capwapBaseAcNameListGroup group is optional." 2276 GROUP capwapBaseMacAclsGroup 2277 DESCRIPTION 2278 "The capwapBaseMacAclsGroup group is optional." 2280 GROUP capwapBaseWtpsGroup2 2281 DESCRIPTION 2282 "The capwapBaseWtpsGroup2 group is optional." 2284 GROUP capwapBaseWtpRebootStatsGroup 2285 DESCRIPTION 2286 "The capwapBaseWtpRebootStatsGroup group is optional." 2288 GROUP capwapBaseRadioStatsGroup 2289 DESCRIPTION 2290 "The capwapBaseRadioStatsGroup group is optional." 2292 GROUP capwapBaseParametersGroup 2293 DESCRIPTION 2294 "The capwapBaseParametersGroup group is optional." 2296 GROUP capwapBaseStatsGroup 2297 DESCRIPTION 2298 "The capwapBaseStatsGroup group is optional." 2300 GROUP capwapBaseNotificationGroup 2301 DESCRIPTION 2302 "The group capwapBaseNotificationGroup is optional." 2304 GROUP capwapBaseNotifyVarGroup 2305 DESCRIPTION 2306 "The capwapBaseNotifyVarGroup group is optional. 2307 If capwapBaseNotificationGroup is supported, 2308 this group must be implemented." 2310 OBJECT capwapBaseRadioWirelessBinding 2311 SYNTAX INTEGER { reserved0(0), reserved2(2) } 2312 DESCRIPTION 2313 "A value other than reserved0(0), reserved2(2) need not be 2314 supported if there is no wireless binding defined for 2315 technologies used." 2316 ::= { capwapBaseCompliances 1 } 2318 capwapBaseAcNodeGroup OBJECT-GROUP 2319 OBJECTS { 2320 capwapBaseWtpSessions, 2321 capwapBaseMaxWtpSessionsConfig, 2322 capwapBaseStationSessions, 2323 capwapBaseMaxStationSessionsConfig 2324 } 2325 STATUS current 2326 DESCRIPTION 2327 "The collection of objects which are used to represent 2328 basic properties for AC from CAPWAP protocol perspective." 2329 ::= { capwapBaseGroups 1 } 2331 capwapBaseAcNodeGroup2 OBJECT-GROUP 2332 OBJECTS { 2333 capwapBaseDataChannelSecOptions, 2334 capwapBaseDataChannelSecConfig, 2335 capwapBaseControlChannelAuthenOptions, 2336 capwapBaseControlChannelAuthenConfig 2337 } 2338 STATUS current 2339 DESCRIPTION 2340 "The collection of objects which are used to represent 2341 other properties such as security for AC from 2342 CAPWAP protocol perspective." 2343 ::= { capwapBaseGroups 2 } 2345 capwapBaseAcNameListGroup OBJECT-GROUP 2346 OBJECTS { 2347 capwapBaseAcNameListName, 2348 capwapBaseAcNameListPriority, 2349 capwapBaseAcNameListRowStatus 2350 } 2351 STATUS current 2352 DESCRIPTION 2353 "The collection of objects which are used to configure 2354 AC name list." 2355 ::= { capwapBaseGroups 3 } 2357 capwapBaseMacAclsGroup OBJECT-GROUP 2358 OBJECTS { 2359 capwapBaseMacAclStationId, 2360 capwapBaseMacAclsRowStatus 2361 } 2362 STATUS current 2363 DESCRIPTION 2364 "The collection of objects which are used to configure 2365 stations ACL." 2366 ::= { capwapBaseGroups 4 } 2368 capwapBaseWtpStateGroup OBJECT-GROUP 2369 OBJECTS { 2370 capwapBaseWtpIpAddressType, 2371 capwapBaseWtpIpAddress, 2372 capwapBaseWtpPhyAddress, 2373 capwapBaseWtpState 2374 } 2375 STATUS current 2376 DESCRIPTION 2377 "The collection of objects which are used to represent 2378 WTP state information." 2380 ::= { capwapBaseGroups 5 } 2382 capwapBaseWtpsGroup OBJECT-GROUP 2383 OBJECTS { 2384 capwapBaseWtpName, 2385 capwapBaseWtpLocation, 2386 capwapBaseWtpBaseMacAddress, 2387 capwapBaseTunnelModeOptions, 2388 capwapBaseMacTypeOptions, 2389 capwapBaseWtpRadiosInUseNum, 2390 capwapBaseWtpRadioNumLimit 2391 } 2392 STATUS current 2393 DESCRIPTION 2394 "The collection of objects which are used to represent 2395 configuration and properties information for WTP 2396 in running state." 2397 ::= { capwapBaseGroups 6 } 2399 capwapBaseWtpsGroup2 OBJECT-GROUP 2400 OBJECTS { 2401 capwapBaseWtpPhyIndex, 2402 capwapBaseWtpDiscoveryType, 2403 capwapBaseWtpStaticIpEnable, 2404 capwapBaseWtpStaticIpType, 2405 capwapBaseWtpStaticIp, 2406 capwapBaseWtpNetmask, 2407 capwapBaseWtpGateway, 2408 capwapBaseWtpFallbackEnable, 2409 capwapBaseWtpRetransmitCount 2410 } 2411 STATUS current 2412 DESCRIPTION 2413 "The collection of objects which are used to represent 2414 configuration and properties information for WTP 2415 in running state." 2416 ::= { capwapBaseGroups 7 } 2418 capwapBaseRadiosGroup OBJECT-GROUP 2419 OBJECTS { 2420 capwapBaseVirtualRadioIfIndex, 2421 capwapBaseRadioWirelessBinding 2422 } 2423 STATUS current 2424 DESCRIPTION 2425 "The collection of objects which are used to represent 2426 wireless binding type, the mapping relationship between 2427 'WLAN Virtual Radio Interface' and PHY radio." 2429 ::= { capwapBaseGroups 8 } 2431 capwapBaseStationsGroup OBJECT-GROUP 2432 OBJECTS { 2433 capwapBaseStationAddedTime, 2434 capwapBaseStationVlanName 2435 } 2436 STATUS current 2437 DESCRIPTION 2438 "The collection of objects which are used to represent 2439 stations' basic property." 2440 ::= { capwapBaseGroups 9 } 2442 capwapBaseWtpRebootStatsGroup OBJECT-GROUP 2443 OBJECTS { 2444 capwapBaseWtpRebootCount, 2445 capwapBaseWtpInitCount, 2446 capwapBaseWtpLinkFailureCount, 2447 capwapBaseWtpSwFailureCount, 2448 capwapBaseWtpHwFailureCount, 2449 capwapBaseWtpOtherFailureCount, 2450 capwapBaseWtpUnknownFailureCount, 2451 capwapBaseWtpLastFailureType 2452 } 2453 STATUS current 2454 DESCRIPTION 2455 "The collection of objects which are used for collecting 2456 WTP reboot count, link failure count, hardware failure 2457 count and so on." 2458 ::= { capwapBaseGroups 10 } 2460 capwapBaseRadioStatsGroup OBJECT-GROUP 2461 OBJECTS { 2462 capwapBaseRadioResetCount, 2463 capwapBaseRadioSwFailCount, 2464 capwapBaseRadioHwFailCount, 2465 capwapBaseRadioOtherFailCount, 2466 capwapBaseRadioUnknownFailCount, 2467 capwapBaseRadioConfigUpdateCount, 2468 capwapBaseRadioChannelChangeCount, 2469 capwapBaseRadioBandChangeCount, 2470 capwapBaseRadioCurrentNoiseFloor, 2471 capwapBaseRadioDecryptErrorCount, 2472 capwapBaseRadioLastFailType 2473 } 2474 STATUS current 2475 DESCRIPTION 2476 "The collection of objects which are used for collecting 2477 radio reset count, channel change count, hardware failure 2478 count and so on" 2479 ::= { capwapBaseGroups 11 } 2481 capwapBaseParametersGroup OBJECT-GROUP 2482 OBJECTS { 2483 capwapBaseMaxRetransmitNum, 2484 capwapBaseChangeStatePendingTimer, 2485 capwapBaseDataCheckTimer, 2486 capwapBaseMinDTLSSessionDeleteTimer, 2487 capwapBaseEchoInterval, 2488 capwapBaseRetransmitInterval, 2489 capwapBaseSilentInterval, 2490 capwapBaseWaitDTLSTimer, 2491 capwapBaseWaitJoinTimer 2492 } 2493 STATUS current 2494 DESCRIPTION 2495 "Objects used for CAPWAP protocol." 2496 ::= { capwapBaseGroups 12 } 2498 capwapBaseStatsGroup OBJECT-GROUP 2499 OBJECTS { 2500 capwapBaseFailedDTLSAuthFailCount, 2501 capwapBaseFailedDTLSSessionCount 2502 } 2503 STATUS current 2504 DESCRIPTION 2505 "Objects used for CAPWAP protocol." 2506 ::= { capwapBaseGroups 13 } 2508 capwapBaseNotificationGroup NOTIFICATION-GROUP 2509 NOTIFICATIONS { 2510 capwapBaseChannelUp, 2511 capwapBaseChannelDown, 2512 capwapBaseDecryptErrorReport, 2513 capwapBaseJoinFailure, 2514 capwapBaseImageUpgradeFailure, 2515 capwapBaseConfigMsgError, 2516 capwapBaseRadioOperableStatus, 2517 capwapBaseAuthenticationFailure 2518 } 2519 STATUS current 2520 DESCRIPTION 2521 "Collection of notifications in this MIB." 2522 ::= { capwapBaseGroups 14 } 2524 capwapBaseNotifyVarGroup OBJECT-GROUP 2525 OBJECTS { 2526 capwapBaseNtfWtpId, 2527 capwapBaseNtfRadioId, 2528 capwapBaseNtfChannelType, 2529 capwapBaseNtfAuthenMethod, 2530 capwapBaseNtfChannelDownReason, 2531 capwapBaseNtfStationIdList, 2532 capwapBaseNtfAuthenFailureReason, 2533 capwapBaseNtfRadioOperStatusFlag, 2534 capwapBaseNtfRadioStatusCause, 2535 capwapBaseNtfJoinFailureReason, 2536 capwapBaseNtfImageFailureReason, 2537 capwapBaseNtfConfigMsgErrorType, 2538 capwapBaseNtfMsgErrorElements 2539 } 2540 STATUS current 2541 DESCRIPTION 2542 "Objects used for notification." 2543 ::= { capwapBaseGroups 15 } 2545 END 2547 10. Security Considerations 2549 There are a number of management objects defined in this MIB module 2550 with a MAX-ACCESS clause of read-write and/or read-create. Such 2551 objects may be considered sensitive or vulnerable in some network 2552 environments. The support for SET operations in a non-secure 2553 environment without proper protection can have a negative effect on 2554 network operations. The followings are the tables and objects and 2555 their sensitivity/vulnerability: 2557 o - Unauthorized changes to the capwapBaseWtpTable, writable objects 2558 under capwapBaseAcs group may disrupt allocation of resources in 2559 the network. 2561 Some of the readable objects in this MIB module (i.e., objects with a 2562 MAX-ACCESS other than not-accessible) may be considered sensitive or 2563 vulnerable in some network environments. It is thus important to 2564 control even GET and/or NOTIFY access to these objects and possibly 2565 to even encrypt the values of these objects when sending them over 2566 the network via SNMP. The followings are the tables and objects and 2567 their sensitivity/vulnerability: 2569 o - The capwapBaseWtpTable exposes WTP's important information like 2570 IP address, MAC type and so on; 2572 o - The capwapBaseWtpRebootStatTable exposes WTP's failure 2573 information; 2575 o - The capwapBaseRadioStatsTable exposes radio's failure 2576 information; 2578 SNMP versions prior to SNMPv3 did not include adequate security. 2579 Even if the network itself is secure (for example by using IPSec), 2580 even then, there is no control as to who on the secure network is 2581 allowed to access and GET/SET (read/change/create/delete) the objects 2582 in this MIB module. 2584 It is RECOMMENDED that implementers consider the security features as 2585 provided by the SNMPv3 framework (see [RFC3410], section 8), 2586 including full support for the SNMPv3 cryptographic mechanisms (for 2587 authentication and privacy). 2589 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2590 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2591 enable cryptographic security. It is then a customer/operator 2592 responsibility to ensure that the SNMP entity giving access to an 2593 instance of this MIB module is properly configured to give access to 2594 the objects only to those principals (users) that have legitimate 2595 rights to indeed GET or SET (change/create/delete) them. 2597 11. IANA Considerations 2599 11.1. IANA Considerations for CAPWAP-BASE-MIB 2601 The MIB module in this document uses the following IANA-assigned 2602 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 2604 Descriptor OBJECT IDENTIFIER value 2605 ---------- ----------------------- 2607 capwapBaseMIB { mib-2 XXX } 2609 11.2. IANA Considerations for ifType 2611 Require IANA to assign a ifType for 'WTP Virtual Radio Interface' 2612 type. 2614 12. Contributors 2616 This MIB is based on contributions from Long Gao. 2618 13. Acknowledgements 2620 The authors wish to thank David Harrington, Yu Liu, Xi Yao, Sachin 2621 Dutta, Ju Wang, Yujin Zhao, Haitao Zhang. 2623 14. References 2625 14.1. Normative References 2627 [RFC2119] Bradner, S., "Key words for 2628 use in RFCs to Indicate 2629 Requirement Levels", 2630 BCP 14, RFC 2119, 2631 March 1997. 2633 [RFC2578] McCloghrie, K., Ed., 2634 Perkins, D., Ed., and J. 2635 Schoenwaelder, Ed., 2636 "Structure of Management 2637 Information Version 2 2638 (SMIv2)", STD 58, RFC 2578, 2639 April 1999. 2641 [RFC2579] McCloghrie, K., Ed., 2642 Perkins, D., Ed., and J. 2643 Schoenwaelder, Ed., 2644 "Textual Conventions for 2645 SMIv2", STD 58, RFC 2579, 2646 April 1999. 2648 [RFC2580] McCloghrie, K., Perkins, 2649 D., and J. Schoenwaelder, 2650 "Conformance Statements for 2651 SMIv2", STD 58, RFC 2580, 2652 April 1999. 2654 [RFC2863] McCloghrie, K. and F. 2655 Kastenholz, "The Interfaces 2656 Group MIB", RFC 2863, 2657 June 2000. 2659 [RFC3418] Presuhn, R., "Management 2660 Information Base (MIB) for 2661 the Simple Network 2662 Management Protocol 2663 (SNMP)", STD 62, RFC 3418, 2664 December 2002. 2666 [RFC4001] Daniele, M., Haberman, B., 2667 Routhier, S., and J. 2668 Schoenwaelder, "Textual 2669 Conventions for Internet 2670 Network Addresses", 2671 RFC 4001, February 2005. 2673 [RFC4133] Bierman, A. and K. 2674 McCloghrie, "Entity MIB 2675 (Version 3)", RFC 4133, 2676 August 2005. 2678 [I-D.ietf-capwap-protocol-specification] Montemurro, M., Stanley, 2679 D., and P. Calhoun, "CAPWAP 2680 Protocol Specification", dr 2681 aft-ietf-capwap-protocol- 2682 specification-14 (work in 2683 progress), October 2008. 2685 14.2. Informative References 2687 [RFC3410] Case, J., Mundy, R., 2688 Partain, D., and B. 2689 Stewart, "Introduction and 2690 Applicability Statements 2691 for Internet-Standard 2692 Management Framework", 2693 RFC 3410, December 2002. 2695 Authors' Addresses 2697 Yang Shi (editor) 2698 H3C Tech. Co., Ltd 2699 Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian District, 2700 Beijing 2701 China(100085) 2703 Phone: +86 010 82775276 2704 EMail: young@h3c.com 2705 David Perkins (editor) 2706 SNMPinfo 2707 288 Quailbrook Ct San Carlos, 2708 CA 94070 2709 USA 2711 Phone: +1 408 394-8702 2712 EMail: dperkins@snmpinfo.com 2714 Chris Elliott (editor) 2715 Cisco Systems, Inc. 2716 7025 Kit Creek Rd., P.O. Box 14987 Research Triangle Park 2717 27709 2718 USA 2720 Phone: +1 919-392-2146 2721 EMail: chelliot@cisco.com 2723 Yong Zhang (editor) 2724 Fortinet, Inc. 2725 1090 Kifer Road 2726 Sunnyvale, CA 94086 2727 USA 2729 EMail: yzhang@fortinet.com 2731 Full Copyright Statement 2733 Copyright (C) The IETF Trust (2008). 2735 This document is subject to the rights, licenses and restrictions 2736 contained in BCP 78, and except as set forth therein, the authors 2737 retain all their rights. 2739 This document and the information contained herein are provided on an 2740 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2741 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 2742 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 2743 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 2744 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2745 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2747 Intellectual Property 2749 The IETF takes no position regarding the validity or scope of any 2750 Intellectual Property Rights or other rights that might be claimed to 2751 pertain to the implementation or use of the technology described in 2752 this document or the extent to which any license under such rights 2753 might or might not be available; nor does it represent that it has 2754 made any independent effort to identify any such rights. Information 2755 on the procedures with respect to rights in RFC documents can be 2756 found in BCP 78 and BCP 79. 2758 Copies of IPR disclosures made to the IETF Secretariat and any 2759 assurances of licenses to be made available, or the result of an 2760 attempt made to obtain a general license or permission for the use of 2761 such proprietary rights by implementers or users of this 2762 specification can be obtained from the IETF on-line IPR repository at 2763 http://www.ietf.org/ipr. 2765 The IETF invites any interested party to bring to its attention any 2766 copyrights, patents or patent applications, or other proprietary 2767 rights that may cover technology that may be required to implement 2768 this standard. Please address the information to the IETF at 2769 ietf-ipr@ietf.org.