North American Network Operators Group|
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
RE: frame relay to atm conversion tool?
- From: Brennan_Murphy
- Date: Fri Jan 10 16:08:13 2003
I now have a prototype spreadsheet. Email
me offline if you are interested in
getting a copy...maybe helping in making
it more accurate.
From: Peter E. Fry [mailto:firstname.lastname@example.org]
Sent: Thursday, January 09, 2003 10:46 PM
Subject: RE: frame relay to atm conversion tool?
On 9 Jan 2003 at 17:45, Swaminathan, Sekar wrote:
> Instead of Frame Relay frames, you have to look at the
> payload which is usually IP packets. Here is the formula
> that I would use: [...]
Specifying an "average packet size" is rough: I've observed that on
an "average Internet connection" around 35% of packets are 64 bytes,
35% 1500 bytes, and the remainder scattered about. The average is
guaranteed to be a poor match for at least 70% of your traffic.
Not that it matters. Most carriers configure FRATM VCCs as
"1536kbps frame relay = 4500cps", treating fractions accordingly.
The last thing you want to do is exceed this cell rate (around
1710kbps at a 1500-byte packet size), as on a policed link you'll
lose nonconforming cells. (Actually, a 1536kb frame relay seems to
be closer to a 1705kb ATM VCC. Eh, the IWF has to buffer some
anyway.) If you increase your cell rates you potentially
oversubscribe your frame link (and the IWF may disallow it in any
case). So if you're tempted to exceed this ratio be very certain of
your link characteristics.
Add to that: when a sustained rate is defined (VBR service
category) the ATM peak rate probably doesn't mean what you would
expect, so I recommend sustained = peak. (ABR is the best match for
data, but isn't often used.)
As to the original question, I wouldn't recommend translating a
burstable frame to ATM unless you can order an ABR VCC or get UPC
and/or frame discard disabled on your link (don't bet on it). It's
not likely you can match parameters, so without flow control you're
essentially looking at reduced performance or packet loss under load.
Whatever you do get, I recommend you ask your carrier for a spec.
You have plenty of variables and relatively robust protocols, meaning
you could take a shot, miss, and only find out for certain that you
had when you'd really rather not. Get it reasonably right, though,
and it'll do right by you.
Huh. Now that I look at it, I need to rethink my own figures yet
again (I haven't even implemented the last rethink) as I appear to
have tended toward the conservative in some areas. Grrr.
Take it easy.
Peter E. Fry