Примечания к выпуску для Cisco Cisco 2106 Wireless LAN Controller

<td colspan="2"><input type="button" name="Submit" value="Submit" class="button" 

onclick="submitAction();"> </td> </tr> </table> </div>

</form>

</body>

</html>

This section lists 

 and 

 for Cisco controllers and lightweight access 

points.

These caveats are open in controller software release 4.2.207.0.

These caveats are open in controller software release 4.2.207.0 and have a severity of 1 or 2.

CSCsg66040—After a software upgrade, controllers might experience intermittent access to the 
management interface through HTTPS.

Workaround: Follow these steps to workaround the issue:

Make sure HTTPS is enabled on the controller’s management interface, reboot the controller 
from the CLI, and monitor the last service if error messages appear after the controller prompts 
you to enter a username and password to login.

Login with the relevant credentials and reconfigure the virtual interface with this CLI command:

Reboot the controller and make sure the Secure Web service shows up as OK.

Generate a certificate using this CLI command:

Click Yes when prompted and wait a few minutes for the certificate to generate.

Reboot the controller.

CSCsh93279—The 1000 series access points do not consistently forward probe requests to the 
controller.

Workaround: None.

CSCsj67447—When you use the controller GUI to modify an existing (or newly created) guest LAN 
and you choose an ingress interface that is already in use, no error appears. The error that appears 
on the CLI should also appear on the GUI: “Ingress interface is in use by some other guest lan.”

Workaround: None.

CSCsk68117—U-APSD state changes on a client device are not updated on the controller.

Workaround: Reboot the access point, or disassociate the client from the controller and then 
reassociate it.