3Com Router User Manual

							Configure Frame Relay QoS267
Configure Frame Relay 
DE Rule List
1Configure a DE rule list
Perform the following configurations in system view.
Ta b l e 307   Configure a DE rule list
By default, no DE rule list is defined.
A router can support up to 10 DE rule lists, and each of them can contain up to 
100 DE rules.
The commands fr del inbound-interface and fr del protocol can be used 
to add multiple rules to a DE rule list. The commands 
undo fr del 
inbound-interface
 and undo fr del protocol can delete one DE rule each 
time. To delete a DE rule list, the user should delete all the DE rules in it.
2Apply the DE rule list on a Frame Relay PVC
Perform the following configurations in synchronous serial interface view.
Ta b l e 308   Apply the DE rule list on a Frame Relay PVC
By default, no DE rule lists are applied on Frame Relay PVCs.
Configure Frame Relay 
Queueing Management
1Configure the Frame Relay PVC queueing
After the Frame Relay traffic shaping is enabled on a Frame Relay interface, each 
PVC under this interface will own its independent PVC queue. If the function is not 
enabled on the Frame Relay interface, the PVCs will have no PVC queues.
Perform the following configurations in frame relay class view.
Ta b l e 309   Configure the Frame Relay PVC queueing
OperationCommand
Configure an interface-based DE rule listfr del list-number 
inbound-interface type number
Delete the interface-based DE ruleundo fr del list-number 
inbound-interface type number
Configure a protocol-based DE rule listfr del list-number protocol 
protocol [ characteristic ]
Delete the protocol-based DE rule undo fr del list-number protocol 
protocol [ characteristic ]
OperationCommand
Apply the DE rule list on a Frame Relay PVCfr de del list-number dlci-number
Delete a DE rule list from the Frame Relay 
PVCundo fr de del list-number 
dlci-number
OperationCommand
Set the FIFO queue length of a Frame Relay PVCfifo queue-length queue-size
Restore the FIFO queue length of a Frame Relay 
PVC to the default valueundo fifo queue-length
Set the queue type of a Frame Relay PVC to PQpq pql list-number
Restore the queue type of a Frame Relay PVC to 
FIFOundo pq pql 
						

							268CHAPTER 17: CONFIGURING FRAME RELAY
By default, the queue type of a Frame Relay PVC is FIFO.
When the congestion management is enabled on Frame Relay PVCs, the queue 
type on the interface can only be FIFO. 
For the configuration of PQ, CQ and WFQ, refer to the part of  QoS.
2Configure Frame Relay Interface Queueing
The user can configure four queueing types on a Frame Relay interface:.FIFO, PQ, 
CQ and WFQ. All of them are the queues owned by a general QoS. For their 
configurations, refer to the part of 
 QoS.
Frame Relay interface also supports PVC interface priority queueing (PIPQ). This 
queueing type can only be applied on a Frame Relay interface. After Frame Relay 
traffic shaping or Frame Relay congestion management is enabled on a Frame 
Relay interface, the queueing type on the interface can only be either FIFO or PIPQ.
A PIPQ queue classifies the packets into four categories according to different 
Frame Relay PVCs.
A PIPQ queue has four sub-queues. They are respectively high-priority queue (top), 
medium-priority queue (
middle), normal-priority queue (normal) and low-priority 
queue (
bottom). The priorities are listed in descending order. The packets will be 
transmitted according to the priority sequence. Specifically, all the packets in the 
top queue will be first transmitted, then the packets in the middle queue 
followed by the packets in the normal queue, and finally those in the 
bottom 
queue. Each Frame Relay PVC on the interface has its own PIPQ priority. Therefore, 
the packets from this PVC can only enter the corresponding PIPQ queue.
Perform the following configurations respectively in interface view and frame relay 
class view.
Ta b l e 310   Configure PIPQ
By default, the queueing type of a Frame Relay interface is FIFO.
Set the queue type of a Frame Relay PVC to CQcq cql list-number
Restore the queue type of a Frame Relay PVC to 
FIFOundo cq cql
Set the queue type of a Frame Relay PVC to 
WFQwfq [ 
congestive-discard-threshold [ 
dynamic-queues ] ]
Restore the queue type of a Frame Relay PVC to 
FIFOundo wfq
OperationCommand
Set the queueing type of Frame Relay interface to 
PIPQ and set the length of each PIPQ queue at 
the same time (in interface 
view)
fr pvc-pq [ top-limit 
middle-limit normal-limit 
bottom-limit ]
Restore the queueing type of Frame Relay 
interface to FIFO (in interface 
view)
undo fr pvc-pq
Set the priority of PIPQ on the Frame Relay PVC 
(in frame relay class view)pvc-pq { top | middle | normal 
| bottom }
Restore the priority of PIPQ on the Frame Relay 
PVC to normal (in 
frame relay class view)
undo pvc-pq 
						

							Configure Frame Relay over Other Protocols269
