Examples: Bundling Multiple Frame Relay DLCIs into a Single Link Using MLFR
Example: Configuring a Multilink Interface with MLFR FRF.15
[edit interfaces]
ml-1/0/0 {
unit 1 {
encapsulation multilink-frame-relay-end-to-end;
family inet {
address 192.168.5.2/32 {
destination 192.168.5.3;
}
}
}
unit 10 {
encapsulation multilink-frame-relay-end-to-end;
family inet {
address 10.1.1.3/32 {
destination 10.1.1.2;
}
}
}
}
t1-5/1/0 {
unit 0 {
dlci 16;
encapsulation multilink-frame-relay-end-to-end;
family mlfr-end-to-end {
bundle ml-1/0/0.1;
}
}
}
t1-5/1/1 {
unit 0 {
dlci 17;
encapsulation multilink-frame-relay-end-to-end;
family mlfr-end-to-end {
bundle ml-1/0/0.10;
}
}
}
t1-5/1/2 {
unit 0 {
dlci 26;
encapsulation multilink-frame-relay-end-to-end;
family mlfr-end-to-end {
bundle ml-1/0/0.10;
}
}
}
See Also
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 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
Procedure
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.
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 dce set interfaces lsq-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 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
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 Junos OS CLI User Guide.
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 the router R0 as a DCE device.
[edit] user@host# edit interfaces lsq-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] 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 device R0.
[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 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.
For device R0
[edit]
user@host# show chassis
fpc 0 {
pic 0 {
mlfr-uni-nni-bundles 1;
}
}
[edit]
user@host# show interfaces lsq-0/0/0
dce;
unit 0 {
dlci 400;
family inet {
address 10.0.0.10/24;
}
}
[edit]
user@host# show interfaces lsq-0/0/0:0
encapsulation multilink-frame-relay-uni-nni;
[edit]
user@host# show interfaces t1-2/0/0
encapsulation multilink-frame-relay-uni-nni;
unit 0 {
family mlfr-uni-nni {
bundle lsq-0/0/0:0;
}
}
[edit]
user@host# show interfaces t1-2/0/1
encapsulation multilink-frame-relay-uni-nni;
unit 0 {
family mlfr-uni-nni {
bundle lsq-0/0/0:0;
}
}
For device R1
[edit]
user@host# show chassis
unit 0 {
dlci 400;
family inet {
address 10.0.0.9/24;
}
}
[edit]
user@host# show interfaces lsq-0/0/0:0
encapsulation multilink-frame-relay-uni-nni;
[edit]
user@host# show interfaces t1-2/0/0
encapsulation multilink-frame-relay-uni-nni;
unit 0 {
family mlfr-uni-nni {
bundle lsq-0/0/0:0;
}
}
[edit]
user@host# show interfaces t1-2/0/1
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.
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 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
Procedure
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.
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 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 in the Junos OS CLI User Guide.
To configure the MLFR FRF.15 bundle:
Create an interface on both the routers.
[edit] user@host# edit interfaces lsq-0/0/0 unit 0
Set a logical unit on the interface and define the family type for the routers 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 the router 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 router, enter commit from configuration mode.
Configuring DLCIs on Link Services Logical Interfaces
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
- Configuring Multicast-Capable DLCIs for MLFR FRF.16 Bundles
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:
dlci dlci-identifier;
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:
multicast-dlci dlci-identifier;
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.
See Also
Example: Configuring a Link Services PIC with MLFR FRF.16
[edit chassis]
fpc 1 {
pic 2 {
mlfr-uni-nni-bundles 5;
}
}
[edit interfaces]
t1-0/0/0 {
encapsulation multilink-frame-relay-uni-nni;
unit 0 {
family mlfr-uni-nni {
bundle ls-1/2/0:0;
}
}
}
t1-0/0/1 {
encapsulation multilink-frame-relay-uni-nni;
unit 0 {
family mlfr-uni-nni {
bundle ls-1/2/0:0;
}
}
}
ls-1/2/0:0 {
dce;
encapsulation multilink-frame-relay-uni-nni;
unit 0 {
dlci 26;
family inet {
address 10.26.1.1/32 {
destination 10.26.1.2;
}
}
}
}
See Also
Example: Configuring Inline Multilink Frame Relay (FRF.16) for WAN 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
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
set chassis fpc 1 pic 0 mlfr-uni-nni-bundles-inline 1 set interfaces lsq-1/0/0:0 dce set interfaces lsq-1/0/0:0 encapsulation multilink-frame-relay-uni-nni set interfaces lsq-1/0/0:0 unit 0 dlci 10 set interfaces lsq-1/0/0:0 unit 1 dlci 20 set interfaces lsq-1/0/0:0 unit 0 family inet address 10.1.1.1/24 set interfaces lsq-1/0/0:0 unit 1 family inet address 192.0.2.1./24 set interfaces t1-1/0/0:5 encapsulation multilink-frame-relay-uni-nni set interfaces t1-1/0/0:6 encapsulation multilink-frame-relay-uni-nni set interfaces t1-1/0/0:5 unit 0 family mlfr-uni-nni bundle lsq-1/0/0:0 set interfaces t1-1/0/0:6 unit 0 family mlfr-uni-nni bundle lsq-1/0/0:0
Device R1
set chassis fpc 2 pic 0 mlfr-uni-nni-bundles-inline 1 set interfaces lsq-2/0/0:0 encapsulation multilink-frame-relay-uni-nni set interfaces lsq-2/0/0:0 unit 0 dlci 10 set interfaces lsq-2/0/0:0 unit 1 dlci 20 set interfaces lsq-2/0/0:0 unit 0 family inet address 10.1.1.2/24 set interfaces lsq-2/0/0:0 unit 1 family inet address 192.0.2.2/24 set interfaces t1-2/0/0:5 encapsulation multilink-frame-relay-uni-nni set interfaces t1-2/0/0:6 encapsulation multilink-frame-relay-uni-nni set interfaces t1-2/0/0:5 unit 0 family mlfr-uni-nni bundle lsq-2/0/0:0 set interfaces t1-2/0/0:6 unit 0 family mlfr-uni-nni bundle lsq-2/0/0:0
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 Junos OS CLI User Guide.
To configure inline Multlink Frame Relay (FRF.16) for WAN Interfaces:
Configure a chassis interface and specify the number of MFR bundles.
[edit] user@R0# set chassis fpc 1 pic 0 mlfr-uni-nni-bundles-inline 1
Create the interface and specify the MFR encapsulation type.
[edit] user@R0# set interfaces lsq-1/0/0:0 encapsulation multilink-frame-relay-uni-nni
Set Router R0 as a DCE device.
[edit ] user@R0# set interfaces lsq-1/0/0:0 dce
Specify the DLCI value.
[edit] user@R0# set interfaces lsq-1/0/0:0 unit 0 dlci 10 user@R0# set interfaces lsq-1/0/0:0 unit 1 dlci 20
Specify a logical unit on the multilink bundle and set the family type.
[edit] user@R0# set interfaces lsq-1/0/0:0 unit 0 family inet address 10.1.1.1/24 user@R0# set interfaces lsq-1/0/0:0 unit 1 family inet address 192.0.2.1/24
Create the T1 interfaces and set the Frame Relay encapsulation.
[edit] user@R0# set interfaces t1-1/0/0:5 encapsulation multilink-frame-relay-uni-nni user@R0# set interfaces t1-1/0/0:6 encapsulation multilink-frame-relay-uni-nni
Specify the multilink bundle to which the interface is to be added as a constituent link on Router R0.
[edit] user@R0# set interfaces t1-1/0/0:5 unit 0 family mlfr-uni-nni bundle lsq-1/0/0:0 user@R0# set interfaces t1-1/0/0:6 unit 0 family mlfr-uni-nni bundle lsq-1/0/0:0
To Configure Router R1
Step-by-Step Procedure
To configure inline Multilink Frame Relay (FRF.16) for WAN Interfaces:
Configure a chassis interface and specify the number of MFR bundles.
[edit] user@R1# set chassis fpc 2 pic 0 mlfr-uni-nni-bundles-inline 1
Create the interface and specify the MFR encapsulation type.
[edit] user@R1# set interfaces lsq-2/0/0:0 encapsulation multilink-frame-relay-uni-nni
Specify the DLCI value.
[edit] user@R0# set interfaces lsq-2/0/0:0 unit 0 dlci 10 user@R0# set interfaces lsq-2/0/0:0 unit 1 dlci 20
Specify a logical unit on the multilink bundle and set the family type.
[edit] user@R0# set interfaces lsq-2/0/0:0 unit 0 family inet address 10.1.1.2/24 user@R0# set interfaces lsq-2/0/0:0 unit 1 family inet address 192.0.2.2/24
Create the T1 interfaces and set the Frame Relay encapsulation.
[edit] user@R1# set interfaces t1-2/0/0:5 encapsulation multilink-frame-relay-uni-nni user@R1# set interfaces t1-2/0/0:6 encapsulation multilink-frame-relay-uni-nni
Specify the multilink bundle to which the interface is to be added as a constituent link on Router R1.
[edit] user@R1# set interfaces t1-2/0/0:5 unit 0 family mlfr-uni-nni bundle lsq-2/0/0:0 user@R1# set interfaces t1-2/0/0:6 unit 0 family mlfr-uni-nni bundle lsq-2/0/0:0
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:
[edit]
user@R0# show chassis
fpc 1 {
pic 0 {
mlfr-uni-nni-bundles-inline 1;
}
}
[edit]
user@R0# show interfaces lsq-1/0/0:0
dce;
encapsulation multilink-frame-relay-uni-nni;
unit 0 {
dlci 10;
family inet {
address 10.1.1.1/24;
}
}
unit 1 {
dlci 20;
family inet {
address 192.0.2.1/24;
}
}
[edit]
user@R0# show interfaces t1-1/0/0:5
encapsulation multilink-frame-relay-uni-nni;
unit 0 {
family mlfr-uni-nni {
bundle lsq-1/0/0:0;
}
}
[edit]
user@R0# show interfaces t1-1/0/0:6
encapsulation multilink-frame-relay-uni-nni;
unit 0 {
family mlfr-uni-nni {
bundle lsq-1/0/0:0;
}
}
If you are done configuring the router, enter commit from configuration mode.
For Router R1:
[edit]
user@R1# show chassis
fpc 2{
pic 0 {
mlfr-uni-nni-bundles-inline 1;
}
}
[edit]
user@R1# show interfaces lsq-2/0/0:0
encapsulation multilink-frame-relay-uni-nni;
unit 0 {
dlci 10;
family inet {
address 10.1.1.2/24;
}
}
unit 1 {
dlci 20;
family inet {
address 192.0.2.2/24;
}
}
[edit]
user@R1# show interfaces t1-2/0/0:5
encapsulation multilink-frame-relay-uni-nni;
unit 0 {
family mlfr-uni-nni {
bundle lsq-2/0/0:0;
}
}
[edit]
user@R1# show interfaces t1-2/0/0:6
encapsulation multilink-frame-relay-uni-nni;
unit 0 {
family mlfr-uni-nni {
bundle lsq-2/0/0:0;
}
}
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
command-name
user@R0> show interfaces lsq-1/0/0:0 extensive
Physical interface: lsq-1/0/0:0, Enabled, Physical link is Up
Interface index: 261, SNMP ifIndex: 122042, Generation: 4955
Link-level type: Multilink-FR-UNI-NNI, MTU: 1508
Device flags : Present Running
Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
Last flapped : Never
Statistics last cleared: Never
Hold-times : Up 0 ms, Down 0 ms
Multilink Frame Relay UNI NNI bundle options:
Device type DCE
MRRU 1508
Bandwidth 3072kbps
Fragmentation threshold 0
Red differential delay limit 120
Yellow differential delay limit 72
Red differential delay action Remove link
Reassembly drop timer 65535
Links needed to sustain bundle 1
Link layer overhead 4.0 %
LIP Hello timer 10
Acknowledgement timer 4
Acknowledgement retries 2
Bundle class A
LMI type Q.933 Annex A
T391 LIV polling timer 10
T392 polling verification timer 15
N391 full status polling count 6
N392 error threshold 3
N393 monitored event count 4
Q.933 Annex A LMI settings: n392dce 3, n393dce 4, t392dce 15 seconds
LMI statistics:
Input : 52 (last seen 00:00:01 ago)
Output: 54 (last sent 00:00:01 ago)
DTE statistics:
Enquiries sent : 0
Full enquiries sent : 0
Enquiry responses received : 0
Full enquiry responses received : 0
DCE statistics:
Enquiries received : 44
Full enquiries received : 8
Enquiry responses sent : 46
Full enquiry responses sent : 8
Common statistics:
Unknown messages received : 0
Asynchronous updates received : 0
Out-of-sequence packets received : 0
Keepalive responses timedout : 1
Interface transmit statistics: Disabled
Traffic statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
IPv6 transit statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Multilink Frame Relay UNI NNI bundle errors:
Packet drops 0 (0 bytes)
Fragment drops 0 (0 bytes)
MRRU exceeded 0
Exception events 0
Multilink Frame Relay UNI NNI bundle statistics:
Frames fps Bytes bps
Multilink:
Input : 0 0 0 0
Output: 0 0 0 0
Network:
Input : 0 0 0 0
Output: 0 0 0 0
Multilink Frame Relay UNI NNI bundle links information:
Active bundle links 2
Removed bundle links 0
Disabled bundle links 0
Multilink Frame Relay UNI NNI active bundle links statistics:
Frames fps Bytes bps
t1-1/0/0:5
Up time: 00:08:18
Input : 0 0 0 0
Output: 0 0 0 0
Current differential delay 0.1 ms
Recent high differential delay 0.8 ms
Times over red diff delay 0
Times over yellow diff delay 0
LIP:add_lnk lnk_ack lnk_rej hello hel_ack lnk_rem rem_ack
Rcv: 2 1 0 50 49 0 0
Xmt: 16 2 0 49 50 1 0
t1-1/0/0:6
Up time: 00:08:18
Input : 0 0 0 0
Output: 0 0 0 0
Current differential delay 0.0 ms
Recent high differential delay 0.7 ms
Times over red diff delay 0
Times over yellow diff delay 0
LIP:add_lnk lnk_ack lnk_rej hello hel_ack lnk_rem rem_ack
Rcv: 2 1 0 50 49 0 0
Xmt: 16 2 0 49 50 1 0
Logical interface lsq-1/0/0:0.0 (Index 336) (SNMP ifIndex 122044) (Generation 6209)
Flags: Up Point-To-Point SNMP-Traps Encapsulation: Multilink-FR-UNI-NNI
Last flapped: 2014-04-24 04:13:05 PDT (00:08:18 ago)
Multilink class 0 status:
Received sequence number 0x0
Transmit sequence number 0xffffffff
Packet drops 0 (0 bytes)
Fragment drops 0 (0 bytes)
MRRU exceeded 0
Fragment timeout 0
Missing sequence number 0
Out-of-order sequence number 0
Out-of-range sequence number 0
Packet data buffer overflow 0
Fragment data buffer overflow 0
Multilink class drop timeout 0 (ms)
Statistics Frames fps Bytes bps
Bundle:
Multilink:
Input : 0 0 0 0
Output: 0 0 0 0
Network:
Input : 0 0 0 0
Output: 0 0 0 0
Link:
t1-1/0/0:5
Up time: 00:08:18
Input : 0 0 0 0
Output: 0 0 0 0
t1-1/0/0:6
Up time: 00:08:18
Input : 0 0 0 0
Output: 0 0 0 0
Multilink detail statistics:
Bundle:
Fragments:
Input : 0 0 0 0
Output: 0 0 0 0
Non-fragments:
Input : 0 0 0 0
Output: 0 0 0 0
Protocol inet, MTU: 1500, Generation: 6258, Route table: 0
Flags: Sendbcast-pkt-to-re
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.1.1/24, Local: 10.1.1.1, Broadcast: Unspecified, Generation: 4209
DLCI 10
Flags: Active
Total down time: 01:15:17 sec, Last down: 01:23:28 ago
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Logical interface lsq-1/0/0:0.1 (Index 337) (SNMP ifIndex 122067) (Generation 6210)
Flags: Up Point-To-Point SNMP-Traps Encapsulation: Multilink-FR-UNI-NNI
Last flapped: 2014-04-24 04:13:05 PDT (00:08:18 ago)
Multilink class 0 status:
Received sequence number 0x0
Transmit sequence number 0xffffffff
Packet drops 0 (0 bytes)
Fragment drops 0 (0 bytes)
MRRU exceeded 0
Fragment timeout 0
Missing sequence number 0
Out-of-order sequence number 0
Out-of-range sequence number 0
Packet data buffer overflow 0
Fragment data buffer overflow 0
Multilink class drop timeout 0 (ms)
Statistics Frames fps Bytes bps
Bundle:
Multilink:
Input : 0 0 0 0
Output: 0 0 0 0
Network:
Input : 0 0 0 0
Output: 0 0 0 0
Link:
t1-1/0/0:5
Up time: 00:08:18
Input : 0 0 0 0
Output: 0 0 0 0
t1-1/0/0:6
Up time: 00:08:18
Input : 0 0 0 0
Output: 0 0 0 0
Multilink detail statistics:
Bundle:
Fragments:
Input : 0 0 0 0
Output: 0 0 0 0
Non-fragments:
Input : 0 0 0 0
Output: 0 0 0 0
Protocol inet, MTU: 1500, Generation: 6260, Route table: 0
Flags: Sendbcast-pkt-to-re
Addresses, Flags: Is-Preferred Is-Primary
Destination: 192.0.2/24, Local: 192.0.2.1, Broadcast: Unspecified, Generation: 4207
DLCI 20
Flags: Active
Total down time: 01:15:17 sec, Last down: 01:23:28 ago
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
DLCI statistics:
Active DLCI :2 Inactive DLCI :0
From the operational mode, enter the show interfaces lsq-2/0/0:0
extensive command.
user@R1> show interfaces lsq-2/0/0:0 extensive
Physical interface: lsq-2/0/0:0, Enabled, Physical link is Up
Interface index: 232, SNMP ifIndex: 44389, Generation: 235
Link-level type: Multilink-FR-UNI-NNI,MTU: 1508
Device flags : Present Running
Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
Last flapped : Never
Statistics last cleared: Never
Hold-times : Up 0 ms, Down 0 ms
Multilink Frame Relay UNI NNI bundle options:
Device type DTE
MRRU 1508
Bandwidth 3072kbps
Fragmentation threshold 0
Red differential delay limit 120
Yellow differential delay limit 72
Red differential delay action Remove link
Reassembly drop timer 65535
Links needed to sustain bundle 1
Link layer overhead 4.0 %
LIP Hello timer 10
Acknowledgement timer 4
Acknowledgement retries 2
Bundle class A
LMI type Q.933 Annex A
T391 LIV polling timer 10
T392 polling verification timer 15
N391 full status polling count 6
N392 error threshold 3
N393 monitored event count 4
Q.933 Annex A LMI settings: n391dte 6, n392dte 3, n393dte 4, t391dte 10 seconds
LMI statistics:
Input : 80 (last seen 00:00:10 ago)
Output: 100 (last sent 00:00:10 ago)
DTE statistics:
Enquiries sent : 82
Full enquiries sent : 16
Enquiry responses received : 67
Full enquiry responses received : 13
DCE statistics:
Enquiries received : 0
Full enquiries received : 0
Enquiry responses sent : 0
Full enquiry responses sent : 0
Common statistics:
Unknown messages received : 0
Asynchronous updates received : 0
Out-of-sequence packets received : 0
Keepalive responses timedout : 1
Interface transmit statistics: Disabled
Traffic statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
IPv6 transit statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Multilink Frame Relay UNI NNI bundle errors:
Packet drops 0 (0 bytes)
Fragment drops 0 (0 bytes)
MRRU exceeded 0
Exception events 0
Multilink Frame Relay UNI NNI bundle statistics:
Frames fps Bytes bps
Multilink:
Input : 0 0 0 0
Output: 0 0 0 0
Network:
Input : 0 0 0 0
Output: 0 0 0 0
Multilink Frame Relay UNI NNI bundle links information:
Active bundle links 2
Removed bundle links 0
Disabled bundle links 0
Multilink Frame Relay UNI NNI active bundle links statistics:
Frames fps Bytes bps
t1-2/0/0:5
Up time: 00:12:57
Input : 0 0 0 0
Output: 0 0 0 0
Current differential delay 0.0 ms
Recent high differential delay 2.8 ms
Times over red diff delay 0
Times over yellow diff delay 0
LIP:add_lnk lnk_ack lnk_rej hello hel_ack lnk_rem rem_ack
Rcv: 1 2 0 77 78 0 0
Xmt: 14 1 0 78 77 0 0
t1-2/0/0:6
Up time: 00:12:57
Input : 0 0 0 0
Output: 0 0 0 0
Current differential delay 0.0 ms
Recent high differential delay 2.8 ms
Times over red diff delay 0
Times over yellow diff delay 0
LIP:add_lnk lnk_ack lnk_rej hello hel_ack lnk_rem rem_ack
Rcv: 1 2 0 77 78 0 0
Xmt: 14 1 0 78 77 0 0
Logical interface lsq-2/0/0:0.0 (Index 348) (SNMP ifIndex 44399) (Generation 161)
Flags: Up Point-To-Point SNMP-Traps Encapsulation: Multilink-FR-UNI-NNI
Last flapped: 2014-04-24 04:13:05 PDT (00:12:57 ago)
Multilink class 0 status:
Received sequence number 0x0
Transmit sequence number 0xffffffff
Packet drops 0 (0 bytes)
Fragment drops 0 (0 bytes)
MRRU exceeded 0
Fragment timeout 0
Missing sequence number 0
Out-of-order sequence number 0
Out-of-range sequence number 0
Packet data buffer overflow 0
Fragment data buffer overflow 0
Multilink class drop timeout 0 (ms)
Statistics Frames fps Bytes bps
Bundle:
Multilink:
Input : 0 0 0 0
Output: 0 0 0 0
Network:
Input : 0 0 0 0
Output: 0 0 0 0
Link:
t1-2/0/0:5
Up time: 00:12:57
Input : 0 0 0 0
Output: 0 0 0 0
t1-2/0/0:6
Up time: 00:12:57
Input : 0 0 0 0
Output: 0 0 0 0
Multilink detail statistics:
Bundle:
Fragments:
Input : 0 0 0 0
Output: 0 0 0 0
Non-fragments:
Input : 0 0 0 0
Output: 0 0 0 0
Protocol inet, MTU: 1500, Generation: 193, Route table: 0
Flags: Sendbcast-pkt-to-re
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.1.1/24, Local: 10.1.1.2, Broadcast: Unspecified, Generation: 149
DLCI 10
Flags: Active, DCE-Configured
Total down time: 00:03:18 sec, Last down: 00:15:38 ago
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Logical interface lsq-2/0/0:0.1 (Index 349) (SNMP ifIndex 44400) (Generation 162)
Flags: Up Point-To-Point SNMP-Traps Encapsulation: Multilink-FR-UNI-NNI
Last flapped: 2014-04-24 04:13:05 PDT (00:12:57 ago)
Multilink class 0 status:
Received sequence number 0x0
Transmit sequence number 0xffffffff
Packet drops 0 (0 bytes)
Fragment drops 0 (0 bytes)
MRRU exceeded 0
Fragment timeout 0
Missing sequence number 0
Out-of-order sequence number 0
Out-of-range sequence number 0
Packet data buffer overflow 0
Fragment data buffer overflow 0
Multilink class drop timeout 0 (ms)
Statistics Frames fps Bytes bps
Bundle:
Multilink:
Input : 0 0 0 0
Output: 0 0 0 0
Network:
Input : 0 0 0 0
Output: 0 0 0 0
Link:
t1-2/0/0:5
Up time: 00:12:57
Input : 0 0 0 0
Output: 0 0 0 0
t1-2/0/0:6
Up time: 00:12:57
Input : 0 0 0 0
Output: 0 0 0 0
Multilink detail statistics:
Bundle:
Fragments:
Input : 0 0 0 0
Output: 0 0 0 0
Non-fragments:
Input : 0 0 0 0
Output: 0 0 0 0
Protocol inet, MTU: 1500, Generation: 194, Route table: 0
Flags: Sendbcast-pkt-to-re
Addresses, Flags: Is-Preferred Is-Primary
Destination: 192.0.2/24, Local: 192.0.2.2, Broadcast: Unspecified, Generation: 151
DLCI 20
Flags: Active, DCE-Configured
Total down time: 00:03:18 sec, Last down: 00:15:38 ago
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
DLCI statistics:
Active DLCI :2 Inactive DLCI :0