To configure MCML on a link services IQ interface, you must specify how many multilink
classes should be negotiated when a link joins the bundle, and you must specify the
mapping of a forwarding class into an MCML class.
To specify how many multilink classes should be negotiated when a link joins the bundle,
include the multilink-max-classes statement:
multilink-max-classes number;
You can include this statement at the following hierarchy levels:
•
[edit interfaces interface-name unit logical-unit-number]
•
[edit logical-systems logical-system-name interfaces interface-name
unit logical-unit-number]
The number of multilink classes can be 1 through 8. The number of multilink classes for
each forwarding class must not exceed the number of multilink classes to be negotiated.
NOTE: In ACX Series routers, the multilink classes can be 1 through 4.
To specify the mapping of a forwarding class into a MCML class, include the multilink-class
statement at the [edit class-of-service fragmentation-maps map-name forwarding-class
class-name] hierarchy level:
[edit class-of-service fragmentation-maps map-name forwarding-class class-name]
multilink-class number;
The multilink class index number can be 0 through 7. The multilink-class statement and
no-fragmentation statements are mutually exclusive.
NOTE: In ACX Series routers, the multilink class index number can be 0
through 3. ACX Series routers do not support the no-fragmentation statement
for fragmentation map.
To view the number of multilink classes negotiated, issue the show interfaces
lsq-fpc/pic/port.logical-unit-number detail command.
Related
Documentation
Layer 2 Service Package Capabilities and Interfaces•
• Configuring LSQ Interfaces as NxT1 or NxE1 Bundles Using MLPPP
• Configuring LSQ Interfaces for ATM2 IQ Interfaces Using MLPPP
• Configuring LSQ Interfaces for T3 Links Configured for Compressed RTP over MLPPP
• Link Services Configuration for Junos Interfaces
519Copyright © 2017, Juniper Networks, Inc.
Chapter 17: Configuring MLPPP