venerdì 25 ottobre 2013
TRAFFIC-SHAPING LEGACY on MAP-CLASS
Legacy FRTS
This is the most well-known FRTS method, which has been available for quite
a while on Cisco routers. It is now being outdated by MQC configurations.
The key characteristic is that all settings are configured under map-class command mode, and later are applied to a particular set PVCs. The
same configuration concept was used for legacy ATM configuration mode (map-class atm).
The key characteristic is that all settings are configured under map-class command mode, and later are applied to a particular set PVCs. The
same configuration concept was used for legacy ATM configuration mode (map-class atm).
Legacy FRTS has the following characteristics:
- Enabled with frame-relay traffic-shaping command at
physical interface level- Incompatible with GTS or MQC commands at subinterfaces or physical interface levels
- With FRTS you can enforce bitrate per-VC (VC-granular, unlike GTS), by applying a map-class to PVC
- When no map-class is explicitly applied to PVC, it’s CIR and Tc are set to 56K/125ms by default
- Shaping parameters are configured under map-class frame-relay configuration submode
- Allows to configure fancy-queueing (WFQ/PQ/CQ) or simple FIFO per-VC
- No option to configure fancy-queueing at interface level: interface queue is forced to FIFO (if no FRF.12 is configured)
- Allows for adaptive shaping (throttling down to minCIR) on BECN reception (just as GTS) and option to reflect incoming FECNs as BECNs
- Option to enable adaptive shaping which responds to interface congestion (non-empty interface
R25#sh frame-relay pvc 253
PVC Statistics for interface Serial0/0 (Frame Relay DTE)
DLCI = 253, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0
input pkts 3753 output pkts 1313 in bytes 246264
out bytes 120733 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 0
out bcast pkts 1234 out bcast bytes 100994
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
pvc create time 02:55:56, last time pvc status changed 02:28:38
R25#
interface Serial0/0
ip address 10.10.10.11 255.255.255.248
ip pim dr-priority 100
ip pim nbma-mode
ip pim sparse-mode
encapsulation frame-relay
ip ospf authentication message-digest
ip ospf message-digest-key 1 md5 cisco
ip ospf network point-to-multipoint
ipv6 address FE80::25 link-local
ipv6 address 2001:CC1E:ABCD:100:10:10:2:11/64
ipv6 ospf network point-to-multipoint
ipv6 ospf 1 area 0
serial restart-delay 0
frame-relay map ipv6 2001:CC1E:ABCD:100:10:10:2:9 253 broadcast
frame-relay map ipv6 2001:CC1E:ABCD:100:10:10:2:10 254 broadcast
frame-relay map ipv6 FE80::23 253
frame-relay map ipv6 FE80::24 254
frame-relay map ip 10.10.10.10 254 broadcast
frame-relay map ip 10.10.10.9 253 broadcast
frame-relay interface-dlci 253
class frts
no frame-relay inverse-arp
R25(config)#interface Serial0/0
R25(config-if)#frame-relay traffic-shaping
IN QUESTO MODO SI ABILITA IL TRAFFIC SHAPING E L'OUTPUT DEL COMANDO PRECEDENTE CAMBIA "sh frame-relay pvc 253"
R25#sh frame-relay pvc 253
PVC Statistics for interface Serial0/0 (Frame Relay DTE)
DLCI = 253, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0
input pkts 3820 output pkts 1337 in bytes 250704
out bytes 123017 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 0
out bcast pkts 1257 out bcast bytes 102950
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
pvc create time 02:59:05, last time pvc status changed 02:31:47
cir 1000 bc 8000 be 0 byte limit 15 interval 125 <-- parametri prima assenti
mincir 500 byte increment 15 Adaptive Shaping none <-- parametri prima assenti
pkts 4 bytes 366 pkts delayed 0 bytes delayed 0 <-- parametri prima assenti
shaping inactive
traffic shaping drops 0
Output queue 0/40, 0 drop, 0 dequeued
martedì 15 ottobre 2013
lunedì 14 ottobre 2013
giovedì 10 ottobre 2013
FRAME-RELAY MQC vs LEGACY
GTS Generic Traffic Shaping
MQC" way to configuer Frame Realy traffic shaping. I have my configuration as follows:
!
class-map VOICE
match ip dscp ef
!
class-map DATA
match ip dscp cs1
!
! "Child" policy-map, used to implement CBWFQ
!
policy-map CBWFQ
class VOICE
priority 64
class DATA
bandwidth 128
class class-default
fair-queue
!
! "Parent" policy map, used for PVC shaping
!
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
Iscriviti a:
Post (Atom)