Rate classes with inbound/outbound rate limits

Hi Srikanth,

After some testing, it doesn't look like my original solution is going to work for you. We need to change the way that we target the "backend virtual" to make this work. Instead of sending the traffic to a pool containing the "backend" virtual server, we'll use an iRule to select the "backend" virtual server.

1. Remove the pool containing the "backend" from the "frontend" virtual server.

2. Create the following iRule:

when CLIENT_ACCEPTED {
    virtual "backend_virtual_server"
}

3. Assign the iRule to the "frontend" virtual server.

After that you should have a normal "backend" virtual server that looks pretty basic plus the outbound rate class. The "frontend" virtual server will have the iRule, the inbound rate class, and any necessary profiles.

The performance hit from this solution should not be bad. You're already limiting the throughput with the rate class and the latency should not change significantly.

Sorry for the confusion,

-George