UDP Load Balancing for Radius traffic.
I am wanting to setup a UDP Virtual Server (10.1.0 code LTM 6900) to load balance between my AAA servers and some servers. Right now I have all traffic (TCP and UDP) on the F5 going through the default IPv4 Forwarding VS. I want to setup a separate VS that can load balance the TCP and UDP traffic to the servers. The traffic UDP using the Radius protocol. I have read F5's White Paper and looked at the manuals but noting is straight forward in either of those docs.
My 1st pass on this is setup the VS with it's own IP from the range assigned to the subnet on the egress VLAN of the F5's and just pass all traffic coming from the AAA servers to one pool member until I have the time to fully test the LB solution in my lab. This way I can get the AAA's to switch over to the new IP and I can get the traffic ready for the LB solution.
The question I have is it better to just setup another IPv4 Forwarding VS using the new IP and have it look for the source IP's of the AAA's as the valid IP's to forward? That way any other traffic coming in bound for the servers behind the F5's would not be effected. I have other traffic that needs to remain going through the original default IPv4 Forwarding VS.
Second question is how do I handle originating traffic coming back from the servers in the pool to the AAA's? Do I use SNAT so they get translated into the new IP of the new VS?