11-04-2013 04:23 AM
Hi,
I bought nearly a year ago two WAP321 and I'm having some problems with one of them. A couple of months ago I bought a WAP121 to increase coverage area of my WAP321 and I set up a WDS between 321 and 121. It works fine and the interfaces are up. The problem is that between 2 days to a couple of weeks, the WAP321 crashes and wds link goes down, and Ethernet so does. (Ethernet is active but no response to ping is given and web cli doesn't responds too). The only way to solve this is restarting the AP.
The topology is the following
CISCO SG300 -----------(trunk)------------DLINK-----------ADSL ->Internet
| |
| |
| |
| |
| |
WAP321 <- (this one crashes) WAP321
|
|
|(WDS)
|
WAP121
I tried multiple versions of the software. I'm currently with 1.0.3.4. I have the feeling that is more stable than 1.0.4.2. With both versions, the same problem.
Also notice that there are 2 VLANs on the network.
Here is an extract from the crash dump:
crashdumps:
crashdump1:
Software Version: 1.0.3.4
Crash Log:
Uptime of the AP: 0 Days, 10 Hours, 25 Minutes and 23 Seconds
CPU Unable to handle kernel paging request for process = swapper and pid = 0
epc == c0518fe0, ra == c054d604
Stack Trace:
[<00000000c054d604>] - wlc_scbfree+0xe8/0x3b4 [wl]
[<00000000c054e0d0>] - wlc_userscb_alloc+0x2c8/0x2d0 [wl]
[<00000000c054e87c>] - wlc_scblookup+0x11c/0x1c0 [wl]
[<00000000c057c024>] - wlc_ap_authresp+0x68c/0x9d0 [wl]
[<00000000c0535264>] - wlc_recvctl+0x1158/0x28b8 [wl]
[<00000000c0676ae4>] - wlc_recv+0x5f8/0x808 [wl]
[<00000000c067f7f8>] - wlc_dpc+0x6c8/0xb30 [wl]
[<00000000c06794c0>] - wl_dpc+0x50/0x164 [wl]
[<000000008002f09c>] - tasklet_action+0x70/0xf4
[<000000008002ea20>] - __do_softirq+0x80/0x110
[<000000008002eb18>] - do_softirq+0x68/0x70
crashdump2:
Software Version: 1.0.3.4
Crash Log:
Uptime of the AP: 0 Days, 14 Hours, 47 Minutes and 50 Seconds
CPU Unable to handle kernel paging request for process = swapper and pid = 0
epc == c0518fe0, ra == c054d604
Stack Trace:
[<00000000c054d604>] - wlc_scbfree+0xe8/0x3b4 [wl]
[<00000000c054e0d0>] - wlc_userscb_alloc+0x2c8/0x2d0 [wl]
[<00000000c054e87c>] - wlc_scblookup+0x11c/0x1c0 [wl]
[<00000000c057c024>] - wlc_ap_authresp+0x68c/0x9d0 [wl]
[<00000000c0535264>] - wlc_recvctl+0x1158/0x28b8 [wl]
[<00000000c0676ae4>] - wlc_recv+0x5f8/0x808 [wl]
[<00000000c067f7f8>] - wlc_dpc+0x6c8/0xb30 [wl]
[<00000000c06794c0>] - wl_dpc+0x50/0x164 [wl]
[<000000008002f09c>] - tasklet_action+0x70/0xf4
[<000000008002ea20>] - __do_softirq+0x80/0x110
[<000000008002eb18>] - do_softirq+0x68/0x70
Thanks in advance,
Àlex Roig
12-07-2013 07:49 AM
Hello Alex,
did you ever solve your crash problem on the WAP321? I'm asking because I just bought two brand new WA321, and both of them have crash dumps, and beside they are not stable: somtimes I can't ping then over the LAN and the wireless connection is not possible (even though I can see the SSID being broacasted).
Maybe we have a setup in common which could explain this behaviour? I also have setup two VLANs, one for the management interface, another one for the Wireless clients. I also de-activated the untagegd VLAN 1. I don't use WDS.
The WAP are runing the latest avaialble firmware,1.0.4.2.
Sincerely,
Nicolas
12-08-2013 02:52 PM
Hi Nicolas,
I still have problems with one of my WAP321. I haven't discovered anything else so far. What I have observed the last days, is that the AP restarts itself after crash or whatever. A couple times I have logged in the web interface I have seen uptime around 5 hours with noone having restarted the AP. Really strange.
The one that runs properly, is at version 1.0.4.2 and I've had any problems with it. Their configuration is the same except from the WDS.
There's quite a lot of people with similar problems. Hope that Cisco solves this via software update the sooner. The last software version dates from August...
I will have to do a bigger deployment and I'm seriously thinking to go with Aironet 1600. They are much more expensive but its stability and performance should be better. I don't want to have stability problems and this Small Business series are giving me too much headache.
This holidays I will have time to do some different tests to the AP and try do discover what makes it crash. I'll post everything relevant I find! If someone knows something, please, help!
Sincerely,
Àlex Roig
12-09-2013 01:03 AM
Hi Alex,
thanks for your response.
Well I am not using WDS at all on both of my devices, so for me I think WDS is not the isssue.
But right now the WAP are freezed, impossible to do anything but reboot them (after two days of uptime)!
Would you mind to share your configuration (the config.xml file you get after an export on the working WAP) without the passwords so I can compare our settings?
Thanks.
Nicolas
12-09-2013 01:23 AM
12-09-2013 03:00 AM
Thanks Alex, I did some comparison, and here are the settings which are different:
75
60
up
0
1
up
bg-n
on
up
off
down
off
down
down
wlan0
down
0
down
no
I might try to do a factory reset on the device and start with a new configuration to see if it changes anything. I already did that but then I uploaded my backup configuration file config.xml.
I'll keep you posted.
Nicolas
12-09-2013 04:45 AM
By the way, I did some searching on the forum, check the following issues (in case you dind't see them so far):
https://supportforums.cisco.com/message/4112119
https://supportforums.cisco.com/message/3973182
Nicolas
12-09-2013 03:51 PM
Thanks for this!
I saw it time ago but didn't tried it. I didn't thought that this could be the cause of the problem. Right now, 2 hours and 45 minutes uptime. I'll see tomorrow morning if it's still stable!
About the differences in the config, I don't really think that this can lead to a problem...
Did you succeeded enabling the native VLAN?
Alex Roig
12-10-2013 01:10 AM
Well so far so good:
WAP1: System Uptime: 0 days, 18 hours, 37 minutes
WAP2: System Uptime: 0 days, 18 hours, 38 minutes
I have just checked the checkbox "Untagged VLAN" with the defaults. I'm not using this VLAN 1 anyway. I have setup a "Management VLAN ID" with ID 100.
I'll check tomorrow again
12-10-2013 01:20 AM
It seems to work fine for me: 12 hours system uptime
I'll check it tonight again!
12-13-2013 03:55 AM
Hi!
How is it going on?
I think that untagged vlan was the problem. Still stable right now!
If it's stable a week more, I'll update firmware to the lastest version.
Hope yours are working well.
Àlex Roig
12-22-2013 04:44 AM
Hi Alex,
the AP is working pretty fine by now:
System Uptime: 10 days, 21 hours, 39 minutes
I had a response from the support team, apparently they escalated the issue to the level 2 support team.
Let's see if a new firmware will come next ...
Feliz navidad !
Nicolas
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide