WLC crash troubleshooting

[Rps-Cheers]

Hi everyone,

i have problem that is about WLC crash.what information should I collect when a WLC crash,or a WLC automatically restart?

Is there any command to get some logs,in order to we can know what reason about the issues?

thanks 

BR

Moments

[Scott Fella]

There is a crash file that is stored and can be exported. This is what TAC will ask for if you open a case.

Search for WLC crash file or WLC crash log:

https://supportforums.cisco.com/t5/wireless-mobility-documents/how-to-find-amp-retrieve-wlc-s-crash-coredump-from-its-s-flash/ta-p/3145554

[Rps-Cheers]

Hi Scott，

the wlc don't buy cisco service，so i cannot open a tac case.I just troubleshoot it by myself.

thanks for your help.Is there any other information？

[Scott Fella · Accepted solution]

You can look at the crash file/log and it should state why the crash happened. Then you just google the crash and see what others have posted about it. That is the best way.

[Rps-Cheers]

haha、ok，thanks for your help ^_^

[Leo Laohoo]

There are two WLC files needed: crashinfo and core dump.

[Rps-Cheers]

HI Leo; I have collect the show tech of WLC，i found there are some info as below: -------------------------------------------------------- Beginning of Crash File: mwar_dump2.crash -------------------------------------------------------- 0x4090e8 0x20218e0 0x2021897 0x409691 0x118fd89 0x118ff05 0x40b33a 0xf28393 0x201d32f 0x20b4369 ************************************************************ * Start Cisco Crash Handler Serv * ************************************************************ Sys Name: QX_WLC_Master Model: AIR-CT5520-K9 Version: 8.2.151.0 Timestamp: Mon Jun 11 19:53:39 2018 SystemUpTime: 205 days 19 hrs 56 mins 9 secs pid: 4354 TID: 1050912512 Task Name: TempStatus Reason: Reaper Reset BsnTime :17352860 MON(R) Tick: 1776399 2018-06-11 11:53:38.865954 MON(R) ExitTick: 1776373 MON(RW) Tick: 592656 2018-06-11 11:53:16.461958 MON(R) Trigger: 2 MON(R) State: 105 Long time taken timer call back information: Time Stamp: Sat Nov 18 12:57:24 2017 timer cb: 0x63be60 ('Unknown') Duration : 1000000 usecs, cbCount= 6 Timer Current Time :17352860 secs ------------------------------------------------------------ Analysis of Failure: Software was stopped by the reaper for the following reason: Reaper Reset: Task "TempStatus" missed software watchdog ------------------------------------------------------------ i think it maybe hit a bug which is CSCuw80627 https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuw80627 Do you think so?

[Leo Laohoo · Accepted solution]

That looks like it.
Raise a TAC Case to get this confirmed and for TAC to provide advisory as to what version fixes this bug. It looks like a memory leak.

[Rps-Cheers]

OK，thanks