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. And see here for current known issues.

New Member

Updated WLCs shows wierd log messages and most APs do not associate

Hi, I recently updated my 4402 WLC to latest Software Version                 (7.0.98.0).

This first seamed to have worked fine. WLCs rebooted fine, then APs rebooted and upgraded their software images.

All fine as it seamed.

The I went on to also upgrade to latest Emergency Image Version(5.2.157.0).

After rebooting the WLCs most APs won't associate again.

Logs from WLCs shows a lot of messages like:

---

Oct  7 20:11:38 wlc-1 WLC-1: *mmListen: Oct 07 22:11:38.857: %MM-3-INVALID_PKT_RECVD: mm_listen.c:6691 Received an invalid packet from 192.168.128.18. Source member:0.0.0.0. source member unknown.
Oct  7 20:11:38 wlc-1 WLC-1: *mmListen: Oct 07 22:11:38.857: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
Oct  7 20:11:38 wlc-1 WLC-1: -Traceback:  105fbe18 102cb318 105f3ab0 10c0d250 111cd0cc
Oct  7 20:11:38 wlc-1 WLC-1:
Oct  7 20:11:38 wlc-1 WLC-1: *mmListen: Oct 07 22:11:38.857: %MM-3-INVALID_PKT_RECVD: mm_listen.c:6691 Received an invalid packet from 192.168.128.18. Source member:0.0.0.0. source member unknown.
Oct  7 20:11:38 wlc-1 WLC-1: *mmListen: Oct 07 22:11:38.857: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
Oct  7 20:11:38 wlc-1 WLC-1: -Traceback:  105fbe18 102cb318 105f3ab0 10c0d250 111cd0cc
Oct  7 20:11:38 wlc-1 WLC-1:
Oct  7 20:11:39 wlc-1 WLC-1: *mmListen: Oct 07 22:11:39.749: %MM-3-INVALID_PKT_RECVD: mm_listen.c:6691 Received an invalid packet from 192.168.128.18. Source member:0.0.0.0. source member unknown.
Oct  7 20:11:39 wlc-1 WLC-1: *mmListen: Oct 07 22:11:39.749: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
Oct  7 20:11:39 wlc-1 WLC-1: -Traceback:  105fbe18 102cb318 105f3ab0 10c0d250 111cd0cc
Oct  7 20:11:39 wlc-1 WLC-1:
Oct  7 20:11:39 wlc-1 WLC-1: *mmListen: Oct 07 22:11:39.749: %MM-3-INVALID_PKT_RECVD: mm_listen.c:6691 Received an invalid packet from 192.168.128.18. Source member:0.0.0.0. source member unknown.
Oct  7 20:11:39 wlc-1 WLC-1: *mmListen: Oct 07 22:11:39.749: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
Oct  7 20:11:39 wlc-1 WLC-1: -Traceback:  105fbe18 102cb318 105f3ab0 10c0d250 111cd0cc
Oct  7 20:11:39 wlc-1 WLC-1:
Oct  7 20:11:40 wlc-1 WLC-1: *mmListen: Oct 07 22:11:40.749: %MM-3-INVALID_PKT_RECVD: mm_listen.c:6691 Received an invalid packet from 192.168.128.18. Source member:0.0.0.0. source member unknown.
Oct  7 20:11:40 wlc-1 WLC-1: *mmListen: Oct 07 22:11:40.749: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
Oct  7 20:11:40 wlc-1 WLC-1: -Traceback:  105fbe18 102cb318 105f3ab0 10c0d250 111cd0cc
Oct  7 20:11:40 wlc-1 WLC-1:
Oct  7 20:11:40 wlc-1 WLC-1: *mmListen: Oct 07 22:11:40.749: %MM-3-INVALID_PKT_RECVD: mm_listen.c:6691 Received an invalid packet from 192.168.128.18. Source member:0.0.0.0. source member unknown.
Oct  7 20:11:40 wlc-1 WLC-1: *mmListen: Oct 07 22:11:40.749: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
Oct  7 20:11:40 wlc-1 WLC-1: -Traceback:  105fbe18 102cb318 105f3ab0 10c0d250 111cd0cc
Oct  7 20:11:40 wlc-1 WLC-1:
Oct  7 20:11:40 wlc-1 WLC-1: *osapiReaper: Oct 07 22:11:40.905: %OSAPI-6-FILE_DOES_NOT_EXIST: osapi_file.c:348 File : /proc/755/stat does not exist.(errno 2)
Oct  7 20:11:40 wlc-1 WLC-1: -Traceback:  105eaae4 105f4d44 105f7848 105fa648 105f3ab0 10c0d250 111cd0cc
Oct  7 20:11:40 wlc-1 WLC-1:
Oct  7 20:11:43 wlc-1 WLC-1: *mmMobility: Oct 07 22:11:43.210: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
Oct  7 20:11:43 wlc-1 WLC-1: -Traceback:  105fbe18 102d8be0 102bc81c 102d5d20 105f3ab0 10c0d250 111cd0cc
Oct  7 20:11:43 wlc-1 WLC-1:
Oct  7 20:11:43 wlc-1 WLC-1: *mmListen: Oct 07 22:11:43.210: %MM-3-INVALID_PKT_RECVD: mm_listen.c:6691 Received an invalid packet from 192.168.128.18. Source member:0.0.0.0. source member unknown.
Oct  7 20:11:43 wlc-1 WLC-1: *mmListen: Oct 07 22:11:43.211: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
Oct  7 20:11:43 wlc-1 WLC-1: -Traceback:  105fbe18 102cb318 105f3ab0 10c0d250 111cd0cc
Oct  7 20:11:43 wlc-1 WLC-1:
Oct  7 20:11:50 wlc-1 WLC-1: *osapiReaper: Oct 07 22:11:50.913: %OSAPI-6-FILE_DOES_NOT_EXIST: osapi_file.c:348 File : /proc/755/stat does not exist.(errno 2)
Oct  7 20:11:50 wlc-1 WLC-1: -Traceback:  105eaae4 105f4d44 105f7848 105fa648 105f3ab0 10c0d250 111cd0cc

