Overview of LFI in MLPPP
Except on the first page, right running head:
Heading1 or Heading1NewPage text (automatic)
377
Alcatel-Lucent
Beta
Beta
CLI Configuration Guide
O
VERVIEW
OF
LFI
IN
MLPPP
Multilink is negotiated during the initial LCP option negotiation. It permits a system
to indicate to its peer that it is capable of combining multiple physical links into a
"bundle". A system indicates to its peer that it is willing to do multilink by sending
the multilink option as part of the initial LCP option negotiation. Refer to RFC 1990
for further details.
Fragments are created on the MLPPP link based on the ‘fragment delay’
configured on the MLPPP bundle interface. The fragment size is calculated based
on the fragment delay value and the link speed. Hence, fragment size could be
different for different links on the same MLPPP bundle based on different link
speeds.
To interleave the voice packets and data fragments, QoS policy must be
configured on the MLPPP bundle. This will make sure that the same QoS policy is
applied to all the link interfaces in the MLPPP bundle and hence similar treatment
is done to packets irrespective of which link eventually it passes through.
Slippage on multilink interface allows configuration of buffer in terms of MRU,
which represent number of fragments to be stored without getting reassembled.
The default value will be 32 MRU size packets to be stored. The range will be 16-
256 MRU worth of data.
P
ACKET
F
ORMATS
Network Protocol packets are first encapsulated according to the normal PPP
procedures (2 bytes of Protocol ID of the Network Protocol being carried through
PPP), and large packets are broken up into multiple segments sized appropriately
(based on serialization delay configured). Sender must not include the Address
and Control Field (2 bytes) in the logical entity to be fragmented. A new PPP
header consisting of the Multilink Protocol Identifier, and the Multilink header is
inserted before each section. (Thus the first fragment of a multilink packet in PPP
will have two headers, one for the fragment, followed by the header for the packet
itself containing the Network Protocol ID).
PPP multilink fragments are encapsulated using the protocol identifier 0x00-0x3d.
Following the protocol identifier is a four byte header containing a sequence
number, and two one bit fields indicating that the fragment begins a packet or
terminates a packet.
Individual fragments by default will have long sequence number, therefore, have
the following format:
Summary of Contents for OmniAccess 700
Page 38: ...Left running head Chapter name automatic 12 Beta Beta CLI Configuration Guide Alcatel Lucent ...
Page 176: ...Left running head Chapter name automatic 150 Beta Beta CLI Configuration Guide Alcatel Lucent ...
Page 260: ...Left running head Chapter name automatic 234 Beta Beta CLI Configuration Guide Alcatel Lucent ...
Page 434: ...Left running head Chapter name automatic 408 Beta Beta CLI Configuration Guide Alcatel Lucent ...
Page 464: ...Left running head Chapter name automatic 438 Beta Beta CLI Configuration Guide Alcatel Lucent ...
Page 638: ...Left running head Chapter name automatic 612 Beta Beta CLI Configuration Guide Alcatel Lucent ...
Page 940: ...Left running head Chapter name automatic 914 Beta Beta CLI Configuration Guide Alcatel Lucent ...
Page 1002: ...Left running head Chapter name automatic 976 Beta Beta CLI Configuration Guide Alcatel Lucent ...
Page 1120: ...Left running head Chapter name automatic 2 Beta Beta CLI Configuration Guide Alcatel Lucent ...
