default precedence of 0.
Eight precedences exist, numbered from 0 to 7. Precedence 0 is the least important and 7 is the most
important. A precedence can be viewed as a separate traffic queue; traffic in precedence 2 will be
forwarded before traffic in precedence 0, precedence 4 forwarded before 2.
The meaning of a precedence comes from the fact that it is either higher or lower than another
precedence. If, for example, two precedences are used in a scenario, choosing 4 and 6 instead of 0
and 3 will makes no difference.
Figure 10.3. The Eight Pipe Precedences
Allocating Precedence
The way precedence is assigned to a packet is decided by the Pipe Rule that controls it and is done
in one of three ways:
•
Use the precedence of the first pipe - Each pipe has a default precedence and packets take the
default precedence of the first pipe they pass through.
•
Use the allocated precedence - The Pipe Rule explicitly allocates a precedence.
•
Use the DSCP bits - Take the precedence from the DSCP bits in the packet. DSCP is a subset of
the Diffserv architecture where the Type of Service (ToS) bits are included in the IP packet
header.
Pipe Precedences
When a pipe is configured, a Default Precedence, a Minimum Precedence and a Maximum
Precedence can be specified. The Default Precedence is the precedence taken by a packet if it is not
explicitly assigned by a Pipe Rule as described in the preceding paragraph.
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). If precedences are used then the total limit for the
pipe as a whole must be specified so the pipe knows when what its capacity is and therefore when
precedences are used.
The Best Effort Precedence
10.1.6. Precedences
Chapter 10. Traffic Management
384
Summary of Contents for 800 - DFL 800 - Security Appliance
Page 24: ...1 3 NetDefendOS State Engine Packet Flow Chapter 1 NetDefendOS Overview 24 ...
Page 69: ...2 6 4 Restore to Factory Defaults Chapter 2 Management and Maintenance 69 ...
Page 121: ...3 9 DNS Chapter 3 Fundamentals 121 ...
Page 181: ...4 7 5 Advanced Settings for Transparent Mode Chapter 4 Routing 181 ...
Page 192: ...5 5 IP Pools Chapter 5 DHCP Services 192 ...
Page 282: ...6 7 Blacklisting Hosts and Networks Chapter 6 Security Mechanisms 282 ...
Page 300: ...mechanism 7 3 7 SAT and FwdFast Rules Chapter 7 Address Translation 300 ...
Page 301: ...7 3 7 SAT and FwdFast Rules Chapter 7 Address Translation 301 ...
Page 318: ...8 3 Customizing HTML Pages Chapter 8 User Authentication 318 ...
Page 322: ...ALG 9 1 5 The TLS Alternative for VPN Chapter 9 VPN 322 ...
Page 377: ...Management Interface Failure with VPN Chapter 9 VPN 377 ...
Page 408: ...10 4 6 SLB_SAT Rules Chapter 10 Traffic Management 408 ...
Page 419: ...11 5 HA Advanced Settings Chapter 11 High Availability 419 ...
Page 426: ...12 3 5 Limitations Chapter 12 ZoneDefense 426 ...
Page 449: ...13 9 Miscellaneous Settings Chapter 13 Advanced Settings 449 ...