1-- ******************************************************************* 2-- CISCO-LWAPP-DOT11-CLIENT-CCX-TC-MIB.my 3-- Sheeba Kamra Jan 2007 4-- 5-- Copyright (c) 2006-2007 by Cisco Systems, Inc. 6-- 7 8-- All rights reserved. 9-- ***************************************************************** 10 11CISCO-LWAPP-DOT11-CLIENT-CCX-TC-MIB DEFINITIONS ::= BEGIN 12 13IMPORTS 14 MODULE-IDENTITY 15 FROM SNMPv2-SMI 16 TEXTUAL-CONVENTION 17 FROM SNMPv2-TC 18 ciscoMgmt 19 FROM CISCO-SMI; 20 21-- ******************************************************************** 22-- * MODULE IDENTITY 23-- ******************************************************************** 24 25ciscoLwappDot11ClientCCXTextualConventions MODULE-IDENTITY 26 LAST-UPDATED "200703220000Z" 27 ORGANIZATION "Cisco Systems Inc." 28 CONTACT-INFO 29 "Cisco Systems, 30 Customer Service 31 32 Postal: 170 West Tasman Drive 33 San Jose, CA 95134 34 USA 35 36 Tel: +1 800 553-NETS 37 38 Email: cs-wnbu-snmp@cisco.com" 39 DESCRIPTION 40 "This module defines the textual conventions used 41 throughout the Cisco enterprise MIBs designed for 42 implementation on Central Controllers (CC) that 43 terminate the Light Weight Access Point Protocol 44 tunnel from Light-weight LWAPP Access Points, 45 specifically for the functions of the Cisco Client 46 Extensions (CCX) program. 47 48 This MIB provides textual conventions used in the 49 configuration and status information mibs 50 about the CCX clients that the controller is aware of. 51 52 53 GLOSSARY 54 55 Light Weight Access Point Protocol ( LWAPP ) 56 57 This is a generic protocol that defines the 58 communication between the Access Points and the 59 Central Controller. 60 61 Mobile Node ( MN ) 62 63 A roaming 802.11 wireless device in a wireless 64 network associated with an access point. Mobile Node, 65 Mobile Station(Ms) and client are used 66 interchangeably. 67 68 Cisco Client eXtentions (CCX) 69 The Cisco Client Extensions (CCX) Program is a 70 program of working through silicon providers to 71 embed Cisco client technology in wireless client 72 reference designs, and to promote compliant and 73 interoperable third-party clients with Cisco's 74 infrastructure, thus further driving wireless adoption 75 in the market. 76 77 Extensible Authentication Protocol (EAP) 78 79 The Extensible Authentication Protocol (EAP) is an 80 Internet Engineering Task Force (IETF) standard that 81 provides an infrastructure for network access clients and 82 authentication servers to host plug-in modules for current 83 and future authentication methods and technologies. 84 85 Wired Equivalent Privacy (WEP) 86 87 A security method defined by 802.11. WEP uses a 88 symmetric key stream cipher called RC4 to encrypt the data 89 packets. 90 91 92 93 REFERENCE 94 95 [1] Part 11 Wireless LAN Medium Access Control ( MAC ) 96 and Physical Layer ( PHY ) Specifications. 97 98 [2] Draft-obara-capwap-lwapp-00.txt, IETF Light 99 Weight Access Point Protocol. 100 101 [3] Cisco Compatible Extensions for WLAN Devices 102 Version 5.0.11" 103 REVISION "200703220000Z" 104 DESCRIPTION 105 "Added 2 more radio types to CiscoLwappDot11ClientRadioType." 106 REVISION "200702220000Z" 107 DESCRIPTION 108 "Reverted some of the enum names to be in line with the CCXV5 109 spec." 110 REVISION "200702190000Z" 111 DESCRIPTION 112 "Incorporated review comments." 113 REVISION "200701300000Z" 114 DESCRIPTION 115 "Initial version of this mib module." 116 ::= { ciscoMgmt 611 } 117 118 119 120CiscoLwappDot11ClientReqStatus ::= TEXTUAL-CONVENTION 121 STATUS current 122 DESCRIPTION 123 "This field indicates the status of current request.The values 124 used can be one of the following: 125 126 initiate - this will be used to trigger a request to get 127 some parameters from a CCX client. 128 129 inProgress - this indicates that the request to get the 130 details from the client is still in progress. 131 132 success - indicates that the query was executed 133 successfully. 134 135 failed - this indicates that the request to get some 136 parameters from a CCX client failed. 137 138 requestNotProcessedByClient - indicates that the CCX client 139 did not honour this request." 140 SYNTAX INTEGER { 141 initiate(1), 142 inProgress(2), 143 success(3), 144 failure(4), 145 requestNotProcessedByClient(5) 146 } 147 148CiscoLwappDot11ClientSSId ::= TEXTUAL-CONVENTION 149 STATUS current 150 DESCRIPTION 151 "This represents the Service Set Identifier assigned 152 to WLAN." 153 SYNTAX OCTET STRING (SIZE (1..32)) 154 155CiscoLwappDot11ClientAuthMethod ::= TEXTUAL-CONVENTION 156 STATUS current 157 DESCRIPTION 158 "This is the authentication method used by the client. 159 The possible values are: 160 none - this indicates that no authentication method is 161 used 162 163 preSharedKey - this refers to the method of using pre 164 shared key for authentication 165 166 eap - this is Extensible Authentication Protocol 167 168 unknown - this indicates an authentication protocol other 169 than the ones defined above" 170 SYNTAX INTEGER { 171 none(0), 172 preSharedKey(1), 173 eap(2), 174 unknown(255) 175 } 176 177CiscoLwappDot11ClientEAPMethod ::= TEXTUAL-CONVENTION 178 STATUS current 179 DESCRIPTION 180 "This identifies the Extensible Authentication Protocol(EAP) 181 method used. The possible values are: 182 183 leap - this is Lightweight Extensible Authentication 184 Protocol 185 186 eapFast - this is Extensible Authentication 187 Protocol with Flexible Authentication via Secure Tunneling 188 189 eapTls - this is Extensible Authentication 190 Protocol with Transport Layer Security 191 192 eapTtls - this is Extensible Authentication Protocol with 193 Tunneled Transport Layer Security 194 195 peap0EapMschap2 - this refers to Protected Extensible 196 Authentication Protocol Version 0 with Microsoft 197 Challenge Handshake Authentication Protocol version 2 198 199 peap1EapGtc - this refers to Protected Extensible 200 Authentication Protocol Version 1 with Generic Token Card 201 202 eapMd5 - this is Extensible Authentication Protocol with 203 Message-Digest algorithm 5 204 205 eapSim - this is Extensible Authentication Protocol using 206 the Global System for Mobile Communications (GSM) 207 Subscriber Identity Module (SIM) 208 209 preSharedKey - this refers to the method of using pre 210 shared key for authentication 211 212 unknown - this indicates an EAP method other 213 than the ones defined above" 214 SYNTAX INTEGER { 215 leap(0), 216 eapFast(1), 217 eapTls(2), 218 eapTtls(3), 219 peap0EapMschap2(4), 220 peap1EapGtc(5), 221 eapMd5(6), 222 eapSim(7), 223 preSharedKey(8), 224 unknown(255) 225 } 226 227CiscoLwappDot11ClientKeyMgmtMethod ::= TEXTUAL-CONVENTION 228 STATUS current 229 DESCRIPTION 230 "This is the key management method used by the client. 231 The possible values are: 232 233 staticWep - this is Wired Equivalent Privacy with a static 234 key defined 235 236 dynamicWep - this is Wired Equivalent Privacy with a 237 dynamic key 238 239 wpa - this indicates wifi protected access 240 241 wpaCckm - this is wifi protected access with 242 Cisco Centralized Key Management 243 244 wpa2 - this indicates version 2 of wifi protected access 245 246 wpa2Cckm - this is wifi protected access 247 version 2 with Cisco Centralized Key Management 248 249 cckm - this indicates Cisco Centralized Key 250 Management 251 252 unknown - this indicates a key management method other 253 than the ones defined above" 254 SYNTAX INTEGER { 255 none(0), 256 staticWep(1), 257 dynamicWep(2), 258 wpa(3), 259 wpaCckm(4), 260 wpa2(5), 261 wpa2Cckm(6), 262 cckm(7), 263 unknown(255) 264 } 265 266CiscoLwappDot11ClientEncryptionMethod ::= TEXTUAL-CONVENTION 267 STATUS current 268 DESCRIPTION 269 "This is the encryption method used by the client. 270 The possible values are: 271 272 none - no encryption is used 273 274 wep40 - this is Wired Equivalent Privacy with a 40 bit 275 secret key 276 277 wep104 - this is Wired Equivalent Privacy with a 104 bit 278 secret key 279 280 tkip - this indicates Temporal Key Integrity 281 Protocol 282 283 ckip - this is Cisco Key Integrity Protocol 284 285 aesCcmp - this is Advanced Encryption Standard 286 - Counter Mode Cipher Block Chaining-Message Authentication 287 Code Protocol 288 289 unknown - this indicates an encryption method other 290 than the ones defined above" 291 SYNTAX INTEGER { 292 none(0), 293 wep40(1), 294 wep104(2), 295 tkip(3), 296 ckip(4), 297 aesCcmp(5), 298 unknown(255) 299 } 300 301CiscoLwappDot11ClientCredentialType ::= TEXTUAL-CONVENTION 302 STATUS current 303 DESCRIPTION 304 "This indicates how the 802.11 credentials are configured for 305 the client. 306 The possible values are: 307 308 localSaved - credentials are locally saved 309 310 manuallyPrompted - client is prompted for the credentials 311 312 hostOsLogin - this means the host operating system's login 313 credentials will be used 314 315 unknown - this indicates a credential method other 316 than the ones defined above" 317 SYNTAX INTEGER { 318 localSaved(0), 319 manuallyPrompted(1), 320 hostOsLogin(2), 321 unknown(255) 322 } 323 324CiscoLwappDot11ClientPowerSaveMode ::= TEXTUAL-CONVENTION 325 STATUS current 326 DESCRIPTION 327 "This is the type of power save mode configured on the 328 client. The possible values are: 329 330 awake - this indicates that the client is constantly awake 331 332 normal - this indicates normal power save mode 333 334 maxPower - this indicates maximum power save mode 335 336 uApsd - this indicates Unsolicited Automatic 337 Power Save Delivery 338 339 sApsd - this indicates Solicited Automatic Power 340 Save Delivery 341 342 unknown - this indicates a power save mode other 343 than the ones defined above" 344 SYNTAX INTEGER { 345 awake(0), 346 normal(1), 347 maxPower(2), 348 uApsd(3), 349 sApsd(4), 350 unknown(255) 351 } 352 353CiscoLwappDot11ClientTxPowerMode ::= TEXTUAL-CONVENTION 354 STATUS current 355 DESCRIPTION 356 "This field identifies the transmit power mode of the 357 client. The possible values are: 358 359 fixed - this indicates that the client is operating at a 360 fixed power mode 361 362 automatic - this indicates that the client power will be 363 determined automatically" 364 SYNTAX INTEGER { 365 fixed(0), 366 automatic(1) 367 } 368 369CiscoLwappDot11ClientRadioType ::= TEXTUAL-CONVENTION 370 STATUS current 371 DESCRIPTION 372 "This is the radio type of the client. The possible values 373 are: 374 unused - this is currently a reserved radio type and is 375 not used 376 377 fhss - this is Frequency-hopping spread spectrum based 378 radio 379 380 dsss - this is Direct Sequence spread spectrum based 381 radio 382 383 infraRedBaseband - this is infrared baseband based radio 384 385 oFdm - this is orthogonal frequency division 386 multiplexing based radio 387 388 highRateDsss - this is high rate direct sequence spread 389 spectrum based radio 390 391 erp - this indicates effective radiated power based radio 392 393 draft11n2point4Ghz - this indicates a 2.4 Ghz band radio 394 as defined in draft 802.11n 395 396 draft11n5Ghz - this indicates a 5 Ghz band radio 397 as defined in draft 802.11n" 398 SYNTAX INTEGER { 399 unused(0), 400 fhss(1), 401 dsss(2), 402 irBaseband(3), 403 oFdm(4), 404 highRateDsss(5), 405 erp(6), 406 draft11n2point4Ghz(7), 407 draft11n5Ghz(8) 408 } 409 410CiscoLwappDot11ClientDataRates ::= TEXTUAL-CONVENTION 411 STATUS current 412 DESCRIPTION 413 "This field indicates the data rates supported by a 414 client. If a data rate is supported by a client, the 415 corresponding bit is set to 1 else it is 416 set to 0. The different data rates (in Mhz) are 1, 2, 417 5.5, 6, 9, 11, 12, 18, 24, 36, 48, 54." 418 SYNTAX BITS { 419 mhz1(0), 420 mhz2(1), 421 mhz5point5(2), 422 mhz6(3), 423 mhz9(4), 424 mhz11(5), 425 mhz12(6), 426 mhz18(7), 427 mhz24(8), 428 mhz36(9), 429 mhz48(10), 430 mhz54(11) 431 } 432 433END 434 435 436 437