Forum Discussion

Joe_Lupo_283884's avatar
Joe_Lupo_283884
Icon for Nimbostratus rankNimbostratus
Jan 31, 2017

Virtual Server Connection Rate Limit Reached

Does anyone know how to get a virtual server back to "Available (Enabled) - The virtual server is available" WITHOUT setting the Connection Rate Limit to "0". I saw somewhere that setting the Connection Rate Limit back to "0" as a fix to get the VS back to Available, but I want to keep a Connection Rate Limit on this VS and have it be Available. Currently, even after setting the Connection Rate limit high, the VS returns back to "Unavailable (Enabled) - The virtual server's rate limit has been reached".

 

Any insight??

 

LTM
security

2 Replies

Sort By
  • Vijay_E's avatar
    Vijay_E
    Icon for Cirrus rankCirrus
    Jan 31, 2017

    Don't set the VS limit ;)

     

    Even after reaching the limit, the VS still processes the existing connection. It just won't accept new connections. That is the goal of the VS limit.

     

    If you don't want this specific function, why not remove the VS limit ? If you want to set a connection limit, just make sure the number is higher than normal traffic flow.

     

  • CarloT_354159's avatar
    CarloT_354159
    Icon for Nimbostratus rankNimbostratus
    Oct 24, 2018

    Hi - we are facing the same issue in our Production Environment (TMOS-BIG-IP 12.1.2 Build 2.0.276 Hotfix HF2; 2x BIG-IP 4000 in an Active / Standby Cluster Pair) with one of our Virtual Servers where we enabled the "Connection Limit / Connection Rate Limit" feature; similarly to what Joe Lupo posted, also in our Active / Standby Cluster Setup the "Connection Rate Limit exceeded" notification for the specific Virtual Server is reported only by one of the unit of the Cluster (the unit that we have currently set to Standby), even under low traffic volume.

     

    The other unit (formerly set to "Standby" - now currently running as "Active") do not report any error notification message.

     

    Did you manage to solve the issue ? Is there a way to clear the wrong notification message that is automatically presented on the standby unit of the cluster ? To me it sounds more and more like a Feature Bug. Is there already an entry in the F5's Bug Tracker DB ?

     

    Thanks.