[Contents] [Prev] [Next] [Index] [Report an Error]

# Configuration Tasks

MLFR configuration consists of three major tasks, each with several steps:

1. Create the member links to be aggregated into a multilink bundle.
   1. Specify the interface on which you want to configure MLFR.
      `
      host1(config)#interface serial 2/0:1
      `
   2. Specify MLFR as the encapsulation method on the interface.
      `
      host1(config-if)#encapsulation mlframe-relay ietf
      `
2. Add member links to a multilink bundle.
   1. Define the MLFR bundle.
      `
      host1(config)#interface mlframe-relay boston
      `
   2. Add each member link.
      `
      host1(config-if)#member-interface serial 2/0:1
      `
   3. (Optional) Add a description to the major interface.
      `
      host1(config-if)#frame-relay description bostonBundleDescription
      `
   4. (Optional) Configure Frame Relay parameters.
      `
      host1(config-if)#frame-relay intf-type dce
      host1(config-if)#frame-relay lmi-type cisco
      `
3. Configure the Frame Relay subinterface.
   1. Define the subinterface for the MLFR bundle.
      `
      host1(config)#interface mlframe-relay boston.1
      `
   2. Assign a DLCI for the subinterface.
      `
      host1(config-subif)#frame-relay interface-dlci 16 ietf
      `
   3. (Optional) Add a description to the subinterface.
      `
      host1(config-subif)#frame-relay description bostonBundleSubOneDescription
      `
   4. Assign an IP address to the subinterface.
      `
      host1(config-subif)#ip address 10.10.100.1 255.255.255.0
      `

## Configuration Example

The following commands configure three T1 lines and aggregate them into a multilink bundle named boston.

`

host1(config)#interface serial 2/0:1
host1(config-if)#encapsulation mlframe-relay ietf
host1(config-if)#exit
host1(config)#interface serial 2/0:2
host1(config-if)#encapsulation mlframe-relay ietf
host1(config-if)#exit
host1(config)#interface serial 2/0:3
host1(config-if)#encapsulation mlframe-relay ietf
host1(config-if)#exit
host1(config)#interface mlframe-relay boston
host1(config-if)#member-interface serial 2/0:1
host1(config-if)#frame-relay description bostonBundleDescription
host1(config-if)#frame-relay intf-type dce
host1(config-if)#frame-relay lmi-type cisco
host1(config-if)#member-interface serial 2/0:2
host1(config-if)#member-interface serial 2/0:3
host1(config-if)#exit
host1(config)#interface mlframe-relay boston.1
host1(config-subif)frame-relay description bostonBundleSubOneDescription
host1(config-subif)#frame-relay interface-dlci 16 ietf
host1(config-subif)#ip address 10.10.100.1 255.255.255.0

`

## Configuring Frame Relay Versus MLFR

All the configuration commands that apply to Frame Relay also apply to MLFR. The following listing describes commands specific to configuring MLFR; for other Frame Relay commands, see Configuring Frame Relay.

encapsulation mlframe-relay ietf

- Use to configure MLFR as the encapsulation method on an individual interface.
- Use this command only within the context of an individual interface. Issuing this command creates an MLFR link, also referred to as an MLFR bundle member.
- Example
  `
  host1(config)#interface serial 2/0:1
  host1(config-if)#encapsulation mlframe-relay ietf
  `
- Use theno version to disable MLFR on an interface.
- See encapsulation mlframe-relay ietf.

interface mlframe-relay

- Use to create a Frame Relay major interface, also known as the MLFR bundle.
- Example
  `
  host1(config-if)#interface mlframe-relay group2
  `
- Use the no version to delete the MLFR bundle.
- See interface mlframe-relay.

member-interface

- Use to add an MLFR interface—also known as an MLFR bundle member—to an MLFR bundle.
- Example
  `
  host1(config-if)#member-interface serial 2/0:1
  `
- Use the no version to remove the specified interface from the MLFR bundle.
- See member-interface.

[Contents] [Prev] [Next] [Index] [Report an Error]