idnits 2.17.1 draft-ietf-capwap-base-mib-00.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 2440. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2451. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2458. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2464. ** The document seems to lack an RFC 3978 Section 5.4 (updated by RFC 4748) Copyright Line. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (May 21, 2008) is 5813 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 4133 (Obsoleted by RFC 6933) Summary: 3 errors (**), 0 flaws (~~), 1 warning (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force Y. Shi, Ed. 3 Internet-Draft H3C Tech. Co., Ltd 4 Intended status: Standards Track D. Perkins, Ed. 5 Expires: November 22, 2008 SNMPinfo 6 C. Elliott, Ed. 7 Cisco Systems, Inc. 8 P. Puneet, Ed. 9 Broadcom, Inc. 10 May 21, 2008 12 CAPWAP Protocol Base MIB 13 draft-ietf-capwap-base-mib-00 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 November 22, 2008. 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. Textual Conventions . . . . . . . . . . . . . . . . . . . 5 56 6.2. The capwapObjects Subtree . . . . . . . . . . . . . . . . 7 57 6.3. The capwapConformance Subtree . . . . . . . . . . . . . . 7 58 6.4. The capwapNotifications Subtree . . . . . . . . . . . . . 7 59 6.5. Brief Description of MIB Objects . . . . . . . . . . . . . 7 60 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 8 61 7.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 8 62 7.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 8 63 7.3. Relationship to the ENTITY-MIB . . . . . . . . . . . . . . 10 64 7.4. Relationship to MIB standards of other SDOs . . . . . . . 10 65 7.5. MIB modules required for IMPORTS . . . . . . . . . . . . . 10 66 8. Example of CAPWAP-MIB Usage . . . . . . . . . . . . . . . . . 10 67 9. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 12 68 10. Security Considerations . . . . . . . . . . . . . . . . . . . 48 69 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 49 70 11.1. IANA Considerations for CAPWAP-MIB . . . . . . . . . . . . 49 71 11.2. IANA Considerations for ifType . . . . . . . . . . . . . . 49 72 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 49 73 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 49 74 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 49 75 14.1. Normative References . . . . . . . . . . . . . . . . . . . 49 76 14.2. Informative References . . . . . . . . . . . . . . . . . . 51 78 1. Introduction 80 Current work is under way in the IETF to specify the CAPWAP Protocol 81 [I-D.ietf-capwap-protocol-specification], which enables an Access 82 Controller (AC) to manage a collection of Wireless Termination Points 83 (WTPs) 85 This document defines a MIB module that can be used to manage CAPWAP 86 implementations. This MIB module covers both configuration and WTP 87 status-monitoring aspects of CAPWAP, and provides a way to reuse 88 current MIB standards and future extensions for any wireless binding 89 technology. 91 2. The Internet-Standard Management Framework 93 For a detailed overview of the documents that describe the current 94 Internet-Standard Management Framework, please refer to section 7 of 95 RFC 3410 [RFC3410]. 97 Managed objects are accessed via a virtual information store, termed 98 the Management Information Base or MIB. MIB objects are generally 99 accessed through the Simple Network Management Protocol (SNMP). 100 Objects in the MIB are defined using the mechanisms defined in the 101 Structure of Management Information (SMI). This memo specifies a MIB 102 module that is compliant to the SMIv2, which is described in STD 58, 103 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 104 [RFC2580]. 106 3. Terminology 108 This document uses terminology from the document describing the 109 CAPWAP Protocol specification [I-D.ietf-capwap-protocol- 110 specification]. WTPs are viewed as remote RF interfaces controlled 111 by the AC via CAPWAP protocol. The CAPWAP protocol supports two 112 modes of operation: Split and Local MAC. In Split MAC mode all L2 113 wireless data and management frames are encapsulated via the CAPWAP 114 protocol and exchanged between the AC and the WTP. The Local MAC 115 mode of operation allows for the data frames to be either locally 116 bridged, or tunneled as 802.3 frames. From AC, operator could 117 centrally control WTPs configuration and monitor their status. 118 CAPWAP use DTLS protocol to implement control channel security. 120 4. Conventions 122 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 123 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 124 document are to be interpreted as described in RFC 2119 [RFC2119]. 126 5. Overview 128 The CAPWAP Protocol MIB module (CAPWAP-MIB) have the following design 129 objectives: 131 - To work well under centralized architectures, and provide a way to 132 centrally manage and control wireless network by SNMP 134 - To be consistent with CAPWAP protocol 136 - To reuse current MIB standards and future extensions for a wireless 137 binding technology 139 - To enable interoperability between vendors 141 - To meet operator requirements for centralized architectures 143 The basic idea of CAPWAP-MIB is: 145 - The SNMP agent run on the AC side, and it MAY not be required on 146 the WTP side. It follows same idea as CAPWAP protocol: Centralized 147 Control 149 - As a generic mechanism, it is independent of any wireless binding 150 technologies and defined by a independent MIB file 152 - To be independent of any wireless binding technologies and have 153 ability to reuse MIB standards of other SDOs, is the main challenge 154 for design of the MIB 156 - The ifIndex [RFC2863] will play a role in bridging between MIB 157 standards defined by different SDOs 159 - The operator could manage and control the centralized wireless 160 architectures using multiple MIB standards defined by multiple SDOs, 161 while keeping them loosely coupled 163 It is designed to satisfy the following requirements and constraints: 165 - From AC to centrally manage and monitor WTPs 167 - The MIB module supports CAPWAP protocol parameters queries 169 - The MIB module supports showing WTPs current state 171 - The MIB module provides the information of AC, WTPs, radio and 172 station objects' basic property and their relationship 173 - The MIB module supports indicating the "WTP Virtual Radio 174 Interface" and PHY radio's mapping relationship 176 - The counters are provided for WTP, radio's reboot event, hardware 177 event failure and so on 179 - The MIB module provides the various notification like channel up, 180 join failure and so on 182 Before coming to details of CAPWAP-MIB module, it will introduce how 183 CAPWAP-MIB is able to be independent of any wireless binding 184 technologies and reuse MIB standards of other SDOs. As centralized 185 Wireless architecture, the operator has to prepare configuration at 186 AC side before WTPs connects to AC. For any wireless binding 187 technology, the configuration and management of radio is very 188 important. Under centralized Wireless architecture, according to 189 [I-D.ietf-capwap-protocol-specification], a specific PHY radio could 190 be identified by identifier of a WTP and radio (WTP id + radio id). 191 As usual, the standard of a binding technology provides MIB standard 192 for radio management on its own. For example, according to IEEE 193 802.11 WG MIB standards, the MIB tables such as Dot11OperationTable 194 are able to support WTP radio configuration. These tables use 195 ifIndex as the index, and work well under standalone Wireless 196 architecture. 198 To reuse MIB objects (defined by SDOs such as IEEE) for radio is very 199 import, and the key point is to reuse the idea of ifIndex. So it is 200 required a way to maintain the mapping relationship between "WTP id + 201 radio id" and "ifIndex". As a generic mechanism, ifIndex can 202 identify an interface in abstract way, and it does NOT care for an 203 interface's PHY location (either on WTP or AC). AC can have 204 interfaces of "WTP Virtual Radio Interface" ifType, it will logically 205 represents PHY radios on the WTPs side. It looks like that PHY 206 radios are located on the AC side, and PHY location of WTP (radio) is 207 hidden to the operator. Operator can operate radios by MIB tables 208 (such as IEEE 802.11 WG's) with ifIndex of "WTP Virtual Radio 209 Interface". As an Abstract interface, "WTP Virtual Radio Interface" 210 could be used by any wireless binding technology such as IEEE 802.11 211 and 802.16. The table of capwapRadioBindTable will indicate the 212 mapping relationship between "WTP id + Radio id" and IfIndex. 214 6. Structure of the MIB Module 216 6.1. Textual Conventions 218 The following textual conventions are defined: 220 CapwapWTPId ::= TEXTUAL-CONVENTION 221 STATUS current 222 DESCRIPTION 223 "Represents a unique identifier of a WTP instance. 224 As usual, a serial number of WTP will be used." 225 SYNTAX OCTET STRING(SIZE(128)) 227 CapwapStationId ::= TEXTUAL-CONVENTION 228 STATUS current 229 DESCRIPTION 230 "Represents a unique identifier of a station instance. 231 As usual, the MAC address of station will be used." 232 SYNTAX OCTET STRING (SIZE (6)) 234 CapwapRadioId ::= TEXTUAL-CONVENTION 235 STATUS current 236 DESCRIPTION 237 "Represents a unique identifier of a radio on a WTP." 238 SYNTAX Unsigned32 (1..4294967295) 240 CapwapWTPTunnelMode ::= TEXTUAL-CONVENTION 241 STATUS current 242 DESCRIPTION 243 "Represents the tunneling mode for station data that are 244 supported by the WTP. 245 The possible value could be: 246 localBridging(1) - Local Bridging Mode, 247 dot3Tunnel(2) - 802.3 Frame Tunnel Mode, 248 nativeTunnel(3) - Native Frame Tunnel Mode." 249 REFERENCE 250 "Section 4.6.41. of CAPWAP Protocol Specification, RFC xxx." 251 SYNTAX INTEGER { localBridging(1), dot3Tunnel(2), 252 nativeTunnel(3) } 254 CapwapWTPMACType ::= TEXTUAL-CONVENTION 255 STATUS current 256 DESCRIPTION 257 "Represents the MAC mode of operation supported by the WTP. 258 The possible value could be: 259 localMAC(1) - Local-MAC Mode, 260 splitMAC(2) - Split-MAC Mode." 261 REFERENCE 262 "Section 4.6.44. of CAPWAP Protocol Specification, RFC xxx." 263 SYNTAX INTEGER { localMAC(1), splitMAC(2) } 265 CapwapChannelType::= TEXTUAL-CONVENTION 266 STATUS current 267 DESCRIPTION 268 "Represents the channel type for CAPWAP protocol. 270 The following values are supported: 271 data(1) - data Channel 272 control(2) - control Channel." 273 SYNTAX INTEGER { data(1), control(2) } 275 CapwapWTPAuthenMethod ::= TEXTUAL-CONVENTION 276 STATUS current 277 DESCRIPTION 278 "Represents the authentication credential type 279 for WTP. 280 The following values are supported: 281 clear(1) - clear text and no authentication, 282 x509(2) - X.509 Certificate Based, 283 psk(3) - Pre-Shared Secret, 284 other(8) - Other method, for example, vendor specific. 285 As mandatory requirement, CAPWAP control channel 286 authentication should use DTLS, and either by certificate or 287 PSK. For data channel, DTLS is optional." 288 SYNTAX INTEGER { clear(1), x509(2), psk(3), other(8) } 290 6.2. The capwapObjects Subtree 292 The subtree provides information for statistic data and configuration 293 parameters of WTP and radio. 295 6.3. The capwapConformance Subtree 297 The subtree provides conformance information of MIB objects. 299 6.4. The capwapNotifications Subtree 301 The subtree describe the notifications defined in the MIB module, and 302 their purpose. 304 6.5. Brief Description of MIB Objects 306 The MIB objects were derived from the CAPWAP protocol document 307 [I-D.ietf- capwap-protocol-specification]. 309 1) capwapWTPStateTable 311 The WTPs status table is used to indicate each WTP's CAPWAP FSM 312 state. 314 2) capwapWTPTable 316 The WTPs table is used for providing property and configuration 317 information in details for WTPs in running state. 319 3) capwapRadioBindTable 321 The radio bind table is used to indicate the mapping relationship 322 between logical interface of "WTP Virtual Radio Interface" ifType and 323 PHY radio. 325 4) capwapStationTable 327 The station table is used for providing stations' basic property 328 information. 330 5) capwapWTPRebootStatsTable 332 The WTP reboot statistic table is used for collecting WTP reboot 333 count, link failure count, hardware failure count and so on. 335 6) capwapRadioStatsTable 337 The WTP radio statistic table is used for collecting radio reset 338 count, channel change count, hardware failure count and so on. 340 7. Relationship to Other MIB Modules 342 7.1. Relationship to the SNMPv2-MIB 344 The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being 345 mandatory for all systems, and the objects apply to the entity as a 346 whole. The 'system' group provides identification of the management 347 entity and certain other system-wide data. The CAPWAP-MIB does not 348 duplicate those objects. 350 7.2. Relationship to the IF-MIB 352 The Interfaces Group [RFC2863] defines generic managed objects for 353 managing interfaces. This memo contains the media-specific 354 extensions to the Interfaces Group for managing WTP radio object that 355 are modeled as interfaces. 357 IF-MIB is required to support on the AC side. For each PHY radio at 358 WTP side, it will have a logical interface of 'WTP Virtual Radio 359 Interface' ifType at AC side. The ifIndex of interface will 360 represent PHY radio by logical. The interface SHOULD be modeled as 361 an ifEntry and provide appropriate interface information. 363 Some specific interpretations of ifTable for CAPWAP-MIB are as 364 follow. 366 Object Use for the CAPWAP MIB. 368 ifIndex Each interface of 'WTP Virtual Radio Interface' type 369 maybe be represented by an ifEntry. 371 ifDescr Description of the interface of 'WTP Virtual Radio 372 Interface' ifType. 374 ifType IANAifType of 'WTP Virtual Radio Interface'. 376 ifName Textual name (unique on this system) of the interface 377 or an octet string of zero length. 379 ifAlias The nonvolatile 'alias' name for the interface, as 380 specified by a network manager. 382 ifPhysAddress The physical address of the interface; i.e., 383 BSSID of a 802.11 radio. 385 ifAdminStatus This variable indicates the operator's intent as 386 to whether PHY should be enabled, disabled, or 387 running in some diagnostic testing mode on this 388 interface. 389 Also see [RFC2863]. 391 ifOperStatus This value reflects the actual or operational status 392 of radio. 393 Also see [RFC2863]. 395 ifLastChange The value of sysUpTime at the time the interface 396 entered its current operational state. 397 Also see [RFC2863]. 399 ifInOctets The number of received octets over the interface; 400 i.e., the number of octets received as 802.11 frames. 402 ifOutOctets The number of transmitted octets over the interface; 403 i.e., the number of octets transmitted as 802.11 404 frames. 406 ifInErrors The number of frames dropped due to 407 uncorrectable errors. 409 ifInUnknownProtos 410 The number of received frame discarded during 411 frame header validation, including frames with 412 unrecognized label values. 414 ifOutErrors See [RFC2863]. 416 7.3. Relationship to the ENTITY-MIB 418 The ENTITY-MIB [RFC4133] meets need for a standardized way of 419 representing a single agent, which supports multiple instances of one 420 MIB. It could express a certain relationship between multiple 421 entities, and provide entity properties for each entity. 423 Under the wireless centralized architectures, the SNMP agent will run 424 on the AC side, and not required on the WTP side. By the ENTITY-MIB 425 on the AC side, it could keep entity information of AC and WTPs. 426 From the ENTITY-MIB perspective, the overall physical entity (AC) is 427 a "compound" of multiple physical entities (WTPs which connects to 428 AC), all entities are identified by Physical index. In the 429 capwapWTPTable of CAPWAP-MIB, it uses capwapWTPPHYIndex object to 430 keep the mapping relationship of WTP object between CAPWAP-MIB and 431 ENTITY-MIB. 433 7.4. Relationship to MIB standards of other SDOs 435 The MIB standards (such as IEEE 802.11 MIB) of a wireless binding is 436 required to support on the AC side. The CAPWAP-MIB module is able to 437 support any wireless binding technology. Through ifIndex of 'WTP 438 Virtual Radio Interface' ifType, it provides consistent and abstract 439 way of reusing MIB objects of a wireless binding technology. 441 7.5. MIB modules required for IMPORTS 443 The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], 444 SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863], INET- 445 ADDRESS-MIB [RFC4001] and ENTITY-MIB [RFC4133]. 447 8. Example of CAPWAP-MIB Usage 449 With the idea of "WTP Virtual Radio Interface" in the mind, the 450 usage of MIB will be easily understood. Here takes IEEE 802.11 451 binding technology as an example. 453 1) Identify each PHY radio by "WTP Virtual Radio Interface" 454 According to [I-D.ietf-capwap-protocol-specification], each radio on 455 a WTP will be identified by a radio Id. Each WTP could be identified 456 by its serial number. 457 When configuration for a WTP is prepared before a WTP connects to AC, 458 the following information is available in the CapwapRadioBindTable. 459 In CapwapRadioBindTable 460 { 461 capwapWTPId = 12345678 462 capwapRadioId = 1 463 capwapWTPVirtualRadioifIndex = 10, 464 capwapWirelessBinding = dot11(2), 465 } 466 Suppse WTP's serial number is 12345678, and first radio id is 1. 467 At AC side, the ifIndex of interface in "WTP Virtual Radio Interface" 468 ifType is 10 which represents the PHY radio 1. 469 By the mechanism of "WTP Virtual Radio Interface", it seemed that WTP 470 PHY radios are located at AC side. 471 The interface of "WTP Virtual Radio Interface" ifType is modeled by 472 ifTable. 473 In ifTable 474 { 475 ifIndex = 10, 476 ifDescr = "WTP Virtual Radio Interface", 477 ifType = IANAifType of "WTP Virtual 478 Radio Interface", 479 ifMtu = 0, 480 ifSpeed = 0, 481 ifPhysAddress = 0.0.0.0.0.0, 482 ifAdminStatus = true, 483 ifOperStatus = false, 484 ifLastChange = 0, 485 ifInOctets = 0, 486 ifInUcastPkts = 0, 487 ifInDiscards = 0, 488 ifInErrors = 0, 489 ifInUnknownProtos = 0, 490 ifOutOctets = 0, 491 ifOutUcastPkts = 0, 492 ifOutDiscards = 0, 493 ifOutErrors = 0, 494 } 496 2) Configure specific wireless binding parameters for "WTP Virtual 497 Radio Interface" 498 It will be done at the AC side through specific wireless binding MIB 499 such as IEEE 802.11 MIB. 500 For example, to configure parameter for "WTP Virtual Radio Interface" 501 by 802.11 Dot11OperationTable. 502 In Dot11OperationTable 503 { 504 ifIndex = 10, 505 dot11MACAddress = 0.0.0.0.0.0, 506 dot11RTSThreshold = 2347, 507 dot11ShortRetryLimit = 7, 508 dot11LongRetryLimit = 4, 509 dot11FragmentationThreshold = 256, 510 dot11MaxTransmitMSDULifetime = 512, 511 dot11MaxReceiveLifetime = 512, 512 dot11ManufacturerID = "capwap", 513 dot11ProductID = "capwap" 514 } 515 In the example, it suppose ifIndex of an interface in 516 "WTP Virtual Radio Interface" ifType is 10. 518 3) Other configurations for a specific wireless binding 519 For example, WLAN service configuration will be done through CAPWAP 520 binding MIB and IEEE 802.11 MIB. In the CAPWAP 802.11 binding MIB 521 draft, it will give more explain. 523 4) WTP reports its current configuration status 524 After join phase and before WTP get configuration from AC, it will 525 report its current configuration status to AC through configuration 526 status message. The data of MIB objects will be updated at AC side. 527 For example, for 802.11 binding, WTP will update data in the 528 ifTable and IEEE 802.11 MIB so on according to message content. 529 As an example for ifIndex 10, its ifOperStatus in ifTable will be 530 updated according to current radio operational status in the 531 CAPWAP message. 533 5) Query WTP and radio statistics data 534 After WTPs come to run status, operator could query WTP and 535 radio statistics data through CAPWAP-MIB and specific binding MIB. 536 For example, through dot11CountersTable in the IEEE 802.11 MIB, 537 operator could query counter data for radio which is identified 538 by ifIndex of a virtual radio interface. With capwapACState table 539 in the MIB, operator could query configuration and properties of 540 WTPs which are in run status. 542 6) Query other statistics data of a specific wireless binding 543 For example, operator could query the statistics data of 544 WLAN service through 802.11 binding MIB and IEEE 802.11 MIB. 545 In the CAPWAP 802.11 binding MIB draft, it will give more explain. 547 7) Query other properties of WTP 548 Operator could query MIB objects in the ENTITY-MIB by 549 capwapWTPPHYIndex in the capwapWTPTable of CAPWAP-MIB. 550 The properties of WTP such as software version, hardware version 551 and so on are available in the ENTITY-MIB. 553 9. Definitions 555 CAPWAP-MIB DEFINITIONS ::= BEGIN 557 IMPORTS 558 PhysAddress, TEXTUAL-CONVENTION, TruthValue, 559 DateAndTime 560 FROM SNMPv2-TC 561 InterfaceIndex 562 FROM IF-MIB 563 PhysicalIndex 564 FROM ENTITY-MIB 565 SnmpAdminString 566 FROM SNMP-FRAMEWORK-MIB 567 NOTIFICATION-GROUP, OBJECT-GROUP, MODULE-COMPLIANCE 568 FROM SNMPv2-CONF 569 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2, 570 Integer32, Unsigned32, Counter32 571 FROM SNMPv2-SMI 572 InetAddressType, InetAddress 573 FROM INET-ADDRESS-MIB; 575 capwapMIB MODULE-IDENTITY 576 LAST-UPDATED "200805210000Z" -- May 21th, 2008 577 ORGANIZATION "IETF Control And Provisioning of Wireless Access 578 Points (CAPWAP) Working Group 579 http://www.ietf.org/html.charters/capwap-charter.html" 580 CONTACT-INFO 581 "General Discussion: capwap@frascone.com 582 To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap 584 Yang Shi 585 H3C, Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian 586 District,Beijing,China(100085) 587 Email: young@h3c.com 589 David T. Perkins 590 228 Bayview Dr 591 San Carlos, CA 94070 592 USA 593 Phone: +1 408 394-8702 594 Email: dperkins@snmpinfo.com 596 Chris Elliott 597 Cisco Systems, Inc. 598 7025 Kit Creek Rd., P.O. Box 14987 599 Research Triangle Park 27709 600 USA 601 Phone: +1 919-392-2146 602 Email: chelliot@cisco.comP 604 Puneet Agarwal 605 BroadCom, Inc. 607 USA 608 Email: pagarwal@broadcom.com" 610 DESCRIPTION 611 "Copyright (C) 2008 The Internet Society. This version of 612 the MIB module is part of RFC xxx; see the RFC itself 613 for full legal notices. 615 This MIB module contains managed object definitions for 616 the CAPWAP Protocol." 617 REVISION "200805210000Z" 618 DESCRIPTION 619 "Initial version published as RFC xxx" 620 ::= { mib-2 xxx } 622 -- Textual Conventions 624 CapwapWTPId ::= TEXTUAL-CONVENTION 625 STATUS current 626 DESCRIPTION 627 "Represents a unique identifier of a WTP instance. 628 As usual, a serial number of WTP will be used." 629 SYNTAX OCTET STRING(SIZE(128)) 631 CapwapStationId ::= TEXTUAL-CONVENTION 632 STATUS current 633 DESCRIPTION 634 "Represents a unique identifier of a station instance. 635 As usual, the MAC address of station will be used." 636 SYNTAX OCTET STRING (SIZE (6)) 638 CapwapRadioId ::= TEXTUAL-CONVENTION 639 STATUS current 640 DESCRIPTION 641 "Represents a unique identifier of a radio on a WTP." 642 SYNTAX Unsigned32 (1..4294967295) 644 CapwapWTPTunnelMode ::= TEXTUAL-CONVENTION 645 STATUS current 646 DESCRIPTION 647 "Represents the tunneling mode for station data that are 648 supported by the WTP. 649 The possible value could be: 650 localBridging(1) - Local Bridging Mode, 651 dot3Tunnel(2) - 802.3 Frame Tunnel Mode, 652 nativeTunnel(3) - Native Frame Tunnel Mode." 653 REFERENCE 654 "Section 4.6.43. of CAPWAP Protocol Specification, RFC xxx." 656 SYNTAX INTEGER { localBridging(1), dot3Tunnel(2), 657 nativeTunnel(3) } 659 CapwapWTPMACType ::= TEXTUAL-CONVENTION 660 STATUS current 661 DESCRIPTION 662 "Represents the MAC mode of operation supported by the WTP. 663 The possible value could be: 664 localMAC(1) - Local-MAC Mode, 665 splitMAC(2) - Split-MAC Mode." 666 REFERENCE 667 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 668 SYNTAX INTEGER { localMAC(1), splitMAC(2) } 670 CapwapChannelType::= TEXTUAL-CONVENTION 671 STATUS current 672 DESCRIPTION 673 "Represents the channel type for CAPWAP protocol. 674 The following values are supported: 675 data(1) - data Channel 676 control(2) - control Channel." 677 SYNTAX INTEGER { data(1), control(2) } 679 CapwapWTPAuthenMethod ::= TEXTUAL-CONVENTION 680 STATUS current 681 DESCRIPTION 682 "Represents the authentication credential type 683 for WTP. 684 The following values are supported: 685 clear(1) - cleartext and no authentication, 686 x509(2) - X.509 Certificate Based, 687 psk(3) - Pre-Shared Secret, 688 other(8) - Other method, for example, vendor specific. 689 As mandatory requirement, CAPWAP control channel 690 authentication should use DTLS, and either by certificate or 691 PSK. For data channel, DTLS is optional." 692 SYNTAX INTEGER { clear(1), x509(2), psk(3), other(8) } 694 -- Top level components of this MIB 696 -- Notifications 697 capwapNotifications OBJECT IDENTIFIER 698 ::= { capwapMIB 0 } 699 -- Tables, Scalars 700 capwapObjects OBJECT IDENTIFIER 701 ::= { capwapMIB 1 } 702 -- Conformance 703 capwapConformance OBJECT IDENTIFIER 704 ::= { capwapMIB 2 } 706 -- AC Objects Group 708 capwapAC OBJECT IDENTIFIER 709 ::= { capwapObjects 1 } 711 capwapWTPSessions OBJECT-TYPE 712 SYNTAX Unsigned32 713 MAX-ACCESS read-only 714 STATUS current 715 DESCRIPTION 716 "Represents the total number of WTPs which are connecting to 717 AC." 718 REFERENCE 719 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 720 ::= { capwapAC 1 } 722 capwapWTPSessionsLimit OBJECT-TYPE 723 SYNTAX Unsigned32 724 MAX-ACCESS read-only 725 STATUS current 726 DESCRIPTION 727 "Represents the maximum number of WTP sessions supported by 728 the AC." 729 REFERENCE 730 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 731 ::= { capwapAC 2 } 733 capwapStationSessions OBJECT-TYPE 734 SYNTAX Unsigned32 735 MAX-ACCESS read-only 736 STATUS current 737 DESCRIPTION 738 "Represents the total number of stations which are accessing 739 the wireless service." 740 REFERENCE 741 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 742 ::= { capwapAC 3 } 744 capwapStationSessionsLimit OBJECT-TYPE 745 SYNTAX Unsigned32 746 MAX-ACCESS read-only 747 STATUS current 748 DESCRIPTION 749 "Represents the maximum number of station sessions supported by 750 the AC." 752 REFERENCE 753 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 754 ::= { capwapAC 4 } 756 capwapDataChannelSecOptions OBJECT-TYPE 757 SYNTAX Integer32 758 MAX-ACCESS read-only 759 STATUS current 760 DESCRIPTION 761 "Represents the security policy supported for CAPWAP data 762 channel. 763 The AC MAY support more than one option, represented by the bit 764 field below. 765 clear(1) - Clear Text, 766 dtls(2) - DTLS, 767 vendor(3) - vendor specific." 768 REFERENCE 769 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 770 ::= { capwapAC 5 } 772 capwapWTPAuthenOptions OBJECT-TYPE 773 SYNTAX Integer32 774 MAX-ACCESS read-only 775 STATUS current 776 DESCRIPTION 777 "Represents the authentication credential type supported by the 778 AC for control channel. 779 The AC MAY support more than one option, represented by the bit 780 field below. 781 x509(1) - X.509 Certificate Based 782 psk(2) - Pre-Shared Secret." 783 REFERENCE 784 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 785 ::= { capwapAC 6 } 787 capwapWTPFallbackEnable OBJECT-TYPE 788 SYNTAX TruthValue 789 MAX-ACCESS read-write 790 STATUS current 791 DESCRIPTION 792 "Represents enable or disable automatic CAPWAP fallback in the 793 event that a WTP detects its preferred AC, and is not currently 794 connected to it." 795 REFERENCE 796 "Section 4.6.42. of CAPWAP Protocol Specification, RFC xxx." 797 ::= { capwapAC 7 } 799 capwapWTPACNameList OBJECT-TYPE 800 SYNTAX OCTET STRING(SIZE(256)) 801 MAX-ACCESS read-write 802 STATUS current 803 DESCRIPTION 804 "Represents the name list of ACs and use semicolon to separate 805 AC name. The AC name could be configured with the order of 806 Primary AC, secondary AC and so on. WTP will try to connect to 807 AC name in the list one by one till it connected to one AC." 808 REFERENCE 809 "Section 4.6.5. of CAPWAP Protocol Specification, RFC xxx." 810 ::= { capwapAC 8 } 812 -- End of AC Objects Group 814 -- WTP Objects Group 816 capwapWTPs OBJECT IDENTIFIER 817 ::= { capwapObjects 2 } 819 -- capwapWTPStateTable table 821 capwapWTPStateTable OBJECT-TYPE 822 SYNTAX SEQUENCE OF CapwapWTPStateEntry 823 MAX-ACCESS not-accessible 824 STATUS current 825 DESCRIPTION 826 "A table of objects that display WTPs in different 827 CAPWAP FSM state." 828 ::= { capwapWTPs 1 } 830 capwapWTPStateEntry OBJECT-TYPE 831 SYNTAX CapwapWTPStateEntry 832 MAX-ACCESS not-accessible 833 STATUS current 834 DESCRIPTION 835 "A set of objects that display WTPs in different 836 CAPWAP FSM state." 837 INDEX { capwapWTPId } 838 ::= { capwapWTPStateTable 1 } 840 CapwapWTPStateEntry ::= SEQUENCE { 841 capwapWTPId CapwapWTPId, 842 capwapWTPIPAddressType InetAddressType, 843 capwapWTPIPAddress InetAddress, 844 capwapWTPPHYAddress PhysAddress, 845 capwapWTPState INTEGER } 847 capwapWTPId OBJECT-TYPE 848 SYNTAX CapwapWTPId 849 MAX-ACCESS accessible-for-notify 850 STATUS current 851 DESCRIPTION 852 "Represents the unique identifier of a WTP." 853 ::= { capwapWTPStateEntry 1 } 855 capwapWTPIPAddressType OBJECT-TYPE 856 SYNTAX InetAddressType 857 MAX-ACCESS read-only 858 STATUS current 859 DESCRIPTION 860 "Represents the type of IP address of WTP." 861 ::= { capwapWTPStateEntry 2 } 863 capwapWTPIPAddress OBJECT-TYPE 864 SYNTAX InetAddress 865 MAX-ACCESS read-only 866 STATUS current 867 DESCRIPTION 868 "Represents the IP address(IPv4 or IPv6) of a WTP." 869 ::= { capwapWTPStateEntry 3 } 871 capwapWTPPHYAddress OBJECT-TYPE 872 SYNTAX PhysAddress 873 MAX-ACCESS read-only 874 STATUS current 875 DESCRIPTION 876 "Represents the PHY address of a WTP." 877 ::= { capwapWTPStateEntry 4 } 879 capwapWTPState OBJECT-TYPE 880 SYNTAX INTEGER { 881 dtls(1), join(2), image(3), configure(4), 882 run(5), clear(6), unknown(7) 883 } 884 MAX-ACCESS read-only 885 STATUS current 886 DESCRIPTION 887 "Represents the various possible CAPWAP FSM states of WTP 888 The following values are supported: 889 dtls(1) - DTLS negotiation process 890 join(2) - WTP is joining with AC, 891 image(3) - WTP is downloading software, 892 configure(4) - WTP is getting configuration from AC, 893 run(5) - WTP comes to run state, 894 clear(6) - WTP recoveries default configuration. 896 unknown(7) - Operator already prepare configuration 897 for WTP, while WTP has not contact with AC 898 till now." 899 REFERENCE 900 "Section 2.3.1. of CAPWAP Protocol Specification, RFC xxx." 901 ::= { capwapWTPStateEntry 5 } 903 -- End of capwapWTPStateTable Table 905 -- capwapWTPTable Table 907 capwapWTPTable OBJECT-TYPE 908 SYNTAX SEQUENCE OF CapwapWTPEntry 909 MAX-ACCESS not-accessible 910 STATUS current 911 DESCRIPTION 912 "A table of objects that display and control WTPs in 913 running state. Values of all read-write objects in this 914 table are persistent at restart/reboot." 915 ::= { capwapWTPs 2 } 917 capwapWTPEntry OBJECT-TYPE 918 SYNTAX CapwapWTPEntry 919 MAX-ACCESS not-accessible 920 STATUS current 921 DESCRIPTION 922 "A set of objects that display and control a WTP in 923 running state." 924 INDEX { capwapWTPCurrId } 925 ::= { capwapWTPTable 1 } 927 CapwapWTPEntry ::= SEQUENCE { 928 capwapWTPCurrId CapwapWTPId, 929 capwapWTPPHYIndex PhysicalIndex, 930 capwapWTPName SnmpAdminString, 931 capwapWTPLocation SnmpAdminString, 932 capwapWTPBaseMACAddress PhysAddress, 933 capwapWTPTunnelModeOptions CapwapWTPTunnelMode, 934 capwapWTPMACTypeOptions CapwapWTPMACType, 935 capwapWTPDiscoveryType INTEGER, 936 capwapWTPRadiosInUseNum Unsigned32, 937 capwapWTPRadioNumLimit Unsigned32, 938 capwapWTPStaticIPEnable TruthValue, 939 capwapWTPStaticIPType InetAddressType, 940 capwapWTPStaticIP InetAddress, 941 capwapWTPNetmask InetAddress, 942 capwapWTPGateway InetAddress } 944 capwapWTPCurrId OBJECT-TYPE 945 SYNTAX CapwapWTPId 946 MAX-ACCESS not-accessible 947 STATUS current 948 DESCRIPTION 949 "Represents the unique identifier of a WTP Which is 950 in running state." 951 ::= { capwapWTPEntry 1 } 953 capwapWTPPHYIndex OBJECT-TYPE 954 SYNTAX PhysicalIndex 955 MAX-ACCESS read-only 956 STATUS current 957 DESCRIPTION 958 "Represents the unique physical index of a physical entity 959 in the ENTITY-MIB. The information such as software version 960 of specific WTP could be accessed through the index." 961 ::= { capwapWTPEntry 2 } 963 capwapWTPName OBJECT-TYPE 964 SYNTAX SnmpAdminString 965 MAX-ACCESS read-write 966 STATUS current 967 DESCRIPTION 968 "Represents the name of a WTP." 969 REFERENCE 970 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 971 ::= { capwapWTPEntry 3 } 973 capwapWTPLocation OBJECT-TYPE 974 SYNTAX SnmpAdminString 975 MAX-ACCESS read-write 976 STATUS current 977 DESCRIPTION 978 "Represents the location of a WTP." 979 REFERENCE 980 "Section 4.6.31. of CAPWAP Protocol Specification, RFC xxx." 981 ::= { capwapWTPEntry 4 } 983 capwapWTPBaseMACAddress OBJECT-TYPE 984 SYNTAX PhysAddress 985 MAX-ACCESS read-only 986 STATUS current 987 DESCRIPTION 988 "Represents the WTP's Base MAC Address, which MAY be assigned 989 to the primary Ethernet interface." 990 REFERENCE 991 "Section 4.6.40. of CAPWAP Protocol Specification, RFC xxx." 993 ::= { capwapWTPEntry 5 } 995 capwapWTPTunnelModeOptions OBJECT-TYPE 996 SYNTAX CapwapWTPTunnelMode 997 MAX-ACCESS read-only 998 STATUS current 999 DESCRIPTION 1000 "Represents the tunneling modes for station data that are 1001 supported by the WTP. 1002 The WTP MAY support more than one option, represented by the 1003 bit field below. 1004 localBridging(1) - Local Bridging Mode, 1005 dot3Tunnel(2) - 802.3 Frame Tunnel Mode, 1006 nativeTunnel(3) - Native Frame Tunnel Mode." 1007 REFERENCE 1008 "Section 4.6.43. of CAPWAP Protocol Specification, RFC xxx." 1009 ::= { capwapWTPEntry 6 } 1011 capwapWTPMACTypeOptions OBJECT-TYPE 1012 SYNTAX CapwapWTPMACType 1013 MAX-ACCESS read-only 1014 STATUS current 1015 DESCRIPTION 1016 "Represents the MAC mode of operation supported by the WTP. 1017 The WTP MAY support more than one option, represented by the 1018 bit field below. 1019 localMAC(1) - Local-MAC Mode, 1020 splitMAC(2) - Split-MAC Mode." 1021 REFERENCE 1022 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1023 ::= { capwapWTPEntry 7 } 1025 capwapWTPDiscoveryType OBJECT-TYPE 1026 SYNTAX INTEGER { 1027 unknown(1), staticConfig(2), dhcp(3), dns(4), acRef(5) 1028 } 1029 MAX-ACCESS read-only 1030 STATUS current 1031 DESCRIPTION 1032 "Represents how WTP discovered the AC. 1033 The following values are supported: 1034 unknown(1) - the method is unknown, 1035 staticConfig(2) - static IP configuration, 1036 dhcp(3) - DHCP, 1037 dns(4) - DNS, 1038 acRef(5) - AC Referral." 1039 REFERENCE 1040 "Section 4.6.23. of CAPWAP Protocol Specification, RFC xxx." 1042 ::= { capwapWTPEntry 8 } 1044 capwapWTPRadiosInUseNum OBJECT-TYPE 1045 SYNTAX Unsigned32 1046 MAX-ACCESS read-only 1047 STATUS current 1048 DESCRIPTION 1049 "Represents the number of radios which are in use." 1050 REFERENCE 1051 "Section 4.6.41. of CAPWAP Protocol Specification, RFC xxx." 1052 ::= { capwapWTPEntry 9 } 1054 capwapWTPRadioNumLimit OBJECT-TYPE 1055 SYNTAX Unsigned32 1056 MAX-ACCESS read-only 1057 STATUS current 1058 DESCRIPTION 1059 "Represents the maximum radio number could be supported 1060 by WTP." 1061 REFERENCE 1062 "Section 4.6.41. of CAPWAP Protocol Specification, RFC xxx." 1063 ::= { capwapWTPEntry 10 } 1065 capwapWTPStaticIPEnable OBJECT-TYPE 1066 SYNTAX TruthValue 1067 MAX-ACCESS read-write 1068 STATUS current 1069 DESCRIPTION 1070 "Represents whether the WTP should use a static IP address 1071 or not. A value of false disables the static IP address, 1072 while a value of true enables it." 1073 REFERENCE 1074 "Section 4.6.51. of CAPWAP Protocol Specification, RFC xxx." 1075 ::= { capwapWTPEntry 11 } 1077 capwapWTPStaticIPType OBJECT-TYPE 1078 SYNTAX InetAddressType 1079 MAX-ACCESS read-write 1080 STATUS current 1081 DESCRIPTION 1082 "Represents whether WTP uses IPV4 or IPV6 static IP address." 1083 ::= { capwapWTPEntry 12 } 1085 capwapWTPStaticIP OBJECT-TYPE 1086 SYNTAX InetAddress 1087 MAX-ACCESS read-write 1088 STATUS current 1089 DESCRIPTION 1090 "When capwapWTPStaticIPEnable is true, it represents the static 1091 IP address to assign to the WTP." 1092 REFERENCE 1093 "Section 4.6.51. of CAPWAP Protocol Specification, RFC xxx." 1094 ::= { capwapWTPEntry 13 } 1096 capwapWTPNetmask OBJECT-TYPE 1097 SYNTAX InetAddress 1098 MAX-ACCESS read-write 1099 STATUS current 1100 DESCRIPTION 1101 "When capwapWTPStaticIPEnable is true, it represents the netmask 1102 to assign to the WTP." 1103 REFERENCE 1104 "Section 4.6.51. of CAPWAP Protocol Specification, RFC xxx." 1105 ::= { capwapWTPEntry 14 } 1107 capwapWTPGateway OBJECT-TYPE 1108 SYNTAX InetAddress 1109 MAX-ACCESS read-write 1110 STATUS current 1111 DESCRIPTION 1112 "When capwapWTPStaticIPEnable is true, it represents the gateway 1113 to assign to the WTP." 1114 REFERENCE 1115 "Section 4.6.51. of CAPWAP Protocol Specification, RFC xxx." 1116 ::= { capwapWTPEntry 15 } 1118 -- End of capwapWTPTable table 1120 -- capwapRadioBindTable Table 1122 capwapRadioBindTable OBJECT-TYPE 1123 SYNTAX SEQUENCE OF CapwapRadioBindEntry 1124 MAX-ACCESS not-accessible 1125 STATUS current 1126 DESCRIPTION 1127 "A table of objects that display the mapping relationship 1128 between specific interface of 'WTP Virtual Radio Interface' 1129 ifType and PHY radio. The mapping relationship in this table 1130 is persistent at restart/reboot." 1131 ::= { capwapWTPs 3 } 1133 capwapRadioBindEntry OBJECT-TYPE 1134 SYNTAX CapwapRadioBindEntry 1135 MAX-ACCESS not-accessible 1136 STATUS current 1137 DESCRIPTION 1138 "A set of objects that display the mapping relationship 1139 between 'WTP Virtual Radio' and PHY radio." 1140 INDEX { capwapWTPId, capwapRadioId } 1141 ::= { capwapRadioBindTable 1 } 1143 CapwapRadioBindEntry ::= SEQUENCE { 1144 capwapRadioId CapwapRadioId, 1145 capwapWTPVirtualRadioIfIndex InterfaceIndex, 1146 capwapWirelessBinding INTEGER 1147 } 1149 capwapRadioId OBJECT-TYPE 1150 SYNTAX CapwapRadioId 1151 MAX-ACCESS accessible-for-notify 1152 STATUS current 1153 DESCRIPTION 1154 "Represents the identifier of a PHY radio on a WTP, and only 1155 requires unique on a WTP. 1156 For example, WTP A and WTP B will use same value of 1157 capwapRadioId for their first radio." 1158 REFERENCE 1159 "Section 4.3. of CAPWAP Protocol Specification, RFC xxx." 1160 ::= { capwapRadioBindEntry 1 } 1162 capwapWTPVirtualRadioIfIndex OBJECT-TYPE 1163 SYNTAX InterfaceIndex 1164 MAX-ACCESS read-only 1165 STATUS current 1166 DESCRIPTION 1167 "Represents the ifIndex for an interface of 'WTP Virtual Radio 1168 Interface' ifType. 1169 Before WTPs connect to AC and get configuration, operator 1170 will prepare configuration for them. At AC side, there are 1171 interface of 'WTP Virtual Radio Interface' type which represent 1172 PHY radio interface at WTP side. 1173 As most MIBs use ifIndex to identify an interface for 1174 configuration and statistic data, for example, IEEE 802.11 MIB. 1175 It will be very easy to reuse other MIBs such as IEEE 802.11 1176 MIB by 'WTP Virtual Radio Interface'. 1177 Require IANA to assign an ifType for 'WTP Virtual Radio 1178 Interface'." 1179 ::= { capwapRadioBindEntry 2 } 1181 capwapWirelessBinding OBJECT-TYPE 1182 SYNTAX INTEGER { none(1), dot11(2), dot16(3), epc(4) } 1183 MAX-ACCESS read-only 1184 STATUS current 1185 DESCRIPTION 1186 "Represents the wireless binding type for radio. 1187 The following values are supported: 1188 none(1) - No any wireless binding defined. 1189 dot11(2) - IEEE 802.11. 1190 dot16(3) - IEEE 802.16. 1191 epc(4) - EPCGlobal." 1192 REFERENCE 1193 "Section 4.3. of CAPWAP Protocol Specification, RFC xxx." 1194 ::= { capwapRadioBindEntry 3 } 1196 -- End of capwapRadioBindTable Table 1198 -- capwapStationTable Table 1200 capwapStationTable OBJECT-TYPE 1201 SYNTAX SEQUENCE OF CapwapStationEntry 1202 MAX-ACCESS not-accessible 1203 STATUS current 1204 DESCRIPTION 1205 "A table of objects that display stations which are 1206 associated with the specific radio on the WTP." 1207 ::= { capwapWTPs 4 } 1209 capwapStationEntry OBJECT-TYPE 1210 SYNTAX CapwapStationEntry 1211 MAX-ACCESS not-accessible 1212 STATUS current 1213 DESCRIPTION 1214 "A set of objects that display a station which is 1215 associated with the specific radio on the WTP." 1216 INDEX { capwapWTPCurrId, capwapRadioId, capwapStationId } 1217 ::= { capwapStationTable 1 } 1219 CapwapStationEntry ::= SEQUENCE { 1220 capwapStationId CapwapStationId, 1221 capwapStationAddedTime DateAndTime, 1222 capwapStationVlanName OCTET STRING 1223 } 1225 capwapStationId OBJECT-TYPE 1226 SYNTAX CapwapStationId 1227 MAX-ACCESS not-accessible 1228 STATUS current 1229 DESCRIPTION 1230 "Represents the unique identifier of the station." 1231 REFERENCE 1232 "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." 1233 ::= { capwapStationEntry 1 } 1235 capwapStationAddedTime OBJECT-TYPE 1236 SYNTAX DateAndTime 1237 MAX-ACCESS read-only 1238 STATUS current 1239 DESCRIPTION 1240 "Represents the time when the station is added." 1241 REFERENCE 1242 "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." 1243 ::= { capwapStationEntry 2 } 1245 capwapStationVlanName OBJECT-TYPE 1246 SYNTAX OCTET STRING (SIZE(32)) 1247 MAX-ACCESS read-only 1248 STATUS current 1249 DESCRIPTION 1250 "Represents VLAN name to which the station is associated." 1251 REFERENCE 1252 "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." 1253 ::= { capwapStationEntry 3 } 1255 -- End of capwapStationTable Table 1257 -- capwapWTPRebootStatTable 1259 capwapWTPRebootStatsTable OBJECT-TYPE 1260 SYNTAX SEQUENCE OF CapwapWTPRebootStatsEntry 1261 MAX-ACCESS not-accessible 1262 STATUS current 1263 DESCRIPTION 1264 "A table of objects that display WTPs' reboot statistic 1265 data." 1266 REFERENCE 1267 "Section 4.6.50. of CAPWAP Protocol Specification, RFC xxx." 1268 ::= { capwapWTPs 5 } 1270 capwapWTPRebootStatsEntry OBJECT-TYPE 1271 SYNTAX CapwapWTPRebootStatsEntry 1272 MAX-ACCESS not-accessible 1273 STATUS current 1274 DESCRIPTION 1275 "A set of objects that display the reboot statistic data 1276 of a WTP." 1277 INDEX { capwapWTPCurrId } 1278 ::= { capwapWTPRebootStatsTable 1 } 1280 CapwapWTPRebootStatsEntry ::= SEQUENCE { 1281 capwapWTPRebootCount Counter32, 1282 capwapWTPInitCount Counter32, 1283 capwapWTPLinkFailureCount Counter32, 1284 capwapWTPSwFailureCount Counter32, 1285 capwapWTPHwFailureCount Counter32, 1286 capwapWTPOtherFailureCount Counter32, 1287 capwapWTPUnknownFailureCount Counter32, 1288 capwapWTPLastFailureType INTEGER 1289 } 1291 capwapWTPRebootCount OBJECT-TYPE 1292 SYNTAX Counter32 1293 MAX-ACCESS read-only 1294 STATUS current 1295 DESCRIPTION 1296 "Represents the number of reboots that have occurred due to a 1297 WTP crash. A value of 65535 implies that this information is 1298 not available on the WTP." 1299 ::= { capwapWTPRebootStatsEntry 1 } 1301 capwapWTPInitCount OBJECT-TYPE 1302 SYNTAX Counter32 1303 MAX-ACCESS read-only 1304 STATUS current 1305 DESCRIPTION 1306 "Represents the number of reboots that have occurred at the 1307 request of a CAPWAP protocol message, such as a change in 1308 configuration that required a reboot or an explicit CAPWAP 1309 protocol reset request. A value of 65535 implies that this 1310 information is not available on the WTP." 1311 ::= { capwapWTPRebootStatsEntry 2 } 1313 capwapWTPLinkFailureCount OBJECT-TYPE 1314 SYNTAX Counter32 1315 MAX-ACCESS read-only 1316 STATUS current 1317 DESCRIPTION 1318 "Represents the number of times that a CAPWAP protocol 1319 connection with an AC has failed due to link failure." 1320 ::= { capwapWTPRebootStatsEntry 3 } 1322 capwapWTPSwFailureCount OBJECT-TYPE 1323 SYNTAX Counter32 1324 MAX-ACCESS read-only 1325 STATUS current 1326 DESCRIPTION 1327 "Represents the number of times that a CAPWAP protocol 1328 connection with an AC has failed due to software related 1329 reasons." 1330 ::= { capwapWTPRebootStatsEntry 4 } 1332 capwapWTPHwFailureCount OBJECT-TYPE 1333 SYNTAX Counter32 1334 MAX-ACCESS read-only 1335 STATUS current 1336 DESCRIPTION 1337 "Represents the number of times that a CAPWAP protocol 1338 connection with an AC has failed due to hardware related 1339 reasons." 1340 ::= { capwapWTPRebootStatsEntry 5 } 1342 capwapWTPOtherFailureCount OBJECT-TYPE 1343 SYNTAX Counter32 1344 MAX-ACCESS read-only 1345 STATUS current 1346 DESCRIPTION 1347 "Represents the number of times that a CAPWAP protocol 1348 connection with an AC has failed due to known reasons, other 1349 than AC initiated, link, software or hardware failure." 1350 ::= { capwapWTPRebootStatsEntry 6 } 1352 capwapWTPUnknownFailureCount OBJECT-TYPE 1353 SYNTAX Counter32 1354 MAX-ACCESS read-only 1355 STATUS current 1356 DESCRIPTION 1357 "Represents the number of times that a CAPWAP protocol 1358 connection with an AC has failed for unknown reasons." 1359 ::= { capwapWTPRebootStatsEntry 7 } 1361 capwapWTPLastFailureType OBJECT-TYPE 1362 SYNTAX INTEGER { 1363 notSupport(1), acInit(2), linkFailure(3), 1364 swFailure(4), hwFailure(5),other(6), unknown(255) 1365 } 1366 MAX-ACCESS read-only 1367 STATUS current 1368 DESCRIPTION 1369 "The failure type of the most recent WTP failure. 1370 The following values are supported: 1371 notSupport(1) - Not Supported, 1372 acInit(2) - AC Initiated, 1373 linkFailure(3) - Link Failure, 1374 swFailure(4) - Software Failure, 1375 hwFailure(5) - Hardware Failure, 1376 otherFailure(6) - Other Failure, 1377 unknown(255) - Unknown (e.g., WTP doesn't keep track 1378 of info)." 1379 ::= { capwapWTPRebootStatsEntry 8 } 1381 -- End of capwapWTPRebootStatsTable table 1383 -- capwapRadioStatsTable table 1385 capwapRadioStatsTable OBJECT-TYPE 1386 SYNTAX SEQUENCE OF CapwapRadioStatsEntry 1387 MAX-ACCESS not-accessible 1388 STATUS current 1389 DESCRIPTION 1390 "A table of objects that display statistics on radios behavior, 1391 and reasons of radios have been reset." 1392 ::= { capwapWTPs 6 } 1394 capwapRadioStatsEntry OBJECT-TYPE 1395 SYNTAX CapwapRadioStatsEntry 1396 MAX-ACCESS not-accessible 1397 STATUS current 1398 DESCRIPTION 1399 "A set of objects that display the statistic data of 1400 events happened on a specific radio of a WTP." 1401 INDEX { capwapWTPCurrId, capwapRadioId } 1402 ::= { capwapRadioStatsTable 1 } 1404 CapwapRadioStatsEntry ::= SEQUENCE { 1405 capwapRadioResetCount Counter32, 1406 capwapRadioSwFailCount Counter32, 1407 capwapRadioHwFailCount Counter32, 1408 capwapRadioOtherFailCount Counter32, 1409 capwapRadioUnknownFailCount Counter32, 1410 capwapRadioConfigUpdateCount Counter32, 1411 capwapRadioChannelChangeCount Counter32, 1412 capwapRadioBandChangeCount Counter32, 1413 capwapRadioCurrentNoiseFloor Integer32, 1414 capwapRadioDecryptErrorCount Counter32, 1415 capwapRadioTxQueueLevel Integer32, 1416 capwapRadioRFLinkFramesCount Counter32, 1417 capwapRadioLastFailType INTEGER 1418 } 1420 capwapRadioResetCount OBJECT-TYPE 1421 SYNTAX Counter32 1422 MAX-ACCESS read-only 1423 STATUS current 1424 DESCRIPTION 1425 "Represents the number of times that that the radio has been 1426 reset." 1427 REFERENCE 1428 "Section 4.6.49. of CAPWAP Protocol Specification, RFC xxx." 1429 ::= { capwapRadioStatsEntry 1 } 1431 capwapRadioSwFailCount OBJECT-TYPE 1432 SYNTAX Counter32 1433 MAX-ACCESS read-only 1434 STATUS current 1435 DESCRIPTION 1436 "Represents the number of times that the radio has failed due 1437 to software related reasons." 1438 REFERENCE 1439 "Section 4.6.49. of CAPWAP Protocol Specification, RFC xxx." 1440 ::= { capwapRadioStatsEntry 2 } 1442 capwapRadioHwFailCount OBJECT-TYPE 1443 SYNTAX Counter32 1444 MAX-ACCESS read-only 1445 STATUS current 1446 DESCRIPTION 1447 "Represents the number of times that the radio has failed due 1448 to hardware related reasons." 1449 REFERENCE 1450 "Section 4.6.49. of CAPWAP Protocol Specification, RFC xxx." 1451 ::= { capwapRadioStatsEntry 3 } 1453 capwapRadioOtherFailCount OBJECT-TYPE 1454 SYNTAX Counter32 1455 MAX-ACCESS read-only 1456 STATUS current 1457 DESCRIPTION 1458 "Represents the number of times that the radio has failed due to 1459 known reasons, other than software or hardware failure." 1460 REFERENCE 1461 "Section 4.6.49. of CAPWAP Protocol Specification, RFC xxx." 1462 ::= { capwapRadioStatsEntry 4 } 1464 capwapRadioUnknownFailCount OBJECT-TYPE 1465 SYNTAX Counter32 1466 MAX-ACCESS read-only 1467 STATUS current 1468 DESCRIPTION 1469 "Represents the number of times that the radio has failed for 1470 unknown reasons." 1472 REFERENCE 1473 "Section 4.6.49. of CAPWAP Protocol Specification, RFC xxx." 1474 ::= { capwapRadioStatsEntry 5 } 1476 capwapRadioConfigUpdateCount OBJECT-TYPE 1477 SYNTAX Counter32 1478 MAX-ACCESS read-only 1479 STATUS current 1480 DESCRIPTION 1481 "Represents the number of times that the radio configuration has 1482 been updated." 1483 REFERENCE 1484 "Section 4.6.49. of CAPWAP Protocol Specification, RFC xxx." 1485 ::= { capwapRadioStatsEntry 6 } 1487 capwapRadioChannelChangeCount OBJECT-TYPE 1488 SYNTAX Counter32 1489 MAX-ACCESS read-only 1490 STATUS current 1491 DESCRIPTION 1492 "Represents the number of times that the radio channel has 1493 been changed." 1494 REFERENCE 1495 "Section 4.6.49. of CAPWAP Protocol Specification, RFC xxx." 1496 ::= { capwapRadioStatsEntry 7 } 1498 capwapRadioBandChangeCount OBJECT-TYPE 1499 SYNTAX Counter32 1500 MAX-ACCESS read-only 1501 STATUS current 1502 DESCRIPTION 1503 "Represents the number of times that the radio has changed 1504 frequency bands." 1505 REFERENCE 1506 "Section 4.6.49. of CAPWAP Protocol Specification, RFC xxx." 1507 ::= { capwapRadioStatsEntry 8 } 1509 capwapRadioCurrentNoiseFloor OBJECT-TYPE 1510 SYNTAX Integer32 1511 UNITS "dBm" 1512 MAX-ACCESS read-only 1513 STATUS current 1514 DESCRIPTION 1515 "Represents the noise floor of the radio receiver in units of 1516 dBm." 1517 REFERENCE 1518 "Section 4.6.49. of CAPWAP Protocol Specification, RFC xxx." 1519 ::= { capwapRadioStatsEntry 9 } 1521 capwapRadioDecryptErrorCount OBJECT-TYPE 1522 SYNTAX Counter32 1523 MAX-ACCESS read-only 1524 STATUS current 1525 DESCRIPTION 1526 "Represents the number of decryption errors that occurred on the 1527 WTP. Note that this field is only valid in cases where the WTP 1528 provides encryption/decryption services." 1529 REFERENCE 1530 "Section 4.6.49. of CAPWAP Protocol Specification, RFC xxx." 1531 ::= { capwapRadioStatsEntry 10 } 1533 capwapRadioTxQueueLevel OBJECT-TYPE 1534 SYNTAX Integer32 (0..100) 1535 MAX-ACCESS read-only 1536 STATUS current 1537 DESCRIPTION 1538 "Represents the percentage of Wireless Transmit queue 1539 utilization,calculated as the sum of utilized transmit queue 1540 lengths divided by the sum of maximum transmit queue lengths, 1541 multiplied by 100." 1542 REFERENCE 1543 "Section 4.6.48. of CAPWAP Protocol Specification, RFC xxx." 1544 ::= { capwapRadioStatsEntry 11 } 1546 capwapRadioRFLinkFramesCount OBJECT-TYPE 1547 SYNTAX Counter32 1548 MAX-ACCESS read-only 1549 STATUS current 1550 DESCRIPTION 1551 "Represents the number of frames transmitted or received per 1552 second by the WTP over the radio interface." 1553 REFERENCE 1554 "Section 4.6.48. of CAPWAP Protocol Specification, RFC xxx." 1555 ::= { capwapRadioStatsEntry 12 } 1557 capwapRadioLastFailType OBJECT-TYPE 1558 SYNTAX INTEGER { 1559 notSupport(1), 1560 swFailure(2), 1561 hwFailure(3), 1562 otherFailure(4), 1563 unknown(255) 1564 } 1565 MAX-ACCESS read-only 1566 STATUS current 1567 DESCRIPTION 1568 "Represents the failure type of the most recent radio failure. 1570 The following values are supported: 1571 notSupport(1) - Not Supported, 1572 swFailure(2) - Software Failure, 1573 hwFailure(3) - Hardware Failure, 1574 otherFailure(4) - Other Failure, 1575 unknown(255) - Unknown." 1576 ::= { capwapRadioStatsEntry 13 } 1578 -- End of capwapRadioStatsTable table 1580 -- CAPWAP Variables Group 1582 capwapVariables OBJECT IDENTIFIER 1583 ::= { capwapObjects 3 } 1585 capwapDataChannelDeadInterval OBJECT-TYPE 1586 SYNTAX Unsigned32 1587 UNITS "second" 1588 MAX-ACCESS read-only 1589 STATUS current 1590 DESCRIPTION 1591 "Represents the minimum time, in seconds, a WTP MUST wait 1592 without having received a Data Channel Keep Alive packet 1593 before the destination for the Data Channel Keep Alive 1594 packets may be considered dead." 1595 REFERENCE 1596 "Section 4.7.3. of CAPWAP Protocol Specification, RFC xxx." 1597 ::= { capwapVariables 1 } 1599 capwapDataCheckTimer OBJECT-TYPE 1600 SYNTAX Unsigned32 1601 UNITS "second" 1602 MAX-ACCESS read-only 1603 STATUS current 1604 DESCRIPTION 1605 "Represents The number of seconds the AC will wait for 1606 the Data Channel Keep Alive, which is required by the 1607 CAPWAP state machine's Data Check state. 1608 The AC resets the state machine if this timer expires 1609 prior to transitioning to the next state." 1610 REFERENCE 1611 "Section 4.7.4. of CAPWAP Protocol Specification, RFC xxx." 1612 ::= { capwapVariables 2 } 1614 capwapMaxDiscoveryInterval OBJECT-TYPE 1615 SYNTAX Unsigned32 1616 UNITS "second" 1617 MAX-ACCESS read-only 1618 STATUS current 1619 DESCRIPTION 1620 "Represents the maximum time allowed between sending 1621 Discovery Request messages, in seconds. 1622 This value MUST be no less than 2 seconds and no greater 1623 than 180 seconds." 1624 REFERENCE 1625 "Section 4.7.9. of CAPWAP Protocol Specification, RFC xxx." 1626 ::= { capwapVariables 3 } 1628 capwapMaxDiscoveries OBJECT-TYPE 1629 SYNTAX Unsigned32 1630 MAX-ACCESS read-only 1631 STATUS current 1632 DESCRIPTION 1633 "Represents the maximum number of Discovery Request messages 1634 that will be sent after a WTP boots." 1635 REFERENCE 1636 "Section 4.8.6. of CAPWAP Protocol Specification, RFC xxx." 1637 ::= { capwapVariables 4 } 1639 capwapMaxRetransmit OBJECT-TYPE 1640 SYNTAX Unsigned32 1641 MAX-ACCESS read-only 1642 STATUS current 1643 DESCRIPTION 1644 "Represent the maximum number of retransmission for a given 1645 CAPWAP packet before the link layer considers the peer dead." 1646 REFERENCE 1647 "Section 4.8.7. of CAPWAP Protocol Specification, RFC xxx." 1648 ::= { capwapVariables 5 } 1650 capwapRetransmitInterval OBJECT-TYPE 1651 SYNTAX Unsigned32 1652 UNITS "second" 1653 MAX-ACCESS read-only 1654 STATUS current 1655 DESCRIPTION 1656 "Represents the minimum time, in seconds, in which a 1657 non-acknowledged CAPWAP packet will be retransmitted." 1658 REFERENCE 1659 "Section 4.7.12. of CAPWAP Protocol Specification, RFC xxx." 1660 ::= { capwapVariables 6 } 1662 capwapReportInterval OBJECT-TYPE 1663 SYNTAX Unsigned32 1664 UNITS "second" 1665 MAX-ACCESS read-only 1666 STATUS current 1667 DESCRIPTION 1668 "Represents the interval for WTP send report." 1669 REFERENCE 1670 "Section 4.8.8. of CAPWAP Protocol Specification, RFC xxx." 1671 ::= { capwapVariables 7 } 1673 -- End of CAPWAP Variables Group 1675 -- CAPWAP Statistics Group 1677 capwapStats OBJECT IDENTIFIER 1678 ::= { capwapObjects 4 } 1680 capwapWTPRetransmitCount OBJECT-TYPE 1681 SYNTAX Counter32 1682 MAX-ACCESS read-only 1683 STATUS current 1684 DESCRIPTION 1685 "Represents the number of retransmissions for a given 1686 CAPWAP packet." 1687 REFERENCE 1688 "Section 4.8.9. of CAPWAP Protocol Specification, RFC xxx." 1689 ::= { capwapStats 1 } 1691 capwapFailedDTLSAuthFailCount OBJECT-TYPE 1692 SYNTAX Counter32 1693 MAX-ACCESS read-only 1694 STATUS current 1695 DESCRIPTION 1696 "Represents the number of failed DTLS session 1697 establishment attempts due to authentication failures." 1698 REFERENCE 1699 "Section 4.8.3. of CAPWAP Protocol Specification, RFC xxx." 1700 ::= { capwapStats 2 } 1702 capwapFailedDTLSSessionCount OBJECT-TYPE 1703 SYNTAX Counter32 1704 MAX-ACCESS read-only 1705 STATUS current 1706 DESCRIPTION 1707 "Represents the number of failed DTLS session 1708 establishment attempts." 1709 REFERENCE 1710 "Section 4.8.4. of CAPWAP Protocol Specification, RFC xxx." 1711 ::= { capwapStats 3 } 1713 -- Notifications 1715 capwapChannelUp NOTIFICATION-TYPE 1716 OBJECTS { capwapWTPId, 1717 capwapChannelType, 1718 capwapWTPAuthenMethod } 1719 STATUS current 1720 DESCRIPTION 1721 "This notification is sent by AC when a CAPWAP channel 1722 established. The notification is separated for data or control 1723 channel." 1724 ::= { capwapNotifications 1 } 1726 capwapChannelDown NOTIFICATION-TYPE 1727 OBJECTS { capwapWTPId, capwapChannelDownReason } 1728 STATUS current 1729 DESCRIPTION 1730 "This notification is sent by AC when CAPWAP channel becomes 1731 down." 1732 ::= { capwapNotifications 2 } 1734 capwapDecryptErrorReport NOTIFICATION-TYPE 1735 OBJECTS { capwapWTPId, 1736 capwapRadioId, 1737 capwapIdEntryNum, 1738 capwapStationIdList } 1739 STATUS current 1740 DESCRIPTION 1741 "This notification is generated when a WTP that has occurred 1742 decryption error since the last report." 1743 REFERENCE 1744 "Section 4.6.18. of CAPWAP Protocol Specification, RFC xxx." 1745 ::= { capwapNotifications 3 } 1747 capwapJoinFailure NOTIFICATION-TYPE 1748 OBJECTS { capwapWTPId, capwapJoinFailureReason } 1749 STATUS current 1750 DESCRIPTION 1751 "This notification is generated when a WTP fails to join." 1752 REFERENCE 1753 "Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx." 1754 ::= { capwapNotifications 4 } 1756 capwapImageUpgradeFailure NOTIFICATION-TYPE 1757 OBJECTS { capwapWTPId, capwapImageFailureReason } 1758 STATUS current 1759 DESCRIPTION 1760 "This notification is generated when a WTP fails to update 1761 software image." 1762 REFERENCE 1763 "Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx." 1764 ::= { capwapNotifications 5 } 1766 capwapConfigMsgError NOTIFICATION-TYPE 1767 OBJECTS { capwapWTPId, capwapConfigMsgErrorType, 1768 capwapMsgErrorElements } 1769 STATUS current 1770 DESCRIPTION 1771 "This notification is generated when a WTP received message 1772 elements in the Configuration Status Response which it was 1773 unable to apply locally." 1774 REFERENCE 1775 "Section 4.6.36. of CAPWAP Protocol Specification, RFC xxx." 1776 ::= { capwapNotifications 6 } 1778 capwapRadioOperableStatus NOTIFICATION-TYPE 1779 OBJECTS { capwapWTPId, 1780 capwapRadioId, 1781 capwapRadioOperStatusFlag, 1782 capwapRadioFailureReason } 1783 STATUS current 1784 DESCRIPTION 1785 "The notification will notify which radio become inoperable 1786 or operable." 1787 REFERENCE 1788 "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." 1789 ::= { capwapNotifications 7 } 1791 capwapWTPAuthenticationFailure NOTIFICATION-TYPE 1792 OBJECTS { capwapWTPId, 1793 capwapChannelType, 1794 capwapWTPAuthenMethod, 1795 capwapWTPAuthenFailureReason } 1796 STATUS current 1797 DESCRIPTION 1798 "The notification will notify the authentication failure event, 1799 and provides the reason for it." 1800 ::= { capwapNotifications 8 } 1802 -- Objects used only in notifications 1804 -- for notifications 1805 capwapNotifyVarObjects OBJECT IDENTIFIER 1806 ::= { capwapObjects 5 } 1808 capwapChannelType OBJECT-TYPE 1809 SYNTAX CapwapChannelType 1810 MAX-ACCESS accessible-for-notify 1811 STATUS current 1812 DESCRIPTION 1813 "Represents the channel type for CAPWAP protocol." 1814 ::= { capwapNotifyVarObjects 1 } 1816 capwapWTPAuthenMethod OBJECT-TYPE 1817 SYNTAX CapwapWTPAuthenMethod 1818 MAX-ACCESS accessible-for-notify 1819 STATUS current 1820 DESCRIPTION 1821 "Represents authentication method for Channel." 1822 ::= { capwapNotifyVarObjects 2 } 1824 capwapChannelDownReason OBJECT-TYPE 1825 SYNTAX INTEGER { timeout(1), rekeyfailure(2), apReboot(3) } 1826 MAX-ACCESS accessible-for-notify 1827 STATUS current 1828 DESCRIPTION 1829 "Represents the reason for Channel down. 1830 The following values are supported: 1831 timeout(1) - The keep alive is timeout, 1832 rekeyfailure(2) - Rekey process is failed, channel will be 1833 broken. 1834 apReboot(3) - AC reboot WTP." 1835 ::= { capwapNotifyVarObjects 3 } 1837 capwapIdEntryNum OBJECT-TYPE 1838 SYNTAX Unsigned32 1839 MAX-ACCESS accessible-for-notify 1840 STATUS current 1841 DESCRIPTION 1842 "Represents the entry number of station id in the 1843 capwapStationIdList." 1844 REFERENCE 1845 "Section 4.6.15. of CAPWAP Protocol Specification, RFC xxx." 1846 ::= { capwapNotifyVarObjects 4 } 1848 capwapStationIdList OBJECT-TYPE 1849 SYNTAX OCTET STRING 1850 MAX-ACCESS accessible-for-notify 1851 STATUS current 1852 DESCRIPTION 1853 "Represents the list of station id." 1854 REFERENCE 1855 "Section 4.6.15. of CAPWAP Protocol Specification, RFC xxx." 1857 ::= { capwapNotifyVarObjects 5 } 1859 capwapWTPAuthenFailureReason OBJECT-TYPE 1860 SYNTAX INTEGER { 1861 keyMismatch(1), invalidCA(2), micError(3), 1862 timeout(4), unknown(8) 1863 } 1864 MAX-ACCESS accessible-for-notify 1865 STATUS current 1866 DESCRIPTION 1867 "Represents reason for WTP authorization failure. 1868 The following values are supported: 1869 keyMismatch(1) - WTP's and AC's key is not matched, 1870 invalidCA(2) - ca is not valid, 1871 micError(3) - detect MIC error, 1872 timeout(4) - WaitDTLS Timer is timeout, 1873 unknown(8) - Unknown reason." 1874 REFERENCE 1875 "Section 2.3.1. of CAPWAP Protocol Specification, RFC xxx." 1876 ::= { capwapNotifyVarObjects 6 } 1878 capwapRadioOperStatusFlag OBJECT-TYPE 1879 SYNTAX INTEGER { operable(1), inoperable(2) } 1880 MAX-ACCESS accessible-for-notify 1881 STATUS current 1882 DESCRIPTION 1883 "Represents the operation status of a radio. 1884 The following values are supported: 1885 operable(1) - To indicate radio is operable, 1886 inoperable(2) - To indicate radio is inoperable, and 1887 capwapRadioFailureReason object will 1888 give reason in details" 1889 REFERENCE 1890 "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." 1891 ::= { capwapNotifyVarObjects 7 } 1893 capwapRadioFailureReason OBJECT-TYPE 1894 SYNTAX INTEGER { 1895 hwError(1), swError(2), adminSet(3), unknown(8) 1896 } 1897 MAX-ACCESS accessible-for-notify 1898 STATUS current 1899 DESCRIPTION 1900 "Represents errors caused by configuration operation. 1901 The following values are supported 1902 hwError(1) - Radio Failure, 1903 swError(2) - Software Failure, 1904 adminSet(3) - Administratively Set, 1905 unknown(8) - Unknown reason." 1906 REFERENCE 1907 "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." 1908 ::= { capwapNotifyVarObjects 8 } 1910 capwapJoinFailureReason OBJECT-TYPE 1911 SYNTAX INTEGER { 1912 unspecified(1), resDepletion(2), unknownSource(3), 1913 incorrectData(4), sessionInUse(5), notSupportHw(6), 1914 notSupportBinding(7) 1915 } 1916 MAX-ACCESS accessible-for-notify 1917 STATUS current 1918 DESCRIPTION 1919 "The following join failure types are supported: 1920 unspecified(1) - unspecified failure reason, 1921 resDepletion(2) - Resource Depletion, 1922 unknownSource(3) - Unknown Source, 1923 incorrectData(4) - Incorrect Data, 1924 sessionInUse(5) - Session ID already in use, 1925 notSupportHw(6) - WTP Hardware not supported, 1926 notSupportBinding(7) - Binding Not Supported." 1927 REFERENCE 1928 "Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx." 1929 ::= { capwapNotifyVarObjects 9 } 1931 capwapImageFailureReason OBJECT-TYPE 1932 SYNTAX INTEGER { 1933 invalidChecksum(1), 1934 invalidLength(2), 1935 other(3), 1936 inUse(4) 1937 } 1938 MAX-ACCESS accessible-for-notify 1939 STATUS current 1940 DESCRIPTION 1941 "The following software upgrade failure types are supported: 1942 invalidChecksum(1) - Invalid Checksum, 1943 invalidLength(2) - Invalid Data Length, 1944 other(3) - Other Error, 1945 inUse(4) - Image Already Present." 1946 REFERENCE 1947 "Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx." 1948 ::= { capwapNotifyVarObjects 10 } 1950 capwapConfigMsgErrorType OBJECT-TYPE 1951 SYNTAX INTEGER { 1952 unknownElement(1), unsupportedElement(2), 1953 unknownValue(3), unsupportedValue(4) 1954 } 1955 MAX-ACCESS accessible-for-notify 1956 STATUS current 1957 DESCRIPTION 1958 "The following software upgrade failure types are supported: 1959 unknownElement(1) - Unknown Message Element, 1960 unsupportedElement(2) - Unsupported Message Element, 1961 unknownValue(3) - Unknown Message Element Value, 1962 unsupportedValue(4) - Unsupported Message Element Value." 1963 REFERENCE 1964 "Section 4.6.36. of CAPWAP Protocol Specification, RFC xxx." 1965 ::= { capwapNotifyVarObjects 11 } 1967 capwapMsgErrorElements OBJECT-TYPE 1968 SYNTAX SnmpAdminString 1969 MAX-ACCESS accessible-for-notify 1970 STATUS current 1971 DESCRIPTION 1972 "Represents the message element sent by the AC in the 1973 Configuration Status Response message that caused the error." 1974 REFERENCE 1975 "Section 4.6.36. of CAPWAP Protocol Specification, RFC xxx." 1976 ::= { capwapNotifyVarObjects 12 } 1978 -- Module compliance 1980 capwapCompliances OBJECT IDENTIFIER 1981 ::= { capwapConformance 1 } 1983 capwapGroups OBJECT IDENTIFIER 1984 ::= { capwapConformance 2 } 1986 capwapCompliance MODULE-COMPLIANCE 1987 STATUS current 1988 DESCRIPTION 1989 "Describes the requirements for conformance to the 1990 CAPWAP Base MIB." 1992 MODULE -- this module 1993 MANDATORY-GROUPS { capwapACNodeGroup, 1994 capwapWTPStateGroup, 1995 capwapWTPsGroup, 1996 capwapRadiosGroup 1997 } 1999 GROUP capwapACNodeGroup2 2000 DESCRIPTION 2001 "The capwapACNodeGroup2 group is optional." 2003 GROUP capwapWTPsGroup2 2004 DESCRIPTION 2005 "The capwapWTPsGroup2 group is optional." 2007 GROUP capwapWTPRebootStatsGroup 2008 DESCRIPTION 2009 "The capwapWTPRebootStatsGroup group is optional." 2011 GROUP capwapRadioStatsGroup 2012 DESCRIPTION 2013 "The capwapRadioStatsGroup group is optional." 2015 GROUP capwapVariablesGroup 2016 DESCRIPTION 2017 "The capwapVariablesGroup group is optional." 2019 GROUP capwapStatsGroup 2020 DESCRIPTION 2021 "The capwapStatsGroup group is optional." 2023 GROUP capwapNofificationGroup 2024 DESCRIPTION 2025 "The group capwapNofificationGroup is optional." 2027 GROUP capwapNotifyVarGroup 2028 DESCRIPTION 2029 "The capwapNotifyVarGroup group is optional. 2030 If capwapNofificationGroup is supported, 2031 this group must be implemented." 2033 OBJECT capwapWirelessBinding 2034 SYNTAX INTEGER { none(1) } 2035 DESCRIPTION 2036 "A value other than none(1) need not be supported if there is 2037 no wireless binding defined for technologies used." 2038 ::= { capwapCompliances 1 } 2040 capwapACNodeGroup OBJECT-GROUP 2041 OBJECTS { 2042 capwapWTPSessions, 2043 capwapWTPSessionsLimit, 2044 capwapStationSessions, 2045 capwapStationSessionsLimit 2046 } 2047 STATUS current 2048 DESCRIPTION 2049 "The collection of objects which are used to represent 2050 basic properties for AC from CAPWAP protocol perspective." 2051 ::= { capwapGroups 1 } 2053 capwapACNodeGroup2 OBJECT-GROUP 2054 OBJECTS { 2055 capwapDataChannelSecOptions, 2056 capwapWTPAuthenOptions, 2057 capwapWTPFallbackEnable, 2058 capwapWTPACNameList 2059 } 2060 STATUS current 2061 DESCRIPTION 2062 "The collection of objects which are used to represent 2063 other properties such as security for AC from 2064 CAPWAP protocol perspective." 2065 ::= { capwapGroups 2 } 2067 capwapWTPStateGroup OBJECT-GROUP 2068 OBJECTS { 2069 capwapWTPId, 2070 capwapWTPIPAddressType, 2071 capwapWTPIPAddress, 2072 capwapWTPPHYAddress, 2073 capwapWTPState 2074 } 2075 STATUS current 2076 DESCRIPTION 2077 "The collection of objects which are used to represent 2078 WTP state information." 2079 ::= { capwapGroups 3 } 2081 capwapWTPsGroup OBJECT-GROUP 2082 OBJECTS { 2083 capwapWTPName, 2084 capwapWTPLocation, 2085 capwapWTPBaseMACAddress, 2086 capwapWTPTunnelModeOptions, 2087 capwapWTPMACTypeOptions, 2088 capwapWTPRadiosInUseNum, 2089 capwapWTPRadioNumLimit 2090 } 2091 STATUS current 2092 DESCRIPTION 2093 "The collection of objects which are used to represent 2094 configuration and properties information for WTP 2095 in running state." 2097 ::= { capwapGroups 4 } 2099 capwapWTPsGroup2 OBJECT-GROUP 2100 OBJECTS { 2101 capwapWTPPHYIndex, 2102 capwapWTPDiscoveryType, 2103 capwapWTPStaticIPEnable, 2104 capwapWTPStaticIPType, 2105 capwapWTPStaticIP, 2106 capwapWTPNetmask, 2107 capwapWTPGateway 2108 } 2109 STATUS current 2110 DESCRIPTION 2111 "The collection of objects which are used to represent 2112 configuration and properties information for WTP 2113 in running state." 2114 ::= { capwapGroups 5 } 2116 capwapRadiosGroup OBJECT-GROUP 2117 OBJECTS { 2118 capwapRadioId, 2119 capwapWTPVirtualRadioIfIndex, 2120 capwapWirelessBinding 2121 } 2122 STATUS current 2123 DESCRIPTION 2124 "The collection of objects which are used to represent 2125 wireless binding type, the mapping relationship between 2126 'WLAN Virtual Radio Interface' and PHY radio." 2127 ::= { capwapGroups 6 } 2129 capwapStationsGroup OBJECT-GROUP 2130 OBJECTS { 2131 capwapStationAddedTime, 2132 capwapStationVlanName 2133 } 2134 STATUS current 2135 DESCRIPTION 2136 "The collection of objects which are used to represent 2137 stations' basic property." 2138 ::= { capwapGroups 7 } 2140 capwapWTPRebootStatsGroup OBJECT-GROUP 2141 OBJECTS { 2142 capwapWTPRebootCount, 2143 capwapWTPInitCount, 2144 capwapWTPLinkFailureCount, 2145 capwapWTPSwFailureCount, 2146 capwapWTPHwFailureCount, 2147 capwapWTPOtherFailureCount, 2148 capwapWTPUnknownFailureCount, 2149 capwapWTPLastFailureType 2150 } 2151 STATUS current 2152 DESCRIPTION 2153 "The collection of objects which are used for collecting 2154 WTP reboot count, link failure count, hardware failure 2155 count and so on." 2156 ::= { capwapGroups 8 } 2158 capwapRadioStatsGroup OBJECT-GROUP 2159 OBJECTS { 2160 capwapRadioResetCount, 2161 capwapRadioSwFailCount, 2162 capwapRadioHwFailCount, 2163 capwapRadioOtherFailCount, 2164 capwapRadioUnknownFailCount, 2165 capwapRadioConfigUpdateCount, 2166 capwapRadioChannelChangeCount, 2167 capwapRadioBandChangeCount, 2168 capwapRadioCurrentNoiseFloor, 2169 capwapRadioDecryptErrorCount, 2170 capwapRadioTxQueueLevel, 2171 capwapRadioRFLinkFramesCount, 2172 capwapRadioLastFailType 2173 } 2174 STATUS current 2175 DESCRIPTION 2176 "The collection of objects which are used for collecting 2177 radio reset count, channel change count, hardware failure 2178 count and so on" 2179 ::= { capwapGroups 9 } 2181 capwapVariablesGroup OBJECT-GROUP 2182 OBJECTS { 2183 capwapDataChannelDeadInterval, 2184 capwapDataCheckTimer, 2185 capwapMaxDiscoveryInterval, 2186 capwapMaxDiscoveries, 2187 capwapRetransmitInterval, 2188 capwapMaxRetransmit, 2189 capwapReportInterval 2190 } 2191 STATUS current 2192 DESCRIPTION 2193 "Objects used for CAPWAP protocol." 2194 ::= { capwapGroups 10 } 2196 capwapStatsGroup OBJECT-GROUP 2197 OBJECTS { 2198 capwapWTPRetransmitCount, 2199 capwapFailedDTLSAuthFailCount, 2200 capwapFailedDTLSSessionCount 2201 } 2202 STATUS current 2203 DESCRIPTION 2204 "Objects used for CAPWAP protocol." 2205 ::= { capwapGroups 11 } 2207 capwapNofificationGroup NOTIFICATION-GROUP 2208 NOTIFICATIONS { 2209 capwapChannelUp, 2210 capwapChannelDown, 2211 capwapDecryptErrorReport, 2212 capwapJoinFailure, 2213 capwapImageUpgradeFailure, 2214 capwapConfigMsgError, 2215 capwapRadioOperableStatus, 2216 capwapWTPAuthenticationFailure 2217 } 2218 STATUS current 2219 DESCRIPTION 2220 "Collection of notifications in this MIB." 2221 ::= { capwapGroups 12 } 2223 capwapNotifyVarGroup OBJECT-GROUP 2224 OBJECTS { 2225 capwapWTPId, 2226 capwapRadioId, 2227 capwapChannelType, 2228 capwapWTPAuthenMethod, 2229 capwapChannelDownReason, 2230 capwapIdEntryNum, 2231 capwapStationIdList, 2232 capwapWTPAuthenFailureReason, 2233 capwapRadioOperStatusFlag, 2234 capwapRadioFailureReason, 2235 capwapJoinFailureReason, 2236 capwapImageFailureReason, 2237 capwapConfigMsgErrorType, 2238 capwapMsgErrorElements 2239 } 2240 STATUS current 2241 DESCRIPTION 2242 "Objects used for notification." 2243 ::= { capwapGroups 13 } 2245 END 2247 10. Security Considerations 2249 There are a number of management objects defined in this MIB module 2250 with a MAX-ACCESS clause of read-write and/or read-create. Such 2251 objects may be considered sensitive or vulnerable in some network 2252 environments. The support for SET operations in a non-secure 2253 environment without proper protection can have a negative effect on 2254 network operations. These are the tables and objects and their 2255 sensitivity/vulnerability: 2257 o - Unauthorized changes to the capwapWTPTable, writable objects 2258 under capwapACs group may disrupt allocation of resources in the 2259 network. 2261 Some of the readable objects in this MIB module (i.e., objects with a 2262 MAX-ACCESS other than not-accessible) may be considered sensitive or 2263 vulnerable in some network environments. It is thus important to 2264 control even GET and/or NOTIFY access to these objects and possibly 2265 to even encrypt the values of these objects when sending them over 2266 the network via SNMP. These are the tables and objects and their 2267 sensitivity/vulnerability: 2269 o - The capwapWTPTable exposes WTP's important information like IP 2270 address, MAC type and so on; 2272 o - The capwapWTPRebootStatTable exposes WTP's failure information; 2274 o - The capwapRadioStatsTable exposes radio's failure information; 2276 SNMP versions prior to SNMPv3 did not include adequate security. 2277 Even if the network itself is secure (for example by using IPSec), 2278 even then, there is no control as to who on the secure network is 2279 allowed to access and GET/SET (read/change/create/delete) the objects 2280 in this MIB module. 2282 It is RECOMMENDED that implementers consider the security features as 2283 provided by the SNMPv3 framework (see [RFC3410], section 8), 2284 including full support for the SNMPv3 cryptographic mechanisms (for 2285 authentication and privacy). 2287 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2288 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2289 enable cryptographic security. It is then a customer/operator 2290 responsibility to ensure that the SNMP entity giving access to an 2291 instance of this MIB module is properly configured to give access to 2292 the objects only to those principals (users) that have legitimate 2293 rights to indeed GET or SET (change/create/delete) them. 2295 11. IANA Considerations 2297 11.1. IANA Considerations for CAPWAP-MIB 2299 The MIB module in this document uses the following IANA-assigned 2300 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 2302 Descriptor OBJECT IDENTIFIER value 2303 ---------- ----------------------- 2305 capwapMIB { mib-2 XXX } 2307 11.2. IANA Considerations for ifType 2309 Require IANA to assign a ifType for 'WTP Virtual Radio Interface' 2310 type. 2312 12. Contributors 2314 This MIB is based on contributions from Long Gao. 2316 13. Acknowledgements 2318 The authors wish to thank David Harrington, Yu Liu, Xi Yao, Sachin 2319 Dutta, Ju Wang, Yujin Zhao, Haitao Zhang. 2321 14. References 2323 14.1. Normative References 2325 [RFC2119] Bradner, S., "Key words for 2326 use in RFCs to Indicate 2327 Requirement Levels", 2328 BCP 14, RFC 2119, 2329 March 1997. 2331 [RFC2578] McCloghrie, K., Ed., 2332 Perkins, D., Ed., and J. 2333 Schoenwaelder, Ed., 2334 "Structure of Management 2335 Information Version 2 2336 (SMIv2)", STD 58, RFC 2578, 2337 April 1999. 2339 [RFC2579] McCloghrie, K., Ed., 2340 Perkins, D., Ed., and J. 2341 Schoenwaelder, Ed., 2342 "Textual Conventions for 2343 SMIv2", STD 58, RFC 2579, 2344 April 1999. 2346 [RFC2580] McCloghrie, K., Perkins, 2347 D., and J. Schoenwaelder, 2348 "Conformance Statements for 2349 SMIv2", STD 58, RFC 2580, 2350 April 1999. 2352 [RFC2863] McCloghrie, K. and F. 2353 Kastenholz, "The Interfaces 2354 Group MIB", RFC 2863, 2355 June 2000. 2357 [RFC3418] Presuhn, R., "Management 2358 Information Base (MIB) for 2359 the Simple Network 2360 Management Protocol 2361 (SNMP)", STD 62, RFC 3418, 2362 December 2002. 2364 [RFC4001] Daniele, M., Haberman, B., 2365 Routhier, S., and J. 2366 Schoenwaelder, "Textual 2367 Conventions for Internet 2368 Network Addresses", 2369 RFC 4001, February 2005. 2371 [RFC4133] Bierman, A. and K. 2372 McCloghrie, "Entity MIB 2373 (Version 3)", RFC 4133, 2374 August 2005. 2376 [I-D.ietf-capwap-protocol-specification] Calhoun, P., "CAPWAP 2377 Protocol Specification", dr 2378 aft-ietf-capwap-protocol- 2379 specification-10 (work in 2380 progress), March 2008. 2382 14.2. Informative References 2384 [RFC3410] Case, J., Mundy, R., 2385 Partain, D., and B. 2386 Stewart, "Introduction and 2387 Applicability Statements 2388 for Internet-Standard 2389 Management Framework", 2390 RFC 3410, December 2002. 2392 Authors' Addresses 2394 Yang Shi (editor) 2395 H3C Tech. Co., Ltd 2396 Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian District, 2397 Beijing 2398 China(100085) 2400 Phone: +86 010 82775276 2401 EMail: young@h3c.com 2403 David Perkins (editor) 2404 SNMPinfo 2405 288 Quailbrook Ct San Carlos, 2406 CA 94070 2407 USA 2409 Phone: +1 408 394-8702 2410 EMail: dperkins@snmpinfo.com 2412 Chris Elliott (editor) 2413 Cisco Systems, Inc. 2414 7025 Kit Creek Rd., P.O. Box 14987 Research Triangle Park 2415 27709 2416 USA 2418 Phone: +1 919-392-2146 2419 EMail: chelliot@cisco.com 2421 Puneet Agarwal (editor) 2422 Broadcom, Inc. 2424 EMail: pagarwal@broadcom.com 2426 Full Copyright Statement 2428 Copyright (C) The IETF Trust (2008). 2430 This document is subject to the rights, licenses and restrictions 2431 contained in BCP 78, and except as set forth therein, the authors 2432 retain all their rights. 2434 This document and the information contained herein are provided on an 2435 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2436 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 2437 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 2438 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 2439 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2440 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2442 Intellectual Property 2444 The IETF takes no position regarding the validity or scope of any 2445 Intellectual Property Rights or other rights that might be claimed to 2446 pertain to the implementation or use of the technology described in 2447 this document or the extent to which any license under such rights 2448 might or might not be available; nor does it represent that it has 2449 made any independent effort to identify any such rights. Information 2450 on the procedures with respect to rights in RFC documents can be 2451 found in BCP 78 and BCP 79. 2453 Copies of IPR disclosures made to the IETF Secretariat and any 2454 assurances of licenses to be made available, or the result of an 2455 attempt made to obtain a general license or permission for the use of 2456 such proprietary rights by implementers or users of this 2457 specification can be obtained from the IETF on-line IPR repository at 2458 http://www.ietf.org/ipr. 2460 The IETF invites any interested party to bring to its attention any 2461 copyrights, patents or patent applications, or other proprietary 2462 rights that may cover technology that may be required to implement 2463 this standard. Please address the information to the IETF at 2464 ietf-ipr@ietf.org.