idnits 2.17.1 draft-yangshi-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 18. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 2337. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2348. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2355. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2361. 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 are 2 instances of too long lines in the document, the longest one being 2 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 12, 2008) is 5912 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) == Unused Reference: 'RFC4181' is defined on line 2289, but no explicit reference was found in the text ** Obsolete normative reference: RFC 4133 (Obsoleted by RFC 6933) Summary: 3 errors (**), 0 flaws (~~), 3 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force Yang Shi, Ed. 3 Internet-Draft H3C Tech. Co., Ltd 4 Intended status: Standards Track Perkins, Ed. 5 Expires: August 15, 2008 SNMPinfo 6 Chris, Ed. 7 Cisco Systems, Inc. 8 February 12, 2008 10 CAPWAP Protocol Base MIB 11 draft-yangshi-capwap-base-mib-02 13 Status of This Memo 15 By submitting this Internet-Draft, each author represents that any 16 applicable patent or other IPR claims of which he or she is aware 17 have been or will be disclosed, and any of which he or she becomes 18 aware will be disclosed, in accordance with Section 6 of BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 This Internet-Draft will expire on August 15, 2008. 38 Copyright Notice 40 Copyright (C) The IETF Trust (2008). 42 Abstract 44 This memo defines a portion of the Management Information Base (MIB) 45 for use with network management protocols. In particular, it 46 describes managed objects for modeling the Control And Provisioning 47 of Wireless Access Points (CAPWAP) Protocol. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 2. The Internet-Standard Management Framework . . . . . . . . . . 3 53 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 56 6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 5 57 6.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 5 58 6.2. The capwapObjects Subtree . . . . . . . . . . . . . . . . 7 59 6.3. The capwapConformance Subtree . . . . . . . . . . . . . . 7 60 6.4. The capwapNotifications Subtree . . . . . . . . . . . . . 7 61 6.5. Brief Description of MIB Objects . . . . . . . . . . . . . 7 62 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 8 63 7.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 8 64 7.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 8 65 7.3. Relationship to the ENTITY-MIB . . . . . . . . . . . . . . 10 66 7.4. Relationship to MIB standards of other SDOs . . . . . . . 10 67 7.5. MIB modules required for IMPORTS . . . . . . . . . . . . . 10 68 8. Example of CAPWAP-MIB Usage . . . . . . . . . . . . . . . . . 10 69 9. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 12 70 10. Security Considerations . . . . . . . . . . . . . . . . . . . 46 71 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 47 72 11.1. IANA Considerations for CAPWAP-MIB . . . . . . . . . . . . 47 73 11.2. IANA Considerations for ifType . . . . . . . . . . . . . . 47 74 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 47 75 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 47 76 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 47 77 14.1. Normative References . . . . . . . . . . . . . . . . . . . 47 78 14.2. Informative References . . . . . . . . . . . . . . . . . . 49 80 1. Introduction 82 Current work is under way in the IETF to specify the CAPWAP Protocol 83 [I-D.ietf-capwap-protocol-specification], which enables an Access 84 Controller (AC) to manage a collection of Wireless Termination Points 85 (WTPs) 87 This document defines a MIB module that can be used to manage CAPWAP 88 implementations. This MIB module covers both configuration and WTP 89 status-monitoring aspects of CAPWAP, and provides a way to reuse 90 current MIB standards and future extensions for any wireless binding 91 technology. 93 2. The Internet-Standard Management Framework 95 For a detailed overview of the documents that describe the current 96 Internet-Standard Management Framework, please refer to section 7 of 97 RFC 3410 [RFC3410]. 99 Managed objects are accessed via a virtual information store, termed 100 the Management Information Base or MIB. MIB objects are generally 101 accessed through the Simple Network Management Protocol (SNMP). 102 Objects in the MIB are defined using the mechanisms defined in the 103 Structure of Management Information (SMI). This memo specifies a MIB 104 module that is compliant to the SMIv2, which is described in STD 58, 105 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 106 [RFC2580]. 108 3. Terminology 110 This document uses terminology from the document describing the 111 CAPWAP Protocol specification [I-D.ietf-capwap-protocol- 112 specification]. WTPs are viewed as remote RF interfaces controlled 113 by the AC via CAPWAP protocol. The CAPWAP protocol supports two 114 modes of operation: Split and Local MAC. In Split MAC mode all L2 115 wireless data and management frames are encapsulated via the CAPWAP 116 protocol and exchanged between the AC and the WTP. The Local MAC 117 mode of operation allows for the data frames to be either locally 118 bridged, or tunneled as 802.3 frames. From AC, operator could 119 centrally control WTPs configuration and monitor their status. 120 CAPWAP use DTLS protocol to implement control channel security. 122 4. Conventions 124 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 125 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 126 document are to be interpreted as described in RFC 2119 [RFC2119]. 128 5. Overview 130 The CAPWAP Protocol MIB module (CAPWAP-MIB) have the following design 131 objectives: 133 - To work well under centralized architectures, and provide a way to 134 centrally manage and control wireless network by SNMP 136 - To be consistent with CAPWAP protocol 138 - To reuse current MIB standards and future extensions for a wireless 139 binding technology 141 - To enable interoperability between vendors 143 - To meet operator requirements for centralized architectures 145 The basic idea of CAPWAP-MIB is: 147 - The SNMP agent run on the AC side, and it MAY not be required on 148 the WTP side. It follows same idea as CAPWAP protocol: Centralized 149 Control 151 - As a generic mechanism, it is independent of any wireless binding 152 technologies and defined by a independent MIB file 154 - To be independent of any wireless binding technologies and have 155 ability to reuse MIB standards of other SDOs, is the main challenge 156 for design of the MIB 158 - The ifIndex [RFC2863] will play a role in bridging between MIB 159 standards defined by different SDOs 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 173 - The MIB module provides the information of AC, WTPs, radio and 174 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-MIB module, it will introduce how 185 CAPWAP-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 oprepare configuration at 188 AC side 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 identifer 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 import, and the key point is to reuse the idea of ifIndex. So it is 202 required a way to maintain the mapping relationship between "WTP id + 203 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 WTP or AC). AC can have 206 interfaces of "WTP Virtual Radio Interface" ifType, it will logically 207 represents PHY radios on the WTPs side. It looks like that PHY 208 radios are located on the AC side, 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 218 6.1. Textual Conventions 220 The following textual conventions are defined: 222 CapwapWTPId ::= TEXTUAL-CONVENTION 223 STATUS current 224 DESCRIPTION 225 "Represents a unique identifier of a WTP instance. 226 As usual, a serial number of WTP will be used." 227 SYNTAX OCTET STRING(SIZE(128)) 229 CapwapStationId ::= TEXTUAL-CONVENTION 230 STATUS current 231 DESCRIPTION 232 "Represents a unique identifier of a station instance. 233 As usual, the MAC address of station will be used." 234 SYNTAX OCTET STRING (SIZE (6)) 236 CapwapRadioId ::= TEXTUAL-CONVENTION 237 STATUS current 238 DESCRIPTION 239 "Represents a unique identifier of a radio on a WTP." 240 SYNTAX Unsigned32 (1..4294967295) 242 CapwapWTPTunnelMode ::= TEXTUAL-CONVENTION 243 STATUS current 244 DESCRIPTION 245 "Represents the tunneling mode for station data that are 246 supported by the WTP. 247 The possible value could be: 248 localBridging(1) - Local Bridging Mode, 249 dot3Tunnel(2) - 802.3 Frame Tunnel Mode, 250 nativeTunnel(3) - Native Frame Tunnel Mode." 251 REFERENCE 252 "Section 4.6.41. of CAPWAP Protocol Specification, RFC xxx." 253 SYNTAX INTEGER { localBridging(1), dot3Tunnel(2), 254 nativeTunnel(3) } 256 CapwapWTPMACType ::= TEXTUAL-CONVENTION 257 STATUS current 258 DESCRIPTION 259 "Represents the MAC mode of operation supported by the WTP. 260 The possible value could be: 261 localMAC(1) - Local-MAC Mode, 262 splitMAC(2) - Split-MAC Mode." 263 REFERENCE 264 "Section 4.6.44. of CAPWAP Protocol Specification, RFC xxx." 265 SYNTAX INTEGER { localMAC(1), splitMAC(2) } 267 CapwapChannelType::= TEXTUAL-CONVENTION 268 STATUS current 269 DESCRIPTION 270 "Represents the channel type for CAPWAP protocol. 272 The following values are supported: 273 data(1) - data Channel 274 control(2) - control Channel." 275 SYNTAX INTEGER { data(1), control(2) } 277 CapwapWTPAuthenMethod ::= TEXTUAL-CONVENTION 278 STATUS current 279 DESCRIPTION 280 "Represents the authentication credential type 281 for WTP. 282 The following values are supported: 283 clear(1) - clear text and no authentication, 284 x509(2) - X.509 Certificate Based, 285 psk(3) - Pre-Shared Secret, 286 other(8) - Other method, for example, vendor specific. 287 As mandatory requirement, CAPWAP control channel 288 authentication should use DTLS, and either by certificate or 289 PSK. For data channel, DTLS is optional." 290 SYNTAX INTEGER { clear(1), x509(2), psk(3), other(8) } 292 6.2. The capwapObjects Subtree 294 The subtree provides information for statistic data and configuration 295 parameters of WTP and radio. 297 6.3. The capwapConformance Subtree 299 The subtree provides conformance information of MIB objects. 301 6.4. The capwapNotifications Subtree 303 The subtree describe the notifications defined in the MIB module, and 304 their purpose. 306 6.5. Brief Description of MIB Objects 308 The MIB objects were derived from the CAPWAP protocol document 309 [I-D.ietf- capwap-protocol-specification]. 311 1) capwapWTPStateTable 313 The WTPs status table is used to indicate each WTP's CAPWAP FSM 314 state. 316 2) capwapWTPTable 318 The WTPs table is used for providing property and configuration 319 information in details for WTPs in running state. 321 3) capwapRadioBindTable 323 The radio bind table is used to indicate the mapping relationship 324 between logical interface of "WTP Virtual Radio Interface" ifType and 325 PHY radio. 327 4) capwapStationTable 329 The station table is used for providing stations' basic property 330 information. 332 5) capwapWTPRebootStatsTable 334 The WTP reboot statistic table is used for collecting WTP reboot 335 count, link failure count, hardware failure count and so on. 337 6) capwapRadioStatsTable 339 The WTP radio statistic table is used for collecting radio reset 340 count, channel change count, hardware failure count and so on. 342 7. Relationship to Other MIB Modules 344 7.1. Relationship to the SNMPv2-MIB 346 The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being 347 mandatory for all systems, and the objects apply to the entity as a 348 whole. The 'system' group provides identification of the management 349 entity and certain other system-wide data. The CAPWAP-MIB does not 350 duplicate those objects. 352 7.2. Relationship to the IF-MIB 354 The Interfaces Group [RFC2863] defines generic managed objects for 355 managing interfaces. This memo contains the media-specific 356 extensions to the Interfaces Group for managing WTP radio object that 357 are modeled as interfaces. 359 IF-MIB is required to support on the AC side. For each PHY radio at 360 WTP side, it will have a logical interface of 'WTP Virtual Radio 361 Interface' ifType at AC side. The ifIndex of interface will 362 represent PHY radio by logical. The interface SHOULD be modeled as 363 an ifEntry and provide appropriate interface information. 365 Some specific interpretations of ifTable for CAPWAP-MIB are as 366 follow. 368 Object Use for the CAPWAP MIB. 370 ifIndex Each interface of 'WTP Virtual Radio Interface' type 371 maybe be represented by an ifEntry. 373 ifDescr Description of the interface of 'WTP Virtual Radio 374 Interface' ifType. 376 ifType IANAifType of 'WTP Virtual Radio Interface'. 378 ifName Textual name (unique on this system) of the interface 379 or an octet string of zero length. 381 ifAlias The nonvolatile 'alias' name for the interface, as 382 specified by a network manager. 384 ifPhysAddress The physical address of the interface; i.e., 385 BSSID of a 802.11 radio. 387 ifAdminStatus This variable indicates the operator's intent as 388 to whether PHY should be enabled, disabled, or 389 running in some diagnostic testing mode on this 390 interface. 391 Also see [RFC2863]. 393 ifOperStatus This value reflects the actual or operational status 394 of radio. 395 Also see [RFC2863]. 397 ifLastChange The value of sysUpTime at the time the interface 398 entered its current operational state. 399 Also see [RFC2863]. 401 ifInOctets The number of received octets over the interface; 402 i.e., the number of octets received as 802.11 frames. 404 ifOutOctets The number of transmitted octets over the interface; 405 i.e., the number of octets transmitted as 802.11 406 frames. 408 ifInErrors The number of frames dropped due to 409 uncorrectable errors. 411 ifInUnknownProtos 412 The number of received frame discarded during 413 frame header validation, including frames with 414 unrecognized label values. 416 ifOutErrors See [RFC2863]. 418 7.3. Relationship to the ENTITY-MIB 420 The ENTITY-MIB [RFC4133] meets need for a standardized way of 421 representing a single agent, which supports multiple instances of one 422 MIB. It could express a certain relationship between multiple 423 entities, and provide entity properties for each entity. 425 Under the wireless centralized architectures, the SNMP agent will run 426 on the AC side, and not required on the WTP side. By the ENTITY-MIB 427 on the AC side, it could keep entity information of AC and WTPs. 428 From the ENTITY-MIB perspective, the overall physical entity (AC) is 429 a "compound" of multiple physical entities (WTPs which connects to 430 AC), all entities are identified by Physical index. In the 431 capwapWTPTable of CAPWAP-MIB, it uses capwapWTPPHYIndex object to 432 keep the mapping relationship of WTP object between CAPWAP-MIB and 433 ENTITY-MIB. 435 7.4. Relationship to MIB standards of other SDOs 437 The MIB standards (such as IEEE 802.11 MIB) of a wireless binding is 438 required to support on the AC side. The CAPWAP-MIB module is able to 439 support any wireless binding technology. Through ifIndex of 'WTP 440 Virtual Radio Interface' ifType, it provides consistent and abstract 441 way of reusing MIB objects of a wireless binding technology. 443 7.5. MIB modules required for IMPORTS 445 The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], 446 SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863], INET- 447 ADDRESS-MIB [RFC4001] and ENTITY-MIB [RFC4133]. 449 8. Example of CAPWAP-MIB Usage 451 With the idea of "WTP Virtual Radio Interface" in the mind, the 452 usage of MIB will be easily understood. Here takes IEEE 802.11 453 binding technology as an example. 455 1) Identify each PHY radio by "WTP Virtual Radio Interface" 456 According to [I-D.ietf-capwap-protocol-specification], each radio on 457 a WTP will be identified by a radio Id. Each WTP could be identified 458 by its serial number. 459 When configuration for a WTP is prepared before a WTP connects to AC, 460 the following information is available in the CapwapRadioBindTable. 461 In CapwapRadioBindTable 462 { 463 capwapWTPId = 12345678 464 capwapRadioId = 1 465 capwapWTPVirtualRadioifIndex = 10, 466 capwapWirelessBinding = dot11(2), 467 } 468 Suppse WTP's serial number is 12345678, and first radio id is 1. 469 At AC side, the ifIndex of interface in "WTP Virtual Radio Interface" 470 ifType is 10 which represents the PHY radio 1. 471 By the mechanism of "WTP Virtual Radio Interface", it seemed that WTP 472 PHY radios are located at AC side. 473 The interface of "WTP Virtual Radio Interface" ifType is modeled by 474 ifTable. 475 In ifTable 476 { 477 ifIndex = 10, 478 ifDescr = "WTP Virtual Radio Interface", 479 ifType = IANAifType of "WTP Virtual 480 Radio Interface", 481 ifMtu = 0, 482 ifSpeed = 0, 483 ifPhysAddress = 0.0.0.0.0.0, 484 ifAdminStatus = true, 485 ifOperStatus = false, 486 ifLastChange = 0, 487 ifInOctets = 0, 488 ifInUcastPkts = 0, 489 ifInDiscards = 0, 490 ifInErrors = 0, 491 ifInUnknownProtos = 0, 492 ifOutOctets = 0, 493 ifOutUcastPkts = 0, 494 ifOutDiscards = 0, 495 ifOutErrors = 0, 496 } 498 2) Configure specific wireless binding parameters for "WTP Virtual 499 Radio Interface" 500 It will be done at the AC side through specific wireless binding MIB 501 such as IEEE 802.11 MIB. 502 For example, to configure parameter for "WTP Virtual Radio Interface" 503 by 802.11 Dot11OperationTable. 504 In Dot11OperationTable 505 { 506 ifIndex = 10, 507 dot11MACAddress = 0.0.0.0.0.0, 508 dot11RTSThreshold = 2347, 509 dot11ShortRetryLimit = 7, 510 dot11LongRetryLimit = 4, 511 dot11FragmentationThreshold = 256, 512 dot11MaxTransmitMSDULifetime = 512, 513 dot11MaxReceiveLifetime = 512, 514 dot11ManufacturerID = "capwap", 515 dot11ProductID = "capwap" 516 } 517 In the example, it suppose ifIndex of an interface in 518 "WTP Virtual Radio Interface" ifType is 10. 520 3) Other configurations for a specific wireless binding 521 For example, WLAN service configuration will be done through CAPWAP 522 binding MIB and IEEE 802.11 MIB. In the CAPWAP 802.11 binding MIB 523 draft, it will give more explain. 525 4) WTP reports its current configuration status 526 After join phase and before WTP get configuration from AC, it will 527 report its current configuration status to AC through configuration 528 status message. The data of MIB objects will be updated at AC side. 529 For example, for 802.11 binding, WTP will update data in the 530 ifTable and IEEE 802.11 MIB so on according to message content. 531 As an example for ifIndex 10, its ifOperStatus in ifTable will be 532 updated according to current radio operational status in the 533 CAPWAP message. 535 5) Query WTP and radio statistics data 536 After WTPs come to run status, operator could query WTP and 537 radio statistics data through CAPWAP-MIB and specific binding MIB. 538 For example, through dot11CountersTable in the IEEE 802.11 MIB, 539 operator could query counter data for radio which is identified 540 by ifIndex of a virtual radio interface. With capwapACState table 541 in the MIB, operator could query configuration and properties of 542 WTPs which are in run status. 544 6) Query other statistics data of a specific wireless binding 545 For example, operator could query the statistics data of 546 WLAN service through 802.11 binding MIB and IEEE 802.11 MIB. 547 In the CAPWAP 802.11 binding MIB draft, it will give more explain. 549 7) Query other properties of WTP 550 Operator could query MIB objects in the ENTITY-MIB by capwapWTPPHYIndex 551 in the capwapWTPTable of CAPWAP-MIB. The properties of WTP such as 552 software version, hardware version and so on are available in the 553 ENTITY-MIB. 555 9. Definitions 557 CAPWAP-MIB DEFINITIONS ::= BEGIN 559 IMPORTS 560 PhysAddress, TEXTUAL-CONVENTION, TruthValue, 561 DateAndTime 562 FROM SNMPv2-TC 563 InterfaceIndex 564 FROM IF-MIB 565 PhysicalIndex 566 FROM ENTITY-MIB 567 SnmpAdminString 568 FROM SNMP-FRAMEWORK-MIB 569 NOTIFICATION-GROUP, OBJECT-GROUP, MODULE-COMPLIANCE 570 FROM SNMPv2-CONF 571 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2, 572 Integer32, Unsigned32, Counter32 573 FROM SNMPv2-SMI 574 InetAddressType, InetAddress 575 FROM INET-ADDRESS-MIB; 577 capwapMIB MODULE-IDENTITY 578 LAST-UPDATED "200802120000Z" -- Feb 12, 2008 579 ORGANIZATION "IETF Control And Provisioning of Wireless Access 580 Points (CAPWAP) Working Group 581 http://www.ietf.org/html.charters/capwap-charter.html" 582 CONTACT-INFO 583 "General Discussion: capwap@frascone.com 584 To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap 586 Yang Shi 587 H3C, Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian 588 District,Beijing,China(100085) 589 Email: young@h3c.com 591 David T. Perkins 592 228 Bayview Dr 593 San Carlos, CA 94070 594 USA 595 Phone: +1 408 394-8702 596 Email: dperkins@snmpinfo.com 598 Chris Elliott 599 Cisco Systems, Inc. 600 7025 Kit Creek Rd., P.O. Box 14987 601 Research Triangle Park 27709 602 USA 603 Phone: +1 919-392-2146 604 Email: chelliot@cisco.com" 606 DESCRIPTION 607 "Copyright (C) 2008 The Internet Society. This version of 608 the MIB module is part of RFC xxx; see the RFC itself 609 for full legal notices. 611 This MIB module contains managed object definitions for 612 the CAPWAP Protocol." 613 REVISION "200802120000Z" 614 DESCRIPTION 615 "Initial version published as RFC xxx" 616 ::= { mib-2 xxx } 618 -- Textual Conventions 620 CapwapWTPId ::= TEXTUAL-CONVENTION 621 STATUS current 622 DESCRIPTION 623 "Represents a unique identifier of a WTP instance. 624 As usual, a serial number of WTP will be used." 625 SYNTAX OCTET STRING(SIZE(128)) 627 CapwapStationId ::= TEXTUAL-CONVENTION 628 STATUS current 629 DESCRIPTION 630 "Represents a unique identifier of a station instance. 631 As usual, the MAC address of station will be used." 632 SYNTAX OCTET STRING (SIZE (6)) 634 CapwapRadioId ::= TEXTUAL-CONVENTION 635 STATUS current 636 DESCRIPTION 637 "Represents a unique identifier of a radio on a WTP." 638 SYNTAX Unsigned32 (1..4294967295) 640 CapwapWTPTunnelMode ::= TEXTUAL-CONVENTION 641 STATUS current 642 DESCRIPTION 643 "Represents the tunneling mode for station data that are 644 supported by the WTP. 645 The possible value could be: 646 localBridging(1) - Local Bridging Mode, 647 dot3Tunnel(2) - 802.3 Frame Tunnel Mode, 648 nativeTunnel(3) - Native Frame Tunnel Mode." 649 REFERENCE 650 "Section 4.6.41. of CAPWAP Protocol Specification, RFC xxx." 651 SYNTAX INTEGER { localBridging(1), dot3Tunnel(2), 652 nativeTunnel(3) } 654 CapwapWTPMACType ::= TEXTUAL-CONVENTION 655 STATUS current 656 DESCRIPTION 657 "Represents the MAC mode of operation supported by the WTP. 658 The possible value could be: 659 localMAC(1) - Local-MAC Mode, 660 splitMAC(2) - Split-MAC Mode." 661 REFERENCE 662 "Section 4.6.44. of CAPWAP Protocol Specification, RFC xxx." 663 SYNTAX INTEGER { localMAC(1), splitMAC(2) } 665 CapwapChannelType::= TEXTUAL-CONVENTION 666 STATUS current 667 DESCRIPTION 668 "Represents the channel type for CAPWAP protocol. 669 The following values are supported: 670 data(1) - data Channel 671 control(2) - control Channel." 672 SYNTAX INTEGER { data(1), control(2) } 674 CapwapWTPAuthenMethod ::= TEXTUAL-CONVENTION 675 STATUS current 676 DESCRIPTION 677 "Represents the authentication credential type 678 for WTP. 679 The following values are supported: 680 clear(1) - cleartext and no authentication, 681 x509(2) - X.509 Certificate Based, 682 psk(3) - Pre-Shared Secret, 683 other(8) - Other method, for example, vendor specific. 684 As mandatory requirement, CAPWAP control channel 685 authentication should use DTLS, and either by certificate or 686 PSK. For data channel, DTLS is optional." 687 SYNTAX INTEGER { clear(1), x509(2), psk(3), other(8) } 689 -- Top level components of this MIB 691 -- Notifications 692 capwapNotifications OBJECT IDENTIFIER 693 ::= { capwapMIB 0 } 694 -- Tables, Scalars 695 capwapObjects OBJECT IDENTIFIER 696 ::= { capwapMIB 1 } 697 -- Conformance 698 capwapConformance OBJECT IDENTIFIER 699 ::= { capwapMIB 2 } 701 -- AC Objects Group 702 capwapAC OBJECT IDENTIFIER 703 ::= { capwapObjects 1 } 705 capwapWTPSessions OBJECT-TYPE 706 SYNTAX Unsigned32 707 MAX-ACCESS read-only 708 STATUS current 709 DESCRIPTION 710 "Represents the total number of WTPs which are connecting to 711 AC." 712 REFERENCE 713 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 714 ::= { capwapAC 1 } 716 capwapWTPSessionsLimit OBJECT-TYPE 717 SYNTAX Unsigned32 718 MAX-ACCESS read-only 719 STATUS current 720 DESCRIPTION 721 "Represents the maximum number of WTP sessions supported by 722 the AC." 723 REFERENCE 724 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 725 ::= { capwapAC 2 } 727 capwapStationSessions OBJECT-TYPE 728 SYNTAX Unsigned32 729 MAX-ACCESS read-only 730 STATUS current 731 DESCRIPTION 732 "Represents the total number of stations which are accessing 733 the wireless service." 734 REFERENCE 735 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 736 ::= { capwapAC 3 } 738 capwapStationSessionsLimit OBJECT-TYPE 739 SYNTAX Unsigned32 740 MAX-ACCESS read-only 741 STATUS current 742 DESCRIPTION 743 "Represents the maximum number of station sessions supported by 744 the AC." 745 REFERENCE 746 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 747 ::= { capwapAC 4 } 749 capwapDataChannelSecOptions OBJECT-TYPE 750 SYNTAX Integer32 751 MAX-ACCESS read-only 752 STATUS current 753 DESCRIPTION 754 "Represents the security policy supported for CAPWAP data 755 channel. 756 The AC MAY support more than one option, represented by the bit 757 field below. 758 clear(1) - Clear Text, 759 dtls(2) - DTLS, 760 vendor(3) - vendor specific." 761 REFERENCE 762 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 763 ::= { capwapAC 5 } 765 capwapWTPAuthenOptions OBJECT-TYPE 766 SYNTAX Integer32 767 MAX-ACCESS read-only 768 STATUS current 769 DESCRIPTION 770 "Represents the authentication credentia type supported by the 771 AC for control channel. 772 The AC MAY support more than one option, represented by the bit 773 field below. 774 x509(1) - X.509 Certificate Based 775 psk(2) - Pre-Shared Secret." 776 REFERENCE 777 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 778 ::= { capwapAC 6 } 780 capwapWTPFallbackEnable OBJECT-TYPE 781 SYNTAX TruthValue 782 MAX-ACCESS read-write 783 STATUS current 784 DESCRIPTION 785 "Represents enable or disable automatic CAPWAP fallback in the 786 event that a WTP detects its preferred AC, and is not currently 787 connected to it." 788 REFERENCE 789 "Section 4.6.40. of CAPWAP Protocol Specification, RFC xxx." 790 ::= { capwapAC 7 } 792 capwapWTPACNameList OBJECT-TYPE 793 SYNTAX OCTET STRING(SIZE(256)) 794 MAX-ACCESS read-write 795 STATUS current 796 DESCRIPTION 797 "Represents the name list of ACs and use semicolon to separate AC 798 name. The AC name could be configured with the order of 799 Primary AC, secondary AC and so on. WTP will try to connect to 800 AC name in the list one by one till it connected to one AC." 801 REFERENCE 802 "Section 4.6.5. of CAPWAP Protocol Specification, RFC xxx." 803 ::= { capwapAC 8 } 805 capwapMaxFailedDTLSSessionRetry OBJECT-TYPE 806 SYNTAX Unsigned32 807 MAX-ACCESS read-only 808 STATUS current 809 DESCRIPTION 810 "Represents the maximum number of failed DTLS session 811 establishment attempts before the CAPWAP device enters a silent 812 period." 813 REFERENCE 814 "Section 4.7.7. of CAPWAP Protocol Specification, RFC xxx." 815 ::= { capwapAC 9 } 817 capwapWTPIdleTimeout OBJECT-TYPE 818 SYNTAX Unsigned32 819 UNITS "kbtyes" 820 MAX-ACCESS read-only 821 STATUS current 822 DESCRIPTION 823 "Represents the time out parameter for WTP idle state." 824 REFERENCE 825 "Section 4.8.5. of CAPWAP Protocol Specification, RFC xxx." 826 ::= { capwapAC 10 } 828 capwapWTPMaxDiscoveries OBJECT-TYPE 829 SYNTAX Unsigned32 830 MAX-ACCESS read-only 831 STATUS current 832 DESCRIPTION 833 "Represents the maximum number of Discovery Request messages 834 that will be sent after a WTP boots" 835 REFERENCE 836 "Section 4.8.6. of CAPWAP Protocol Specification, RFC xxx." 837 ::= { capwapAC 11 } 839 capwapWTPMaxRetransmit OBJECT-TYPE 840 SYNTAX Unsigned32 841 MAX-ACCESS read-only 842 STATUS current 843 DESCRIPTION 844 "Represent the maximum number of retransmission for a given 845 CAPWAP packet before the link layer considers the peer dead." 847 REFERENCE 848 "Section 4.8.7. of CAPWAP Protocol Specification, RFC xxx." 849 ::= { capwapAC 12 } 851 capwapWTPReportInterval OBJECT-TYPE 852 SYNTAX Unsigned32 853 UNITS "second" 854 MAX-ACCESS read-only 855 STATUS current 856 DESCRIPTION 857 "Represents the interval for WTP send report." 858 REFERENCE 859 "Section 4.8.8. of CAPWAP Protocol Specification, RFC xxx." 860 ::= { capwapAC 13 } 862 -- End of AC Objects Group 864 -- WTP Objects Group 866 capwapWTPs OBJECT IDENTIFIER 867 ::= { capwapObjects 2 } 869 -- capwapWTPStateTable table 871 capwapWTPStateTable OBJECT-TYPE 872 SYNTAX SEQUENCE OF CapwapWTPStateEntry 873 MAX-ACCESS not-accessible 874 STATUS current 875 DESCRIPTION 876 "A table of objects that display WTPs in different 877 CAPWAP FSM state." 878 ::= { capwapWTPs 1 } 880 capwapWTPStateEntry OBJECT-TYPE 881 SYNTAX CapwapWTPStateEntry 882 MAX-ACCESS not-accessible 883 STATUS current 884 DESCRIPTION 885 "A set of objects that display WTPs in different 886 CAPWAP FSM state." 887 INDEX { capwapWTPId } 888 ::= { capwapWTPStateTable 1 } 890 CapwapWTPStateEntry ::= SEQUENCE { 891 capwapWTPId CapwapWTPId, 892 capwapWTPIPAddressType InetAddressType, 893 capwapWTPIPAddress InetAddress, 894 capwapWTPPHYAddress PhysAddress, 895 capwapWTPState INTEGER } 897 capwapWTPId OBJECT-TYPE 898 SYNTAX CapwapWTPId 899 MAX-ACCESS accessible-for-notify 900 STATUS current 901 DESCRIPTION 902 "Represents the unique identifier of a WTP." 903 ::= { capwapWTPStateEntry 1 } 905 capwapWTPIPAddressType OBJECT-TYPE 906 SYNTAX InetAddressType 907 MAX-ACCESS read-only 908 STATUS current 909 DESCRIPTION 910 "Represents the type of IP address of WTP." 911 ::= { capwapWTPStateEntry 2 } 913 capwapWTPIPAddress OBJECT-TYPE 914 SYNTAX InetAddress 915 MAX-ACCESS read-only 916 STATUS current 917 DESCRIPTION 918 "Represents the IP address(IPv4 or IPv6) of a WTP." 919 ::= { capwapWTPStateEntry 3 } 921 capwapWTPPHYAddress OBJECT-TYPE 922 SYNTAX PhysAddress 923 MAX-ACCESS read-only 924 STATUS current 925 DESCRIPTION 926 "Represents the PHY address of a WTP." 927 ::= { capwapWTPStateEntry 4 } 929 capwapWTPState OBJECT-TYPE 930 SYNTAX INTEGER { 931 dtls(1), join(2), image(3), configure(4), 932 run(5), clear(6), unknown(7) 933 } 934 MAX-ACCESS read-only 935 STATUS current 936 DESCRIPTION 937 "Represents the various possible CAPWAP FSM states of WTP 938 The following values are supported: 939 dtls(1) - DTLS negotiation process 940 join(2) - WTP is joining with AC, 941 image(3) - WTP is downloading software, 942 configure(4) - WTP is getting configuration from AC, 943 run(5) - WTP comes to run state, 944 clear(6) - WTP recoveries default configuration. 945 unknown(7) - Operator already prepare configuration 946 for WTP, while WTP has not contact with AC 947 till now." 948 REFERENCE 949 "Section 2.3.1. of CAPWAP Protocol Specification, RFC xxx." 950 ::= { capwapWTPStateEntry 5 } 952 -- End of capwapWTPStateTable Table 954 -- capwapWTPTable Table 956 capwapWTPTable OBJECT-TYPE 957 SYNTAX SEQUENCE OF CapwapWTPEntry 958 MAX-ACCESS not-accessible 959 STATUS current 960 DESCRIPTION 961 "A table of objects that display and control WTPs in 962 running state. Values of all read-write objects in this 963 table are persistent at restart/reboot." 964 ::= { capwapWTPs 2 } 966 capwapWTPEntry OBJECT-TYPE 967 SYNTAX CapwapWTPEntry 968 MAX-ACCESS not-accessible 969 STATUS current 970 DESCRIPTION 971 "A set of objects that display and control a WTP in 972 running state." 973 INDEX { capwapWTPCurrId } 974 ::= { capwapWTPTable 1 } 976 CapwapWTPEntry ::= SEQUENCE { 977 capwapWTPCurrId CapwapWTPId, 978 capwapWTPPHYIndex PhysicalIndex, 979 capwapWTPName SnmpAdminString, 980 capwapWTPLocation SnmpAdminString, 981 capwapWTPBaseMACAddress PhysAddress, 982 capwapWTPTunnelModeOptions CapwapWTPTunnelMode, 983 capwapWTPMACTypeOptions CapwapWTPMACType, 984 capwapWTPDiscoveryType INTEGER, 985 capwapWTPRadiosInUseNum Unsigned32, 986 capwapWTPRadioNumLimit Unsigned32, 987 capwapWTPStaticIPEnable TruthValue, 988 capwapWTPStaticIPType InetAddressType, 989 capwapWTPStaticIP InetAddress, 990 capwapWTPNetmask InetAddress, 991 capwapWTPGateway InetAddress } 993 capwapWTPCurrId OBJECT-TYPE 994 SYNTAX CapwapWTPId 995 MAX-ACCESS not-accessible 996 STATUS current 997 DESCRIPTION 998 "Represents the unique identifier of a WTP Which is 999 in running state." 1000 ::= { capwapWTPEntry 1 } 1002 capwapWTPPHYIndex OBJECT-TYPE 1003 SYNTAX PhysicalIndex 1004 MAX-ACCESS read-only 1005 STATUS current 1006 DESCRIPTION 1007 "Represents the unique physical index of a physical entity 1008 in the ENTITY-MIB. The information such as software version 1009 of specific WTP could be accessed through the index." 1010 ::= { capwapWTPEntry 2 } 1012 capwapWTPName OBJECT-TYPE 1013 SYNTAX SnmpAdminString 1014 MAX-ACCESS read-write 1015 STATUS current 1016 DESCRIPTION 1017 "Represents the name of a WTP." 1018 REFERENCE 1019 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 1020 ::= { capwapWTPEntry 3 } 1022 capwapWTPLocation OBJECT-TYPE 1023 SYNTAX SnmpAdminString 1024 MAX-ACCESS read-write 1025 STATUS current 1026 DESCRIPTION 1027 "Represents the location of a WTP." 1028 REFERENCE 1029 "Section 4.6.28. of CAPWAP Protocol Specification, RFC xxx." 1030 ::= { capwapWTPEntry 4 } 1032 capwapWTPBaseMACAddress OBJECT-TYPE 1033 SYNTAX PhysAddress 1034 MAX-ACCESS read-only 1035 STATUS current 1036 DESCRIPTION 1037 "Represents the WTP's Base MAC Address, which MAY be assigned 1038 to the primary Ethernet interface." 1039 REFERENCE 1040 "Section 4.6.38. of CAPWAP Protocol Specification, RFC xxx." 1041 ::= { capwapWTPEntry 5 } 1043 capwapWTPTunnelModeOptions OBJECT-TYPE 1044 SYNTAX CapwapWTPTunnelMode 1045 MAX-ACCESS read-only 1046 STATUS current 1047 DESCRIPTION 1048 "Represents the tunneling modes for station data that are 1049 supported by the WTP. 1050 The WTP MAY support more than one option, represented by the 1051 bit field below. 1052 localBridging(1) - Local Bridging Mode, 1053 dot3Tunnel(2) - 802.3 Frame Tunnel Mode, 1054 nativeTunnel(3) - Native Frame Tunnel Mode." 1055 REFERENCE 1056 "Section 4.6.41. of CAPWAP Protocol Specification, RFC xxx." 1057 ::= { capwapWTPEntry 6 } 1059 capwapWTPMACTypeOptions OBJECT-TYPE 1060 SYNTAX CapwapWTPMACType 1061 MAX-ACCESS read-only 1062 STATUS current 1063 DESCRIPTION 1064 "Represents the MAC mode of operation supported by the WTP. 1065 The WTP MAY support more than one option, represented by the 1066 bit field below. 1067 localMAC(1) - Local-MAC Mode, 1068 splitMAC(2) - Split-MAC Mode." 1069 REFERENCE 1070 "Section 4.6.44. of CAPWAP Protocol Specification, RFC xxx." 1071 ::= { capwapWTPEntry 7 } 1073 capwapWTPDiscoveryType OBJECT-TYPE 1074 SYNTAX INTEGER { 1075 unknown(1), staticConfig(2), dhcp(3), dns(4), acRef(5) 1076 } 1077 MAX-ACCESS read-only 1078 STATUS current 1079 DESCRIPTION 1080 "Represents how WTP discovered the AC. 1081 The following values are supported: 1082 unknown(1) - the method is unknown, 1083 staticConfig(2) - static IP configuration, 1084 dhcp(3) - DHCP, 1085 dns(4) - DNS, 1086 acRef(5) - AC Referral." 1087 REFERENCE 1088 "Section 4.6.20. of CAPWAP Protocol Specification, RFC xxx." 1089 ::= { capwapWTPEntry 8 } 1091 capwapWTPRadiosInUseNum OBJECT-TYPE 1092 SYNTAX Unsigned32 1093 MAX-ACCESS read-only 1094 STATUS current 1095 DESCRIPTION 1096 "Represents the number of radios which are in use." 1097 REFERENCE 1098 "Section 4.6.39. of CAPWAP Protocol Specification, RFC xxx." 1099 ::= { capwapWTPEntry 9 } 1101 capwapWTPRadioNumLimit OBJECT-TYPE 1102 SYNTAX Unsigned32 1103 MAX-ACCESS read-only 1104 STATUS current 1105 DESCRIPTION 1106 "Represents the maximum radio number could be supported 1107 by WTP." 1108 REFERENCE 1109 "Section 4.6.39. of CAPWAP Protocol Specification, RFC xxx." 1110 ::= { capwapWTPEntry 10 } 1112 capwapWTPStaticIPEnable OBJECT-TYPE 1113 SYNTAX TruthValue 1114 MAX-ACCESS read-write 1115 STATUS current 1116 DESCRIPTION 1117 "Represents whether the WTP should use a static IP address 1118 or not. A value of false disables the static IP address, 1119 while a value of true enables it." 1120 REFERENCE 1121 "Section 4.6.49. of CAPWAP Protocol Specification, RFC xxx." 1122 ::= { capwapWTPEntry 11 } 1124 capwapWTPStaticIPType OBJECT-TYPE 1125 SYNTAX InetAddressType 1126 MAX-ACCESS read-write 1127 STATUS current 1128 DESCRIPTION 1129 "Represents whether WTP uses IPV4 or IPV6 static IP address." 1130 ::= { capwapWTPEntry 12 } 1132 capwapWTPStaticIP OBJECT-TYPE 1133 SYNTAX InetAddress 1134 MAX-ACCESS read-write 1135 STATUS current 1136 DESCRIPTION 1137 "When capwapWTPStaticIPEnable is true, it represents the static 1138 IP address to assign to the WTP." 1139 REFERENCE 1140 "Section 4.6.49. of CAPWAP Protocol Specification, RFC xxx." 1141 ::= { capwapWTPEntry 13 } 1143 capwapWTPNetmask OBJECT-TYPE 1144 SYNTAX InetAddress 1145 MAX-ACCESS read-write 1146 STATUS current 1147 DESCRIPTION 1148 "When capwapWTPStaticIPEnable is true, it represents the netmask 1149 to assign to the WTP." 1150 REFERENCE 1151 "Section 4.6.49. of CAPWAP Protocol Specification, RFC xxx." 1152 ::= { capwapWTPEntry 14 } 1154 capwapWTPGateway OBJECT-TYPE 1155 SYNTAX InetAddress 1156 MAX-ACCESS read-write 1157 STATUS current 1158 DESCRIPTION 1159 "When capwapWTPStaticIPEnable is true, it represents the gateway 1160 to assign to the WTP." 1161 REFERENCE 1162 "Section 4.6.49. of CAPWAP Protocol Specification, RFC xxx." 1163 ::= { capwapWTPEntry 15 } 1165 -- End of capwapWTPTable table 1167 -- capwapRadioBindTable Table 1169 capwapRadioBindTable OBJECT-TYPE 1170 SYNTAX SEQUENCE OF CapwapRadioBindEntry 1171 MAX-ACCESS not-accessible 1172 STATUS current 1173 DESCRIPTION 1174 "A table of objects that display the mapping relationship 1175 between specific interface of 'WTP Virtual Radio Interface' 1176 ifType and PHY radio. The mapping relationship in this table 1177 is persistent at restart/reboot." 1178 ::= { capwapWTPs 3 } 1180 capwapRadioBindEntry OBJECT-TYPE 1181 SYNTAX CapwapRadioBindEntry 1182 MAX-ACCESS not-accessible 1183 STATUS current 1184 DESCRIPTION 1185 "A set of objects that display the mapping relationship 1186 between 'WTP Virtual Radio' and PHY radio." 1187 INDEX { capwapWTPId, capwapRadioId } 1188 ::= { capwapRadioBindTable 1 } 1190 CapwapRadioBindEntry ::= SEQUENCE { 1191 capwapRadioId CapwapRadioId, 1192 capwapWTPVirtualRadioIfIndex InterfaceIndex, 1193 capwapWirelessBinding INTEGER 1194 } 1196 capwapRadioId OBJECT-TYPE 1197 SYNTAX CapwapRadioId 1198 MAX-ACCESS accessible-for-notify 1199 STATUS current 1200 DESCRIPTION 1201 "Represents the identifier of a PHY radio on a WTP, and only 1202 requires unique on a WTP. 1203 For example, WTP A and WTP B will use same value of 1204 capwapRadioId for their first radio." 1205 REFERENCE 1206 "Section 4.6.31. of CAPWAP Protocol Specification, RFC xxx." 1207 ::= { capwapRadioBindEntry 1 } 1209 capwapWTPVirtualRadioIfIndex OBJECT-TYPE 1210 SYNTAX InterfaceIndex 1211 MAX-ACCESS read-only 1212 STATUS current 1213 DESCRIPTION 1214 "Represents the ifIndex for an interface of 'WTP Virtual Radio 1215 Interface' ifType. 1216 Before WTPs connect to AC and get configuration, operator 1217 will prepare configuration for them. At AC side, there are 1218 interface of 'WTP Virtual Radio Interface' type which represent 1219 PHY radio interface at WTP side. 1220 As most MIBs use ifIndex to identify an interface for 1221 configuration and statistic data, for example, IEEE 802.11 MIB. 1222 It will be very easy to reuse other MIBs such as IEEE 802.11 1223 MIB by 'WTP Virtual Radio Interface'. 1224 Require IANA to assign an ifType for 'WTP Virtual Radio 1225 Interface'." 1226 ::= { capwapRadioBindEntry 2 } 1228 capwapWirelessBinding OBJECT-TYPE 1229 SYNTAX INTEGER { none(1), dot11(2), dot16(3), epc(4) } 1230 MAX-ACCESS read-only 1231 STATUS current 1232 DESCRIPTION 1233 "Represents the wireless binding type for radio. 1234 The following values are supported: 1235 none(1) - No any wireless binding defined. 1236 dot11(2) - IEEE 802.11. 1237 dot16(3) - IEEE 802.16. 1238 epc(4) - EPCGlobal." 1239 REFERENCE 1240 "Section 4.3. of CAPWAP Protocol Specification, RFC xxx." 1241 ::= { capwapRadioBindEntry 3 } 1243 -- End of capwapRadioBindTable Table 1245 -- capwapStationTable Table 1247 capwapStationTable OBJECT-TYPE 1248 SYNTAX SEQUENCE OF CapwapStationEntry 1249 MAX-ACCESS not-accessible 1250 STATUS current 1251 DESCRIPTION 1252 "A table of objects that display stations which are 1253 associated with the specific radio on the WTP." 1254 ::= { capwapWTPs 4 } 1256 capwapStationEntry OBJECT-TYPE 1257 SYNTAX CapwapStationEntry 1258 MAX-ACCESS not-accessible 1259 STATUS current 1260 DESCRIPTION 1261 "A set of objects that display a station which is 1262 associated with the specific radio on the WTP." 1263 INDEX { capwapWTPCurrId, capwapRadioId, capwapStationId } 1264 ::= { capwapStationTable 1 } 1266 CapwapStationEntry ::= SEQUENCE { 1267 capwapStationId CapwapStationId, 1268 capwapStationAddedTime DateAndTime, 1269 capwapStationVlanName OCTET STRING 1270 } 1272 capwapStationId OBJECT-TYPE 1273 SYNTAX CapwapStationId 1274 MAX-ACCESS not-accessible 1275 STATUS current 1276 DESCRIPTION 1277 "Represents the unique identifier of the station." 1278 REFERENCE 1279 "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." 1280 ::= { capwapStationEntry 1 } 1282 capwapStationAddedTime OBJECT-TYPE 1283 SYNTAX DateAndTime 1284 MAX-ACCESS read-only 1285 STATUS current 1286 DESCRIPTION 1287 "Represents the time when the station is added." 1288 REFERENCE 1289 "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." 1290 ::= { capwapStationEntry 2 } 1292 capwapStationVlanName OBJECT-TYPE 1293 SYNTAX OCTET STRING (SIZE(32)) 1294 MAX-ACCESS read-only 1295 STATUS current 1296 DESCRIPTION 1297 "Represents VLAN name to which the station is associated." 1298 REFERENCE 1299 "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." 1300 ::= { capwapStationEntry 3 } 1302 -- End of capwapStationTable Table 1304 -- capwapWTPRebootStatTable 1306 capwapWTPRebootStatsTable OBJECT-TYPE 1307 SYNTAX SEQUENCE OF CapwapWTPRebootStatsEntry 1308 MAX-ACCESS not-accessible 1309 STATUS current 1310 DESCRIPTION 1311 "A table of objects that display WTPs' reboot statistic 1312 data." 1313 ::= { capwapWTPs 5 } 1315 capwapWTPRebootStatsEntry OBJECT-TYPE 1316 SYNTAX CapwapWTPRebootStatsEntry 1317 MAX-ACCESS not-accessible 1318 STATUS current 1319 DESCRIPTION 1320 "A set of objects that display the reboot statistic data 1321 of a WTP." 1323 INDEX { capwapWTPCurrId } 1324 ::= { capwapWTPRebootStatsTable 1 } 1326 CapwapWTPRebootStatsEntry ::= SEQUENCE { 1327 capwapWTPRebootCount Counter32, 1328 capwapWTPInitCount Counter32, 1329 capwapWTPLinkFailureCount Counter32, 1330 capwapWTPSwFailureCount Counter32, 1331 capwapWTPHwFailureCount Counter32, 1332 capwapWTPOtherFailureCount Counter32, 1333 capwapWTPUnknownFailureCount Counter32, 1334 capwapWTPLastFailureType INTEGER 1335 } 1337 capwapWTPRebootCount OBJECT-TYPE 1338 SYNTAX Counter32 1339 MAX-ACCESS read-only 1340 STATUS current 1341 DESCRIPTION 1342 "Represents the number of reboots that have occurred due to a 1343 WTP crash. A value of 65535 implies that this information is 1344 not available on the WTP." 1345 REFERENCE 1346 "Section 4.6.48. of CAPWAP Protocol Specification, RFC xxx." 1347 ::= { capwapWTPRebootStatsEntry 1 } 1349 capwapWTPInitCount OBJECT-TYPE 1350 SYNTAX Counter32 1351 MAX-ACCESS read-only 1352 STATUS current 1353 DESCRIPTION 1354 "Represents the number of reboots that have occurred at the 1355 request of a CAPWAP protocol message, such as a change in 1356 configuration that required a reboot or an explicit CAPWAP 1357 protocol reset request. A value of 65535 implies that this 1358 information is not available on the WTP." 1359 REFERENCE 1360 "Section 4.6.48. of CAPWAP Protocol Specification, RFC xxx." 1361 ::= { capwapWTPRebootStatsEntry 2 } 1363 capwapWTPLinkFailureCount OBJECT-TYPE 1364 SYNTAX Counter32 1365 MAX-ACCESS read-only 1366 STATUS current 1367 DESCRIPTION 1368 "Represents the number of times that a CAPWAP protocol 1369 connection with an AC has failed due to link failure." 1370 REFERENCE 1371 "Section 4.6.48. of CAPWAP Protocol Specification, RFC xxx." 1372 ::= { capwapWTPRebootStatsEntry 3 } 1374 capwapWTPSwFailureCount OBJECT-TYPE 1375 SYNTAX Counter32 1376 MAX-ACCESS read-only 1377 STATUS current 1378 DESCRIPTION 1379 "Represents the number of times that a CAPWAP protocol 1380 connection with an AC has failed due to software related 1381 reasons." 1382 REFERENCE 1383 "Section 4.6.48. of CAPWAP Protocol Specification, RFC xxx." 1384 ::= { capwapWTPRebootStatsEntry 4 } 1386 capwapWTPHwFailureCount OBJECT-TYPE 1387 SYNTAX Counter32 1388 MAX-ACCESS read-only 1389 STATUS current 1390 DESCRIPTION 1391 "Represents the number of times that a CAPWAP protocol 1392 connection with an AC has failed due to hardware related 1393 reasons." 1394 REFERENCE 1395 "Section 4.6.48. of CAPWAP Protocol Specification, RFC xxx." 1396 ::= { capwapWTPRebootStatsEntry 5 } 1398 capwapWTPOtherFailureCount OBJECT-TYPE 1399 SYNTAX Counter32 1400 MAX-ACCESS read-only 1401 STATUS current 1402 DESCRIPTION 1403 "Represents the number of times that a CAPWAP protocol 1404 connection with an AC has failed due to known reasons, other 1405 than AC initiated, link, software or hardware failure." 1406 REFERENCE 1407 "Section 4.6.48. of CAPWAP Protocol Specification, RFC xxx." 1408 ::= { capwapWTPRebootStatsEntry 6 } 1410 capwapWTPUnknownFailureCount OBJECT-TYPE 1411 SYNTAX Counter32 1412 MAX-ACCESS read-only 1413 STATUS current 1414 DESCRIPTION 1415 "Represents the number of times that a CAPWAP protocol 1416 connection with an AC has failed for unknown reasons." 1417 REFERENCE 1418 "Section 4.6.48. of CAPWAP Protocol Specification, RFC xxx." 1420 ::= { capwapWTPRebootStatsEntry 7 } 1422 capwapWTPLastFailureType OBJECT-TYPE 1423 SYNTAX INTEGER { 1424 notSupport(1), acInit(2), linkFailure(3), 1425 swFailure(4), hwFailure(5),other(6), unknown(255) 1426 } 1427 MAX-ACCESS read-only 1428 STATUS current 1429 DESCRIPTION 1430 "The failure type of the most recent WTP failure. 1431 The following values are supported: 1432 notSupport(1) - Not Supported, 1433 acInit(2) - AC Initiated, 1434 linkFailure(3) - Link Failure, 1435 swFailure(4) - Software Failure, 1436 hwFailure(5) - Hardware Failure, 1437 otherFailure(6) - Other Failure, 1438 unknown(255) - Unknown (e.g., WTP doesn't keep track 1439 of info)." 1440 REFERENCE 1441 "Section 4.6.48. of CAPWAP Protocol Specification, RFC xxx." 1442 ::= { capwapWTPRebootStatsEntry 8 } 1444 -- End of capwapWTPRebootStatsTable table 1446 -- capwapRadioStatsTable table 1448 capwapRadioStatsTable OBJECT-TYPE 1449 SYNTAX SEQUENCE OF CapwapRadioStatsEntry 1450 MAX-ACCESS not-accessible 1451 STATUS current 1452 DESCRIPTION 1453 "A table of objects that display statistics on radios behavior, 1454 and reasons of radios have been reset." 1455 ::= { capwapWTPs 6 } 1457 capwapRadioStatsEntry OBJECT-TYPE 1458 SYNTAX CapwapRadioStatsEntry 1459 MAX-ACCESS not-accessible 1460 STATUS current 1461 DESCRIPTION 1462 "A set of objects that display the statistic data of 1463 events happened on a specific radio of a WTP." 1464 INDEX { capwapWTPCurrId, capwapRadioId } 1465 ::= { capwapRadioStatsTable 1 } 1467 CapwapRadioStatsEntry ::= SEQUENCE { 1468 capwapRadioResetCount Counter32, 1469 capwapRadioSwFailCount Counter32, 1470 capwapRadioHwFailCount Counter32, 1471 capwapRadioOtherFailCount Counter32, 1472 capwapRadioUnknownFailCount Counter32, 1473 capwapRadioConfigUpdateCount Counter32, 1474 capwapRadioChannelChangeCount Counter32, 1475 capwapRadioBandChangeCount Counter32, 1476 capwapRadioCurrentNoiseFloor Integer32, 1477 capwapRadioDecryptErrorCount Counter32, 1478 capwapRadioTxQueueLevel Integer32, 1479 capwapRadioRFLinkFramesPerSec Counter32, 1480 capwapRadioLastFailType INTEGER 1481 } 1483 capwapRadioResetCount OBJECT-TYPE 1484 SYNTAX Counter32 1485 MAX-ACCESS read-only 1486 STATUS current 1487 DESCRIPTION 1488 "Represents the number of times that that the radio has been 1489 reset." 1490 REFERENCE 1491 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1492 ::= { capwapRadioStatsEntry 1 } 1494 capwapRadioSwFailCount OBJECT-TYPE 1495 SYNTAX Counter32 1496 MAX-ACCESS read-only 1497 STATUS current 1498 DESCRIPTION 1499 "Represents the number of times that the radio has failed due 1500 to software related reasons." 1501 REFERENCE 1502 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1503 ::= { capwapRadioStatsEntry 2 } 1505 capwapRadioHwFailCount OBJECT-TYPE 1506 SYNTAX Counter32 1507 MAX-ACCESS read-only 1508 STATUS current 1509 DESCRIPTION 1510 "Represents the number of times that the radio has failed due 1511 to hardware related reasons." 1512 REFERENCE 1513 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1514 ::= { capwapRadioStatsEntry 3 } 1516 capwapRadioOtherFailCount OBJECT-TYPE 1517 SYNTAX Counter32 1518 MAX-ACCESS read-only 1519 STATUS current 1520 DESCRIPTION 1521 "Represents the number of times that the radio has failed due to 1522 known reasons, other than software or hardware failure." 1523 REFERENCE 1524 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1525 ::= { capwapRadioStatsEntry 4 } 1527 capwapRadioUnknownFailCount OBJECT-TYPE 1528 SYNTAX Counter32 1529 MAX-ACCESS read-only 1530 STATUS current 1531 DESCRIPTION 1532 "Represents the number of times that the radio has failed for 1533 unknown reasons." 1534 REFERENCE 1535 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1536 ::= { capwapRadioStatsEntry 5 } 1538 capwapRadioConfigUpdateCount OBJECT-TYPE 1539 SYNTAX Counter32 1540 MAX-ACCESS read-only 1541 STATUS current 1542 DESCRIPTION 1543 "Represents the number of times that the radio configuration has 1544 been updated." 1545 REFERENCE 1546 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1547 ::= { capwapRadioStatsEntry 6 } 1549 capwapRadioChannelChangeCount OBJECT-TYPE 1550 SYNTAX Counter32 1551 MAX-ACCESS read-only 1552 STATUS current 1553 DESCRIPTION 1554 "Represents the number of times that the radio channel has 1555 been changed." 1556 REFERENCE 1557 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1558 ::= { capwapRadioStatsEntry 7 } 1560 capwapRadioBandChangeCount OBJECT-TYPE 1561 SYNTAX Counter32 1562 MAX-ACCESS read-only 1563 STATUS current 1564 DESCRIPTION 1565 "Represents the number of times that the radio has changed 1566 frequency bands." 1567 REFERENCE 1568 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1569 ::= { capwapRadioStatsEntry 8 } 1571 capwapRadioCurrentNoiseFloor OBJECT-TYPE 1572 SYNTAX Integer32 1573 UNITS "dbm" 1574 MAX-ACCESS read-only 1575 STATUS current 1576 DESCRIPTION 1577 "Represents the noise floor of the radio receiver in units of 1578 dBm." 1579 ::= { capwapRadioStatsEntry 9 } 1581 capwapRadioDecryptErrorCount OBJECT-TYPE 1582 SYNTAX Counter32 1583 MAX-ACCESS read-only 1584 STATUS current 1585 DESCRIPTION 1586 "Represents the number of decryption errors that occurred on the 1587 WTP. Note that this field is only valid in cases where the WTP 1588 provides encryption/decryption services." 1589 REFERENCE 1590 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1591 ::= { capwapRadioStatsEntry 10 } 1593 capwapRadioTxQueueLevel OBJECT-TYPE 1594 SYNTAX Integer32 (0..100) 1595 MAX-ACCESS read-only 1596 STATUS current 1597 DESCRIPTION 1598 "Represents the percentage of Wireless Transmit queue 1599 utilization,calculated as the sum of utilized transmit queue 1600 lengths divided by the sum of maximum transmit queue lengths, 1601 multiplied by 100." 1602 REFERENCE 1603 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1604 ::= { capwapRadioStatsEntry 11 } 1606 capwapRadioRFLinkFramesPerSec OBJECT-TYPE 1607 SYNTAX Counter32 1608 MAX-ACCESS read-only 1609 STATUS current 1610 DESCRIPTION 1611 "Represents the number of frames transmitted or received per 1612 second by the WTP over the radio interface." 1613 REFERENCE 1614 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1615 ::= { capwapRadioStatsEntry 12 } 1617 capwapRadioLastFailType OBJECT-TYPE 1618 SYNTAX INTEGER { 1619 notSupport(1), 1620 swFailure(2), 1621 hwFailure(3), 1622 otherFailure(4), 1623 unknown(255) 1624 } 1625 MAX-ACCESS read-only 1626 STATUS current 1627 DESCRIPTION 1628 "Represents the failure type of the most recent radio failure. 1629 The following values are supported: 1630 notSupport(1) - Not Supported, 1631 swFailure(2) - Software Failure, 1632 hwFailure(3) - Hardware Failure, 1633 otherFailure(4) - Other Failure, 1634 unknown(255) - Unknown." 1635 ::= { capwapRadioStatsEntry 13 } 1637 -- End of capwapRadioStatsTable table 1639 -- Notifications 1641 capwapChannelUp NOTIFICATION-TYPE 1642 OBJECTS { capwapWTPId, 1643 capwapChannelType, 1644 capwapWTPAuthenMethod } 1645 STATUS current 1646 DESCRIPTION 1647 "This notification is sent by AC when a CAPWAP channel 1648 established. The notification is separated for data or control 1649 channel." 1650 ::= { capwapNotifications 1 } 1652 capwapChannelDown NOTIFICATION-TYPE 1653 OBJECTS { capwapWTPId, capwapChannelDownReason } 1654 STATUS current 1655 DESCRIPTION 1656 "This notification is sent by AC when CAPWAP channel becomes 1657 down." 1658 ::= { capwapNotifications 2 } 1660 capwapDecryptErrorReport NOTIFICATION-TYPE 1661 OBJECTS { capwapWTPId, 1662 capwapRadioId, 1663 capwapIdEntryNum, 1664 capwapStationIdList } 1665 STATUS current 1666 DESCRIPTION 1667 "This notification is generated when a WTP that has occurred 1668 decryption error since the last report." 1669 REFERENCE 1670 "Section 4.6.15. of CAPWAP Protocol Specification, RFC xxx." 1671 ::= { capwapNotifications 3 } 1673 capwapJoinFailure NOTIFICATION-TYPE 1674 OBJECTS { capwapWTPId, capwapJoinFailureReason } 1675 STATUS current 1676 DESCRIPTION 1677 "This notification is generated when a WTP fails to join." 1678 REFERENCE 1679 "Section 4.6.33. of CAPWAP Protocol Specification, RFC xxx." 1680 ::= { capwapNotifications 4 } 1682 capwapImageUpgradeFailure NOTIFICATION-TYPE 1683 OBJECTS { capwapWTPId, capwapImageFailureReason } 1684 STATUS current 1685 DESCRIPTION 1686 "This notification is generated when a WTP fails to update 1687 software image." 1688 REFERENCE 1689 "Section 4.6.33. of CAPWAP Protocol Specification, RFC xxx." 1690 ::= { capwapNotifications 5 } 1692 capwapConfigMsgError NOTIFICATION-TYPE 1693 OBJECTS { capwapWTPId, capwapConfigMsgErrorType, 1694 capwapMsgErrorElements } 1695 STATUS current 1696 DESCRIPTION 1697 "This notification is generated when a WTP received message 1698 elements in the Configuration Status Response which it was 1699 unable to apply locally." 1700 REFERENCE 1701 "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." 1702 ::= { capwapNotifications 6 } 1704 capwapRadioOperableStatus NOTIFICATION-TYPE 1705 OBJECTS { capwapWTPId, 1706 capwapRadioId, 1707 capwapRadioOperStatusFlag, 1708 capwapRadioFailureReason } 1709 STATUS current 1710 DESCRIPTION 1711 "The notification will notify which radio become inoperable 1712 or operable." 1713 REFERENCE 1714 "Section 4.6.32. of CAPWAP Protocol Specification, RFC xxx." 1715 ::= { capwapNotifications 7 } 1717 capwapWTPAuthenticationFailure NOTIFICATION-TYPE 1718 OBJECTS { capwapWTPId, 1719 capwapChannelType, 1720 capwapWTPAuthenMethod, 1721 capwapWTPAuthenFailureReason } 1722 STATUS current 1723 DESCRIPTION 1724 "The notification will notify the authentication failure event, 1725 and provides the reason for it." 1726 REFERENCE 1727 "Section 2.3.1. of CAPWAP Protocol Specification, RFC xxx." 1728 ::= { capwapNotifications 8 } 1730 -- Objects used only in notifications 1732 -- for notifications 1733 capwapNotifyVarObjects OBJECT IDENTIFIER 1734 ::= { capwapObjects 3 } 1736 capwapChannelType OBJECT-TYPE 1737 SYNTAX CapwapChannelType 1738 MAX-ACCESS accessible-for-notify 1739 STATUS current 1740 DESCRIPTION 1741 "Represents the channel type for CAPWAP protocol." 1742 ::= { capwapNotifyVarObjects 1 } 1744 capwapWTPAuthenMethod OBJECT-TYPE 1745 SYNTAX CapwapWTPAuthenMethod 1746 MAX-ACCESS accessible-for-notify 1747 STATUS current 1748 DESCRIPTION 1749 "Represents authentication method for Channel." 1750 ::= { capwapNotifyVarObjects 2 } 1752 capwapChannelDownReason OBJECT-TYPE 1753 SYNTAX INTEGER { timeout(1), rekeyfailure(2), apReboot(3) } 1754 MAX-ACCESS accessible-for-notify 1755 STATUS current 1756 DESCRIPTION 1757 "Represents the reason for Channel down. 1758 The following values are supported: 1759 timeout(1) - The keep alive is timeout, 1760 rekeyfailure(2) - Rekey process is failed, channel will be 1761 broken. 1762 apReboot(3) - AC reboot WTP." 1763 ::= { capwapNotifyVarObjects 3 } 1765 capwapIdEntryNum OBJECT-TYPE 1766 SYNTAX Unsigned32 1767 MAX-ACCESS accessible-for-notify 1768 STATUS current 1769 DESCRIPTION 1770 "Represents the entry number of station id in the 1771 capwapStationIdList." 1772 REFERENCE 1773 "Section 4.6.15. of CAPWAP Protocol Specification, RFC xxx." 1774 ::= { capwapNotifyVarObjects 4 } 1776 capwapStationIdList OBJECT-TYPE 1777 SYNTAX OCTET STRING 1778 MAX-ACCESS accessible-for-notify 1779 STATUS current 1780 DESCRIPTION 1781 "Represents the list of station id." 1782 REFERENCE 1783 "Section 4.6.15. of CAPWAP Protocol Specification, RFC xxx." 1784 ::= { capwapNotifyVarObjects 5 } 1786 capwapWTPAuthenFailureReason OBJECT-TYPE 1787 SYNTAX INTEGER { 1788 keyMismatch(1), invalidCA(2), micError(3), 1789 timeout(4), unknown(8) 1790 } 1791 MAX-ACCESS accessible-for-notify 1792 STATUS current 1793 DESCRIPTION 1794 "Represents reason for WTP authorization failure. 1795 The following values are supported: 1796 keyMismatch(1) - WTP's and AC's key is not matched, 1797 invalidCA(2) - ca is not valid, 1798 micError(3) - detect MIC error, 1799 timeout(4) - WaitDTLS Timer is timeout, 1800 unknown(8) - Unknown reason." 1801 REFERENCE 1802 "Section 2.3.1. of CAPWAP Protocol Specification, RFC xxx." 1803 ::= { capwapNotifyVarObjects 6 } 1805 capwapRadioOperStatusFlag OBJECT-TYPE 1806 SYNTAX INTEGER { operable(1), inoperable(2) } 1807 MAX-ACCESS accessible-for-notify 1808 STATUS current 1809 DESCRIPTION 1810 "Represents the operation status of a radio. 1811 The following values are supported: 1812 operable(1) - To indicate radio is operable, 1813 inoperable(2) - To indicate radio is inoperable, and 1814 capwapRadioFailureReason object will 1815 give reason in details" 1816 REFERENCE 1817 "Section 4.6.32. of CAPWAP Protocol Specification, RFC xxx." 1818 ::= { capwapNotifyVarObjects 7 } 1820 capwapRadioFailureReason OBJECT-TYPE 1821 SYNTAX INTEGER { 1822 hwError(1), swError(2), adminSet(3), unknown(8) 1823 } 1824 MAX-ACCESS accessible-for-notify 1825 STATUS current 1826 DESCRIPTION 1827 "Represents errors caused by configuration operation. 1828 The following values are supported 1829 hwError(1) - Radio Failure, 1830 swError(2) - Software Failure, 1831 adminSet(3) - Administratively Set, 1832 unknown(8) - Unknown reason." 1833 REFERENCE 1834 "Section 4.6.32. of CAPWAP Protocol Specification, RFC xxx." 1835 ::= { capwapNotifyVarObjects 8 } 1837 capwapJoinFailureReason OBJECT-TYPE 1838 SYNTAX INTEGER { 1839 unspecified(1), resDepletion(2), unknownSource(3), 1840 incorrectData(4), sessionInUse(5), notSupportHw(6), 1841 notSupportBinding(7) 1842 } 1843 MAX-ACCESS accessible-for-notify 1844 STATUS current 1845 DESCRIPTION 1846 "The following join failure types are supported: 1847 unspecified(1) - unspecified failure reason, 1848 resDepletion(2) - Resource Depletion, 1849 unknownSource(3) - Unknown Source, 1850 incorrectData(4) - Incorrect Data, 1851 sessionInUse(5) - Session ID already in use, 1852 notSupportHw(6) - WTP Hardware not supported, 1853 notSupportBinding(7) - Binding Not Supported." 1854 REFERENCE 1855 "Section 4.6.33. of CAPWAP Protocol Specification, RFC xxx." 1856 ::= { capwapNotifyVarObjects 9 } 1858 capwapImageFailureReason OBJECT-TYPE 1859 SYNTAX INTEGER { 1860 invalidChecksum(1), 1861 invalidLength(2), 1862 other(3), 1863 inUse(4) 1864 } 1865 MAX-ACCESS accessible-for-notify 1866 STATUS current 1867 DESCRIPTION 1868 "The following software upgrade failure types are supported: 1869 invalidChecksum(1) - Invalid Checksum, 1870 invalidLength(2) - Invalid Data Length, 1871 other(3) - Other Error, 1872 inUse(4) - Image Already Present." 1873 REFERENCE 1874 "Section 4.6.33. of CAPWAP Protocol Specification, RFC xxx." 1875 ::= { capwapNotifyVarObjects 10 } 1877 capwapConfigMsgErrorType OBJECT-TYPE 1878 SYNTAX INTEGER { 1879 unknownElement(1), unsupportedElement(2), 1880 unknownValue(3), unsupportedValue(4) 1881 } 1882 MAX-ACCESS accessible-for-notify 1883 STATUS current 1884 DESCRIPTION 1885 "The following software upgrade failure types are supported: 1886 unknownElement(1) - Unknown Message Element, 1887 unsupportedElement(2) - Unsupported Message Element, 1888 unknownValue(3) - Unknown Message Element Value, 1889 unsupportedValue(4) - Unsupported Message Element Value." 1890 REFERENCE 1891 "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." 1892 ::= { capwapNotifyVarObjects 11 } 1894 capwapMsgErrorElements OBJECT-TYPE 1895 SYNTAX SnmpAdminString 1896 MAX-ACCESS accessible-for-notify 1897 STATUS current 1898 DESCRIPTION 1899 "Represents the message element sent by the AC in the 1900 Configuration Status Response message that caused the error." 1901 REFERENCE 1902 "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." 1903 ::= { capwapNotifyVarObjects 12 } 1905 -- Module compliance 1907 capwapCompliances OBJECT IDENTIFIER 1908 ::= { capwapConformance 1 } 1910 capwapGroups OBJECT IDENTIFIER 1911 ::= { capwapConformance 2 } 1913 capwapCompliance MODULE-COMPLIANCE 1914 STATUS current 1915 DESCRIPTION 1916 "Describes the requirements for conformance to the 1917 CAPWAP Base MIB." 1919 MODULE -- this module 1920 MANDATORY-GROUPS { capwapACNodeGroup, 1921 capwapWTPStateGroup, 1922 capwapWTPsGroup, 1923 capwapRadiosGroup, 1924 capwapStationsGroup } 1926 GROUP capwapACNodeGroup2 1927 DESCRIPTION 1928 "The capwapACNodeGroup2 group is optional." 1930 GROUP capwapWTPsGroup2 1931 DESCRIPTION 1932 "The capwapWTPsGroup2 group is optional." 1934 GROUP capwapWTPRebootStatsGroup 1935 DESCRIPTION 1936 "The capwapWTPRebootStatsGroup group is optional." 1938 GROUP capwapRadioStatsGroup 1939 DESCRIPTION 1940 "The capwapRadioStatsGroup group is optional." 1942 GROUP capwapNofificationGroup 1943 DESCRIPTION 1944 "The group capwapNofificationGroup is optional." 1946 GROUP capwapNotifyVarGroup 1947 DESCRIPTION 1948 "The capwapNotifyVarGroup group is optional. 1949 If capwapNofificationGroup is supported, 1950 this group must be implemented." 1952 OBJECT capwapWirelessBinding 1953 SYNTAX INTEGER { none(1) } 1954 DESCRIPTION 1955 "A value other than none(1) need not be supported if there is 1956 no wireless binding defined for technologies used." 1957 ::= { capwapCompliances 1 } 1959 capwapACNodeGroup OBJECT-GROUP 1960 OBJECTS { 1961 capwapWTPSessions, 1962 capwapWTPSessionsLimit, 1963 capwapStationSessions, 1964 capwapStationSessionsLimit, 1965 capwapWTPIdleTimeout, 1966 capwapWTPMaxDiscoveries, 1967 capwapWTPMaxRetransmit, 1968 capwapWTPReportInterval 1969 } 1970 STATUS current 1971 DESCRIPTION 1972 "The collection of objects which are used to represent 1973 basic properties for AC from CAPWAP protocol perspective." 1974 ::= { capwapGroups 1 } 1976 capwapACNodeGroup2 OBJECT-GROUP 1977 OBJECTS { 1978 capwapDataChannelSecOptions, 1979 capwapWTPAuthenOptions, 1980 capwapWTPFallbackEnable, 1981 capwapWTPACNameList, 1982 capwapMaxFailedDTLSSessionRetry 1983 } 1984 STATUS current 1985 DESCRIPTION 1986 "The collection of objects which are used to represent 1987 other properties such as security for AC from 1988 CAPWAP protocol perspective." 1989 ::= { capwapGroups 2 } 1991 capwapWTPStateGroup OBJECT-GROUP 1992 OBJECTS { 1993 capwapWTPId, 1994 capwapWTPIPAddressType, 1995 capwapWTPIPAddress, 1996 capwapWTPPHYAddress, 1997 capwapWTPState 1998 } 1999 STATUS current 2000 DESCRIPTION 2001 "The collection of objects which are used to represent 2002 WTP state information." 2003 ::= { capwapGroups 3 } 2005 capwapWTPsGroup OBJECT-GROUP 2006 OBJECTS { 2007 capwapWTPName, 2008 capwapWTPLocation, 2009 capwapWTPBaseMACAddress, 2010 capwapWTPTunnelModeOptions, 2011 capwapWTPMACTypeOptions, 2012 capwapWTPRadiosInUseNum, 2013 capwapWTPRadioNumLimit 2014 } 2015 STATUS current 2016 DESCRIPTION 2017 "The collection of objects which are used to represent 2018 configuration and properties information for WTP 2019 in running state." 2020 ::= { capwapGroups 4 } 2022 capwapWTPsGroup2 OBJECT-GROUP 2023 OBJECTS { 2024 capwapWTPPHYIndex, 2025 capwapWTPDiscoveryType, 2026 capwapWTPStaticIPEnable, 2027 capwapWTPStaticIPType, 2028 capwapWTPStaticIP, 2029 capwapWTPNetmask, 2030 capwapWTPGateway 2031 } 2032 STATUS current 2033 DESCRIPTION 2034 "The collection of objects which are used to represent 2035 configuration and properties information for WTP 2036 in running state." 2037 ::= { capwapGroups 5 } 2039 capwapRadiosGroup OBJECT-GROUP 2040 OBJECTS { 2041 capwapRadioId, 2042 capwapWTPVirtualRadioIfIndex, 2043 capwapWirelessBinding 2044 } 2045 STATUS current 2046 DESCRIPTION 2047 "The collection of objects which are used to represent 2048 wireless binding type, the mapping relationship between 2049 'WLAN Virtual Radio Interface' and PHY radio." 2050 ::= { capwapGroups 6 } 2052 capwapStationsGroup OBJECT-GROUP 2053 OBJECTS { 2054 capwapStationAddedTime, 2055 capwapStationVlanName 2056 } 2057 STATUS current 2058 DESCRIPTION 2059 "The collection of objects which are used to represent 2060 stations' basic property." 2061 ::= { capwapGroups 7 } 2063 capwapWTPRebootStatsGroup OBJECT-GROUP 2064 OBJECTS { 2065 capwapWTPRebootCount, 2066 capwapWTPInitCount, 2067 capwapWTPLinkFailureCount, 2068 capwapWTPSwFailureCount, 2069 capwapWTPHwFailureCount, 2070 capwapWTPOtherFailureCount, 2071 capwapWTPUnknownFailureCount, 2072 capwapWTPLastFailureType 2073 } 2074 STATUS current 2075 DESCRIPTION 2076 "The collection of objects which are used for collecting 2077 WTP reboot count, link failure count, hardware failure 2078 count and so on." 2079 ::= { capwapGroups 8 } 2081 capwapRadioStatsGroup OBJECT-GROUP 2082 OBJECTS { 2083 capwapRadioResetCount, 2084 capwapRadioSwFailCount, 2085 capwapRadioHwFailCount, 2086 capwapRadioOtherFailCount, 2087 capwapRadioUnknownFailCount, 2088 capwapRadioConfigUpdateCount, 2089 capwapRadioChannelChangeCount, 2090 capwapRadioBandChangeCount, 2091 capwapRadioCurrentNoiseFloor, 2092 capwapRadioDecryptErrorCount, 2093 capwapRadioTxQueueLevel, 2094 capwapRadioRFLinkFramesPerSec, 2095 capwapRadioLastFailType 2096 } 2097 STATUS current 2098 DESCRIPTION 2099 "The collection of objects which are used for collecting 2100 radio reset count, channel change count, hardware failure 2101 count and so on" 2102 ::= { capwapGroups 9 } 2104 capwapNofificationGroup NOTIFICATION-GROUP 2105 NOTIFICATIONS { 2106 capwapChannelUp, 2107 capwapChannelDown, 2108 capwapDecryptErrorReport, 2109 capwapJoinFailure, 2110 capwapImageUpgradeFailure, 2111 capwapConfigMsgError, 2112 capwapRadioOperableStatus, 2113 capwapWTPAuthenticationFailure 2114 } 2115 STATUS current 2116 DESCRIPTION 2117 "Collection of notifications in this MIB." 2118 ::= { capwapGroups 10 } 2120 capwapNotifyVarGroup OBJECT-GROUP 2121 OBJECTS { 2122 capwapWTPId, 2123 capwapRadioId, 2124 capwapChannelType, 2125 capwapWTPAuthenMethod, 2126 capwapChannelDownReason, 2127 capwapIdEntryNum, 2128 capwapStationIdList, 2129 capwapWTPAuthenFailureReason, 2130 capwapRadioOperStatusFlag, 2131 capwapRadioFailureReason, 2132 capwapJoinFailureReason, 2133 capwapImageFailureReason, 2134 capwapConfigMsgErrorType, 2135 capwapMsgErrorElements 2136 } 2137 STATUS current 2138 DESCRIPTION 2139 "Objects used for notification." 2140 ::= { capwapGroups 11 } 2142 END 2144 10. Security Considerations 2146 There are a number of management objects defined in this MIB module 2147 with a MAX-ACCESS clause of read-write and/or read-create. Such 2148 objects may be considered sensitive or vulnerable in some network 2149 environments. The support for SET operations in a non-secure 2150 environment without proper protection can have a negative effect on 2151 network operations. These are the tables and objects and their 2152 sensitivity/vulnerability: 2154 o - Unauthorized changes to the capwapWTPTable, writeable objects 2155 under capwapACs group may disrupt allocation of resources in the 2156 network. 2158 Some of the readable objects in this MIB module (i.e., objects with a 2159 MAX-ACCESS other than not-accessible) may be considered sensitive or 2160 vulnerable in some network environments. It is thus important to 2161 control even GET and/or NOTIFY access to these objects and possibly 2162 to even encrypt the values of these objects when sending them over 2163 the network via SNMP. These are the tables and objects and their 2164 sensitivity/vulnerability: 2166 o - The capwapWTPTable exposes WTP's important information like IP 2167 address, MAC type and so on; 2169 o - The capwapWTPRebootStatTable exposes WTP's failure information; 2171 o - The capwapRadioStatsTable exposes radio's failure information; 2173 SNMP versions prior to SNMPv3 did not include adequate security. 2174 Even if the network itself is secure (for example by using IPSec), 2175 even then, there is no control as to who on the secure network is 2176 allowed to access and GET/SET (read/change/create/delete) the objects 2177 in this MIB module. 2179 It is RECOMMENDED that implementers consider the security features as 2180 provided by the SNMPv3 framework (see [RFC3410], section 8), 2181 including full support for the SNMPv3 cryptographic mechanisms (for 2182 authentication and privacy). 2184 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2185 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2186 enable cryptographic security. It is then a customer/operator 2187 responsibility to ensure that the SNMP entity giving access to an 2188 instance of this MIB module is properly configured to give access to 2189 the objects only to those principals (users) that have legitimate 2190 rights to indeed GET or SET (change/create/delete) them. 2192 11. IANA Considerations 2194 11.1. IANA Considerations for CAPWAP-MIB 2196 The MIB module in this document uses the following IANA-assigned 2197 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 2199 Descriptor OBJECT IDENTIFIER value 2200 ---------- ----------------------- 2202 capwapMIB { mib-2 XXX } 2204 11.2. IANA Considerations for ifType 2206 Require IANA to assign a ifType for 'WTP Virtual Radio Interface' 2207 type. 2209 12. Contributors 2211 This MIB is based on contributions from Long Gao. 2213 13. Acknowledgements 2215 The authors wish to thank David Harrington, Yu Liu, Xi Yao, Sachin 2216 Dutta, Ju Wang, Yujin Zhao, Haitao Zhang. 2218 14. References 2220 14.1. Normative References 2222 [RFC2119] Bradner, S., "Key words for 2223 use in RFCs to Indicate 2224 Requirement Levels", 2225 BCP 14, RFC 2119, 2226 March 1997. 2228 [RFC2578] McCloghrie, K., Ed., 2229 Perkins, D., Ed., and J. 2230 Schoenwaelder, Ed., 2231 "Structure of Management 2232 Information Version 2 2233 (SMIv2)", STD 58, RFC 2578, 2234 April 1999. 2236 [RFC2579] McCloghrie, K., Ed., 2237 Perkins, D., Ed., and J. 2238 Schoenwaelder, Ed., 2239 "Textual Conventions for 2240 SMIv2", STD 58, RFC 2579, 2241 April 1999. 2243 [RFC2580] McCloghrie, K., Perkins, 2244 D., and J. Schoenwaelder, 2245 "Conformance Statements for 2246 SMIv2", STD 58, RFC 2580, 2247 April 1999. 2249 [RFC2863] McCloghrie, K. and F. 2250 Kastenholz, "The Interfaces 2251 Group MIB", RFC 2863, 2252 June 2000. 2254 [RFC3418] Presuhn, R., "Management 2255 Information Base (MIB) for 2256 the Simple Network 2257 Management Protocol 2258 (SNMP)", STD 62, RFC 3418, 2259 December 2002. 2261 [RFC4001] Daniele, M., Haberman, B., 2262 Routhier, S., and J. 2263 Schoenwaelder, "Textual 2264 Conventions for Internet 2265 Network Addresses", 2266 RFC 4001, February 2005. 2268 [RFC4133] Bierman, A. and K. 2269 McCloghrie, "Entity MIB 2270 (Version 3)", RFC 4133, 2271 August 2005. 2273 [I-D.ietf-capwap-protocol-specification] Calhoun, P., "CAPWAP 2274 Protocol Specification", dr 2275 aft-ietf-capwap-protocol- 2276 specification-08 (work in 2277 progress), November 2007. 2279 14.2. Informative References 2281 [RFC3410] Case, J., Mundy, R., 2282 Partain, D., and B. 2283 Stewart, "Introduction and 2284 Applicability Statements 2285 for Internet-Standard 2286 Management Framework", 2287 RFC 3410, December 2002. 2289 [RFC4181] Heard, C., "Guidelines for 2290 Authors and Reviewers of 2291 MIB Documents", BCP 111, 2292 RFC 4181, September 2005. 2294 Authors' Addresses 2296 Yang Shi (editor) 2297 H3C Tech. Co., Ltd 2298 Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian District, 2299 Beijing 2300 China(100085) 2302 Phone: +86 010 82775276 2303 EMail: young@h3c.com 2305 D. Perkins (editor) 2306 SNMPinfo 2307 288 Quailbrook Ct San Carlos, 2308 CA 94070 2309 USA 2311 Phone: +1 408 394-8702 2312 EMail: dperkins@snmpinfo.com 2314 Chris Elliott (editor) 2315 Cisco Systems, Inc. 2316 7025 Kit Creek Rd., P.O. Box 14987 Research Triangle Park 2317 27709 2318 USA 2320 Phone: +1 919-392-2146 2321 EMail: chelliot@cisco.com 2323 Full Copyright Statement 2325 Copyright (C) The IETF Trust (2008). 2327 This document is subject to the rights, licenses and restrictions 2328 contained in BCP 78, and except as set forth therein, the authors 2329 retain all their rights. 2331 This document and the information contained herein are provided on an 2332 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2333 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 2334 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 2335 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 2336 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2337 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2339 Intellectual Property 2341 The IETF takes no position regarding the validity or scope of any 2342 Intellectual Property Rights or other rights that might be claimed to 2343 pertain to the implementation or use of the technology described in 2344 this document or the extent to which any license under such rights 2345 might or might not be available; nor does it represent that it has 2346 made any independent effort to identify any such rights. Information 2347 on the procedures with respect to rights in RFC documents can be 2348 found in BCP 78 and BCP 79. 2350 Copies of IPR disclosures made to the IETF Secretariat and any 2351 assurances of licenses to be made available, or the result of an 2352 attempt made to obtain a general license or permission for the use of 2353 such proprietary rights by implementers or users of this 2354 specification can be obtained from the IETF on-line IPR repository at 2355 http://www.ietf.org/ipr. 2357 The IETF invites any interested party to bring to its attention any 2358 copyrights, patents or patent applications, or other proprietary 2359 rights that may cover technology that may be required to implement 2360 this standard. Please address the information to the IETF at 2361 ietf-ipr@ietf.org. 2363 Acknowledgement 2365 Funding for the RFC Editor function is provided by the IETF 2366 Administrative Support Activity (IASA).