Forum Discussion
Switching boot image
ok, so the issue resolved? 😊
It stopped logging in /var/log/ltm but now when i running my load-test with 500k TCP connection with 800/s rate then some of my tcp connection not getting through and client saying failed to connect.
I have tried bunch of new TCP profile, buffer adjustment and all short of thing but no improvement but then i decided to add more SNAT ip in pool and that works i didn't get error of connection failure so i thought let me load more tcp connection so i start my load-testing with 600k tcp connection with 800/s rate and that test failed again with connection failure, so trying to understand why SNAT source port starving? I have check connection table and its not using all 64k ports but still something somewhere not right. Do you have any clue to trace this kind of issue? I may enable TCP reset cause logs and see..
- JoernApr 16, 2020Altostratus
what kind of test is this? sometimes it can be problem with the application that it has fixed source port area e.g. 3CX Voip Client
- tux143Apr 16, 2020Cirrus
We have 4 mongooseIM server behind F5 and bunch of xmpp clients sending xmpp traffic like text messages etc.. to simulate production workload. my goal is to run 1 million clients (tcp connection) with 1000/s rate.
(i have run same workload without F5 and its successful like all client sending traffic directly to mongooseIM nodes using scripted way to load-balance connection but my goal is to run them behind F5 for many reason.
We have all TCP application no more UDP or SIP style traffic which need special care of source port preservation.
Recent Discussions
Related Content
* 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