Cisco Cisco IOS XE 3.5E
28
Release Notes for Catalyst 3850 Series Switch, Cisco IOS XE Release 3.2.xSE
OL-28114-04
Features
Local Auth
Local auth is an authentication method that allows
users and wireless clients to be authenticated
locally on the switch/controller. It is designed for
use in remote offices that want to maintain
connectivity to wireless clients when the backend
system becomes disrupted or the external
authentication server goes down.
users and wireless clients to be authenticated
locally on the switch/controller. It is designed for
use in remote offices that want to maintain
connectivity to wireless clients when the backend
system becomes disrupted or the external
authentication server goes down.
Internal DHCP Server
The controllers contain an internal DHCP server.
This server is typically used in branch offices that
do not already have a DHCP server. The internal
server provides DHCP addresses to wireless
clients.
This server is typically used in branch offices that
do not already have a DHCP server. The internal
server provides DHCP addresses to wireless
clients.
New Hierarchical Mobility
Allows a client to roam seamlessly between
AireOS controllers running the maintenance
Release 7.3.112.0 or Release 7.5 and Cisco
controllers running Cisco IOS Release 3.2.xSE.
AireOS controllers running the maintenance
Release 7.3.112.0 or Release 7.5 and Cisco
controllers running Cisco IOS Release 3.2.xSE.
Web GUI
A web browser, or graphical user interface (GUI),
is built into each controller. It allows multiple
users to simultaneously browse into the controller
HTTP or HTTPS (HTTP over SSL) management
pages to configure parameters and monitor the
operational status for the controller and its
associated access points.
is built into each controller. It allows multiple
users to simultaneously browse into the controller
HTTP or HTTPS (HTTP over SSL) management
pages to configure parameters and monitor the
operational status for the controller and its
associated access points.
AP Priority
During installation, we recommend that you
connect all lightweight access points to a
dedicated controller, and configure each
lightweight access point for final operation. This
step configures each lightweight access point for
a primary, secondary, and tertiary controller.
When sufficient controllers are deployed, if one
controller fails, active access point client sessions
are momentarily dropped while the dropped
access point associates with another controller,
which allows the client device to immediately
reassociate and reauthenticate.
connect all lightweight access points to a
dedicated controller, and configure each
lightweight access point for final operation. This
step configures each lightweight access point for
a primary, secondary, and tertiary controller.
When sufficient controllers are deployed, if one
controller fails, active access point client sessions
are momentarily dropped while the dropped
access point associates with another controller,
which allows the client device to immediately
reassociate and reauthenticate.
AP Priming
If the access point was previously associated to a
controller, the IP addresses of the primary,
secondary, and tertiary controllers are stored in
the access point's nonvolatile memory. This
process of storing controller IP addresses on an
access point for later deployment is called
priming the access point.
controller, the IP addresses of the primary,
secondary, and tertiary controllers are stored in
the access point's nonvolatile memory. This
process of storing controller IP addresses on an
access point for later deployment is called
priming the access point.
Table 9
Wireless Features (continued)
Feature
Description