09-02-2019 12:44 AM - edited 07-05-2021 10:56 AM
Hello
I noticed a radio issue with IW3702 APs running version 8.5.140.0 and FC mode. Looking at the logs on the APs I noticed a bunch of radio reset codes similar to those below. I did some searching online and I found a bug with the same issue for a different model AP and mode described here CSCvn56211. So I upgraded APs to the suggested version 8.5.151.0 however, the issue still remains.
*Sep 1 10:05:43.651: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio0 due to the reason code 42 *Sep 1 10:05:43.659: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio0 due to the reason code 56 *Sep 1 10:05:43.659: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio0 due to the reason code 21 *Sep 1 10:05:43.663: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down *Sep 1 10:05:43.671: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio1 due to the reason code 42 *Sep 1 10:05:43.675: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio1 due to the reason code 27 *Sep 1 10:05:43.675: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset *Sep 1 10:05:43.679: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down *Sep 1 10:05:44.291: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio1 due to the reason code 56 *Sep 1 10:05:44.291: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio1 due to the reason code 21 *Sep 1 10:05:44.291: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio0 due to the reason code 10 *Sep 1 10:05:44.291: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio1 due to the reason code 10
Does anyone have a similar issue?
Rudi
09-02-2019 04:38 AM
09-02-2019 05:01 AM
09-02-2019 05:39 AM
05-13-2021 04:34 AM
Hi
i've similar issue on 8.5.170.0 with CAP2702Es. did u get any help from TAC?
10-06-2021 04:45 PM
Did you get any resolution on this? I'm in the progress of migrating a bunch of 3702's running 8.5.151.0 from local to FlexConnect mode and have started noticing these errors popping up in the logs.
10-07-2021 12:20 AM
had no luck (
10-07-2021 12:28 AM
Is there a reason why you don't upgrade to the newer 8.5.x builds?
I also found this bug, which is not exactly the same, but might be close enough:
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvn53435
That one is fixed in the 8.5.160.0 release, but there are also other radio bugs that were fixed in the newer builds.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide