RE: Traffic shaping values

From: Jerry Haverkos (jhaverkos@columbus.rr.com)
Date: Thu Mar 20 2003 - 12:38:09 GMT-3


Hunt

For Voice Cisco recommends mincir=cir. This is meant to eliminate voice
packets being tagged with the DE bit and periodically dropped by the
"Cloud".

In your case mincir-cir=32000

As you stated Cisco recommends Bc=cir/100. That would be 320 in your case.
This parameter is meant to make Tc much smaller than normal. It is meant to
even out the transmission of real time data to eliminate "jitter".

Excess Burst (Be) should always be 0 for voice, again to keep from
transmitting above the contracted CIR and thus having voice packets tagged
with the DE bit.

If your pvc is for voice, I have no idea where they got their values.

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Hunt Lee
Sent: Thursday, March 20, 2003 9:04 AM
To: ccielab@groupstudy.com
Subject: Traffic shaping values

Hi Group,

I bummed into one last question for the day...

R2 --- Frame --- R3

Clockrate on all interfaces are set to 64000
MTU size = 750
CIR between the PVC is 32k

The solution config I got is:-

traffic-shape rate 32000 4000 4000 1000

How did they get to these bc, be & byte limit values?

I have done some research on CCO, and Cisco seems to advice that when doing
traffic
shaping on Voice:

Bc = CIR / 100 = 320
Be = 0
Byte limit = I couldnt find anything on this

Any help would be greatly appreciated.

Regards,
Lee

http://mobile.yahoo.com.au - Yahoo! Mobile
- Check & compose your email via SMS on your Telstra or Vodafone mobile.



This archive was generated by hypermail 2.1.4 : Sat Apr 05 2003 - 08:51:42 GMT-3