- Cisco IOS Wide-Area Networking Command Reference, Release 12.2
Table Of Contents
frame-relay map ip tcp header-compression
frame-relay priority-dlci-group
frame-relay traps-maximum dlci-status-change
frame-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 that a Local Management Interface (LMI) has been configured, use the no form of this command.
frame-relay lmi-n391dte keep-exchanges
no frame-relay lmi-n391dte keep-exchanges
Syntax 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 from 1 through 255.
Defaults
6 keep exchanges
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command when the interface is configured as data terminal equipment (DTE) or a Network-to-Network Interface (NNI) as a means of setting the full status message polling interval.
Examples
In the following example, one out of every four status inquiries generated 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 data communications equipment (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 threshold
Syntax Description
threshold
Error threshold value. Acceptable value is a positive integer in the range from 1 through 10.
Defaults
2 errors
Command Modes
Interface configuration
Command History
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.
Examples
The following example sets the LMI failure threshold to 3. The router acts as a Frame Relay DCE or NNI switch.
interface serial 0frame-relay intf-type DCEframe-relay lmi-n392dce 3Related Commands
frame-relay lmi-n392dte
To set the error threshold on a data terminal equipment (DTE) or network-to-network interface (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 threshold
Syntax Description
threshold
Error threshold value. Acceptable value is a positive integer in the range from 1 through 10.
Defaults
3 errors
Command Modes
Interface configuration
Command History
Examples
The following example sets the Loca Management Interface (LMI) failure threshold to 3. 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 data communications equipment (DCE) and Network-to-Network Interface (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 events
Syntax Description
events
Value of monitored events count. Acceptable value is a positive integer in the range from 1 through 10.
Defaults
2 events
Command Modes
Interface configuration
Command History
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 argument 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.
Examples
The following example sets the Local Management Interface (LMI) monitored events count to 3. The router acts as a Frame Relay DCE or NNI switch.
interface serial 0frame-relay intf-type DCEframe-relay lmi-n393dce 3Related Commands
frame-relay lmi-n393dte
To set the monitored event count on a data terminal equipment (DTE) or Network-to-Network Interface (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 events
Syntax Description
events
Value of monitored events count. Acceptable value is a positive integer in the range from 1 through 10.
Defaults
4 events
Command Modes
Interface configuration
Command History
Examples
The following example sets the Local Management Interface (LMI) monitored events count to 3. 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 data communications equipment (DCE) or Network-to-Network Interface (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 seconds
no frame-relay lmi-t392dce seconds
Syntax Description
Defaults
15 seconds
Command Modes
Interface configuration
Command History
Usage Guidelines
The value for the timer must be greater than the DTE or NNI keepalive timer.
Examples
The following example indicates a polling verification timer on a DCE or NNI interface set to 20 seconds:
interface serial 3frame-relay intf-type DCEframe-relay lmi-t392dce 20Related Commands
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 American National Standards Institute (ANSI) standard T1.617.
cisco
LMI type defined jointly by Cisco and three other companies.
q933a
ITU-T Q.933 Annex A.
Defaults
LMI autosense is active and determines the LMI type by communicating with the switch.
Command Modes
Interface configuration
Command History
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.
If you want to deactivate LMI autosense, use this command and the keepalive command to configure the LMI. For more information about LMI autosense and configuring the LMI, refer to the chapter "Configuring Frame Relay" in the Cisco IOS Wide-Area Networking Configuration Guide.
Examples
The following is an example of the commands you might enter to configure an interface for the ANSI Annex D LMI type:
interface Serial1encapsulation frame-relayframe-relay lmi-type ansikeepalive 15frame-relay local-dlci
To set the source data-link connection identifier (DLCI) for use when the Local Management Interface (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-dlci
Syntax Description
Defaults
No source DLCI is set.
Command Modes
Interface configuration
Command History
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
The frame-relay local-dlci command is provided mainly to allow testing of the Frame Relay encapsulation in a setting where two servers are connected back-to-back. This command is not required in a live Frame Relay network.
Examples
The following example specifies 100 as the local DLCI:
interface serial 4frame-relay local-dlci 100frame-relay map
To define the mapping between a destination protocol address and the data-link connection identifier (DLCI) used to connect to the destination address, use the frame-relay map interface configuration command. To delete the map entry, use the no form of this command.
frame-relay map protocol protocol-address dlci [broadcast] [ietf | cisco] [payload-compress {packet-by-packet | frf9 stac [hardware-options] | data-stream stac [hardware-options]}]
no frame-relay map protocol protocol-address
Syntax Description
Defaults
No mapping is defined.
Command Modes
Interface configuration
Command History
10.0
This command was introduced.
11.3
The payload-compress frf9 stac keyword was added.
12.1(5)T
The payload-compress data-stream stac keyword was added.
Usage Guidelines
Many DLCIs can be known by a router or access server and can send data to many different places, but they are all multiplexed over one physical link. The Frame Relay map defines the logical connection between a specific protocol and address pair and the correct DLCI.
The optional ietf and cisco keywords allow flexibility in the configuration. If no keywords are specified, 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 can be configured through use of the cisco keyword with the frame-relay map command.
Data-stream compression is supported on interfaces and virtual circuits (VCs) using Cisco proprietary encapsulation. When the data-stream stac keyword is specified, Cisco encapsulation is automatically enabled. FRF.9 compression is supported on IETF-encapsulated VCs and interfaces. When the frf9 stac keyword is specified, IETF encapsulation is automatically enabled.
Packet-by-packet 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 (ietf or cisco).
Use the frame-relay map command to enable or disable payload compression on multipoint interfaces. Use the frame-relay payload-compress command to enable or disable payload compression on point-to-point interfaces.
We recommend that you shut down the interface before changing encapsulation types. Although shutting down the interface is not required, it ensures that the interface is reset for the new encapsulation.
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, selection of a designated router required manual assignment in the OSPF configuration using the neighbor interface router command. When the frame-relay map command (with the broadcast keyword) and the ip ospf network command (with the broadcast keyword) are configured, there is no need to configure any neighbors manually. OSPF will now automatically run over the Frame Relay network as a broadcast network. (See the ip ospf network interface command for more detail.)
Note
Examples
IP Address Mapping Example
The following example maps the destination IP address 172.16.123.1 to DLCI 100:
interface serial 0frame-relay map ip 172.16.123.1 100 broadcastOSPF will use DLCI 100 to broadcast updates.
FRF.9 Compression Example
The following example shows FRF.9 compression configuration using the frame-relay map command:
interface serial2/0/1ip address 172.16.1.4 255.255.255.0no ip route-cacheencapsulation frame-relay ietfno keepaliveshutdownframe-relay map ip 172.16.1.1 105 ietf payload-compress frf9 stacData-Stream Compression Example
The following example shows data-stream compression configuration using the frame-relay map command:
interface serial0/0frame-relay map ip 10.0.0.1 100 payload-compress data-stream stacRelated Commands
frame-relay map bridge
To specify that broadcasts are to be forwarded during bridging, use the frame-relay map bridge interface configuration command. To delete the map entry, use the no form of this command.
frame-relay map bridge dlci [broadcast] [ietf]
no frame-relay map bridge dlci
Syntax Description
Defaults
No broadcasts are forwarded.
Command Modes
Interface configuration
Command History
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; refer to the section "Frame Relay Configuration Examples" in the Cisco IOS Wide-Area Networking Configuration Guide for more examples of subinterfaces.
frame-relay map clns
To forward broadcasts when Connectionless Network Service (CLNS) is used for routing, use the frame-relay map clns interface configuration command. To delete the map entry, use the no form of this interface configuration command.
frame-relay map clns dlci [broadcast]
no frame-relay map clns dlci
Syntax Description
dlci
DLCI number to which CLNS broadcasts are forwarded on the specified interface.
broadcast
(Optional) Broadcasts are forwarded when multicast is not enabled.
Defaults
No broadcasts are forwarded.
Command Modes
Interface configuration
Command History
Examples
The following example uses DLCI 125 for CLNS routing:
interface serial 0frame-relay map clns 125 broadcastframe-relay map ip tcp header-compression
To assign to an IP map header compression characteristics 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.
frame-relay map ip ip-address dlci [broadcast] tcp header-compression [active | passive] [connections number]
Syntax Description
Defaults
The default maximum number of TCP header compression connections is 256.
Command Modes
Interface configuration
Command History
10.0
This command was introduced.
12.1(2)T
This command was modified to enable the configuration of the maximum number of header compression connections.
Usage Guidelines
If you do not specify the number of TCP header compression connections, the map will inherit the current value from the interface.
IP maps inherit the compression characteristics of the associated interface unless this command is used to provide different characteristics. This command can also 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 that has a compressed header.
If you change the encapsulation characteristics of the interface to Internet Engineering Task Force (IETF) encapsulation, you lose the TCP header compression configuration of the associated IP map.
The frame-relay map ip ip-address dlci tcp header-compression active command can also be entered as frame-relay map ip ip-address dlci active tcp header-compression.
We recommend that you shut down the interface before changing encapsulation types. Although shutting down the interface is not required, it ensures that the interface is reset for the new encapsulation.
Examples
The following example illustrates a command sequence for configuring an IP map associated with serial interface 1 to enable active TCP/IP header compression:
interface serial 1encapsulation frame-relayip address 10.108.177.170 255.255.255.0frame-relay map ip 10.108.177.180 190 tcp header-compression activeRelated Commands
frame-relay mincir
To specify the minimum acceptable incoming or outgoing committed information rate (CIR) for a Frame Relay virtual circuit, use the frame-relay mincir map-class configuration command. To reset the minimum acceptable CIR to the default, use the no form of this command.
frame-relay mincir {in | out} bps
no frame-relay mincir
Syntax Description
Defaults
56000 bps
Command Modes
Map-class configuration
Command History
Usage Guidelines
Rate values greater than 2048 must be entered with trailing zeros. For example, 2048000 and 5120000.
The network uses the mincir value when allocating resources for the SVC. If the mincir value cannot be supported, the call is cleared.
Examples
The following example defines the peak and average traffic rate, the minimum CIR, and the idle timer for the fast_vcs map class and applies those values to DLCI 100, which is associated with that map class:
interface serial 0frame-relay interface-dlci 100class fast_vcmap-class frame-relay fast_vcframe-relay traffic-rate 56000 128000frame-relay idle-timer 30frame-relay mincir out 48000Related Commands
frame-relay multicast-dlci
To define the data-link connection identifier (DLCI) to be used for multicasts, use the frame-relay multicast-dlci interface configuration command. To remove the multicast group, use the no form of this command.
frame-relay multicast-dlci number
no frame-relay multicast-dlci
Syntax Description
Defaults
No DLCI is defined.
Command Modes
Interface configuration
Command History
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
Examples
The following example specifies 1022 as the multicast DLCI:
interface serial 0frame-relay multicast-dlci 1022frame-relay payload-compress
To enable Stacker payload compression on a specified point-to-point interface or subinterface, use the frame-relay payload-compress 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 | frf9 stac [hardware-options] | data-stream stac [hardware-options]}
no frame-relay payload-compress {packet-by-packet | frf9 stac | data-stream stac}
Syntax Description
packet-by-packet
Packet-by-packet payload compression using the Stacker method.
frf9 stac
Enables FRF.9 compression using the Stacker method.
•
•
•
hardware-options
Choose one of the following hardware options:
•
•
•
data-stream stac
Enables data-stream compression using the Stacker method.
•
•
1 CSA = compression service adapter
2 VIP2 = second-generation Versatile Interface Processor
Defaults
Disabled
Command Modes
Interface configuration
Command History
11.0
This command was introduced.
11.2
The packet-by-packet keyword was added.
11.3
The frf9 stac keyword was added.
12.1(5)T
The data-stream stac keyword was added.
Usage Guidelines
Use the frame-relay payload-compress 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.
We recommend that you shut down the interface before changing encapsulation types. Although shutting down the interface is not required, it ensures that the interface is reset for the new encapsulation.
Data-stream hardware compression is supported on interfaces and virtual circuits (VCs) using Cisco proprietary encapsulation. When the data-stream stac keyword is specified, Cisco encapsulation is automatically enabled. FRF.9 compression is supported on VCs and interfaces that using Internet Engineering Task Force (IETF) encapsulation type. When the frf9 stac keyword is specified, IETF encapsulation is automatically enabled.
Examples
FRF.9 Compression Example
The following example configures FRF.9 compression for subinterfaces:
interface serial2/0/0no ip addressno ip route-cacheencapsulation frame-relayip route-cache distributedno keepaliveshutdown!interface serial2/0/0.500 point-to-pointip address 172.16.1.4 255.255.255.0no cdp enableframe-relay interface-dlci 500 ietfframe-relay payload-compress frf9 stacData-Stream Compression Example
The following example shows the configuration of data-stream compression using the frame-relay payload-compress command:
interface serial1/0encapsulation frame-relayframe-relay traffic-shaping!interface serial1/0.1 point-to-pointip address 10.0.0.1 255.0.0.0frame-relay interface-dlci 100frame-relay payload-compress data-stream stacRelated Commands
Defines mapping between a destination protocol address and the DLCI used to connect to the destination address.
frame-relay policing
To enable Frame Relay policing on all switched PVCs on the interface, use the frame-relay policing interface configuration command. To disable Frame Relay policing, use the no form of this command.
frame-relay policing
no frame-relay policing
Syntax Description
This command has no arguments or keywords.
Defaults
Frame Relay policing is not enabled on switched PVCs.
Command Modes
Interface configuration
Command History
Usage Guidelines
You must enable Frame Relay policing on the incoming interface before you can configure traffic-policing parameters.
You must enable Frame Relay switching, using the frame-relay switching global command, before the frame-relay policing command will be effective on switched PVCs.
Examples
The following example shows the configuration of Frame Relay policing on serial interface 0:
interface serial0frame-relay policingRelated Commands
frame-relay priority-dlci-group
To prioritize multiple data-link connection identifiers (DLCIs) according to the type of Frame Relay traffic, use the frame-relay priority-dlci-group interface configuration command.
frame-relay priority-dlci-group group-number high-dlci medium-dlci normal-dlci low-dlci
Syntax Description
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is applied at the interface or subinterface level. Levels in descending order are high, medium, normal, and low.
This command allows you to define different DLCIs for different categories of traffic based on traffic priorities. This command does not itself define priority queueing, but it can be used in conjunction with priority queueing.
A global priority list must be defined, and the associated DLCIs must already be applied to the configuration before you enable this command.
Associate the DLCIs to their prospective groups and define their priority levels. This command is used for multiple DLCIs, where the source and destination endpoints are the same (parallel paths). This command should not be used on a main interface, or point-to-point subinterface, where only a single DLCI is configured.
A DLCI can only be affiliated with a single priority-group; however, there can be multiple groups per interface or subinterface.
You must configure the high-priority and medium-priority DLCI values. If you do not explicitly associate a DLCI for the normal-dlci and low-dlci priority 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 static map entries using frame-relay map commands or use Inverse Address Resolution Protocol (ARP), the high-level DLCI is the only DLCI that is mapped. In the example, DLCI 40 is defined as having the highest priority. Therefore, DLCI 40 is the only DLCI that should be included in the frame-relay map command. DLCI 50 should not be included in a frame-relay map command.
Examples
The following example shows the frame-relay priority-dlci-group command configured on a main interface with a static Frame Relay map entry. Note that DLCI 40 is the high-priority DLCI as defined in the frame-relay priority-dlci-group command and the only DLCI included in the frame-relay map command.
interface serial 1ip address 172.21.177.1 255.255.255.0encapsulation frame-relayframe-relay priority-dlci-group 1 40frame-relay map ip 172.21.177.2 40 broadcastThe following example shows the frame-relay priority-dlci-group command configured on subinterfaces where multiple priority groups are defined. DLCI 40 is the high-priority DLCI in group 1, and DLCI 80 is the high-priority DLCI in group 2.
interface Serial3no ip addressencapsulation frame-relay!interface Serial3.2 multipointip address 172.21.177.1 255.255.255.0frame-relay interface-dlci 40frame-relay priority-dlci-group 1 40!interface Serial3.3 multipointip address 131.108.177.180 255.255.255.0frame-relay priority-dlci-group 2 80 90 100 100frame-relay interface-dlci 80!interface Serial 4no ip addressencapsulation frame-relay!interface serial4.1 multipointip address 172.16.1.1 255.255.255.0frame-relay priority-dlci-group 3 200 210 300 300frame-relay priority-dlci-group 4 400 410 410 410frame-relay interface-dlci 200frame-relay interface-dlci 400Related Commands
Defines mapping between a destination protocol address and the DLCI used to connect to the destination address.
frame-relay priority-group
To assign a priority queue to virtual circuits associated with a map class, use the frame-relay priority-group 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 priority-group list-number
no frame-relay priority-group list-number
Syntax Description
Defaults
If this command is not entered, the default is first-come, first-served queueing.
Command Modes
Map-class configuration
Command History
Usage Guidelines
Definition of the priority queue takes place in the existing manner (through priority-list commands). Because only one form of queueing can be associated with a particular map class, subsequent definitions overwrite previous ones.
Examples
The following example configures a map class for a specified DLCI, specifies a priority list for the map class, and then defines the priority list:
interface serial 0encapsulation frame-relayframe-relay interface-dlci 100class pri_vcmap-class frame-relay pri_vcframe-relay priority-group 1priority-list 1 protocol ip highRelated Commands
frame-relay pvc
To configure Frame Relay permanent virtual circuits (PVCs) for FRF.8 Frame Relay-ATM Service Interworking, use the frame-relay pvc interface configuration command. To remove the PVC, use the no form of the command.
frame-relay pvc dlci service {transparent | translation} [clp-bit {0 | 1 | map-de}][de-bit
{0 | 1 | map-clp}][efci-bit {0 | 1 | map-fecn}] interface atm0 {vpi/vci | vcd}no frame-relay pvc dlci service {transparent | translation} [clp-bit {0 | 1 | map-de}][de-bit
{0 | 1 | map-clp}][efci-bit {0 | 1 | map-fecn}] interface atm0 {vpi/vci | vcd}Syntax Description
