All MIBs › CISCO-LWAPP-TC-MIB
Organization: Cisco Systems, Inc.
Last Updated: 2019-11-29
Category: Cisco Devices, Textual Conventions and Registries, Wireless and WLAN
Description:
Defines textual conventions used across Cisco LWAPP (Lightweight Access Point Protocol) MIB modules for wireless LAN controller management.
Imported Objects
From CISCO-SMI
| ciscoMgmt | OBJECT-IDENTITY |
From SNMPv2-SMI
| Gauge32 | |
| MODULE-IDENTITY | |
| Unsigned32 |
From SNMPv2-TC
| TEXTUAL-CONVENTION |
What Is CISCO-LWAPP-TC-MIB?
CISCO-LWAPP-TC-MIB is a Cisco textual-conventions MIB that defines shared data types used across Cisco's family of enterprise MIBs implemented on Wireless LAN Controllers (Central Controllers, or CCs) that terminate the Lightweight Access Point Protocol (LWAPP) from associated lightweight access points. It contains no runtime data objects or tables of its own (sample_objects is empty)—it purely establishes common SNMP textual conventions (data type definitions) that other Cisco LWAPP MIBs reference for consistency. As such it does not itself expose uptime, hardware sensors, or performance counters; those are defined in the actual LWAPP-related MIBs (e.g., controller, access point, or client MIBs) that import these conventions. It has an explicit, direct dependency relationship with the broader suite of Cisco LWAPP/CAPWAP wireless MIBs, since those modules import types defined here. It is deployed only in conjunction with Cisco Unified Wireless Network (WLC-based) environments, never as a standalone monitored entity. Any CISCO-LWAPP-TC-MIB OID that appears in a sibling wireless MIB's imports clause simply references one of these shared textual conventions rather than a runtime object.
IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-LWAPP-TC-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- Cisco Wireless LAN Controllers (WLC) and LWAPP-based lightweight access points
Monitoring Examples
Since this module defines only textual conventions and no sample_objects, there is no direct monitoring scenario here—it supplies shared data types (e.g., enumerations, string formats) consumed by other Cisco LWAPP MIBs. Real monitoring of controller and access point status would be performed against those sibling MIBs that reference the conventions defined in this module.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| ciscoLwappTextualConventions | 1.3.6.1.4.1.9.9.514 | This module defines textual conventions used throughout the Cisco enterprise MIBs designed for implementation on Central Controllers that terminate the Light Weight Access Point Protocol from LWAPP Access Points. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ +......+ + + + + + + + + + CC + + CC + + CC + + CC + + + + + + + + + +......+ +......+ +......+ +......+ .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + AP + + AP + + AP + + AP + + AP + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ . . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + MN + + MN + + MN + + MN + + MN + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ The LWAPP tunnel exists between the controller and the APs. The MNs communicate with the APs through the protocol defined by the 802.11 standard. LWAPP APs, upon bootup, discover and join one of the controllers and the controller pushes the configuration, that includes the WLAN parameters, to the LWAPP APs. The APs then encapsulate all the 802.11 frames from wireless clients inside LWAPP frames and forward the LWAPP frames to the controller. GLOSSARY Access Point ( AP ) An entity that contains an 802.11 medium access control ( MAC ) and physical layer ( PHY ) interface and provides access to the distribution services via the wireless medium for associated clients. LWAPP APs encapsulate all the 802.11 frames in LWAPP frames and sends it to the controller to which it is logically connected. Advanced Encryption Standard ( AES ) In cryptography, the Advanced Encryption Standard (AES), also known as Rijndael, is a block cipher adopted as an encryption standard by the US government. It is expected to be used worldwide and analysed extensively, as was the case with its predecessor, the Data Encryption Standard (DES). AES was adopted by National Institute of Standards and Technology (NIST) as US FIPS PUB 197 in November 2001 after a 5-year standardisation process. Central Controller ( CC ) The central entity that terminates the LWAPP protocol tunnel from the LWAPP APs. Throughout this MIB, this entity is also referred to as 'controller'. Light Weight Access Point Protocol ( LWAPP ) This is a generic protocol that defines the communication between the Access Points and the Central Controller. Management Frame Protection ( MFP ) A proprietary mechanism devised to integrity protect the otherwise unprotected management frames of the 802.11 protocol specification. Message Integrity Check ( MIC ) A checksum computed on a sequence of bytes and made known to the receiving party in a data communication, to let the receiving party make sure the bytes received were not compromised enroute. Mobile Node ( MN ) A roaming 802.11 wireless device in a wireless network associated with an access point. Temporal Key Integrity Protocol ( TKIP ) A security protocol defined to enhance the limitations of WEP. Message Integrity Check and per-packet keying on all WEP-encrypted frames are two significant enhancements provided by TKIP to WEP. Wired Equivalent Privacy ( WEP ) A security method defined by 802.11. WEP uses a symmetric key stream cipher called RC4 to encrypt the data packets. 802.11n 802.11n builds upon previous 802.11 standards by adding MIMO (multiple-input multiple-output). MIMO uses multiple transmitter and receiver antennas to allow for increased data throughput through spatial multiplexing and increased range. Control/Extension Channel A single 802.11 channel is 20 MHz wide. 802.11n allows the use of channels of width 40 MHz by combining two 20 MHz channels. The channels are known as the primary or control channel and secondary or extension channel. Both the channels are used for transmission and reception of data. REFERENCE [1] Part 11 Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications. [2] Draft-obara-capwap-lwapp-00.txt, IETF Light Weight Access Point Protocol. [3] Enhanced Wireless Consortium MAC Specification, v1.24. [4] Enhanced Wireless Consortium PHY Specification, v1.27. |
RFC description
Cisco vendor-specific textual convention MIB for lightweight AP (LWAPP); defines common data types and enumerations used in LWAPP management MIBs.
Start monitoring Cisco Wireless LAN Controllers (LWAPP-based) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.