For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

cvitale_103614's avatar
cvitale_103614
Icon for Nimbostratus rankNimbostratus
Jul 16, 2014

Specify use specific custom persistence profile in iRule

We currently have this iRule association on LTM VIP service. It does a conditional check and if it meets criteria then it says to use (persist cookie) else it will use (persist source_addr). We would...
cvitale_103614's avatar
cvitale_103614
Icon for Nimbostratus rankNimbostratus
Jul 16, 2014

Steve, Thanks for the response. Yes I have tried that (just simply putting in the profile name) but rejects with following error.

 

01070151:3: Rule [iRule-Test-tmp] error: line 6: [invalid option "source_addr-3600sec" must be: cookie none source_addr simple dest_addr sticky msrdp ssl uie universal hash carp sip add lookup delete] [source_addr-3600sec]

 

when HTTP_REQUEST { if { (([HTTP::path] starts_with "/poweshell") && ([IP::addr [IP::client_addr] equals 10.15.10.15])) } { persist cookie } else { persist source_addr-3600sec } }

 

Steve_M__153836's avatar
Steve_M__153836
Icon for Nimbostratus rankNimbostratus
Jul 16, 2014
Sorry I think I was wrong. I don't think you can specify a custom persistence profile in an iRule. What you can do is specify the standard profile with the values that you want. Example "persist source_addr 255.255.255.0 3600". In this case you're specifying the mask and a timeout of 3600 seconds.