Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

How To 1

Status
Not open for further replies.

ermora

IS-IT--Management
Apr 5, 2004
70
US
Configure 1841 routers for Diff Serv (Differential Services) 46 QOS standard?
 
RT01 Config
FastEthernet0/0: 192.168.0.1
Serial0/1/0: 172.16.1.1
|
|
T1 (1mb)
|
|
RT02 Config
FastEthernet0/0: 192.168.1.1
Serial0/1/0: 172.16.1.2
 
Your question makes no sense. What is the topology and what are you trying to achieve? Are you trying to prioritise voice traffic out of an interface? are you trying to classify traffic?
Simply stating:
How to configure 1841 routers for Diff Serv (Differential Services) 46 QOS standard?
means nothing........

 
ADB100,
Sorry, it's what I received in email. Let me back track a bit...

We are in the process of implementing Avaya Office IP 500 in two of our business locations that have a Point-to-point circuit (T1 1mb).

I need to enable the routers on the P2P circuit to handle QOS so that voice traffic is prioritised. I requested information regarding QOS requirements and received an email saying "Diff Serv (Differential Serivces) 46 QOS Standard" - which means next to nothing to me - and thought to ask for assistance here.

 
OK. What you are looking at doing is implementing a QoS service-policy on the WAN interfaces of the 1841 routers. To do this you need to define a policy and apply it to the egress of the WAN circuit:
Code:
class-map match-all EF
 match dscp ef
!
policy-map wan-qos
 class EF
  priority percent 33
 class class-default
  fair-queue
!
interface serial0
 service-policy output wan-qos
![/quote]

This is a very simple QoS policy and will provide a Low Latency Queue (LLQ) for DSCP EF (46) traffic.  All other traffic is handled by the default class and is set for fair-queueing.  The chances are that the signalling for the Avaya kit uses a different DSCP value for signalling (usually DSCP 24 or 40) so ideally you should have a separate queue for this traffic as well.
If you apply this you should verify traffic is matching the classes with the command 'show policy-map interface serial0' command.

It can get much more complicated with different data classes, policing and markdown etc.  I suggest you have a look on CCO for some more help.

HTH

Andy
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top