Re: Frame-Relay QOS Question, please explain

From: Michael Dorion (dorionm@gmail.com)
Date: Fri Oct 24 2008 - 13:49:25 ARST


You could apply a service policy directly to the interface, but based on the
wording I'm guessing it's a multipoint interface with multiple PVCs.

Here is an example on R3 pvc 301, I think this covers it.

------------------
!on R3

policy-map FR
 class class-default
  shape peak 128000 8000 8000
  police cir 64000 bc 1000 be 1000
    conform-action transmit
    exceed-action transmit
    violate-action set-frde-transmit
!
map-class frame-relay FRAME
 service-policy output FR
!
interface Serial 1/0
 frame-relay interface-dlci 301
  class FRAME

------------------
!on SW1 (Behind R3)
ping 19.19.13.1 rep 1000 tim 0
.................................
--------------------
!on R3
Rack1R3#sho policy-map interface
 Serial1/0: DLCI 301 -

  Service-policy output: FR

    Class-map: class-default (match-any)
      1005 packets, 104580 bytes
      5 minute offered rate 20000 bps, drop rate 0 bps
      Match: any
      Traffic Shaping
           Target/Average Byte Sustain Excess Interval Increment
             Rate Limit bits/int bits/int (ms) (bytes)
           256000/128000 2000 8000 8000 62 2000

        Adapt Queue Packets Bytes Packets Bytes Shaping
        Active Depth Delayed Delayed Active
        - 0 809 84196 743 77272 no
      police:
          cir 64000 bps, bc 1000 bytes, be 1000 bytes
        conformed 192 packets, 19968 bytes; actions:
          transmit
        exceeded 9 packets, 936 bytes; actions:
          transmit
        violated 799 packets, 83096 bytes; actions:
          set-frde-transmit
        conformed 0 bps, exceed 0 bps, violate 2000 bps

Rack1R3#sho fram pvc 301 | be DLCI

DLCI = 301, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1/0

  input pkts 809 output pkts 808 in bytes 84096
  out bytes 84080 dropped pkts 0 in pkts dropped
0
  out pkts dropped 196 out bytes dropped 20384
  late-dropped out pkts 196 late-dropped out bytes 20384
  in FECN pkts 0 in BECN pkts 0 out FECN pkts 0
  out BECN pkts 0 in DE pkts 0 out DE pkts 799
  out bcast pkts 0 out bcast bytes 0
  5 minute input rate 3000 bits/sec, 4 packets/sec
  5 minute output rate 3000 bits/sec, 4 packets/sec
  pvc create time 02:40:50, last time pvc status changed 02:40:50
--------------------------

Notice "target" rate is 256k even though peak is set to 128. You can set an
adaptive minimum in the FR policy map with "shape adaptive 128000 " under
class class-default.

On Fri, Oct 24, 2008 at 7:39 AM, Reza Toghraee <reza@toghraee.com> wrote:

> Hello
>
>
>
> A task is asking :
>
>
>
> PVC 304 should be configured with MINCIR 128000 bps and Peak Rate 128000
> bps. Use a method based on dual token bucket algorithm to mark outgoing
> traffic on R3 with the discard eligible bit, if the traffic exceeds 1000
> byte normal burst size and 1000 byte excess burst size at the committed
> rate
> of 64000 bps.
>
>
>
> What is proper way to solve this?
>
>
>
> Reza
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net



This archive was generated by hypermail 2.1.4 : Sat Nov 01 2008 - 15:35:22 ARST