Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Examples: Bundling Multiple Frame Relay DLCIs into a Single Link Using MLFR

 

This example shows how to configure MLFR FRF.16 for additional bandwidth, load balancing, and redundancy.

Requirements

Before you begin, you should have two MX Series 5G Universal Routing Platforms 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

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 in the CLI User Guide.

To configure an MLFR FRF.16 bundle:

  1. Configure a chassis interface.
  2. Specify the number of MLFR bundles.
  3. Create an interface.
  4. Specify the MLFR encapsulation type.
  5. Set the router R0 as a DCE device.
  6. Specify a logical unit on the multilink bundle and set the family type.
  7. Create the T1 interfaces and set the Frame Relay encapsulation.
  8. Specify the multilink bundle to which the interface is to be added as a constituent link on device R0.
  9. Specify the multilink bundle to which the interface is to be added as a constituent link on device R1.

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

Purpose

Verify the MLFR FRF.16 configuration.

Action

From operational mode, enter the show interfaces command.

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 MX Series 5G Universal Routing Platforms (MX240, MX480, or MX960 routers) 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 MX Series routers, 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. You specify the names of the constituent links to be added to the multilink bundle as t1-2/0/0 and t1-2/0/1 and 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 (range is from 16 through 1022). 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

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 in the CLI User Guide.

To configure the MLFR FRF.15 bundle:

  1. Create an interface on both the routers.
  2. Set a logical unit on the interface and define the family type for the routers R0 and R1.
  3. Define the multilink bundle as an MLFR FRF.15 bundle.
  4. Specify the names of the constituent links to be added to the multilink bundle.
  5. Define the router R0 as a DCE device.
  6. Specify the DLCI as well as the multilink bundle to which the interface is to be added.

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.

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

Verification

Confirm that the configuration is working properly:

Verifying the MLFR FRF.15 Configuration

Purpose

Verify the MLFR FRF.15 configuration.

Action

From operational mode, enter the show interfaces command.

For link services interfaces only, you can configure multiple DLCIs for MLFR FRF.16 or MLPPP bundles.

DLCIs are not supported on multilink interfaces.

Configuring Point-to-Point DLCIs for MLFR FRF.16 and MLPPP Bundles

For link services interfaces only, you can configure multiple point-to-point DLCIs for each MLFR FRF.16 or MLPPP bundle. A channelized interface, such as ls-1/1/1:0, denotes a single MLFR FRF.16 bundle. To configure a DLCI, include the dlci statement:

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 DLCI identifier is a value from 16 through 1022. Numbers 1 through 15 are reserved for future use.

When you configure point-to-point connections, the maximum transmission unit (MTU) sizes on both sides of the connection must be the same.

Configuring Multicast-Capable DLCIs for MLFR FRF.16 Bundles

For link services interfaces only, you can configure multiple multicast-capable DLCIs for each MLFR FRF.16 bundle. A channelized interface, such as ls-1/1/1:0, denotes a single MLFR FRF.16 bundle. By default, Frame Relay connections assume unicast traffic. If your Frame Relay switch performs multicast replication, you can configure the link services connection to support multicast traffic by including the multicast-dlci statement:

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 DLCI identifier is a value from 16 through 1022 that defines the Frame Relay DLCI over which the switch expects to receive multicast packets for replication.

You can configure multicast support only on point-to-multipoint link services connections. Multicast-capable DLCIs are not supported on multilink interfaces.

If keepalives are enabled, causing the interface to send Local Management Interface (LMI) messages during idle times, the number of possible DLCI configurations is limited by the MTU selected for the interface. For more information, see Configuring Keepalives on Link Services Physical Interfaces.

Inline Multilink PPP (MLPPP), Multilink Frame Relay (FRF.16), and Multilink Frame Relay End-to-End (FRF.15) for time-division multiplexing (TDM) WAN interfaces provide bundling services through the Packet Forwarding Engine without requiring a PIC or Dense Port Concentrator (DPC).

Traditionally, bundling services are used to bundle multiple low-speed links to create a higher bandwidth pipe. This combined bandwidth is available to traffic from all links and supports link fragmentation and interleaving (LFI) on the bundle, reducing high priority packet transmission delay.

This support includes multiple links on the same bundle as well as multiclass extension for MLPPP. Through this service you can enable bundling services without additional DPC slots to support Service DPC and free up the slots for other MICs.

This example shows how to configure Multilink Frame Relay (FRF.16) for additional bandwidth, load balancing, and redundancy by aggregating low-speed links such as T1 (WAN interfaces).

Requirements

This example uses the following hardware and software components:

  • Two MX Series Routers

  • Junos OS Release 14.1 or later release

Before you begin, configure two MX Series routers (the MX240, MX480, or MX960) with at least two WAN interfaces that communicate over T1 links.

Overview

In this example, you aggregate T1 interfaces to create an MFR FRF.16 bundle on two MX Series routers, R0 and R1. You configure the chassis interface and specify the number of MFR 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-. You set the multilink bundle as an MFR FRF.16 bundle by specifying the multilink-frame-relay-uni-nni encapsulation type. Then you define Router R0 as a DCE device and Router R1 as a DTE device. You configure a logical unit on the multilink bundle lsq-, and set the family type to inet. You create the T1 interfaces, 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-.

Topology

Figure 1: Configuring Inline Multilink Frame Relay (FRF.16) for WAN Interfaces
Configuring Inline Multilink
Frame Relay (FRF.16) for WAN Interfaces

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.

Device R0

Device R1

To Configure Router R0

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode in the CLI User Guide.

To configure inline Multlink Frame Relay (FRF.16) for WAN Interfaces:

  1. Configure a chassis interface and specify the number of MFR bundles.
  2. Create the interface and specify the MFR encapsulation type.
  3. Set Router R0 as a DCE device.
  4. Specify the DLCI value.
  5. Specify a logical unit on the multilink bundle and set the family type.
  6. Create the T1 interfaces and set the Frame Relay encapsulation.
  7. Specify the multilink bundle to which the interface is to be added as a constituent link on Router R0.

To Configure Router R1

Step-by-Step Procedure

To configure inline Multilink Frame Relay (FRF.16) for WAN Interfaces:

  1. Configure a chassis interface and specify the number of MFR bundles.
  2. Create the interface and specify the MFR encapsulation type.
  3. Specify the DLCI value.
  4. Specify a logical unit on the multilink bundle and set the family type.
  5. Create the T1 interfaces and set the Frame Relay encapsulation.
  6. Specify the multilink bundle to which the interface is to be added as a constituent link on Router R1.

Results

For Router R0, from configuration mode, confirm your configuration by entering the show chassis, show interfaces lsq-1/0/0:0, show interfaces t1-1/0/0:5, and show interfaces t1-1/0/0:6 commands.

For Router R1, from configuration mode, confirm your configuration by entering the show chassis, show interfaces lsq-2/0/0:0, show interfaces t1-2/0/0:5, and show interfaces t1-2/0/0:6 commands.

If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.

For Router R0:

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

For Router R1:

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

Verification

Verifying the MFR FRF.16 Configuration

Purpose

Verify the MFR FRF.16 configuration.

Action

From operational mode, run the show interfaces lsq-1/0/0:0 extensive command.

Sample Output

From the operational mode, enter the show interfaces lsq-2/0/0:0 extensive command.