Configure Quality of Service options

Quality of Service (QoS) options allow you to manage the traffic performance of various services, such as Voice over IP (VoIP), cloud computing, traffic shaping, traffic prioritizing, and bandwidth allocation. When configuring QOS, you can only control the queue for outgoing packets on each interface (egress packets), not what is received on the interface (packet ingress).

A QoS binding contains the policies and rules that apply to packets exiting the IX15 device on the binding's interface. By default, the IX15 device has two preconfigured QoS bindings, Outbound and Inbound. These bindings are an example configuration designed for a typical VoIP site:

Outbound provides an example of matching packets as they are routed from the device onto the WAN interface.
Inbound provides an example of matching packets as they are routed from the device onto a LAN interface.

These example bindings are disabled by default.

Enable the preconfigured bindings

Create a new binding

 Web

Log into Digi Remote Manager, or log into the local Web UI as a user with full Admin access rights.
Access the device configuration:
Remote Manager:
1. Locate your device as described in Use Digi Remote Manager to view and manage your device.
2. Click the Device ID.
3. Click Settings.
4. Click to expand Config.
Local Web UI:
1. On the menu, click System. Under Configuration, click Device Configuration.
  The Configuration window is displayed.
Click Firewall > Quality of Service.
For Add Binding, click .

The quality of service binding configuration window is displayed.
Enable the binding.
(Optional) Type a Label for the binding.
Select an Interface to queue egress packets on. The binding will only match traffic that is being sent out on this interface.
(Optional) For Interface bandwidth (Mbit), set the maximum egress bandwidth of the interface, in megabits, allocated to this binding. Typically, this should be 95% of the available bandwidth. Allowed value is any integer between 1 and 1000.
Create a policy for the binding:
At least one policy is required for each binding. Each policy can contain up to 30 rules.
1. Click to expand Policy.
2. For Add Policy, click .
  
  The QoS binding policy configuration window is displayed.
  
  New QoS binding policies are enabled by default. To disable, toggle off Enable.
3. (Optional) Type a Label for the binding policy.
4. For Weight, type a value for the amount of available bandwidth allocated to the policy, relative to other policies for this binding.
  The larger the weight, with respect to the other policy weights, the larger portion of the maximum bandwidth is available for this policy. For example, if a binding contains three policies, and each policy contains a weight of 10, each policy will be allocated one third of the total interface bandwidth.
5. For Latency, type the maximum delay before the transmission of packets. A lower latency means that the packets will be scheduled more quickly for transmission.
6. Select Default to identify this policy as a fall-back policy. The fall-back policy will be used for traffic that is not matched by any other policy. If there is no default policy associated with this binding, packets that do not match any policy rules will be dropped.
7. If Default is disabled, you must configure at least one rule:
  1. Click to expand Rule.
  2. For Add Rule, click .
    
    The QoS binding policy rule configuration window is displayed.
    New QoS binding policy rules are enabled by default. To disable, toggle off Enable.
  3. (Optional) Type a Label for the binding policy rule.
  4. For Type Of Service, type the value of the Type of Service (ToS) packet header that defines packet priority. If unspecified, this field is ignored.
    See https://www.tucny.com/Home/dscp-tos for a list of common TOS values.
  5. For Protocol, select the IP protocol matching criteria for this rule.
  6. For Source port, type the port, or any, as a source traffic matching criteria.
  7. For Destination port, type the port, or any, as a destination traffic matching criteria.
  8. Click to expand Source address and select the Type:
    - Any: Source traffic from any address will be matched.
    - Interface: Only traffic from the selected Interface will be matched.
    - IPv4 address: Only traffic from the IP address typed in IPv4 address will be matched. Use the format IPv4_address[/netmask], or use any to match any IPv4 address.
    - IPv6 address: Only traffic from the IP address typed in IPv6 address will be matched. Use the format IPv6_address[/prefix_length], or use any to match any IPv6 address.
    - MAC address: Only traffic from the MAC address typed in MAC address will be matched.
  9. Click to expand Destination address and select the Type:
    - Any: Traffic destined for anywhere will be matched.
    - Interface: Only traffic destined for the selected Interface will be matched.
    - IPv4 address: Only traffic destined for the IP address typed in IPv4 address will be matched. Use the format IPv4_address[/netmask], or use any to match any IPv4 address.
    - IPv6 address: Only traffic destined for the IP address typed in IPv6 address will be matched. Use the format IPv6_address[/prefix_length], or use any to match any IPv6 address.
  Repeat to add a new rule. Up to 30 rules can be configured.
