QoS Policies Template

The QoS Policy determines how flows are queued and marked.

The QoS Policy's SET actions determine two things:

•	what traffic class a shaped flow -- whether optimized or pass-through -- is assigned

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

Use the Shaper to define, prioritize, and name traffic classes.

Think of it as the Shaper defines and the QoS Policy assigns.

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 rules.

•	Similarly, you can create rules from 10000 – 65534 which have lower priority than Orchestrator 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.

n	To allow any IP address, use 0.0.0.0/0.

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

n	To allow any port, use 0.

Handling and Marking DSCP Packets

n	DSCP markings specify end-to-end QoS policies throughout a network.

n	The default values for LAN QoS and WAN QoS are trust-lan.

Applying DSCP Markings to Optimized (Tunnelized) Traffic

n	The appliance encapsulates optimized traffic. This adds an IP outer header to packets for travel across the WAN. This outer header contains the WAN QoS DSCP marking.

n	LAN QoS – the DSCP marking applied to the IP header before encapsulation

n	WAN QoS – the DSCP marking in the encapsulating outer IP header. The remote appliance removes the outer IP header.

 

 

 

Applying DSCP Markings to Pass-through Traffic

n	The appliance applies the QoS Policy's DSCP markings to all pass-through flows -- shaped and unshaped.

n	Pass-through traffic doesn't receive an additional header, so it's handled differently:

•	The Optimization Policy's LAN QoS Set Action is ignored.

•	The specified WAN QoS marking replaces the packet's existing LAN QoS DSCP marking.

•	When the packet reaches the remote appliance, it retains the modified QoS setting as it travels to its destination.

 

 

 

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