Cisco Systems OL-8376-01 Ventilation Hood User Manual


 
1-10
FAQ and Troubleshooting Guide for the CiscoWorks Wireless LAN Solution Engine
OL-8376-01
Chapter 1 FAQs and Troubleshooting
Deployment Wizard Troubleshooting
Symptom After performing certain operations on the WLSE, such as clicking Apply in the Display Faults
page, then clicking the client browser Refresh button, a pop-up message is generated indicating that the
page cannot be refreshed.
Possible Cause The browser Refresh button was used.
Recommended Action Avoid using the Refresh button on the browser. Instead, use the navigational
tools provided by the WLSE user interface. If either of the following messages display, click
Cancel: on Internet Explorer, “The page cannot be refreshed without resending the information.
Click Retry to send the information again, or click Cancel to return to the page that you are trying
to view;” and on Firefox, “The page you are trying to view contains POSTDATA. If you resend the
data, any action the form carried out (such as search or online purchase) will be repeated. To resend
the data, click OK. Otherwise, click Cancel.
Symptom The Web interface of the WLSE is not available, but you can log in to the CLI.
Possible Cause The SNMP community file may be corrupted.
Recommended Action See the reset device-snmp command in the “Using CLI Commands” chapter
in the User Guide for the CiscoWorks Wireless LAN Solution Engine, Release 2.13 on Cisco.com.
This command is intended as a last resort and should be used with caution. Please read the command
description in the User Guide before using this command.
Deployment Wizard Troubleshooting
Symptom An error message displays when I try to access the Wizard.
Possible Cause You may not have the appropriate roles and privileges assigned to your login.
Recommended Action Select Admin > User Admin > Manage Roles, and make sure that both the
Wizard > WLSE Wizard and Configure > Auto Update options are checked.
Symptom An error message displays when I try to create an auto-managed configuration in the Deploy
Config screen.
Possible Cause The subnet that you selected is already used in another auto-managed configuration.
Someone may have deleted the configuration template by using the options under the Config tab,
but did not delete the related auto-managed configuration.
Recommended Action Delete the auto-managed configuration from the main Config tab (Configure
> Auto Updated > Auto-Managed Configuration).