Configure Frame Relay 
over Other Protocols
Frame Relay over IPIP networks are used to carry the Frame Relay data to interconnect the Frame 
Relay networks. In the technique of Frame Relay over IP, a GRE tunnel is 
established between the Frame Relay networks at both ends of IP, and the Frame 
Relay data are carried over IP. The application of Frame Relay over IP is illustrated in 
the following figure: 
Figure 88   Typical application of Frame Relay over IP
Configure Frame Relay over IP
1Configure tunnel interface
Create a tunnel interface in all views or enter the tunnel interface view to perform 
the following configurations.
Ta b l e 311   Configure a tunnel interface
In addition, the user can make the configurations, such as packet mode, ID 
keyword, for the tunnel interface. The tunnel interface configuration details will 
not be covered here. Please read the related chapters in Operation manual - VPN 
for reference.
2Configure Frame Relay Switching
Enable Frame Relay switching in system view and configure Frame Relay switched 
routes in serial interface view.
Ta b l e 312   Configure Frame Relay switching
If the specified tunnel interface does not exist when implementing configuration, 
the system will automatically create a tunnel interface. However, the Frame Relay 
switched route can take effect only after the source address, destination address, 
and IP address have been configured for the tunnel interface.
IP Network
Frame Relay
NetworkFrame Relay
Network
OperationCommand
Create a tunnel interfaceinterface tunnel 
tunnel-number
Specify a source address for the tunnel interfacesource ip-address
Specify a destination address for the tunnel interfacedestination ip-address
OperationCommand
Enable Frame Relay switchingfr switching
Configure a Frame Relay switched routefr dlci-switch in-dlci 
interface tunnel number 
out-dlci 
						

							270CHAPTER 17: CONFIGURING FRAME RELAY
After configuring the Frame Relay route through the fr dlci-switch interface 
tunnel
 command, two routes will be added to the Frame Relay routing table on 
the router. One route takes the tunnel interface as the incoming interface and the 
serial interface as the outgoing interface. On the contrary, the other route takes 
the serial interface as the incoming interface and the tunnel interface as the 
outgoing interface.
After the Frame Relay route is configured through the fr dlci-switch 
interface tunnel 
command, a PVC will be created on the tunnel interface and 
assigned with a DLCI number out-dlci. When implementing configuration, make 
sure that the same DLCI number (that is, out-dlci) should be used on the tunnel 
interfaces at two ends of the GRE tunnel.
Frame Relay over ISDN Nowadays, Frame Relay technique has gained wide applications, in which, most 
devices are accessed to the Frame Relay networks via leased lines. To shorten the 
time for users to access Frame Relay networks and lower the cost of leased lines, 
ISDNs and the related devices can be used to access Frame Relay networks, the 
so-called Frame Relay over ISDN.
With the Frame Relay over ISDN technique, the cost of a leased line can be shared 
by the routers, so the overall cost is lowered. The users can access the Frame Relay 
networks much quicker and with lower cost. At the same time, ISDN can also be 
taken as a standby for Frame Relay accessing. Therefore, the Frame Relay over 
ISDN is mainly used in the following two aspects:
■The simplest application is to take Frame Relay over ISDN as the main 
communications method. That is, all the routers support Frame Relay over 
ISDN, and the individual routers can directly access the Frame Relay networks 
(without TA adapters) to communicate.
■Combined with BDR, Frame Relay over ISDN can be taken as the standby 
communication method for Frame Relay. In such applications, routers support 
Frame Relay over ISDN. Being the standby for a Frame Relay network, ISDN can 
be used to re-establish the connections for accessing the Frame Relay network, 
whenever a Frame Relay accessing line/device fails to work or the Frame Relay 
network is blocked.
Frame Relay over ISDN Operation Process and Fundamentals
The following figure shows a typical networking for Frame Relay accessing, in 
which all the routers support Frame Relay over ISDN:
Figure 89   Networking of a typical Frame Relay over ISDN application
RouterA, RouterB and RouterC support Frame Relay over ISDN. Being DTE devices, 
they and RouterD transmit Frame Relay packets over ISDN B channels. RouterD, 
which works as a DCE device, supports both Frame Relay over ISDN and Frame 
Relay switching. A simplified working procedure is shown below:
■RouterA (DTE device) originates a call on the BRI interface to the PRI interface 
on RouterD (DCE device).
Frame Relay
Router B
ISDN
Router A
Frame Relay 
						

							Configure Frame Relay over Other Protocols271
