Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Example: Configuring Multilink Frame Relay FRF.16

Requirements

Before you begin, you should have two MX Series 3D Universal Edge Routers configured with at least two serial interfaces that communicate over serial links.

Overview

In this example, you aggregate two T1 interfaces to create an MLFR FRF.16 bundle on two MX Series, R0 and R1. You configure the chassis interface and specify the number of MLFR FRF.16 bundles to be created on the interface. You then specify the channel to be configured as a multilink bundle and create interface lsq-0/0/0:0. You set the multilink bundle as an MLFR FRF.16 bundle by specifying the MLFR UNI NNI encapsulation type.

Then you define R0 as a DCE device and R1 as a DTE device. You configure a logical unit on the multilink bundle lsq-0/0/0:0, and set the family type to inet. You then assign a DLCI of 400 and an IP address of 10.0.0.10/24 to the multilink bundle. You create the T1 interfaces, t1-2/0/0 and t1-2/0/1, that are to be added as constituent links to the multilink bundle and define the Frame Relay encapsulation type. Finally, you set the multilink bundle to lsq-0/0/0:0.

Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.

Step-by-Step Procedure

1. Configure a chassis interface.
   [edit]user@host# edit chassis
2. Specify the number of MLFR bundles.
   [edit chassis]user@host# set fpc 0 pic 0 mlfr-uni-nni-bundles 1
3. Create an interface.
   [edit]user@host# edit interfaces lsq-0/0/0:0
4. Specify the MLFR encapsulation type.
   [edit interfaces lsq-0/0/0:0]user@host# set encapsulation multilink-frame-relay-uni-nni
5. Set the router R0 as a DCE device.
   [edit]user@host# edit interfaces lsq-0/0/0user@host# set dce
6. Specify a logical unit on the multilink bundle and set the family type.
   [edit interfaces lsq-0/0/0]user@host# set unit 0 dlci 400 family inet address 10.0.0.10/24
7. Create the T1 interfaces and set the Frame Relay encapsulation.
   [edit interfaces]user@host# set t1-2/0/0 encapsulation multilink-frame-relay-uni-nniuser@host# set t1-2/0/1 encapsulation multilink-frame-relay-uni-nni
8. Specify the multilink bundle to which the interface is to be added as a constituent link on device R0.
   [edit interfaces t1-2/0/0]user@host# set unit 0 family mlfr-uni-nni bundle lsq-0/0/0:0
9. Specify the multilink bundle to which the interface is to be added as a constituent link on device R1.
   [edit interfaces t1-2/0/1]user@host# set unit 0 family mlfr-uni-nni bundle lsq-0/0/0:0

Results

From configuration mode, confirm your configuration by entering the show chassis, show interfaces lsq-0/0/0, show interfaces lsq-0/0/0:0, show interfaces t1-2/0/0, and show interfaces t1-2/0/1 commands for the routers R0 and R1. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

If you are done configuring the device, enter commit from configuration mode.

Verification

Confirm that the configuration is working properly:

• Verifying the MLFR FRF.16 Configuration

Verifying the MLFR FRF.16 Configuration

Purpose

Verify the MLFR FRF.16 configuration.

Action

From operational mode, enter the show interfaces command.