本帖最后由 reay 于 2016-4-6 17:07 编辑
Local modeThis is the default mode of operation. When an LAP is placed into local
mode, the AP will transmit on the normally assigned channel. However, the AP also
monitors all other channels in the band over a period of 180 seconds to scan each of
the other channels for 60ms during the non−transmit time. During this time, the AP
performs noise floor measurements, measures interference, and scans for IDS events.
♦
REAP modeRemote Edge Access Point (REAP) mode enables an LAP to reside
across a WAN link and still be able to communicate with the WLC and provide the
functionality of a regular LAP. REAP mode is supported only on the 1030 LAPs.
♦
H−REAP Mode H−REAP is a wireless solution for branch office and remote office
deployments. H−REAP enables customers to configure and control access points
(APs) in a branch or remote office from the corporate office through a WAN link
without the need to deploy a controller in each office. H−REAPs can switch client
data traffic locally and perform client authentication locally when the connection to
the controller is lost. When connected to the controller, H−REAPs can also tunnel
traffic back to the controller.
♦
Monitor modeMonitor mode is a feature designed to allow specified
LWAPP−enabled APs to exclude themselves from handling data traffic between
clients and the infrastructure. They instead act as dedicated sensors for location based
services (LBS), rogue access point detection, and intrusion detection (IDS). When
APs are in Monitor mode they cannot serve clients and continuously cycle through all
♦
configured channels listening to each channel for approximately 60 ms.
Note: From the controller release 5.0, LWAPPs can also be configured in Location
Optimized Monitor Mode (LOMM), which optimizes the monitoring and location
calculation of RFID tags. For more information on this mode, refer to Cisco Unified
Wireless Network Software Release 5.0.
Note: With controller release 5.2, the Location Optimized Monitor Mode
(LOMM) section has been renamed Tracking Optimization, and the LOMM
Enabled drop−down box has been renamed Enable Tracking Optimization.
Note: For more information on how to configure Tracking Optimization, read the
Optimizing RFID Tracking on Access Points section.
Rogue detector modeLAPs that operate in Rogue Detector mode monitor the rogue
APs. They do not transmit or contain rogue APs. The idea is that the rogue detector
should be able to see all the VLANs in the network since rogue APs can be connected
to any of the VLANs in the network (thus we connect it to a trunk port). The switch
sends all the rogue AP/Client MAC address lists to the Rogue Detector (RD). The RD
then forwards those up to the WLC in order to compare with the MACs of clients that
the WLC APs have heard over the air. If MACs match, then the WLC knows the
rogue AP to which those clients are connected is on the wired network.
♦
Sniffer modeAn LWAPP that operates in Sniffer mode functions as a sniffer and
captures and forwards all the packets on a particular channel to a remote machine that
runs Airopeek. These packets contain information on timestamp, signal strength,
packet size and so on. The Sniffer feature can be enabled only if you run Airopeek,
which is a third−party network analyzer software that supports decoding of data
packets.
♦
Bridge Mode Bridge mode is used when the access points are setup in a mesh
environment and used to bridge between each other.
