1-15
Cisco Wireless LAN Controller Configuration Guide
OL-9141-03
Chapter 1 Overview
Pico Cell Functionality
Pico Cell functionality includes optimization of the operating system (operating system) to support this
functionality as follows:
•
The Cisco WCS Pico Cell Mode parameter reconfigures operating system parameters, allowing
operating system to function efficiently in pico cell deployments. Note that when the operator is
deploying a pico cell network the operating system must also have more memory allocated (512 to
2048 MB) using the
config database size 2048
CLI command.
•
Client mobility between multiple mobility domains when such exist.
•
Addition of a WPA2 VFF extension to eliminate the need to re-key after every association. This
allows the re-use of existing PTK and GTK.
•
With WPA2 PMK caching and VFF, the PMK cache is transferred as part of context transfer prior
to the authentication phase. This allows expedited handoffs to work for both intra- and
inter-controller roaming events.
•
A beacon/probe response that allows lightweight access point to indicate which controller it is
attached to so that reauthorization events only occur when needed, minimizing inter-controller
handoffs and thus reducing CPU usage.
•
Allows changes to lightweight access point sensitivity for pico cells.
•
Allows control of lightweight access point fallback behavior to optimize pico cell use.
•
Supports heat maps for directional antennas.
•
Allows specific control over blacklisting events
•
Allows configuring and viewing basic LWAPP configuration using the lightweight access point CLI.
Startup Wizard
When a controller is powered up with a new factory operating system software load or after being reset
to factory defaults, the bootup script runs the Startup Wizard, which prompts the installer for initial
configuration. The Startup Wizard:
•
Ensures that the controller has a System Name, up to 32 characters.
•
Adds an Administrative username and password, each up to 24 characters.
•
Ensures that the controller can communicate with the GUI, CLI, or Cisco WCS (either directly or
indirectly) through the service port by accepting a valid IP configuration protocol (none or DHCP),
and if none, IP Address and netmask. If you do not want to use the service port, enter 0.0.0.0 for the
IP Address and netmask.
•
Ensures that the controller can communicate with the network (802.11 Distribution System) through
the management interface by collecting a valid static IP Address, netmask, default router IP address,
VLAN identifier, and physical port assignment.
•
Prompts for the IP address of the DHCP server used to supply IP addresses to clients, the controller
management interface, and optionally to the service port interface.
•
Asks for the LWAPP Transport Mode, described in the
“Layer 2 and Layer 3 LWAPP Operation”
section on page 1-7
.
•
Collects the Virtual Gateway IP Address; any fictitious, unassigned IP address (such as 1.1.1.1) to
be used by Layer 3 Security and Mobility managers.
•
Allows you to enter the Mobility Group (RF Group) Name.
•
Collects the wireless LAN 1 802.11 SSID, or Network Name.
