Page 66 / 90
Scroll up to view Page 61 - 65
User Manual
Page 66
of 90
Example 1: HTB Queue Discipline Enabled
In the example below, HTB Queue Discipline is enabled. The PPPoE1 connection has a
total of 300 Kbps of bandwidth, of which 100 Kbps is given to CoS1 and another 100 Kbps
is given to CoS2. When there is no CoS1 or CoS2 packets, CoS6 packets have the whole
300 Kbps of bandwidth.
HTB Queue Discipline enabled
HTB Queue Discipline enabled
HTB Queue Discipline enabled
HTB Queue Discipline enabled
Page 67 / 90
User Manual
Page 67
of 90
Example 2: Low Latency Queue Discipline Enabled
In this second example, Low Latency Queue Discipline is enabled. CoS1 is not rate
controlled (hence the field is disabled). CoS2 takes 100 Kbps when there is no CoS1
packet. CoS6 has 300 Kbps when there is no CoS1 or CoS2 packets. This is similar to the
HTB queue discipline as they are both rate-based algorithm, except that CoS1 is handled
differently.
Low Latency Queue Discipline enabled
Low Latency Queue Discipline enabled
Low Latency Queue Discipline enabled
Low Latency Queue Discipline enabled
Page 68 / 90
User Manual
Page 68
of 90
Example 3: PRIOWRR Enabled
In this third example, PRIOWRR is enabled. Since PRIOWRR operates only on the number
of packets being transmitted, the max rate field has been disabled. Only percentage can
be assigned to the CoS2 - CoS6. CoS1 is not rate controlled (hence the field is not
displayed). When there is no CoS1 packet, CoS2, CoS3, CoS4 each has 10 percent, and
CoS6 has 70 percent. This is similarly to the Low Latency Queue discipline, except that
one is packet-based, and the other is rate-based.
PRIOWRR enabled
PRIOWRR enabled
PRIOWRR enabled
PRIOWRR enabled
Page 69 / 90
User Manual
Page 69
of 90
Policy Routing Configuration
The Policy Routing Configuration page is accessed by selecting Policy Routing
Configuration on the Advanced home page under QoS. This page enables you to
configure policy routing and QoS. The policy routing configuration is discussed as follows.
The QoS configuration is discussed in ‘‘Ingress Payload Database Configuration’’.
Policy Routing Configuration
Policy Routing Configuration
Policy Routing Configuration
Policy Routing Configuration
Currently routing algorithms make decision based on destination address, i.e. only
Destination IP address and subnet mask is supported. The Policy Routing page enables
you to route packets on the basis of various fields in the packet. The following fields can
be configured for Policy Routing:
°
Destination IP address/mask
°
Source IP address/mask
°
Source MAC address
°
Protocol (TCP, UDP, ICMP, etc)
°
Source port
19216811.live