CISCO-LWAPP-DOT11-CLIENT-CCX-REPORTS-MIB
AI MIB Summary
The CISCO-LWAPP-DOT11-CLIENT-CCX-REPORTS-MIB enables Cisco Central Controllers to monitor and report Cisco Compatible Extensions (CCX) specific metrics and radio management data for 802.11 mobile clients associated with LWAPP-enabled Access Points. This module facilitates the collection of proprietary performance, roaming, and power-saving statistics that extend beyond standard IEEE 802.11 definitions to support optimized wireless network operations.
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
Main OID:
ciscoLwappDot11ClientRmMIB.1.3.6.1.4.1.9.9.767
63
Objects
Active
Status
5
Dependencies
Imported Objects
Objects
63 total| Object Name |
|---|
ciscoLwappDot11ClientRmMIBThis 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 MODULE-IDENTITY .1.3.6.1.4.1.9.9.767 |
ciscoLwapDot11ClientRmMIBNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.767.0 |
ciscoLwappDot11ClientRmMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.767.1 |
cldccrRmReq OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.767.1.1 |
cldccrRmReqTableThis table is used to configure the radio
measurement request parameters to be sent to the ccxv4
clients. SEQUENCE OF CldccrRmReqEntry .1.3.6.1.4.1.9.9.767.1.1.1 |
cldccrRmReqEntryEach entry represents a conceptual row in this table.
An entry corresponds to a client for which a certain
type of report is being fetched. CldccrRmReqEntry .1.3.6.1.4.1.9.9.767.1.1.1.1 |
cldccrRmReqReportTypeThis object is set to list of radio measurement
requests the reports of which will be sent by the
ccxv4 client to the controller.rw Bits .1.3.6.1.4.1.9.9.767.1.1.1.1.1 |
cldccrRmInitiateReqThis object is used to send the rm req message to the
client.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.767.1.1.1.1.2 |
cldccrRmReqNumIterationsThis attribute is used to set the number of times
the rm request will be sent to the client.rw INTEGER .1.3.6.1.4.1.9.9.767.1.1.1.1.3 |
cldccrRmReqMeasDurationThe time interval between two RM Reqs in seconds.rw Unsigned32 .1.3.6.1.4.1.9.9.767.1.1.1.1.4 |
cldccrRmReqRowStatusThis is the status column for this row and is used to
create and delete specific instances of rows in this
table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.767.1.1.1.1.5 |
cldccrRmResp OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.767.1.2 |
cldccrRmHistRepTableThis table contains the noise histogram reports of the clients
which were queried for the same. SEQUENCE OF CldccrRmHistRepEntry .1.3.6.1.4.1.9.9.767.1.2.1 |
cldccrRmHistRepEntryThere is an entry in the table where entry is identified
by the client Mac address. CldccrRmHistRepEntry .1.3.6.1.4.1.9.9.767.1.2.1.1 |
cldccrRmHistIndexIndex which will be the channel number in most
cases. Unsigned32 .1.3.6.1.4.1.9.9.767.1.2.1.1.1 |
cldccrRmHistRepChannelNumberChannel number indicates the channel number to which the noise
histogram Report applies.ro Unsigned32 .1.3.6.1.4.1.9.9.767.1.2.1.1.2 |
cldccrRmHistRepTimeStampTimestamp of the histogram report.ro OCTET STRING .1.3.6.1.4.1.9.9.767.1.2.1.1.3 |
cldccrRmHistRepRPIDensity0This Field stores the RPI density in power range
power << -87 db.ro Unsigned32 .1.3.6.1.4.1.9.9.767.1.2.1.1.4 |
cldccrRmHistRepRPIDensity1This Field stores the RPI density in power
range -87 < power << -82.ro Unsigned32 .1.3.6.1.4.1.9.9.767.1.2.1.1.5 |
cldccrRmHistRepRPIDensity2This Field stores the RPI density in power
range -82 < power << -77.ro Unsigned32 .1.3.6.1.4.1.9.9.767.1.2.1.1.6 |
cldccrRmHistRepRPIDensity3This Field stores the RPI density in power
range -77 < power << -72.ro Unsigned32 .1.3.6.1.4.1.9.9.767.1.2.1.1.7 |
cldccrRmHistRepRPIDensity4This Field stores the RPI density in power
range -72< Power << -67.ro Unsigned32 .1.3.6.1.4.1.9.9.767.1.2.1.1.8 |
cldccrRmHistRepRPIDensity5This Field stores the RPI density in power
range -67< Power << -62.ro Unsigned32 .1.3.6.1.4.1.9.9.767.1.2.1.1.9 |
cldccrRmHistRepRPIDensity6This Field stores the RPI density in power
range -62< Power<< -57.ro Unsigned32 .1.3.6.1.4.1.9.9.767.1.2.1.1.10 |
cldccrRmHistRepRPIDensity7This Field stores the RPI density in power
range -57< Power<< -52.ro Unsigned32 .1.3.6.1.4.1.9.9.767.1.2.1.1.11 |
cldccrRmBeaconRepTableThis table contains the beacon reports of the clients
which were queried for the same. SEQUENCE OF CldccrRmBeaconRepEntry .1.3.6.1.4.1.9.9.767.1.2.2 |
cldccrRmBeaconRepEntryThere is an entry in the table where entry is identified
by the client Mac address. CldccrRmBeaconRepEntry .1.3.6.1.4.1.9.9.767.1.2.2.1 |
cldccrRmBeaconIndexIndex which will be the channel number in most
cases. Unsigned32 .1.3.6.1.4.1.9.9.767.1.2.2.1.1 |
cldccrRmBeaconRptChannelNumberChannel number indicates the channel number to which the noise
beacon report applies.ro Unsigned32 .1.3.6.1.4.1.9.9.767.1.2.2.1.2 |
cldccrRmBeaconRptTimeStampTimestamp of the beacon report.ro OCTET STRING .1.3.6.1.4.1.9.9.767.1.2.2.1.3 |
cldccrRmBeaconRptPhyTypePhy type indicates the physical
medium used.ro Enumeration .1.3.6.1.4.1.9.9.767.1.2.2.1.4 |
cldccrRmBeaconRptReceivedPowerThis field indicates the received strength of
the beacon or probe response frame in dBm.ro Unsigned32 .1.3.6.1.4.1.9.9.767.1.2.2.1.5 |
cldccrRmBeaconRptBSSIDThis field contains the 6-byte BSSID of the STA that
transmitted the beacon or probe response frame.ro MacAddress (SNMPv2-TC) .1.3.6.1.4.1.9.9.767.1.2.2.1.6 |
cldccrRmBeaconRptParentTsfThis 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.ro OCTET STRING .1.3.6.1.4.1.9.9.767.1.2.2.1.7 |
cldccrRmBeaconRptTargetTsfThis 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.ro OCTET STRING .1.3.6.1.4.1.9.9.767.1.2.2.1.8 |
cldccrRmBeaconRptIntervalThis field is equal to the 2-byte Beacon Interval
field in the received beacon or probe response.ro Unsigned32 .1.3.6.1.4.1.9.9.767.1.2.2.1.9 |
cldccrRmBeaconRptCapInfoThis attribute represents the capability info.ro Unsigned32 .1.3.6.1.4.1.9.9.767.1.2.2.1.10 |
cldccRmChannelLoadReportTableThis table contains the channel load reports of
the clients which were queried for the same. SEQUENCE OF CldccRmChannelLoadReportEntry .1.3.6.1.4.1.9.9.767.1.2.3 |
cldccRmChannelLoadReportEntryThere is an entry in the table where entry is
identified by the client Mac address. CldccRmChannelLoadReportEntry .1.3.6.1.4.1.9.9.767.1.2.3.1 |
cldccRmChannelLoadReportIndexThis indicates the index of the report table. Unsigned32 .1.3.6.1.4.1.9.9.767.1.2.3.1.1 |
cldccRmChannelLoadReportChannelNumberChannel Number indicates the channel number to which
the Channel Load Report applies.ro Unsigned32 .1.3.6.1.4.1.9.9.767.1.2.3.1.2 |
cldccRmChannelLoadReportTimeStampTimestamp of the channel load report.ro OCTET STRING .1.3.6.1.4.1.9.9.767.1.2.3.1.3 |
cldccRmChannelLoadReportCCABusyFractionCCA Busy Fraction shall contain the fractional duration
over which CCA indicated the channel was busy during the
measurement duration.ro Unsigned32 .1.3.6.1.4.1.9.9.767.1.2.3.1.4 |
cldccRmFrameReportTableThis table contains the frame reports of
the clients which were queried for the same. SEQUENCE OF CldccRmFrameReportEntry .1.3.6.1.4.1.9.9.767.1.2.4 |
cldccRmFrameReportEntryThere is an entry in the table where entry is
identified by the client Mac address. CldccRmFrameReportEntry .1.3.6.1.4.1.9.9.767.1.2.4.1 |
cldccRmFrameReportElemIndexThis attribute represents the index of
element index of frame report. Unsigned32 .1.3.6.1.4.1.9.9.767.1.2.4.1.1 |
cldccRmFrameReportSubElemIndexThis attribute represents the index of
the sub element in a frame report. Unsigned32 .1.3.6.1.4.1.9.9.767.1.2.4.1.2 |
cldccRmFrameReportChanNumberThis attribute represents the channel number
of frame report.ro Unsigned32 .1.3.6.1.4.1.9.9.767.1.2.4.1.3 |
cldccRmFrameReportTimeStampTimestamp of the frame report.ro OCTET STRING .1.3.6.1.4.1.9.9.767.1.2.4.1.4 |
cldccRmFrameReportTransmitAddrThis represents the transmitted address.ro MacAddress (SNMPv2-TC) .1.3.6.1.4.1.9.9.767.1.2.4.1.5 |
cldccRmFrameReportBssidThis represents the bssid.ro MacAddress (SNMPv2-TC) .1.3.6.1.4.1.9.9.767.1.2.4.1.6 |
cldccRmFrameReportRecvSigPowerThis field indicates the received strength of
the beacon or probe response frame in dBm.ro Unsigned32 .1.3.6.1.4.1.9.9.767.1.2.4.1.7 |
cldccRmFrameReportFrameCountThis field indicates the received strength of
the beacon or probe response frame in dBm.ro Unsigned32 .1.3.6.1.4.1.9.9.767.1.2.4.1.8 |
cldccrRmReqStatus OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.767.1.3 |
cldccrRmReqStatusTableThis table is used to get the status for
each of the reports. SEQUENCE OF CldccrRmReqStatusEntry .1.3.6.1.4.1.9.9.767.1.3.1 |
cldccrRmReqStatusEntryThere is an entry in the table where entry is identified
by the client Mac address. CldccrRmReqStatusEntry .1.3.6.1.4.1.9.9.767.1.3.1.1 |
cldccrRmFrameReqStatusThis attribute is used to initiate/track a frame
report request to the ccxv4 client.ro CiscoLwappCcxRmReqStatus .1.3.6.1.4.1.9.9.767.1.3.1.1.1 |
cldccrRmHistogramReqStatusThis attribute is used to initiate/track a noise histogram
request to the ccxv4 client.ro CiscoLwappCcxRmReqStatus .1.3.6.1.4.1.9.9.767.1.3.1.1.2 |
cldccrRmBeaconReqStatusThis attribute is used to initiate/track a beacon request
to the ccxv4 client.ro CiscoLwappCcxRmReqStatus .1.3.6.1.4.1.9.9.767.1.3.1.1.3 |
cldccrRmChanLoadReqStatusThis attribute is used to initiate/track a channel load request
to the ccxv4 client.ro CiscoLwappCcxRmReqStatus .1.3.6.1.4.1.9.9.767.1.3.1.1.4 |
ciscoLwappDot11ClientRmMIBConform OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.767.2 |
ciscoLwappDot11ClientRmMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.767.2.1 |
ciscoLwappDot11ClientRmMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.767.2.2 |