-
Router Products Command Reference
-
About This Manual
-
Router Product Overview
-
User Interface Commands
-
System Image, Microcode Image, and Configuration File Load Comm
-
Terminal Line and Modem Support Commands
-
System Management Commands
-
Interface Commands
-
ATM Commands
-
DDR Commands
-
Frame Relay Commands
-
ISDN Commands
-
LAN Emulation Commands
-
SMDS Commands
-
X.25 Commands
-
Apollo Domain Commands
-
AppleTalk Commands
-
Banyan VINES Commands
-
DECnet Commands
-
IP Commands
-
IP Routing Protocols Commands
-
ISO CLNS Commands
-
Novell IPX Commands
-
XNS Commands
-
Source-Route Bridging Commands
-
Remote Source-Route Bridging Commands
-
DLSw+ Configuration Commands
-
STUN and BSTUN Configuration Commands
-
LLC2 and SDLC Configuration Commands
-
IBM Network Media Translation Commands
-
DSPU and SNA Service Point Configuration Commands
-
SNA Frame Relay Access Support Commands
-
APPN Configuration Commands
-
IBM Channel Attach Configuration Commands
-
References and Recommended Reading
-
Ethernet Type Codes
-
Regular Expressions
-
ASCII character Set
-
Platform Support
-
Switching Appendix
-
Table Of Contents
frame-relay ip tcp header-compression
frame-relay map ip tcp header-compression
frame-relay payload-compress packet-by-packet
frame-relay priority-dlci-group
configurationform of this frame-relay switching
show frame-relay ip tcp header-compression
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 Router Products Configuration Guide.
clear frame-relay-inarp
To clear dynamically created Frame Relay maps, which are created by the use of Inverse ARP, use the clear frame-relay-inarp EXEC command.
clear frame-relay-inarp
Syntax Description
This command has no arguments or keywords.
Command Mode
EXEC
Example
The following example clears dynamically created Frame Relay maps:
clear frame-relay-inarpRelated Commands
frame-relay inverse-arp
show frame-relay mapencapsulation 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
Default
Enabled
Command Mode
Interface configuration
Usage Guidelines
Use this command with no keywords to restore the default Cisco encapsulation.
Examples
The following example configures Cisco Frame Relay encapsulation on interface serial 1:
interface serial 1 encapsulation frame-relayUse the ietf keyword if your router is connected to another vendor's equipment across a Frame Relay network to conform with RFC 1490:
interface serial 1 encapsulation frame-relay ietfframe-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
Command Syntax
Default
The default values are as follows:
size—64 packets
byte-rate—256000 bytes per second
packet-rate—36 packets per secondCommand Mode
Interface configuration
Usage Guidelines
For purposes of the Frame Relay broadcast queue, broadcast traffic is defined as packets that have been replicated for transmission on multiple DLCIs, but it does not include the original routing packet or SAP packet, which passes through the normal queue. Due to timing sensitivity, bridged broadcasts and spanning tree packets are 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 will be 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.
As a general rule, 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
•
The packet rate is not critical if you set the byte rate conservatively. As a general rule, set the packet rate assuming 250-byte packets.
Example
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 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, in the range from 1 through 10.
dlci
DLCI number.
Default
No DE group is defined.
Command Mode
Interface configuration
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.
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.
Example
The following example specifies that group number 3 will be used for DLCI 170:
frame-relay de-group 3 170Related Command
frame-relay de-list
frame-relay de-list
To define a discard eligibility (DE) list specifying which packets will have the DE bit set and thus will be 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} characteristicSyntax Description
Default
Discard eligibility is not defined.
Command Mode
Global configuration
Usage Guidelines
To remove an entire DE list, use the no form of this command with no options and arguments.
This prioritization 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.
Example
The following example specifies that IP packets larger than 512 bytes will have the discard eligibility bit set.
frame-relay de-list 1 protocol ip gt 512frame-relay interface-dlci
To assign a data link connection identifier (DLCI) to a specified Frame Relay subinterface on the router, 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 [option]
no frame-relay interface-dlci dlci [option]
frame-relay interface-dlci dlci [protocol ip ip-address]Syntax Description
dlci
A DLCI number to be used on the specified subinterface.
option
(Optional) Broadcast or encapsulation keyword defined in Table 9-1.
protocol ip ip-address
Indicates the IP address of the serial interface of a new router onto which a router configuration file is to be autoinstalled over a Frame Relay network. Use this option only when this router will act as the BOOTP server for autoinstallation over Frame Relay.
Default
No DLCI is assigned.
Command Mode
Interface configuration
Usage Guidelines
Use this command only for subinterfaces on a router. Use of the command on an interface, rather than a subinterface, will prevent the router from forwarding packets intended for that DLCI.
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 "Example" 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 will act as the BOOTP server for autoinstallation over Frame Relay.
For more information about autoinstalling router configuration files over a Frame Relay network, see the "Loading System Images, Microcode Images, and Configuration Files" chapter in the Router Products Configuration Guide.
lists the frame-relay interface-dlci option keywords.
Table 9-1 Frame Relay Interface-DLCI Option Keywords
broadcast
Broadcasts should be forwarded out through this interface.
ietf
IETF Frame Relay encapsulation.
cisco
Cisco Frame Relay encapsulation.
Example
The following example assigns DLCI 100 to serial subinterface 5.17:
! Enter interface configuration and begin assignments on interface serial 5interface serial 5! Enter subinterface configuration by assigning subinterface 17interface serial 5.17! Now assign a DLCI number to subinterface 5.17frame-relay interface-dlci 100frame-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
Default
dte
Command Mode
Interface configuration
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.
Example
The following example configures a DTE switch type:
frame-relay switching!interface serial 2frame-relay intf-type dteframe-relay inverse-arp
If the Inverse Address Resolution Protocol (Inverse ARP) was previously disabled on a router 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
Supported protocols: appletalk, decnet, ip, ipx, vines, and xns.
dlci
One of the DLCI numbers used on the interface. Acceptable numbers are integers in the range 16 through 1007.
Default
Enabled.
Command Mode
Interface configuration
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 a router 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 running Frame Relay to discover the protocol address of a device associated with the virtual circuit.
In Frame Relay, permanent virtual circuits 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.
Example
The following example sets Inverse ARP on an interface running AppleTalk:
interface serial 0frame-relay inverse-arp appletalk 100Related Commands
clear frame-relay-inarp
show frame-relay mapframe-relay ip tcp header-compression
To configure an interface to ensure that the associated PVC will always carry outgoing 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-compressionSyntax Description
passive
(Optional) Compresses the outgoing TCP/IP packet header only if an incoming packet had a compressed header.
Default
Active TCP/IP header compression; all outgoing TCP/IP packets are subjected to header compression.
Command Mode
Interface configuration
Usage Guidelines
This command applies to interfaces that support Frame Relay encapsulation, specifically serial ports and 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.
Example
The following example configures serial interface 1 to use the default encapsulation (cisco) and passive TCP header compression:
interface serial 1encapsulation frame-relayframe-relay ip tcp header-compression passiveRelated Command
frame-relay map ip tcp header-compression
frame-relay keepalive
To enable the local management interface (LMI) mechanism for serial lines using Frame Relay encapsulation, use the frame-relay keepalive interface configuration command. Use the
no form of this command to disable this capability.frame-relay keepalive number
no frame-relay keepaliveSyntax Description
number
An integer that defines the keepalive interval. The interval must be set and must be less than the interval set on the switch; see the frame-relay lmi-t392dce command description.
Default
10 seconds
Command Mode
Interface configuration
Usage Guidelines
The frame-relay keepalive and keepalive commands perform the same function; both commands enable the keepalive sequence. The keepalive sequence is part of the Local Management Interface (LMI) protocol, so these commands also control the enabling and disabling of the LMI.
When viewing the configuration information using the show configuration command, only the keepalive command setting is included; you will not see the frame-relay keepalive setting.
Note
Example
The following example sets the keepalive timer on the server for a period that is two or three seconds faster (shorter interval) than the interval set on the keepalive timer of the Frame Relay switch. The difference in keepalive intervals ensures proper synchronization between the Cisco server and the Frame Relay switch.
interface serial 3 frame-relay keepalive 8Related Commands
A dagger (†) indicates that the command is documented in another chapter.
keepalive †
frame-relay lmi-t392dceframe-relay lmi-n391dte
To set a full status polling interval, use the frame-relay lmi-n391dte interface configuration command. To restore the default interval value, assuming an LMI has been configured, use the no form of this command.
frame-relay lmi-n391dte keep-exchanges
no frame-relay lmi-n391dte keep-exchangesSyntax Description
keep-exchanges
Number of keep exchanges to be done before requesting a full status message. Acceptable value is a positive integer in the range 1 through 255.
Default
6 keep exchanges
Command Mode
Interface configuration
Usage Guidelines
Use this command when the interface is configured as data terminal equipment (DTE) or Network-to-Network Interface (NNI) as a means of setting the full status message polling interval.
Example
In the following example, one out of every four status inquiries generated by the router will request a full status response from the switch. The other three status inquiries will request keepalive exchanges only.
interface serial 0frame-relay intf-type DTEframe-relay lmi-n391dte 4frame-relay lmi-n392dce
To set the DCE and the Network-to-Network Interface (NNI) error threshold, use the frame-relay lmi-n392dce interface configuration command. To remove the current setting, use the no form of this command.
frame-relay lmi-n392dce threshold
no frame-relay lmi-n392dce thresholdSyntax Description
Default
2
Command Mode
Interface configuration
Usage Guidelines
In Cisco's implementation, N392 errors must occur within the number defined by the N393 event count in order for the link to be declared down. Therefore, the threshold value for this command must be less than the count value defined in the frame-relay lmi-n393dce command.
Example
In the following example, the LMI failure threshold is set to three. The router acts as a Frame Relay DCE or NNI switch.
interface serial 0frame-relay intf-type DCEframe-relay lmi-n392dce 3Related Command
frame-relay lmi-n393dce
frame-relay lmi-n392dte
To set the error threshold on a DTE or NNI interface, use the frame-relay lmi-n392dte interface configuration command. To remove the current setting, use the no form of this command.
frame-relay lmi-n392dte threshold
no frame-relay lmi-n392dte thresholdSyntax Description
Default
3
Command Mode
Interface configuration
Example
In the following example, the LMI failure threshold is set to three. The router acts as a Frame Relay DTE or NNI switch.
interface serial 0frame-relay intf-type DTEframe-relay lmi-n392dte 3frame-relay lmi-n393dce
To set the DCE and NNI monitored events count, use the frame-relay lmi-n393dce interface configuration command. To remove the current setting, use the no form of this command.
frame-relay lmi-n393dce events
no frame-relay lmi-n393dce eventsSyntax Description
events
Monitored events count value. Acceptable value is a positive integer in the range 1 through 10.
Default
2
Command Mode
Interface configuration
Usage Guidelines
This command and the frame-relay lmi-n392dce command define the condition that causes the link to be declared down. In Cisco's implementation, N392 errors must occur within the events count in order for the link to be declared down. Therefore, the events value defined in this command must be greater than the threshold value defined in the frame-relay lmi-n392dce command.
Example
In the following example, the LMI monitored events count is set to three. The router acts as a Frame Relay DCE or NNI switch.
interface serial 0frame-relay intf-type DCEframe-relay lmi-n393dce 3Related Command
frame-relay lmi-n392dce
frame-relay lmi-n393dte
To set the monitored event count on a DTE or NNI interface, use the frame-relay lmi-n393dte interface configuration command. To remove the current setting, use the no form of this command.
frame-relay lmi-n393dte events
no frame-relay lmi-n393dte eventsSyntax Description
events
Monitored events count value. Acceptable value is a positive integer in the range 1 through 10.
Default
4
Command Mode
Interface configuration
Example
In the following example, the LMI monitored events count is set to three. The router acts as a Frame Relay DTE or NNI switch.
interface serial 0frame-relay intf-type DTEframe-relay lmi-n393dte 3frame-relay lmi-t392dce
To set the polling verification timer on a DCE or NNI interface, use the frame-relay lmi-t392dce interface configuration command. To remove the current setting, use the no form of this command.
frame-relay lmi-t392dce timer
no frame-relay lmi-t392dce timerSyntax Description
timer
Polling verification timer value (in seconds). Acceptable value is a positive integer in the range 5 through 30.
Default
15
Command Mode
Interface configuration
Usage Guidelines
The value for the timer must be greater than the DTE or NNI keepalive timer.
Example
The following example indicates a polling verification timer on a DCE or NNI interface set to 20:
interface serial 3frame-relay intf-type DCEframe-relay lmi-t392dce 20Related Command
frame-relay keepalive
frame-relay lmi-type
To select the Local Management Interface (LMI) type, use the frame-relay lmi-type interface configuration command. To return to the default LMI type, use the no form of this command.
frame-relay lmi-type {ansi | cisco | q933a}
no frame-relay lmi-type {ansi | q933a}Syntax Description
ansi
Annex D defined by ANSI standard T1.617.
cisco
LMI type defined jointly by Cisco and three other companies.
q933a
ITU-T Q.933 Annex A.1
1 The International Telecommunication Union Telecommunication Standardization Sector (ITU-T) carries out the functions of the former Consultative Committee for International Telegraph and Telephone (CCITT).
Default
Cisco LMI
Command Mode
Interface configuration
Usage Guidelines
Cisco's implementation of Frame Relay supports three LMI types: Cisco, ANSI Annex D, and
ITU-T Q.933 Annex A.The LMI type is set on a per-interface basis and is shown in the output of the show interfaces EXEC command.
Example
The following is an example of the commands you enter to select the ANSI Annex D LMI type:
interface Serial1encapsulation frame-relayframe-relay lmi-type ansiframe-relay local-dlci
To set the source DLCI for use when the LMI is not supported, use the frame-relay local-dlci interface configuration command. To remove the DLCI number, use the no form of this command.
frame-relay local-dlci number
no frame-relay local-dlciSyntax Description
Default
No source DLCI is set.
Command Mode
Interface configuration
Usage Guidelines
If LMI is supported and the multicast information element is present, the network server sets its local DLCI based on information provided via the LMI.
Note
Example
The following example specifies 100 as the local DLCI:
interface serial 4 frame-relay local-dlci 100frame-relay map
To define the mapping between a destination protocol address and the DLCI used to connect to the destination address, use the frame-relay map interface configuration command. Use the no form of this command to delete the map entry.
frame-relay map protocol protocol-address dlci [broadcast] [ietf | cisco | payload-compress packet-by-packet]
no frame-relay map protocol protocol-address
Syntax Description
Default
No mapping is defined.
Command Mode
Interface configuration
Usage Guidelines
There can be many DLCIs known by a router or access server that can send data to many different places, but they are all multiplexed over one physical link. The Frame Relay map tells the Cisco IOS software how to get from a specific protocol and address pair to the correct DLCI.
The optional ietf and cisco keywords allow flexibility in the configuration. If no keywords are specified in the configuration, the map inherits the attributes set with the encapsulation frame-relay command. You can also use the encapsulation options to specify that, for example, all interfaces use IETF encapsulation except one, which needs the original Cisco encapsulation method, and it can be defined using the cisco keyword with the frame-relay map command.
Payload compression is Cisco-proprietary and will not interoperate with routers of other manufacturers.
You can disable payload compression by entering the no frame-relay map payload command and then entering the frame-relay map command again with one of the other encapsulation keywords: cisco or ietf.
Use the frame-relay map command to enable or disable payload compression on multipoint interfaces. Use the frame-relay payload-compress packet-by-packet command to enable or disable payload compression on point-to-point interfaces.
The broadcast keyword provides two functions: It forwards broadcasts when multicasting is not enabled, and it simplifies the configuration of OSPF for nonbroadcast networks that will use Frame Relay.
The broadcast keyword might also be required for some routing protocols—for example, AppleTalk—that depend on regular routing table updates, especially when the router at the remote end is waiting for a routing update packet to arrive before adding the route.
By requiring selection of a designated router, OSPF treats a nonbroadcast, multiaccess network such as Frame Relay in much the same way as it treats a broadcast network. In previous releases, this required manual assignment in the OSPF configuration using the neighbor interface router command. When the frame-relay map command is included in the configuration with the broadcast, and the ip ospf network command (with the broadcast keyword) is configured, there is no need to configure any neighbors manually. OSPF will now automatically run over the Frame Relay network as a broadcast network. (Refer to the ip ospf network interface command for more detail.)
Note
Example
The following example maps the destination IP address 131.108.123.1 to DLCI 100:
interface serial 0 frame-relay map IP 131.108.123.1 100 broadcastOSPF will use DLCI 100 to broadcast updates.
Related commands
frame-relay payload-compress packet-by-packet
frame-relay map bridge
Use the frame-relay map bridge interface configuration command to specify that broadcasts should be forwarded when bridging. Use the no form of this command to delete the map entry.
frame-relay map bridge dlci [broadcast] [ietf]
no frame-relay map bridge dlciSyntax Description
Default
No broadcasts are forwarded.
Command Mode
Interface configuration
Examples
The following example uses DLCI 144 for bridging:
interface serial 0frame-relay map bridge 144 broadcastThe following example sets up separate point-to-point links over a subinterface and runs transparent bridging over it:
interface serial 0bridge-group 1encapsulation frame-relayinterface serial 0.1bridge-group 1frame-relay map bridge 42 broadcastinterface serial 0.2bridge-group 1frame-relay map bridge 64 broadcastinterface serial 0.3bridge-group 1frame-relay map bridge 73 broadcastDLCI 42 is used as the link; see the section "Frame Relay Configuration Examples" in the Router Products Configuration Guide for more examples of subinterfaces.
frame-relay map clns
Use the frame-relay map clns interface configuration command to specify that broadcasts should be forwarded when routing using ISO CLNS. Use the no form of this interface configuration command to delete the map entry.
frame-relay map clns dlci [broadcast]
no frame-relay map clns dlciSyntax Description
dlci
DLCI number to which CLNS broadcasts should be forwarded on the specified interface.
broadcast
(Optional) Broadcasts should be forwarded when multicast is not enabled.
Default
No broadcasts are forwarded.
Command Mode
Interface configuration
Example
The following example uses DLCI 125 for ISO CLNS routing:
interface serial 0 frame-relay map clns 125 broadcastframe-relay map ip tcp header-compression
To assign header compression characteristics to an IP map that differ from the compression characteristics of the interface with which the IP map is associated, use the frame-relay map ip tcp header-compression interface configuration command. To remove the IP map, use the no form of this command.
frame-relay map ip ip-address dlci [broadcast] [cisco | ietf] [nocompress]
tcp header-compression {active | passive}
no frame-relay map ip ip-address dlciSyntax Description
Default
The default encapsulation is cisco.
Command Mode
Interface configuration
Usage Guidelines
To disable TCP/IP header compression on the IP map, use the nocompress form of the command.
IP maps inherit the compression characteristics of the associated interface unless this command is used to provide different characteristics. This command can also be used to reconfigure an IP map that existed before TCP header compression was configured on the associated interface.
When IP maps at both ends of a connection inherit passive compression, the connection will never transfer compressed traffic because neither side will generate a packet with a compressed header.
If you change the encapsulation characteristics of the interface to IETF, you lose the TCP header compression configuration of the associated IP map.
The command frame-relay map ip ip-address dlci tcp header-compression active can also be entered as frame-relay map ip ip-address dlci active tcp header-compression.
Example
The following example illustrates a command sequence configuring an IP map associated with serial interface 1 to enable active TCP header compression:
interface serial 1encapsulation frame-relayip address 131.108.177.170 255.255.255.0frame-relay map ip 131.108.177.180 190 cisco tcp header-compression activeRelated Command
frame-relay ip tcp header-compression
frame-relay multicast-dlci
Use the frame-relay multicast-dlci interface configuration command to define the DLCI to be used for multicasts. Use the no form of this command to remove the multicast group.
frame-relay multicast-dlci number
no frame-relay multicast-dlciSyntax Description
Default
No DLCI is defined.
Command Mode
Interface configuration
Usage Guidelines
Use this command when the multicast facility is not supported. Network transmissions (packets) sent to a multicast DLCI are delivered to all network servers defined as members of the multicast group.
Note
Example
The following example specifies 1022 as the multicast DLCI:
interface serial 0frame-relay multicast-dlci 1022frame-relay payload-compress packet-by-packet
To enable the stac payload compression on a specified point-to-point interface or subinterface, use the frame-relay payload-compress packet-by-packet interface configuration command. To disable payload compression on a specified point-to-point interface or subinterface, use the no form of this command.
frame-relay payload-compress packet-by-packet
no frame-relay payload-compress packet-by-packetSyntax Description
This command has no keywords and arguments.
Default
Disabled
Command Mode
Interface configuration
Usage Guidelines
Use the frame-relay payload-compress packet-by-packet command to enable or disable payload compression on a point-to-point interface or subinterface. Use the frame-relay map command to enable or disable payload compression on a multipoint interface or subinterface.
Related Commands
frame-relay priority-dlci-group
To enable multiple parallel DLCIs for different types of Frame Relay traffic, associate specified DLCIs with the same group, and define their levels, use the frame-relay priority-dlci-group subinterface configuration command.
frame-relay priority-dlci-group group-number high-dlci medium-dlci normal-dlci low-dlci
Syntax Description
Default
Disabled
Command Mode
Interface configuration
Usage Guidelines
This command applies at the subinterface level.
Levels in descending order are high, medium, normal, and low.
This command defines different DLCIs for different categories of traffic. It does not itself define priority queueing but can be used in association with it.
A global priority list must be defined before this command is used. In addition, the DLCIs mentioned in this command must be defined before this command is used.
If you do not explicitly specify a DLCI for each of the levels, the last DLCI specified in the command line is used as the value of the remaining arguments. For example, the following two commands are equivalent:
frame-relay priority-dlci-group 1 40 50frame-relay priority-dlci-group 1 40 50 50 50When you configure frame-relay map commands or use Inverse ARP, the high level DLCI is the only one that is mapped. If you had entered one of the commands above, you would configure DLCI 40, but not DLCI 50, in a frame-relay map command.
Related Command
A dagger (†) indicates that the command is documented in another chapter.
frame-relay map
priority-list †frame-relay route
Use the frame-relay route interface configuration command to specify the static route for PVC switching. Use the no form of this command to remove a static route.
frame-relay route in-dlci out-interface out-dlci
no frame-relay route in-dlci out-interface out-dlciSyntax Description
Default
No static route is specified.
Command Mode
Interface configuration
Examples
The following example configures a static route that allows packets in DLCI 100 and transmits packets out over DLCI 200 on interface serial 2:
frame-relay route 100 interface Serial2 200The following example illustrates the commands you enter for a complete configuration that includes two static routes for PVC switching between interface serial 1 and interface serial 2:
interface Serial1no ip addressencapsulation frame-relaykeepalive 15frame-relay lmi-type ansiframe-relay intf-type dceframe-relay route 100 interface Serial2 200frame-relay route 101 interface Serial2 201clockrate 2000000configurationform of this frame-relay switching
Use the frame-relay switching global configuration command to enable PVC switching on a Frame Relay DCE or an NNI. Use the no form of this command to disable switching.
frame-relay switching
no frame-relay switchingSyntax Description
This command has no arguments or keywords.
Default
Disabled
Command Mode
Global configuration
Usage Guidelines
This command must be added to the configuration file before configuring the routes.
Example
The following example shows the simple command that is entered in the configuration file before the Frame Relay configuration commands to enable switching:
frame-relay switchingshow frame-relay ip tcp header-compression
To display statistics and TCP/IP header compression information for the interface, use the show frame-relay ip tcp header-compression EXEC command.
show frame-relay ip tcp header-compression
Syntax Description
This command has no arguments or keywords.
Command Mode
EXEC
Sample Display
The following is sample output from the show frame-relay ip tcp header-compression command:
DLCI 200 Link/Destination info: ip 131.108.177.200Interface Serial0:Rcvd: 40 total, 36 compressed, 0 errors0 dropped, 0 buffer copies, 0 buffer failuresSent: 0 total, 0 compressed0 bytes saved, 0 bytes sentConnect: 16 rx slots, 16 tx slots, 0 long searches, 0 misses, 0% hit ratioFive minute miss rate 0 misses/sec, 0 max misses/secdescribes the fields shown in the display.
Table 9-2 Show Frame-Relay IP TCP Header-Compression Field Descriptions
show frame-relay lmi
Use the show frame-relay lmi EXEC command to display statistics about the Local Management Interface (LMI).
show frame-relay lmi [type number]
Syntax Description
Command Mode
EXEC
Usage Guidelines
Enter the command without arguments to obtain statistics about all Frame Relay interfaces.
Sample Displays
The following is sample output from the show frame-relay lmi command when the interface is a DTE:
Router# show frame-relay lmiLMI Statistics for interface Serial1 (Frame Relay DTE) LMI TYPE = ANSIInvalid Unnumbered info 0 Invalid Prot Disc 0Invalid dummy Call Ref 0 Invalid Msg Type 0Invalid Status Message 0 Invalid Lock Shift 0Invalid Information ID 0 Invalid Report IE Len 0Invalid Report Request 0 Invalid Keep IE Len 0Num Status Enq. Sent 9 Num Status msgs Rcvd 0Num Update Status Rcvd 0 Num Status Timeouts 9The following is sample output from the show frame-relay lmi command when the interface is an NNI:
Router# show frame-relay lmiLMI Statistics for interface Serial3 (Frame Relay NNI) LMI TYPE = CISCOInvalid Unnumbered info 0 Invalid Prot Disc 0Invalid dummy Call Ref 0 Invalid Msg Type 0Invalid Status Message 0 Invalid Lock Shift 0Invalid Information ID 0 Invalid Report IE Len 0Invalid Report Request 0 Invalid Keep IE Len 0Num Status Enq. Rcvd 11 Num Status msgs Sent 11Num Update Status Rcvd 0 Num St Enq. Timeouts 0Num Status Enq. Sent 10 Num Status msgs Rcvd 10Num Update Status Sent 0 Num Status Timeouts 0describes significant fields shown in the output.
Table 9-3 Show Frame-Relay LMI Field Descriptions
show frame-relay map
To display the current map entries and information about the connections, use the show frame-relay map EXEC command.
show frame-relay map
Syntax Description
This command has no arguments or keywords.
Command Mode
EXEC
Sample Display
The following is sample output from the show frame-relay map command:
Router# show frame-relay mapSerial 1 (administratively down): ip 131.108.177.177dlci 177 (0xB1,0x2C10), static,broadcast,CISCOTCP/IP Header Compression (inherited), passive (inherited)describes significant fields shown in the display.
Table 9-4
Show Frame-Relay Map Field Descriptions
Related Command
show frame-relay pvc
show frame-relay pvc
To display statistics about PVCs for Frame Relay interfaces, use the show frame-relay pvc EXEC command.
show frame-relay pvc [type number [dlci]]
Syntax Description
Command Mode
EXEC
Usage Guidelines
To obtain statistics about PVCs on all Frame Relay interfaces, use this command with no arguments.
When the interface is configured as a DCE and the DLCI usage is SWITCHED, the value displayed in the PVC STATUS field is determined by the status of outgoing interfaces (up or down) and status of the outgoing PVC. The status of the outgoing PVC is updated in the local management interface (LMI) message exchange. PVCs terminated on a DCE interface use the status of the interface to set the PVC STATUS.
If the outgoing interface is a tunnel, the PVC status is determined by what is learned from the tunnel.
If an LMI status report indicates that a PVC is not active, then it is marked as inactive. A PVC is marked as deleted if it is not listed in a periodic LMI status message.
In the case of a hybrid DTE switch, the PVC status on the DTE side is determined by the PVC status reported by the external Frame Relay network through the LMI.
Congestion control mechanisms are currently not supported, but the switch passes Forward Explicit Congestion Notification (FECN) bits, backward explicit congestion notification (BECN) bits, and discard eligibility (DE) bits unchanged from ingress to egress points in the network.
Sample Display
The following is sample output from the show frame-relay pvc command:
Router# show frame-relay pvcPVC Statistics for interface Serial1 (Frame Relay DCE)DLCI = 100, DLCI USAGE = SWITCHED, PVC STATUS = ACTIVEinput pkts 0 output pkts 0 in bytes 0out bytes 0 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0pvc create time 0:03:03 last time pvc status changed 0:03:03Num Pkts Switched 0DLCI = 101, DLCI USAGE = SWITCHED, PVC STATUS = INACTIVEinput pkts 0 output pkts 0 in bytes 0out bytes 0 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0pvc create time 0:02:58 last time pvc status changed 0:02:58Num Pkts Switched 0DLCI = 102, DLCI USAGE = SWITCHED, PVC STATUS = DELETEDinput pkts 0 output pkts 0 in bytes 0out bytes 0 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0pvc create time 0:02:58 last time pvc status changed 0:02:58Num Pkts Switched 0The following is sample output from the show frame-relay pvc command for multipoint subinterfaces. The output displays both the subinterface number and the DLCI. This display is the same whether the PVC is configured for static or dynamic addressing.
DLCI = 300, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0.103>> input pkts 10 output pkts 7 in bytes 6222> out bytes 6034 dropped pkts 0 in FECN pkts 0> in BECN pkts 0 out FECN pkts 0 out BECN pkts 0> in DE pkts 0 out DE pkts 0> pvc create time 0:13:11 last time pvc status changed 0:11:46>>DLCI = 400, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0.104>> input pkts 20 output pkts 8 in bytes 5624> out bytes 5222 dropped pkts 0 in FECN pkts 0> in BECN pkts 0 out FECN pkts 0 out BECN pkts 0> in DE pkts 0 out DE pkts 0> pvc create time 0:03:57 last time pvc status changed 0:03:48describes the fields shown in the displays.
Table 9-5 Show Frame-Relay PVC Field Descriptions
show frame-relay route
Use the show frame-relay route EXEC command to display all configured Frame Relay routes, along with their status.
show frame-relay route
Syntax Description
This command has no arguments or keywords.
Command Mode
EXEC
Sample Display
The following is sample output from the show frame-relay route command:
Router# show frame-relay routeInput Intf Input Dlci Output Intf Output Dlci StatusSerial1 100 Serial2 200 activeSerial1 101 Serial2 201 activeSerial1 102 Serial2 202 activeSerial1 103 Serial3 203 inactiveSerial2 200 Serial1 100 activeSerial2 201 Serial1 101 activeSerial2 202 Serial1 102 activeSerial3 203 Serial1 103 inactivedescribes significant fields shown in the output.
Table 9-6 Show Frame-Relay Route Field Descriptions
show frame-relay traffic
Use the show frame-relay traffic EXEC command to display the router's global Frame Relay statistics since the last reload.
show frame-relay traffic
Syntax Description
This command has no arguments or keywords.
Command Mode
EXEC
Sample Display
The following is sample output from the show frame-relay traffic command:
Router# show frame-relay trafficFrame Relay statistics:ARP requests sent 14, ARP replies sent 0ARP request recvd 0, ARP replies recvd 10Information shown in the display is self-explanatory.
show interfaces serial
Use the show interfaces serial EXEC command to display information about a serial interface. When using the Frame Relay encapsulation, use the show interfaces serial command to display information about the multicast DLCI, the DLCIs used on the interface, and the LMI DLCI used for the Local Management Interface.
show interfaces serial number
Syntax Description
Command Mode
EXEC
Usage Guidelines
The multicast DLCI and the local DLCI can be set using the frame-relay multicast-dlci and the frame-relay local-dlci commands, or provided through the Local Management Interface. The status information is taken from the LMI, when active.
Sample Displays
The following is sample output from the show interfaces serial command for a serial interface with the CISCO LMI enabled:
Router# show interface serial 1Serial1 is up, line protocol is downHardware is MCI SerialInternet address is 131.108.174.48, subnet mask is 255.255.255.0MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 246/255, load 1/255Encapsulation FRAME-RELAY, loopback not set, keepalive set (10 sec)LMI enq sent 2, LMI stat recvd 0, LMI upd recvd 0, DTE LMI downLMI enq recvd 266, LMI stat sent 264, LMI upd sent 0LMI DLCI 1023 LMI type is CISCO frame relay DTELast input 0:00:04, output 0:00:02, output hang neverLast clearing of "show interface" counters 0:44:32Output queue 0/40, 0 drops; input queue 0/75, 0 dropsFive minute input rate 0 bits/sec, 0 packets/secFive minute output rate 0 bits/sec, 0 packets/sec307 packets input, 6615 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 input packets with dribble condition detected266 packets output, 3810 bytes, 0 underruns0 output errors, 0 collisions, 2 interface resets, 0 restarts178 carrier transitionsThe display shows the statistics for the LMI as the number of status inquiry messages sent (LMI sent), the number of status messages received (LMI recvd), and the number of status updates received (upd recvd). See the Frame Relay Interface specification for additional explanations of this output.
The following is sample output from the show interfaces serial command for a serial interface with the ANSI LMI enabled:
Router# show interface serial 1Serial1 is up, line protocol is downHardware is MCI SerialInternet address is 131.108.174.48, subnet mask is 255.255.255.0MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 249/255, load 1/255Encapsulation FRAME-RELAY, loopback not set, keepalive set (10 sec)LMI enq sent 4, LMI stat recvd 0, LMI upd recvd 0, DTE LMI downLMI enq recvd 268, LMI stat sent 264, LMI upd sent 0LMI DLCI 0 LMI type is ANSI Annex D frame relay DTELast input 0:00:09, output 0:00:07, output hang neverLast clearing of "show interface" counters 0:44:57Output queue 0/40, 0 drops; input queue 0/75, 0 dropsFive minute input rate 0 bits/sec, 0 packets/secFive minute output rate 0 bits/sec, 0 packets/sec309 packets input, 6641 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 input packets with dribble condition detected268 packets output, 3836 bytes, 0 underruns0 output errors, 0 collisions, 2 interface resets, 0 restarts180 carrier transitionsEach display provides statistics and information about the type of LMI configured, either CISCO for the Cisco LMI type, ANSI for the ANSI T1.617 Annex D LMI type, or ITU-T for the ITU-T Q.933 Annex A LMI type. See the description for the show interfaces command for a description of the other fields displayed by this command.
Related Command
A dagger (†) indicates that the command is documented in another chapter.
show interfaces†
