From: Anh P Tran (anhtran81@optusnet.com.au)
Date: Mon Oct 10 2005 - 09:46:29 GMT-3
Stefan,
To help you understand this, I quickly lab it up here.
R1 connect to R2 via frame-relay PVC 102
Rack1R1#show run int s0/0
Building configuration...
Current configuration : 461 bytes
!
interface Serial0/0
 ip address 163.1.12.1 255.255.255.0
 encapsulation frame-relay
 load-interval 30
 no fair-queue
 frame-relay traffic-shaping
 frame-relay map clns 102 broadcast
 frame-relay map ip 163.1.12.2 102 broadcast
 frame-relay interface-dlci 102
  class DLCI-102
 no frame-relay inverse-arp
end 
Rack1R1#sho run map-class
Building configuration...
Current configuration:
!
map-class frame-relay DLCI-102
 frame-relay cir 64000
First, we don't set up any de-list and let try to generate some data
Rack1R1#ping 150.1.2.2 timeout 0 rep 100000
Type escape sequence to abort.
Sending 100000, 100-byte ICMP Echos to 150.1.2.2, timeout is 0 seconds:
......................................................................
......................................................................
......................................................................
....
Rack1R1#sho fram pvc 102 
PVC Statistics for interface Serial0/0 (Frame Relay DTE)
DLCI = 102, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0
  input pkts 19872         output pkts 19595        in bytes 5506952   
  out bytes 3185993        dropped pkts 5710        in pkts dropped 0
  out pkts dropped 5710             out bytes dropped 593993    
  late-dropped out pkts 5710        late-dropped out bytes 593993    
  in FECN pkts 0           in BECN pkts 0           out FECN pkts 0         
  out BECN pkts 0          in DE pkts 0             out DE pkts 0  <<<< Here
nothing being Marked        
  out bcast pkts 886       out bcast bytes 1244617   
  5 minute input rate 55000 bits/sec, 57 packets/sec
  5 minute output rate 53000 bits/sec, 59 packets/sec
  pvc create time 01:59:39, last time pvc status changed 01:58:26
  cir 64000     bc 64000     be 0         byte limit 1000   interval 125 
  mincir 32000     byte increment 1000  Adaptive Shaping none
  pkts 17457     bytes 1859507   pkts delayed 17425     bytes delayed
1849409  
  shaping active    <<<< Shaping active now due to the traffic load exceed
the CIR  
  traffic shaping drops 0
  Queueing strategy: fifo
  Output queue 32/40, 5808 drop, 17511 dequeued
That is the answer for question 1. The router is the end device and will not
mark any de-bit by default even if you exceed the CIR, but the provider
cloud will mark it depend on their configuration.
Now, let try to mark it with packet larger than 512 bytes
Rack1R1# show run | i Serial0/0|de-list|de-group
frame-relay de-list 1 protocol ip gt 512
interface Serial0/0
 frame-relay de-group 1 102
Rack1R1#clear counters s0/0
Clear "show interface" counters on this interface [confirm]
Rack1R1#ping 150.1.2.2 repeat 1000 size 550 df
Type escape sequence to abort.
Sending 1000, 550-byte ICMP Echos to 150.1.2.2, timeout is 2 seconds:
Packet sent with the DF bit set
!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Rack1R1#show frame pvc 102
PVC Statistics for interface Serial0/0 (Frame Relay DTE)
DLCI = 102, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0
  input pkts 65            output pkts 86           in bytes 51194     
  out bytes 36147          dropped pkts 0           in pkts dropped 0
  out pkts dropped 0                out bytes dropped 0         
  in FECN pkts 0           in BECN pkts 0           out FECN pkts 0         
  out BECN pkts 0          in DE pkts 0             out DE pkts 40  <<< the
router will mark the de bit now      
  out bcast pkts 6         out bcast bytes 9030      
  5 minute input rate 6000 bits/sec, 2 packets/sec
  5 minute output rate 3000 bits/sec, 2 packets/sec
  pvc create time 02:03:38, last time pvc status changed 02:02:25
  cir 64000     bc 64000     be 0         byte limit 1000   interval 125 
  mincir 32000     byte increment 1000  Adaptive Shaping none
  pkts 86        bytes 36147     pkts delayed 2         bytes delayed 241
  shaping inactive    
  traffic shaping drops 0
  Queueing strategy: fifo
  Output queue 0/40, 0 drop, 2 dequeued
