Frame-relay traffic shaping using MQC

To apply frame-relay traffic shaping using a normal map-class, the command frame-relay traffic-shaping must be applied to the main interface.

This method has a pitfall; the problem is that when you apply the frame-relay traffic-shaping command to the main interface any DLCI that has no explicit map-class will be shaped to 56K by default. This means that if you need to apply traffic shaping to only one PVC all other PVCs will be shaped to 56K by default.

MQC shaping can be used to solve this problem by configuring shaping on specific PVC without the need to use the command frame-relay traffic-shaping at all.

The following configuration is showing how-to:

policy-map FRTS
 class class-default
!-- Add all shaping parameters here. bc, be, mincir etc.
  shape average 1000000

!-- Frame-relay normal map-class
map-class frame-relay FRTSMAP
 service-policy output FRTS

interface Serial1/0
  frame-relay interface-dlci 102
!-- map-class applied to the DLCI
  class FRTSMAP

!-- Verification of the configuration

R1#sh policy-map interface s1/0
 Serial1/0: DLCI 102 -

  Service-policy output: FRTS

    Class-map: class-default (match-any)
      29 packets, 2852 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match: any
      Traffic Shaping
           Target/Average   Byte   Sustain   Excess    Interval  Increment
             Rate           Limit  bits/int  bits/int  (ms)      (bytes)
          1000000/1000000   6250   25000     25000     25        3125     

        Adapt  Queue     Packets   Bytes     Packets   Bytes     Shaping
        Active Depth                         Delayed   Delayed   Active
        -      0         29        2852      0         0         no

Check Also

Best AI tools list