Configuration Tasks
MLFR configuration consists of three major tasks, each with several steps:
- Create the member links to be aggregated into a multilink
bundle.
- Specify the interface on which you want to configure MLFR.host1(config)#interface serial 2/0:1
- Specify MLFR as the encapsulation method on the interface.host1(config-if)#encapsulation mlframe-relay ietf
- Specify the interface on which you want to configure MLFR.
- Add member links to a multilink bundle.
- Define the MLFR bundle.host1(config)#interface mlframe-relay boston
- Add each member link.host1(config-if)#member-interface serial 2/0:1
- (Optional) Add a description to the major interface.host1(config-if)#frame-relay description bostonBundleDescription
- (Optional) Configure Frame Relay parameters.host1(config-if)#frame-relay intf-type dce host1(config-if)#frame-relay lmi-type cisco
- Define the MLFR bundle.
- Configure the Frame Relay subinterface.
- Define the subinterface for the MLFR bundle.host1(config)#interface mlframe-relay boston.1
- Assign a DLCI for the subinterface.host1(config-subif)#frame-relay interface-dlci 16 ietf
- (Optional) Add a description to the subinterface.host1(config-subif)#frame-relay description bostonBundleSubOneDescription
- Assign an IP address to the subinterface. host1(config-subif)#ip address 10.10.100.1 255.255.255.0
- Assign an IPv6 address to the subinterface. host1(config-subif)#ipv6 address 1::1/64
- Define the subinterface for the MLFR bundle.
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.
- Examplehost1(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.
- Examplehost1(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.
- Examplehost1(config-if)#member-interface serial 2/0:1
- Use the no version to remove the specified interface from the MLFR bundle.
- See member-interface.
Hide Navigation Pane
Show Navigation Pane
SHA1