[c-nsp] CBWFQ on Frame-relay interfaces - 12.2.28SB?

Rolf Mendelsohn rolf-web at cyberops.biz
Thu Feb 8 16:40:29 EST 2007


Hi Brian / Rodney,

pe1.wdh1.na(config-subif)#frame-relay class cbwfq
Invalid policy. MQC must have only class-default shaped or legacy
queueing must not be shaped.

pe1.wdh1.na(config-subif)#exit
pe1.wdh1.na(config)#interface Serial3/5:0

pe1.wdh1.na(config-if)#frame-relay class cbwfq ?
  <cr>

policy-map cbwfq
  class class-default
    fair-queue

Rodney:

Thanks, it seems to be working.

pe1.wdh1.na(config-subif)#service-policy output mpls-qos
Leased-line fragmentation works with main interface service-policy only.
 CBWFQ : Not supported on subinterfaces

Does FR.12 Interleaving happen automatically if a frame/packet matches a 
priority queue? Or am I missing something for this to happen?

class-map match-any qos1
  description Critical Class
  match mpls experimental topmost 5  6  7
  match ip precedence 5  6  7
  match access-group name core-loopbacks
class-map match-any qos2
  description Priority class
  match mpls experimental topmost 1  2  3  4
  match ip precedence 1  2  3  4

policy-map mpls-qos
 description Set a General Backbone QoS policy
  class qos1
    priority percent 20
  class qos2
    bandwidth percent 40
  class class-default
    bandwidth percent 40

interface Serial3/5:0
 description 576k Backbone link to Town B
 mtu 1516
 bandwidth 576
 no ip address
 encapsulation frame-relay IETF
 frame-relay lmi-type ansi
 frame-relay intf-type dce
 frame-relay fragment 768 end-to-end
 service-policy output mpls-qos
end

interface Serial3/5:0.1 point-to-point
 description 576k Backbone link to Town B
 bandwidth 576
 ip address XXX
 mpls ip
 no cdp enable
 frame-relay interface-dlci 208
end

pe1.wdh1.na#sh policy-map interface
 Serial3/5:0

  Service-policy output: mpls-qos

    queue stats for all priority classes:

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

    Class-map: qos1 (match-any)
      78 packets, 21338 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match: mpls experimental topmost 5  6  7
        0 packets, 0 bytes
        5 minute rate 0 bps
      Match: ip precedence 5  6  7
        78 packets, 21338 bytes
        5 minute rate 0 bps
      Match: access-group name core-loopbacks
        0 packets, 0 bytes
        5 minute rate 0 bps
      Priority: 20% (115 kbps), burst bytes 2850, b/w exceed drops: 0

    Class-map: qos2 (match-any)
      437 packets, 528612 bytes
      5 minute offered rate 20000 bps, drop rate 0 bps
      Match: mpls experimental topmost 1  2  3  4
        0 packets, 0 bytes
        5 minute rate 0 bps
      Match: ip precedence 1  2  3  4
        437 packets, 528612 bytes
        5 minute rate 20000 bps
      Queueing
      queue limit 64 packets
      (queue depth/total drops/no-buffer drops) 0/0/0
      (pkts output/bytes output) 444/539140
      bandwidth 40% (230 kbps)

    Class-map: class-default (match-any)
      1864 packets, 152324 bytes
      5 minute offered rate 14000 bps, drop rate 0 bps
      Match: any
        1864 packets, 152324 bytes
        5 minute rate 14000 bps
      Queueing
      queue limit 64 packets
      (queue depth/total drops/no-buffer drops) 0/0/0
      (pkts output/bytes output) 2352/205322
      bandwidth 40% (230 kbps)


cheers
/rolf

On Thursday 08 February 2007 17:04, Brian Turnbow wrote:
> You need to do it under a  frame relay class
>
>
> map-class frame-relay cbwfqovFR    (apply this class under your dlci)
>  no frame-relay adaptive-shaping
>  service-policy output cbwfq
>
> Regads
> Brian
>
> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net
> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Rolf Mendelsohn
> Sent: giovedì 8 febbraio 2007 15.15
> To: cisco-nsp at puck.nether.net
> Subject: [c-nsp] CBWFQ on Frame-relay interfaces - 12.2.28SB?
>
> Hi Everybody,
>
> Do you know if CBWFQ is supported on Frame-relay interfaces (12.2.28SB)?
>
> If so how would i enable it?
>
> 12.2SB
>
> pe1.wdh1.na#sh run | beg Town!
>  description 576k Backbone link to TownA
>  mtu 1516
>  bandwidth 576
>  no ip address
>  encapsulation frame-relay IETF
>  frame-relay lmi-type ansi
>  frame-relay intf-type dce
>  frame-relay fragment 768 end-to-end
>  service-policy output cbwfq
> !
> interface Serial3/5:0.1 point-to-point
>  description 576k Backbone link to TownA
>  bandwidth 576
>  ip address A.B.C.D 255.255.255.254
>  mpls ip
>  no cdp enable
>  frame-relay interface-dlci 208
>
> pe1.wdh1.na#sh queueing int s3/5:0
> pe1.wdh1.na#sh queueing int s3/5:0.1
>                                   ^
> % Invalid input detected at '^' marker.
>
> pe1.wdh1.na#sh int s3/5:0 fai
> pe1.wdh1.na#sh int s3/5:0 fair-queue
> pe1.wdh1.na
>
> pe1.wdh1.na(config-if)#fair-queue
> Remove HQF queueing from interface before installing legacy command.
> Possibly have service-policy with heirarchical shaping attached.
>
> 12.4.12SP-Services
>
> gw1.wvb1.na#sh queueing int s1/1:11
> Interface Serial1/1:11 queueing strategy: fair
>   Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 406
>   Queueing strategy: weighted fair
>   Output queue: 0/1000/64/406 (size/max total/threshold/drops)
>      Conversations  0/24/256 (active/max active/max total)
>      Reserved Conversations 0/0 (allocated/max allocated)
>      Available Bandwidth 576 kilobits/sec
> !
> interface Serial1/1:11
>  description 576K Backbone link from Town B
>  mtu 1516
>  bandwidth 576
>  no ip address
>  encapsulation frame-relay IETF
>  frame-relay fragment 768 end-to-end
>  frame-relay lmi-type ansi
>  max-reserved-bandwidth 100
> end
> !
> interface Serial1/1:11.1 point-to-point
>  description 576K Backbone link from Town B
>  bandwidth 576
>  ip address A.B.C.82 255.255.255.254
>  mpls ip
>  no cdp enable
>  frame-relay interface-dlci 208
> end
>
> cheers
> /rolf
> _______________________________________________
> 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