Table Of Contents
Frame Relay Commands
class (map-list configuration)
class (virtual circuit configuration)
clear frame-relay-inarp
encapsulation frame-relay
frame-relay adaptive-shaping
frame-relay bc
frame-relay be
frame-relay becn-response-enable
frame-relay broadcast-queue
frame-relay cir
frame-relay class
frame-relay custom-queue-list
frame-relay de-group
frame-relay de-list
frame-relay idle-timer
frame-relay interface-dlci
frame-relay intf-type
frame-relay inverse-arp
frame-relay ip tcp header-compression
frame-relay lapf frmr
frame-relay lapf k
frame-relay lapf n200
frame-relay lapf n201
frame-relay lapf t200
frame-relay lapf t203
frame-relay lmi-n391dte
frame-relay lmi-n392dce
frame-relay lmi-n392dte
frame-relay lmi-n393dce
frame-relay lmi-n393dte
frame-relay lmi-t392dce
frame-relay lmi-type
frame-relay local-dlci
frame-relay map
frame-relay map bridge
frame-relay map clns
frame-relay map ip tcp header-compression
frame-relay mincir
frame-relay multicast-dlci
frame-relay payload-compress
frame-relay priority-dlci-group
frame-relay priority-group
frame-relay qos-autosense
frame-relay route
frame-relay svc
frame-relay switching
frame-relay traffic-rate
frame-relay traffic-shaping
keepalive (LMI)
map-class frame-relay
map-group
map-list
show frame-relay ip tcp header-compression
show frame-relay lapf
show frame-relay lmi
show frame-relay map
show frame-relay pvc
show frame-relay qos-autosense
show frame-relay route
show frame-relay svc maplist
show frame-relay traffic
Frame Relay Commands
Use the commands described in this chapter to configure access to Frame Relay networks.
For Frame Relay configuration information and examples, refer to the "Configuring Frame Relay" chapter in the Wide-Area Networking Configuration Guide.
class (map-list configuration)
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
protocol
|
Supported protocol, bridging, or logical link control keywords: appletalk, bridging, clns, decnet, dlsw, ip, ipx, llc2, rsrb, vines, and xns.
|
protocol-address
|
Protocol address. The bridge and clns keywords do not use protocol addresses.
|
class map-class
|
Name of the map class from which to derive quality of service (QOS) information.
|
broadcast
|
(Optional) Allows broadcasts on this SVC.
|
trigger
|
(Optional) Enables a broadcast packet to trigger an SVC. If an SVC already exists that uses this map class, the SVC will carry the broadcast. This keyword can be configured only if broadcast is also configured.
|
ietf
|
(Optional) Specifies RFC 1490 encapsulation. The default is Cisco encapsulation.
|
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
Release
|
Modification
|
11.2
|
This command was introduced.
|
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 15085551212
ip 131.108.177.100 class hawaii
appletalk 1000.2 class rainbow
In the following example, the trigger keyword allows AppleTalk broadcast packets to trigger an SVC:
ip 172.21.177.1 class jamaica broadcast ietf
appletalk 1000.2 class jamaica broadcast trigger ietf
Related Commands
Command
|
Description
|
map-class frame-relay
|
Specifies a map class to define QoS values for an SVC.
|
map-list
|
Specifies a map group and link it to a local E.164 or X.121 source address and a remote E.164 or X.121 destination address for Frame Relay SVCs.
|
class (virtual circuit configuration)
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
name
|
Name of map class to associate with this DLCI.
|
Defaults
No map class is defined.
Command Modes
Virtual circuit configuration
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
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-point
frame-relay interface-dlci 100
map-class frame-relay slow_vcs
The 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-multipoint
frame-relay map ip 131.26.13.2 100
frame-relay interface-dlci 100
frame-relay interface-dlci 100
map-class frame-relay fast_vc
frame-relay traffic-rate 56000 128000
frame-relay idle-timer 30
Related Commands
Command
|
Description
|
frame-relay interface-dlci
|
Assigns a DLCI to a specified Frame Relay subinterface on the router or access server.
|
frame-relay map
|
Defines mapping between a destination protocol address and the DLCI used to connect to the destination address.
|
map-class frame-relay
|
Specifies a map class to define QoS values for an SVC.
|
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
Release
|
Modification
|
10.0
|
This command was introduced.
|
Examples
The following example clears dynamically created Frame Relay maps:
Related Commands
Command
|
Description
|
frame-relay inverse-arp
|
Reenables Inverse ARP on a specified interface or subinterface, if the Inverse ARP was previously disabled on a router or access server configured for Frame Relay.
|
show frame-relay map
|
Displays the current map entries and information about the connections.
|
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
cisco
|
(Optional) Uses Cisco's own encapsulation, which is a 4-byte header, with 2 bytes to identify the data-link connection identifier (DLCI) and 2 bytes to identify the packet type.
|
ietf
|
(Optional) Sets the encapsulation method to comply with the Internet Engineering Task Force (IETF) standard (RFC 1490). Use this keyword when connecting to another vendor's equipment across a Frame Relay network.
|
Defaults
Enabled
Command Modes
Interface configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
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:
encapsulation frame-relay
Use 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:
encapsulation frame-relay ietf
frame-relay adaptive-shaping
Use the frame-relay adaptive-shaping map-class subcommand to select the type of backward notification you want to use. Use the no form of the command to disable backward notification.
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 messages.
|
Defaults
Disabled
Command Modes
Map-class subcommand
Command History
Release
|
Modification
|
11.3
|
This command was introduced.
|
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.
encapsulation frame-relay
frame-relay traffic-shaping
frame-relay class control-A
map-class frame-relay control-A
frame-relay adaptive-shaping foresight
Related Commands
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
Release
|
Modification
|
11.2
|
This command was introduced.
|
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 Bc 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 31383040709000
ip 172.21.177.26 class jamaica ietf
ipx 123.0000.0c07.d530 class jamaica ietf
map-class frame-relay jamaica
frame-relay cir in 2000000
frame-relay mincir in 1000000
frame-relay cir out 15000
frame-relay mincir out 10000
frame-relay idle-timer 30
Related Commands
Command
|
Description
|
frame-relay be
|
Sets the incoming or outgoing excess burst size (Be) for a Frame Relay VC.
|
frame-relay cir
|
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
in | out
|
Incoming or outgoing.
|
bits
|
Excess burst size, in bits.
|
Defaults
7000 bits
Command Modes
Map-class configuration
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
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 Bc 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 31383040709000
ip 172.21.177.26 class jamaica ietf
ipx 123.0000.0c07.d530 class jamaica ietf
map-class frame-relay jamaica
frame-relay cir in 2000000
frame-relay mincir in 1000000
frame-relay cir out 15000
frame-relay mincir out 10000
frame-relay idle-timer 30
Related Commands
Command
|
Description
|
frame-relay bc
|
Specifies the incoming or outgoing committed burst size (Bc) for a Frame Relay VC.
|
frame-relay cir
|
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.
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 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 transmitted per second.
|
packet-rate
|
Maximum number of packets to be transmitted per second.
|
Defaults
size—64 packets
byte-rate—256000 bytes per second
packet-rate—36 packets per second
Command Modes
Interface configuration
Command History
Release
|
Modification
|
10.3
|
This command was introduced.
|
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:
•
N/4 times the minimum remote access rate (measured in bytes per second), where N is the number of DLCIs to which the broadcast must be replicated
•
1/4 the local access rate (measured in bytes per second)
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 160
frame-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
in | out
|
Incoming or outgoing.
|
bps
|
Committed information rate (CIR), in bits per second.
|
Defaults
56000 bits per second
Command Modes
Map-class configuration
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
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 2000000
Related Commands
Command
|
Description
|
frame-relay bc
|
Specifies the incoming or outgoing committed burst size (Bc) for a Frame Relay VC.
|
frame-relay be
|
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 in 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
name
|
Name of the map class to associate with this interface or subinterface.
|
Defaults
No map class is defined.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
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.
Use the map class associated with the virtual circuit if it exists.
2.
If not, use the map class associated with the subinterface if the map class exists.
3.
If not, use map class associated with interface if the map class exists.
4.
If not, use the interface default parameters.
Examples
The following example associates the map class slow_vcs with the serial 0.1 subinterface and the map class slow_vcs is defined to have an outbound CIR value of 9600:
frame-relay class slow_vcs
map-class frame-relay slow_vcs
If 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 queuing associated with a specified map class, use the frame-relay custom-queue-list map-class configuration command. To remove the specified queuing from the virtual circuit and cause it to revert to the default first-come-first-served queuing, use the no form of this command.
frame-relay custom-queue-list list-number
no frame-relay custom-queue-list list-number
Syntax Description
list-number
|
Custom queue list number.
|
Defaults
If this command is not entered, the default queuing is first come first served.
Command Modes
Map-class configuration
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
Usage Guidelines
Definition of the custom queue takes place in the existing manner (through queue-list commands).
Only one form of queuing 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_vcs
frame-relay custom-queue-list 1
queue-list 1 queue 4 byte-count 100
Related Commands
frame-relay de-group
To specify the discard eligibility (DE) group number to be used for a specified 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
Release
|
Modification
|
10.0
|
This command was introduced.
|
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 170
Related Commands
Command
|
Description
|
frame-relay de-list
|
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
list-number
|
Number of the DE list.
|
protocol protocol
|
One of the following keywords corresponding to a supported protocol or device: arp—Address Resolution Protocol. apollo—Apollo Domain. appletalk—AppleTalk. bridge—bridging device. clns—ISO Connectionless Network Service. clns_es—CLNS end systems. clns_is—CLNS intermediate systems. compressedtcp—Compressed Transmission Control Protocol (TCP). decnet—DECnet. decnet_node—DECnet end node. decnet_router-L1—DECnet Level 1 (intra-area) router. decnet_router-L2—DECnet Level 2 (interarea) router. ip—Internet Protocol. ipx—Novell Internet Packet Exchange Protocol. vines—Banyan VINES. xns—Xerox Network Systems.
|
interface type
|
One of the following interface types: serial, null, or ethernet.
|
number
|
Interface number.
|
characteristic
|
One of the following:
fragments—Fragmented IP packets. tcp port—TCP packets to or from a specified port. udp port—User Datagram Protocol (UDP) packets to or from a specified port. list access-list-number—Previously defined access list number. gt bytes—Sets the DE bit for packets larger than the specified number of bytes (including the 4 byte Frame Relay Encapsulation). lt bytes—Sets the DE bit for packets smaller than the specified number of bytes (including the 4 byte Frame Relay Encapsulation).
|
Defaults
Discard eligibility is not defined.
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
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 512
frame-relay idle-timer
To specify the idle timeout interval for a switched virtual circuit, use the frame-relay idle-timer map-class configuration command. To reset the idle timer to its default interval, use the no form of this command.
frame-relay idle-timer [in | out] seconds
no frame-relay idle-timer seconds
Syntax Description
in
|
(Optional) timeout interval applies to inbound packet activity
|
out
|
(Optional) timeout interval applies to outbound packet activity
|
seconds
|
Time interval, in seconds, with no frames exchanged on a switched virtual circuit, after which the SVC is released.
|
Defaults
120 seconds
Command Modes
Map-class configuration
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
11.3
|
The following keywords were added:
• in
• out
|
Usage Guidelines
The frame-relay idle-timer command applies to switched virtual circuits that are associated with the map class where the idle-timer is defined.
The idle timer must be tuned for each application. Routing protocols such as Routing Information Protocol (RIP) might keep the SVC up indefinitely because updates go out every 10 seconds.
Beginning in Release 11.3, if in and out are not specified in the command, the timeout interval applies to both timers. In Release 11.2, the timeout interval applies to the outbound timer.
Examples
The following example defines the traffic rate and idle timer for the fast_vcs map class and applies those values to DLCI 100, which is associated with that map class:
frame-relay interface-dlci 100
map-class frame-relay fast_vcs
frame-relay traffic-rate 56000 128000
frame-relay idle-timer 30
Related Commands
frame-relay interface-dlci
To assign a data link connection identifier (DLCI) to a specified Frame Relay subinterface on the router or access server, use the frame-relay interface-dlci interface configuration command. To remove this assignment, use the no form of this command.
frame-relay interface-dlci dlci [ietf | cisco] [voice-encap size]
no frame-relay interface-dlci dlci [ietf | cisco] [voice-encap size]
BOOTP server only
frame-relay interface-dlci dlci [protocol ip ip-address]
Syntax Description
dlci
|
DLCI number to be used on the specified subinterface.
The following DLCI ranges are based on LMI protocol:
ANSI: 16 - 991
CISCO: 16 - 1007
Q933a: 16 - 991
|
ietf | cisco
|
(Optional) Encapsulation type: Internet Engineering Task Force (IETF) Frame Relay encapsulation or Cisco Frame Relay encapsulation.
|
protocol ip ip-address
|
(Optional) Indicates the IP address of the main interface of a new router or access server onto which a router configuration file is to be automatically installed over a Frame Relay network. Use this option only when this device will act as the BOOTP server for automatic installation over Frame Relay.
|
voice-encap size
|
(Supported on the Cisco MC3810 only.) Specifies that data segmentation will be used to support Voice over Frame Relay. The voice encapsulation size denotes the data segmentation size. For a list of recommended data segmentation sizes, see Usage Guidelines.
|
Defaults
No DLCI is assigned.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
This command is typically used for subinterfaces; however, it can also be used on main interfaces. Using the frame-relay interface-dlci command on main interfaces will enable the use of routing protocols on interfaces that use Inverse ARP. The frame-relay interface-dlci command on a main interface is also valuable for assigning a specific class to a single PVC where special characteristics are desired. Subinterfaces are logical interfaces associated with a physical interface. You must specify the interface and subinterface before you can use this command to assign any DLCIs and any encapsulation or broadcast options. See the "Examples" section for the sequence of commands.
This command is required for all point-to-point subinterfaces; it is also required for multipoint subinterfaces for which dynamic address resolution is enabled. It is not required for multipoint subinterfaces configured with static address mappings.
Use the protocol ip ip-address option only when this router or access server will act as the BOOTP server for autoinstallation over Frame Relay.
For the voice-encap option on the Cisco MC3810, set the data segmentation size based on the port access rate. Table 46 lists recommended data segmentation sizes for different port access rates. Also, when the voice-encap option is configured on the Cisco MC3810, all priority queuing, custom queuing, and weighted fair queuing is disabled on the interface.
Table 46 Recommended Data Segmentation Sizes for Port Access Rates
Port Access Rate
|
Recommended Data Segmentation Size 1
|
64 kbps
|
80 bytes
|
128 kbps
|
160 bytes
|
256 kbps
|
320 bytes
|
512 kbps
|
640 bytes
|
1536 kbps (full T1)
|
1600 bytes
|
2048 kbps (full E1)
|
1600 bytes
|
For more information about automatically installing router configuration files over a Frame Relay network, see the "Loading System Images and Microcode" chapter in the Configuration Fundamentals Configuration Guide.
Examples
The following example assigns DLCI 100 to serial subinterface 5.17:
! Enter interface configuration and begin assignments on interface serial 5
! Enter subinterface configuration by assigning subinterface 17
! Now assign a DLCI number to subinterface 5.17
frame-relay interface-dlci 100
Related Commands
Command
|
Description
|
frame-relay class
|
Associates a map class with an interface or subinterface.
|
frame-relay intf-type
Use the frame-relay intf-type interface configuration command to configure a Frame Relay switch type. Use the no form of this command to disable the switch.
frame-relay intf-type [dce | dte | nni]
no frame-relay intf-type [dce | dte | nni]
Syntax Description
dce
|
(Optional) Router or access server functions as a switch connected to a router.
|
dte
|
(Optional) Router or access server is connected to a Frame Relay network. This is the default.
|
nni
|
(Optional) Router or access server functions as a switch connected to a switch—supports Network-to-Network Interface (NNI) connections.
|
Defaults
dte
Command Modes
Interface configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
This command can be used only if Frame Relay switching has previously been enabled globally by use of the frame-relay switching command.
Examples
The following example configures a data terminal equipment (DTE) switch type:
frame-relay intf-type dte
frame-relay inverse-arp
If the Inverse Address Resolution Protocol (Inverse ARP) was previously disabled on a router or access server configured for Frame Relay, use the frame-relay inverse-arp interface configuration command to reenable Inverse ARP on a specified interface or subinterface. Use the no form of this command to disable this feature.
frame-relay inverse-arp [protocol] [dlci]
no frame-relay inverse-arp [protocol] [dlci]
Syntax Description
protocol
|
(Optional) Supported protocols: appletalk, decnet, ip, ipx, vines, and xns.
|
dlci
|
(Optional) One of the DLCI numbers used on the interface. Acceptable numbers are integers in the range 16 through 1007.
|
Defaults
Enabled
Command Modes
Interface configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
To enable Inverse ARP for all protocols that were enabled before the prior no frame-relay inverse-arp command was issued, use the frame-relay inverse-arp command without arguments. To disable Inverse ARP for all protocols of an interface, use the no frame-relay inverse-arp command without arguments.
To enable or disable Inverse ARP for a specific protocol and DLCI pair, use both the protocol and dlci arguments. To enable or disable Inverse ARP for all protocols on a DLCI, use only the dlci argument. To enable or disable Inverse ARP for a protocol for all DLCIs on the specified interface or subinterface, use only the protocol argument.
This implementation of Inverse ARP is based on RFC 1293. It allows a router or access server running Frame Relay to discover the protocol address of a device associated with the virtual circuit.
In Frame Relay, permanent virtual circuits (PVCs) are identified by a DLCI, which is the equivalent of a hardware address. By exchanging signaling messages, a network announces a new virtual circuit, and with Inverse ARP, the protocol address at the other side of the circuit can be discovered.
The show frame-relay map command displays the word "dynamic" to flag virtual circuits that are created dynamically by Inverse ARP.
Examples
The following example sets Inverse ARP on an interface running AppleTalk:
frame-relay inverse-arp appletalk 100
Related Commands
Command
|
Description
|
clear frame-relay-inarp
|
Clears dynamically created Frame Relay maps, which are created by the use of Inverse ARP.
|
show frame-relay map
|
Displays the current map entries and information about the connections.
|
frame-relay ip tcp header-compression
To configure an interface to ensure that the associated PVC will always carry outgoing Transmission Control Protocol/Internet Protocol (TCP/IP) headers in compressed form, use the frame-relay ip tcp header-compression interface configuration command. To disable compression of TCP/IP packet headers on the interface, use the no form of this command.
frame-relay ip tcp header-compression [passive]
no frame-relay ip tcp header-compression
Syntax Description
passive
|
(Optional) Compresses the outgoing TCP/IP packet header only if an incoming packet had a compressed header.
|
Defaults
Active TCP/IP header compression; all outgoing TCP/IP packets are subjected to header compression.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
This command applies to interfaces that support Frame Relay encapsulation, specifically serial ports and High-Speed Serial Interface (HSSI).
Frame Relay must be configured on the interface before this command can be used.
TCP/IP header compression and IETF encapsulation are mutually exclusive. If an interface is changed to IETF encapsulation, all encapsulation and compression characteristics are lost.
When you use this command to enable TCP/IP header compression, every IP map inherits the compression characteristics of the interface, unless header compression is explicitly rejected or modified by use of the frame-relay map ip tcp header compression command.
We recommend that you 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 type.
Examples
The following example configures serial interface 1 to use the default encapsulation (cisco) and passive TCP header compression:
encapsulation frame-relay
frame-relay ip tcp header-compression passive
Related Commands
Command
|
Description
|
frame-relay map ip tcp header-compression
|
Assigns header compression characteristics to an IP map different to the compression characteristics of the interface with which the IP map is associated.
|
frame-relay lapf frmr
To resume the default setting of sending the Frame Reject (FRMR) frame at the LAPF Frame Reject procedure after having set the option of not sending the frame, use the frame-relay frmr command. To set the option of not sending the Frame Reject (FRMR) frame at the LAPF Frame Reject procedure, use the no frame-relay lapf frmr interface configuration command.
frame-relay frmr
no frame-relay lapf frmr
Syntax Description
This command has no arguments or keywords.
Defaults
Send FRMR during the Frame Reject procedure.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
Usage Guidelines
If the Frame Relay switch does not support FRMR, use the no form of this command to suppress the transmission of FRMR frames.
Examples
The following example suppresses the transmission of FRMR frames:
frame-relay lapf k
To set the Link Access Procedure for Frame Relay (LAPF) window size k, use the frame-relay lapf k interface configuration command. To reset the maximum window size k to the default value, use the no form of this command
frame-relay lapf k number
no frame-relay lapf k [number]
Syntax Description
number
|
Maximum number of Information frames that are either outstanding for transmission or are transmitted but unacknowledged, in the range 1 through 127.
|
Defaults
7 frames
Command Modes
Interface configuration
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
Usage Guidelines
This command is used to tune Layer 2 system parameters to work well with the Frame Relay switch. Normally, you do not need to change the default setting.
Manipulation of Layer 2 parameters is not recommended if you do not know well the resulting functional change. For more information, refer to the ITU-T Q.922 specification for LAPF.
Examples
The following example resets the LAPF window size k to the default value:
Related Commands