For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

cgrieves_14587's avatar
cgrieves_14587
Icon for Nimbostratus rankNimbostratus
Jul 28, 2010

Rate limiting and pool redirection

We've got a client-facing application server pool sitting behind a Brocade SLB. Everything works fine, but we are vulnerable to clients who cache our product availability and overload the farm, which causes disruption to all clients. Currently we manage this manually, by creating redirection rules based on source IP. Is it possible with F5 products (and presumably iRules) to configure a transaction rate limit, above which specific clients (identified by IP address) can be transparently redirected to a second server pool, thereby protecting "well behaved" clients?
basic
getting started
new to f5

1 Reply

  • Hamish's avatar
    Hamish
    Icon for Cirrocumulus rankCirrocumulus
    Sep 02, 2010
    Yep.

     

     

    In fact there's several request rate limiting iRules in the codeshare... All you'll have to do is marry some of that up with a quick lookup table (Supplied via a DataGroup - always my first choice instead of hard-coding) and you'll be away laughing.

     

     

    IIRC the iRUles you'll want to look at are Version_9_Throttle_on_Requests_Per_Second, HTTPRequestTthrottle and HTTP_throttle_alternative

     

     

    (There are others as well).

     

     

    H