On Fri, Jul 25, 2014 at 7:48 PM, Simon Morley <simon@polkaspots.com> wrote:
Agreed. So it would seem there is an issue getting the traffic back out again as suspected.
We don't have a million users so I shan't bother looking at the F5s. Will hassle Google again.
I suspect their health check is randomly removing the machines from the load balancers.
I'm curious what they use for udp health check. Do they even have any? Is it something that aware of radius packets? Or is it just basic ping check? -- Fajar
Thanks
On 25 July 2014 13:24, Alan DeKok <aland@deployingradius.com> wrote:
Simon Morley wrote:
I've discussed with Google and they're saying the connection isn't closed and the load-balancer therefore puts the instance in 'unhealthy' mode.
UDP sessions aren't "closed". The google support guys don't seem to be competent.
Has anyone tried this successfully - either on GCE or other UDP load balancer? Does anyone have any thoughts about how I could solve?
F5 load balancers seem to work. But they are useful only when you're at Telco scale. i.e. 1M+ users. For pretty much everyone else, it doesn't matter.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html