|
I have performed some comparison between the code, generated by Frame Relay Auto QoS command, and the Frame Relay recommended QoS settings from QoS SRND file. Here are results: 1. Frame Relay with MLPPP matches exactly, line-by-line. Sure, some "fine tuning" required, like renaming the policy or setting shaping to 95% of like bandwidth. However, it works perfectly (differences are in the red): | AutoQoS | QoS SRND | | class-map match-any AutoQoS-VoIP-RTP-Trust
match ip dscp ef
class-map match-any AutoQoS-VoIP-Control-Trust
match ip dscp cs3
match ip dscp af31 | class-map match-all Voice
match ip dscp ef class-map match-any Call-Signaling match ip dscp cs3
match ip dscp af31 | | policy-map AutoQoS-Policy-Trust
class AutoQoS-VoIP-RTP-Trust
priority percent 70
class AutoQoS-VoIP-Control-Trust
bandwidth percent 5
class class-default
fair-queue
| policy-map WAN-EDGE
class Voice
priority percent 33
compress header ip rtp
class Call-Signaling
bandwidth percent 5
class class-default
fair-queue | | interface Serial0/0
frame-relay traffic-shaping
| interface Serial6/0 frame-relay traffic-shaping | | interface Serial0/0.1 point-to-point
bandwidth 512
frame-relay interface-dlci 201 ppp Virtual-Template200
class AutoQoS-FR-Se0/0-201
auto qos voip trust fr-atm
| interface Serial6/0.60 point-to-point
bandwidth 512
frame-relay interface-dlci 60 ppp Virtual-Template60 class FRTS-512kbps | | interface Virtual-Template200
bandwidth 512
ip address 162.10.101.2 255.255.255.0
ppp multilink
ppp multilink interleave
ppp multilink fragment delay 10
service-policy output AutoQoS-Policy-Trust
| interface Virtual-Template60
bandwidth 256
ip address 10.200.60.2 255.255.255.252
ppp multilink
ppp multilink interleave
ppp multilink fragment-delay 10
service-policy output WAN-EDGE | | map-class frame-relay AutoQoS-FR-Se0/0-201
frame-relay cir 512000
frame-relay bc 5120
frame-relay be 0
frame-relay mincir 512000 | map-class frame-relay FRTS-512kbps
frame-relay cir 486400
frame-relay bc 4864
frame-relay be 0
frame-relay mincir 486400 | 2. Frame Relay with FRF.12 is a little bit different.SRND recommends nested policies with "shape average" command, while AutoQoS does the same "cir/mincir/bc/be" as in MLPPP example. Also, the "IP RTP compression" defined in the different places. | AutoQoS | QoS SRND | | class-map match-any AutoQoS-VoIP-RTP-Trust
match ip dscp ef
class-map match-any AutoQoS-VoIP-Control-Trust
match ip dscp cs3
match ip dscp af31 | class-map match-all Voice
match ip dscp ef class-map match-any Call-Signaling match ip dscp cs3
match ip dscp af31 | | policy-map AutoQoS-Policy-Trust
class AutoQoS-VoIP-RTP-Trust
priority percent 70
class AutoQoS-VoIP-Control-Trust
bandwidth percent 5
class class-default
fair-queue | policy-map WAN-EDGE
class Voice
priority percent 33
compress header ip rtp
class Call-Signaling
bandwidth percent 5
class class-default
fair-queue | | interface Serial0/2/0
frame-relay traffic-shaping
| interface Serial2/0 | | interface Serial0/2/0.1 point-to-point
bandwidth 768
frame-relay interface-dlci 301 CISCO
class AutoQoS-FR-Se0/2/0-301
auto qos voip trust
frame-relay ip rtp header-compression
| interface Serial2/0.12 point-to-point ip address 10.1.121.1 255.255.255.252 frame-relay interface-dlci 301 class FR-MAP-CLASS-1536 | | | policy-map MQC-FRTS-768 class class-default shape average 729600 7296 0 service-policy WAN-EDGE | | map-class frame-relay AutoQoS-FR-Se0/2/0-301
service-policy output AutoQoS-Policy-Trust frame-relay fragment 960 frame-relay cir 768000
frame-relay bc 7680
frame-relay be 0
frame-relay mincir 768000
| map-class frame-relay FR-MAP-CLASS-768 service-policy output MQC-FRTS-768 frame-relay fragment 960 |
|