■The DCE device identifies the calling number of the incoming call and 
authenticates the DTE device according to it to determine whether to accept or 
deny the call.
■If the DTE device passes the authentication, it can establish a B channel to the 
DCE device for carrying out the Frame Relay communications.
Normally, if a DCE device is connected to multiple DTE devices, calls can only be 
originated from the DTE side. However, it is not the case for back-to-back 
connections.
Binding of multiple B channels is not supported. After a call is successfully made, a 
DTE device and a DCE device can only be connected via a B channel.
Since a B channel can only be connected to a remote end and cannot have more 
than one IP addresses, it cannot be configured with multiple DLCIs, nor configured 
with multiple sub-interfaces.
Physical Connection Between Frame Relay over ISDN Devices
■Back-to-back connection between DTE and DCE devices
The DTE and DCE devices are connected to ISDN via ISDN (BRI or PRI) 
interfaces, and both ends can make calls, as shown in the following figure:
Figure 90   Back-to-back connection between DTE and DCE devices
If legacy BDR is adopted on the ISDN interface used with Frame Relay, the 
calling party can directly use the configured dial string to make an ISDN call to 
the remote end, after it finds an available B channel. If dialer profiles are 
adopted, the calling party will re-configure the selected available B channel 
with the link layer protocol on the dialer interface, and then use the configured 
dial string to place an ISDN call to the remote end. 
After a physical B channel is set up, Frame Relay LMI (Local Management 
Interface) and inverse ARP process will start. If an agreement is reached 
through the negotiation, Frame Relay will be used to carry the network layer 
data on the B channel.
If dialer profiles are adopted, the called party searches for the dialer interface 
according to the dialing number in the ISDN packet. If the dialer interface is found, 
the called party will re-configure the selected B channel with the link layer 
protocol on the dialer interface. If the dialer interface is not found but the 
dialer 
call-in 
command has been configured, it will disconnect the call. If the dialer 
call-in
 command is not configured, PPP will be adopted by default. Therefore, 
each dialer interface of the called party should be configured with a unique dialing 
number, and can only receive the calls from that number. This restriction, however, 
is not placed on the calling parties.
■Frame Relay switching connection between DTE devices
ISDN
Switch
Router B
Router ADTEDCE
Bri0
Bri1Pri 
						

							272CHAPTER 17: CONFIGURING FRAME RELAY
A DCE device provides Frame Relay switching. Its one end is connected to a 
DTE device via ISDN, and the other end is directly connected to another DTE 
device, as shown in the following figure:
Figure 91   Frame Relay switching connection between DTE devices
The DCE device cannot originate a call, since the PVC segment that the DCE 
device establishes via ISDN can only be activated through dialing. The call can 
only be originated by the DTE device, which is connected to ISDN. After the call 
is successfully made, the corresponding PVC segment is established for 
transmitting the network layer data.
If legacy BDR is adopted on the ISDN interface worked with Frame Relay on the 
DCE device, the calling party will use the configured dial string to make an 
ISDN call to the DCE device. If dialer profiles are adopted, the calling party (the 
DTE device) will re-configure the selected available B channel with the link layer 
protocol on the dialer interface, and then use the configured dial string to 
make an ISDN call to the DCE device.
After a physical B channel is set up, Frame Relay LMI and inverse ARP process 
will start. If an agreement is reached through the negotiation, the 
corresponding PVC will be established. Then, the DCE device will look for 
another PVC segment according to the Frame Relay switching configuration 
and activate the PVC segment. When both PVC segments are in active status, it 
means that the whole PVC is set up. In this case, Frame Relay can be adopted 
on the B channel to carry the network layer data.
Distinguished from legacy BDR, dialer profiles require a called party to search for 
the dialer interface according to the dialing number in the ISDN packet, and hence 
obtain the link layer protocol type for the B channel. Then, the called party can 
dynamically configure the dialer interface or physical ISDN interface and initialize 
it.
Configure Frame Relay over ISDN
Frame Relay over ISDN provides a means for accessing devices from ISDN to a 
Frame Relay network. Its implementation fully depends on the techniques of 
Frame Relay and BDR. This section only covers the Frame Relay over ISDN-related 
commands. For configuration details and commands, refer to the Frame Relay and 
BDR Configuration in this manual.
1Related Frame Relay Configuration
Only some simple Frame Relay configurations are covered in this section. For other 
configurations, refer to the Link Layer Protocol.
Perform the following configuration in synchronous serial interface view.
Ta b l e 313   Configure the Frame Relay-related commands
ISDN
Switch
Router ADTEDCE
Bri0
Bri1PriDTE
Router C S1S1
Frame Relay
Switching
Router B
OperationCommand 
						

							Configure Frame Relay over Other Protocols273