R1 marked the traffic without shaping active as the packet size greater than
512.
Rack1R1#show frame pvc 102
PVC Statistics for interface Serial0/0 (Frame Relay DTE)
DLCI = 102, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0
  input pkts 563           output pkts 579          in bytes 366871    
  out bytes 302905         dropped pkts 0           in pkts dropped 0
  out pkts dropped 0                out bytes dropped 0         
  in FECN pkts 0           in BECN pkts 0           out FECN pkts 0         
  out BECN pkts 0          in DE pkts 0             out DE pkts 468 <<< I
stopped the traffic now at this value      
  out bcast pkts 22        out bcast bytes 33110     
  5 minute input rate 14000 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
  pvc create time 02:06:05, last time pvc status changed 02:04:52
  cir 64000     bc 64000     be 0         byte limit 1000   interval 125 
  mincir 32000     byte increment 1000  Adaptive Shaping none
  pkts 579       bytes 302905    pkts delayed 6         bytes delayed 2457
  shaping inactive    
  traffic shaping drops 0
  Queueing strategy: fifo
  Output queue 0/40, 0 drop, 6 dequeued
Now generate small packet more than the cir
Rack1R1#ping 150.1.2.2 repeat 1000000 timeout 0 size 100
Type escape sequence to abort.
Sending 1000000, 100-byte ICMP Echos to 150.1.2.2, timeout is 0 seconds:
......................................................................
......................................................................
......................................................................
......................................................................
.................................
Rack1R1#show frame pvc 102                      
PVC Statistics for interface Serial0/0 (Frame Relay DTE)
DLCI = 102, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0
  input pkts 7617          output pkts 8058         in bytes 1174014   
  out bytes 1106154        dropped pkts 2361        in pkts dropped 0
  out pkts dropped 2361             out bytes dropped 245749    
  late-dropped out pkts 2361        late-dropped out bytes 245749    
  in FECN pkts 0           in BECN pkts 0           out FECN pkts 0         
  out BECN pkts 0          in DE pkts 0             out DE pkts 468   <<< no
DE increase    
  out bcast pkts 41        out bcast bytes 60355     
  5 minute input rate 28000 bits/sec, 30 packets/sec
  5 minute output rate 28000 bits/sec, 33 packets/sec
  pvc create time 02:08:37, last time pvc status changed 02:07:24
  cir 64000     bc 64000     be 0         byte limit 1000   interval 125 
  mincir 32000     byte increment 1000  Adaptive Shaping none
  pkts 8001      bytes 1099615   pkts delayed 7388      bytes delayed 786822
  shaping active      <<<<<<<<<< Shaping now active
  traffic shaping drops 0
  Queueing strategy: fifo
  Output queue 35/40, 2416 drop, 7473 dequeued
So the answer for question 2 is, router only set the de-bit according to the
de-list set, not by the traffic excceed the CIR. The provider is the one who
measure your traffic and tag or set that bit when your traffic over the
provision CIR.
Please correct me if I missed some thing. Hope this help
Anh Tran
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Stefan Grey
Sent: Monday, 10 October 2005 5:34 PM
To: chrlewis@cisco.com; ccielab@groupstudy.com
Subject: Frame-relay de-list!!
Hello,
I just want make sure that I correctly understand how the de bit works or
better understand this process.
1. De bit is assigned to the output frame-relay traffic only in the case if
traffic is more than the Cir value. So to the traffic that is above Cir
value by default is assigned the de bit??
2. If we want only cirtain type of traffic above cir to be marked by the de
bit. Say IP traffic gt than 512 than we use the command as below.
frame-relay de-list 1 protocol ip gt 512
So as I understand this traffic would be marked with de bit all  or just
above the cir value. What would happen with traffic that is above cir but is
not under that lis???
thanks for the explanation,
This archive was generated by hypermail 2.1.4 : Sun Nov 06 2005 - 22:00:50 GMT-3