CISCO-LWAPP-DOT11-CLIENT-CCX-REPORTS-MIB

All MIBs › CISCO-LWAPP-DOT11-CLIENT-CCX-REPORTS-MIB

Organization: Cisco Systems Inc.

Last Updated: 2010-12-13

Description: Cisco LWAPP MIB for collecting CCX radio measurement reports from 802.11 wireless clients via Cisco WLAN controllers

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) 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.

What Is CISCO-LWAPP-DOT11-CLIENT-CCX-REPORTS-MIB?

The CISCO-LWAPP-DOT11-CLIENT-CCX-REPORTS-MIB collects Cisco Compatible Extensions radio measurement reports from 802.11 wireless clients via Cisco Wireless LAN Controllers terminating LWAPP tunnels from lightweight access points. It exposes tables for requesting radio measurements, including report type, number of iterations, and measurement duration, and historical tables holding the resulting measurement reports, including channel number and timestamp. Administrators use this data to monitor wireless client and RF environment health, initiating a measurement request and then examining cldccrRmHistRepTable entries to assess channel conditions or interference a specific client experienced, which helps diagnose spotty wireless performance. It belongs to the Cisco LWAPP/802.11 controller MIB family and layers Cisco's CCX radio-management extensions on top of standard 802.11 concepts. It is deployed in enterprise WLANs for RF troubleshooting and site-survey validation using CCX-capable client devices. Engineers can download the CISCO-LWAPP-DOT11-CLIENT-CCX-REPORTS-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-LWAPP-DOT11-CLIENT-CCX-REPORTS-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 Controller (WLC)
802.11 CCX-capable wireless client

Monitoring Examples

An admin populates cldccrRmReqTable/Entry with cldccrRmReqReportType, cldccrRmReqNumIterations, and cldccrRmReqMeasDuration, then sets cldccrRmReqRowStatus/cldccrRmInitiateReq to trigger the measurement. Results appear in cldccrRmHistRepTable indexed by cldccrRmHistIndex, showing cldccrRmHistRepChannelNumber and cldccrRmHistRepTimeStamp for each historical report, letting the admin correlate a client's reported channel conditions with observed connectivity complaints.

What Can Be Monitored

radio measurement report history
measurement channel number
measurement report timestamp
measurement request status

Imported Objects

From CISCO-LWAPP-DOT11-CLIENT-MIB

cldcClientMacAddress

OBJECT-TYPE

From CISCO-SMI

ciscoMgmt

OBJECT-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

MacAddress
RowStatus
TEXTUAL-CONVENTION
TruthValue

OIDs

