CSM 4.2 Service per packet for udp traffic

[irodi]

Hi,

We have a problem with the predictor round robin. We have to balance traffic UDP with the same source IP and PORT. Round robin algorithm use the same server for all the traffic as well as see the same source address. We use the service per packet option, but if we use this the nat server doesn't work? It is possible?

Thanks

Ira

[Gilles Dufour]

if you do per-packet the csm does not create a flow entry, so when the server response comes back from the server ip, the CSM is unable to map it to the vserver.

So your servers need to be configured with the same loopback ip address which will be the same as the vserver ip address.

The servers need to be directly connected to the CSM [no next-hop] so the CSM can forward traffic without changing destination ip.

Another solution instead of per-packet, would be to reduce the idle timeout to a minimum, so the CSM removes the flow entry earlier and permit the next packet to be loadbalanced to a diffirent server.

Regards,

Gilles.

[irodi]

Hi Gilles,

thanks for the fast response you give me. I need a idle timeout less then 1 second and this is impossible, while 0 means infinite.

The most udp traffic is with the same source ip address and source port. So in this case the round robin doesn't work? Have you any other suggestion for our case? the first you give (configuring loopback on the server is impossible).

Thanks

Ira