Summary of the content on the page No. 1
FAQ and Troubleshooting Guide for
the CiscoWorks Wireless LAN
Solution Engine
Release 2.5
Corporate Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 526-4100
Summary of the content on the page No. 2
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE
Summary of the content on the page No. 3
CONTENTS CHAPTER 1 FAQs and Troubleshooting 1-1 General FAQs and Troubleshooting 1-1 Faults FAQs and Troubleshooting 1-11 Devices FAQs and Troubleshooting 1-13 Configuration FAQs and Troubleshooting 1-19 Firmware FAQs and Troubleshooting 1-24 Reports FAQs and Troubleshooting 1-32 Radio Manager FAQs and Troubleshooting 1-36 Administration FAQs and Troubleshooting 1-43 CHAPTER 2 Fault Descriptions 2-1 Access Point Faults 2-2 WLSE Fault 2-20 AAA Server Faults 2-20 Switch Faults 2-25 Router Fault
Summary of the content on the page No. 4
Contents FAQ and Troubleshooting Guide for the CiscoWorks Wireless LAN Solution Engine iv
Summary of the content on the page No. 5
CH APTER 1 FAQs and Troubleshooting This FAQ and troubleshooting guide consists of the following sections: • General Questions—See General FAQs and Troubleshooting, page 1-1 Faults—Faults FAQs and Troubleshooting, page 1-11 Devices—Devices FAQs and Troubleshooting, page 1-13 Configuration—Configuration FAQs and Troubleshooting, page 1-19 Firmware—Firmware FAQs and Troubleshooting, page 1-24 Reports—Reports FAQs and Troubleshooting, page 1-32 Radio Manager —Radio Manager FAQs and Tr
Summary of the content on the page No. 6
Chapter 1 FAQs and Troubleshooting General FAQs and Troubleshooting Is Telnet enabled or disabled by default on the WLSE? Can SSH be disabled?, page 1-2 Can I run a job to convert a number of access points from non-IOS to IOS? What are the requirements for WLSE usernames and passwords? Q. Can several users be logged on and managing the same access point at once? A. Yes, several users can view data and reports on the same access point. More than one user can create configuration a
Summary of the content on the page No. 7
Chapter 1 FAQs and Troubleshooting General FAQs and Troubleshooting Q. Can I run a job to convert a number of access points from non-IOS to IOS? A. Yes, you can run a firmware job, using a special IOS upgrade image that is available on Cisco.com. For more information, see the firmware upgrade information in the online help or the User Guide for the CiscoWorks Wireless LAN Solution Engine, Release 2.5. Q. What are the requirements for WLSE usernames and passwords? A. Usernames can be up
Summary of the content on the page No. 8
Chapter 1 FAQs and Troubleshooting General FAQs and Troubleshooting Symptom After the WLSE reboots, the login screen appears, followed by an Internal Server Error message. Possible Cause The servlet engine in the WLSE is starting up. Recommended Action Wait for 20 to 30 seconds, then log in again. Symptom A search for an access point using APs Based on Client IP, displays the following message, “search yielded no results.” Possible Cause The device you are searching for is an IOS device
Summary of the content on the page No. 9
Chapter 1 FAQs and Troubleshooting General FAQs and Troubleshooting Symptom Cannot log into the system. Possible Cause You did not run the setup program to create an initial system configuration or you lost all the user account passwords. Recommended Action 1. Did you run the setup program after booting the system for the first time? If no, run the setup program. If yes, continue to the next step. 2. Do you know the password for any system user accounts? If no, see Cannot log in as a sys
Summary of the content on the page No. 10
Chapter 1 FAQs and Troubleshooting General FAQs and Troubleshooting 5. Enter the following command. This erases the WLSE’s configuration, returns the WLSE to factory defaults, and reloads the WLSE. [root@CiscoMaintImage/]# erase config Symptom After the WLSE starts up, the setup login prompt appears. Use the setup program. The WLSE cannot connect to the network. Possible Cause – The network cable is not connected to the Ethernet 0 port. – The Ethernet 0 interface is disabled or misconfi
Summary of the content on the page No. 11
Chapter 1 FAQs and Troubleshooting General FAQs and Troubleshooting If the ping command gets a response, the system is connected to the network. If the system cannot connect to a particular host, the problem is either with the network configuration or that host. Contact your network administrator for assistance. If the ping command does not get a response, continue. – Attempt to connect to another host on the same subnet as the system. If the ping command can connect to a host on the s
Summary of the content on the page No. 12
Chapter 1 FAQs and Troubleshooting General FAQs and Troubleshooting – If connecting via HTTP, the IP address was not appended with :1741. – The client system is not configured. Recommended Action 1. Make sure that the system can connect to the network. Attempt to connect the system using a Web browser. If you cannot connect, continue. 2. If you are attempting to connect via HTTP, verify that the IP address is appended with :1741. 3. If you are attempting to connect via HTTP, verify th
Summary of the content on the page No. 13
Chapter 1 FAQs and Troubleshooting General FAQs and Troubleshooting For more information on the reload command, see the CLI appendix in the User Guide for the CiscoWorks Wireless LAN Solution Engine, Release 2.5. You can access a PDF version of this guide by clicking View PDF in the WLSE’s online help. 10. If you still cannot connect to the system using a Web browser, contact Cisco’s Technical Assistance Center for assistance. Symptom The system time or date is incorrect. Possible Cau
Summary of the content on the page No. 14
Chapter 1 FAQs and Troubleshooting General FAQs and Troubleshooting Symptom Cannot connect to system with Telnet or Telnet interaction is slow. Possible Cause – Telnet is disabled or configured incorrectly. – The WLSE cannot recognize host names. If you are not using name recognition, slow or non-existent telnet interaction is an expected problem. Note Telnet is disabled by default. SSH is enabled by default. Recommended Action If the problem is not the network, perform the following ste
Summary of the content on the page No. 15
Chapter 1 FAQs and Troubleshooting Faults FAQs and Troubleshooting 4. Verify that the system can get DNS services from the network by entering the following command: # nslookup dns-name {hostname | ip-address} where dns-name is the DNS name of a host on the network that is registered in DNS and hostname and ip-address is the same IP address specified in 2. The command returns the IP address of the host. 5. If the system cannot resolve DNS names to IP addresses, the DNS server it is us
Summary of the content on the page No. 16
Chapter 1 FAQs and Troubleshooting Faults FAQs and Troubleshooting Q. Does acknowledging a fault clear it? A. No, it only removes it from the Active list. For a description of fault states, see the information on understanding fault states in the online help. Q. What traps are sent from the WLSE? A. Traps are sent based on fault policy and threshold settings on the WLSE. The WLSE only sends out v2c traps, so make sure your trap listener is configured to accept v2c traps. Solaris 2.8- b
Summary of the content on the page No. 17
Chapter 1 FAQs and Troubleshooting Devices FAQs and Troubleshooting 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 Administration > Appliance > Configure Mailroute. Symptom No VLAN fault 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 informati
Summary of the content on the page No. 18
Chapter 1 FAQs and Troubleshooting Devices FAQs and Troubleshooting Q. Why is hostname (device name), sysContact, and sysLocation information not updated in the WLSE after I change these parameters on the access point? A. The hostname (device name), sysContact, and sysLocation parameters are updated during discovery, not during inventory. Make sure you schedule a periodic discovery under Administration > Discover > Scheduled Discovery. Q. What is an invalid CDP seed? A. An invalid seed
Summary of the content on the page No. 19
Chapter 1 FAQs and Troubleshooting Devices FAQs and Troubleshooting Devices Troubleshooting This section contains the following troubleshooting information: Devices were discovered but are not displayed in the GUI; for example, in Reports. There is a time discrepancy in the scheduled discovery jobs. Devices are placed in Misconfigured Devices group after discovery and dot11mib fault is displayed. Access points are placed in Misconfigured Devices group even though they have been
Summary of the content on the page No. 20
Chapter 1 FAQs and Troubleshooting Devices FAQs and Troubleshooting a. Reset the WLSE system 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 local browser time. Select Administration > Appliance > Time/NTP/Name. Symptom Devices are placed in Misconfigured Devices group after discovery and dot11mib fault is displayed. Possible Cause IOS devices are not confi
