Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

4402 with latest 5.148 crashes on debug client command

I can reproduce system crash/reset at will when I turn on the debug client command.

Sun Apr 6 04:03:10 2008: 00:16:41:a8:58:9f 0.0.0.0 DHCP_REQD (7) Deleted mobile LWAPP rule on AP [00:00:00:00:00:00]

Sun Apr 6 04:03:10 2008: 00:16:41:a8:58:9f Deleting mobile on AP 00:00:00:00:00:00(0)

Sun Apr 6 04:03:10 2008: 00:16:41:a8:58:9f 0.0.0.0 Removed NPU entry.

Sun Apr 6 04:03:10 2008: 00:16:41:a8:58:9f Adding mobile on Wired Guest 00:00:00:00:00:00(0)

Sun Apr 6 04:03:15 2008: 00:16:41:a8:58:9f apfMsExpireCallback (apf_ms.c:433) Expiring Mobile!

Read from remote host usce02wc.net: Connection reset by peer

14 REPLIES
Silver

Re: 4402 with latest 5.148 crashes on debug client command

These outputs do not give an idea on the root cause of the WLC crash. Are these the only outputs present in the crash log? Can you post the complete crash log information from the WLC? That will give some insight to identify the issue.

Community Member

Re: 4402 with latest 5.148 crashes on debug client command

Yes thanks here is the crash log.....

Hall of Fame Super Silver

Re: 4402 with latest 5.148 crashes on debug client command

If you can reproduce this, then you should open a TAC case and have them look into this.... unless they already know about this:)

-Scott
*** Please rate helpful posts ***
Community Member

Re: 4402 with latest 5.148 crashes on debug client command

TAC wont let me open a case becasue my smartnet expired a few weeks ago. That's why I am here!

Hall of Fame Super Silver

Re: 4402 with latest 5.148 crashes on debug client command

I understand. Well there are issues with the 5 code and NPU errors and reboots with the WiSM's. Never heard if there are issues with the 4402 or 4404's, but no fix as of yet as what I know.

-Scott
*** Please rate helpful posts ***
Community Member

Re: 4402 with latest 5.148 crashes on debug client command

OK, thanks ... just wanted to warn others about this. It's really frustrating as this is one of the more useful debug commands.

Hall of Fame Super Silver

Re: 4402 with latest 5.148 crashes on debug client command

The most reliable code I think is 4.1.185. $.2 has issues but will be trying the 4.2.112 since 4.2 is required by the 1252 ap's. Haven't heard any good experiences yet with 5, but there must be others that haven't had issues with 5.

-Scott
*** Please rate helpful posts ***
Community Member

Re: 4402 with latest 5.148 crashes on debug client command

Well, I have the same version 5.0.148 and recently my 4404WLC crashed, it rebooted automatically.

Any ideas?

Hall of Fame Super Silver

Re: 4402 with latest 5.148 crashes on debug client command

5.0 has soo many issues in my mind. Youare better off to down grade to 4.2.

-Scott
*** Please rate helpful posts ***
Community Member

Re: 4402 with latest 5.148 crashes on debug client command

I agree. If you require stability on your WLAN DO NOT USE 5.148 code. I am only running it in the lab for now. After a couple of days the 4402 with 5.148 starts sending SNMP traps with "TRACEBACK" errors. The only way to get this to stop is to reboot the WLC.

Community Member

Re: 4402 with latest 5.148 crashes on debug client command

There should be a 5.1 version out .... rsn.

I _am_ running 5.0.148 on 6 wisms and since downgrading is a drag ....

Hall of Fame Super Silver

Re: 4402 with latest 5.148 crashes on debug client command

Even when the 5.1 comes available, I wouldn't be the first to test it. Now that they are combining the mesh train into it, i would think it would be worse..... well at least the first couple versions.

-Scott
*** Please rate helpful posts ***
Community Member

Re: 4402 with latest 5.148 crashes on debug client command

Anyone see this on the 5.148 code ? It starts after 2 days and you have to reboot to clear it.

Jul 1 13:21:09 armonk usce02wc e3-net-00001 - ERROR (local0.alert - Traceback: 100e9828 100ea138 10100410 1038c32c 10c060e4 10d744f8) 11

Jul 1 13:21:09 armonk usce02wc e3-net-00001 - ERROR (local0.alert - Traceback: 100e9828 100ea138 10100410 1038c32c 10c060e4 10d744f8) 11

Jul 1 13:21:09 armonk usce02wc e3-net-00001 - ERROR (local0.alert - Traceback: 100e9828 100ea138 10100410 1038c32c 10c060e4 10d744f8) 11

Jul 1 13:21:09 armonk usce02wc e3-net-00001 - ERROR (local0.alert - Traceback: 100e9828 100ea138 10100410 1038c32c 10c060e4 10d744f8) 11

Jul 1 13:21:08 armonk usce02wc e3-net-00001 - ERROR (local0.alert - Traceback: 100e9828 100ea138 10100410 1038c32c 10c060e4 10d744f8) 11

Jul 1 13:21:08 armonk usce02wc e3-net-00001 - ERROR (local0.alert - Traceback: 100e9828 100ea138 10100410 1038c32c 10c060e4 10d744f8) 11

Jul 1 13:21:08 armonk usce02wc e3-net-00001 - ERROR (local0.alert - Traceback: 100e9828 100ea138 10100410 1038c32c 10c060e4 10d744f8) 11

Jul 1 13:21:08 armonk usce02wc e3-net-00001 - ERROR (local0.alert - Traceback: 100e9828 100ea138 10100410 1038c32c 10c060e4 10d744f8) 11

Community Member

Re: 4402 with latest 5.148 crashes on debug client command

Didn't look for it, but on a recent TAC case about crap that wasn't working in 5.148 I was instructed to go back to 4.2.130. Which is better, but still goofy.

283
Views
0
Helpful
14
Replies
CreatePlease to create content