QoS Policies Tab

Configuration > QoS Policies

The QoS Policy determines how flows are queued and marked.

The QoS Policies tab displays the QoS policy entries that exist on the appliances.

This includes the appliance-based defaults, entries applied manually (via the WebUI or CLI), and entries that result from applying a Orchestrator QoS Policy template.

Both the Shaper and the QoS Policy deal with traffic classes. How are they related?

>> The Shaper defines and the QoS Policy assigns. <<

Use the Templates tab to create and manage QoS policies for multiple appliances, or click the Edit icon to manage QoS Policies directly for a particular appliance.

The QoS Policy's SET actions determine two things:

n	to what traffic class a shaped flow -- optimized or pass-through -- is assigned

n	whether to trust incoming DSCP markings for LAN QoS and WAN QoS, or to remark them as they leave for the WAN

Priority

n	You can create rules with any priority between 1 and 65534.

•	If you are using Orchestrator templates to add route map entries, the Orchestrator will delete all entries from 1000 – 9999, inclusive, before applying its policies.

•	You can create rules from 1 – 999, which have higher priority than Orchestrator template rules.

•	Similarly, you can create rules from 10000 – 65534 which have lower priority than Orchestrator template rules.

n	Adding a rule increments the last Priority by 10. This leaves room for you to insert a rule in between rules without having to renumber subsequent priorities. Likewise, you can just edit the number.

Source or Destination

n	An IP address can specify a subnet - for example: 10.10.10.0/24 (IPv4) or fe80::204:23ff:fed8:4ba2/64 (IPv6).

n	To allow any IP address, use 0.0.0.0/0 (IPv4) or ::/0 (IPv6).

n	Ports are available only for the protocols tcp, udp, and tcp/udp.

n	To allow any port, use 0.

Please send comments or suggestions regarding user documentation to techpubs@silver-peak.com.