06-25-2013 03:46 PM
The rate class limits are counted and applied per-Stingray-instance. In an active/active cluster, one option would be to configure the rate limit to half the value you want; assuming even traffic distribution across the cluster, this would give you the effect you need. If you need a very strictly-applied rate limit, you would be better to run active-passive with respect to the traffic that should be limited.
One additional observation - the bandwidth classes can be configured to operate across the cluster; in an active-active scenario, the traffic managers continually negotiate to get an appropriate share of the total bandwidth allocation.
06-26-2013 02:04 AM
> Is this stated in the documentation?
Only by omission. I've updated Feature Brief: Bandwidth and Rate Shaping in Stingray Traffic Manager to make it known.