2Configuration Related to Frame Relay Switching
Only some simple Frame Relay switching configurations are covered in this section. 
For other configurations, refer to the Link Layer Protocol.
Configure the commands fr switch and fr switching in system view, and 
perform other configurations in synchronous serial interface view.
Ta b l e 314   Configure the commands related to Frame Relay switching
In addition to Frame Relay switching connections between serial interfaces, the fr 
switch command also supports the Frame Relay switching connections between 
ISDN BRI, ISDN PRI and dialer interfaces.
3BDR-related Configuration
■Adopt legacy BDR
If legacy BDR is adopted to implement Frame Relay over ISDN, the user can 
refer to Dial-up of this manual for all the configurations except for the link layer 
protocol on the dialer or physical ISDN interface. The link layer protocol should 
be configured through the 
link-protocol fr command.
Perform the following configuration in physical ISDN or dialer interface view.
Ta b l e 315   Configure the link layer protocol of the interface
The two ends of a BDR call should work with the same link layer protocol.
For a physical interface (such as an ISDN BRI or PRI interface), both the D channel 
and B channel are configured with Frame Relay.
Configure the synchronous serial 
interface with Frame Relaylink-protocol fr [ ietf | nonstandard 
]
Set the Frame Relay interface typefr interface-type { dte | dce | nni }
Add a static address mapfr map { ip | ipx } protocol-address 
dlci dlci [ broadcast ] [ nonstandard 
| ietf ] [ logic-channel 
channel_number ] [ nocompress | 
compression vj ] [ compression frf9 ]
Assign a DLCI number for the main 
interface or a sub-interfacefr dlci dlci-number
OperationCommand
Enable Frame Relay to implement PVC 
switchingfr switching
Configure a terminal type for a Frame 
Relay interfacefr interface-type { dte | dce | nni }
Assign DLCI number for the main interface 
or a sub-interfacefr dlci dlci-number
Configure a Frame Relay switched virtual 
circuit (SVC)fr switch name interface type number 
dlci dlci interface type number dlci 
dlci
OperationCommand
Configure the link layer protocol of the 
interface to Frame Relaylink-protocol fr [ ietf | 
nonstandard ] 
						

							274CHAPTER 17: CONFIGURING FRAME RELAY
In the legacy BDR implementation of Frame Relay over ISDN, a dialer interface and 
all the ISDN physical interfaces (including BRI and PRI interfaces) attached to it will 
be Configured with Frame Relay.
■Adopt dialer profiles
In the dialer profiles implementation of Frame Relay over ISDN, the dialer 
number 
command must be configured, besides using the link-protocol fr 
command to change the link layer protocol on the interface. The configuration 
is necessary because the negotiation of user name is disabled after the dialer 
interface is configured with Frame Relay, so the called party will identify 
different dialer interfaces according to the dial strings of the calling parties. In 
this case, however, there is no need to configure the 
dialer user command. 
In addition, the 
dialer call-in command must be configured for the called 
party to pre-process a dial-in number, thereby to determine whether the user 
dialing the number should be accessed. For other configurations, refer to the 
Dial-up.
Perform the following configuration in physical ISDN or dialer interface view.
Ta b l e 316   Configure parameters related to dialer profiles
The two ends of a BDR call should work with the same link layer protocol.
For a dialer interface adopting dialer profiles to implement Frame Relay over ISDN, 
it should be configured with Frame Relay. In addition, Frame Relay and PPP are 
probably carried on a B channel for supporting the dynamic configuration on the 
channel. Therefore, the ISDN physical interface should be configured with PPP. 
After the dynamic B channel is disconnected, the link layer protocol of the ISDN 
interface will be automatically restored to PPP (by default, physical interface will 
inherit the configurations of dialer interface).
Multiple dialer number is allowed to configure for the calling party, which is the 
so-called dialer string rotary backup. For the called party, after a dialer interface 
link layer protocol is configured to Frame Relay, the dialer numbers configured 
on other dialer interfaces cannot be the same dialer number configured on it. 
Otherwise, calls will fail.
Display and debug 
Frame RelayPlease use the display and debugging commands in all views.
Ta b l e 317   Display and Debug Frame Relay
OperationCommand
Configure a dialer interface with Frame Relaylink-protocol fr [ ietf | 
nonstandard ]
Enable dialer profilesdialer bundle number
Configure the dial string for calling a remote 
enddialer number dial-string [ 
:isdn_subaddress ]
Pre-process ISDN dial-in numbersdialer call-in remote-number [ 
callback ]
OperationCommand
Display receiving/sending statistics information 
of Frame Relay LMI type packetsdisplay fr lmi-info [ interface 
type number ]
Display protocol address and Frame Relay 
address mapping tabledisplay fr map-info 
						

							Display and debug Frame Relay275
Display Frame Relay data receiving/sending 
statistics information.display fr statistics [ 
interface type number ]
Display the Frame Relay PVC statisticsdisplay fr pvc-info [ serial 
number ] [ dlci dlci-number ]
Display Frame Relay PVC route tabledisplay fr dlci-switch
Display Frame Relay switch PVC route tabledisplay fr switch-table
Display Frame Relay protocol status of each 
interfacedisplay fr interface
Display statistics information of Frame Relay 
inverse address resolution protocol packetsdisplay fr inarp-info
Display the statistics of MFR bundle and bundle 
linkdisplay mfr [ interface mfr 
number | interface serial 
number ] [ detailed ]
Display the statistics of Frame Relay compressiondisplay fr compression
Display statistics information of MFR interfacedisplay interfaces mfr number
Clear all the automatically established Frame 
Relay address mappingsreset fr inarp-info
Enable all the debugging of Frame Relaydebugging fr all [ interface 
type number ] 
Enable the debugging of Frame Relay annexgdebugging fr annexg [ interface 
type number ] [ dlci ]
Enable the debugging of Frame Relay arpdebugging fr arp [ interface 
type number ]
Enable the debugging of Frame Relay 
compressiondebugging fr compress [ 
interface type number ]
Enable the debugging of Frame Relay 
congestiondebugging fr congestion [ 
interface type number ]
Enable the debugging of Frame Relay DE 
messagedebugging fr de [ interface 
type number ]
Enable the debugging of Frame Relay DLCI 
queuedebugging fr dlciqueue 
interface type number dlci 
dlci-number
Enable the debugging of Frame Relay eventdebugging fr event [ interface 
type number ]
Enable the debugging of Frame Relay fragmentdebugging fr fragment interface 
type number dlci
Enable the debugging of Frame Relay lmidebugging fr lmi [ interface 
type number ]
Display the debug messages for the MFR 
bundles and bundle linksdebugging fr mfr [ control [ 
interface mfr number | 
interface serial number ] ]
Enable the debugging of Frame Relay packetdebugging fr packet [ interface 
type number [ dlci ] ] [ hex | 
detail | all ]
Enable the debugging of Frame Relay PIPQdebugging fr pipq [ interface 
type number ]
Enable the debugging of Frame Relay statusdebugging fr status [ interface 
type number [ dlci ] ]
Enable the debugging of Frame Relay traffic ratedebugging fr transmit-rate [ 
interface type number ] 
						

							276CHAPTER 17: CONFIGURING FRAME RELAY
Typical Frame Relay 
Configuration 
Example
Interconnect LANs via 
Frame Relay NetworkI. Networking Requirement
Interconnect LANs via the public Frame Relay network. The router work as user 
equipment in the Frame Relay DTE mode. The routers use static address mapping.
II. Networking Diagram
Figure 92   Interconnect LANs via Frame Relay network
III. Configuration Procedure
1Configure Router A:
aConfigure interface IP address
[Router]interface serial 1
[Router-Serial1]ip address 202.38.163.251 255.255.255.0
bConfigure the link layer protocol of the interface to Frame Relay
[Router-Serial1]link-protocol fr
[Router-Serial1]fr interface-type dte
cConfigure static address mapping
[Router-Serial1]fr map ip 202.38.163.252 dlci 50
[Router-Serial1]fr map ip 202.38.163.253 dlci 60
2Configure Router B:
aConfigure interface IP address
[Router]interface serial 1
[Router-Serial1] ip address 202.38.163.252 255.255.255.0
bConfigure the link layer protocol of the interface to Frame Relay
[Router-Serial1]link-protocol fr
[Router-Serial1]fr interface-type dte
cConfigure static address mapping
[Router-Serial1]fr map ip 202.38.163.251 dlci 70
3Configure Router C:
aConfigure interface IP address
[Router]interface serial 1
FR
Router C
Router B
DLCI=50
DLCI=60
DLCI=80DLCI=70 Quidway Router A
IP:202.38.163.253 IP:202.38.163.251IP:202.38.163.252