Forum Discussion

jan_de_wachter_'s avatar
jan_de_wachter_
Icon for Nimbostratus rankNimbostratus
Jan 20, 2017

LTM FastL4 and source-address persistency

We have an application that was difficult to make working as needed.

At last we succeeded by creating a Performance (Layer4) VS with FasL4 profile. They also needed sticky sessions.

ltm virtual /Infrabel/a1183-***-***_vs {
    destination /Infrabel/10.252.13.204%113:6039
    ip-protocol tcp
    mask 255.255.255.255
    partition Infrabel
    persist {
        /Infrabel/a1183-***-***_sticky-mirror {
            default yes
        }
    }
    pool /Infrabel/a1183-***-***_pool
    profiles {
        fastL4 { }
    }
    source 0.0.0.0%113/0
    source-address-translation {
        type automap
    }
    vs-index 160
}

The application guys are happy, everything is fine. BUT we can't find any persistency records.

I thougt that with an FastL4 profile, you couldn't have any special profiles (like coockie persistency, ...) which need HTTP (L7). But destination and / or source address persistency profile was permitted.

Can anyone help me with this "logic" problem - is there source address persistency or not and how can I find this out?

Thanks

Jan

4 Replies

  • Not sure if you are looking for this. tmsh show /ltm persistence persist-records but be careful while using this command under heavy load.

     

  • You can check specifically for source based persistence with this tmsh command:

     

    (cfg-sync Changes Pending)(Active)(/Common)(tmos) show ltm persistence persist-records mode source-address Sys::Persistent Connections source-address 10.x.x.x 10.x.x.x:443 10.x.x.x:9820 (tmm: 7)

     

  • Thank you for the answers BUT my real question is:

     

    Is there source address persistency when having Performance (Layer4) VS with FasL4 profile?

     

    Source address persistency is defined (and accepted by the GUI), but when doing these show commands I do not see any persistency. And there are always connections active!

     

    In the documentation they say it should work, but I don't see any persistency!

     

    Thanks

     

    Jan

     

  • Yes you can see the source-addr persistence records with fastl4 profile. try with more specific command tmsh show ltm persistence persist-records virtual (PerfL4 Virtual server name) without brackets if still your don't see the record look for timeout value in persistence profile may be its getting removed before you fire the command in CLI.