Click Apply to save the configuration and apply the change.

 Command line

Select the device in Remote Manager and click Actions > Open Console, or log into the IX15 local command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection menu. Type admin to access the Admin CLI.
At the command line, type config to enter configuration mode:
```
> config
(config)>
```

Add a binding:

(config)> add firewall qos end
(config firewall qos 2)>

New binding are enabled by default. To disable:

(config firewall qos 2)> enable false
(config firewall qos 2)>

(Optional) Set a label for the new binding:

(config firewall qos 2)> label my_binding
(config firewall qos 2)>

Set the interface to queue egress packets on. The binding will only match traffic that is being sent out on this interface:
1. Use the ? to determine available interfaces:
2. Set the interface. For example:
```
(config firewall qos 2)> interface /network/interface/eth1
(config firewall qos 2)>
```
(Optional) Set the maximum egress bandwidth of the interface, in megabits, allocated to this binding.
```
(config firewall qos 2)> bandwidth int
(config firewall qos 2)> 
```
where int is an integer between 1 and 1000. Typically, this should be 95% of the available bandwidth. The default is 95.
Create a policy for the binding:
At least one policy is required for each binding. Each policy can contain up to 30 rules.
1. Change to the policy node of the configuration:
```
(config firewall qos 2)> policy
(config firewall qos 2 policy)> 
```
2. Add a policy:
```
(config firewall qos 2 policy)> add end
(config firewall qos 2 policy 0)> 
```
  New QoS binding policies are enabled by default. To disable:
```
(config firewall qos 2 policy 0)> enable false
(config firewall qos 2 policy 0)> 
```
3. (Optional) Set a label for the new binding policy:
```
(config firewall qos 2 policy 0)> label my_binding_policy
(config firewall qos 2 policy 0)> 
```
4. Set a value for the amount of available bandwidth allocated to the policy, relative to other policies for this binding.
  The larger the weight, with respect to the other policy weights, the larger portion of the maximum bandwidth is available for this policy. For example, if a binding contains three policies, and each policy contains a weight of 10, each policy will be allocated one third of the total interface bandwidth.
```
(config firewall qos 2 policy 0)> weight int
(config firewall qos 2 policy 0)> 
```
  where int is any integer between 1 and 65535. The default is 10.
5. Set the maximum delay before the transmission of packets. A lower number means that the packets will be scheduled more quickly for transmission.
```
(config firewall qos 2 policy 0)> latency int
(config firewall qos 2 policy 0)> 
```
  where int is any integer, 1 or greater. The default is 100.
6. To identify this policy as a fall-back policy:
```
(config firewall qos 2 policy 0)> default true
(config firewall qos 2 policy 0)> 
```
  The fall-back policy will be used for traffic that is not matched by any other policy. If there is no default policy associated with this binding, packets that do not match any policy rules will be dropped. If the policy is not a fall-back policy, you must configure at least one rule:
  1. Change to the rule node of the configuration:
```
(config firewall qos 2 policy 0)> rule
(config firewall qos 2 policy 0 rule)> 
```
  2. Add a rule:
```
(config firewall qos 2 policy 0 rule)> add end
(config firewall qos 2 policy 0 rule 0)> 
```
    New QoS binding policy rules are enabled by default. To disable:
