Configuring Multilink Frame Relay
The topics below discuss the overview and configuration details of Multilink Frame Relay (MLFR) FRF.15 and FRF.16 for security devices.
Understanding Multilink Frame Relay FRF.15
The link services intelligent queuing interface lsq-0/0/0 supports Multilink Frame Relay end-to-end (MLFR FRF.15).
With MLFR FRF.15, multilink bundles are configured as logical
units on the link services intelligent queuing interface, such as lsq-0/0/0.0. MLFR FRF.15 bundles combine multiple permanent
virtual circuits (PVCs) into one aggregated virtual circuit (AVC).
This process provides fragmentation over multiple PVCs on one end
and reassembly of the AVC on the other end. You can configure LFI
and CoS with MLFR in the same way that you configure them with MLPPP.
Example: Configuring Multilink Frame Relay FRF.15
This example shows how to configure MLFR FRF.15 for additional bandwidth, load balancing, and redundancy by aggregating low-speed links such as T1, E1, and serial links.
Requirements
Before you begin, you should have two Juniper Networks devices configured with at least two serial interfaces that communicate over serial links.
Overview
In this example, you aggregate two T1 links to create the MLFR FRF.15 bundle on two Juniper Networks devices, R0 and R1, and set the interface to lsq-0/0/0. You configure a logical unit on the lsq-0/0/0 interface and set the family type to inet with address 10.0.0.4/24. Then you configure an IP address for the multilink bundle on the unit level of the interface.
You define the multilink bundle as an MLFR FRF.15 bundle by specifying the MLFR end-to-end encapsulation type. Specify the names of the constituent links to be added to the multilink bundle as t1-2/0/0 and t1-2/0/1. You can then set the encapsulation type to frame relay. You then define R0 as a DCE device and R1 as a DTE device. You set the DLCI value to 100.The DLCI value range is 16 through 1022. Finally, you set the multilink bundle to lsq-0/0/0:0.
Configuration
Procedure
CLI Quick Configuration
To quickly configure this example, copy the
following command, paste it into a text file, remove any line breaks,
change any details necessary to match your network configuration,
copy and paste the command into the CLI at the [edit] hierarchy
level, and then enter commit from configuration mode.
For device R0 set interfaces lsq-0/0/0 unit 0 family inet address 10.0.0.4/24 set interfaces lsq-0/0/0 unit 0 encapsulation multilink-frame-relay-end-to-end set interfaces t1-2/0/0 encapsulation frame-relay set interfaces t1-2/0/1 encapsulation frame-relay set interfaces lsq-0/0/0:0 dce set interfaces lsq-0/0/0 unit 0 dlci 100 family mlfr-end-to-end bundle lsq-0/0/0.0
For device R1 set interfaces lsq-0/0/0 unit 0 family inet address 10.0.0.5/24 set interfaces lsq-0/0/0 unit 0 encapsulation multilink-frame-relay-end-to-end set interfaces t1-2/0/0 encapsulation frame-relay set interfaces t1-2/0/1 encapsulation frame-relay set interfaces lsq-0/0/0 unit 0 dlci 100 family mlfr-end-to-end bundle lsq-0/0/0.0
Step-by-Step Procedure
The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration Mode.
To configure the MLFR FRF.15 bundle:
Create an interface on both devices.
[edit] user@host# edit interfaces lsq-0/0/0 unit 0
Set a logical unit on the interface and define the family type for devices R0 and R1.
[edit interfaces lsq-0/0/0 unit 0] user@host# set family inet address 10.0.0.4/24 user@host# set family inet address 10.0.0.5/24
Define the multilink bundle as an MLFR FRF.15 bundle.
[edit interfaces lsq-0/0/0 unit 0] user@host# set encapsulation multilink-frame-relay-end-to-end
Specify the names of the constituent links to be added to the multilink bundle.
[edit interfaces] user@host# set t1-2/0/0 encapsulation frame-relay user@host# set t1-2/0/1 encapsulation frame-relay
Define device R0 as a DCE device.
[edit interfaces] user@host# edit lsq-0/0/0 user@host# set dce
Specify the DLCI as well as the multilink bundle to which the interface is to be added.
[edit interfaces lsq-0/0/0] user@host# set unit 0 dlci 100 family mlfr-end-to-end bundle lsq-0/0/0.0
Results
From configuration mode, confirm your configuration
by entering the show interfaces lsq-0/0/0, show interfaces
t1-2/0/0, and show interfaces t1-2/0/1 commands for
R0 and R1. If the output does not display the intended configuration,
repeat the configuration instructions in this example to correct it.
For device R0
[edit]
user@host# show interfaces lsq-0/0/0
dce;
unit 0 {
encapsulation multilink-frame-relay-end-to-end;
dlci 100;
family inet {
address 10.0.0.4/24;
}
family mlfr-end-to-end {
bundle lsq-0/0/0.0;
}
}
[edit]
user@host#show interfaces t1-2/0/0
encapsulation frame-relay;
[edit]
user@host# show interfaces t1-2/0/1
encapsulation frame-relay;
For device R1
[edit]
user@host# show interfaces lsq-0/0/0
unit 0 {
encapsulation multilink-frame-relay-end-to-end;
dlci 100;
family inet {
address 10.0.0.5/24;
}
family mlfr-end-to-end {
bundle lsq-0/0/0.0;
}
}
[edit]
user@host# show interfaces t1-2/0/0
encapsulation frame-relay;
[edit]
user@host# show interfaces t1-2/0/1
encapsulation frame-relay;
If you are done configuring the device, enter commit from configuration mode.
Understanding Multilink Frame Relay FRF.16
The link services intelligent queuing interface lsq-0/0/0 supports the Multilink Frame Relay (MLFR) user-to-network interface
(UNI) and network-to-network interface (NNI) (MLFR FRF.16).
MLFR FRF.16 configures multilink bundles as channels on the
link services intelligent queuing interface, such as lsq-0/0/0:0. A multilink bundle carries Frame Relay permanent virtual circuits
(PVCs), identified by their data-link connection identifiers (DLCIs).
Each DLCI is configured at the logical unit level of the link services
intelligent queuing interface and is also referred as a logical interface. Packet fragmentation and reassembly
occur on each virtual circuit. You can configure LFI and CoS with
MLFR in the same way that you configure them with MLPPP.
Example: Configuring Multilink Frame Relay FRF.16
This example shows how to configure MLFR FRF.16 for additional bandwidth, load balancing, and redundancy.
Requirements
Before you begin, you should have two Juniper Networks devices 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 Juniper Networks devices, 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.
Topology
Configuration
Procedure
CLI Quick Configuration
To quickly configure this example, copy the
following command, paste it into a text file, remove any line breaks,
change any details necessary to match your network configuration,
copy and paste the command into the CLI at the [edit] hierarchy
level, and then enter commit from configuration mode.
For device R0 set chassis fpc 0 pic 0 mlfr-uni-nni-bundles 1 set interfaces lsq-0/0/0:0 encapsulation multilink-frame-relay-uni-nni set interfaces lsq-0/0/0:0 dce set interfaces lsq-0/0/0:0 unit 0 dlci 400 family inet address 10.0.0.10/24 set interfaces t1-2/0/0 encapsulation multilink-frame-relay-uni-nni set interfaces t1-2/0/1 encapsulation multilink-frame-relay-uni-nni set interfaces t1-2/0/0 unit 0 family mlfr-uni-nni bundle lsq-0/0/0:0 set interfaces t1-2/0/1 unit 0 family mlfr-uni-nni bundle lsq-0/0/0:0 For device R1 set chassis fpc 0 pic 0 mlfr-uni-nni-bundles 1 set interfaces lsq-0/0/0:0 encapsulation multilink-frame-relay-uni-nni set interfaces lsq-0/0/0:0 unit 0 dlci 400 family inet address 10.0.0.9/24 set interfaces t1-2/0/0 encapsulation multilink-frame-relay-uni-nni set interfaces t1-2/0/1 encapsulation multilink-frame-relay-uni-nni set interfaces t1-2/0/0 unit 0 family mlfr-uni-nni bundle lsq-0/0/0:0 set interfaces t1-2/0/1 unit 0 family mlfr-uni-nni bundle lsq-0/0/0:0
Procedure
The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration Mode.
To configure an MLFR FRF.16 bundle:
-
Configure a chassis interface.
[edit] user@host# edit chassis
-
Specify the number of MLFR bundles.
[edit chassis] user@host# set fpc 0 pic 0 mlfr-uni-nni-bundles 1
-
Create an interface.
[edit] user@host# edit interfaces lsq-0/0/0:0
-
Specify the MLFR encapsulation type.
[edit interfaces lsq-0/0/0:0] user@host# set encapsulation multilink-frame-relay-uni-nni
-
Set device R0 as a DCE device.
[edit interfaces lsq-0/0/0:0] user@host# set dce
-
Specify a logical unit on the multilink bundle and set the family type.
[edit interfaces lsq-0/0/0:0] user@host# set unit 0 dlci 400 family inet address 10.0.0.10/24
-
Create the T1 interfaces and set the Frame Relay encapsulation.
[edit interfaces] user@host# set t1-2/0/0 encapsulation multilink-frame-relay-uni-nni user@host# set t1-2/0/1 encapsulation multilink-frame-relay-uni-nni
-
Specify the multilink bundle to which the interface is to be added as a constituent link on the devices R0 and R1.
[edit interfaces t1-2/0/0] user@host# set unit 0 family mlfr-uni-nni bundle lsq-0/0/0:0
-
Specify the multilink bundle to which the interface is to be added as a constituent link on the devices R0 and 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 commands for devices R0 and R1. If the output does
not display the intended configuration, repeat the configuration
instructions in this example to correct it.
For device R0
[edit chassis]user@host#show fpc 0 { pic 0 { mlfr-uni-nni-bundles 1; } }
[edit interfaces lsq-0/0/0:0]user@host#show dce; encapsulation multilink-frame-relay-uni-nni; unit 0 { dlci 400; family inet { address 10.0.0.10/24; } }
[edit interfaces t1-2/0/0]user@host#show encapsulation multilink-frame-relay-uni-nni; unit 0 { family mlfr-uni-nni { bundle lsq-0/0/0:0; } }
[edit interfaces t1-2/0/1]user@host#show encapsulation multilink-frame-relay-uni-nni; unit 0 { family mlfr-uni-nni { bundle lsq-0/0/0:0; } }
For device R1
[edit chassis]user@host#show fpc 0 { pic 0 { mlfr-uni-nni-bundles 1; } }
[edit interfaces lsq-0/0/0:0]user@host#show encapsulation multilink-frame-relay-uni-nni;
[edit interfaces t1-2/0/0]user@host#show encapsulation multilink-frame-relay-uni-nni; unit 0 { family mlfr-uni-nni { bundle lsq-0/0/0:0; } }
[edit interfaces t1-2/0/1]user@host#show encapsulation multilink-frame-relay-uni-nni; unit 0 { family mlfr-uni-nni { bundle lsq-0/0/0:0; }
If you are done configuring the device, enter commit from
configuration mode.