OID symbolic	OID numeric	Type	Access	Description
ciscoLwappDot11ClientRmMIB	1.3.6.1.4.1.9.9.767			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
ciscoLwapDot11ClientRmMIBNotifs	1.3.6.1.4.1.9.9.767.0
ciscoLwappDot11ClientRmMIBObjects	1.3.6.1.4.1.9.9.767.1
cldccrRmReq	1.3.6.1.4.1.9.9.767.1.1
cldccrRmReqTable	1.3.6.1.4.1.9.9.767.1.1.1		not-accessible	This table is used to configure the radio measurement request parameters to be sent to the ccxv4 clients.
cldccrRmReqEntry	1.3.6.1.4.1.9.9.767.1.1.1.1		not-accessible	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.
BIT cldccrRmReqReportType	1.3.6.1.4.1.9.9.767.1.1.1.1.1	Bits	read-create	This object is set to list of radio measurement requests the reports of which will be sent by the ccxv4 client to the controller.
T/F cldccrRmInitiateReq	1.3.6.1.4.1.9.9.767.1.1.1.1.2	TruthValue	read-create	This object is used to send the rm req message to the client.
INT cldccrRmReqNumIterations	1.3.6.1.4.1.9.9.767.1.1.1.1.3	INTEGER	read-create	This attribute is used to set the number of times the rm request will be sent to the client.
U32 cldccrRmReqMeasDuration	1.3.6.1.4.1.9.9.767.1.1.1.1.4	Unsigned32	read-create	The time interval between two RM Reqs in seconds.
ROW cldccrRmReqRowStatus	1.3.6.1.4.1.9.9.767.1.1.1.1.5	RowStatus	read-create	This is the status column for this row and is used to create and delete specific instances of rows in this table.
cldccrRmResp	1.3.6.1.4.1.9.9.767.1.2
cldccrRmHistRepTable	1.3.6.1.4.1.9.9.767.1.2.1		not-accessible	This table contains the noise histogram reports of the clients which were queried for the same.
cldccrRmHistRepEntry	1.3.6.1.4.1.9.9.767.1.2.1.1		not-accessible	There is an entry in the table where entry is identified by the client Mac address.
U32 cldccrRmHistIndex	1.3.6.1.4.1.9.9.767.1.2.1.1.1	Unsigned32	not-accessible	Index which will be the channel number in most cases.
U32 cldccrRmHistRepChannelNumber	1.3.6.1.4.1.9.9.767.1.2.1.1.2	Unsigned32	read-only	Channel number indicates the channel number to which the noise histogram Report applies.
OCT cldccrRmHistRepTimeStamp	1.3.6.1.4.1.9.9.767.1.2.1.1.3	OCTET STRING	read-only	Timestamp of the histogram report.
U32 cldccrRmHistRepRPIDensity0	1.3.6.1.4.1.9.9.767.1.2.1.1.4	Unsigned32	read-only	This Field stores the RPI density in power range power << -87 db.
U32 cldccrRmHistRepRPIDensity1	1.3.6.1.4.1.9.9.767.1.2.1.1.5	Unsigned32	read-only	This Field stores the RPI density in power range -87 < power << -82.
U32 cldccrRmHistRepRPIDensity2	1.3.6.1.4.1.9.9.767.1.2.1.1.6	Unsigned32	read-only	This Field stores the RPI density in power range -82 < power << -77.
U32 cldccrRmHistRepRPIDensity3	1.3.6.1.4.1.9.9.767.1.2.1.1.7	Unsigned32	read-only	This Field stores the RPI density in power range -77 < power << -72.
U32 cldccrRmHistRepRPIDensity4	1.3.6.1.4.1.9.9.767.1.2.1.1.8	Unsigned32	read-only	This Field stores the RPI density in power range -72< Power << -67.
U32 cldccrRmHistRepRPIDensity5	1.3.6.1.4.1.9.9.767.1.2.1.1.9	Unsigned32	read-only	This Field stores the RPI density in power range -67< Power << -62.
U32 cldccrRmHistRepRPIDensity6	1.3.6.1.4.1.9.9.767.1.2.1.1.10	Unsigned32	read-only	This Field stores the RPI density in power range -62< Power<< -57.
U32 cldccrRmHistRepRPIDensity7	1.3.6.1.4.1.9.9.767.1.2.1.1.11	Unsigned32	read-only	This Field stores the RPI density in power range -57< Power<< -52.
cldccrRmBeaconRepTable	1.3.6.1.4.1.9.9.767.1.2.2		not-accessible	This table contains the beacon reports of the clients which were queried for the same.
cldccrRmBeaconRepEntry	1.3.6.1.4.1.9.9.767.1.2.2.1		not-accessible	There is an entry in the table where entry is identified by the client Mac address.
U32 cldccrRmBeaconIndex	1.3.6.1.4.1.9.9.767.1.2.2.1.1	Unsigned32	not-accessible	Index which will be the channel number in most cases.
U32 cldccrRmBeaconRptChannelNumber	1.3.6.1.4.1.9.9.767.1.2.2.1.2	Unsigned32	read-only	Channel number indicates the channel number to which the noise beacon report applies.
OCT cldccrRmBeaconRptTimeStamp	1.3.6.1.4.1.9.9.767.1.2.2.1.3	OCTET STRING	read-only	Timestamp of the beacon report.
INT cldccrRmBeaconRptPhyType	1.3.6.1.4.1.9.9.767.1.2.2.1.4	INTEGER	read-only	Phy type indicates the physical medium used.
U32 cldccrRmBeaconRptReceivedPower	1.3.6.1.4.1.9.9.767.1.2.2.1.5	Unsigned32	read-only	This field indicates the received strength of the beacon or probe response frame in dBm.
MAC cldccrRmBeaconRptBSSID	1.3.6.1.4.1.9.9.767.1.2.2.1.6	MacAddress	read-only	This field contains the 6-byte BSSID of the STA that transmitted the beacon or probe response frame.
OCT cldccrRmBeaconRptParentTsf	1.3.6.1.4.1.9.9.767.1.2.2.1.7	OCTET STRING	read-only	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.
OCT cldccrRmBeaconRptTargetTsf	1.3.6.1.4.1.9.9.767.1.2.2.1.8	OCTET STRING	read-only	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.
U32 cldccrRmBeaconRptInterval	1.3.6.1.4.1.9.9.767.1.2.2.1.9	Unsigned32	read-only	This field is equal to the 2-byte Beacon Interval field in the received beacon or probe response.
U32 cldccrRmBeaconRptCapInfo	1.3.6.1.4.1.9.9.767.1.2.2.1.10	Unsigned32	read-only	This attribute represents the capability info.
cldccRmChannelLoadReportTable	1.3.6.1.4.1.9.9.767.1.2.3		not-accessible	This table contains the channel load reports of the clients which were queried for the same.
cldccRmChannelLoadReportEntry	1.3.6.1.4.1.9.9.767.1.2.3.1		not-accessible	There is an entry in the table where entry is identified by the client Mac address.
U32 cldccRmChannelLoadReportIndex	1.3.6.1.4.1.9.9.767.1.2.3.1.1	Unsigned32	not-accessible	This indicates the index of the report table.
U32 cldccRmChannelLoadReportChannelNumber	1.3.6.1.4.1.9.9.767.1.2.3.1.2	Unsigned32	read-only	Channel Number indicates the channel number to which the Channel Load Report applies.
OCT cldccRmChannelLoadReportTimeStamp	1.3.6.1.4.1.9.9.767.1.2.3.1.3	OCTET STRING	read-only	Timestamp of the channel load report.
U32 cldccRmChannelLoadReportCCABusyFraction	1.3.6.1.4.1.9.9.767.1.2.3.1.4	Unsigned32	read-only	CCA Busy Fraction shall contain the fractional duration over which CCA indicated the channel was busy during the measurement duration.
cldccRmFrameReportTable	1.3.6.1.4.1.9.9.767.1.2.4		not-accessible	This table contains the frame reports of the clients which were queried for the same.
cldccRmFrameReportEntry	1.3.6.1.4.1.9.9.767.1.2.4.1		not-accessible	There is an entry in the table where entry is identified by the client Mac address.
U32 cldccRmFrameReportElemIndex	1.3.6.1.4.1.9.9.767.1.2.4.1.1	Unsigned32	not-accessible	This attribute represents the index of element index of frame report.
U32 cldccRmFrameReportSubElemIndex	1.3.6.1.4.1.9.9.767.1.2.4.1.2	Unsigned32	not-accessible	This attribute represents the index of the sub element in a frame report.
U32 cldccRmFrameReportChanNumber	1.3.6.1.4.1.9.9.767.1.2.4.1.3	Unsigned32	read-only	This attribute represents the channel number of frame report.
OCT cldccRmFrameReportTimeStamp	1.3.6.1.4.1.9.9.767.1.2.4.1.4	OCTET STRING	read-only	Timestamp of the frame report.
MAC cldccRmFrameReportTransmitAddr	1.3.6.1.4.1.9.9.767.1.2.4.1.5	MacAddress	read-only	This represents the transmitted address.
MAC cldccRmFrameReportBssid	1.3.6.1.4.1.9.9.767.1.2.4.1.6	MacAddress	read-only	This represents the bssid.
U32 cldccRmFrameReportRecvSigPower	1.3.6.1.4.1.9.9.767.1.2.4.1.7	Unsigned32	read-only	This field indicates the received strength of the beacon or probe response frame in dBm.
U32 cldccRmFrameReportFrameCount	1.3.6.1.4.1.9.9.767.1.2.4.1.8	Unsigned32	read-only	This field indicates the received strength of the beacon or probe response frame in dBm.
cldccrRmReqStatus	1.3.6.1.4.1.9.9.767.1.3
cldccrRmReqStatusTable	1.3.6.1.4.1.9.9.767.1.3.1		not-accessible	This table is used to get the status for each of the reports.
cldccrRmReqStatusEntry	1.3.6.1.4.1.9.9.767.1.3.1.1		not-accessible	There is an entry in the table where entry is identified by the client Mac address.
CIS cldccrRmFrameReqStatus	1.3.6.1.4.1.9.9.767.1.3.1.1.1	CiscoLwappCcxRmReqStatus	read-only	This attribute is used to initiate/track a frame report request to the ccxv4 client.
CIS cldccrRmHistogramReqStatus	1.3.6.1.4.1.9.9.767.1.3.1.1.2	CiscoLwappCcxRmReqStatus	read-only	This attribute is used to initiate/track a noise histogram request to the ccxv4 client.
CIS cldccrRmBeaconReqStatus	1.3.6.1.4.1.9.9.767.1.3.1.1.3	CiscoLwappCcxRmReqStatus	read-only	This attribute is used to initiate/track a beacon request to the ccxv4 client.
CIS cldccrRmChanLoadReqStatus	1.3.6.1.4.1.9.9.767.1.3.1.1.4	CiscoLwappCcxRmReqStatus	read-only	This attribute is used to initiate/track a channel load request to the ccxv4 client.
ciscoLwappDot11ClientRmMIBConform	1.3.6.1.4.1.9.9.767.2
ciscoLwappDot11ClientRmMIBCompliances	1.3.6.1.4.1.9.9.767.2.1
ciscoLwappDot11ClientRmMibCompliance	1.3.6.1.4.1.9.9.767.2.1.1			The compliance statement for the SNMP entities that implement the ciscoLwappDot11ClientRmMIB module.
ciscoLwappDot11ClientRmMIBGroups	1.3.6.1.4.1.9.9.767.2.2
ciscoLwappDot11ClientRmConfigGroup	1.3.6.1.4.1.9.9.767.2.2.1			This collection of objects represent the reports of the CCX Clients.

RFC description

Cisco Lightweight AP (LWAPP) wireless client CCX reporting; provides client performance metrics and diagnostics on wireless controllers.

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.

Download CISCO-LWAPP-DOT11-CLIENT-CCX-REPORTS-MIB

What Is CISCO-LWAPP-DOT11-CLIENT-CCX-REPORTS-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description