|
Francois Baligant wrote:
>
> We have a very weird problem load-balancing UDP-based
> RADIUS packets.
don't know anything about RADIUS - I'll assume I don't need to know
for the moment.
> UDP 195.74.212.37:16450 rr
> -> 195.74.212.26:16450 Route 1 0 0
> -> 195.74.212.34:16450 Route 1 0 0
> UDP 195.74.212.31:1646 wlc
> -> 195.74.212.26:1646 Route 1 0 106
> -> 195.74.212.10:1646 Route 1 0 106
> UDP 195.74.212.31:1645 wlc
> -> 195.74.212.26:1645 Route 1 0 1
> -> 195.74.212.10:1645 Route 1 0 0
>
> We try to load-balance 3 ports. 1645 (authentication),
> 1646 (accounting) and 16450 (authentication for another
> kind of service).
>
> What's weird is that 1645 works really fine but the 2
> others rules just do not load-balance. Packets are always
> sent to the same host. (in fact the first that was added
> to the VS IP)
how is the output above an example of it not working?
Someone had a similar sounding problem with ntp (which is udp based).
All packets would go to one host and then after a little while to
another. In the short term the load balancing was bad, but
over the long term (>15mins) the loadbalancing was fine.
The udp LVS code sends all udp packets to one realserver, till a timeout
is reached, and then sends the next packets to another realserver.
It sounds like all udp packets are going to one realserver forever, right?
> UDP packets come from a single
> server (our central proxy radius).
Do you mean that the udp packets are coming from a single machine, which
is a client for the LVS, but is a server for your users?
Joe
--
Joseph Mack PhD, Senior Systems Engineer, Lockheed Martin
contractor to the National Environmental Supercomputer Center,
mailto:mack.joseph@xxxxxxx ph# 919-541-0007, RTP, NC, USA
|
