Our SysAdmin team has reported a sharp increase in CPU usage on the nodes in our ltm pools after upgrading to BIG-IP 16.2.1. from 14.2.1. The servers are maintained by a different team, but I can confirm they are running Apache 2.2.27
Has anyone experienced similar outcomes during upgrades?
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.
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.
Sorry I couldn't follow the context, is the load high on the servers or on the F5 ?
If it's on the F5, run the top cmd and see which deamon is causing it. See if it's the odd or even cores, so that we'll know if it's the tmm or non tmm.
Some good feedback here. I'd add:
THE Jason Rahm? I'm honoured! I enjoy your Lightboard Lessons.
We updated from 18.104.22.168 to 22.214.171.124 this week. Can you guess what day it was?
So, the resolution is updating to 126.96.36.199, but I am still investigating to determine a root cause. I have not had a chance to compare before/after packet captures yet.
One detail I left out of the initial post- these apache webservers are Identity proxies that sit in our DMZ and forward traffic between our external f5 hosts and our internal f5 hosts.
I had assumed that the high CPU was caused by the external f5 hosts forwarding to the Identity proxies. But, perhaps it was between the Identity proxies and our internal f5 hosts.