Filter
Top Products
1-26
FAQ and Troubleshooting Guide for the CiscoWorks Wireless LAN Solution Engine
OL-8376-01
Chapter 1 FAQs and Troubleshooting
Configuration FAQs and Troubleshooting
Symptom A configuration job fails using a template imported from an IOS access point.
Possible Cause It has commands such as power local 100 that cause it to fail.
Recommended Action Check the job log to see which commands failed; remove the commands from
the template using the Custom Values screen; then save the template and rerun the configuration job.
Symptom The banner command in an IOS custom template fails or is incomplete.
Possible Cause The banner command fails because it contains 240 or more characters.
Possible Cause A delimiter in the banner string, can cause a partial banner to be applied to the device.
For example,
if the following command is typed in the custom template using the letter “c” as the delimiter:
banner motd c This is to check banner c, the following is displayed when previewed: “banner
motd c This is to c.
” The banner displays incorrectly because there is a word in the banner
(check) that begins with the same character used as the delimiter.
Recommended Action Use less than 240 characters in the banner string, and do not use characters for
delimiters if the characters are also used in the text of the banner.
Symptom An IOS template job failed.
Possible Cause The template has the hostname configured instead of the IP address, and the DNS
name resolution is not configured correctly on the access point.
Recommended Action Use the IP address or configure the DNS name correctly on the access point.
Symptom Configuration jobs fail because the Telnet/SSH credentials are not valid, even though
credentials have been entered on the WLSE.
Possible Cause The credentials entered on the WLSE do not exactly match the data entered in
Devices > Discovery > Device Credentials > Telnet/SSH User/Password.
Recommended Action Make sure that the Telnet/SSH credentials data entered on the WLSE show the
correct device login response. Match the device login sequence with the credential fields, as shown
in Symptom Firmware jobs fail because the Telnet/SSH credentials are not valid., page 1-30.
Symptom Access points do not get the expected configuration applied from an auto-managed
configuration template.
Possible Cause An auto-managed configuration template exists that is assigned to meet other
matching criteria.
Recommended Action Check the matching criteria by selecting Configure > Auto Update >
Auto-Managed Configuration > Assign Templates.