This is a hotfix release for 2.3o which also brings enhancements to monitoring and audit reporting, improves overall system reliability, and resolves several network-related issues.
Add support for reading SFP port DDM info (RX power, temperature, etc.), optionally enabled under Settings->System->Advanced.
Add support for reporting firmware updates to audit log.
Add support for reporting storage usage.
Improve reliability for system storage.
Resolve DHCPv6 issues when IGMP snooping is enabled.
Reduce DNS traffic used for connectivity checks.
Resolve DNS resolution issues introduced in 2.3o.
This update is being rolled out now. You can manually initiate the upgrade if you’d like, or it will automatically update overnight (if auto-updates are enabled). The complete, up-to-date changelog is available here:
If you have questions, feedback, or run into any issues, feel free to reply here or start a new topic. Including configuration details or relevant logs where possible helps us troubleshoot and respond more quickly.
What exactly are your QC processes prior to releasing updates? Because I hate to be the bearer of bad news, but I am down yet again after attempting to update from 2.3n to 2.3p. This platform is literally unpredictable.
These releases have gone out to thousands+ of sites already, with no incidents logged. This was after a slow rollout to internal test sites with no observed issues. This also includes local controller installs. I would definitely like to take a look at your specific setup, if that’s possible, though!
Yes, but how could you verify these success rates with those who are managed locally?
Unless one of these Alta components are the culprit, I honestly cannot think of any reason as to why this continuously occurs with only your products. To be completely honest, these issues began once I introduced the S24 into the network.
I’m not really at liberty to explain our proprietary methods, but suffice it to say that there have been no anomalies with this upgrade cycle that hit our radar.
I will say that your experiences are definitely out of the ordinary (backed by our analytics), but also that most users do not run local controllers, which we still obviously fully support (and do not see anomalies there, either). That being said, we’ve been on your site multiple times in the past to resolves issues, and I’m happy to take another look.
I’ve invited you before and I’ll gladly invite you again. This is not a complex network, but at this point I’m about ready to transition back over to TiK. After taking some time to review a few things, it looks like the issues are still revolving around the SFP interfaces on the S24 as I’ve mentioned again time after time to you and the team.
Not to pry but are you running the docker container or like a full blow server type thing? I was looking at running my own as well and you are one of the first I read that run their own. I tried getting the docker working on Unraid once but stopped for a bit.
I’m waiting for ALTA to provide cloud management capabilities for our on-premises CONTROL device. They’re taking too long with this. Now, you can understand why Tom Lawrence stopped evangelising their products, and so have I. All of my projects are UniFi.
I’ve read that the local controller still requires internet or something? Is that true? The reason I wanted to self host is because I have fiber with a bypass and when the internet goes down(like i messing with something) I have literally no control over alta or view on what it is seeing.
Unfortunately I didn’t have time yesterday. I’ve provided logs to Alta for now. Something has got to give, I cannot continue doing this each time there’s an update.
I’ve already removed the Route10 from the network, next will be will be switches if this isn’t resolved which will leave the AP’s remaining.
No traffic goes in/out unless I explicitly allow it. I allow WAN access briefly to all Alta devices after I’ve vetted firmware updates on here ensuring there weren’t any recorded issues.
I’ve been plagued with the same issue every couple of updates following their update process. Specifically when the firmware writes and issues the initial reboot. The switches never recover properly requiring a manual power cycle. The concern seems to be isolated to their switches, specifically their SFP interfaces not recovering (which have always been utilized as my northbound interface)
I believe you are speaking about your specific system here, but the normal setup for most customers does require the control device to have Internet access.
Normally, all Alta devices would issue requests to alta.inc in intervals. I only allow for local NTP, and block everything else.
Full disclosure. I’ve never had issues with my network prior to Alta. I suspect I either have a defective S24, or there is a question of firmware specific to my hardware or batch.
Well, anything I had before Alta had zero issues even with the same DAC’s or SFP/SFP+ brands. So if it’s a question of vendor, I’m happy to provide that to Alta, yet again. I’ve been using the same vendors since the beginning.