CISCO-LWAPP-DOT11-CLIENT-CCX-REPORTS-MIB: View SNMP OID List / Download MIB

This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight 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 them to the controller to which it is logically connected. Central Controller ( CC ) The central entity that terminates the LWAPP protocol tunnel from the LWAPP APs. Throughout this MIB, this entity also referred to as 'controller'. Cisco Compatible eXtensions (CCX) Wireless LAN Access Points (APs) manufactured by Cisco Systems have features and capabilities beyond those in related standards (e.g., IEEE 802.11 suite of standards, Wi-Fi recommendations by WECA, 802.1X security suite, etc). A number of features provide higher performance. For example, Cisco AP transmits a specific Information Element, which the clients adapt to for enhanced performance. Similarly, a number of features are implemented by means of proprietary Information Elements, which Cisco clients use in specific ways to carry out tasks above and beyond the standard. Other examples of feature categories are roaming and power saving. Light Weight Access Point Protocol ( LWAPP ) This is a generic protocol that defines the communication between the Access Points and the Central Controller. Mobile Node ( MN ) A roaming 802.11 wireless device in a wireless network associated with an access point. The terms 'Mobile node' and 'client' are used interchangeably. Radio Management (RM) This term refers to managing the 802.11 radio environment to provide the best quality service to to the 802.11 wireless clients. Service Set Identifier ( SSID ) SSID is a unique identifier that APs and clients use to identify with each other. SSID is a simple means of access control and is not for security. The SSID can be any alphanumeric entry up to 32 characters. REFERENCE [1] Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications [2] Draft-obara-capwap-lwapp-00.txt, IETF Light Weight Access Point Protocol

This table is used to configure the radio measurement request parameters to be sent to the ccxv4 clients.

Each entry represents a conceptual row in this table. An entry corresponds to a client for which a certain type of report is being fetched.

This object is set to list of radio measurement requests the reports of which will be sent by the ccxv4 client to the controller. Bits: 'frameReport': 3, 'beaconReport': 2, 'channelLoadReport': 0, 'histogramReport': 1.

This object is used to send the rm req message to the client.

This attribute is used to set the number of times the rm request will be sent to the client.

The time interval between two RM Reqs in seconds.

This is the status column for this row and is used to create and delete specific instances of rows in this table.

This table contains the noise histogram reports of the clients which were queried for the same.

There is an entry in the table where entry is identified by the client Mac address.

Index which will be the channel number in most cases.

Channel number indicates the channel number to which the noise histogram Report applies.

Timestamp of the histogram report.

This Field stores the RPI density in power range power << -87 db.

This Field stores the RPI density in power range -87 < power << -82.

This Field stores the RPI density in power range -82 < power << -77.

This Field stores the RPI density in power range -77 < power << -72.

This Field stores the RPI density in power range -72< Power << -67.

This Field stores the RPI density in power range -67< Power << -62.

This Field stores the RPI density in power range -62< Power<< -57.

This Field stores the RPI density in power range -57< Power<< -52.

This table contains the beacon reports of the clients which were queried for the same.

There is an entry in the table where entry is identified by the client Mac address.

Index which will be the channel number in most cases.

Channel number indicates the channel number to which the noise beacon report applies.

Timestamp of the beacon report.

Phy type indicates the physical medium used. Enumeration: 'erp': 6, 'ofdm': 4, 'dss': 2, 'unused': 3, 'highDataRateDss': 5, 'fh': 1.

This field indicates the received strength of the beacon or probe response frame in dBm.

This field contains the 6-byte BSSID of the STA that transmitted the beacon or probe response frame.

This field is used to store the parent TSF Parent TSF contains the lower 4 bytes of the serving APs. TSF value at the time the measuring STA received the beacon or probe response frame.

This field is used to store the Target TSF. Target TSF contains the 8-byte TSF value contained in the beacon or probe response received by the measuring STA.

This field is equal to the 2-byte Beacon Interval field in the received beacon or probe response.

This attribute represents the capability info.

This table contains the channel load reports of the clients which were queried for the same.

There is an entry in the table where entry is identified by the client Mac address.

This indicates the index of the report table.

Channel Number indicates the channel number to which the Channel Load Report applies.

Timestamp of the channel load report.

CCA Busy Fraction shall contain the fractional duration over which CCA indicated the channel was busy during the measurement duration.

This table contains the frame reports of the clients which were queried for the same.

There is an entry in the table where entry is identified by the client Mac address.

This attribute represents the index of element index of frame report.

This attribute represents the index of the sub element in a frame report.

This attribute represents the channel number of frame report.

Timestamp of the frame report.

This represents the transmitted address.

This represents the bssid.

This field indicates the received strength of the beacon or probe response frame in dBm.

This field indicates the received strength of the beacon or probe response frame in dBm.

This table is used to get the status for each of the reports.

There is an entry in the table where entry is identified by the client Mac address.

This attribute is used to initiate/track a frame report request to the ccxv4 client.

This attribute is used to initiate/track a noise histogram request to the ccxv4 client.

This attribute is used to initiate/track a beacon request to the ccxv4 client.

This attribute is used to initiate/track a channel load request to the ccxv4 client.

The compliance statement for the SNMP entities that implement the ciscoLwappDot11ClientRmMIB module.

This collection of objects represent the reports of the CCX Clients.