Forum Discussion
Hi Sand87ch,
you could flush your logs via SSH.
[itacs@kw-f5-dev:Active:Standalone] / # > /var/log/ltm
[itacs@kw-f5-dev:Active:Standalone] / # > /var/log/audit
[itacs@kw-f5-dev:Active:Standalone] / # > /var/log/messages
Instead of flushing those logs, you could just use tail your ltm log during your tests to see what happens...
[itacs@kw-f5-dev:Active:Standalone] / # tail -f /var/log/ltm
If the default logs wont give you a clue whats happening, you may turn on TCP-RST logging and repeat the test again...
Configuring the BIG-IP system to log TCP RST packets (f5.com)
Cheers, Kai
Hi Kai,
I will do this.Meanwhile following this doc viz., https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm-implementations-12-1-0/27.html i made some changes and tested.
However still the errors keep coming in jmeter like the screenshot posted yesterday.
I made the changes in my Big IP VE ,nodes and pools.i set the following in my BIGIP VE
And set the request queue depth to yes in pools but without any success.
- Kai_WilkeDec 07, 2022MVP
I would recommend to remove such limits, if you dont have the need to restict one VS from consuming too much network ressources, so that other VS can continue to work stable.
Cheers, Kai