Archive for the ‘QOS’ Category

PPP Virtual template and Frame-relay

Posted: August 30, 2006 by sankar in QOS, WAN

To configure a virtual template for MLP LFI on a frame-relay subinterface, you have to remove the DLCI configured under that subinterface first before reapplying it back with the ppp keyword.

int s0/0

no frame-relay interface-dlci 30

 frame-relay interface-dlci 30 ppp virtual-template 1

Apply any LLQ, IP settings, ppp configs under the virtual template interface.


* Remove ip address of serial subinterface interface

* Remove DLCI of subinterface.

* Its recommended to do this configuration on the remote site first.

int s0/0.9

no ip address

frame-relay interface-dlci 900 ppp virtual-template 1

int virtual-template 1

ip add

ppp multilink

ppp multilink interleave

ppp multilink fragment-delay 10 — milliseconds.

service-policy output VATS

Frame relay voice adaptive traffic shaping

Posted: August 19, 2006 by cciestudy in QOS, WAN

** You will need to disable frame relay traffic shaping at the main interface level for this to work **

Configure LLQ for voice 

policy-map BR2-HQ
class RTP
priority percent 33
class Sig
bandwidth percent 2
class class-default
Configure Voice activated FRTS:

policy-map VATS  ———–  Line rate is 768kbps, CIR is 384kbps. Use 95 % of CIR for shape average and shape adaptive.
class class-default
shape average 729600 3648 0 
shape adaptive 364800
shape fr-voice-adapt deactivation 50
service-policy BR2-HQ
Configure FRTS class-map and apply VATS policy to the class-map

map-class frame-relay BR2-HQ
frame-relay fragment 480  ——— configures end-to-end FRF.12 fragmentation based on CIR of 384kbps
service-policy output VATS

interface Serial0/0
no ip address
encapsulation frame-relay
no dce-terminal-timing-enable
frame-relay fragmentation voice-adaptive deactivation 50
interface Serial0/0.201 point-to-point
ip address
frame-relay interface-dlci 201
class BR2-HQ

QoS for CUE CCM Integration

Posted: July 20, 2006 by cciestudy in Cisco Unity Express, QOS

One of the current limitations is that the JTAPI (CTI-quick buffer encoding [QBE]) signaling packets are unmarked (TOS = 0) when the Cisco Unity Express AIM transmits them. In order to correct this, use an access control list (ACL) on the router that has the Cisco Unity Express AIM installed to mark and prioritize the traffic.

The JTAPI signaling from the Cisco CallManager is correctly marked with a differentiated services code point (DSCP) value of CS3.

The JTAPI signaling protocol uses TCP port 2748. Dedicate 20 kbps per Cisco Unity Express site for this traffic.

All Real-Time Protocol (RTP) audio traffic from the Cisco Unity Express AIM or the IP phone is correctly marked with a DSCP value of 0xEF.

This example shows a sample configuration for this on the router where a.b.c.d is the IP address of the Cisco Unity Express AIM:

access-list 101 permit tcp host a.b.c.d any eq 2748
class-map match-all cti-qbe
 match access-group 101
policy-map cti-qbe
 class cti-qbe
 set dscp af31
 bandwidth 20
interface Serial0/1
 service-policy output cti-qbe

CIR calculation

Posted: July 10, 2006 by sankar in QOS, WAN

WHen calculating cir and mincir for FRTS, use 95 % of the CIR value. If CIR = 256k, it should be used as 256000. Do not multiply 256 with 1024.

Frame-relay fragment

Posted: July 10, 2006 by sankar in Cisco General, QOS, WAN

Frame-relay fragment is typically not needed for link speeds above 768 kbps.

If CIR is 256k and link speed is 480kbps, frame-relay fragment should be based off of PVC CIR ie 256 K.

QOS Aggregate policer

Posted: June 22, 2006 by sankar in 6500, QOS

************* IGNORE THIS POST..this is still a big confusion****************** 

When applying a qos aggregate policer to traffic, you dont need to apply it on every line.

set qos acl ip TestACL dscp 26 tcp any eq 2000 any 

set qos acl ip TestACL dscp 26 aggregate Policer any