---

When looking back a bit in the logs it looks like this started after upgrading the Software version. But after this first reload it the APs came back and worked. Now they don't.

The case seams to be the same with both my WLCs.

What could have gone wrong?

Please advice.

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: Updated WLCs shows wierd log messages and most APs do not as

Not sure which messages are concerning you the most...

Regarding the message:

Oct  7 20:11:39 wlc-1 WLC-1: *mmListen: Oct 07 22:11:39.749: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
Oct  7 20:11:39 wlc-1 WLC-1: -Traceback:  105fbe18 102cb318 105f3ab0 10c0d250 111cd0cc
Oct  7 20:11:39 wlc-1 WLC-1:

There is already a bug for it: CSCth64522

And for:

Oct  7 20:11:50 wlc-1 WLC-1: *osapiReaper: Oct 07 22:11:50.913: %OSAPI-6-FILE_DOES_NOT_EXIST: osapi_file.c:348 File : /proc/755/stat does not exist.(errno 2)
Oct  7 20:11:50 wlc-1 WLC-1: -Traceback:  105eaae4 105f4d44 105f7848 105fa648 105f3ab0 10c0d250 111cd0cc

Looks like it's matching CSCtf39550

Both bug fixes should be included in the next 7.0 release and should not impact the WLC behavior.

Hope this helps...

3 REPLIES
New Member

Re: Updated WLCs shows wierd log messages and most APs do not as

An update...

After waiting a loong time. Over 60 minutes the APs are now back again.

And looking closer at the logs tells me that thoose weird messages I posted earlier only apears on one of the controllers.

/M

Re: Updated WLCs shows wierd log messages and most APs do not as

Is the time right on the controller. I found this about the one error. But doesnt make sense if the all got back on again ...


Error Message    %MM-3-INVALID_PKT_RECVD: Received an invalid packet from 
[dec].[dec].[dec].[dec]. Source member:[dec].[dec].[dec].[dec]. [chars]. 

Explanation   Internal system error

Recommended Action   Please check mobility configuration to see if it needs correction.

__________________________________________________________________________________________ "Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin ___________________________________________________________
Cisco Employee

Re: Updated WLCs shows wierd log messages and most APs do not as

Not sure which messages are concerning you the most...

Regarding the message:

Oct  7 20:11:39 wlc-1 WLC-1: *mmListen: Oct 07 22:11:39.749: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
Oct  7 20:11:39 wlc-1 WLC-1: -Traceback:  105fbe18 102cb318 105f3ab0 10c0d250 111cd0cc
Oct  7 20:11:39 wlc-1 WLC-1:

There is already a bug for it: CSCth64522

And for:

Oct  7 20:11:50 wlc-1 WLC-1: *osapiReaper: Oct 07 22:11:50.913: %OSAPI-6-FILE_DOES_NOT_EXIST: osapi_file.c:348 File : /proc/755/stat does not exist.(errno 2)
Oct  7 20:11:50 wlc-1 WLC-1: -Traceback:  105eaae4 105f4d44 105f7848 105fa648 105f3ab0 10c0d250 111cd0cc

Looks like it's matching CSCtf39550

Both bug fixes should be included in the next 7.0 release and should not impact the WLC behavior.

Hope this helps...

3046
Views
14
Helpful
3
Replies
CreatePlease to create content