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

Kevin_M_182964's avatar
Kevin_M_182964
Icon for Nimbostratus rankNimbostratus
Jan 16, 2015

do I need to add a persist entry, or does calling persist suffice?

I am trying to create persistent connections based on a transaction ID that is passed from the server to the client. I first grab the transaction ID in the header of the response from the server: ...
application delivery
devops
iRules
LTM
StephanManthey's avatar
StephanManthey
Icon for Nacreous rankNacreous
Jan 16, 2015

Hi Kevin,

seeing multiple persistence records may be caused by the parallel processing in your BIG-IP (CMP, clustered multi processing).

Persistence records need to be distributed to each TMM instance and that´s why they my be dumped multiple times.

I guess you see at the end of each persistence record different entries for tmm instances (i.e. tmm: 0, tmm: 1).

Both records should point to the same pool member.

Using the following command provides a more detailed view and perhaps you spot another difference in case my assumption is wrong: 

tmsh show ltm persist persist-records all-properties

Thanks, Stephan