QOS config....

Unanswered Question
Nov 3rd, 2009
User Badges:

Hi...


I am confusing while configuring qos.

This is my present scenarion,

DC ---------SP MPLS---------Branch


I have antivirus server at DC which is used for updating client at Branch.But problem is that at Branch side i have 128 Kb Link.In the morning while updating antivirus my bandwidth is choked up completely.


Is there any workaround for avoiding this kind of problem?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3 (1 ratings)
Loading.
lgijssel Tue, 11/03/2009 - 02:22
User Badges:
  • Red, 2250 points or more

QoS will not really help you. By reducing the bandwidth for update-traffic, the sessions will likely starve before completion.

The only viable solution would be to install a local update server at the branch office.


regards,

Leo

Joseph W. Doherty Tue, 11/03/2009 - 09:32
User Badges:
  • Super Bronze, 10000 points or more

"Is there any workaround for avoiding this kind of problem?"


There may be. Possible solutions depend on your equipment and logical topology.


For instance, if only the DC and branch exchanged traffic, and if your equipement supported it, a hiearchal policy at the DC shaping for 128 Kbps, with the subordinate policy providing the AV update traffic a minimal bandwidth guarantee might do the trick.


i.e.


policy-map shape4branch


class matchBranch

bandwidth 128

shape average 128000

service-policy branchPolicy


policy-map branchPolicy


class AV

bandwidth percent 1


class class-default

fair-queue


If other sites could also send traffic to the branch (common on MPLS clouds), then you would likely need to work with the MPLS vendor's QoS. For such, you would classify AV update to go into the least bandwidth guaranteed class. (BTW, you might still need to priorization QoS at the DC.)

arjunsawant Tue, 11/03/2009 - 19:59
User Badges:

Hi...


Thanx for ur reply..


But where i have to configure these command,

on DC or branch router.Because i have 20 branches which are connected to DC with same scenario and having same problem.


where should i apply this policy on IN/OUT interface and in which direction?

Joseph W. Doherty Wed, 11/04/2009 - 03:24
User Badges:
  • Super Bronze, 10000 points or more

If the issue is only as you describe, you define the policy at the DC for output. If there is no branch-to-branch communication, you would have a class statement to match each branch (normally you match against destination block address), otherwise you just deprioritize the AV traffic into a single class and utilize your MPLS vendor's QoS model so that such traffic is also deprioritized by them as it exits the MPLS cloud.


As examples:


For first instance:

policy-map shape4branchs


class matchBranch1

bandwidth 128

shape average 128000

service-policy branchPolicy


class matchBranch2

bandwidth 128

shape average 128000

service-policy branchPolicy


policy-map branchPolicy


class AV

bandwidth percent 1


class class-default

fair-queue


=or (2nd instance)=


policy-map branchPolicy


class AV

bandwidth percent 1

set ip dscp ?? (value depends on MPLS vendor)


class class-default

fair-queue

set ip dscp ?? (value depends on MPLS vendor)


Actions

This Discussion