Concurrent SSL-Sessions & Visibility
Hi, a customer just asked a simple question, for which I couldn't find any information on the fly. "How many concurrent SSL sessions can be handled by an i2600?" (not TPS!) The TPS values can be found in the datasheet (2.5K RSA-2048), and also the max. L4 connections (14M). I could only find an FAQ for the 1600/3400 models of a czech vendor, that shows these numbers that I'm looking for. (here) The numbers for "Max. SSL Concurrent Connections" seem to correlate with the "Max. Concurrent Connections" by a factor of 1:8. So for an i2600 (14M MCC) this would result in 1.75M MSSLCC. But that's just random guessing based on an unofficial(?) document... Is there any official evidence or documentation/description for that? Also, is it possible to monitor the concurrent SSL-connections in Dashboard or in any statistics? Cause I see the normal connections, and the SSL TPS, but not the concurrent SSL connections for the system... Thanks in advance!
LTM excessive connections on Virtual Server
My Virtual Server is showing 460 connections but the pool members aare only showing 50 connections. I have checked the source addresses of these connections and they are all different. I have deleted the connections but they build up again to the same amount. I have changed the DNS record of the Virtual Server to another LTM but the connections follow it across. How can I permanently delete these connections?
How does the F5 compute for the Connections(Current, Maximum and Total)
Hi Guys, Would like to ask if How does the F5 compute for the Connections(Current, Maximum and Total)? is it based on the time out settings you set? Can you also define the differences of the 3? I do have an idea not sure though if its correct. Please correct me if I'm wrong Current - Real time connections Maximum - Maximum connection reach within the time out set? Total - Total connections pool have within the time out? Thank you!
Leveraging SSL connections between BIG IP LTM and backend servers
Hi Team, I have a scenario, wherein the SSL worker threads on the backend servers are being exhausted while processing all the SSL requests between BIG-LTM and the backend servers. I'm looking at some options/settings on BIGIP which can leverage already open SSL connections with backend servers so as to not bombard the backend servers with too many SSL handshake requests. I see OneConnect profile can leverage the already existing idle connections between LTM and backend server but not sure if it can used for leveraging open SSL connections as well. The idea is to reduce the number of encryption/decryption mechanism on the backend server. Can anyone provide their expertise to achieve this. BR, MSKClient connections increased dramatically after enabling oneconnect
Hi folks, I am very puzzled by what I am seeing here. I enabled oneconnect on three virtual servers which are serving http traffic. I configured a customized version of the tcp-lan-optimized profile which only changed the Proxy Buffer High and Low levels to match our traffic, and a oneconnect profile which only changes the Maximum Reuse to slightly below the HTTP KeepAlive on our web servers. That said, I've also tried the default profiles, and had the same results. After enabling oneconnect, new connections to our backend servers dropped significantly as expected; however, the number of active connections roughly tripled. It appears to be client connections. When I check the virtual server statistics, the three virtual servers have a combined 22.5K current connections; however, when I check the pool which all three use, it only lists around 800 active connections. What could have caused this jump? It appears that traffic is being served properly, but I am concerned as to what this means. Thanks in advance for your advice.
