Cisco Cisco 2000 Series Wireless LAN Controller Release Notes
14
Release Notes for Cisco Wireless LAN Controller and Cisco Lightweight Access Point for Release 3.1.105.0
OL-7431-03
Caveats
Caveats
This section lists open and closed caveats in operating system release 3.1.105.0 for Wireless LAN
Controllers and associated Cisco lightweight access points.
Controllers and associated Cisco lightweight access points.
Open Caveats
These caveats are open in operating system release 3.1.105.0:
•
CSCar13192—In Cisco 2000 Series Wireless LAN Controllers, the trap message for SNMP
authentication failure contains reversed IP address. If an SNMP query is made to a Cisco 2000 Series
Wireless LAN Controller, and if the query results in an authentication failure, the IP address of the
querying machine appears reversed on the trap log message.
authentication failure contains reversed IP address. If an SNMP query is made to a Cisco 2000 Series
Wireless LAN Controller, and if the query results in an authentication failure, the IP address of the
querying machine appears reversed on the trap log message.
•
CSCar13259—Clients are not excluded on Cisco Aironet 1030 remote edge lightweight access
points in REAP mode.
points in REAP mode.
•
CSCar13330—When using the web configuration wizard to complete the initial configuration on a
Cisco 2000 Series Wireless LAN Controller, on the RADIUS configuration page, after enabling the
server, an error message is returned saying “Error in enabling the server.”
Workaround: The RADIUS server may be enabled after the configuration wizard is complete and
the Wireless LAN Controller UI is in regular mode. To go to the RADIUS server details, click the
Security tab and then select RADIUS Authentication under the AAA menu. Then, click the edit link
for the RADIUS server entry. On the RADIUS edit page, enable the server state and click Apply.
Cisco 2000 Series Wireless LAN Controller, on the RADIUS configuration page, after enabling the
server, an error message is returned saying “Error in enabling the server.”
Workaround: The RADIUS server may be enabled after the configuration wizard is complete and
the Wireless LAN Controller UI is in regular mode. To go to the RADIUS server details, click the
Security tab and then select RADIUS Authentication under the AAA menu. Then, click the edit link
for the RADIUS server entry. On the RADIUS edit page, enable the server state and click Apply.
•
CSCei65293—The 5-GHz, RM-21A radio module on Cisco Aironet 1200 series lightweight access
points has an articulating antenna with a dual function: diversity omni or patch antenna. When the
antenna is folded flat to the access point housing it is in 9-dBi patch mode, and when it is in any
other position it is in 5-dBi omni mode. When you change the antenna position to switch antenna
modes you must reset the Cisco Aironet 1200 series lightweight access point to apply the change.
points has an articulating antenna with a dual function: diversity omni or patch antenna. When the
antenna is folded flat to the access point housing it is in 9-dBi patch mode, and when it is in any
other position it is in 5-dBi omni mode. When you change the antenna position to switch antenna
modes you must reset the Cisco Aironet 1200 series lightweight access point to apply the change.
•
CSCsa95763—The Wireless LAN Controller Web UI cannot display more than 80 local net users
on the page Security->AAA->Local Net Users.
Workaround: Use the Wireless LAN Controller CLI to view all the Local Net User entries.
on the page Security->AAA->Local Net Users.
Workaround: Use the Wireless LAN Controller CLI to view all the Local Net User entries.
•
CSCsb01980—When using the web configuration wizard on a Wireless LAN Controller, when the
operator enters incorrect data for the management interface, error messages are shown only at the
end of the wizard and thus the user must return to the management interface page for correction. The
data entered in the management interface page, such as the port number, is not validated
immediately but at the end of the wizard. As a result any error messages are shown only at the end.
Workaround: This issue can cause the user some inconvenience and the user may prefer to use the
CLI configuration wizard instead to avoid it.
operator enters incorrect data for the management interface, error messages are shown only at the
end of the wizard and thus the user must return to the management interface page for correction. The
data entered in the management interface page, such as the port number, is not validated
immediately but at the end of the wizard. As a result any error messages are shown only at the end.
Workaround: This issue can cause the user some inconvenience and the user may prefer to use the
CLI configuration wizard instead to avoid it.
•
CSCsb01983—The Wireless LAN Controller Web Configuration wizard is not reachable after
making repeated invalid entries for the management interface port.
When an operator connects to the Wireless LAN Controller Web Configuration wizard on address
192.168.1.1, and when the operator enters an invalid port number on the Management Interface
configuration page, at the end of the wizard, the operator is redirected to the management interface
page to correct the port. If the operator enters an incorrect port and submits, the configuration wizard
becomes inaccessible.
Workaround: Reboot the Wireless LAN Controller through the CLI to access the web wizard again.
making repeated invalid entries for the management interface port.
When an operator connects to the Wireless LAN Controller Web Configuration wizard on address
192.168.1.1, and when the operator enters an invalid port number on the Management Interface
configuration page, at the end of the wizard, the operator is redirected to the management interface
page to correct the port. If the operator enters an incorrect port and submits, the configuration wizard
becomes inaccessible.
Workaround: Reboot the Wireless LAN Controller through the CLI to access the web wizard again.
•
CSCsb09699—ACL rules with specified source or destination IP addresses are not working. For
instance, create a permit ACL with source as 20.0.0.11/255.255.255.255 and all other parameters as
any. The wireless client from this IP address is not able to ping the server.
instance, create a permit ACL with source as 20.0.0.11/255.255.255.255 and all other parameters as
any. The wireless client from this IP address is not able to ping the server.