Saving pools to persistence table when it's not the LB default

I'm not sure how there would ever be two persistence records for the same client as defined by the source IP and user-agent string with different values. I could see that the timeout of 60 seconds might be too short and a client would make a request more than a minute after the previous request. That would mean the previous persistence record would be removed and the subsequent request could be sent to the other pool.

 

 

Can you reproduce this consistently enough to capture a tcpdump of the failure? If so, you might consider opening a support case on the issue. It would probably help to add logging to the rule of the client IP address, user-agent string, the persistence record that's found and the selected pool and pool member. The output from 'b persist all show all' might help as well. You can write out the persistence records to a file every 5 seconds using a while loop on the CLI:

 

 

interval=5; output=/var/tmp/b.persist.out; while true; echo -e "\n======================`date +%Y%m%d-%H%M`======================\n" >> $output; do b persist all show all >> $output; sleep $interval; done &

 

 

Make sure to get it on a single line. The script will run in the background. It will write out the output from ‘b persist all show all’ every 5 seconds (or whatever number you set interval to). The output is written to /var/tmp/b.persist.out (or whatever you set output to).

 

 

The & at the end of the line sets the command to run in the background, so you can log out of your SSH session and it won’t affect the running of the command.

 

 

To stop the command from running, log back into the BIG-IP via SSH and run ‘kill %1’ without the single quotes. Make absolutely sure to type exactly kill %1.

 

 

Aaron