In addition to marking the traffic that leaves a device interface, you can also mark traffic on a per-policy basis. The marking action you select is applied to all traffic that uses the policy. Multiple policies that use the same marking actions have no effect on each other. Device interfaces can also have their own QoS Marking settings. To use QoS Marking or prioritization settings for a policy, you must override any per-interface QoS Marking settings.
The available QoS marking settings depend on the policy type. The H.323 and SIP ALGs have different QoS marking settings than other policies. All policies support DSCP and IP Precedence marking types and these marking methods.
In an ALG, you can assign different marking values to audio, video, and data traffic.
Many different algorithms can be used to prioritize network traffic. Fireware XTM uses the strict priority queuing method to prioritize traffic through your XTM device. Prioritization in Fireware XTM is applied per policy and is equivalent to CoS (class of service) levels 0–7, where 0 is normal priority (default) and 7 is the highest priority. Level 5 is commonly used for streaming data such as VoIP or video conferencing. Reserve levels 6 and 7 for policies that allow system administration connections to make sure they are always available and avoid interference from other high priority network traffic. Use the Priority Levels table in the subsequent section as a guideline when you assign priorities.
You cannot configure prioritization in H.323-ALG and SIP-ALG policies.
We recommend that you assign a priority higher than 5 only to network administration policies, such as the WatchGuard policy or the WG-Mgmt-Server policy. Give high priority business traffic a priority of 5 or lower.
|0||Routine (HTTP, FTP)|
|3||Flash (Telnet, SSH, RDP)|
|6||Internetwork Control (Remote router configuration)|
|7||Network Control (Firewall, router, switch management)|
About QoS Marking