cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2913
Views
25
Helpful
7
Replies

Cisco 1852i Bootloop

da-support-nl
Visitor

Hello everybody,

 

Currently i am experiencing bootloop issues on multiple 1852i access points.

I can't really find any clue on what goes wrong, perhaps a firmware issue but i can't be sure. 

 

Hoping someone can read my log file and sees what goes wrong and why. 

 

I bought these 1852 access points about a year ago and they started acting up a few months ago. 

There are currently running firmware 8.5.135.0.

7 Replies 7

Leo Laohoo
Hall of Fame
Hall of Fame

RMA the AP.  It is dead.

Mark Elsen
Hall of Fame
Hall of Fame

 

 - FYI : https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvf71074?rfs=iqvred

 M.



-- ' Listen to the wind, it talks  
          Listen to the silence, it speaks
             Listen to your heart, it knows
Ganado Mucho (1809 to 1893 ) Navajo Indian

Rich R
VIP
VIP

I agree with @Leo Laohoo - the radio hardware is dead (says so in the logs) - nothing to do with software bug @Mark Elsen 

The only way to resolve this is to replace the AP.

------------------------------
Please click Helpful if this post helped you and Accept as Solution if this answered your query.
------------------------------
TAC recommended codes for AireOS WLC's   and   TAC recommended codes for 9800 WLC's
Best Practices for AireOS WLC's,   Best Practices for 9800 WLC's   and   Cisco Wireless compatibility matrix
Check your 9800 WLC config with Wireless Config Analyzer using "show tech wireless" output or "config paging disable" then "show run-config" output on AireOS and use Wireless Debug Analyzer to analyze your WLC client debugs
Field Notice: FN63942 APs and WLCs Fail to Create CAPWAP Connections Due to Certificate Expiration
Field Notice: FN72424 Later Versions of WiFi 6 APs Fail to Join WLC - Software Upgrade Required
Field Notice: FN72524 IOS APs stuck in downloading state after 4 Dec 2022 due to Certificate Expired
- Fixed in 8.10.196.0, latest 9800 releases, 8.5.182.12 (8.5.182.13 for 3504) and 8.5.182.109 (IRCM, 8.5.182.111 for 3504)
Field Notice: FN70479 AP Fails to Join or Joins with 1 Radio due to Country Mismatch, RMA needed
Field Notice: FN74383 APs Running 17.12.4/5/6/6a May Run Out of Flash Space Preventing Upgrades
How to avoid boot loop due to corrupted image on Wave 2 and Catalyst 11ax Access Points (CSCvx32806)
Field Notice: FN74035 - Wave2 APs DFS May Not Detect Radar After Channel Availability Check Time
Leo's list of bugs affecting 2800/3800/4800/1560 APs
Default AP console baud rate from 17.12.x is 115200 - introduced by CSCwe88390
AP supported channel lookup: https://apchannels.cisco.com/

Okay i will RMA it then.

 

I still find it weird that these fairly new AP's die one by one. 

 

Can this have anything to do with the POE switch?

And can you point me to the lines of log that tell you that its dead? (Trying to learn and understand the logs). 

 

Thank you!!

 

                            >...And can you point me to the lines of log that tell you that its dead? 

  wcp/RadDrv1 :: Dot11BaseDriver vendor_get_bssid ioctl SIOCGIFHWADDR failed for apr1v13 error No such device

  The way I see it :  the software tries to access a device-component which does not respond or is not available (probably a radio). Actions of last resort could be factory reset and or cold power start (e.g.)

 M.



-- ' Listen to the wind, it talks  
          Listen to the silence, it speaks
             Listen to your heart, it knows
Ganado Mucho (1809 to 1893 ) Navajo Indian

> I still find it weird that these fairly new AP's die one by one.

Known issue with 1832 APs so probably no surprise to see the same on 1852s.  See numerous mentions of the high failure rates of 1832s on these forums.

> Can this have anything to do with the POE switch?

Unlikely.  Obviously you should make sure you're using the right equipment which complies with standards and configured correctly but this is more likely a problem with sub-standard components used in the APs.

ps: I should point out that Cisco insist that even the high failure rate of the 1832s is within their predicted MTBF over the entire installed base.

 

------------------------------
Please click Helpful if this post helped you and Accept as Solution if this answered your query.
------------------------------
TAC recommended codes for AireOS WLC's   and   TAC recommended codes for 9800 WLC's
Best Practices for AireOS WLC's,   Best Practices for 9800 WLC's   and   Cisco Wireless compatibility matrix
Check your 9800 WLC config with Wireless Config Analyzer using "show tech wireless" output or "config paging disable" then "show run-config" output on AireOS and use Wireless Debug Analyzer to analyze your WLC client debugs
Field Notice: FN63942 APs and WLCs Fail to Create CAPWAP Connections Due to Certificate Expiration
Field Notice: FN72424 Later Versions of WiFi 6 APs Fail to Join WLC - Software Upgrade Required
Field Notice: FN72524 IOS APs stuck in downloading state after 4 Dec 2022 due to Certificate Expired
- Fixed in 8.10.196.0, latest 9800 releases, 8.5.182.12 (8.5.182.13 for 3504) and 8.5.182.109 (IRCM, 8.5.182.111 for 3504)
Field Notice: FN70479 AP Fails to Join or Joins with 1 Radio due to Country Mismatch, RMA needed
Field Notice: FN74383 APs Running 17.12.4/5/6/6a May Run Out of Flash Space Preventing Upgrades
How to avoid boot loop due to corrupted image on Wave 2 and Catalyst 11ax Access Points (CSCvx32806)
Field Notice: FN74035 - Wave2 APs DFS May Not Detect Radar After Channel Availability Check Time
Leo's list of bugs affecting 2800/3800/4800/1560 APs
Default AP console baud rate from 17.12.x is 115200 - introduced by CSCwe88390
AP supported channel lookup: https://apchannels.cisco.com/

Scott Fella
Hall of Fame
Hall of Fame

When you issue an RMA, then its up to you to either have TAC review and provide you with an answer, or else, you just end up replacing the unit.  I tend to know when an ap is bad and also it might be easier to just replace the ap.  Environment can also be the cause of ap's failing especially in a dirty environment.  Now, I'm not saying this is your case, but the only way to find out, is to open a TAC case and then have them provide you with root cause before you RMA the device.

-Scott
*** Please rate helpful posts ***
Review Cisco Networking for a $25 gift card