Frame Relay Traffic Shaping Summary

GTS

- Interface/subinterface level (no pvc level)
- Internal shaper is WFQ
- Could be used with WFQ/PQ/CQ at interface level

interface Serial0/0/0:0.1 point-to-point
ip address 177.0.112.1 255.255.255.0
traffic-shape rate 512000
traffic-shape adaptive 256000
traffic-shape fecn-adapt
frame-relay interface-dlci 112


Legacy FRTS

- Enabled with frame-relay traffic-shaping
- PVC granularity
- Default to 56k/125ms once activated
- Could be used with WFQ/PQ/CQ per PVC
- Could not be used with WFQ/PQ/CQ at interface level (if FRF.12 2 dual fifo is enabled at interface level)
- Could use FRF12 of the map-class, per VC fragmentation

map-class frame-relay SHAPE_384K
frame-relay cir 384000
frame-relay bc 3840
frame-relay be 0
frame-relay adaptive-shaping becn
frame-relay adaptive-shaping interface-congestion
frame-relay fair-queue

interface Serial 0/0/0:0
frame-relay traffic-shaping
!
interface Serial 0/0/0:0.1
ip address 177.0.112.1 255.255.255.0
frame-relay interface-dlci 112
class SHAPE_384K



MQC based FRTS

- Needed for Voice-Adaptive Traffic Shaping
- Could use FRF 12 at interface level (for all vc of the interface)
- Incompatible with the command frame-relay traffic-shaping

policy-map CBWFQ
class VOICE
priority 64
class DATA
bandwidth 128
class class-default
fair-queue

policy-map SHAPE_384K
class class-default
shape average 384000
shape adaptive 192000
service-policy CBWFQ

map-class frame-relay SHAPE_384K
service-policy output SHAPE_384K

interface Serial 0/0/0:0.1
ip address 177.0.112.1 255.255.255.0
frame-relay interface-dlci 112
class SHAPE_384K


MQC based Class based traffic shaping

- Use map-class
- Incompatible with frame-relay traffic-shaping
- Incompatible with adaptive shaping
- Use service policy with shaping configured on default-class or by pvc matching a dlci
- CBFWQ could be used to child policy
- FRF.12 is applied at interface level

policy-map CBWFQ
class VOICE
priority 64
class DATA
bandwidth 128
class class-default
fair-queue

policy-map SHAPE_384K
class class-default
shape average 384000
shape adaptive 192000
service-policy CBWFQ

interface Serial 0/0/0:0.1
ip address 177.0.112.1 255.255.255.0
service-policy output SHAPE_384K
frame-relay interface-dlci 112

PPP over Frame Relay

PPP over Frame Relay (PPPoFR) could be used for :

- Need for authentication between routers
- Need for same IP on multiple DLCI and static mapping not permitted.

int s0/0
encap frame-relay
frame-relay interface-dlci XXX ppp virtual-template1
frame-relay interface-dlci YYY ppp virtual-template1

int virtual-template1
ip add 10.0.0.1 255.255.255.0
ppp authentication chap

Frame-Relay Interfaces types

Physical
PVC establishment :

• LMI automatically applies all DLCI to the interface or
• frame-relay interface dlci applies the specified dlci to the interface
  

Layer2/Layer mapping

• Need static mapping or
• Need inverse-arp enabled on the DLCI
  

Point-To-Point
PVC establishment :

• frame-relay interface dlci applies the specified dlci to the interface

Layer2/Layer mapping

• No mapping needed (everything for the subnet is sent thrue pt-to-pt interface)
• Inverse arp is not needed ans disabled by default
  

Point-To-MultiPoint
PVC establishment :

• LMI automatically applies all DLCI to the interface or
• frame-relay interface dlci applies the specified dlci to the interface

Layer2/Layer mapping

• Need static mapping or
• Need inverse-arp enabled on the DLCI
  

Frame-Relay Legacy Traffic Shaping

Some recalls :

Guaranteed rate = minimum guaranteed rate by the Telco. Configured with minCIR (bps) by default is 1/2 CIR
CIR = rate provided by Telco during no congestion. Configured with CIR (bps) By default it's 2x CIR
Access rate = maximum rate of the link. Configured with Bc (bits). Bc = (Access Rate - CIR)*Tc By default Tc is 125ms or 1/8 of seconds.

Example
32kbps is guarantedd
64kbps of Cir
192kbps of Access Rate

map-class frame-relay cisco
frame-relay cir 64000
frame-relay mincir 32000
frame-relay adaptive-shaping becn
frame-relay bc 8000
frame-relay be 16000 

interface Serial0/0 
interface Serial/0/
frame-relay traffic-shaping
frame-relay class cisco

Verification commands :

show traffic-shaping

Frame-Relay DE setting

Purpose of the exercice is to set the DE bit of a frame-relay packet depending on the length. 2 solutions depending on constraints :

1) If it's for all dlci of a given interface, you could use a Service-Policy :

class-map match-all DE1024
match packet length min 1024
!
policy-map DE1024
class DE1024
set fr-de
!
interface Serial0/0
service-policy output DE1024

2) If it's for a specific dlci, you could use the de-list command :

frame-relay de-list 1 protocol ip gt 1024
!
interface Serial0/0
frame-relay de-group 1 501

To check, connect on the other side router :

R2#sh frame-relay pvc 105

PVC Statistics for interface Serial0/0 (Frame Relay DTE)

DLCI = 105, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial0/0.2

input pkts 25 output pkts 25 in bytes 13600
out bytes 13600 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 7 out DE pkts 0
out bcast pkts 0 out bcast bytes 0
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
pvc create time 00:49:33, last time pvc status changed 00:35:02