Forum Discussion
Hamish
May 11, 2010Cirrocumulus
Hi Defra.
What you want is 3 rate classes for this (If you're doing it statically).
1. global_rate. With 40Mbps (Assuming they meant Mbps and not MBps here...)
2. http_rate, a child of global_rate, with 30Mbps limit, but a burst of 40Mbps, no limit on the burst.
3. ftp_rate, a child of global_rate, with 10Mbps limit, (No burst allowed)
Then also set a minimum of 30Mbps and 10Mbps respectively on the http and ftp rate classes...
So what you should get here is http_rate able to burst to 40Mbps unless ftp_rate wants it. Because ftp_rate gets a guaranteed 10Mbps, the rate that http can get will be reduced by 10Mbps from the burstable 40Mbps down to the target 30Mbps. ftp has no burst so cant' go above 10Mbps, and http then gets the 30Mbps that is required.
Again, as hoolio suggested attach each rate to the respective VS's... More granularity requires more rate classes and an iRule to decide which of the rate classes the connection should be associated with. But if granularity is not required, then you don't need any iRules.
H