Forum Discussion

mikegray_198028's avatar
Sep 01, 2016

persistance issue

Hi Team,

I am facing load balancing issue with a default hash persistence profile. f5 sending traffic only to one server and we don't have any irule . can some one help me on this.

ltm virtual testvip {
destination 192.168.10.1:https
ip-protocol tcp
mask 255.255.255.255
persist {
    hash {
        default yes
    }
}
pool testvip
profiles {
    testvip-clientssl {
        context clientside
    }
    newhttp_x_forward { }
    oneconnect { }
    tcp-lan-optimized {
        context serverside
    }
    tcp-wan-optimized {
        context clientside
    }
}
source 0.0.0.0/0
source-address-translation {
    type automap
}
vs-index 715}
        ======================================          
             testvip                Common  220.5M  343.2M  315.8K  253.1K  0   959     51.0K   50.7K   0   0
       --   server1.test.com:8086   Common  220.5M  343.2M  315.8K  253.1K  0   959     51.0K   50.7K   0   0
       --   server2.test.com:8086   Common  0   0   0   0   0   0   0   0   0   0

3 Replies

  • What do you want the persistence to do ? Using default hash persistence won't help much without understanding the logic required. Can you provide us some more information on the persistence logic required ?

     

  • For Jsessionid persistence, use this SOL7392

     

    I am assuming that the JSessionid exists only in the cookie. If it exists in the URI too, then you may need something like this

     

  • Out of curiosity - Does the F5 only see "one" IP address trying to be load balanced ?