12/8/2023 0 Comments Router throttlingIf the first topology change event occurs after the maximum wait-interval begins, the SPF calculation is again scheduled at the start-interval and subsequent wait-intervals are reset according to the timers throttle spf command. Once the maximum wait-time is reached, the wait-interval remains the same until the topology stabilizes. The wait-interval doubles when at least one topology change event is received during the previous wait-interval. The wait-interval indicates the amount of time to wait before scheduling an SPF calculation in an event of topology change in this case, 1000 milliseconds. Spf-max-wait: Maximum wait between two SPF calculations. Spf-hold: Minimum hold-time between two SPF calculations. Spf-start: Initial delay to schedule an SPF calculation after a topology change. The OSPF SPF Throttling is configured using the command timers throttle spf OSPF router configuration command. By default, SPF interval is chosen dynamically and depends on frequency of topology changes. SPF runs when there is a topology change. This is absolutely ridiculous that Google can't figure this out, or they have and can't fix via firmware ( and they don't want to replace millions and millions of units).OSPF Shortest Path First Throttling feature allows to schedule SPF calculations in milliseconds interval and delay SPF calculations during network instability. I rebooted the Google Wifi AP this morning and retested my wireless connect from my phone, sitting in the same spot (I went from 42up/35down to 453up/461down). However any device connected wirelessly to the Google Wifi AP, get the drop down to ~90Mbs up/down. The good news is that any device connected through a WIRE going to the Linksys Router gets the expected ~900Mbs up/down. I can tell you that it is the device itself, no matter whether acting as a ROUTER or Acting as a simple AP, the same thing happens. Thinking this was an issue of the router functionality. I then took one of my mesh Google Wifi devices and reset it and am using it now as an AP (put in Bridge Mode). Based upon all the discussion, I removed the Google Wifi as my ROUTER and replaced it with a Linksys EA9300 that I had been using as a basic AP (Bridge Mode). I wanted to post another update - have no idea if it will help or confuse the matter. Looks like there are a TON of merged threads that got thrown into it too: I did some more research, and now I'm thinking the below thread shares common issues as myself. Ran them for a week each without any throttling. My other two routers do not have this issue at all. This issue happens only with the Google WiFi router, both wired and wireless, anda network restart consistently fixes it, albeit temporarily. Network analytics, PRTG, WireShark show no anomalies in my network, or any weird traffic or dropped packets. Also worth noting that I'm an IT Senior Systems and Network Admin by trade, with a close eye on my home network. It's worth noting that this just started happening maybe in the last 1-2 months.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |