Configuring Link Services and CoS

To configure link services and CoS on an AS or MultiServices PIC, you must perform the following steps:

1. Enable the Layer 2 service package. You enable service packages per PIC, not per port. When you enable the Layer 2 service package, the entire PIC uses the configured package. To enable the Layer 2 service package, include the service-package statement at the [edit chassis fpc slot-number pic pic-number adaptive-services] hierarchy level, and specify layer-2:

   service-package layer-2;

   For more information about AS or MultiServices PIC service packages, see Enabling Service Packages and Layer 2 Service Package Capabilities and Interfaces.

2. Configure a multilink PPP or FRF.16 bundle by combining constituent links into a virtual link, or bundle.

   Configuring an MLPPP Bundle

   To configure an MLPPP bundle, configure constituent links and bundle properties by including the following statements in the configuration:

   [edit interfaces interface-name unit logical-unit-number]

   encapsulation ppp;

   family mlppp {

   bundle lsq-fpc/pic/port.logical-unit-number;

   }

   [edit interfaces lsq-fpc/pic/port unit logical-unit-number]

   drop-timeout milliseconds;

   encapsulation multilink-ppp;

   fragment-threshold bytes;

   link-layer-overhead percent;

   minimum-links number;

   mrru bytes;

   short-sequence;

   family inet {

   address address;

   }

   For more information about these statements, see the Link and Multilink Services Configuration Guidelines.

   Configuring an MLFR FRF.16 Bundle

   To configure an MLFR FRF.16 bundle, configure constituent links and bundle properties by including the following statements in the configuration:

   [edit chassis fpc slot-number pic slot-number]

   mlfr-uni-nni-bundles number;

   [edit interfaces interface-name]

   encapsulation multilink-frame-relay-uni-nni;

   unit logical-unit-number {

   family mlfr-uni-nni {

   bundle lsq-fpc/pic/port:channel;

   }

   }

   For more information about the mlfr-uni-nni-bundles statement, see the JUNOS System Basics Configuration Guide. MLFR FRF.16 uses channels as logical units.

   For MLFR FRF.16, you must configure one end as data circuit-terminating equipment (DCE) by including the following statements at the [edit interfaces lsq-fpc/pic/port:channel] hierarchy level.

   encapsulation multilink-frame-relay-uni-nni;

   dce;

   mlfr-uni-nni-options {

   acknowledge-retries number;

   acknowledge-timer milliseconds;

   action-red-differential-delay (disable-tx | remove-link);

   drop-timeout milliseconds;

   fragment-threshold bytes;

   hello-timer milliseconds;

   link-layer-overhead percent;

   lmi-type (ansi | itu);

   minimum-links number;

   mrru bytes;

   n391 number;

   n392 number;

   n393 number;

   red-differential-delay milliseconds;

   t391 number;

   t392 number;

   yellow-differential-delay milliseconds;

   }

   unit logical-unit-number {

   dlci dlci-identifier;

   family inet {

   address address;

   }

   }

   For more information about MLFR UNI NNI properties, see Link and Multilink Services Configuration Guidelines.

3. To configure CoS components for each multilink bundle, enable per-unit scheduling on the interface, configure a scheduler map, apply the scheduler to each queue, configure a fragmentation map, and apply the fragmentation map to each bundle. Include the following statements:

   [edit interfaces]

   lsq-fpc/pic/port {

   per-unit-scheduler; # Enables per-unit scheduling on the bundle

   }

   [edit class-of-service]

   interfaces {

   lsq-fpc/pic/port { # Multilink PPP

   unit logical-unit-number {

   scheduler-map map-name; # Applies scheduler map to each queue

   }

   }

   lsq-fpc/pic/port:channel { # MLFR FRF.16

   unit logical-unit-number {

   # Scheduler map provides scheduling information for

   # the queues within a single DLCI.

   scheduler-map map-name;

   shaping-rate percent percent;

   }

   forwarding-classes {

   queue queue-number class-name priority (high | low);

   }

   scheduler-maps {

   map-name {

   forwarding-class class-name scheduler scheduler-name;

   }

   }

   schedulers {

   scheduler-name {

   buffer-size (percent percentage | remainder | temporal microseconds);

   priority priority-level;

   transmit-rate (percent percentage | rate | remainder) <exact>;

   }

   }

   fragmentation-maps {

   map-name {

   forwarding-class class-name {

   fragment-threshold bytes;

   no-fragmentation;

   }

   }

   }

   Associate a fragmentation map with a multilink PPP interface or MLFR FRF.16 DLCI by including the following statements at the [edit class-of-service] hierarchy level:

   interfaces {

   lsq-fpc/pic/port {

   unit logical-unit-number { # Multilink PPP

   fragmentation-map map-name;

   }

   }

   lsq-fpc/pic/port:channel { # MLFR FRF.16

   unit logical-unit-number {

   fragmentation-map map-name;

   }