Displaying And Maintaining Multilink Frame Relay; Multilink Frame Relay Configuration Examples; Mfr Direct Connection Configuration Example - 3Com MSR 50 Series Configuration Manual

Displaying and
Maintaining Multilink
Frame Relay
Multilink Frame Relay
Configuration
Examples
MFR Direct Connection
Configuration Example
To do...
Configure MFR bundle link
identifier
Configure hello packet
sending period of MFR
bundle link
Configure the waiting time
before MFR bundle link
resends hello packets
Configure maximum
fragment size for the bundle
link
Configure the maximum
times that MFR bundle link
can resend hello packet
Return to system view
Configure the MFR interface
to return ADD_LINK messages
and transit the corresponding
physical interface to the
protocol ADD_SENT state
when it is in protocol up state
and receives an ADD_LINK
request from the peer
To do...
Display configuration and status
of MFR interface
Display configuration and
statistics information of MFR
bundle and bundle links
Network requirements
Router A and Router B are directly connected through Serial 2/0 and Serial 2/1.
The frame relay protocol is used to bundle the two serial ports to provide broader
bandwidth.

Displaying and Maintaining Multilink Frame Relay

Use the command...
mfr link-name [ name ] Optional
mfr timer hello seconds Optional
mfr timer ack seconds
mfr fragment-size
bytes
mfr retry number
quit
mfr
stateup-respond-addli
nk
Use the command...
display interface mfr
[ interface-number ]
display mfr [ interface interface-type
interface-number | verbose ]
Remarks
The bundle link identifier is the
name of the current interface by
default.
The hello packet sending period of
bundle link is 10 seconds by
default.
Optional
The waiting time before resending
hello message is 4 seconds by
default.
Optional
The maximum fragment size is of
300 bytes. The priority of fragment
size configured in frame relay
interface view is higher than that in
MFR interface view.
Optional
The hello packet can be resent 2
times at the maximum by default.
-
Optional
By default, an MFR interface does
not respond to ADD_LINK requests
received even if it is in protocol up
state. This causes the peer port
cannot be in protocol up state.
Remarks
Available in any
view
Available in any
view
259