Forum Discussion
Nikoolayy1
MVP
Better check from the servers whuch process causes the issue not on the F5. The issue could be that F5 now uses more complex SSL ciphers or something needs to be changed in the server side TCP profile on the F5 device to optimize the traffic.
https://support.f5.com/csp/article/K50411377
https://support.f5.com/csp/article/K72605755
Still check the F5 LTM logs for some new errors with the VIP/nodes/pools/poolmembers and also see the f5 interfaces for some errors just in case.
dhubick
May 06, 2022Altocumulus
Best I can tell, it was using "ECDHE-RSA-AES128-GCM-SHA256" before and after upgrade.
Thanks for the leads though. Still checking into TCP profiles.