[c-nsp] QOS - 6509 - Next Step?

Thu Feb 1 12:39:11 EST 2007

hmmm.. interesting... we're msfc2/sup2 combo here ....

So, all of my changes to wrr-queue on the interfaces etc. isn't needed?
Again, we're not trying to do congestion avoidance at this level, just
priority queuing if needed.. 

My understanding of priority queuing is that it allows dscp=ef traffic to be
first in first out and take priority over everything else....?  Sorry if
that sounds like a basic question, just still getting my head around
everything....;)

Paul

  _____  

From: david.ponsdesserre at uk.bnpparibas.com
[mailto:david.ponsdesserre at uk.bnpparibas.com] 
Sent: Thursday, February 01, 2007 11:29 AM
To: paul at paulstewart.org
Cc: cisco-nsp at puck.nether.net; cisco-nsp-bounces at puck.nether.net
Subject: Re: [c-nsp] QOS - 6509 - Next Step?

Paul , 

This is how we have configured the voice traffic marking here ( 6509
WS-SUP32-GE-3B / MSFC 2A daughterboard / POE ) 

mls qos 
! 
class-map match-all voice 
  match access-group name match_voice 
! 
policy-map voice_priority 
  class voice 
   set dscp ef 
  class class-default 
   set dscp default 
! 
interface FastEthernet1/1 
 description IPT Port 
 switchport 
 switchport trunk encapsulation dot1q 
 switchport trunk native vlan 441 
 switchport trunk allowed vlan 441,442 
 switchport mode trunk 
 switchport nonegotiate 
 spanning-tree portfast 
 service-policy input voice_priority 
! 
ip access-list extended match_voice 
 remark matches all traffic from voice equipment 
 permit ip 22.0.0.0 0.255.255.255 any 
 deny   ip any any 
 remark matches all traffic from voice equipment 
! 
vlan 442 
 name VOICE 
! 
interface Vlan442 
 ip address 22.102.133.1 255.255.255.128 
 no ip redirects 
 ip flow ingress 
 arp timeout 720 
! 

Hope this helps 
David 

Internet 
paul at paulstewart.org 

Sent by: cisco-nsp-bounces at puck.nether.net 

01/02/2007 15:23 

To
cisco-nsp 

cc

Subject
[c-nsp] QOS - 6509 - Next Step?

Hi there...

I'm working on providing priority within our core of 6509's  and prefer to
do marking via NBAR.  Is this a very bad idea in general?  We have NBAR
support in all our routers pretty much throughout...

This is not to address congestion as our core and distribution has no
congestion (referring to maxxing out link speeds etc. specifically)...

So I have started working with several VLAN interfaces on our 6509 (layer 3
interfaces) and have DSCP=EF for SIP/MGCP/RTP traffic like this:

class-map match-any QOS-VOIP
 match protocol sip
 match protocol rtp
 match protocol mgcp
!
!
policy-map QOS
 class QOS-VOIP
  set dscp ef
 class class-default
  set dscp default

interface Vlan104
description xxxxxxxxxxxxxxxxxxx
bandwidth 100000
ip address xxx.xxx.xxx.105 255.255.255.248
ip nbar protocol-discovery
service-policy input QOS

On VLAN interfaces I can only apply the service policy inbound - not
outbound:

dis1-rtr-mb(config-if)#service-policy output QOS
MQC features are not supported in output direction for this interface

I don't believe this is a problem because I understand that QOS is applied
in one direction only - outbound, which on a VLAN layer3 interface would
actually mean traffic *leaving* the interface is marked .. correct??

So, I've been doing a lot of reading from "End-to-End QOS Network Design"
which is a great book... I'm faced right now with too much information..;)

Next step would be to assign queues on the actual interfaces?  Can I assign
queues to vlan interfaces or only physical interfaces?  My problem is that
the cards are 6148 and 6248 cards so limited queues.... as I understand it
the 6248 is 1Q4T and the 6148 is 1P2Q2T?

I hope someone can point me in the right direction for the "next step"...;)

Thanks very much,

Paul

_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

This message and any attachments (the "message") is 

intended solely for the addressees and is confidential. 

If you receive this message in error, please delete it and

immediately notify the sender. Any use not in accord with

its purpose, any dissemination or disclosure, either whole

or partial, is prohibited except formal approval. The internet

can not guarantee the integrity of this message.

BNP PARIBAS (and its subsidiaries) shall (will) not

therefore be liable for the message if modified. 

****************************************************************************
******************

BNP Paribas Private Bank London Branch is authorised

by CECEI & AMF and is regulated by the Financial Services

Authority for the conduct of its investment business in

the United Kingdom.

BNP Paribas Securities Services London Branch is authorised 

by CECEI & AMF and is regulated by the Financial Services 

Authority for the conduct of its investment business in 

the United Kingdom.

BNP Paribas Fund Services UK Limited is authorised and 

regulated by the Financial Services Authority