MLFR Configuration
Except on the first page, right running head:
Heading1 or Heading1NewPage text (automatic)
389
Alcatel-Lucent
Beta Beta
OmniAccess 5740 Unified Services Gateway CLI Configuration Guide
MLFR CONFIGURATION COMMANDS
To configure an MLFR, first a bundle interface needs to be configured. Then
MLFR encapsulation is set on individual interfaces that become a part of the
bundle by member link configuration.
IP routing protocols as well as policies such as ACL, NAT, IDS, IPsec, etc.,
configured on an individual interface will not be effective as long as the interface is
part of the MLFR bundle. When the interface is no longer part of the bundle, the
policies configured on the individual interface become active.
T
O CONFIGURE MLFR BUNDLE INTERFACE
EXAMPLE
ALU(config)# interface mlfr 100
ALU(config-if mlfr100)#
T
O CONFIGURE LOCAL MANAGEMENT INTERFACE (LMI) TYPE
Note: LMI Autosense is activated by default as the system acts as a DTE. The LMI
autosense will be activated when the physical interface is up and LMI type is not
configured on that interface.
E
XAMPLE
The following example sets the LMI to ANSI standard:
ALU(config-if mlfr100)# frame-relay lmi-type ansi
The following example sets the LMI-type to its default, i.e., ‘auto-sense’:
ALU(config-if mlfr100)# no frame-relay lmi-type
Command (in CM) Description
interface mlfr <1-256> This command configures a MLFR
bundle interface that is identified by a
user specified number.
This number can vary from 1 - 256.
Command (in ICM) Description
frame-relay lmi-type
{ansi|q933a}
This command is used to set the LMI
type to either ANSI or Q933A.
no frame-relay lmi-type
{ansi|q933a}
The “no” command sets the LMI type to
its default value.
The default LMI type is auto-sense.
To Next Page
Loading...
Need help?
General
