Switch Firmware 2.3b Released!

Switches
1

We’re excited to announce a substantial firmware update for our switches, featuring expanded hardware compatibility and key improvements to core functionality.

  • Add support for S48-APOE and S12.
  • Add support for HTTP time-sync if NTP is unavailable.
  • S8-POE/S16-POE: Improve IGMP Snooping.
  • Improve STP BPDU handling.
  • Improve management CPU latency.
  • S24: Resolve issues with manual 1Gbps setting on SFP ports.
  • 802.1X: Resolve issues when a device links back up.
  • S24: Resolve stability issues introduced in 2.3a.

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:

As always, if you have questions or encounter any issues, feel free to reply here or start a new topic. Please include details about the issue so we can assist you effectively.

4 Likes
2

Thanks, Mike! Out of curiosity, would you be able to provide any more detail on the stability issues that were fixed from 2.3a? If not, no big deal.

Honestly, I know I always enjoy seeing the seeing the little details about what went into fixing and improving things, but I understand not wanting to make the release notes super long as well.

Thanks again!

1 Like
3

@jmszuch There was a incorrect register written as a result of merging support for S48-APOE and S12 into the main branch, and this was corrected.

4 Likes
4

Thanks and much appreciated, Jeff! I’d like your post twice if I could :grinning_face_with_smiling_eyes:

1 Like
5

Hey Alta team,
Just updated one of my S8s to 2.3b and upon reboot it wouldn’t connect to the cloud controller. Figured out that the date was set to Mar 2029 which obviously caused problems with the SSL cert on manage.alta.inc. Any way I can send you logs? I was able to temporarily fix it by manually setting the date on the CLI.

Jul 3 11:54:06 hostname daemon.info htpdate[2298]: Setting 116477488.016 seconds
Jul  3 11:54:06 hostname daemon.info htpdate[2298]: Set time: Mon Mar 12 10:45:34 2029
Mar 12 14:45:34 hostname user.alert : odd response: 4390912
Mar 12 14:45:35 hostname daemon.alert rc: run "curl -s -f -6 -m 7 -X POST https://manage.alta.inc/api/device/boot -o /var/run/boot.json -H 'Content-Type: application/json' -d '{ "id": "xxxxxx", "model": "3", "version": "2.3b", "pubkey": "xxxxxxxxx"
Mar 12 14:45:35 hostname daemon.err rc: [2029/03/12 10:45:35:9302] E: SSL error: certificate has expired (preverify_ok=0;err=10;depth=0)

root@hostname:~# curl https://manage.alta.inc
curl: (60) SSL certificate problem: certificate has expired
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

root@hostname:~# date
Mon Mar 12 10:50:58 EDT 2029
6

If you can reproduce it and get a packet capture some how, we can flag the NTP server you used as incorrect.

7

I took a packet capture while upgrading my second switch and the same issue happened. I think this is related to the new http based time sync because all the NTP responses have the correct time in the packet capture. I can’t see half the http header time values since the traffic is encrypted. The non encrypted HTTP traffic in my capture also shows the correct time. I’ll monitor and if it happens again on the next upgrade I’ll circle back.