- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
6020 AP's on Bluesocket 4.5.0 constantly rebooting
We upgraded to Bluesocket 4.5.0 and are still having trouble with our (6) 6020's rebooting every few hours as we did with 4.2.3: in fact it seems to be worse: one just went offline.
Is anyone successfully running 6020's and having them stay up for weeks and months like 2020's and 1920's etc? If so, I'd like to compare notes.
(Speaking of 2020's: make sure that you use the firmware released in January 2025: the version that was released with 4.5.0 in December is very buggy.)
Otherwise several 1900's, 2000's and 3000's are running fine on 4.5.0 in production in just one building on one of our campuses. We will expand the test and if it goes well upgrade the main controller to 4.5.0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Accept as Solution
- Report Inappropriate Content
Re: 6020 AP's on Bluesocket 4.5.0 constantly rebooting
We are having the exact same issues on our 6040s after 4.5.0. Agreed it seems to be worse. We did have issues as well with the buggy December release but are current on the most recent one. Same with our 2020s and 2030s. Rock solid with the exception of the December release.
Looking at the logs, we are trying to see any regularity in the reboot cycles; nothing thus far. In addition, we find "stalled" 6040s with Power, Network-1 & 5gHz LEDs solid blue. We manually power cycle these. (We also only run 5gHz radios).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Accept as Solution
- Report Inappropriate Content
Re: 6020 AP's on Bluesocket 4.5.0 constantly rebooting
I'm rolling our 6020's back to our 4.2.1 controller with 4.2.3-R-681418 firmware for the 6020's until we hear something from Adtran. We had another 6020 go completely offline yesterday: the reboots are one thing but going off line completely isn't acceptable.
Hopefully this is getting some attention?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Accept as Solution
- Report Inappropriate Content
Re: 6020 AP's on Bluesocket 4.5.0 constantly rebooting
Adtran is aware of the issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Accept as Solution
- Report Inappropriate Content
Re: 6020 AP's on Bluesocket 4.5.0 constantly rebooting
We have this problem too. We only run 6040's so it's been especially detrimental.
Been going back and forth with Adtran for months now without much success. They uploaded a new FW build which seems to reduce the reboots but our guest wifi VLAN does not broadcast correctly.
On
Version 4.2.1
Build 678053

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Accept as Solution
- Report Inappropriate Content
Re: 6020 AP's on Bluesocket 4.5.0 constantly rebooting
Does anyone have anything new to add? The last firmware I tried before having to revert was bsap6040-4-5-0-HA-685193.bidp
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Accept as Solution
- Report Inappropriate Content
Re: 6020 AP's on Bluesocket 4.5.0 constantly rebooting
Hi Brian (or anyone watching this thread) do you have a support ticket open on this issue? If so, would you mind sharing the Ticket #?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Accept as Solution
- Report Inappropriate Content
Re: 6020 AP's on Bluesocket 4.5.0 constantly rebooting
sure, 00365366 and 00373838
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Accept as Solution
- Report Inappropriate Content
Re: 6020 AP's on Bluesocket 4.5.0 constantly rebooting
Hey everyone,
Please open a Support case if you would like Adtran Support assistance, link below:
Thank you,
Adtran Support

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Accept as Solution
- Report Inappropriate Content
Re: 6020 AP's on Bluesocket 4.5.0 constantly rebooting
Since you put it that way; the case was closed, saying that AP firmware fixed it but what firmware fixed this exactly? As far as I know it's still an ongoing issue from what me and others are seeing... not going back to 4.5 unless someone can prove to me its fixed.
|
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Accept as Solution
- Report Inappropriate Content
Re: 6020 AP's on Bluesocket 4.5.0 constantly rebooting
Thank you for sharing. If you feel your case's resolution did not deliver a clear understanding of next steps, fix, workaround, etc. Please feel free to open a new case and inquire further.
Thank you,
Adtran Support
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Accept as Solution
- Report Inappropriate Content
Re: 6020 AP's on Bluesocket 4.5.0 constantly rebooting
I'm still very interested in my opening question: "Is anyone successfully running 6020's and having them stay up for weeks and months like 2020's and 1920's etc? If so, I'd like to compare notes."
I'd like to know what firmware rev and any details about how you achieved stability. If there are no such users yet we'll stick with 2020's and version 4.2.3
As far as I know there has been no new firmware for 4.5.0 for the 6000 series. Also: the firmware released in January for 1900's and 2000's has no updated release notes. So we are all kind of flying blind as to what is getting fixed or not.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Accept as Solution
- Report Inappropriate Content
Re: 6020 AP's on Bluesocket 4.5.0 constantly rebooting
That's why I created 00373838 on 4/23/2025; so far, I have heard nothing.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Accept as Solution
- Report Inappropriate Content
Re: 6020 AP's on Bluesocket 4.5.0 constantly rebooting
Just FYI:
The firmware released in Feb for the 2000 series and 3000 series fixes an issue with DHCP where clients would not properly pull DHCP when they logged onto the network. It also fixes some disconnect issues clients were seeing.
For the 6000 series, we are investigating some possible firmware fixes for stability right now, but they are still in process. If you are experiences crashes, I would strongly encourage you to open a ticket so we can grab that data and verify our fix with it or see next steps.
Thanks,
Evan Hudson
ADTRAN Product Support Engineer

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Accept as Solution
- Report Inappropriate Content
Re: 6020 AP's on Bluesocket 4.5.0 constantly rebooting
Had to have server p10 and our onprem rolled back to Version 4.2.1 Build 678053 because a large majority of our 6040 would reboot at random in quick succession causing large outtages.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Accept as Solution
- Report Inappropriate Content
Re: 6020 AP's on Bluesocket 4.5.0 constantly rebooting
Hi Evan; are you talking about 4.5.0.HA released on Jan 28? Yes that certainly helped the 2000's and 3000's. There are no release notes for that release (they just re-posted the 4.5.0 release notes with them: surely someone could have taken the time to explain what was fixed?) As for the 6000's:my question remains. Is there anyone on this thread that has stability with any controller or firmware release? If so, please tell us about your environment. This is what a manufacturer support community is all about: we are all very invested and want this product to succeed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Accept as Solution
- Report Inappropriate Content
Re: 6020 AP's on Bluesocket 4.5.0 constantly rebooting
Brian: so your 6040's are up for weeks and months at a time with Version 4.2.1 Build 678053. Anything later is unstable?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Accept as Solution
- Report Inappropriate Content
Re: 6020 AP's on Bluesocket 4.5.0 constantly rebooting
that is correct.