Forum Discussion

Nimbostratus

May 05, 2009

soudce address persistency

Hi, I want the F5 to load balance the same client IP to the same pool member ALWAYS so If I have 2 pool members I want that if client with source IP 172.17.1.1 sends traff...

Nimbostratus

May 05, 2009

Thanks for you quick response

I just gave an example.

In reality I'll have much more than 2 pool members (more like 20-50)

As long as the same source IP always goes to the same pool member its good (I dont care about specific mapping. like 172.17.1.1 doesnt have to go to member1. it can go to member17 as long as it will ALWAYS go to member17)

I used "source_addr" persistence. edited the profile and changed the default timeout from "180" to "indefinite" and it seems to do the job

however it stored each and every record in the persistency table forever. if I'll have a lot of source IPs wouldn't it overload the device?

In Alteon I just use "metric hash" and even if the session was aged out, next time a packet comes from the same source IP it will be sent to the same pool member (guess it uses MD5)

define each and every pool member with its MOD result is going to be ugly. especially when I add new servers

b persist show all

| Mode source addr Value 172.17.1.1

| virtual any:http node 172.17.3.102:any age 1494sec

| Mode source addr Value 172.17.1.4

| virtual any:http node 172.17.3.102:any age 3313sec

| Mode source addr Value 172.17.1.7

| virtual any:http node 172.17.3.101:any age 3018sec

| Mode source addr Value 172.17.1.3

| virtual any:http node 172.17.3.102:any age 3494sec

| Mode source addr Value 172.17.1.6

| virtual any:http node 172.17.3.102:any age 3154sec