PointRed Telecom Ltd. MCRD-2458 Manuale Utente
M i c r o R e d & M i c r o V i e w N M S U s e r M a n u a l v 1 . 0
Page 93
3.
We drag & drop the previous classes to these new ones to create a class
hierarchy as depicted at picture 88. We also alter the structure of our
policies, so that only the newly created classes are assigned to them.
hierarchy as depicted at picture 88. We also alter the structure of our
policies, so that only the newly created classes are assigned to them.
Figure 88. Class Hierarchy
This way we limit the PIR at parent classes (3000/3500) and then we further
distribute the bandwidth among the child classes (1499/3500 each). So, we
enforce an upper limit on the amount of bandwidth used for FTP traffic, and
at the same time, we enable both FTP Server to use the full potential of the
reserved bandwidth.
distribute the bandwidth among the child classes (1499/3500 each). So, we
enforce an upper limit on the amount of bandwidth used for FTP traffic, and
at the same time, we enable both FTP Server to use the full potential of the
reserved bandwidth.
Note: We couldn't have set a CIR of 1500 on each subclass, because when we
subdivide a class to subclasses, there should always be some bandwidth available to
accommodate for the rest of the traffic (traffic not covered by any of the subclasses).
subdivide a class to subclasses, there should always be some bandwidth available to
accommodate for the rest of the traffic (traffic not covered by any of the subclasses).
9.5.
Example: Elimination of P2P Traffic
Currently, MicroRed does not support filtering of IP traffic based on its Layer 7
properties. For example, you can't set up a firewall rule to block
incoming/outgoing P2P traffic. Nonetheless, you can virtual eliminate it, by
restricting the bandwidth available to it.
properties. For example, you can't set up a firewall rule to block
incoming/outgoing P2P traffic. Nonetheless, you can virtual eliminate it, by
restricting the bandwidth available to it.
In this example we will set up two Traffic Policies, one for each direction, and
two Traffic Classes, that will reduce the bandwidth available to P2P traffic to as
low as Kbits/sec. P2P users will soon get frustrated and drop their P2P
applications altogether. The following pictures demonstrate the QoS
configuration needed.
two Traffic Classes, that will reduce the bandwidth available to P2P traffic to as
low as Kbits/sec. P2P users will soon get frustrated and drop their P2P
applications altogether. The following pictures demonstrate the QoS
configuration needed.