Table Of Contents
frame-relay becn-response-enable
frame-relay end-to-end keepalive error-threshold
frame-relay end-to-end keepalive event-window
frame-relay end-to-end keepalive mode
frame-relay end-to-end keepalive success-events
frame-relay end-to-end keepalive timer
frame-relay ip tcp header-compression
frame-relay map ip tcp header-compression
frame-relay priority-dlci-group
show frame-relay end-to-end keepalive
show frame-relay ip tcp header-compression
show frame-relay qos-autosense
Frame Relay Commands
Use the commands described in this chapter to configure access to Frame Relay networks.
The following are either new commands or newly introduced from the Cisco IOS 12.0 Voice, Video, and Home Applications Command Reference publication:
•
frame-relay end-to-end keepalive error-threshold
•
•
•
•
•
For Frame Relay configuration information and examples, refer to the "Configuring Frame Relay" chapter in the Cisco IOS Wide-Area Networking Configuration Guide.
For configuration of FRF.5 Frame Relay-ATM Network Interworking and FRF.8 Frame Relay-ATM Service Interworking on the Cisco MC3810, refer to the "Configuring Frame Relay-ATM Interworking" chapter of the Cisco IOS Wide-Area Networking Configuration Guide.
class (map-list)
To associate a map class with a protocol-and-address combination, use the class map-list configuration command.
class protocol protocol-address class map-class [broadcast] [trigger] [ietf]
Syntax Description
Defaults
No protocol, protocol address, and map class are defined. If the ietf keyword is not specified, the default is Cisco encapsulation. If the broadcast keyword is not specified, no broadcasts are sent.
Command Modes
Map-list configuration
Command History
Usage Guidelines
This command is used for Frame Relay switched virtual circuits (SVCs); the parameters within the map class are used to negotiate for network resources. The class is associated with a static map that is configured under a map list.
Examples
In the following example, if IP triggers the call, the SVC is set up with the QOS parameters defined within the class hawaii. However, if AppleTalk triggers the call, the SVC is set up with the QOS parameters defined in the class rainbow. An SVC triggered by either protocol results in two SVC maps, one for IP and one for AppleTalk. Two maps are set up because these protocol-and-address combinations are heading for the same destination, as defined by the dest-addr keyword and the values following it in the map-list command.
map-list bermuda source-addr E164 14085551212 dest-addr E164 15085551212ip 131.108.177.100 class hawaiiappletalk 1000.2 class rainbowIn the following example, the trigger keyword allows AppleTalk broadcast packets to trigger an SVC:
ip 172.21.177.1 class jamaica broadcast ietfappletalk 1000.2 class jamaica broadcast trigger ietfRelated Commands
class (virtual circuit)
To associate a map class with a specified data-link connection identifier (DLCI), use the class virtual circuit configuration command. To remove the association between the DLCI and the map class, use the no form of this command.
class name
no class name
Syntax Description
Defaults
No map class is defined.
Command Modes
Virtual circuit configuration
Command History
Usage Guidelines
This command applies to DLCIs. The class parameter values are specified with the map-class frame-relay command.
Examples
The following example shows how to define map class slow_vcs and apply it to DLCI 100:
interface serial 0.1 point-to-pointframe-relay interface-dlci 100class slow_vcsmap-class frame-relay slow_vcsframe-relay cir out 9600The following example shows how to apply a map class to a DLCI for which a frame-relay map statement exists. The frame-relay interface-dlci command must also be used.
interface serial 0.2 point-to-multipointframe-relay map ip 131.26.13.2 100frame-relay interface-dlci 100class slow_vcsinterface serial 0frame-relay interface-dlci 100class fast_vcmap-class frame-relay fast_vcframe-relay traffic-rate 56000 128000frame-relay idle-timer 30Related Commands
clear frame-relay-inarp
To clear dynamically created Frame Relay maps, which are created by the use of Inverse Address Resolution Protocol (ARP), use the clear frame-relay-inarp EXEC command.
clear frame-relay-inarp
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following example clears dynamically created Frame Relay maps:
clear frame-relay-inarpRelated Commands
encapsulation frame-relay
To enable Frame Relay encapsulation, use the encapsulation frame-relay interface configuration command. To disable Frame Relay encapsulation, use the no form of this command.
encapsulation frame-relay [cisco | ietf]
no encapsulation frame-relay [ietf]
Syntax Description
Defaults
Enabled
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command with no keywords to restore the default Cisco encapsulation, which is a 4-byte header with 2 bytes for the DLCI and 2 bytes to identify the packet type.
You should shut down the interface prior to changing encapsulation types. Although this is not required, shutting down the interface ensures the interface is reset for the new encapsulation.
Examples
The following example configures Cisco Frame Relay encapsulation on interface serial 1:
interface serial 1encapsulation frame-relayUse the ietf keyword if your router or access server is connected to another vendor's equipment across a Frame Relay network to conform with RFC 1490:
interface serial 1encapsulation frame-relay ietffr-atm connect dlci
To connect a Frame Relay data-link connection identifier (DLCI) to an ATM virtual circuit descriptor for FRF.5 Frame Relay-ATM Interworking (currently only available for the Cisco MC 3810), use the fr-atm connect dlci interface configuration command. The encapsulation type of the current interface must be Frame Relay or Frame Relay 1490 Internet Engineering Task Force (IETF). To remove the DLCI-to-VCD connection, use the no form of this command.
fr-atm connect dlci dlci atm-interface pvc [name | [vpi/]vci] [clp-bit {map-de | 0 | 1}] [de-bit {no-map-clp | map-clp}]
no fr-atm connect dlci dlci atm-interface pvc [name | [vpi/]vci] [clp-bit {map-de | 0 | 1}] [de-bit {no-map-clp | map-clp}]
Syntax Description
Defaults
No Frame Relay-ATM connection is configured.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command only applies to Frame Relay-ATM Network Interworking (FRF.5) on the Cisco MC3810.
Note
Examples
The following example configures a Frame Relay-ATM Interworking connection on FR-ATM interface 20, in which Frame Relay DLCI 100 is connected to ATM VPI/VCI 100/200 for ATM interface 0:
interface fr-atm 20fr-atm connect dlci 100 atm0 100/200 clp-bit map-de de-bit map-clpThe following example configures a Frame Relay-ATM Interworking connection on FR-ATM interface 10, in which Frame Relay DLCI 150 is connected to ATM VPI/VCI 0/150 for ATM interface 0:
interface fr-atm 10fr-atm connect dlci 150 atm0 0/150 clp-bit map-de de-bit map-clpRelated Commands
Creates a Frame Relay-ATM Interworking interface on the Cisco MC3810 multiservice concentrator.
frame-relay adaptive-shaping
To select the type of backward notification you want to use, use the frame-relay adaptive-shaping map-class configuration command. To disable backward notification, use the no form of the command.
frame-relay adaptive-shaping {becn | foresight}
no frame-relay adaptive-shaping
Syntax Description
becn
Enables rate adjustment in response to BECN.
foresight
Enables rate adjustment in response to ForeSight and BECN messages.
Defaults
Disabled
Command Modes
Map-class configuration
Command History
Usage Guidelines
This command replaces the frame-relay becn-response-enable command, which will be removed in a future Cisco IOS release. If you use the frame-relay becn-response-enable command in scripts, you should replace it with the frame-relay adaptive-shaping command.
The frame-relay adaptive-shaping command configures a router to respond to either BECN or ForeSight backward congestion notification messages. When BECN is enabled, Frame Relay traffic shaping will adapt to BECN messages. When ForeSight is enabled, Frame Relay traffic shaping will adapt to ForeSight and BECN messages.
Include this command in a map-class definition and apply the map class to either the main interface or to a subinterface.
Examples
This example shows the map-class definition for a router configured with traffic shaping and Router ForeSight enabled:
interface Serial0no ip addressencapsulation frame-relayframe-relay traffic-shapingframe-relay class control-Amap-class frame-relay control-Aframe-relay adaptive-shaping foresightframe-relay cir 56000frame-relay bc 64000Related Commands
Enables both traffic shaping and per-VC queueing for all PVCs and SVCs on a Frame Relay interface.
Specifies a map class to define QoS values for an SVC.
frame-relay bc
To specify the incoming or outgoing committed burst size (Bc) for a Frame Relay virtual circuit, use the frame-relay bc map-class configuration command. To reset the committed burst size to the default, use the no form of this command.
frame-relay bc {in | out} bits
no frame-relay bc {in | out} bits
Syntax Description
in | out
Incoming or outgoing; if neither is specified, both in and out values are set.
bits
Committed burst size, in bits.
Defaults
7000 bits
Command Modes
Map-class configuration
Command History
Usage Guidelines
The Frame Relay committed burst size is specified within a map class to request a certain burst rate for the circuit. Although it is specified in bits, an implicit time factor is the sampling interval Tc on the switch, which is defined as the burst size divided by the committed information rate (CIR).
Examples
In the following example, the serial interface already has a basic configuration, and a map group called bermuda has already been defined. The example shows a map-list configuration that defines the source and destination addresses for bermuda, provides IP and IPX addresses, and ties the map list definition to the map class called jamaica. Then traffic shaping parameters are defined for the map class.
map-list bermuda local-addr X121 31383040703500 dest-addr X121 31383040709000ip 172.21.177.26 class jamaica ietfipx 123.0000.0c07.d530 class jamaica ietfmap-class frame-relay jamaicaframe-relay cir in 2000000frame-relay mincir in 1000000frame-relay cir out 15000frame-relay mincir out 10000frame-relay bc in 15000frame-relay bc out 9600frame-relay be in 10000frame-relay be out 10000frame-relay idle-timer 30Related Commands
Sets the incoming or outgoing excess burst size (Be) for a Frame Relay VC.
Specifies the incoming or outgoing CIR for a Frame Relay VC.
frame-relay be
To set the incoming or outgoing excess burst size (Be) for a Frame Relay virtual circuit, use the frame-relay be map-class configuration command. To reset the excess burst size to the default, use the no form of this command.
frame-relay be {in | out} bits
no frame-relay be {in | out} bits
Syntax Description
Defaults
7000 bits
Command Modes
Map-class configuration
Command History
Usage Guidelines
The Frame Relay excess burst size is specified within a map class to request a certain burst rate for the circuit. Although it is specified in bits, an implicit time factor is the sampling interval Tc on the switch, which is defined as the burst size divided by the committed information rate (CIR).
Examples
In the following example, the serial interface already has a basic configuration, and a map group called bermuda has already been defined. The example shows a map-list configuration that defines the source and destination addresses for bermuda, provides IP and IPX addresses, and ties the map list definition to the map class called jamaica. Then traffic shaping parameters are defined for the map class.
map-list bermuda local-addr X121 31383040703500 dest-addr X121 31383040709000ip 172.21.177.26 class jamaica ietfipx 123.0000.0c07.d530 class jamaica ietfmap-class frame-relay jamaicaframe-relay cir in 2000000frame-relay mincir in 1000000frame-relay cir out 15000frame-relay mincir out 10000frame-relay bc in 15000frame-relay bc out 9600frame-relay be in 10000frame-relay be out 10000frame-relay idle-timer 30Related Commands
Specifies the incoming or outgoing committed burst size (Bc) for a Frame Relay VC.
Specifies the incoming or outgoing CIR for a Frame Relay VC.
frame-relay becn-response-enable
This command has been replaced by the frame-relay adaptive-shaping command. If you use the frame-relay becn-response-enable command in scripts, you should replace it with the frame-relay adaptive-shaping command. This command will be removed from the product in a future release. See the description of the frame-relay adaptive-shaping command earlier in this chapter.
frame-relay broadcast-queue
To create a special queue for a specified interface to hold broadcast traffic that has been replicated for transmission on multiple data-link connection identifiers (DLCIs), use the frame-relay broadcast-queue interface configuration command.
frame-relay broadcast-queue size byte-rate packet-rate
Syntax Description
size
Number of packets to hold in the broadcast queue.
byte-rate
Maximum number of bytes to be sent per second.
packet-rate
Maximum number of packets to be sent per second.
Defaults
size—64 packets
byte-rate—256000 bytes per second
packet-rate—36 packets per second
Command Modes
Interface configuration
Command History
Usage Guidelines
For purposes of the Frame Relay broadcast queue, broadcast traffic is defined as any broadcast packet sent over the frame-relay interface. However, the broadcast traffic does not include the original routing packet or service access point (SAP) packet, which passes through the normal queue. Due to timing sensitivity, bridged broadcasts and spanning-tree packets are also sent through the normal queue. The Frame Relay broadcast queue is managed independently of the normal interface queue. It has its own buffers and a configurable service rate.
A broadcast queue is given a maximum transmission rate (throughput) limit measured in bytes per second and packets per second. The queue is serviced to ensure that only this maximum is provided. The broadcast queue has priority when transmitting at a rate below the configured maximum, and hence has a guaranteed minimum bandwidth allocation. The two transmission rate limits are intended to avoid flooding the interface with broadcasts. The actual limit in any second is the first rate limit that is reached.
Given the transmission rate restriction, additional buffering is required to store broadcast packets. The broadcast queue is configurable to store large numbers of broadcast packets.
The queue size should be set to avoid loss of broadcast routing update packets. The exact size will depend on the protocol being used and the number of packets required for each update. To be safe, set the queue size so that one complete routing update from each protocol and for each DLCI can be stored. As a general rule, start with 20 packets per DLCI. Typically, the byte rate should be less than both of the following:
•
•
The packet rate is not critical if you set the byte rate conservatively. Set the packet rate at 250-byte packets.
Examples
The following example specifies a broadcast queue to hold 80 packets, to have a maximum byte transmission rate of 240,000 bytes per second, and to have a maximum packet transmission rate of 160 packets per second:
frame-relay broadcast-queue 80 240000 160frame-relay cir
To specify the incoming or outgoing committed information rate (CIR) for a Frame Relay virtual circuit, use the frame-relay cir map-class configuration command. To reset the CIR to the default, use the no form of this command.
frame-relay cir {in | out} bps
no frame-relay cir {in | out} bps
Syntax Description
Defaults
56000 bits per second
Command Modes
Map-class configuration
Command History
Usage Guidelines
Use this command to specify a CIR for an SVC. The specified CIR value is sent through the SETUP message to the switch, which then attempts to provision network resources to support this value.
Examples
The following example sets a higher committed information rate for incoming traffic than for outgoing traffic (which is going out on a slow WAN line):
frame-relay cir in 2000000frame-relay cir out 9600Related Commands
Specifies the incoming or outgoing committed burst size (Bc) for a Frame Relay VC.
Sets the incoming or outgoing excess burst size (Be) for a Frame Relay VC.
frame-relay class
To associate a map class with an interface or subinterface, use the frame-relay class interface configuration command. To remove the association between the interface or subinterface and the named map class, use the no form of this command.
frame-relay class name
no frame-relay class name
Syntax Description
Defaults
No map class is defined.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command can apply to interfaces or subinterfaces.
All relevant parameters defined in the name map class are inherited by each virtual circuit created on the interface or subinterface. For each virtual circuit, the precedence rules are as follows:
1.
2.
3.
4.
Examples
The following example associates the slow_vcs map class with the serial 0.1 subinterface and the slow_vcs map class is defined to have an outbound CIR value of 9600:
interface serial 0.1frame-relay class slow_vcsmap-class frame-relay slow_vcsframe-relay cir out 9600If a virtual circuit exists on the serial 0.1 interface and is associated with some other map class, the parameter values of the second map class override those defined in the slow_vc map class for that virtual circuit.
Related Commands
frame-relay custom-queue-list
To specify a custom queue to be used for the virtual circuit queueing associated with a specified map class, use the frame-relay custom-queue-list map-class configuration command. To remove the specified queueing from the virtual circuit and cause it to revert to the default first-come, first-served queueing, use the no form of this command.
frame-relay custom-queue-list list-number
no frame-relay custom-queue-list list-number
Syntax Description
Defaults
If this command is not entered, the default queueing is first come, first served.
Command Modes
Map-class configuration
Command History
Usage Guidelines
Definition of the custom queue takes place in the existing manner (through queue-list commands).
Only one form of queueing can be associated with a particular map class; subsequent definitions overwrite previous ones.
Examples
The following example configures a custom queue list for the fast_vcs map class:
map-class frame-relay fast_vcsframe-relay custom-queue-list 1queue-list 1 queue 4 byte-count 100Related Commands
frame-relay de-group
To specify the discard eligibility (DE) group number to be used for a specified data-link connection identifier (DLCI), use the frame-relay de-group interface configuration command. To disable a previously defined group number assigned to a specified DLCI, use the no form of the command with the relevant keyword and arguments.
frame-relay de-group group-number dlci
no frame-relay de-group [group-number] [dlci]
Syntax Description
group-number
DE group number to apply to the specified DLCI number, between 1 and 10.
dlci
DLCI number.
Defaults
No DE group is defined.
Command Modes
Interface configuration
Command History
Usage Guidelines
To disable all previously defined group numbers, use the no form of this command with no arguments.
This command requires that Frame Relay software be enabled.
Frame Relay DE group functionality works on process-switched packets only.
The DE bit is not set or recognized by the Frame Relay switching code, but must be recognized and interpreted by the Frame Relay network.
Examples
The following example specifies that group number 3 will be used for DLCI 170:
frame-relay de-group 3 170Related Commands
Defines a DE list specifying the packets that have the DE bit set and thus are eligible for discarding during congestion on the Frame Relay switch.
frame-relay de-list
To define a discard eligibility (DE) list specifying the packets that have the DE bit set and thus are eligible for discarding when congestion is experienced on the Frame Relay switch, use the frame-relay de-list global configuration command. To delete a portion of a previously defined DE list, use the no form of this command.
frame-relay de-list list-number {protocol protocol | interface type number} characteristic
no frame-relay de-list list-number {protocol protocol | interface type number} characteristic
Syntax Description
Defaults
Discard eligibility is not defined.
Command Modes
Global configuration
Command History
Usage Guidelines
To remove an entire DE list, use the no form of this command with no options and arguments.
This prioritizing feature requires that the Frame Relay network be able to interpret the DE bit as indicating which packets can be dropped first in case of congestion, or which packets are less time sensitive, or both.
When you calculate packet size, include the data packet size, the ICMP header, the IP header, and the Frame Relay encapsulation bytes. For example, count 92 bytes of data, 8 bytes for the ICMP header, 20 bytes for the IP header, and 4 bytes for the Frame Relay encapsulation, which equals 124 bytes.
Examples
The following example specifies that IP packets larger than 512 bytes (including the 4 byte Frame Relay Encapsulation) will have the DE bit set:
frame-relay de-list 1 protocol ip gt 512frame-relay end-to-end keepalive error-threshold
To modify the keepalive error threshold value, use the frame-relay end-to-end keepalive error-threshold map-class configuration command. To reset the error threshold value to its default, use the no form of this command.
frame-relay end-to-end keepalive error-threshold {send | receive} count
no frame-relay end-to-end keepalive error-threshold {send | receive}
Syntax Description
Defaults
The default value for both the send and receive error threshold is 2.
Command Modes
Map-class configuration
Command History
Usage Guidelines
The send-side value can only be configured in bidirectional and request modes. The receive-side value can only be configured in bidirectional and reply modes. See the frame-relay end-to-end keepalive mode command. When you configure the error threshold, you will also want to configure the event window. See the frame-relay end-to-end keepalive event-window command.
Examples
The following example shows increasing the receive-side error threshold to 4 and changing the event window to 7:
map-class frame-relay olgaframe-relay end-to-end keepalive replyframe-relay end-to-end keepalive error-threshold receive 4frame-relay end-to-end keepalive event-window receive 7Related Commands
frame-relay end-to-end keepalive event-window
To modify the keepalive event window value, use the frame-relay end-to-end keepalive event-window map-class configuration command. To reset default event window size, use the no form of this command.
frame-relay end-to-end keepalive event-window {send | receive} size
no frame-relay end-to-end keepalive event-window {send | receive}
Syntax Description
send
The size of the send-side event window.
receive
The size of the receive-side event window.
size
Number of events in the event window. The maximum value is 32.
Defaults
The default value for both the send and receive event windows is 3.
Command Modes
Map-class configuration
Command History
Usage Guidelines
The send-side value can only be configured in bidirectional and request modes. The receive-side value can only be configured in bidirectional and reply modes. See the frame-relay end-to-end keepalive mode command. When you configure the event window, you will also want to configure the error-threshold. See the frame-relay end-to-end keepalive error-threshold command.
Examples
The following example shows increasing the receive-side error threshold to 4 and changing the event window to 7:
map-class frame-relay olgaframe-relay end-to-end keepalive replyframe-relay end-to-end keepalive error-threshold receive 4frame-relay end-to-end keepalive event-window receive 7Related Commands
frame-relay end-to-end keepalive mode
To enable Frame Relay end-to-end keepalives, use the frame-relay end-to-end keepalive mode map-class configuration command. To disable Frame Relay end-to-end keepalives, use the no form of this command.
frame-relay end-to-end keepalive mode {bidirectional | request | reply | passive-reply}
no frame-relay end-to-end keepalive
Syntax Description
bidirectional
Enables bidirectional mode.
request
Enables request mode.
reply
Enables reply mode.
passive-reply
Enables passive reply mode.
Defaults
When a Frame Relay end-to-end keepalive mode is enabled, default values depend on which mode is selected. For the meaning of the parameters, see the frame-relay end-to-end keepalive timer, frame-relay end-to-end keepalive event-window, frame-relay end-to-end keepalive error-threshold, and frame-relay end-to-end keepalive success-events commands.
Command Modes
Map-class configuration
Command History
Usage Guidelines
To enable Frame Relay end-to-end keepalives, Frame Relay must be configured. In addition, a map-class must be associated and a DLCI assigned to an interface, subinterface, VC or PVC. For more information on associating a frame-relay class with an interface, subinterface, VC or PVC, see the frame-relay class command. For more information on assigning a DLCI to an interface, subinterface, VC or PVC, see the frame-relay interface-dlci command.
In bidirectional mode, both ends of a VC send keepalive requests and respond to keepalive requests. If one end of the VC is configured in the bidirectional mode, the other end must also be configured in the bidirectional mode.
In request mode, the router sends keepalive requests and expects replies from the other end of the VC. If one end of a VC is configured in the request mode, the other end must be configured in the reply or passive-reply mode.
In reply mode, the router does not send keepalive requests, but waits for keepalive requests from the other end of the VC and replies to them. If no keepalive request has arrived within the timer interval, the router times out and increments the error counter by 1. If one end of a VC is configured in the reply mode, the other end must be configured in the request mode.
In passive-reply mode, the router does not send keepalive requests, but waits for keepalive requests from the other end of the VC and replies to them. No timer is set when in this mode, and the error counter is not incremented. If one end of a VC is configured in the passive-reply mode, the other end must be configured in the request mode.
displays parameter values for send- and receive-sides in bidirectional mode.
Table 18 Bidirectional Mode
Timer
10 seconds
15 seconds
Event Window
3
3
Error Threshold
2
2
Success Events
2
2
Table 19 displays parameter values for send- and receive-sides in request mode.
Table 19 Request Mode
Timer
10 seconds
no value set
Event Window
3
no value set
Error Threshold
2
no value set
Success Events
2
no value set
Table 20 displays parameter values for send- and receive-sides in reply mode.
Table 20 Reply Mode
Timer
no value set
15 seconds
Event Window
no value set
3
Error Threshold
no value set
2
Success Events
no value set
2
Passive-Reply Mode
In passive-reply mode, no values are set.
Examples
The following example configures one end of a VC so that a DLCI is assigned to a Frame Relay serial interface, a map class is associated wi
