Alcatel-Lucent OmniAccess 700, Cli Configuration Manual

Page: 418 / 1193

Link Fragmentation and Interleaving (LFI)
Left running head:
Chapter name (automatic)
392
Beta Beta
CLI Configuration Guide
Alcatel-Lucent
O
VERVIEW OF
LFI
IN
F
RAME
R
ELAY
LFI is supported for FR and FR sub-interfaces.
LFI in FR is implemented through End-to-End Fragmentation technique as per the
FRF.12 Frame Relay Forum Standard. End-to-End fragmentation is limited to
fragmenting frames on selected PVCs. Since DLCI 0 is never carried end-to-end,
it is never fragmented using End-to-End fragmentation.
Fragments are created on the FR link based on the fragment size configured on
FR interface. The fragment size is fixed irrespective of the underlying link speed.
To decrease the serialization delay, interleaving functionality must be performed.
Interleaving functionality is implemented through QoS configured on the FR
interface.
E
ND
-
TO
-E
ND
F
RAGMENTATION
End-to-End fragmentation is used between two end devices and is restricted to
use on PVCs only. It is useful when the PVC is configured through slower trunk
interfaces.
P
ACKET
F
ORMATS
End-to-End Fragmentation Format
For End-to-End fragmentation, a two-octet fragmentation header follows the
FRF.3.1 multiprotocol encapsulation header. The Network Layer Protocol ID
(NLPID) 0xB1 has been assigned to identify this fragmentation header format.
Figure 42: End-to-End Fragmentation Format
The (C)ontrol bit is set to 0 in all fragments. It is reserved for future control
functions. There is a separate sequence number maintained for each fragmented
PVC between DTE peers.