•
Default Precedence: 0
•
Maximum Precedence: 7
As described above, the Default Precedence is the precedence taken by a packet if it is not explicitly
assigned by a pipe rule.
The minimum and maximum precedences define the precedence range that the pipe will handle. If a
packet arrives with an already allocated precedence below the minimum then its precedence is
changed to the minimum. Similarly, if a packet arrives with an already allocated precedence above
the maximum, its precedence is changed to the maximum.
For each pipe, separate bandwidth limits may be optionally specified for each precedence level.
These limits can be specified in kilobits per second and/or packets per second (if both are specified
then the first limit reached will be the limit used).
Tip: Specifying bandwidth
Remember that when specifying network traffic bandwidths, the prefix Kilo means
1000 and NOT 1024. For example, 3 Kbps means 3000 bits per second.
Similarly, the prefix Mega means one million in a traffic bandwidth context.
Precedence Limits are also Guarantees
A precedence limit is both a limit and a guarantee. The bandwidth specified for precedence also
guarantees that the bandwidth will be available at the expense of lower precedences. If the specified
bandwidth is exceeded, the excess traffic falls to the lowest precedence. The lowest precedence has
a special meaning which is explained next.
The Lowest (Best Effort) Precedence
The precedence which is the minimum (lowest priority) pipe precedence has a special meaning: it
acts as the Best Effort Precedence. All packets processed at this precedence will always be
processed on a "first come, first forwarded" basis.
Packets with a higher precedence than best effort and that exceed the limit of their precedence will
automatically be transferred down into the lowest (best effort) precedence and they are treated the
same as other packets at the lowest precedence.
In the illustration below the minimum precedence is 2 and the maximum precedence is 6.
Precedence 2 is taken as the best effort precedence.
10.1.6. Precedences
Chapter 10. Traffic Management
459
Содержание NetDefend DFL-260E
Страница 27: ...1 3 NetDefendOS State Engine Packet Flow Chapter 1 NetDefendOS Overview 27...
Страница 79: ...2 7 3 Restore to Factory Defaults Chapter 2 Management and Maintenance 79...
Страница 146: ...3 9 DNS Chapter 3 Fundamentals 146...
Страница 227: ...4 7 5 Advanced Settings for Transparent Mode Chapter 4 Routing 227...
Страница 241: ...5 4 IP Pools Chapter 5 DHCP Services 241...
Страница 339: ...6 7 Blacklisting Hosts and Networks Chapter 6 Security Mechanisms 339...
Страница 360: ...7 4 7 SAT and FwdFast Rules Chapter 7 Address Translation 360...
Страница 382: ...8 3 Customizing HTML Pages Chapter 8 User Authentication 382...
Страница 386: ...The TLS ALG 9 1 5 The TLS Alternative for VPN Chapter 9 VPN 386...
Страница 439: ...Figure 9 3 PPTP Client Usage 9 5 4 PPTP L2TP Clients Chapter 9 VPN 439...
Страница 450: ...9 7 6 Specific Symptoms Chapter 9 VPN 450...
Страница 488: ...10 4 6 Setting Up SLB_SAT Rules Chapter 10 Traffic Management 488...
Страница 503: ...11 6 HA Advanced Settings Chapter 11 High Availability 503...
Страница 510: ...12 3 5 Limitations Chapter 12 ZoneDefense 510...
Страница 533: ...13 9 Miscellaneous Settings Chapter 13 Advanced Settings 533...