Advanced iRules: Tables

We’ve covered quite a bit of ground in the Getting Started with iRules and Intermediate iRules series. In this series, we’ll dive even deeper down the rabbit hole, starting with the table command. Th...
Updated Oct 02, 2023
Version 2.0
300
devops
iRules
series-advanced-irules
JRahm's avatar
Icon for Admin rankAdmin
Christ Follower, Husband, Father, Technologist. I love community and I especially love THIS community. My background is networking, but I've dabbled in all the F5 iStuff, I'm a recovering Perl guy, and am very much a python enthusiast. Learning alongside all of you in this accelerating industry toward modern apps and architectures.
View Profile
JRahm's avatar
Icon for Admin rankAdmin
Christ Follower, Husband, Father, Technologist. I love community and I especially love THIS community. My background is networking, but I've dabbled in all the F5 iStuff, I'm a recovering Perl guy, and am very much a python enthusiast. Learning alongside all of you in this accelerating industry toward modern apps and architectures.
View Profile
Cay_Jeglinski_1's avatar
Cay_Jeglinski_1
Icon for Nimbostratus rankNimbostratus
Sep 27, 2018

Hi Jason,

I have contacted support on this issue. Finally the way it works is to use the same traffic group on all virtual ip addresses, since by default the tables are not synced across traffic groups. You may however choose to sync with

tmsh modify sys db tmm.sessiondb.match_ha_unit value false
tmsh save sys config

Since I have not used this option no recommendation by my side. Perhaps this note helps the community.

Thanks, Cay