Traffic grouped by ip address – Amer Networks E5Web GUI User Manual
Page 671

In addition to, or as an alternative to the total group limit, individual precedences can have
values specified. These values are, in fact, guarantees (not limits) for each user in a group. For
example, precedence 3 might have the value 50 Kbps and this is saying that an individual
user (in other words, each source IP if that is the selected grouping) with that precedence will
be guaranteed 50 Kbps at the expense of lower precedences.
The precedences for each user must be allocated by different pipe rules that trigger on
particular users. For example, if grouping is by source IP then different pipe rules will trigger
on different IPs and send the traffic into the same pipe with the appropriate precedence.
The potential sum of the precedence values could clearly become greater than the capacity
of the pipe in some circumstances so it is important to specify the total pipe limit when using
these guarantees.
Combining the Group Total and Precedences
Use of group precedences and the group total can be combined. This means that:
•
The users in a group are first separated by pipe rules into precedences.
•
The users are then subject to the guarantees specified for their precedence.
•
The combined traffic is subject to the total group limit.
The illustration below shows this flow where the grouping has been selected to be according to
source IP.
Figure 10.6. Traffic Grouped By IP Address
Another Simple Groups Example
Consider another situation where the total bandwidth limit for a pipe is 400 Kbps. If the aim is to
allocate this bandwidth amongst many destination IP addresses so that no single IP address can
take more than 100 Kbps of bandwidth, the following steps are needed.
Chapter 10: Traffic Management
671