Cisco Cisco 2106 Wireless LAN Controller Release Notes
13
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.2.61.0
OL-31336-01
New Features
•
Peer-to-peer blocking—In controller software release 4.2, peer-to-peer blocking is applied to
individual WLANs, and each client inherits the peer-to-peer blocking setting of the WLAN to which
it is associated. You can configure client traffic on the same WLAN to be bridged locally within the
controller, dropped by the controller, or forwarded to the upstream VLAN. This feature is not
applicable to the wired guest access feature.
individual WLANs, and each client inherits the peer-to-peer blocking setting of the WLAN to which
it is associated. You can configure client traffic on the same WLAN to be bridged locally within the
controller, dropped by the controller, or forwarded to the upstream VLAN. This feature is not
applicable to the wired guest access feature.
Note
The GUI option and CLI command to enable or disable peer-to-peer blocking globally have
been removed from the software in favor of this new, more flexible feature.
been removed from the software in favor of this new, more flexible feature.
•
QoS roles—In order to prevent guest users from using the same level of bandwidth as regular users,
you can create QoS roles with different (and presumably lower) bandwidth contracts and assign
them to guest users.
you can create QoS roles with different (and presumably lower) bandwidth contracts and assign
them to guest users.
•
Splash pages—In controller software releases prior to 4.2, a default login page appears when a
client associates to a WLAN using web authentication.This page, which is the same for every
WLAN, allows users to enter their credentials. In controller software release 4.2, you can use the
splash page feature to display different login pages for different WLANs. For example, different
departments within an organization might want to display login pages with their own logo, message,
and so on. When you enable web authentication for a wired or wireless guest access WLAN, you
can choose to override the global authentication configuration set on the Web Login page (using the
Override Global Config parameter) and choose one of the following web login pages for wired or
wireless guest users: the default web login page for the controller, a custom web login page that is
downloaded to the controller, or a web login page from an external server.
client associates to a WLAN using web authentication.This page, which is the same for every
WLAN, allows users to enter their credentials. In controller software release 4.2, you can use the
splash page feature to display different login pages for different WLANs. For example, different
departments within an organization might want to display login pages with their own logo, message,
and so on. When you enable web authentication for a wired or wireless guest access WLAN, you
can choose to override the global authentication configuration set on the Web Login page (using the
Override Global Config parameter) and choose one of the following web login pages for wired or
wireless guest users: the default web login page for the controller, a custom web login page that is
downloaded to the controller, or a web login page from an external server.
•
Syslog server—You can configure the syslog facility for sending syslog messages to a remote host
and set the severity level for filtering the syslog messages.
and set the severity level for filtering the syslog messages.
•
Wired guest access—This feature enables guest users to connect to the guest access network from
a wired Ethernet connection designated and configured for guest access. Wired guest access ports
might be available in a guest office or through specific ports in a conference room. Like wireless
guest user accounts, wired guest access ports are added to the network using the lobby ambassador
feature. Wired guest access can be configured in a standalone configuration or in a dual-controller
configuration that uses both an anchor controller and a foreign controller. This latter configuration
is used to further isolate wired guest access traffic but is not required for deployment of wired guest
access.
a wired Ethernet connection designated and configured for guest access. Wired guest access ports
might be available in a guest office or through specific ports in a conference room. Like wireless
guest user accounts, wired guest access ports are added to the network using the lobby ambassador
feature. Wired guest access can be configured in a standalone configuration or in a dual-controller
configuration that uses both an anchor controller and a foreign controller. This latter configuration
is used to further isolate wired guest access traffic but is not required for deployment of wired guest
access.
Note
Although wired guest access is managed by anchor and foreign anchors when two
controllers are deployed, mobility is not supported for wired guest access clients. In this
case, DHCP and web authentication for the client are handled by the anchor controller.
controllers are deployed, mobility is not supported for wired guest access clients. In this
case, DHCP and web authentication for the client are handled by the anchor controller.
Note
Wired guest access is supported only on the following controllers: 4400 series controllers,
the Cisco WiSM, and the Catalyst 3750G Integrated Wireless LAN Controller Switch.
the Cisco WiSM, and the Catalyst 3750G Integrated Wireless LAN Controller Switch.
New CCXv5 Features
•
Diagnostic channel—This feature enables you to troubleshoot problems regarding client
communication with a WLAN. The client and access points can be put through a defined set of tests
in an attempt to identify the cause of communication difficulties the client is experiencing and then
allow corrective measures to be taken to make the client operational on the network.
communication with a WLAN. The client and access points can be put through a defined set of tests
in an attempt to identify the cause of communication difficulties the client is experiencing and then
allow corrective measures to be taken to make the client operational on the network.