1702I Access point || error log

[lAhmed Saadl]

Dears,

Appreciate your guide, this is frequently and randomly occurs cause the access point to be down and then up in a few secounds.

Thanks,

 

[balaji.bandi]

You need to go more detailed logs and see what is wrong - with that screenshort hard to define what is causing the issue to be honest my views.

check error code and details more you can get : (same for all AP Models)

https://www.cisco.com/c/en/us/support/docs/wireless/aironet-3700-series/117869-technote-ap-00.html

[lAhmed Saadl]

Dear Balaji,

I tried to proceed with the commands mentioned, and this is the result. I didn't anything out of it, perhaps you can advise. 

[Leo Laohoo]

What firmware version is the controller on?

[lAhmed Saadl]

AIR-CT5520-K9

[Leo Laohoo]

---

@lAhmed Saadl wrote:

AIR-CT5520-K9

---

Wrong answer. 

Try again:  What firmware is the controller on?

[lAhmed Saadl]

It was a silly mistake. you're right.  Thanks for attention.  8.10.171.0

[Leo Laohoo]

Log into that particular AP and post the complete output to the command "dir".

[lAhmed Saadl]

Please find the output.

[Mark Elsen]

                Check client load on the access point, perhaps there are too many clients connected 
- Ref : https://www.cisco.com/c/en/us/td/docs/wireless/access_point/tech-notes/ap-radio-reset-codes.html
         >...

45

RADIO_FC_RX_OVERRUN_STUCK

Rx buffer is full which resulted in RCV buffer overrun stuck

[lAhmed Saadl]

Hello Marce,

Nice to meet you again 🙂 Actually, I read that thread before, but the total number of users that access this AP in the working hours doesn't exceed 25 clients, also I noticed that it shows this log again after the working hours where there is hardly any one connected to it. But, I'd like to follow up your recommendation if you advise something to do regarding that.

[Rich R]

Upgrade to 8.10.183.0 (next release due soon but that will make sure you have all available fixes for now).

If you still see the same problem then unfortunately for you it's not going to be fixed because 1702 is way past end of software maintenance date: https://www.cisco.com/c/en/us/products/collateral/wireless/eos-eol-notice-c51-740712.html

You could also open a TAC case (after upgrading) to see whether TAC have any additional advice.