Q. We see this syslog message broadcast on our network. Why does this
occur, and how do we stop it?
AP:001f.ca26.bfb4: %LWAPP−3−CLIENTERRORLOG: Decode Msg: could not match WLAN <id>
A. This error message is generated by LAPs on the network when a WLAN override is
configured for a WLAN, but that particular WLAN is not advertised through the LAP.
Configure config ap syslog host global 0.0.0.0 to stop it, or use a specific IP address if you
have a syslog server.
Q. I have problems when I upgrade my AP using the TFTP server. Every
time I try to upgrade, it adds a .tar extension to the upgrade image file
c1200−k9w7−tar.default, which cause the AP not to recognize the file. I
could not find a way to get rid of the additional .tar extension. (I
downloaded and tried both solarwind and tftpd32.) What should I do to
eliminate this issue?
A. The problem could be that the Operating System is hiding the known file type. Go to My
Computer. Click Tools > Folder Options > View, scroll down until you find the parameter
Hide extensions for known file types, and uncheck the box. This should eliminate the issue.
Q. My Access Points often encounter a "high CPU utilization" alarm
message. In such cases, a hardware reboot gets the Access Point back
into working condition. How can I overcome this issue?
A. There are several reasons for Access Points to reach "high CPU utilization."
If the Cisco Access Point (AP) is connected to the network through a switch,
sometimes "high CPU utilization" is observed on the AP. This is because, by default,
all the VLANs are allowed onto the AP from the switch to which the AP is
connected. This can create a problem, especially when applied to a huge network. If
all the VLANs are allowed onto the AP, it can result in high CPU utilization, and the
connectivity can be affected. Clients associated to the Access Point face throughput
issues, and sometimes high CPU utilization can also bring the Wireless network
down.
In order to avoid this problem, prune the VLANs at the switch so that only the VLAN
traffic in which the AP is interested is passed through the AP.
♦
If the Access Points are configured with loopback interfaces, sometimes "high CPU
utilization" is observed on the AP. Although loopback interfaces can be configured
on the Cisco AP, they are not supported on the AP, so they must not be configured. It
is advised to remove the loopback interfaces if they are configured on the AP.
Note: APs and bridges do not support the interface loopback command.
♦
As a first step in troubleshooting this issue, issue the show process cpu command in the AP.
This gives you an idea of what processes use the CPU.
Also, if the AP runs a version earlier than 12.3(2)JA2, upgrade it to version 12.3(2)JA2
because there is a known issue in earlier versions where service requests killed the CPU.
(100 Seiten)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Kommentare zu diesen Handbüchern