[c-nsp] 7206VXR and CBWFQ

Dean Smith dean at eatworms.org.uk
Mon Oct 20 06:21:01 EDT 2008


I see you have your PVC as vbr-nrt.

Orig poster has UBR

When we've tested QoS on ADSL we found the PVC had to be configured as 
VBR-NRT to make QOS work. this may be the issue here.

I'm sure I found a reference on CCO to this behaviour but cant find it again 
quickly.

Regards
Dean
----- Original Message ----- 
From: "Brian Turnbow" <b.turnbow at twt.it>
To: "Victor Cappuccio" <vcappuccio at gmail.com>
Cc: "Networkers" <cisco at peakpeak.com>; <cisco-nsp at puck.nether.net>
Sent: Monday, October 20, 2008 10:20 AM
Subject: Re: [c-nsp] 7206VXR and CBWFQ


Please don't tell that  to this router


policy-map llq
  class sipRTP
    priority 512
  class class-default
    fair-queue
    random-detect

vc-class atm CVPHDSL-VoIP
  vbr-nrt 1524 1524
  encapsulation aal5snap


interface ATM3/0.20842 point-to-point
 description cust 1
  ip address192.168.0.41 255.255.255.252
 pvc CVPH_CUSTVOIP 208/42
  class-vc CVPHDSL-VoIP
  service-policy out llq

7200-accessjn3#sh policy-map int ATM3/0.20842
 ATM3/0.20842: VC 208/42 -

  Service-policy output: llq

    queue stats for all priority classes:

      queue limit 64 packets
      (queue depth/total drops/no-buffer drops) 0/0/0
      (pkts output/bytes output) 5466056/418685691

    Class-map: sipRTP (match-all)
      5466056 packets, 418685691 bytes
      5 minute offered rate 61000 bps, drop rate 0 bps
      Match: access-group 5
      Priority: 512 kbps, burst bytes 12800, b/w exceed drops: 0

    Class-map: class-default (match-any)
      492783 packets, 493906760 bytes
      5 minute offered rate 509000 bps, drop rate 0 bps
      Match: any
        492783 packets, 493906760 bytes
        5 minute rate 509000 bps
      Queueing
      queue limit 64 packets
      (queue depth/total drops/no-buffer drops/flowdrops) 0/50/0/50
      (pkts output/bytes output) 492733/493866217
      Fair-queue: per-flow queue limit 16
        Exp-weight-constant: 9 (1/512)
        Mean queue depth: 0 packets
        class     Transmitted       Random drop      Tail/Flow drop Minimum 
Maximum Mark
                  pkts/bytes        pkts/bytes       pkts/bytes    thresh 
thresh  prob

        0          486842/493318682       0/0             50/40543 
20            40  1/10
        1              54/22464           0/0              0/0 
22            40  1/10
        2               6/746             0/0              0/0 
24            40  1/10
        3               0/0               0/0              0/0 
26            40  1/10
        4               5/330             0/0              0/0 
28            40  1/10
        5              20/1200            0/0              0/0 
30            40  1/10
        6            5753/515372          0/0              0/0 
32            40  1/10
        7              53/7423            0/0              0/0 
34            40  1/10


http://www.cisco.com/en/US/tech/tk39/tk824/technologies_configuration_example09186a0080094cf6.shtml



Brian




________________________________

From: Victor Cappuccio [mailto:vcappuccio at gmail.com]
Sent: venerdì 17 ottobre 2008 18.52
To: Brian Turnbow
Cc: Networkers; cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] 7206VXR and CBWFQ


Hi,

Subinterfaces and software interfaces do not have their own separate 
transmit (Tx) ring; therefore, no congestion can occur. These interface 
types include dialers, tunnels, and Frame Relay subinterfaces, and will only 
congest when their main hardware interface Tx ring congests. The Tx ring 
state is an indication of congestion for software interfaces.


router(config)# interface Serial0/0.1
router(config-subif)# service-policy output test
 CBWFQ : Not supported on subinterfaces


1.- Create a child or lower-level policy that configures a queueing 
mechanism. In the example below, we configure LLQ using the priority command 
and CBWFQ using the bandwidth command. Refer to Congestion Management 
Overview for more information.

          policy-map child
           class voice
            priority 512

2. Create a parent or top-level policy that applies class-based shaping. 
Apply the child policy as a command under the parent policy since the 
admission control for the child class is done based on the shaping rate for 
the parent class.

          policy-map parent
           class class-default
            shape average 2000000
            service-policy child

3. Apply the parent policy to the subinterface.

          interface Serial0/0.1
           service-policy parent

Cisco Page: http://tinyurl.com/ytt8ge

Note: Class-based shaping works at the interface and subinterface level. 
Cisco IOS 12.2(2.5) introduces the ability to configure shaping on the main 
interface and IP addresses on the subinterfaces.

thanks,

Victor Cappuccio
CCIE R/S# 20657
CCSI# 30452
www.anetworkerblog.com


On Fri, Oct 17, 2008 at 6:19 PM, Brian Turnbow <b.turnbow at twt.it> wrote:


Your pvc needs to be abr/vbr/cbr
You can't do it on ubr

Regards

Brian






-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net 
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Networkers

Sent: venerdì 17 ottobre 2008 17.10
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] 7206VXR and CBWFQ


Whenever I try to apply the following I get an error message about how
CBWFQ can't be applied to subinterfaces.  What is the correct way to do
this?

Thanks,
Chris

class-map match-any VOIP
match ip dscp ef
match  precedence 5
class-map match-all CRITICAL
match access-group 100

policy-map MyCBWFQ
class CRITICAL
  priority 48
class VOIP
  bandwidth 320
  set precedence 6

vc-class atm MyClass
ubr 1536
encapsulation aal5mux ppp Virtual-Template5

interface Virtual-Template5
ip unnumbered Loopback0
service-policy output MyCBWFQ
peer default ip address pool default
ppp authentication pap callin

interface ATM2/0.1921 point-to-point
pvc 1/1921
class-vc MyClass







_______________________________________________
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/
_______________________________________________
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/





-- 


_______________________________________________
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/ 



More information about the cisco-nsp mailing list