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 |
cldcClientMacAddress | CISCO-LWAPP-DOT11-CLIENT-MIB |
ciscoMgmt | CISCO-SMI |
MODULE-COMPLIANCE, OBJECT-GROUP | SNMPv2-CONF |
MODULE-IDENTITY, OBJECT-TYPE, Unsigned32 | SNMPv2-SMI |
RowStatus, MacAddress, TruthValue, TEXTUAL-CONVENTION | SNMPv2-TC |
ciscoLwappDot11ClientRmMIB | .1.3.6.1.4.1.9.9.767 | |
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 | |
cldccrRmReqEntry | .1.3.6.1.4.1.9.9.767.1.1.1.1 | |
cldccrRmReqReportType | .1.3.6.1.4.1.9.9.767.1.1.1.1.1 | |
cldccrRmInitiateReq | .1.3.6.1.4.1.9.9.767.1.1.1.1.2 | |
cldccrRmReqNumIterations | .1.3.6.1.4.1.9.9.767.1.1.1.1.3 | |
cldccrRmReqMeasDuration | .1.3.6.1.4.1.9.9.767.1.1.1.1.4 | |
cldccrRmReqRowStatus | .1.3.6.1.4.1.9.9.767.1.1.1.1.5 | |
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 | |
cldccrRmHistRepEntry | .1.3.6.1.4.1.9.9.767.1.2.1.1 | |
cldccrRmHistIndex | .1.3.6.1.4.1.9.9.767.1.2.1.1.1 | |
cldccrRmHistRepRPIDensity6 | .1.3.6.1.4.1.9.9.767.1.2.1.1.10 | |
cldccrRmHistRepRPIDensity7 | .1.3.6.1.4.1.9.9.767.1.2.1.1.11 | |
cldccrRmHistRepChannelNumber | .1.3.6.1.4.1.9.9.767.1.2.1.1.2 | |
cldccrRmHistRepTimeStamp | .1.3.6.1.4.1.9.9.767.1.2.1.1.3 | |
cldccrRmHistRepRPIDensity0 | .1.3.6.1.4.1.9.9.767.1.2.1.1.4 | |
cldccrRmHistRepRPIDensity1 | .1.3.6.1.4.1.9.9.767.1.2.1.1.5 | |
cldccrRmHistRepRPIDensity2 | .1.3.6.1.4.1.9.9.767.1.2.1.1.6 | |
cldccrRmHistRepRPIDensity3 | .1.3.6.1.4.1.9.9.767.1.2.1.1.7 | |
cldccrRmHistRepRPIDensity4 | .1.3.6.1.4.1.9.9.767.1.2.1.1.8 | |
cldccrRmHistRepRPIDensity5 | .1.3.6.1.4.1.9.9.767.1.2.1.1.9 | |
cldccrRmBeaconRepTable | .1.3.6.1.4.1.9.9.767.1.2.2 | |
cldccrRmBeaconRepEntry | .1.3.6.1.4.1.9.9.767.1.2.2.1 | |
cldccrRmBeaconIndex | .1.3.6.1.4.1.9.9.767.1.2.2.1.1 | |
cldccrRmBeaconRptCapInfo | .1.3.6.1.4.1.9.9.767.1.2.2.1.10 | |
cldccrRmBeaconRptChannelNumber | .1.3.6.1.4.1.9.9.767.1.2.2.1.2 | |
cldccrRmBeaconRptTimeStamp | .1.3.6.1.4.1.9.9.767.1.2.2.1.3 | |
cldccrRmBeaconRptPhyType | .1.3.6.1.4.1.9.9.767.1.2.2.1.4 | |
cldccrRmBeaconRptReceivedPower | .1.3.6.1.4.1.9.9.767.1.2.2.1.5 | |
cldccrRmBeaconRptBSSID | .1.3.6.1.4.1.9.9.767.1.2.2.1.6 | |
cldccrRmBeaconRptParentTsf | .1.3.6.1.4.1.9.9.767.1.2.2.1.7 | |
cldccrRmBeaconRptTargetTsf | .1.3.6.1.4.1.9.9.767.1.2.2.1.8 | |
cldccrRmBeaconRptInterval | .1.3.6.1.4.1.9.9.767.1.2.2.1.9 | |
cldccRmChannelLoadReportTable | .1.3.6.1.4.1.9.9.767.1.2.3 | |
cldccRmChannelLoadReportEntry | .1.3.6.1.4.1.9.9.767.1.2.3.1 | |
cldccRmChannelLoadReportIndex | .1.3.6.1.4.1.9.9.767.1.2.3.1.1 | |
cldccRmChannelLoadReportChannelNumber | .1.3.6.1.4.1.9.9.767.1.2.3.1.2 | |
cldccRmChannelLoadReportTimeStamp | .1.3.6.1.4.1.9.9.767.1.2.3.1.3 | |
cldccRmChannelLoadReportCCABusyFraction | .1.3.6.1.4.1.9.9.767.1.2.3.1.4 | |
cldccRmFrameReportTable | .1.3.6.1.4.1.9.9.767.1.2.4 | |
cldccRmFrameReportEntry | .1.3.6.1.4.1.9.9.767.1.2.4.1 | |
cldccRmFrameReportElemIndex | .1.3.6.1.4.1.9.9.767.1.2.4.1.1 | |
cldccRmFrameReportSubElemIndex | .1.3.6.1.4.1.9.9.767.1.2.4.1.2 | |
cldccRmFrameReportChanNumber | .1.3.6.1.4.1.9.9.767.1.2.4.1.3 | |
cldccRmFrameReportTimeStamp | .1.3.6.1.4.1.9.9.767.1.2.4.1.4 | |
cldccRmFrameReportTransmitAddr | .1.3.6.1.4.1.9.9.767.1.2.4.1.5 | |
cldccRmFrameReportBssid | .1.3.6.1.4.1.9.9.767.1.2.4.1.6 | |
cldccRmFrameReportRecvSigPower | .1.3.6.1.4.1.9.9.767.1.2.4.1.7 | |
cldccRmFrameReportFrameCount | .1.3.6.1.4.1.9.9.767.1.2.4.1.8 | |
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 | |
cldccrRmReqStatusEntry | .1.3.6.1.4.1.9.9.767.1.3.1.1 | |
cldccrRmFrameReqStatus | .1.3.6.1.4.1.9.9.767.1.3.1.1.1 | |
cldccrRmHistogramReqStatus | .1.3.6.1.4.1.9.9.767.1.3.1.1.2 | |
cldccrRmBeaconReqStatus | .1.3.6.1.4.1.9.9.767.1.3.1.1.3 | |
cldccrRmChanLoadReqStatus | .1.3.6.1.4.1.9.9.767.1.3.1.1.4 | |
ciscoLwappDot11ClientRmMIBConform | .1.3.6.1.4.1.9.9.767.2 | |
ciscoLwappDot11ClientRmMIBCompliances | .1.3.6.1.4.1.9.9.767.2.1 | |
ciscoLwappDot11ClientRmMIBGroups | .1.3.6.1.4.1.9.9.767.2.2 |