You may have a CIR of 16k with bursting capabilities.  The problem with
bursting is, if you do it too much it will slow you down.  You may want to get
your frame relay provider on the phone and have them run some reporting on your
circuit to find out what/how much bursting you are doing during normal business
hours.

At a previous site we increased a circuit from 56k to 384k and it didn't help.
AT&T finally did some intrusive testing and placed the circuit on on "high
alert".  The scheduled to have a tech at both ends of the circuit, 1 from AT&T
and the other from the local telco after the intrusive test to do a different
kind of test.  After the intrusive test the circuit cleared up and worked
great.  AT&T said they didn't do anything to the circuit and didn't find
anything wrong during the intrusive test.  We canceled the other test out of
fear they might mess things up.

Hope this helps some,

Larry Barnes

"news.dial.oleane.com" wrote:

> Hello,
>
> Currently, we are running an application on HP3000 through a WAN network
> (permanent ISDN 64k LS).
> The network is a "star", and the HP3k is at the center.
> People are working on PCs connected in  LANs with IP.
>
> We want to migrate the network on a Frame-Relay cloud.
> The issue, is that users are complaining that response time are very slow
> now (about 2x or 3x more).
>
> Are there some parameters to change on the HP3000 which would be more
> appropriate to FR ?
>
> I saw that it was not a line issue, because traffic is under the CIR (16k)
> on FR 64k.
> Moreover we are authorized to burst to the access speed (confirmed with the
> transfer of a big file).
> We installed also the compression on the FR, as on the ISDN previous links,
> but it's still the same.
>
> Any idea are welcome...
>
> Eric