no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
| — | documentation:introduction [2014-01-25 12:04] (current) – created nkukard | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | =====Terms Used===== | ||
| + | |||
| + | ====CIR==== | ||
| + | |||
| + | Commit information rate, this is the rate that is guaranteed to a specific class or pool. The sum of all CIRs of any child item should not exceed the parent CIR, unless you know 100% what you're doing. | ||
| + | |||
| + | ====Limit (bandwidth term)==== | ||
| + | |||
| + | This is the maximum rate that a class or pool can consume. The sum lf all limits of child items should not exceed that of the parent Limit, again unless you know 100% what you're doing. | ||
| + | |||
| + | ====Rate==== | ||
| + | |||
| + | The rate refers to the current traffic speed seen for the class or pool | ||
| + | |||
| + | ====PPS==== | ||
| + | |||
| + | PPS stands for packets per second, this is how many packets are seen for the class or pool per second. | ||
| + | |||
| + | ====Class==== | ||
| + | |||
| + | A traffic class refers to a number of " | ||
| + | |||
| + | ====Pool==== | ||
| + | |||
| + | Pools contain pool members. Pools have a CIR and Limit set to ensure their pool members do not exceed this. | ||
| + | |||
| + | ====Pool Member==== | ||
| + | |||
| + | Pool members are current users and/or IP addresses. Any number of pool members can be added to a pool. All these pool members traffic is treated equally by the pool and the limit applied to it as a whole. | ||
| + | |||
| + | ====Limit (configuration page "Add Limit" | ||
| + | |||
| + | A limit in the configuration sense refers to adding a pool and pool member at the same time, simplifying the configuration process. | ||
| + | |||