-
Cisco IOS Wide-Area Networking Command Reference
-
Introduction
-
A through C
-
D through E
-
fdl through frame-relay lapf n200
-
frame-relay lapf n201 through fr-atm connect dlci
-
H through L
-
M through R
-
sequencing through show mpls l2transport vc
-
show smds addresses through vpls-id
-
x25 accept-reverse through x25 pvc (XOT)
-
x25 pvc rbp local through xot access-group
-
Table Of Contents
frame-relay map ip tcp header-compression
frame-relay multilink bandwidth-class
frame-relay multilink output-threshold
frame-relay payload-compression
frame-relay priority-dlci-group
frame-relay traps-maximum dlci-status-change
frame-relay lapf n201
To set the Link Access Procedure for Frame Relay (LAPF) N201 value (the maximum length of the Information field of the LAPF I frame), use the frame-relay lapf n201 command in interface configuration mode. To reset the maximum length of the Information field to the default of 260 bytes (octets), use the no form of this command.
frame-relay lapf n201 bytes
no frame-relay lapf n201 [bytes]
Syntax Description
bytes
Maximum number of bytes in the Information field of the LAPF I frame. Range is from 1 to 16384. Default is 260.
Defaults
260 bytes
Command Modes
Interface configuration
Command History
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 N201 maximum information field length to the default value:
no frame-relay lapf n201frame-relay lapf t200
To set the Link Access Procedure for Frame Relay (LAPF) retransmission timer value T200, use the frame-relay lapf t200 command in interface configuration mode. To reset the T200 timer to the default value of 15, use the no form of this command.
frame-relay lapf t200 tenths-of-a-second
no frame-relay lapf t200
Syntax Description
Defaults
15 tenths of a second (1.5 seconds)
Command Modes
Interface configuration
Command History
Usage Guidelines
The retransmission timer value T200 should be less than the link idle timer value T203 (using the same time unit).
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 T200 timer to the default value:
no frame-relay lapf t200Related Commands
frame-relay lapf t203
To set the Link Access Procedure for Frame Relay (LAPF) link idle timer value T203 of data-link connection identifier (DLCI) 0, use the frame-relay lapf t203 command in interface configuration mode. To reset the link idle timer to the default value, use the no form of this command.
frame-relay lapf t203 seconds
no frame-relay lapf t203
Syntax Description
seconds
Maximum time allowed with no frames exchanged. Range is from 1 to 65535 seconds. Default is 30.
Defaults
30 seconds
Command Modes
Interface configuration
Command History
Usage Guidelines
The frame-relay lapf t203 command applies to the link; that is, it applies to DLCI 0. Circuits other than DLCI 0 are not affected.
The link idle timer value T203 should be greater than the retransmission timer value T200 (using the same time unit).
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 T203 idle link timer to the default value:
no frame-relay lapf t203frame-relay lmi-n391dte
To set a full status polling interval, use the frame-relay lmi-n391dte command in interface configuration mode. 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 to 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 DCE and the Network-to-Network Interface (NNI) error threshold, use the frame-relay lmi-n392dce command in interface configuration mode. 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
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 DTE or network-to-network interface (NNI) interface, use the frame-relay lmi-n392dte command in interface configuration mode. 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
Defaults
3 errors
Command Modes
Interface configuration
Command History
Examples
The following example sets the Local 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 DCE and Network-to-Network Interface (NNI) monitored events count, use the frame-relay lmi-n393dce command in interface configuration mode. 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 to 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 DTE or Network-to-Network Interface (NNI) interface, use the frame-relay lmi-n393dte command ininterface configuration mode. 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 to 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 DCE or Network-to-Network Interface (NNI) interface, use the frame-relay lmi-t392dce command in interface configuration mode. 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
keepalive (LMI)
Enables the LMI mechanism for serial lines using Frame Relay encapsulation.
frame-relay lmi-type
To select the Local Management Interface (LMI) type, use the frame-relay lmi-type command in interface configuration mode. 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 command in interface configuration mode. 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) or Frame Relay permanent virtual circuit (PVC) bundle that connects to the destination address, use the frame-relay map command in interface configuration mode. To delete the map entry, use the no form of this command.
frame-relay map protocol protocol-address {dlci | vc-bundle vc-bundle-name}[broadcast] [ietf | cisco] [payload-compression {packet-by-packet | frf9 stac [one-way-negotiation] [ratio level] [skip-zero-sync] [software | hardware-options] | data-stream stac [one-way-negotiation] [ratio level] [software | hardware-options]}]
no frame-relay map protocol protocol-address
Syntax Description
protocol
One of the following values: appletalk, decnet, dlsw, ip, ipx, llc2, and rsrb.
protocol-address
Destination protocol address.
dlci
DLCI number used to connect to the specified protocol address on the interface. Acceptable numbers are integers from 16 through 1007, inclusive.
vc-bundle vc-bundle-name
A specific Frame Relay PVC bundle configured on the interface.
broadcast
(Optional) Forwards broadcasts to this address when multicast is not enabled (see the frame-relay multicast-dlci command for more information about multicasts). This keyword also simplifies the configuration of Open Shortest Path First (OSPF) (see the "Usage Guidelines" section for more detail).
ietf
(Optional) Internet Engineering Task Force (IETF) form of Frame Relay encapsulation, based on RFC 1490 and RFC 2427. Used when the router or access server is connected to another vendor's equipment across a Frame Relay network.
cisco
(Optional) Cisco-proprietary encapsulation method consisting of a four-byte header, with two bytes to identify the DLCI and two bytes to identify the packet type.
payload-compression
(Optional) Enables payload compression.
packet-by-packet
(Optional)Packet-by-packet payload compression using the Stacker method.
frf9 stac
(Optional)Enables FRF.9 compression using the Stacker method.
•
•
•
one-way-negotiation
(Optional) Enables one-way negotiation. Use this keyword if your router will be negotiating compression with another device that is running Cisco IOS Release 12.1(9) or earlier releases. Later Cisco IOS releases use a two-way handshake by default to negotiate compression.
ratio level
(Optional) Sets throughput versus compression ratio. This option is available only with hardware compression. Possible values for the level argument are as follows:
high—high compression versus low throughput
medium—medium compression versus medium throughput
low—low compression versus high throughput (default)
software
(Optional) Specifies that compression is implemented in the Cisco IOS software installed in the main processor of the router.
hardware-options
(Optional) Choose one of the following hardware options:
caim element-number—Enables the CAIM3 to perform compression.
distributed—Specifies that compression is implemented in the software that is installed in a VIP2. If the VIP2 is not available, compression is performed in the main processor of the router (software compression). This option applies only to the Cisco 7500 series routers. This option is not supported with data-stream compression.
csa csa_number—Specifies the CSA to use for a particular interface. This option applies only to Cisco 7200 series routers.
skip-zero-sync
(Optional) Causes compression frames to be numbered starting from 1 rather than 0. Use this keyword if your router will be interoperating with a device conforming to IBM partner conventions.
data-stream stac
(Optional) Enables data-stream compression using the Stacker method.
•
•
1 CSA = compression service adapter
2 VIP2 = second-generation Versatile Interface Processor
3 CAIM = compression Advanced Interface Module
Defaults
No mapping is defined.
Command Modes
Interface configuration
Command History
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 or PVC bundle.
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, for example, that 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-compression 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 may 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. 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 run automatically over the Frame Relay network as a broadcast network. (See the ip ospf network interface command for more detail.)
Note
Examples
IP Address to DLCI 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.
IP Address to Frame Relay PVC Bundle Mapping: Example
The following example maps the destination IP address 172.16.123.1 to the Frame Relay PVC bundle named "MAIN-1":
interface serial 0frame-relay map ip 172.16.123.1 vc-bundle MAIN-1 broadcastFRF.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-compression 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-compression data-stream stacRelated Commands
frame-relay map bridge
To specify that broadcasts are to be forwarded during bridging, use the frame-relay map bridge command in interface configuration mode. 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 command in interface configuration mode. To delete the map entry, use the no form of this 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 command in interface configuration mode.
frame-relay map ip ip-address dlci [broadcast] tcp header-compression [active | passive] [connections number]
Syntax Description
Defaults
Maximum number of TCP header compression connections: 256
Command Modes
Interface configuration
Command History
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 command in map-class configuration mode. 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 command in interface configuration mode. 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 multilink ack
To configure the number of seconds for which a bundle link will wait for a hello message acknowledgment before resending the hello message, use the frame-relay multilink ack command in interface configuration mode. To reset this parameter to the default setting, use the no form of this command.
frame-relay multilink ack seconds
no frame-relay multilink ack
Syntax Description
seconds
Number of seconds for which a bundle link will wait for a hello message acknowledgment before resending the hello message. Range: 1 to 10. Default: 4.
Command Default
The default acknowledgement interval is 4 seconds.
Command Modes
Interface configuration
Command History
Usage Guidelines
The frame-relay multilink ack command can be configured only on bundle link interfaces that have been associated with a bundle using the encapsulation frame-relay mfr command.
Both ends of a bundle link send out hello messages at regular intervals. When a peer device receives a hello message, it responds by sending an acknowledgment. This exchange of hello messages and acknowledgments serves as a keepalive mechanism for the link. If the bundle link sends a hello message but does not receive an acknowledgment, it will resend the hello message up to a configured maximum number of times. If the bundle link exhausts the maximum number of retries, the bundle link line protocol is considered down (nonoperational).
The frame-relay multilink ack command setting on the local router is independent of the setting on the peer device.
Examples
The following example shows how to configure the bundle link to wait 6 seconds before resending hello messages:
interface serial0encapsulation frame-relay mfr0frame-relay multilink ack 6Related Commands
frame-relay multilink bandwidth-class
To specify the criterion used to activate or deactivate a Frame Relay bundle, use the frame-relay multilink bandwidth-class command in interface configuration mode. To reset the bandwidth class to the default, use the no form of this command.
frame-relay multilink bandwidth-class [a | b | c [threshold]]
no frame-relay multilink bandwidth-class
Syntax Description
