Qos Classes; Default Qos Classes - Nokia IP40 User Manual

7
Quality of Service
classes according to the weight. Considering the importance of the traffic, you may assign
weight to each class.
For example:
Web traffic is deemed three times important as FTP traffic and the weight assigned is 30.
FTP traffic is assigned a weight of 10.
When the network is congested, traffic shaper maintains the ratio of bandwidth allocation among
web traffic and FTP traffic as 3:1.
Traffic shaper divides the remaining bandwidth among the other classes based on the weight
assigned to them. If only Web traffic and FTP are active and competing in the entire network,
then the remaining available bandwidth allocated will be 75% and 25% respectively. If Web
traffic closes, FTP traffic receives 100% of the bandwidth. Traffic shaper supports
Differentiated Services (DiffServ) packet marking. Packets are marked according to the QoS
class they belong to. These packets are then granted priority on the public network according to
their class.
Note
To enable traffic shaper, see

QoS Classes

You can define different QoS classes based on your requirement. You can assign a bandwidth
limit to each class. This limit acts as the maximum bandwidth limit for all the connections under
this class. Once a class reaches this set limit, no connections of this class will be allocated any
bandwidth, even if unused bandwidth is available. You can also set delay sensitivity, which
indicates whether connections belonging to one class should be allowed to precede the
connections belonging to other classes.
Nokia IP40 supports four default QoS classes and support a maximum of eight user-defined QoS
classes.
Note
To assign traffic to the QoS classes, define an Allow or Allow and Forward firewall rule.

Default QoS Classes

Nokia IP40 supports the following four predefined (default) QoS classes.
118
""Configuring an Internet Connection"
Nokia IP40 Security Platform User's Guide v2.0
on page 73.