CCIE Pursuit Blog

October 25, 2007

LFU 6: Traffic Shaping Won’t Start By Itself

Frame Relay traffic-shaping tasks can be a real pain in the ass.  Make sure that you don’t skip the simple steps when tackling a complicated FRTS task. 

In this scenario I want to create a simple Frame Relay map-class and apply it to DLCI 102 on interface s1/0.  Here’s my configuration:

map-class frame-relay MYFRAMEMAP
 frame-relay tc 100
 frame-relay cir 128000
!
interface Serial1/0
 ip address 10.1.1.1 255.255.255.0
 encapsulation frame-relay
 frame-relay map ip 10.1.1.2 102 broadcast
 frame-relay interface-dlci 102
  class MYFRAMEMAP
 no frame-relay inverse-arp

Done, right?  I go to verify my traffic-shaping and get nothing, nada, zilch:

r1#sh traffic
   <-note: no output
r1#

I try a few more commands:

r1#sh traffic queue
  <-note: no output
r1#

r1#sh traffic stat
                  Acc. Queue Packets   Bytes     Packets   Bytes     Shaping
I/F               List Depth                     Delayed   Delayed   Active

Finally I stumble across the problem:

r1#sh traffic s1/0
Traffic shaping not configured on Serial1/0 dumbass!!!

Okay, so IOS didn’t actually say “dumbass”, but I know that it wanted to.  🙂

Of course I didn’t do “sh traffic s1/0” right away.  No, it took tons of swearing, adding and removing configurations, and making sure that Frame Relay was set up right before I discovered that I had not actually TURNED FRAME RELAY TRAFFIC SHAPING ON!!! 

Quick fix:

r1(config)#int s1/0
r1(config-if)#frame traffic
r1(config-if)#do sh traffic

Interface   Se1/0
       Access Target    Byte   Sustain   Excess    Interval  Increment Adapt
VC     List   Rate      Limit  bits/int  bits/int  (ms)      (bytes)   Active
103           56000     875    7000      0         125       875       –
102           128000    2000   128000    0         125       2000      – <-booyah!!!

Don’t shoot yourself in the foot after mastering the fine art of FRTS.  Be sure to turn “frame-relay traffic-shaping” on for your interface.

Advertisements

1 Comment »

  1. This is not biggest problem in FRTS 🙂
    FRTS is very interesting theme.
    This is just one of the examples of Brian Dennis 🙂
    class-map match-all MY_CLASS
    match any
    !
    policy-map MY_MAP
    class MY_CLASS
    bandwidth percent 100
    !
    interface Serial0/0
    encapsulation frame-relay
    frame-relay traffic-shaping
    frame-relay interface-dlci 102
    class FR_MAP
    !
    map-class frame-relay FR_MAP
    frame-relay cir 512000
    service-policy output MY_MAP
    !

    R1(config-map-class)#do sho policy-map int s0/0 | include Band
    Bandwidth 100 (%)
    Bandwidth 256 (kbps) Max Threshold 64 (packets) R1(config-map-class)#
    R1(config-map-class)#frame-relay cir 256000
    R1(config-map-class)#
    R1(config-map-class)#do sho policy-map int s0/0 | include Band
    Bandwidth 100 (%)
    Bandwidth 128 (kbps) Max Threshold 64 (packets) R1(config-map-class)#
    So if you nest policy-map within FR map-class you reserve persantage of the minCIR in map-class
    Cool trick 🙂

    Comment by UnknownArt — October 26, 2007 @ 2:51 am | Reply


RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Create a free website or blog at WordPress.com.

%d bloggers like this: