From: Church, Chuck (cchurch@netcogov.com)
Date: Wed Jul 13 2005 - 23:13:05 GMT-3
The fragmentation will occur on all frames going out. Not fragmenting
certain types of traffic would defeat the purpose of fragmenting in the
first place. You fragment to reduce serialization delay to support
real time traffic (lower latency). If you allowed big frames through,
the serialization delay would go back up, increasing latency and jitter
for those frames following...
Chuck Church
Lead Design Engineer
CCIE #8776, MCNE, MCSE
Netco Government Services - Design & Implementation Team
1210 N. Parker Rd.
Greenville, SC 29609
Home office: 864-335-9473
Cell: 703-819-3495
cchurch@netcogov.com
PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x4371A48D
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Varthis Vassilantonakis
Sent: Tuesday, July 12, 2005 4:31 PM
To: ccielab@groupstudy.com
Subject: frame-relay fragment issues
Hi group,
I have a FR connection 256kbps and I have configured a map-class like
the following:
map-class frame-relay FRTS
frame-relay cir 256000
frame-relay bc 32000
frame-relay mincir 192000
frame-relay fragment 320
Does the "frame-relay fragment 320" command under the above class issue
a 320 bytes fragment for all traffic passing through the frame-relay
interface on which we assigned the class?
Is there any way to exclude a specific type of traffic (like ftp for
example) from the above fragmentation?
TIA
Varthis
This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:00:29 GMT-3