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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

watchdog reset in WLC 5508 7.4.100.60

Hi ,

Last week we found that primary WLC was hanged so we need to reboot it.

As per logs:

Last Reset....................................... Watchdog reset

We are using 7.4.100.60.

Any idea what could be the root cause.

Regards,

2 ACCEPTED SOLUTIONS

Accepted Solutions
Hall of Fame Super Silver

Re: watchdog reset in WLC 5508 7.4.100.60

Just to add...

Make sure you have upgraded the FUS since your on v7.4. You should be on at least FUS 1.8.0.0. There is also a newer FUS 1.9.0.0 but only required if your on v7.6.x. The FUS can be installed on v7.4 but optional.

http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/fus_rn_OL-31390-01.pdf

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***
VIP Purple

Re: watchdog reset in WLC 5508 7.4.100.60

Check your WLC serial number as well, if it starts FCW1614 or later then it may be due to this bug as well.

CSCul68057

Symptom:

Wireless LAN Controller may encounter unexpected reload without crash file or coredump.

Console log output may include "reaperWatcher rebooting" and "!!!!! Watchdog detected LOCKUP !!!!!",

and there may be "#OSAPI-2-REAPER_WATCHER_INFO" message in syslog.

Conditions:

5508, 2504 or WiSM2 manufactured after April 2012.

Affected S/N: FCW1614xxxx and later

This is due to incompatibility of previous driver with some of the flash components used after that date

Workaround:

None, upgrade to one of the recommended software versions

Anyway your choices are very limited now, only 3 WLC software codes supported by Cisco 7.0.250.0(7.0MR5), 7.4.121.0 (7.4MR2) and 7.6.101.x(7.6MR1). So upgrade to 7.4.121.0 code as that is the highly recommended code at the moment. See below for more details

https://supportforums.cisco.com/docs/DOC-40178

I would suggest to go for FUS 1.9.0.0 as well.

HTH

Rasika

*** Pls rate all useful responses ****

4 REPLIES
VIP Purple

Re: watchdog reset in WLC 5508 7.4.100.60

must be hitting a bug: CSCug65454

Upgrade to version 7.4.121.0

Regards

Dont forget to rate helpful posts

Hall of Fame Super Silver

Re: watchdog reset in WLC 5508 7.4.100.60

Just to add...

Make sure you have upgraded the FUS since your on v7.4. You should be on at least FUS 1.8.0.0. There is also a newer FUS 1.9.0.0 but only required if your on v7.6.x. The FUS can be installed on v7.4 but optional.

http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/fus_rn_OL-31390-01.pdf

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***
VIP Purple

Re: watchdog reset in WLC 5508 7.4.100.60

Check your WLC serial number as well, if it starts FCW1614 or later then it may be due to this bug as well.

CSCul68057

Symptom:

Wireless LAN Controller may encounter unexpected reload without crash file or coredump.

Console log output may include "reaperWatcher rebooting" and "!!!!! Watchdog detected LOCKUP !!!!!",

and there may be "#OSAPI-2-REAPER_WATCHER_INFO" message in syslog.

Conditions:

5508, 2504 or WiSM2 manufactured after April 2012.

Affected S/N: FCW1614xxxx and later

This is due to incompatibility of previous driver with some of the flash components used after that date

Workaround:

None, upgrade to one of the recommended software versions

Anyway your choices are very limited now, only 3 WLC software codes supported by Cisco 7.0.250.0(7.0MR5), 7.4.121.0 (7.4MR2) and 7.6.101.x(7.6MR1). So upgrade to 7.4.121.0 code as that is the highly recommended code at the moment. See below for more details

https://supportforums.cisco.com/docs/DOC-40178

I would suggest to go for FUS 1.9.0.0 as well.

HTH

Rasika

*** Pls rate all useful responses ****

New Member

Hi Rasika,We have this

Hi Rasika,

We have this problem too. 

Last reset by watchdog reset. But we are using 7.3.112.0 that known fixed release on bug CSCul68057.

Any idea what the problem?

 

Regards,

818
Views
15
Helpful
4
Replies