Chapter 1 FAQs and Troubleshooting
Reports FAQs and Troubleshooting
Symptom After running a job, the updated data does not appear in a report.
Possible Cause A full polling cycle has not completed and the new data has not been entered in the database.
Recommended Action Verify that the polling cycle has completed as follows:
a.Select Admin > Appliance > Status > View Log File.
b.Click jobvm.log.
c.Scroll through the log to find the message: “Finished Inventory” for your particular job.
Symptom Email fails to arrive at its destination.
Possible Cause The SMTP server is not configured properly.
Recommended Action Configure the SMTP server by selecting Admin > Appliance > Configure Mailroute.
You can also Telnet or SSH to the WLSE and clear the send queue, the user queue, and the mail log and then send email to yourself. For example:
admin@mywlse: mailcontrl clear
admin@mywlse: mail to email_address
Symptom There is a time discrepancy in the scheduled email jobs.
Possible Cause The time is not set correctly on the WLSE.
Recommended Action
a.Reset the WLSE time to Universal Coordinated Time (UTC) using CLI commands as follows: Enter services stop to stop services.
Enter the clock command to reset the time. Enter services start to restart the services.
b.Set the time in local browser time, select Admin > Appliance > Time/NTP/Name.
Symptom No VLAN information is displayed for IOS access points.
Possible Cause WEP keys have not been configured in each VLAN. When the WEP keys are configured in the IOS access points, VLAN information is accessible by SNMP.
Recommended Action Configure the WEP keys for the corresponding VLAN.
Symptom There is a discrepancy in the first aggregation intervals after the first time the WLSE started up or after the WLSE’s software was upgraded.
For example, weekly data is displayed within 2 days of initial startup or upgrade, or the aggregation period began before the initial startup or upgrade.
FAQ and Troubleshooting Guide for the CiscoWorks Wireless LAN Solution Engine
|
| |
|
