Alcatel-Lucent Specific Overview On Mlppp Features - Alcatel-Lucent OmniAccess 700 Cli Configuration Manual

Left running head:
Chapter name (automatic)
Multilink Point to Point Protocol
Figure 33: MLPPP Header in Short Sequence Number Format
A -L S
LCATEL UCENT PECIFIC
The following features are available with the current release:
•
The OmniAccess 700 supports RFC 1990 (MLPPP Protocol) without necessarily
conforming to all the optional items mentioned in the specification.
•
Specifically, the system supports the logical aggregation, into a configured
MLPPP bundle of any number of channelized or fractional T1 or E1 interfaces,
Serial (V.35/X.21) interfaces, etc. This bundle behaves like a virtual IP interface.
•
Multiple MLPPP bundles may be statically configured on the system. MLPPP
protocol negotiation or data reaching the system on an unconfigured interface are
dropped. Bundles cannot be deleted, but can be shutdown and thereby made
unusable.
•
Without any QoS configuration applied on the MLPPP bundle, the packet
distribution across the MLPPP member links within a bundle is handled in a
weighted round robin fashion, the weight being the bandwidth of the links.
•
Authentication optionally happens at each member link, and is supported through
PAP, CHAP or EAP as configured.
•
IP routing protocols as well as policies such as ACL, NAT, IDS, IPsec, QoS, etc.,
may be applied on the bundle.
•
The default MTU is 1500 on an MLPPP bundle interface. That makes the MRRU
(Maximum Received Restructured Unit) value to 1506 that accounts for the 6
extra bytes of the MLPPP header. If there are interoperability issues with the peer,
the MRRU value of the peer MLPPP interface has to be adjusted accordingly.
350
Beta
O MLPPP F
VERVIEW ON
Alcatel-Lucent
EATURES
CLI Configuration Guide
Beta