Avaya Configuring Frame Relay Services Manual de usuario Pagina 40

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 94
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 39
Configuring Frame Relay Services
2-20 117376-A Rev. A
For example, a typical TFTP frame is 548 bytes. If the CIR is 16,000 bits, the B
c
configured according to the 1/4 guideline would be 4,000 bits, or 500 bytes, which
is not big enough to accommodate a TFTP frame. If you set the B
c
to 16,000/2, or
1/2 CIR, the result is 8,000 bits, or a packet size of 1,000 bytes, which works, but
may result in excessive queuing because the T
c
is 1/2 second. If you set the B
c
to
16,000/3 or 1/3 of CIR, the result is a B
c
of 5,333 bits or 666 bytes, much closer to
the 548 TFTP frame size.
If you cannot predict the typical frame size, monitor frame relay shaping statistics
for numbers of large frames and dropped frames. If either of these numbers is
increasing constantly or dramatically, adjust the B
c
to a higher value in small
increments.
WCP and CIR Enforcement
Data compression maximizes throughput and increases reliability. Traffic shaping
increases reliability, controls congestion, and prioritizes traffic. Compression and
traffic shaping together maximize reliability, but at the expense of throughput.
Traffic shaping occurs at the VC level; compression, at the driver level. Shaping
therefore occurs before compression, which compromises effective compression
because only the precompressed traffic is shaped: the compressed traffic is not
shaped. WCP compresses data at the rate it receives it, which with traffic shaping
is the CIR. It is therefore unrealistic to expect a high compression throughput for
data that originates from a site that also uses traffic shaping.
You can use traffic shaping at one or both ends of a link, but you must use
compression at both ends of a link. It makes sense to use traffic shaping at a
central site, where you have a T1 line that sends data to remote sites with 64 KB
line rates, and the goal is to control the flow of traffic and avoid flooding the
remote sites. But if the CIR is equal to the line rate, which could well be the case
at the remote site with 64 KB line rates, there is no need to use traffic shaping.
You can use compression effectively in the case of the 64 KB site which does not
use traffic shaping. You can also compensate for the throughput cost associated
with using compression and traffic shaping at the central site by taking into
account characteristics of compression and traffic shaping, and fine-tuning traffic
shaping parameters.
When you configure traffic shaping, take into account the compression ratio
you want to achieve.
Vista de pagina 39
1 2 ... 35 36 37 38 39 40 41 42 43 44 45 ... 93 94

Comentarios a estos manuales

Sin comentarios