said by 34764170:
Measuring for the purpose of generating graphs is not the same thing as feeding the data into your magic mechanism software running on the router. I don't agree about the 5 min polling. Anyway, it's a moot point. This magic mechanism would have to exist within JunOS and I can't imagine anyone bothering to implement something like this. The target market is practically non existent.
The idea is to only use this for extreme cases, where a link really gets out of balance, so the 5 minute window should be sufficient. Typically, most links are balanced enough, and it's only a small number (or even just one) that got out of whack.
Depending on how things are done, it might not have required any changes to JunOS. For example, at some point the auth request hits the RADIUS server. Is there any sort of information at that point that might indicate which tunnel the connection came in on? TSI moved to one tunnel per AHSSPI recently, and the solution could be as simple as having your RADIUS server not respond to authentication requests from any tunnels that are overloaded.
Does it require custom code from the ISP? Yes, but so do many things inside an ISP.--
Developer: Tomato/MLPPP, Linux/MLPPP, etc »fixppp.org