This release provides a focused improvement to enhance accuracy in event handling.
Resolve issue of IDS events getting clipped at 240.
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 is status of the ospf fix for the routing table on the router? Perhaps @Alta-MikeD or @Alta-cmb can shed some light on it. I was under the impression it was fixed over a week ago.
Seems like maybe this update caused me an issue as well. I’ve got one device that can no longer access WAN unless I change the static IP, then it works fine. Issue is there are multiple devices dependent on the original static IP. There’s no other IP conflict from what I can tell and I can tell the first issues were early am hours today.
The update seems to be causing my switches to max out the cpu and crash leading to disconnections. Looks like the same problem that was fixed a few versions ago
That was rough. Had to reboot router which then caused a lot of issues, router claimed devices were self assigning IPs to subnets I’ve never used and having conflicts. A lot of devices appeared to have IPs just fine but were non functional. Rebooted router and switch again a couple times and now I think things are ironing themselves out.
Looks like I will now disable auto updates.
I’m no network expert, but I think anything without a static IP got a new one and a subnet or two filled up? Shouldn’t a devices dhcp assigned IP be consistent after just a reboot? Seems like the router was duplicating devices somehow?
Yes, the Route10 stores DHCP assignments through reboot and firmware updates. If you are able to reproduce a situation where this does not happen, then we’d love to take a look, but throughout all of our analytics, we are not seeing this.
Everything is now back to normal, network traffic is passing through fine with no drops and there is no longer any issues with DHCP assignments.
Am certain the 1.4m update caused the issue, just cant put my finger on what exactly made it unstable.
Anyways I performed a hard reset and deleted the Route 10 from the portal. Went through the inital set up process again from the manage.alta page and everything is working perfectly again.
So, I’m here to report some oddness that matches the behavior above. However I have not yet updated to 1.4m. At some point overnight, around 4am my time, my network mostly dropped. Wifi down, some wired items not working, etc. Luckily I was able to get into my local controller and reboot my route10 and AP6Pros, which brought back most of it, however I still have a wired device (at least one, checking to confirm if there are others) that is self-assigning a 169.254.x.x IP. I did the latest switch update as the device is plugged into my s8poe, no luck there. I am going to try the route10 update to 1.4n in a bit, but the behavior seemed too similar to not report here.