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.

This MIB provides information about the Rogue APs
and Clients that are detected by the controller.

The relationship between CC and the LWAPP APs
can be depicted as follows:

      +......+     +......+     +......+
      +      +     +      +     +      +
      +  CC  +     +  CC  +     +  CC  +
      +      +     +      +     +      +
      +......+     +......+     +......+
        ..            .             .
        ..            .             .
       .  .            .             .
      .    .            .             .
     .      .            .             .
    .        .            .             .
+......+ +......+     +......+      +......+
+      + +      +     +      +      +      +
+  AP  + +  AP  +     +  AP  +      +  AP  +
+      + +      +     +      +      +      +
+......+ +......+     +......+      +......+
           .              .             .
         .  .              .             .
        .    .              .             .
       .      .              .             .
      .        .              .             .
   +......+ +......+     +......+      +......+
   +      + +      +     +      +      +      +
   +  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.

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. Mobile Node 
and client are used interchangeably. 

Rogue

Any 802.11 device which is not part of the RF network 
is a Rogue device.

Ad-hoc Network 

A set of mobile devices within direct communication 
range establishing a network among themselves for 
transmitting data, without the use of a Access point 
is called a ad-hoc network. 

Rogue Ad-hoc Client

Any 802.11 client which is part of that ad-hoc network, 
but not in the trusted list.

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.

RSSI

Received Signal Strength Indication (RSSI), the IEEE 802.11
standard defines a mechanism by which RF energy is to be
measured by the circuitry on a wireless NIC. Its value is
measured in dBm and ranges from -128 to 0.

Rogue Location Detection Protocol (RLDP)

RLDP is a protocol to detect and automatically 
contain rogue devices. When the controller discovers 
a rogue access point, it uses the Rogue Location 
Discovery Protocol (RLDP) to determine if the 
rogue is attached to your network.
RLDP can be enabled/disabled per controller level.

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.