idnits 2.17.1 draft-ietf-capwap-base-mib-01.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 2476. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2487. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2494. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2500. ** 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 (October 11, 2008) is 5676 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: April 14, 2009 SNMPinfo 6 C. Elliott, Ed. 7 Cisco Systems, Inc. 8 Y. Zhang, Ed. 9 Fortinet, Inc. 10 October 11, 2008 12 CAPWAP Protocol Base MIB 13 draft-ietf-capwap-base-mib-01 15 Status of This Memo 17 By submitting this Internet-Draft, each author represents that any 18 applicable patent or other IPR claims of which he or she is aware 19 have been or will be disclosed, and any of which he or she becomes 20 aware will be disclosed, in accordance with Section 6 of BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF), its areas, and its working groups. Note that 24 other groups may also distribute working documents as Internet- 25 Drafts. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt. 35 The list of Internet-Draft Shadow Directories can be accessed at 36 http://www.ietf.org/shadow.html. 38 This Internet-Draft will expire on April 14, 2009. 40 Abstract 42 This memo defines a portion of the Management Information Base (MIB) 43 for use with network management protocols. In particular, it 44 describes managed objects for modeling the Control And Provisioning 45 of Wireless Access Points (CAPWAP) Protocol. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 50 2. The Internet-Standard Management Framework . . . . . . . . . . 3 51 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 54 6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 5 55 6.1. The capwapBaseObjects Subtree . . . . . . . . . . . . . . 6 56 6.2. The capwapBaseConformance Subtree . . . . . . . . . . . . 6 57 6.3. The capwapBaseNotifications Subtree . . . . . . . . . . . 6 58 6.4. Brief Description of MIB Objects . . . . . . . . . . . . . 6 59 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7 60 7.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 7 61 7.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 7 62 7.3. Relationship to the ENTITY-MIB . . . . . . . . . . . . . . 8 63 7.4. Relationship to MIB standards of other SDOs . . . . . . . 9 64 7.5. MIB modules required for IMPORTS . . . . . . . . . . . . . 9 65 8. Example of CAPWAP-BASE-MIB Usage . . . . . . . . . . . . . . . 9 66 9. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 11 67 10. Security Considerations . . . . . . . . . . . . . . . . . . . 49 68 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 50 69 11.1. IANA Considerations for CAPWAP-BASE-MIB . . . . . . . . . 50 70 11.2. IANA Considerations for ifType . . . . . . . . . . . . . . 50 71 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 50 72 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 50 73 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 50 74 14.1. Normative References . . . . . . . . . . . . . . . . . . . 50 75 14.2. Informative References . . . . . . . . . . . . . . . . . . 51 77 1. Introduction 79 The CAPWAP Protocol [I-D.ietf-capwap-protocol-specification] defines 80 a standard, interoperable protocol, which enables an Access 81 Controller (AC) to manage a collection of Wireless Termination 82 Points(WTPs) 84 This document defines a MIB module that can be used to manage CAPWAP 85 implementations. This MIB module covers both configuration and WTP 86 status-monitoring aspects of CAPWAP, and provides a way to reuse 87 current MIB standards and future extensions for any wireless binding 88 technology. 90 2. The Internet-Standard Management Framework 92 For a detailed overview of the documents that describe the current 93 Internet-Standard Management Framework, please refer to section 7 of 94 RFC 3410 [RFC3410]. 96 Managed objects are accessed via a virtual information store, termed 97 the Management Information Base or MIB. MIB objects are generally 98 accessed through the Simple Network Management Protocol (SNMP). 99 Objects in the MIB are defined using the mechanisms defined in the 100 Structure of Management Information (SMI). This memo specifies a MIB 101 module that is compliant to the SMIv2, which is described in STD 58, 102 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 103 [RFC2580]. 105 3. Terminology 107 This document uses terminology from the document describing the 108 CAPWAP Protocol specification [I-D.ietf-capwap-protocol- 109 specification]. WTPs are viewed as remote RF interfaces controlled 110 by the AC via CAPWAP protocol. The CAPWAP protocol supports two 111 modes of operation: Split and Local MAC. In Split MAC mode all L2 112 wireless data and management frames are encapsulated via the CAPWAP 113 protocol and exchanged between the AC and the WTPs. The Local MAC 114 mode of operation allows for the data frames to be either locally 115 bridged, or tunneled as 802.3 frames. From AC, operator could 116 centrally control WTPs configuration and monitor their status. 117 CAPWAP use DTLS protocol to implement control channel security. 119 4. Conventions 121 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 122 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 123 document are to be interpreted as described in RFC 2119 [RFC2119]. 125 5. Overview 127 The CAPWAP Protocol MIB module (CAPWAP-BASE-MIB) have the following 128 design objectives: 130 - To implement an architecture that uses SNMP for the management and 131 control of wireless networks, answering the operators requirements 132 for centralized management, whatever the deployment or configuration 133 of the network devices (centralized, distributed, or some mix) 135 - To be consistent with CAPWAP protocol 137 - To reuse current MIB standards and future extensions for a wireless 138 binding technology 140 - To enable interoperability between vendors 142 - To meet operator requirements for centralized architectures 144 The basic idea of CAPWAP-BASE-MIB is: 146 - The CAPWAP-BASE-MIB MUST be run on the AC devices and is NOT 147 REQUIRED on the WTP devices. It follows same idea as CAPWAP 148 protocol: Centralized Control 150 - As a generic mechanism, it is independent of any wireless binding 151 technologies and defined by an independent MIB file 153 - To be independent of any wireless binding technologies and have 154 ability to reuse MIB standards of other SDOs, is the main challenge 155 for design of the MIB 157 - ifIndex [RFC2863] will be used as common handler for corresponding 158 interfaces in the CAPWAP-BASE-MIB and specific wireless technologies 159 MIB modules 161 - The operator could manage and control the centralized wireless 162 architectures using multiple MIB standards defined by multiple SDOs, 163 while keeping them loosely coupled 165 It is designed to satisfy the following requirements and constraints: 167 - From AC to centrally manage and monitor WTPs 169 - The MIB module supports CAPWAP protocol parameters queries 171 - The MIB module supports showing WTPs current state 172 - The MIB module provides the information of AC, WTPs, radio and 173 station objects' basic property and their relationship 175 - The MIB module supports indicating the 'WTP Virtual Radio 176 Interface' and PHY radio's mapping relationship 178 - The counters are provided for WTP, radio's reboot event, hardware 179 event failure and so on 181 - The MIB module provides the various notification like channel up, 182 join failure and so on 184 Before coming to details of CAPWAP-BASE-MIB module, it will introduce 185 how CAPWAP-BASE-MIB is able to be independent of any wireless binding 186 technologies and reuse MIB standards of other SDOs. As centralized 187 Wireless architecture, the operator has to prepare configuration on 188 the AC before WTPs connects to AC. For any wireless binding 189 technology, the configuration and management of radio is very 190 important. Under centralized Wireless architecture, according to 191 [I-D.ietf-capwap-protocol-specification], a specific PHY radio could 192 be identified by identifier of a WTP and radio (WTP id + radio id). 193 As usual, the standard of a binding technology provides MIB standard 194 for radio management on its own. For example, according to IEEE 195 802.11 WG MIB standards, the MIB tables such as Dot11OperationTable 196 are able to support WTP radio configuration. These tables use 197 ifIndex as the index, and work well under standalone Wireless 198 architecture. 200 To reuse MIB objects (defined by SDOs such as IEEE) for radio is very 201 important, and the key point is to reuse the idea of ifIndex. So it 202 is required a way to maintain the mapping relationship between 'WTP 203 id + radio id' and 'ifIndex'. As a generic mechanism, ifIndex can 204 identify an interface in abstract way, and it does NOT care for an 205 interface's PHY location (either on the WTP or AC). AC can have 206 interfaces of 'WTP Virtual Radio Interface' ifType, which will 207 logically represent PHY radios on the WTP. It looks like that PHY 208 radios are located on the AC, and PHY location of WTP (radio) is 209 hidden to the operator. Operator can operate radios by MIB tables 210 (such as IEEE 802.11 WG's) with ifIndex of 'WTP Virtual Radio 211 Interface'. As an Abstract interface, 'WTP Virtual Radio Interface' 212 could be used by any wireless binding technology such as IEEE 802.11 213 and 802.16. The table of capwapRadioBindTable will indicate the 214 mapping relationship between 'WTP id + Radio id' and IfIndex. 216 6. Structure of the MIB Module 217 6.1. The capwapBaseObjects Subtree 219 The subtree provides information for statistic data and configuration 220 parameters of WTP and radio. 222 6.2. The capwapBaseConformance Subtree 224 The subtree provides conformance information of MIB objects. 226 6.3. The capwapBaseNotifications Subtree 228 The subtree describes the notifications defined in the MIB module, 229 and their purpose. 231 6.4. Brief Description of MIB Objects 233 The MIB objects were derived from the CAPWAP protocol document 234 [I-D.ietf- capwap-protocol-specification]. 236 1) capwapBaseWtpStateTable 238 The WTPs status table is used to indicate each WTP's CAPWAP FSM 239 state. 241 2) capwapBaseWtpTable 243 The WTPs table is used for providing property and configuration 244 information in details for WTPs in running state. 246 3) capwapBaseRadioBindTable 248 The radio bind table is used to indicate the mapping relationship 249 between logical interface of 'WTP Virtual Radio Interface' ifType and 250 PHY radio. 252 4) capwapBaseStationTable 254 The station table is used for providing stations' basic property 255 information. 257 5) capwapBaseWtpRebootStatsTable 259 The WTP reboot statistic table is used for collecting WTP reboot 260 count, link failure count, hardware failure count and so on. 262 6) capwapBaseRadioStatsTable 264 The WTP radio statistic table is used for collecting radio reset 265 count, channel change count, hardware failure count and so on. 267 7. Relationship to Other MIB Modules 269 7.1. Relationship to the SNMPv2-MIB 271 The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being 272 mandatory for all systems, and the objects apply to the entity as a 273 whole. The 'system' group provides identification of the management 274 entity and certain other system-wide data. The CAPWAP-BASE-MIB does 275 not duplicate those objects. 277 7.2. Relationship to the IF-MIB 279 The Interfaces Group [RFC2863] defines generic managed objects for 280 managing interfaces. This memo contains the media-specific 281 extensions to the Interfaces Group for managing WTP radio object that 282 are modeled as interfaces. 284 IF-MIB is required to support on the AC. For each PHY radio on the 285 WTP, it will have a logical interface of 'WTP Virtual Radio 286 Interface' ifType on the AC. 'WTP Virtual Radio Interface' provides 287 a way to configure radio's parameters and query radio's traffic 288 statistics, and reuse the MIBs defined by a specific wireless binding 289 technology. The interface SHOULD be modeled as an ifEntry and 290 provide appropriate interface information. 292 Some specific interpretations of ifTable for CAPWAP-BASE-MIB are as 293 follow. 295 Object Use for the CAPWAP-BASE-MIB. 297 ifIndex Each interface of 'WTP Virtual Radio Interface' 298 ifType maybe be represented by an ifEntry. 300 ifDescr Description of the interface of 'WTP Virtual Radio 301 Interface' ifType. 303 ifType IANAifType of 'WTP Virtual Radio Interface'. 305 ifName Textual name (unique on this system) of the interface 306 or an octet string of zero length. 308 ifAlias The nonvolatile 'alias' name for the interface, as 309 specified by a network manager. 311 ifPhysAddress The physical address of the interface, such as the 312 BSSID of a 802.11 radio. 314 ifAdminStatus This variable indicates the operator's intent as 315 to whether PHY should be enabled, disabled, or 316 running in some diagnostic testing mode on this 317 interface. 318 Also see [RFC2863]. 320 ifOperStatus This value reflects the actual or operational status 321 of radio. 322 Also see [RFC2863]. 324 ifLastChange The value of sysUpTime at the time the interface 325 entered its current operational state. 326 Also see [RFC2863]. 328 ifInOctets The number of received octets over the interface; 329 such as the number of octets received as 802.11 330 frames. 332 ifOutOctets The number of transmitted octets over the interface; 333 such as the number of octets transmitted as 802.11 334 frames. 336 ifInErrors The number of inbound frames dropped due to 337 uncorrectable errors. 339 ifInUnknownProtos 340 The number of received frame discarded during 341 frame header validation, including frames with 342 unrecognized label values. 344 ifOutErrors The number of outbound frames dropped due to 345 uncorrectable errors. 347 7.3. Relationship to the ENTITY-MIB 349 The ENTITY-MIB [RFC4133] meets need for a standardized way of 350 representing a single agent, which supports multiple instances of one 351 MIB. It could express a certain relationship between multiple 352 entities, and provide entity properties for each entity. 354 Under the wireless centralized architectures, the SNMP agent will run 355 on the AC, and not required on the WTP. By the ENTITY-MIB on the AC, 356 it could keep entity information such as firmware revision and 357 software revision of AC and WTPs. From the ENTITY-MIB perspective, 358 the overall physical entity (AC) is a 'compound' of multiple physical 359 entities (WTPs which connects to AC), all entities are identified by 360 Physical index. In the capwapBaseWtpTable of CAPWAP-BASE-MIB, it 361 uses capwapBaseWtpPhyIndex object to keep the mapping relationship of 362 WTP object between CAPWAP-BASE-MIB and ENTITY-MIB. 364 By combining the MIBs, operators could query AC and WTP's status and 365 properties. For example, they could get WTP's current status through 366 CAPWAP-BASE-MIB, and WTP's software revision information through 367 ENTITY-MIB. 369 7.4. Relationship to MIB standards of other SDOs 371 The MIB standards (such as IEEE 802.11 MIB) of a wireless binding is 372 required to support on the AC. The CAPWAP-BASE-MIB module is able to 373 support any wireless binding technology. Through ifIndex of 'WTP 374 Virtual Radio Interface' ifType, it provides consistent and abstract 375 way of reusing MIB objects of a wireless binding technology. 377 7.5. MIB modules required for IMPORTS 379 The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], 380 SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863], INET- 381 ADDRESS-MIB [RFC4001] and ENTITY-MIB [RFC4133]. 383 8. Example of CAPWAP-BASE-MIB Usage 385 With the idea of 'WTP Virtual Radio Interface' in the mind, the 386 usage of MIB will be easily understood. Here takes IEEE 802.11 387 binding technology as an example. 389 1) Identify each PHY radio by 'WTP Virtual Radio Interface' 391 According to [I-D.ietf-capwap-protocol-specification], each radio on 392 a WTP will be identified by a radio Id. Each WTP could be identified 393 by its serial number. 395 When configuration for a WTP is prepared before a WTP connects to AC, 396 the following information is available in the 397 CapwapBaseRadioBindTable. 399 In CapwapBaseRadioBindTable 400 { 401 capwapBaseWtpId = 12345678, 402 capwapBaseRadioId = 1, 403 capwapBaseWtpVirtualRadioifIndex = 10, 404 capwapBaseRadioWirelessBinding = dot11(2) 405 } 407 Suppose WTP's serial number is 12345678, and first radio id is 1. 408 On the AC, the ifIndex of interface in 'WTP Virtual Radio Interface' 409 ifType is 10 which represents the PHY radio 1. 411 By the mechanism of 'WTP Virtual Radio Interface', it seems WTP 412 PHY radios are located on the AC. The interface of 'WTP Virtual 413 Radio Interface' ifType is modeled by ifTable. 415 In ifTable 416 { 417 ifIndex = 10, 418 ifDescr = 'WTP Virtual Radio Interface', 419 ifType = IANAifType of 'WTP Virtual 420 Radio Interface', 421 ifMtu = 0, 422 ifSpeed = 0, 423 ifPhysAddress = 0.0.0.0.0.0, 424 ifAdminStatus = true, 425 ifOperStatus = false, 426 ifLastChange = 0, 427 ifInOctets = 0, 428 ifInUcastPkts = 0, 429 ifInDiscards = 0, 430 ifInErrors = 0, 431 ifInUnknownProtos = 0, 432 ifOutOctets = 0, 433 ifOutUcastPkts = 0, 434 ifOutDiscards = 0, 435 ifOutErrors = 0 436 } 438 2) Configure specific wireless binding parameters for 'WTP Virtual 439 Radio Interface' 440 It will be done on the AC through specific wireless binding MIB 441 such as IEEE 802.11 MIB. 442 For example, to configure parameter for 'WTP Virtual Radio Interface' 443 by 802.11 Dot11OperationTable. 445 In Dot11OperationTable 446 { 447 ifIndex = 10, 448 dot11MACAddress = 0.0.0.0.0.0, 449 dot11RTSThreshold = 2347, 450 dot11ShortRetryLimit = 7, 451 dot11LongRetryLimit = 4, 452 dot11FragmentationThreshold = 256, 453 dot11MaxTransmitMSDULifetime = 512, 454 dot11MaxReceiveLifetime = 512, 455 dot11ManufacturerID = 'capwap', 456 dot11ProductID = 'capwap' 457 } 458 In the example, it suppose ifIndex of an interface in 459 'WTP Virtual Radio Interface' ifType is 10. 461 3) Other configurations for a specific wireless binding 462 For example, WLAN service configuration will be done through CAPWAP 463 binding MIB and IEEE 802.11 MIB. In the CAPWAP 802.11 binding MIB 464 draft, it will give more explain. 466 4) WTP reports its current configuration status 467 After join phase and before WTP get configuration from AC, it will 468 report its current configuration status to AC through configuration 469 status request message. The data of MIB objects will be updated on 470 the AC. For example, for 802.11 binding, WTP will update data in the 471 ifTable and IEEE 802.11 MIB so on according to message content. 472 As an example for ifIndex 10, its ifOperStatus in ifTable will be 473 updated according to current radio operational status in the 474 CAPWAP message. 476 5) Query WTP and radio statistics data 477 After WTPs come to run status, operator could query WTP and 478 radio statistics data through CAPWAP-BASE-MIB and specific binding 479 MIB. For example, through dot11CountersTable in the IEEE 802.11 MIB, 480 operator could query counter data for radio which is identified 481 by ifIndex of a virtual radio interface. With capwapBaseAcState table 482 in the MIB, operator could query configuration and properties of 483 WTPs which are in run status. 485 6) Query other statistics data of a specific wireless binding 486 For example, operator could query the statistics data of 487 WLAN service through 802.11 binding MIB and IEEE 802.11 MIB. 488 In the CAPWAP 802.11 binding MIB draft, it will give more explain. 490 7) Query other properties of WTP 491 Operator could query MIB objects in the ENTITY-MIB by 492 capwapBaseWtpPhyIndex in the capwapBaseWtpTable of CAPWAP-BASE-MIB. 493 The properties of WTP such as software version, hardware version 494 and so on are available in the ENTITY-MIB. 496 9. Definitions 498 CAPWAP-BASE-MIB DEFINITIONS ::= BEGIN 500 IMPORTS 502 PhysAddress, TEXTUAL-CONVENTION, TruthValue, 503 DateAndTime 504 FROM SNMPv2-TC 506 InterfaceIndex 507 FROM IF-MIB 508 PhysicalIndex 509 FROM ENTITY-MIB 510 SnmpAdminString 511 FROM SNMP-FRAMEWORK-MIB 512 NOTIFICATION-GROUP, OBJECT-GROUP, MODULE-COMPLIANCE 513 FROM SNMPv2-CONF 514 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2, 515 Integer32, Unsigned32, Counter32 516 FROM SNMPv2-SMI 517 InetAddressType, InetAddress 518 FROM INET-ADDRESS-MIB; 520 capwapBaseMIB MODULE-IDENTITY 521 LAST-UPDATED "200810110000Z" -- Oct 11th, 2008 522 ORGANIZATION "IETF Control And Provisioning of Wireless Access 523 Points (CAPWAP) Working Group 524 http://www.ietf.org/html.charters/capwap-charter.html" 525 CONTACT-INFO 526 "General Discussion: capwap@frascone.com 527 To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap 529 Yang Shi 530 H3C, Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian 531 District,Beijing,China(100085) 532 Email: young@h3c.com 534 David T. Perkins 535 228 Bayview Dr 536 San Carlos, CA 94070 537 USA 538 Phone: +1 408 394-8702 539 Email: dperkins@snmpinfo.com 541 Chris Elliott 542 Cisco Systems, Inc. 543 7025 Kit Creek Rd., P.O. Box 14987 544 Research Triangle Park 27709 545 USA 546 Phone: +1 919-392-2146 547 Email: chelliot@cisco.com 549 Yong Zhang 550 Fortinet, Inc. 551 1090 Kifer Road 552 Sunnyvale, CA 94086 553 USA 554 Email: yzhang@fortinet.com" 556 DESCRIPTION 557 "Copyright (C) 2008 The Internet Society. This version of 558 the MIB module is part of RFC xxx; see the RFC itself 559 for full legal notices. 561 This MIB module contains managed object definitions for 562 the CAPWAP Protocol." 563 REVISION "200810110000Z" 564 DESCRIPTION 565 "Initial version published as RFC xxx" 566 ::= { mib-2 xxx } 568 -- Textual Conventions 570 CapwapBaseWtpIdTC ::= TEXTUAL-CONVENTION 571 DISPLAY-HINT "128a" 572 STATUS current 573 DESCRIPTION 574 "Represents an unique identifier of a WTP instance. 575 As usual, a serial number of WTP will be used." 576 SYNTAX OCTET STRING(SIZE(128)) 578 CapwapBaseStationIdTC ::= TEXTUAL-CONVENTION 579 DISPLAY-HINT "1x:" 580 STATUS current 581 DESCRIPTION 582 "Represents an unique identifier of a station instance. 583 As usual, the MAC address of station will be used." 584 SYNTAX OCTET STRING (SIZE (6)) 586 CapwapBaseRadioIdTC ::= TEXTUAL-CONVENTION 587 DISPLAY-HINT "d" 588 STATUS current 589 DESCRIPTION 590 "Represents an unique identifier of a radio on a WTP." 591 SYNTAX Unsigned32 (1..31) 593 CapwapBaseTunnelModeTC ::= TEXTUAL-CONVENTION 594 STATUS current 595 DESCRIPTION 596 "Represents the tunneling modes of operation that are 597 supported by the WTP. 598 The WTP MAY support more than one option, represented by 599 the bit field below. 600 unused(0) - This bit is unused 601 localBridging(1) - Local Bridging Mode, 602 dot3Tunnel(2) - 802.3 Frame Tunnel Mode, 603 nativeTunnel(3) - Native Frame Tunnel Mode." 604 REFERENCE 605 "Section 4.6.42. of CAPWAP Protocol Specification, RFC xxx." 606 SYNTAX BITS { unused(0), 607 localBridging(1), 608 dot3Tunnel(2), 609 nativeTunnel(3) } 611 CapwapBaseMacTypeTC ::= TEXTUAL-CONVENTION 612 STATUS current 613 DESCRIPTION 614 "Represents the MAC mode of operation supported by the WTP. 615 The following enumerated values are supported: 616 localMAC(0) - Local-MAC Mode, 617 splitMAC(1) - Split-MAC Mode, 618 both(2) - Both Local-MAC and Split-MAC." 619 REFERENCE 620 "Section 4.6.43. of CAPWAP Protocol Specification, RFC xxx." 621 SYNTAX INTEGER { localMAC(0), splitMAC(1), both(2) } 623 CapwapBaseChannelTypeTC::= TEXTUAL-CONVENTION 624 STATUS current 625 DESCRIPTION 626 "Represents the channel type for CAPWAP protocol. 627 The following enumerated values are supported: 628 data(1) - data Channel 629 control(2) - control Channel." 630 SYNTAX INTEGER { data(1), control(2) } 632 CapwapBaseAuthenMethodTC ::= TEXTUAL-CONVENTION 633 STATUS current 634 DESCRIPTION 635 "Represents the authentication credential type 636 for WTP. 637 The following enumerated values are supported: 638 other(1) - Other method, for example, vendor specific. 639 clear(2) - Clear text and no authentication, 640 x509(3) - X.509 Certificate authentication, 641 psk(4) - Pre-Shared Secret authentication, 642 As mandatory requirement, CAPWAP control channel 643 authentication should use DTLS, and either by certificate or 644 PSK. For data channel, DTLS is optional." 645 SYNTAX INTEGER { other(1), clear(2), x509(3), psk(4) } 647 -- Top level components of this MIB 649 -- Notifications 650 capwapBaseNotifications OBJECT IDENTIFIER 651 ::= { capwapBaseMIB 0 } 652 -- Tables, Scalars 653 capwapBaseObjects OBJECT IDENTIFIER 654 ::= { capwapBaseMIB 1 } 655 -- Conformance 656 capwapBaseConformance OBJECT IDENTIFIER 657 ::= { capwapBaseMIB 2 } 659 -- AC Objects Group 661 capwapBaseAc OBJECT IDENTIFIER 662 ::= { capwapBaseObjects 1 } 664 capwapBaseWtpSessions OBJECT-TYPE 665 SYNTAX Unsigned32 (0..65535) 666 MAX-ACCESS read-only 667 STATUS current 668 DESCRIPTION 669 "Represents the total number of WTPs which are connecting to 670 AC." 671 REFERENCE 672 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 673 ::= { capwapBaseAc 1 } 675 capwapBaseWtpSessionsLimit OBJECT-TYPE 676 SYNTAX Unsigned32 (0..65535) 677 MAX-ACCESS read-only 678 STATUS current 679 DESCRIPTION 680 "Represents the maximum number of WTP sessions supported by 681 the AC." 682 REFERENCE 683 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 684 ::= { capwapBaseAc 2 } 686 capwapBaseStationSessions OBJECT-TYPE 687 SYNTAX Unsigned32 (0..65535) 688 MAX-ACCESS read-only 689 STATUS current 690 DESCRIPTION 691 "Represents the total number of stations which are accessing 692 the wireless service provided by the AC." 693 REFERENCE 694 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 695 ::= { capwapBaseAc 3 } 697 capwapBaseStationSessionsLimit OBJECT-TYPE 698 SYNTAX Unsigned32 (0..65535) 699 MAX-ACCESS read-only 700 STATUS current 701 DESCRIPTION 702 "Represents the maximum number of station sessions supported by 703 the AC." 704 REFERENCE 705 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 706 ::= { capwapBaseAc 4 } 708 capwapBaseDataChannelSecOptions OBJECT-TYPE 709 SYNTAX BITS { other(0), clear(1), dtls(2) } 710 MAX-ACCESS read-only 711 STATUS current 712 DESCRIPTION 713 "Represents the security policy supported for CAPWAP data 714 channel. 715 The AC MAY support more than one option, represented by the bit 716 field below. 717 other(0) - Other method, for example, vendor specific. 718 clear(1) - Clear Text, 719 dtls(2) - DTLS." 720 REFERENCE 721 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 722 ::= { capwapBaseAc 5 } 724 capwapBaseWtpAuthenOptions OBJECT-TYPE 725 SYNTAX BITS { unused(0), x509(1), psk(2) } 726 MAX-ACCESS read-only 727 STATUS current 728 DESCRIPTION 729 "Represents the authentication credential type supported by the 730 AC for control channel. 731 The AC MAY support more than one option, represented by the bit 732 field below. 733 unused(0) - This bit is unused 734 x509(1) - X.509 Certificate Based 735 psk(2) - Pre-Shared Secret." 736 REFERENCE 737 "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." 738 ::= { capwapBaseAc 6 } 740 capwapBaseWtpFallbackEnable OBJECT-TYPE 741 SYNTAX TruthValue 742 MAX-ACCESS read-write 743 STATUS current 744 DESCRIPTION 745 "Represents whether to enable or disable automatic CAPWAP 746 fallback in the event that a WTP detects its preferred AC, and 747 is not currently connected to it." 748 REFERENCE 749 "Section 4.6.42. of CAPWAP Protocol Specification, RFC xxx." 750 ::= { capwapBaseAc 7 } 752 -- capwapBaseAcNameListTable table 754 capwapBaseAcNameListTable OBJECT-TYPE 755 SYNTAX SEQUENCE OF CapwapBaseAcNameListEntry 756 MAX-ACCESS not-accessible 757 STATUS current 758 DESCRIPTION 759 "A table of objects that display AC name list." 760 ::= { capwapBaseAc 8 } 762 capwapBaseAcNameListEntry OBJECT-TYPE 763 SYNTAX CapwapBaseAcNameListEntry 764 MAX-ACCESS not-accessible 765 STATUS current 766 DESCRIPTION 767 "A set of objects that display AC name list." 768 INDEX { capwapBaseAcNameListId } 769 ::= { capwapBaseAcNameListTable 1 } 771 CapwapBaseAcNameListEntry ::= SEQUENCE { 772 capwapBaseAcNameListId Unsigned32, 773 capwapBaseAcNameListName OCTET STRING, 774 capwapBaseAcNameListPriority Unsigned32 } 776 capwapBaseAcNameListId OBJECT-TYPE 777 SYNTAX Unsigned32 (1..255) 778 MAX-ACCESS not-accessible 779 STATUS current 780 DESCRIPTION 781 "Represents a unique id for a AC Name list." 782 ::= { capwapBaseAcNameListEntry 1 } 784 capwapBaseAcNameListName OBJECT-TYPE 785 SYNTAX OCTET STRING(SIZE(512)) 786 MAX-ACCESS read-only 787 STATUS current 788 DESCRIPTION 789 "Represents the name of an AC." 790 REFERENCE 791 "Section 4.6.5. of CAPWAP Protocol Specification, RFC xxx." 792 ::= { capwapBaseAcNameListEntry 2 } 794 capwapBaseAcNameListPriority OBJECT-TYPE 795 SYNTAX Unsigned32 (1..255) 796 MAX-ACCESS read-only 797 STATUS current 798 DESCRIPTION 799 "Represents the priority order of the preferred AC. 800 For instance, the value of one (1) is used to set the primary 801 AC, the value of two (2) is used to set the secondary, etc." 802 REFERENCE 803 "Section 4.6.5. of CAPWAP Protocol Specification, RFC xxx." 804 ::= { capwapBaseAcNameListEntry 3 } 806 -- End of AC Objects Group 808 -- WTP Objects Group 810 capwapBaseWtps OBJECT IDENTIFIER 811 ::= { capwapBaseObjects 2 } 813 -- capwapBaseWtpStateTable table 815 capwapBaseWtpStateTable OBJECT-TYPE 816 SYNTAX SEQUENCE OF CapwapBaseWtpStateEntry 817 MAX-ACCESS not-accessible 818 STATUS current 819 DESCRIPTION 820 "A table of objects that display WTP CAPWAP FSM state." 821 ::= { capwapBaseWtps 1 } 823 capwapBaseWtpStateEntry OBJECT-TYPE 824 SYNTAX CapwapBaseWtpStateEntry 825 MAX-ACCESS not-accessible 826 STATUS current 827 DESCRIPTION 828 "A set of objects that display WTP CAPWAP FSM state." 829 INDEX { capwapBaseWtpId } 830 ::= { capwapBaseWtpStateTable 1 } 832 CapwapBaseWtpStateEntry ::= SEQUENCE { 833 capwapBaseWtpId CapwapBaseWtpIdTC, 834 capwapBaseWtpIpAddressType InetAddressType, 835 capwapBaseWtpIpAddress InetAddress, 836 capwapBaseWtpPhyAddress PhysAddress, 837 capwapBaseWtpState INTEGER } 839 capwapBaseWtpId OBJECT-TYPE 840 SYNTAX CapwapBaseWtpIdTC 841 MAX-ACCESS not-accessible 842 STATUS current 843 DESCRIPTION 844 "Represents the unique identifier of a WTP." 845 ::= { capwapBaseWtpStateEntry 1 } 847 capwapBaseWtpIpAddressType OBJECT-TYPE 848 SYNTAX InetAddressType 849 MAX-ACCESS read-only 850 STATUS current 851 DESCRIPTION 852 "Represents the type of IP address of a WTP." 853 ::= { capwapBaseWtpStateEntry 2 } 855 capwapBaseWtpIpAddress OBJECT-TYPE 856 SYNTAX InetAddress 857 MAX-ACCESS read-only 858 STATUS current 859 DESCRIPTION 860 "Represents the IP address of a WTP." 861 ::= { capwapBaseWtpStateEntry 3 } 863 capwapBaseWtpPhyAddress OBJECT-TYPE 864 SYNTAX PhysAddress 865 MAX-ACCESS read-only 866 STATUS current 867 DESCRIPTION 868 "Represents the PHY address of a WTP." 869 ::= { capwapBaseWtpStateEntry 4 } 871 capwapBaseWtpState OBJECT-TYPE 872 SYNTAX INTEGER { 873 dtls(1), join(2), image(3), configure(4), 874 dataCheck(5), run(6), clear(7), unknown(8) 875 } 876 MAX-ACCESS read-only 877 STATUS current 878 DESCRIPTION 879 "Represents the various possible CAPWAP FSM states of WTP 880 The following enumerated values are supported: 881 dtls(1) - DTLS negotiation states, which include 882 DTLS Setup, Authorize, DTLS Connect. 883 join(2) - WTP is joining with AC, 884 image(3) - WTP is downloading software, 885 configure(4) - WTP is getting configuration from AC, 886 dataCheck(5) - AC is waiting for the Data Channel Keep 887 Alive Packet. 888 run(6) - WTP comes to run state, 889 clear(7) - WTP recoveries default configuration. 890 unknown(8) - Operator already prepare configuration 891 for WTP, while WTP has not contact with AC 892 till now." 893 REFERENCE 894 "Section 2.3.1. of CAPWAP Protocol Specification, RFC xxx." 895 ::= { capwapBaseWtpStateEntry 5 } 897 -- End of capwapBaseWtpStateTable Table 899 -- capwapBaseWtpTable Table 901 capwapBaseWtpTable OBJECT-TYPE 902 SYNTAX SEQUENCE OF CapwapBaseWtpEntry 903 MAX-ACCESS not-accessible 904 STATUS current 905 DESCRIPTION 906 "A table of objects that display and control WTPs in 907 running state. Values of all read-write objects in this 908 table are persistent at restart/reboot." 909 ::= { capwapBaseWtps 2 } 911 capwapBaseWtpEntry OBJECT-TYPE 912 SYNTAX CapwapBaseWtpEntry 913 MAX-ACCESS not-accessible 914 STATUS current 915 DESCRIPTION 916 "A set of objects that display and control a WTP in 917 running state." 918 INDEX { capwapBaseWtpCurrId } 919 ::= { capwapBaseWtpTable 1 } 921 CapwapBaseWtpEntry ::= SEQUENCE { 922 capwapBaseWtpCurrId CapwapBaseWtpIdTC, 923 capwapBaseWtpPhyIndex PhysicalIndex, 924 capwapBaseWtpName SnmpAdminString, 925 capwapBaseWtpLocation SnmpAdminString, 926 capwapBaseWtpBaseMacAddress PhysAddress, 927 capwapBaseTunnelModeOptions CapwapBaseTunnelModeTC, 928 capwapBaseMacTypeOptions CapwapBaseMacTypeTC, 929 capwapBaseWtpDiscoveryType INTEGER, 930 capwapBaseWtpRadiosInUseNum Unsigned32, 931 capwapBaseWtpRadioNumLimit Unsigned32, 932 capwapBaseWtpStaticIpEnable TruthValue, 933 capwapBaseWtpStaticIpType InetAddressType, 934 capwapBaseWtpStaticIp InetAddress, 935 capwapBaseWtpNetmask InetAddress, 936 capwapBaseWtpGateway InetAddress, 937 capwapBaseWtpRetransmitCount Unsigned32 } 939 capwapBaseWtpCurrId OBJECT-TYPE 940 SYNTAX CapwapBaseWtpIdTC 941 MAX-ACCESS not-accessible 942 STATUS current 943 DESCRIPTION 944 "Represents the unique identifier of a WTP Which is 945 in running state." 946 ::= { capwapBaseWtpEntry 1 } 948 capwapBaseWtpPhyIndex OBJECT-TYPE 949 SYNTAX PhysicalIndex 950 MAX-ACCESS read-only 951 STATUS current 952 DESCRIPTION 953 "Represents the unique physical index of a physical entity 954 in the ENTITY-MIB. The information such as software version 955 of specific WTP could be accessed through the index." 956 ::= { capwapBaseWtpEntry 2 } 958 capwapBaseWtpName OBJECT-TYPE 959 SYNTAX SnmpAdminString 960 MAX-ACCESS read-write 961 STATUS current 962 DESCRIPTION 963 "Represents the name of a WTP." 964 REFERENCE 965 "Section 4.6.44. of CAPWAP Protocol Specification, RFC xxx." 966 ::= { capwapBaseWtpEntry 3 } 968 capwapBaseWtpLocation OBJECT-TYPE 969 SYNTAX SnmpAdminString 970 MAX-ACCESS read-write 971 STATUS current 972 DESCRIPTION 973 "Represents the location of a WTP." 974 REFERENCE 975 "Section 4.6.29. of CAPWAP Protocol Specification, RFC xxx." 976 ::= { capwapBaseWtpEntry 4 } 978 capwapBaseWtpBaseMacAddress OBJECT-TYPE 979 SYNTAX PhysAddress 980 MAX-ACCESS read-only 981 STATUS current 982 DESCRIPTION 983 "Represents the WTP's Base MAC Address, which MAY be assigned 984 to the primary Ethernet interface." 985 REFERENCE 986 "Section 4.6.39. of CAPWAP Protocol Specification, RFC xxx." 987 ::= { capwapBaseWtpEntry 5 } 989 capwapBaseTunnelModeOptions OBJECT-TYPE 990 SYNTAX CapwapBaseTunnelModeTC 991 MAX-ACCESS read-only 992 STATUS current 993 DESCRIPTION 994 "Represents the tunneling modes of operation supported by 995 the WTP. 996 The WTP MAY support more than one option, represented by the 997 bit field below. 998 localBridging(1) - Local Bridging Mode, 999 dot3Tunnel(2) - 802.3 Frame Tunnel Mode, 1000 nativeTunnel(3) - Native Frame Tunnel Mode." 1001 REFERENCE 1002 "Section 4.6.42. of CAPWAP Protocol Specification, RFC xxx." 1003 ::= { capwapBaseWtpEntry 6 } 1005 capwapBaseMacTypeOptions OBJECT-TYPE 1006 SYNTAX CapwapBaseMacTypeTC 1007 MAX-ACCESS read-only 1008 STATUS current 1009 DESCRIPTION 1010 "Represents the MAC mode of operation supported by the WTP. 1011 The following enumerated values are supported: 1012 localMAC(0) - Local-MAC Mode, 1013 splitMAC(1) - Split-MAC Mode, 1014 both(2) - Both Local-MAC Mode and Split-MAC Mode." 1015 REFERENCE 1016 "Section 4.6.43. of CAPWAP Protocol Specification, RFC xxx." 1017 ::= { capwapBaseWtpEntry 7 } 1019 capwapBaseWtpDiscoveryType OBJECT-TYPE 1020 SYNTAX INTEGER { 1021 unknown(0), staticConfig(1), dhcp(2), dns(3), acRef(4) 1022 } 1023 MAX-ACCESS read-only 1024 STATUS current 1025 DESCRIPTION 1026 "Represents how WTP discovers the AC. 1027 The following enumerated values are supported: 1028 unknown(0) - Unknown, 1029 staticConfig(1) - Static Configuration, 1030 dhcp(2) - DHCP, 1031 dns(3) - DNS, 1032 acRef(4) - AC Referral." 1033 REFERENCE 1034 "Section 4.6.21. of CAPWAP Protocol Specification, RFC xxx." 1035 ::= { capwapBaseWtpEntry 8 } 1037 capwapBaseWtpRadiosInUseNum OBJECT-TYPE 1038 SYNTAX Unsigned32 (0..255) 1039 MAX-ACCESS read-only 1040 STATUS current 1041 DESCRIPTION 1042 "Represents the number of radios in use in the WTP." 1043 REFERENCE 1044 "Section 4.6.40. of CAPWAP Protocol Specification, RFC xxx." 1045 ::= { capwapBaseWtpEntry 9 } 1047 capwapBaseWtpRadioNumLimit OBJECT-TYPE 1048 SYNTAX Unsigned32 (0..255) 1049 MAX-ACCESS read-only 1050 STATUS current 1051 DESCRIPTION 1052 "Represents the maximum radio number supported by the WTP." 1053 REFERENCE 1054 "Section 4.6.40. of CAPWAP Protocol Specification, RFC xxx." 1055 ::= { capwapBaseWtpEntry 10 } 1057 capwapBaseWtpStaticIpEnable OBJECT-TYPE 1058 SYNTAX TruthValue 1059 MAX-ACCESS read-write 1060 STATUS current 1061 DESCRIPTION 1062 "Represents whether the WTP should use a static IP address 1063 or not. A value of false disables the static IP address, 1064 while a value of true enables it." 1065 REFERENCE 1066 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1067 ::= { capwapBaseWtpEntry 11 } 1069 capwapBaseWtpStaticIpType OBJECT-TYPE 1070 SYNTAX InetAddressType 1071 MAX-ACCESS read-write 1072 STATUS current 1073 DESCRIPTION 1074 "Represents whether WTP uses IPV4 or IPV6 static IP address." 1075 ::= { capwapBaseWtpEntry 12 } 1077 capwapBaseWtpStaticIp OBJECT-TYPE 1078 SYNTAX InetAddress 1079 MAX-ACCESS read-write 1080 STATUS current 1081 DESCRIPTION 1082 "When capwapBaseWtpStaticIpEnable is true, it represents the 1083 static IP address to assign to the WTP." 1084 REFERENCE 1085 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1086 ::= { capwapBaseWtpEntry 13 } 1088 capwapBaseWtpNetmask OBJECT-TYPE 1089 SYNTAX InetAddress 1090 MAX-ACCESS read-write 1091 STATUS current 1092 DESCRIPTION 1093 "When capwapBaseWtpStaticIpEnable is true, it represents the 1094 netmask to assign to the WTP." 1095 REFERENCE 1096 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1097 ::= { capwapBaseWtpEntry 14 } 1099 capwapBaseWtpGateway OBJECT-TYPE 1100 SYNTAX InetAddress 1101 MAX-ACCESS read-write 1102 STATUS current 1103 DESCRIPTION 1104 "When capwapBaseWtpStaticIpEnable is true, it represents the 1105 gateway to assign to the WTP." 1106 REFERENCE 1107 "Section 4.6.47. of CAPWAP Protocol Specification, RFC xxx." 1108 ::= { capwapBaseWtpEntry 15 } 1110 capwapBaseWtpRetransmitCount OBJECT-TYPE 1111 SYNTAX Unsigned32 1112 MAX-ACCESS read-only 1113 STATUS current 1114 DESCRIPTION 1115 "Represents the number of retransmissions for a given 1116 CAPWAP packet." 1117 REFERENCE 1118 "Section 4.8.8. of CAPWAP Protocol Specification, RFC xxx." 1119 ::= { capwapBaseWtpEntry 16 } 1121 -- End of capwapBaseWtpTable table 1123 -- capwapBaseRadioBindTable Table 1125 capwapBaseRadioBindTable OBJECT-TYPE 1126 SYNTAX SEQUENCE OF CapwapBaseRadioBindEntry 1127 MAX-ACCESS not-accessible 1128 STATUS current 1129 DESCRIPTION 1130 "A table of objects that display the mapping relationship 1131 between specific interface of 'WTP Virtual Radio Interface' 1132 ifType and PHY radio. The mapping relationship in this table 1133 is persistent at restart/reboot." 1134 ::= { capwapBaseWtps 3 } 1136 capwapBaseRadioBindEntry OBJECT-TYPE 1137 SYNTAX CapwapBaseRadioBindEntry 1138 MAX-ACCESS not-accessible 1139 STATUS current 1140 DESCRIPTION 1141 "A set of objects that display the mapping relationship 1142 between 'WTP Virtual Radio' and PHY radio." 1143 INDEX { capwapBaseWtpId, capwapBaseRadioId } 1144 ::= { capwapBaseRadioBindTable 1 } 1146 CapwapBaseRadioBindEntry ::= SEQUENCE { 1147 capwapBaseRadioId CapwapBaseRadioIdTC, 1148 capwapBaseVirtualRadioIfIndex InterfaceIndex, 1149 capwapBaseRadioWirelessBinding INTEGER 1150 } 1152 capwapBaseRadioId OBJECT-TYPE 1153 SYNTAX CapwapBaseRadioIdTC 1154 MAX-ACCESS not-accessible 1155 STATUS current 1156 DESCRIPTION 1157 "Represents the identifier of a PHY radio on a WTP, and only 1158 requires unique on a WTP. 1159 For example, WTP A and WTP B will use same value of 1160 capwapBaseRadioId for their first radio." 1161 REFERENCE 1162 "Section 4.3. of CAPWAP Protocol Specification, RFC xxx." 1163 ::= { capwapBaseRadioBindEntry 1 } 1165 capwapBaseVirtualRadioIfIndex OBJECT-TYPE 1166 SYNTAX InterfaceIndex 1167 MAX-ACCESS read-only 1168 STATUS current 1169 DESCRIPTION 1170 "Represents the index value that uniquely identifies a 1171 'WLAN Virtual Radio Interface'. The interface identified by a 1172 particular value of this index is the same interface as 1173 identified by the same value of ifIndex. 1174 Before WTPs connect to AC and get configuration, operator 1175 will prepare configuration for them. On the AC, there are 1176 interfaces of 'WTP Virtual Radio Interface' ifType which 1177 represent PHY radio interfaces on the WTP. 1178 As most MIBs use ifIndex to identify an interface for 1179 configuration and statistic data, for example, IEEE 802.11 MIB. 1180 It will be very easy to reuse other MIBs such as IEEE 802.11 1181 MIB by 'WTP Virtual Radio Interface'." 1182 ::= { capwapBaseRadioBindEntry 2 } 1184 capwapBaseRadioWirelessBinding OBJECT-TYPE 1185 SYNTAX INTEGER { reserved0(0), dot11(1), reserved2(2), epc(3) } 1186 MAX-ACCESS read-only 1187 STATUS current 1188 DESCRIPTION 1189 "Represents the wireless binding type for radio. 1190 The following enumerated values are supported: 1191 reserved0(0) - Reserved, 1192 dot11(1) - IEEE 802.11, 1193 reserved2(2) - Reserved, 1194 epc(3) - EPCGlobal." 1195 REFERENCE 1196 "Section 4.3. of CAPWAP Protocol Specification, RFC xxx." 1197 ::= { capwapBaseRadioBindEntry 3 } 1199 -- End of capwapBaseRadioBindTable Table 1201 -- capwapBaseStationTable Table 1203 capwapBaseStationTable OBJECT-TYPE 1204 SYNTAX SEQUENCE OF CapwapBaseStationEntry 1205 MAX-ACCESS not-accessible 1206 STATUS current 1207 DESCRIPTION 1208 "A table of objects that display stations which are accessing 1209 the wireless service provided by the AC." 1210 ::= { capwapBaseWtps 4 } 1212 capwapBaseStationEntry OBJECT-TYPE 1213 SYNTAX CapwapBaseStationEntry 1214 MAX-ACCESS not-accessible 1215 STATUS current 1216 DESCRIPTION 1217 "A set of objects that display a station which is 1218 associated with the specific radio on the WTP." 1219 INDEX { capwapBaseWtpCurrId, 1220 capwapBaseRadioId, 1221 capwapBaseStationId } 1223 ::= { capwapBaseStationTable 1 } 1225 CapwapBaseStationEntry ::= SEQUENCE { 1226 capwapBaseStationId CapwapBaseStationIdTC, 1227 capwapBaseStationAddedTime DateAndTime, 1228 capwapBaseStationVlanName SnmpAdminString 1229 } 1231 capwapBaseStationId OBJECT-TYPE 1232 SYNTAX CapwapBaseStationIdTC 1233 MAX-ACCESS not-accessible 1234 STATUS current 1235 DESCRIPTION 1236 "Represents the unique identifier of the station." 1237 REFERENCE 1238 "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." 1239 ::= { capwapBaseStationEntry 1 } 1241 capwapBaseStationAddedTime OBJECT-TYPE 1242 SYNTAX DateAndTime 1243 MAX-ACCESS read-only 1244 STATUS current 1245 DESCRIPTION 1246 "Represents the time when the station is added." 1247 REFERENCE 1248 "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." 1249 ::= { capwapBaseStationEntry 2 } 1251 capwapBaseStationVlanName OBJECT-TYPE 1252 SYNTAX SnmpAdminString 1253 MAX-ACCESS read-only 1254 STATUS current 1255 DESCRIPTION 1256 "Represents VLAN name to which the station is associated." 1257 REFERENCE 1258 "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." 1259 ::= { capwapBaseStationEntry 3 } 1261 -- End of capwapBaseStationTable Table 1263 -- capwapBaseWtpRebootStatTable 1265 capwapBaseWtpRebootStatsTable OBJECT-TYPE 1266 SYNTAX SEQUENCE OF CapwapBaseWtpRebootStatsEntry 1267 MAX-ACCESS not-accessible 1268 STATUS current 1269 DESCRIPTION 1270 "A table of objects that display WTPs' reboot statistics." 1271 REFERENCE 1272 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1273 ::= { capwapBaseWtps 5 } 1275 capwapBaseWtpRebootStatsEntry OBJECT-TYPE 1276 SYNTAX CapwapBaseWtpRebootStatsEntry 1277 MAX-ACCESS not-accessible 1278 STATUS current 1279 DESCRIPTION 1280 "A set of objects that display the reboot statistic data 1281 of a WTP." 1282 REFERENCE 1283 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1284 INDEX { capwapBaseWtpCurrId } 1285 ::= { capwapBaseWtpRebootStatsTable 1 } 1287 CapwapBaseWtpRebootStatsEntry ::= SEQUENCE { 1288 capwapBaseWtpRebootCount Counter32, 1289 capwapBaseWtpInitCount Counter32, 1290 capwapBaseWtpLinkFailureCount Counter32, 1291 capwapBaseWtpSwFailureCount Counter32, 1292 capwapBaseWtpHwFailureCount Counter32, 1293 capwapBaseWtpOtherFailureCount Counter32, 1294 capwapBaseWtpUnknownFailureCount Counter32, 1295 capwapBaseWtpLastFailureType INTEGER 1296 } 1298 capwapBaseWtpRebootCount OBJECT-TYPE 1299 SYNTAX Counter32 1300 MAX-ACCESS read-only 1301 STATUS current 1302 DESCRIPTION 1303 "Represents the number of reboots that have occurred due to a 1304 WTP crash. A value of 65535 implies that this information is 1305 not available on the WTP." 1306 REFERENCE 1307 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1308 ::= { capwapBaseWtpRebootStatsEntry 1 } 1310 capwapBaseWtpInitCount OBJECT-TYPE 1311 SYNTAX Counter32 1312 MAX-ACCESS read-only 1313 STATUS current 1314 DESCRIPTION 1315 "Represents the number of reboots that have occurred at the 1316 request of a CAPWAP protocol message, such as a change in 1317 configuration that required a reboot or an explicit CAPWAP 1318 protocol reset request. A value of 65535 implies that this 1319 information is not available on the WTP." 1320 REFERENCE 1321 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1322 ::= { capwapBaseWtpRebootStatsEntry 2 } 1324 capwapBaseWtpLinkFailureCount OBJECT-TYPE 1325 SYNTAX Counter32 1326 MAX-ACCESS read-only 1327 STATUS current 1328 DESCRIPTION 1329 "Represents the number of times that a CAPWAP protocol 1330 connection with an AC has failed due to link failure." 1331 REFERENCE 1332 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1333 ::= { capwapBaseWtpRebootStatsEntry 3 } 1335 capwapBaseWtpSwFailureCount OBJECT-TYPE 1336 SYNTAX Counter32 1337 MAX-ACCESS read-only 1338 STATUS current 1339 DESCRIPTION 1340 "Represents the number of times that a CAPWAP protocol 1341 connection with an AC has failed due to software related 1342 reasons." 1343 REFERENCE 1344 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1345 ::= { capwapBaseWtpRebootStatsEntry 4 } 1347 capwapBaseWtpHwFailureCount OBJECT-TYPE 1348 SYNTAX Counter32 1349 MAX-ACCESS read-only 1350 STATUS current 1351 DESCRIPTION 1352 "Represents the number of times that a CAPWAP protocol 1353 connection with an AC has failed due to hardware related 1354 reasons." 1355 REFERENCE 1356 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1357 ::= { capwapBaseWtpRebootStatsEntry 5 } 1359 capwapBaseWtpOtherFailureCount OBJECT-TYPE 1360 SYNTAX Counter32 1361 MAX-ACCESS read-only 1362 STATUS current 1363 DESCRIPTION 1364 "Represents the number of times that a CAPWAP protocol 1365 connection with an AC has failed due to known reasons, other 1366 than AC initiated, link, software or hardware failure." 1367 REFERENCE 1368 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1369 ::= { capwapBaseWtpRebootStatsEntry 6 } 1371 capwapBaseWtpUnknownFailureCount OBJECT-TYPE 1372 SYNTAX Counter32 1373 MAX-ACCESS read-only 1374 STATUS current 1375 DESCRIPTION 1376 "Represents the number of times that a CAPWAP protocol 1377 connection with an AC has failed for unknown reasons." 1378 REFERENCE 1379 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1380 ::= { capwapBaseWtpRebootStatsEntry 7 } 1382 capwapBaseWtpLastFailureType OBJECT-TYPE 1383 SYNTAX INTEGER { notSupport(0), 1384 acInit(1), 1385 linkFailure(2), 1386 swFailure(3), 1387 hwFailure(4), 1388 otherFailure(5), 1389 unknown(255) 1390 } 1391 MAX-ACCESS read-only 1392 STATUS current 1393 DESCRIPTION 1394 "Represents the failure type of the most recent WTP failure. 1395 The following enumerated values are supported: 1396 notSupport(0) - Not Supported, 1397 acInit(1) - AC Initiated, 1398 linkFailure(2) - Link Failure, 1399 swFailure(3) - Software Failure, 1400 hwFailure(4) - Hardware Failure, 1401 otherFailure(5) - Other Failure, 1402 unknown(255) - Unknown (e.g., WTP doesn't keep track 1403 of info)." 1404 REFERENCE 1405 "Section 4.6.46. of CAPWAP Protocol Specification, RFC xxx." 1406 ::= { capwapBaseWtpRebootStatsEntry 8 } 1408 -- End of capwapBaseWtpRebootStatsTable table 1410 -- capwapBaseRadioStatsTable table 1412 capwapBaseRadioStatsTable OBJECT-TYPE 1413 SYNTAX SEQUENCE OF CapwapBaseRadioStatsEntry 1414 MAX-ACCESS not-accessible 1415 STATUS current 1416 DESCRIPTION 1417 "A table of objects that display statistics on radios behavior, 1418 and reasons why the WTP radio has been reset." 1419 REFERENCE 1420 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 1421 ::= { capwapBaseWtps 6 } 1423 capwapBaseRadioStatsEntry OBJECT-TYPE 1424 SYNTAX CapwapBaseRadioStatsEntry 1425 MAX-ACCESS not-accessible 1426 STATUS current 1427 DESCRIPTION 1428 "A set of objects that display the statistic data of 1429 events happened on a specific radio of a WTP." 1430 INDEX { capwapBaseWtpCurrId, capwapBaseRadioId } 1431 ::= { capwapBaseRadioStatsTable 1 } 1433 CapwapBaseRadioStatsEntry ::= SEQUENCE { 1434 capwapBaseRadioResetCount Counter32, 1435 capwapBaseRadioSwFailCount Counter32, 1436 capwapBaseRadioHwFailCount Counter32, 1437 capwapBaseRadioOtherFailCount Counter32, 1438 capwapBaseRadioUnknownFailCount Counter32, 1439 capwapBaseRadioConfigUpdateCount Counter32, 1440 capwapBaseRadioChannelChangeCount Counter32, 1441 capwapBaseRadioBandChangeCount Counter32, 1442 capwapBaseRadioCurrentNoiseFloor Integer32, 1443 capwapBaseRadioDecryptErrorCount Counter32, 1444 capwapBaseRadioLastFailType INTEGER 1445 } 1447 capwapBaseRadioResetCount OBJECT-TYPE 1448 SYNTAX Counter32 1449 MAX-ACCESS read-only 1450 STATUS current 1451 DESCRIPTION 1452 "Represents the number of times that that the radio has been 1453 reset." 1454 REFERENCE 1455 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 1456 ::= { capwapBaseRadioStatsEntry 1 } 1458 capwapBaseRadioSwFailCount OBJECT-TYPE 1459 SYNTAX Counter32 1460 MAX-ACCESS read-only 1461 STATUS current 1462 DESCRIPTION 1463 "Represents the number of times that the radio has failed due 1464 to software related reasons." 1465 REFERENCE 1466 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 1467 ::= { capwapBaseRadioStatsEntry 2 } 1469 capwapBaseRadioHwFailCount OBJECT-TYPE 1470 SYNTAX Counter32 1471 MAX-ACCESS read-only 1472 STATUS current 1473 DESCRIPTION 1474 "Represents the number of times that the radio has failed due 1475 to hardware related reasons." 1476 REFERENCE 1477 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 1478 ::= { capwapBaseRadioStatsEntry 3 } 1480 capwapBaseRadioOtherFailCount OBJECT-TYPE 1481 SYNTAX Counter32 1482 MAX-ACCESS read-only 1483 STATUS current 1484 DESCRIPTION 1485 "Represents the number of times that the radio has failed due to 1486 known reasons, other than software or hardware failure." 1487 REFERENCE 1488 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 1489 ::= { capwapBaseRadioStatsEntry 4 } 1491 capwapBaseRadioUnknownFailCount OBJECT-TYPE 1492 SYNTAX Counter32 1493 MAX-ACCESS read-only 1494 STATUS current 1495 DESCRIPTION 1496 "Represents the number of times that the radio has failed for 1497 unknown reasons." 1498 REFERENCE 1499 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 1500 ::= { capwapBaseRadioStatsEntry 5 } 1502 capwapBaseRadioConfigUpdateCount OBJECT-TYPE 1503 SYNTAX Counter32 1504 MAX-ACCESS read-only 1505 STATUS current 1506 DESCRIPTION 1507 "Represents the number of times that the radio configuration has 1508 been updated." 1510 REFERENCE 1511 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 1512 ::= { capwapBaseRadioStatsEntry 6 } 1514 capwapBaseRadioChannelChangeCount OBJECT-TYPE 1515 SYNTAX Counter32 1516 MAX-ACCESS read-only 1517 STATUS current 1518 DESCRIPTION 1519 "Represents the number of times that the radio channel has 1520 been changed." 1521 REFERENCE 1522 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 1523 ::= { capwapBaseRadioStatsEntry 7 } 1525 capwapBaseRadioBandChangeCount OBJECT-TYPE 1526 SYNTAX Counter32 1527 MAX-ACCESS read-only 1528 STATUS current 1529 DESCRIPTION 1530 "Represents the number of times that the radio has changed 1531 frequency bands." 1532 REFERENCE 1533 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 1534 ::= { capwapBaseRadioStatsEntry 8 } 1536 capwapBaseRadioCurrentNoiseFloor OBJECT-TYPE 1537 SYNTAX Integer32 1538 UNITS "dBm" 1539 MAX-ACCESS read-only 1540 STATUS current 1541 DESCRIPTION 1542 "Represents the noise floor of the radio receiver in units of 1543 dBm." 1544 REFERENCE 1545 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 1546 ::= { capwapBaseRadioStatsEntry 9 } 1548 capwapBaseRadioDecryptErrorCount OBJECT-TYPE 1549 SYNTAX Counter32 1550 MAX-ACCESS read-only 1551 STATUS current 1552 DESCRIPTION 1553 "Represents the number of decryption errors that occurred on the 1554 WTP. Note that this field is only valid in cases where the WTP 1555 provides encryption/decryption services." 1556 REFERENCE 1557 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 1559 ::= { capwapBaseRadioStatsEntry 10 } 1561 capwapBaseRadioLastFailType OBJECT-TYPE 1562 SYNTAX INTEGER { 1563 notSupport(0), 1564 swFailure(1), 1565 hwFailure(2), 1566 otherFailure(3), 1567 unknown(255) 1568 } 1569 MAX-ACCESS read-only 1570 STATUS current 1571 DESCRIPTION 1572 "Represents the failure type of the most recent radio failure. 1573 The following enumerated values are supported: 1574 notSupport(0) - Not Supported, 1575 swFailure(1) - Software Failure, 1576 hwFailure(2) - Hardware Failure, 1577 otherFailure(3) - Other Failure, 1578 unknown(255) - Unknown." 1579 REFERENCE 1580 "Section 4.6.45. of CAPWAP Protocol Specification, RFC xxx." 1581 ::= { capwapBaseRadioStatsEntry 11 } 1583 -- End of capwapBaseRadioStatsTable table 1585 -- CAPWAP Base Parameters Group 1587 capwapBaseParameters OBJECT IDENTIFIER 1588 ::= { capwapBaseObjects 3 } 1590 capwapBaseDataChannelDeadInterval OBJECT-TYPE 1591 SYNTAX Unsigned32 1592 UNITS "second" 1593 MAX-ACCESS read-only 1594 STATUS current 1595 DESCRIPTION 1596 "Represents the minimum time, in seconds, a WTP MUST wait 1597 without having received a Data Channel Keep Alive packet 1598 before the destination for the Data Channel Keep Alive 1599 packets may be considered dead." 1600 REFERENCE 1601 "Section 4.7.3. of CAPWAP Protocol Specification, RFC xxx." 1602 ::= { capwapBaseParameters 1 } 1604 capwapBaseDataCheckTimer OBJECT-TYPE 1605 SYNTAX Unsigned32 1606 UNITS "second" 1607 MAX-ACCESS read-only 1608 STATUS current 1609 DESCRIPTION 1610 "Represents The number of seconds the AC will wait for 1611 the Data Channel Keep Alive, which is required by the 1612 CAPWAP state machine's Data Check state. 1613 The AC resets the state machine if this timer expires 1614 prior to transitioning to the next state." 1615 REFERENCE 1616 "Section 4.7.4. of CAPWAP Protocol Specification, RFC xxx." 1617 ::= { capwapBaseParameters 2 } 1619 capwapBaseMaxRetransmit OBJECT-TYPE 1620 SYNTAX Unsigned32 1621 MAX-ACCESS read-only 1622 STATUS current 1623 DESCRIPTION 1624 "Represent the maximum number of retransmission for a given 1625 CAPWAP packet before the link layer considers the peer dead." 1626 REFERENCE 1627 "Section 4.8.7. of CAPWAP Protocol Specification, RFC xxx." 1628 ::= { capwapBaseParameters 3 } 1630 capwapBaseRetransmitInterval OBJECT-TYPE 1631 SYNTAX Unsigned32 1632 UNITS "second" 1633 MAX-ACCESS read-write 1634 STATUS current 1635 DESCRIPTION 1636 "Represents the minimum time, in seconds, in which a 1637 non-acknowledged CAPWAP packet will be retransmitted." 1638 REFERENCE 1639 "Section 4.7.12. of CAPWAP Protocol Specification, RFC xxx." 1640 ::= { capwapBaseParameters 4 } 1642 capwapBaseReportInterval OBJECT-TYPE 1643 SYNTAX Unsigned32 1644 UNITS "second" 1645 MAX-ACCESS read-write 1646 STATUS current 1647 DESCRIPTION 1648 "Represents the interval for WTP to send Decryption Error 1649 report." 1650 REFERENCE 1651 "Section 4.7.11. of CAPWAP Protocol Specification, RFC xxx." 1652 ::= { capwapBaseParameters 5 } 1654 capwapBaseEchoInterval OBJECT-TYPE 1655 SYNTAX Unsigned32 1656 UNITS "second" 1657 MAX-ACCESS read-write 1658 STATUS current 1659 DESCRIPTION 1660 "Represents the minimum time, in seconds, between sending Echo 1661 Request messages to the AC with which the WTP has joined." 1662 REFERENCE 1663 "Section 4.7.7. of CAPWAP Protocol Specification, RFC xxx." 1664 ::= { capwapBaseParameters 6 } 1666 capwapBaseIdleTimeout OBJECT-TYPE 1667 SYNTAX Unsigned32 1668 UNITS "second" 1669 MAX-ACCESS read-write 1670 STATUS current 1671 DESCRIPTION 1672 "Represents the idle timeout value that the WTP SHOULD enforce 1673 for its active stations." 1674 REFERENCE 1675 "Section 4.7.8. of CAPWAP Protocol Specification, RFC xxx." 1676 ::= { capwapBaseParameters 7 } 1678 -- End of CAPWAP Base Parameters Group 1680 -- CAPWAP Statistics Group 1682 capwapBaseStats OBJECT IDENTIFIER 1683 ::= { capwapBaseObjects 4 } 1685 capwapBaseFailedDTLSAuthFailCount OBJECT-TYPE 1686 SYNTAX Counter32 1687 MAX-ACCESS read-only 1688 STATUS current 1689 DESCRIPTION 1690 "Represents the number of failed DTLS session 1691 establishment attempts due to authentication failures." 1692 REFERENCE 1693 "Section 4.8.3. of CAPWAP Protocol Specification, RFC xxx." 1694 ::= { capwapBaseStats 1 } 1696 capwapBaseFailedDTLSSessionCount OBJECT-TYPE 1697 SYNTAX Counter32 1698 MAX-ACCESS read-only 1699 STATUS current 1700 DESCRIPTION 1701 "Represents the number of failed DTLS session 1702 establishment attempts." 1703 REFERENCE 1704 "Section 4.8.4. of CAPWAP Protocol Specification, RFC xxx." 1705 ::= { capwapBaseStats 2 } 1707 -- Notifications 1709 capwapBaseChannelUp NOTIFICATION-TYPE 1710 OBJECTS { capwapBaseNtfWtpId, 1711 capwapBaseNtfChannelType, 1712 capwapBaseNtfAuthenMethod } 1713 STATUS current 1714 DESCRIPTION 1715 "This notification is sent by AC when a CAPWAP channel 1716 established. The notification is separated for data or control 1717 channel." 1718 ::= { capwapBaseNotifications 1 } 1720 capwapBaseChannelDown NOTIFICATION-TYPE 1721 OBJECTS { capwapBaseNtfWtpId, 1722 capwapBaseNtfChannelType, 1723 capwapBaseNtfChannelDownReason } 1724 STATUS current 1725 DESCRIPTION 1726 "This notification is sent by AC when CAPWAP channel becomes 1727 down. The notification is separated for data or control 1728 channel." 1729 ::= { capwapBaseNotifications 2 } 1731 capwapBaseDecryptErrorReport NOTIFICATION-TYPE 1732 OBJECTS { capwapBaseNtfWtpId, 1733 capwapBaseNtfRadioId, 1734 capwapBaseNtfStationIdList } 1735 STATUS current 1736 DESCRIPTION 1737 "This notification is generated when a WTP that has occurred 1738 decryption error since the last report." 1739 REFERENCE 1740 "Section 4.6.17. of CAPWAP Protocol Specification, RFC xxx." 1741 ::= { capwapBaseNotifications 3 } 1743 capwapBaseJoinFailure NOTIFICATION-TYPE 1744 OBJECTS { capwapBaseNtfWtpId, capwapBaseNtfJoinFailureReason } 1745 STATUS current 1746 DESCRIPTION 1747 "This notification is generated when a WTP fails to join." 1748 REFERENCE 1749 "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." 1750 ::= { capwapBaseNotifications 4 } 1752 capwapBaseImageUpgradeFailure NOTIFICATION-TYPE 1753 OBJECTS { capwapBaseNtfWtpId, capwapBaseNtfImageFailureReason } 1754 STATUS current 1755 DESCRIPTION 1756 "This notification is generated when a WTP fails to update 1757 firmware image." 1758 REFERENCE 1759 "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." 1760 ::= { capwapBaseNotifications 5 } 1762 capwapBaseConfigMsgError NOTIFICATION-TYPE 1763 OBJECTS { capwapBaseNtfWtpId, capwapBaseNtfConfigMsgErrorType, 1764 capwapBaseNtfMsgErrorElements } 1765 STATUS current 1766 DESCRIPTION 1767 "This notification is generated when a WTP received message 1768 elements in the configuration management messages which it was 1769 unable to apply locally." 1770 REFERENCE 1771 "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." 1772 ::= { capwapBaseNotifications 6 } 1774 capwapBaseRadioOperableStatus NOTIFICATION-TYPE 1775 OBJECTS { capwapBaseNtfWtpId, 1776 capwapBaseNtfRadioId, 1777 capwapBaseNtfRadioOperStatusFlag, 1778 capwapBaseNtfRadioStatusCause } 1779 STATUS current 1780 DESCRIPTION 1781 "The notification is generated when a radio's operational state 1782 is changed." 1783 REFERENCE 1784 "Section 4.6.33. of CAPWAP Protocol Specification, RFC xxx." 1785 ::= { capwapBaseNotifications 7 } 1787 capwapBaseAuthenticationFailure NOTIFICATION-TYPE 1788 OBJECTS { capwapBaseNtfWtpId, 1789 capwapBaseNtfChannelType, 1790 capwapBaseNtfAuthenMethod, 1791 capwapBaseNtfAuthenFailureReason } 1792 STATUS current 1793 DESCRIPTION 1794 "The notification will notify the authentication failure event, 1795 and provides the reason for it." 1796 ::= { capwapBaseNotifications 8 } 1798 -- Objects used only in notifications 1800 -- for notifications 1801 capwapBaseNotifyVarObjects OBJECT IDENTIFIER 1802 ::= { capwapBaseObjects 5 } 1804 capwapBaseNtfWtpId OBJECT-TYPE 1805 SYNTAX CapwapBaseWtpIdTC 1806 MAX-ACCESS accessible-for-notify 1807 STATUS current 1808 DESCRIPTION 1809 "Represents the unique identifier of a WTP." 1810 ::= { capwapBaseNotifyVarObjects 1 } 1812 capwapBaseNtfRadioId OBJECT-TYPE 1813 SYNTAX CapwapBaseRadioIdTC 1814 MAX-ACCESS accessible-for-notify 1815 STATUS current 1816 DESCRIPTION 1817 "Represents the identifier of a PHY radio on a WTP, and only 1818 requires unique on a WTP. 1819 For example, WTP A and WTP B will use same value of 1820 capwapBaseNtfRadioId for their first radio." 1821 REFERENCE 1822 "Section 4.3. of CAPWAP Protocol Specification, RFC xxx." 1823 ::= { capwapBaseNotifyVarObjects 2 } 1825 capwapBaseNtfChannelType OBJECT-TYPE 1826 SYNTAX CapwapBaseChannelTypeTC 1827 MAX-ACCESS accessible-for-notify 1828 STATUS current 1829 DESCRIPTION 1830 "Represents the channel type for CAPWAP protocol." 1831 ::= { capwapBaseNotifyVarObjects 3 } 1833 capwapBaseNtfAuthenMethod OBJECT-TYPE 1834 SYNTAX CapwapBaseAuthenMethodTC 1835 MAX-ACCESS accessible-for-notify 1836 STATUS current 1837 DESCRIPTION 1838 "Represents authentication method for Channel." 1839 ::= { capwapBaseNotifyVarObjects 4 } 1841 capwapBaseNtfChannelDownReason OBJECT-TYPE 1842 SYNTAX INTEGER { timeout(1), 1843 rekeyfailure(2), 1844 acRebootWtp(3), 1845 dtlsError(4), 1846 maxRetransmit(5) } 1847 MAX-ACCESS accessible-for-notify 1848 STATUS current 1849 DESCRIPTION 1850 "Represents the reason for Channel down. 1851 The following enumerated values are supported: 1852 timeout(1) - The keep alive is timeout, 1853 rekeyfailure(2) - Rekey process is failed, channel will be 1854 broken. 1855 acRebootWtp(3) - AC reboot WTP. 1856 dtlsError(4) - DTLS notifications: DTLSAborted, 1857 DTLSReassemblyFailure, DTLSPeerDisconnect, 1858 or frequent DTLSDecapFailure. 1859 maxRetransmit(5) - The underlying reliable transport's 1860 RetransmitCount counter has reached the 1861 MaxRetransmit variable" 1862 ::= { capwapBaseNotifyVarObjects 5 } 1864 capwapBaseNtfStationIdList OBJECT-TYPE 1865 SYNTAX OCTET STRING 1866 MAX-ACCESS accessible-for-notify 1867 STATUS current 1868 DESCRIPTION 1869 "Represents the list of station id which use semicolons to 1870 separate each station id." 1871 REFERENCE 1872 "Section 4.6.8. of CAPWAP Protocol Specification, RFC xxx." 1873 ::= { capwapBaseNotifyVarObjects 6 } 1875 capwapBaseNtfAuthenFailureReason OBJECT-TYPE 1876 SYNTAX INTEGER { 1877 keyMismatch(1), invalidCA(2), micError(3), 1878 timeout(4), unknown(8) 1879 } 1880 MAX-ACCESS accessible-for-notify 1881 STATUS current 1882 DESCRIPTION 1883 "Represents reason for WTP authorization failure. 1884 The following enumerated values are supported: 1885 keyMismatch(1) - WTP's and AC's key is not matched, 1886 invalidCA(2) - ca is not valid, 1887 micError(3) - detect MIC error, 1888 timeout(4) - WaitDTLS Timer is timeout, 1889 unknown(8) - Unknown reason." 1890 REFERENCE 1891 "Section 2.3.1. of CAPWAP Protocol Specification, RFC xxx." 1892 ::= { capwapBaseNotifyVarObjects 7 } 1894 capwapBaseNtfRadioOperStatusFlag OBJECT-TYPE 1895 SYNTAX INTEGER { reserved(0), operable(1), inoperable(2) } 1896 MAX-ACCESS accessible-for-notify 1897 STATUS current 1898 DESCRIPTION 1899 "Represents the operation status of a radio. 1900 The following enumerated values are supported: 1901 reserved(0) - Reserved 1902 operable(1) - To indicate radio is operable, 1903 inoperable(2) - To indicate radio is inoperable, and 1904 capwapBaseNtfRadioStatusCause object will 1905 give reason in details." 1906 REFERENCE 1907 "Section 4.6.33. of CAPWAP Protocol Specification, RFC xxx." 1908 ::= { capwapBaseNotifyVarObjects 8 } 1910 capwapBaseNtfRadioStatusCause OBJECT-TYPE 1911 SYNTAX INTEGER { 1912 normal(0), hwError(1), swError(2), adminSet(3) 1913 } 1914 MAX-ACCESS accessible-for-notify 1915 STATUS current 1916 DESCRIPTION 1917 "Represents the reason the radio is out of service. 1918 The following enumerated values are supported: 1919 normal(0) - Normal Status, 1920 hwError(1) - Radio Failure, 1921 swError(2) - Software Failure, 1922 adminSet(3) - Administratively Set." 1923 REFERENCE 1924 "Section 4.6.33. of CAPWAP Protocol Specification, RFC xxx." 1925 ::= { capwapBaseNotifyVarObjects 9 } 1927 capwapBaseNtfJoinFailureReason OBJECT-TYPE 1928 SYNTAX INTEGER { 1929 unspecified(1), resDepletion(2), unknownSource(3), 1930 incorrectData(4), sessionIdInUse(5), notSupportHw(6), 1931 notSupportBinding(7) 1932 } 1933 MAX-ACCESS accessible-for-notify 1934 STATUS current 1935 DESCRIPTION 1936 "Represents the reason of join failure. 1937 The following enumerated values are supported: 1938 unspecified(1) - unspecified failure reason, 1939 resDepletion(2) - Resource Depletion, 1940 unknownSource(3) - Unknown Source, 1941 incorrectData(4) - Incorrect Data, 1942 sessionIdInUse(5) - Session ID already in use, 1943 notSupportHw(6) - WTP Hardware not supported, 1944 notSupportBinding(7) - Binding Not Supported." 1945 REFERENCE 1946 "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." 1947 ::= { capwapBaseNotifyVarObjects 10 } 1949 capwapBaseNtfImageFailureReason OBJECT-TYPE 1950 SYNTAX INTEGER { 1951 invalidChecksum(1), 1952 invalidLength(2), 1953 other(3), 1954 inStorage(4) 1955 } 1956 MAX-ACCESS accessible-for-notify 1957 STATUS current 1958 DESCRIPTION 1959 "Represents the reason of image failure. 1960 The following enumerated values are supported: 1961 invalidChecksum(1) - Invalid Checksum, 1962 invalidLength(2) - Invalid Data Length, 1963 other(3) - Other Error, 1964 inStorage(4) - Image Already Present." 1965 REFERENCE 1966 "Section 4.6.34. of CAPWAP Protocol Specification, RFC xxx." 1967 ::= { capwapBaseNotifyVarObjects 11 } 1969 capwapBaseNtfConfigMsgErrorType OBJECT-TYPE 1970 SYNTAX INTEGER { 1971 unknownElement(1), unsupportedElement(2), 1972 unknownValue(3), unsupportedValue(4) 1973 } 1974 MAX-ACCESS accessible-for-notify 1975 STATUS current 1976 DESCRIPTION 1977 "Represents the type of configuration message error. 1978 The following enumerated values are supported: 1979 unknownElement(1) - Unknown Message Element, 1980 unsupportedElement(2) - Unsupported Message Element, 1981 unknownValue(3) - Unknown Message Element Value, 1982 unsupportedValue(4) - Unsupported Message Element Value." 1983 REFERENCE 1984 "Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx." 1985 ::= { capwapBaseNotifyVarObjects 12 } 1987 capwapBaseNtfMsgErrorElements OBJECT-TYPE 1988 SYNTAX SnmpAdminString 1989 MAX-ACCESS accessible-for-notify 1990 STATUS current 1991 DESCRIPTION 1992 "Represents the message elements sent by the AC in the 1993 Configuration Status Response message that caused the error." 1994 REFERENCE 1995 "Section 4.6.35. of CAPWAP Protocol Specification, RFC xxx." 1996 ::= { capwapBaseNotifyVarObjects 13 } 1998 -- Module compliance 2000 capwapBaseCompliances OBJECT IDENTIFIER 2001 ::= { capwapBaseConformance 1 } 2003 capwapBaseGroups OBJECT IDENTIFIER 2004 ::= { capwapBaseConformance 2 } 2006 capwapBaseCompliance MODULE-COMPLIANCE 2007 STATUS current 2008 DESCRIPTION 2009 "Describes the requirements for conformance to the 2010 CAPWAP-BASE-MIB." 2012 MODULE -- this module 2013 MANDATORY-GROUPS { capwapBaseAcNodeGroup, 2014 capwapBaseWtpStateGroup, 2015 capwapBaseWtpsGroup, 2016 capwapBaseRadiosGroup, 2017 capwapBaseStationsGroup 2018 } 2020 GROUP capwapBaseAcNodeGroup2 2021 DESCRIPTION 2022 "The capwapBaseAcNodeGroup2 group is optional." 2024 GROUP capwapBaseAcNameListGroup 2025 DESCRIPTION 2026 "The capwapBaseAcNameListGroup group is optional." 2028 GROUP capwapBaseWtpsGroup2 2029 DESCRIPTION 2030 "The capwapBaseWtpsGroup2 group is optional." 2032 GROUP capwapBaseWtpRebootStatsGroup 2033 DESCRIPTION 2034 "The capwapBaseWtpRebootStatsGroup group is optional." 2036 GROUP capwapBaseRadioStatsGroup 2037 DESCRIPTION 2038 "The capwapBaseRadioStatsGroup group is optional." 2040 GROUP capwapBaseParametersGroup 2041 DESCRIPTION 2042 "The capwapBaseParametersGroup group is optional." 2044 GROUP capwapBaseStatsGroup 2045 DESCRIPTION 2046 "The capwapBaseStatsGroup group is optional." 2048 GROUP capwapBaseNotificationGroup 2049 DESCRIPTION 2050 "The group capwapBaseNotificationGroup is optional." 2052 GROUP capwapBaseNotifyVarGroup 2053 DESCRIPTION 2054 "The capwapBaseNotifyVarGroup group is optional. 2055 If capwapBaseNotificationGroup is supported, 2056 this group must be implemented." 2058 OBJECT capwapBaseRadioWirelessBinding 2059 SYNTAX INTEGER { reserved0(0), reserved2(2) } 2060 DESCRIPTION 2061 "A value other than reserved0(0), reserved2(2) need not be 2062 supported if there is no wireless binding defined for 2063 technologies used." 2064 ::= { capwapBaseCompliances 1 } 2066 capwapBaseAcNodeGroup OBJECT-GROUP 2067 OBJECTS { 2068 capwapBaseWtpSessions, 2069 capwapBaseWtpSessionsLimit, 2070 capwapBaseStationSessions, 2071 capwapBaseStationSessionsLimit 2072 } 2073 STATUS current 2074 DESCRIPTION 2075 "The collection of objects which are used to represent 2076 basic properties for AC from CAPWAP protocol perspective." 2077 ::= { capwapBaseGroups 1 } 2079 capwapBaseAcNodeGroup2 OBJECT-GROUP 2080 OBJECTS { 2081 capwapBaseDataChannelSecOptions, 2082 capwapBaseWtpAuthenOptions, 2083 capwapBaseWtpFallbackEnable 2084 } 2085 STATUS current 2086 DESCRIPTION 2087 "The collection of objects which are used to represent 2088 other properties such as security for AC from 2089 CAPWAP protocol perspective." 2090 ::= { capwapBaseGroups 2 } 2092 capwapBaseAcNameListGroup OBJECT-GROUP 2093 OBJECTS { 2094 capwapBaseAcNameListName, 2095 capwapBaseAcNameListPriority 2096 } 2097 STATUS current 2098 DESCRIPTION 2099 "The collection of objects which are used to represent 2100 AC name list." 2101 ::= { capwapBaseGroups 3 } 2103 capwapBaseWtpStateGroup OBJECT-GROUP 2104 OBJECTS { 2105 capwapBaseWtpIpAddressType, 2106 capwapBaseWtpIpAddress, 2107 capwapBaseWtpPhyAddress, 2108 capwapBaseWtpState 2109 } 2110 STATUS current 2111 DESCRIPTION 2112 "The collection of objects which are used to represent 2113 WTP state information." 2114 ::= { capwapBaseGroups 4 } 2116 capwapBaseWtpsGroup OBJECT-GROUP 2117 OBJECTS { 2118 capwapBaseWtpName, 2119 capwapBaseWtpLocation, 2120 capwapBaseWtpBaseMacAddress, 2121 capwapBaseTunnelModeOptions, 2122 capwapBaseMacTypeOptions, 2123 capwapBaseWtpRadiosInUseNum, 2124 capwapBaseWtpRadioNumLimit 2125 } 2126 STATUS current 2127 DESCRIPTION 2128 "The collection of objects which are used to represent 2129 configuration and properties information for WTP 2130 in running state." 2131 ::= { capwapBaseGroups 5 } 2133 capwapBaseWtpsGroup2 OBJECT-GROUP 2134 OBJECTS { 2135 capwapBaseWtpPhyIndex, 2136 capwapBaseWtpDiscoveryType, 2137 capwapBaseWtpStaticIpEnable, 2138 capwapBaseWtpStaticIpType, 2139 capwapBaseWtpStaticIp, 2140 capwapBaseWtpNetmask, 2141 capwapBaseWtpGateway 2142 } 2143 STATUS current 2144 DESCRIPTION 2145 "The collection of objects which are used to represent 2146 configuration and properties information for WTP 2147 in running state." 2148 ::= { capwapBaseGroups 6 } 2150 capwapBaseRadiosGroup OBJECT-GROUP 2151 OBJECTS { 2152 capwapBaseVirtualRadioIfIndex, 2153 capwapBaseRadioWirelessBinding 2154 } 2155 STATUS current 2156 DESCRIPTION 2157 "The collection of objects which are used to represent 2158 wireless binding type, the mapping relationship between 2159 'WLAN Virtual Radio Interface' and PHY radio." 2160 ::= { capwapBaseGroups 7 } 2162 capwapBaseStationsGroup OBJECT-GROUP 2163 OBJECTS { 2164 capwapBaseStationAddedTime, 2165 capwapBaseStationVlanName 2166 } 2167 STATUS current 2168 DESCRIPTION 2169 "The collection of objects which are used to represent 2170 stations' basic property." 2171 ::= { capwapBaseGroups 8 } 2173 capwapBaseWtpRebootStatsGroup OBJECT-GROUP 2174 OBJECTS { 2175 capwapBaseWtpRebootCount, 2176 capwapBaseWtpInitCount, 2177 capwapBaseWtpLinkFailureCount, 2178 capwapBaseWtpSwFailureCount, 2179 capwapBaseWtpHwFailureCount, 2180 capwapBaseWtpOtherFailureCount, 2181 capwapBaseWtpUnknownFailureCount, 2182 capwapBaseWtpLastFailureType 2183 } 2184 STATUS current 2185 DESCRIPTION 2186 "The collection of objects which are used for collecting 2187 WTP reboot count, link failure count, hardware failure 2188 count and so on." 2189 ::= { capwapBaseGroups 9 } 2191 capwapBaseRadioStatsGroup OBJECT-GROUP 2192 OBJECTS { 2193 capwapBaseRadioResetCount, 2194 capwapBaseRadioSwFailCount, 2195 capwapBaseRadioHwFailCount, 2196 capwapBaseRadioOtherFailCount, 2197 capwapBaseRadioUnknownFailCount, 2198 capwapBaseRadioConfigUpdateCount, 2199 capwapBaseRadioChannelChangeCount, 2200 capwapBaseRadioBandChangeCount, 2201 capwapBaseRadioCurrentNoiseFloor, 2202 capwapBaseRadioDecryptErrorCount, 2203 capwapBaseRadioLastFailType 2204 } 2205 STATUS current 2206 DESCRIPTION 2207 "The collection of objects which are used for collecting 2208 radio reset count, channel change count, hardware failure 2209 count and so on" 2210 ::= { capwapBaseGroups 10 } 2212 capwapBaseParametersGroup OBJECT-GROUP 2213 OBJECTS { 2214 capwapBaseDataChannelDeadInterval, 2215 capwapBaseDataCheckTimer, 2216 capwapBaseRetransmitInterval, 2217 capwapBaseMaxRetransmit, 2218 capwapBaseEchoInterval, 2219 capwapBaseIdleTimeout, 2220 capwapBaseReportInterval 2221 } 2222 STATUS current 2223 DESCRIPTION 2224 "Objects used for CAPWAP protocol." 2225 ::= { capwapBaseGroups 11 } 2227 capwapBaseStatsGroup OBJECT-GROUP 2228 OBJECTS { 2229 capwapBaseWtpRetransmitCount, 2230 capwapBaseFailedDTLSAuthFailCount, 2231 capwapBaseFailedDTLSSessionCount 2232 } 2233 STATUS current 2234 DESCRIPTION 2235 "Objects used for CAPWAP protocol." 2236 ::= { capwapBaseGroups 12 } 2238 capwapBaseNotificationGroup NOTIFICATION-GROUP 2239 NOTIFICATIONS { 2240 capwapBaseChannelUp, 2241 capwapBaseChannelDown, 2242 capwapBaseDecryptErrorReport, 2243 capwapBaseJoinFailure, 2244 capwapBaseImageUpgradeFailure, 2245 capwapBaseConfigMsgError, 2246 capwapBaseRadioOperableStatus, 2247 capwapBaseAuthenticationFailure 2248 } 2249 STATUS current 2250 DESCRIPTION 2251 "Collection of notifications in this MIB." 2252 ::= { capwapBaseGroups 13 } 2254 capwapBaseNotifyVarGroup OBJECT-GROUP 2255 OBJECTS { 2256 capwapBaseNtfWtpId, 2257 capwapBaseNtfRadioId, 2258 capwapBaseNtfChannelType, 2259 capwapBaseNtfAuthenMethod, 2260 capwapBaseNtfChannelDownReason, 2261 capwapBaseNtfStationIdList, 2262 capwapBaseNtfAuthenFailureReason, 2263 capwapBaseNtfRadioOperStatusFlag, 2264 capwapBaseNtfRadioStatusCause, 2265 capwapBaseNtfJoinFailureReason, 2266 capwapBaseNtfImageFailureReason, 2267 capwapBaseNtfConfigMsgErrorType, 2268 capwapBaseNtfMsgErrorElements 2269 } 2270 STATUS current 2271 DESCRIPTION 2272 "Objects used for notification." 2273 ::= { capwapBaseGroups 14 } 2275 END 2276 10. Security Considerations 2278 There are a number of management objects defined in this MIB module 2279 with a MAX-ACCESS clause of read-write and/or read-create. Such 2280 objects may be considered sensitive or vulnerable in some network 2281 environments. The support for SET operations in a non-secure 2282 environment without proper protection can have a negative effect on 2283 network operations. The followings are the tables and objects and 2284 their sensitivity/vulnerability: 2286 o - Unauthorized changes to the capwapBaseWtpTable, writable objects 2287 under capwapBaseAcs group may disrupt allocation of resources in 2288 the network. 2290 Some of the readable objects in this MIB module (i.e., objects with a 2291 MAX-ACCESS other than not-accessible) may be considered sensitive or 2292 vulnerable in some network environments. It is thus important to 2293 control even GET and/or NOTIFY access to these objects and possibly 2294 to even encrypt the values of these objects when sending them over 2295 the network via SNMP. The followings are the tables and objects and 2296 their sensitivity/vulnerability: 2298 o - The capwapBaseWtpTable exposes WTP's important information like 2299 IP address, MAC type and so on; 2301 o - The capwapBaseWtpRebootStatTable exposes WTP's failure 2302 information; 2304 o - The capwapBaseRadioStatsTable exposes radio's failure 2305 information; 2307 SNMP versions prior to SNMPv3 did not include adequate security. 2308 Even if the network itself is secure (for example by using IPSec), 2309 even then, there is no control as to who on the secure network is 2310 allowed to access and GET/SET (read/change/create/delete) the objects 2311 in this MIB module. 2313 It is RECOMMENDED that implementers consider the security features as 2314 provided by the SNMPv3 framework (see [RFC3410], section 8), 2315 including full support for the SNMPv3 cryptographic mechanisms (for 2316 authentication and privacy). 2318 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2319 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2320 enable cryptographic security. It is then a customer/operator 2321 responsibility to ensure that the SNMP entity giving access to an 2322 instance of this MIB module is properly configured to give access to 2323 the objects only to those principals (users) that have legitimate 2324 rights to indeed GET or SET (change/create/delete) them. 2326 11. IANA Considerations 2328 11.1. IANA Considerations for CAPWAP-BASE-MIB 2330 The MIB module in this document uses the following IANA-assigned 2331 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 2333 Descriptor OBJECT IDENTIFIER value 2334 ---------- ----------------------- 2336 capwapBaseMIB { mib-2 XXX } 2338 11.2. IANA Considerations for ifType 2340 Require IANA to assign a ifType for 'WTP Virtual Radio Interface' 2341 type. 2343 12. Contributors 2345 This MIB is based on contributions from Long Gao. 2347 13. Acknowledgements 2349 The authors wish to thank David Harrington, Yu Liu, Xi Yao, Sachin 2350 Dutta, Ju Wang, Yujin Zhao, Haitao Zhang. 2352 14. References 2354 14.1. Normative References 2356 [RFC2119] Bradner, S., "Key words for 2357 use in RFCs to Indicate 2358 Requirement Levels", 2359 BCP 14, RFC 2119, 2360 March 1997. 2362 [RFC2578] McCloghrie, K., Ed., 2363 Perkins, D., Ed., and J. 2364 Schoenwaelder, Ed., 2365 "Structure of Management 2366 Information Version 2 2367 (SMIv2)", STD 58, RFC 2578, 2368 April 1999. 2370 [RFC2579] McCloghrie, K., Ed., 2371 Perkins, D., Ed., and J. 2373 Schoenwaelder, Ed., 2374 "Textual Conventions for 2375 SMIv2", STD 58, RFC 2579, 2376 April 1999. 2378 [RFC2580] McCloghrie, K., Perkins, 2379 D., and J. Schoenwaelder, 2380 "Conformance Statements for 2381 SMIv2", STD 58, RFC 2580, 2382 April 1999. 2384 [RFC2863] McCloghrie, K. and F. 2385 Kastenholz, "The Interfaces 2386 Group MIB", RFC 2863, 2387 June 2000. 2389 [RFC3418] Presuhn, R., "Management 2390 Information Base (MIB) for 2391 the Simple Network 2392 Management Protocol 2393 (SNMP)", STD 62, RFC 3418, 2394 December 2002. 2396 [RFC4001] Daniele, M., Haberman, B., 2397 Routhier, S., and J. 2398 Schoenwaelder, "Textual 2399 Conventions for Internet 2400 Network Addresses", 2401 RFC 4001, February 2005. 2403 [RFC4133] Bierman, A. and K. 2404 McCloghrie, "Entity MIB 2405 (Version 3)", RFC 4133, 2406 August 2005. 2408 [I-D.ietf-capwap-protocol-specification] Montemurro, M., Stanley, 2409 D., and P. Calhoun, "CAPWAP 2410 Protocol Specification", dr 2411 aft-ietf-capwap-protocol- 2412 specification-13 (work in 2413 progress), September 2008. 2415 14.2. Informative References 2417 [RFC3410] Case, J., Mundy, R., 2418 Partain, D., and B. 2419 Stewart, "Introduction and 2420 Applicability Statements 2421 for Internet-Standard 2422 Management Framework", 2423 RFC 3410, December 2002. 2425 Authors' Addresses 2427 Yang Shi (editor) 2428 H3C Tech. Co., Ltd 2429 Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian District, 2430 Beijing 2431 China(100085) 2433 Phone: +86 010 82775276 2434 EMail: young@h3c.com 2436 David Perkins (editor) 2437 SNMPinfo 2438 288 Quailbrook Ct San Carlos, 2439 CA 94070 2440 USA 2442 Phone: +1 408 394-8702 2443 EMail: dperkins@snmpinfo.com 2445 Chris Elliott (editor) 2446 Cisco Systems, Inc. 2447 7025 Kit Creek Rd., P.O. Box 14987 Research Triangle Park 2448 27709 2449 USA 2451 Phone: +1 919-392-2146 2452 EMail: chelliot@cisco.com 2454 Yong Zhang (editor) 2455 Fortinet, Inc. 2456 1090 Kifer Road 2457 Sunnyvale, CA 94086 2458 USA 2460 EMail: yzhang@fortinet.com 2462 Full Copyright Statement 2464 Copyright (C) The IETF Trust (2008). 2466 This document is subject to the rights, licenses and restrictions 2467 contained in BCP 78, and except as set forth therein, the authors 2468 retain all their rights. 2470 This document and the information contained herein are provided on an 2471 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2472 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 2473 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 2474 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 2475 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2476 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2478 Intellectual Property 2480 The IETF takes no position regarding the validity or scope of any 2481 Intellectual Property Rights or other rights that might be claimed to 2482 pertain to the implementation or use of the technology described in 2483 this document or the extent to which any license under such rights 2484 might or might not be available; nor does it represent that it has 2485 made any independent effort to identify any such rights. Information 2486 on the procedures with respect to rights in RFC documents can be 2487 found in BCP 78 and BCP 79. 2489 Copies of IPR disclosures made to the IETF Secretariat and any 2490 assurances of licenses to be made available, or the result of an 2491 attempt made to obtain a general license or permission for the use of 2492 such proprietary rights by implementers or users of this 2493 specification can be obtained from the IETF on-line IPR repository at 2494 http://www.ietf.org/ipr. 2496 The IETF invites any interested party to bring to its attention any 2497 copyrights, patents or patent applications, or other proprietary 2498 rights that may cover technology that may be required to implement 2499 this standard. Please address the information to the IETF at 2500 ietf-ipr@ietf.org.