User guide

9
Release Notes for the CiscoWorks Wireless LAN Solution Engine, Release 2.7.1
OL-6255-01
Documentation Updates
Using Scanning-Only APs
Step one in the “Using Scanning-Only APs” section should read:
Use a template-based configuration job to configure one or more APs as
scanning-only APs (see “Using IOS Templates”). Follow these guidelines when
you create the template:
• Keep the configuration simple. For example, do not configure VLAN/SSID
for Scanning-Only APs.
• Do not configure the scanning-only AP as an active/backup WDS (to serve
fast roaming traffic).
Note Even though configuring Scanning-Only APs and configuring WDS are
independent features, they will contend with each other on the same CPU
if both are enabled on the same AP. To make certain that Scanning-Only
AP traffic does not affect the real time performance for fast roaming, do
not configure a Scanning-Only AP to act as a WDS (active or backup) to
support fast-roaming clients. However, if the subnet contains only
Scanning-Only APs and no regular APs serving fast-roaming clients, you
can configure one of the Scanning-Only APs to run WDS.
Also in the “Using Scanning-Only APs” section, Step 4 should read:
In a heavy-load environment, APs running in scanning-only mode may face
sporadic connection loss and image upgrade failure. To resolve these problems,
use the following AP configuration CLI commands to balance CPU time:
scheduler interval <100-xxx>
scheduler allocate <3000-xxx> <1000-xxx>
Many newer Cisco platforms use the command scheduler allocate instead of
scheduler interval. The scheduler allocate command takes two parameters: a
period in microseconds for the system to run with interrupts enabled, and a period
in microseconds for the system to run with interrupts masked. Please refer to the
IOS documentation for more information about these commands.