Forum Discussion
yoshijo_100578
Nimbostratus
Feb 11, 2008Issue about Session Persistence Problem
I'm trying to deploy LTM 9.4.1 Build 29.2 clustering mode, and my environment like this...
VIP 192.168.100.1:80 SNAT automap
VIP 192.168.100.1:443 SNAT automap
and pool
...
hoolio
Cirrostratus
Feb 11, 2008Hello,
Intermittent persistence failure can be caused by a pool member being marked down. Also, you might find that you need a OneConnect profile, if multiple HTTP requests from different clients are being made over the same TCP connection to the virtual server.
You can write out the persistence table records using the following command (all on one line):
while true; do echo "--------------------"; date; b persist all show all; sleep 1; done | tee -a /var/tmp/b.persist.all.out
If you're able to reproduce the failure, you could log the persistence table output to a file to see what the BIG-IP sees when the failure occurs. It might also help to capture a tcpdump while testing.
Aaron
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects
