Cisco Cisco 2106 Wireless LAN Controller
39
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.2.130.0
OL-31336-01
Caveats
•
CSCsq23766—A Hifn module installed on a controller running software release 4.2.61.126 might
not be initialized.
not be initialized.
Workaround: None.
•
CSCsq23968—When you configure the management user authentication priority order through
SNMP using the MIB browser, the controller allows you to configure an invalid priority order and
to remove all of the authentication methods from the list.
SNMP using the MIB browser, the controller allows you to configure an invalid priority order and
to remove all of the authentication methods from the list.
Workaround: None.
•
CSCsq25129—A controller software upgrade might fail with a Nessus scan running.
Workaround: None.
•
CSCsq26051—When a Cisco terminal server connects to the controller but the user is not logged in
through the console, the controller might hang after a reboot.
through the console, the controller might hang after a reboot.
Workaround: None.
Resolved Caveats
These caveats are resolved in controller software release 4.2.130.0.
•
CSCsd52483—If you use Option 3 from the controller’s boot menu to install a controller software
release or an ER.aes file, the bootup process halts, and the controller stops responding. The
controller also displays the “grub>” prompt on the console port. This problem affects the following
controllers: 2000 series, 2100 series, and the Controller Network Module.
release or an ER.aes file, the bootup process halts, and the controller stops responding. The
controller also displays the “grub>” prompt on the console port. This problem affects the following
controllers: 2000 series, 2100 series, and the Controller Network Module.
•
CSCsf23288—Some clients that are configured for WPA2 might send encrypted data immediately
after the four-way handshake. If this occurs before the encryption key gets plumbed on the access
point, a WEP decryption error might result.
after the four-way handshake. If this occurs before the encryption key gets plumbed on the access
point, a WEP decryption error might result.
•
CSCsj48872—After you upgrade the controllers in a Cisco WiSM from software release 4.0.206.0
to 4.1.171.0, both of the controllers may reboot repeatedly.
to 4.1.171.0, both of the controllers may reboot repeatedly.
•
CSCsj56899—The controller does not send the hostname or IP address in the syslog message
header, making it difficult to determine which controller sent the message.
header, making it difficult to determine which controller sent the message.
•
CSCsj95069—The web authentication login page on the 2106 controller does not have the Cisco logo.
•
CSCsk54969—A controller might stop redirecting wireless clients on a WLAN that uses web
authentication to the web authentication login page. When this problem occurs, the debug pm
ssh-engine enable command shows output similar to the following:
authentication to the web authentication login page. When this problem occurs, the debug pm
ssh-engine enable command shows output similar to the following:
Tue Apr 1 11:12:23 2008:
SshPmStMain/pm_st_main.c:1954/ssh_pm_st_main_batch_addition_result:Failed to add rule
to the engine: restoring old state
Tue Apr 1 11:12:23 2008:
SshEnginePmApiPm/engine_pm_api_pm.c:1896/ssh_pme_enable_policy_lookup: Could not
allocate message
Tue Apr 1 11:12:28 2008: SshPmRules/pm_rules.c:639/ssh_pm_rule_delete: Trying to
delete an unknown rule 43723
Tue Apr 1 11:12:28 2008: SshPmRules/pm_rules.c:639/ssh_pm_rule_delete:Trying to delete
an unknown rule 43724
Tue Apr 1 11:12:28 2008: SshPmRules/pm_rules.c:639/ssh_pm_rule_delete:Trying to delete
an unknown rule 43725
Tue Apr 1 11:12:29 2008:SshEnginePmApiPm/engine_pm_api_pm.c:1873/
ssh_pme_disable_policy_lookup:Could not allocate message
Browsing to https://1.1.1.1 does work. If browsing to this address does not work when you encounter
these symptoms, then you are not encountering this bug.
these symptoms, then you are not encountering this bug.