```
(config firewall qos 2 policy 0 rule 0)> enable false
(config firewall qos 2 policy 0 rule 0)> 
```
  3. (Optional) Set a label for the new binding policy rule:
```
(config firewall qos 2 policy 0 rule 0)> label my_binding_policy_rule
(config firewall qos 2 policy 0 rule 0)> 
```
  4. Set the value of the Type of Service (ToS) packet header that defines packet priority. If unspecified, this field is ignored.
```
(config firewall qos 2 policy 0 rule 0)> tos value
(config firewall qos 2 policy 0 rule 0)> 
```
    where value is a hexadecimal number. See https://www.tucny.com/Home/dscp-tos for a list of common TOS values.
  5. Set the IP protocol matching criteria for this rule:
```
(config firewall qos 2 policy 0 rule 0)> protocol value
(config firewall qos 2 policy 0 rule 0)> 
```
    where value is one of tcp, udp, or any.
  6. Set the source port to define a source traffic matching criteria:
```
(config firewall qos 2 policy 0 rule 0)> srcport value
(config firewall qos 2 policy 0 rule 0)> 
```
    where value is the IP port number, a range of port numbers using the format IP_port-IP_port, or any.
  7. Set the destination port to define a destination matching criteria:
```
(config firewall qos 2 policy 0 rule 0)> dstport value
(config firewall qos 2 policy 0 rule 0)> 
```
    where value is the IP port number, a range of port numbers using the format IP_port-IP_port, or any.
  8. Set the source address type:
```
(config network qos 2 policy 0 rule 0)> src type value
(config network qos 2 policy 0 rule 0)> 
```
    where value is one of:
    - any: Source traffic from any address will be matched.
      See Firewall configuration for more information about firewall zones.
    - interface: Only traffic from the selected interface will be matched. Set the interface:
    - address: Only traffic from the IP address typed in IPv4 address will be matched. Set the address that will be matched:
```
(config network qos 2 policy 0 rule 0)> src address value
(config network qos 2 policy 0 rule 0)> 
```
      where value uses the format IPv4_address[/netmask], or any to match any IPv4 address.
    - address6: Only traffic from the IP address typed in IPv6 address will be matched. Set the address that will be matched:
```
(config network qos 2 policy 0 rule 0)> src address6 value
(config network qos 2 policy 0 rule 0)> 
```
      where value uses the format IPv6_address[/prefix_length], or any to match any IPv6 address.
    - mac: Only traffic from the MAC address typed in MAC address will be matched. Set the MAC address to be matched:
```
(config network qos 2 policy 0 rule 0)> src mac MAC_address
(config network qos 2 policy 0 rule 0)> 
```
  9. Set the destination address type:
```
(config network qos 2 policy 0 rule 0)> dst type value
(config network qos 2 policy 0 rule 0)> 
```
    where value is one of:
    - any: Traffic destined for anywhere will be matched.
      See Firewall configuration for more information about firewall zones.
    - interface: Only traffic destined for the selected Interface will be matched. Set the interface:
    - address: Only traffic destined for the IP address typed in IPv4 address will be matched. Set the address that will be matched:
```
(config network qos 2 policy 0 rule 0)> src address value
(config network qos 2 policy 0 rule 0)> 
```
      where value uses the format IPv4_address[/netmask], or any to match any IPv4 address.
    - address6: Only traffic destined for the IP address typed in IPv6 address will be matched. Set the address that will be matched:
```
(config network qos 2 policy 0 rule 0)> src address6 value
(config network qos 2 policy 0 rule 0)> 
```
      where value uses the format IPv6_address[/prefix_length], or any to match any IPv6 address.
  Repeat to add a new rule. Up to 30 rules can be configured.
Save the configuration and apply the change.
```
(config)> save
Configuration saved.
>
```
Type exit to exit the Admin CLI.
Depending on your device configuration, you may be presented with an Access selection menu. Type quit to disconnect from the device.