Table Of Contents

frame-relay local-dlci

frame-relay map

frame-relay map bridge

frame-relay map clns

frame-relay map ip tcp header-compression

frame-relay mincir

frame-relay multicast-dlci

frame-relay multilink ack

frame-relay multilink bid

frame-relay multilink hello

frame-relay multilink lid

frame-relay multilink output-threshold

frame-relay multilink retry

frame-relay payload-compression

frame-relay policing

frame-relay priority-dlci-group

frame-relay priority-group

frame-relay pvc

frame-relay qos-autosense

frame-relay route

frame-relay svc

frame-relay switching

frame-relay tc

frame-relay traffic-rate

frame-relay traffic-shaping

frame-relay traps-maximum dlci-status-change

frame-relay vc-bundle

framer-type

fr-atm connect dlci

frame-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

number

Local (source) DLCI number to be used.

Defaults

No source DLCI is set.

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.

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 4

 frame-relay local-dlci 100

frame-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. •If the router contains a CSA1 , compression is performed in the CSA hardware (hardware compression). •If the CSA is not available, compression is performed in the software installed on the VIP22 (distributed compression). •If the VIP2 is not available, compression is performed in the main processor of the router (software compression).
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. •If the router contains a CSA, compression is performed in the CSA hardware (hardware compression). •If the CSA is not available, compression is performed in the main processor of the router (software compression).

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

Release	Modification
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.
12.2(4)T	The skip-zero-sync keyword was added.
12.2(13)T	The vc-bundle vc-bundle-name keyword and argument pair was added. The apollo, vines, and xns arguments were removed because Apollo Domain, Banyan VINES, and Xerox Network Systems are no longer available in the Cisco IOS software. The one-way-negotiation 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 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 The OSPF broadcast mechanism assumes that IP class D addresses are never used for regular traffic over Frame Relay.

---

Examples

IP Address to DLCI Mapping Example

The following example maps the destination IP address 172.16.123.1 to DLCI 100:

interface serial 0

 frame-relay map ip 172.16.123.1 100 broadcast

OSPF 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 0

 frame-relay map ip 172.16.123.1 vc-bundle MAIN-1 broadcast

FRF.9 Compression Example

The following example shows FRF.9 compression configuration using the frame-relay map command:

interface serial2/0/1

 ip address 172.16.1.4 255.255.255.0

 no ip route-cache

 encapsulation frame-relay ietf

 no keepalive

 shutdown

 frame-relay map ip 172.16.1.1 105 ietf payload-compression frf9 stac

Data-Stream Compression Example

The following example shows data-stream compression configuration using the frame-relay map command:

interface serial0/0

 frame-relay map ip 10.0.0.1 100 payload-compression data-stream stac

Related Commands

Command	Description
encapsulation frame-relay	Enables Frame Relay encapsulation on an interface.
frame-relay payload-compression	Enables Stacker payload compression on a specified point-to-point interface or subinterface.
frame-relay vc-bundle	Creates a Frame Relay PVC bundle and enters Frame Relay VC-bundle configuration mode.
ip ospf network	Configures the OSPF network type to a type other than the default for a given medium.

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

dlci	DLCI number to be used for bridging on the specified interface or subinterface.
broadcast	(Optional) Broadcasts are forwarded when multicast is not enabled.
ietf	(Optional) IETF form of Frame Relay encapsulation. Use when the router or access server is connected to another vendor's equipment across a Frame Relay network.

Defaults

No broadcasts are forwarded.

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.

Examples

The following example uses DLCI 144 for bridging:

interface serial 0

 frame-relay map bridge 144 broadcast

The following example sets up separate point-to-point links over a subinterface and runs transparent bridging over it:

interface serial 0

 bridge-group 1

 encapsulation frame-relay

interface serial 0.1

 bridge-group 1

 frame-relay map bridge 42 broadcast

interface serial 0.2

 bridge-group 1

 frame-relay map bridge 64 broadcast

interface serial 0.3

 bridge-group 1

 frame-relay map bridge 73 broadcast

DLCI 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

Release	Modification
10.0	This command was introduced.

Examples

The following example uses DLCI 125 for CLNS routing:

interface serial 0

 frame-relay map clns 125 broadcast

frame-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

ip-address	IP address of the destination or next hop.
dlci	Data-link connection identifier (DLCI) number.
broadcast	(Optional) Forwards broadcasts to the specified IP address.
active	(Optional) Compresses the header of every outgoing TCP/IP packet.
passive	(Optional) Compresses the header of an outgoing TCP/IP packet only if an incoming TCP/IP packet had a compressed header.
connections number	(Optional) Specifies the maximum number of TCP header compression connections. The range is from 3 to 256. Default is 256.

Defaults

Maximum number of TCP header compression connections: 256

Command Modes

Interface configuration

Command History

Release	Modification
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 1

 encapsulation frame-relay

 ip address 10.108.177.170 255.255.255.0

 frame-relay map ip 10.108.177.180 190 tcp header-compression active

Related Commands

Command	Description
frame-relay ip tcp compression-connections	Specifies the maximum number of TCP header compression connections that can exist on a Frame Relay interface.
frame-relay ip tcp header-compression	Enables TCP header compression for all Frame Relay maps on a physical interface.
frame-relay map ip compress	Enables both RTP and TCP header compression on a link.
show frame-relay ip tcp header-compression	Displays statistics and TCP/IP header compression information for the interface.

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

in | out	Incoming or outgoing.
bps	Committed information rate, in bits per second.

Defaults

56000 bps

Command Modes

Map-class configuration

Command History

Release	Modification
11.2	This command was introduced.

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 0

 frame-relay interface-dlci 100

  class fast_vc

map-class frame-relay fast_vc

 frame-relay traffic-rate 56000 128000

 frame-relay idle-timer 30

 frame-relay mincir out 48000 

Related Commands

Command	Description
map-class frame-relay	Specifies a map class to define QoS values for an SVC.

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

number

Multicast DLCI.

Defaults

No DLCI is defined.

Command Modes

Interface configuration

Command History

Release	Modification
10.0	This command was introduced.

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 The frame-relay multicast-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 1022 as the multicast DLCI:

interface serial 0

 frame-relay multicast-dlci 1022

frame-relay multilink ack

To configure the number of seconds that 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 that a bundle link will wait for a hello message acknowledgment before resending the hello message. The range is from 1 to 10 seconds. Default is 4.

Defaults

4 seconds

Command Modes

Interface configuration

Command History

Release	Modification
12.0(17)S	This command was introduced.
12.2(8)T	This command was integrated into Cisco IOS Release 12.2(8)T.

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 serve 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 (unoperational).

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 serial0

 encapsulation frame-relay mfr0

 frame-relay multilink ack 6

Related Commands

Command	Description
encapsulation frame-relay mfr	Creates a multilink Frame Relay bundle link and associates the link with a bundle.
frame-relay multilink hello	Configures the interval at which a bundle link will send out hello messages.
frame-relay multilink retry	Configures the maximum number of times that a bundle link will resend a hello message while waiting for an acknowledgment.

frame-relay multilink bid

To assign a bundle identification (BID) name to a multilink Frame Relay bundle, use the frame-relay multilink bid command in interface configuration mode. To reset the name to the default, use the no form of this command.

frame-relay multilink bid name

no frame-relay multilink bid

Syntax Description

name	Bundle identification name. Maximum length is 49 characters.

Defaults

The default BID is "mfr" plus the number assigned to the bundle using the interface mfr command; for example, "mfr0".

Command Modes

Interface configuration

Command History

Release	Modification
12.0(17)S	This command was introduced.
12.2(8)T	This command was integrated into Cisco IOS Release 12.2(8)T.

Usage Guidelines

This command can be entered only at the multilink Frame Relay bundle interface.

---

Note You can enter the frame-relay multilink bid command at any time without affecting the current state of the interface; however, the BID will not go into effect until the interface has gone from the down state to the up state. One way to bring the interface down and back up again is by using the shut and no shut commands in interface configuration mode.

---

Only one BID is allowed per bundle. A later entry of the frame-relay multilink bid command supersedes prior entries.

The local and peer BIDs do not have to be unique.

Examples

The following example shows how to assign a BID of "bundle1" to the multilink Frame Relay bundle. The previous BID for the bundle was "mfr0".

interface mfr0

 frame-relay multilink bid bundle1

Related Commands

Command	Description
frame-relay multilink lid	Assigns a LID name to a multilink Frame Relay bundle link.
interface mfr	Configures a multilink Frame Relay bundle interface.
show frame-relay multilink	Displays configuration information and statistics about multilink Frame Relay bundles and bundle links.

frame-relay multilink hello

To configure the interval at which a bundle link will send out hello messages, use the frame-relay multilink hello command in interface configuration mode. To reset this value to the default setting, use the no form of this command.

frame-relay multilink hello seconds

no frame-relay multilink hello

Syntax Description

seconds

Interval, in seconds, at which a bundle link will send out hello messages. The range is from 1 to 180.

Defaults

10 seconds

Command Modes

Interface configuration

Command History

Release	Modification
12.0(17)S	This command was introduced.
12.2(8)T	This command was integrated into Cisco IOS Release 12.2(8)T.

Usage Guidelines

The frame-relay multilink hello 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 (unoperational).

The setting of the hello message interval on the local router is independent of the setting on the peer device.

Examples

The following example shows how to configure a bundle link to send hello messages every 15 seconds:

interface serial0

 encapsulation frame-relay mfr0

 frame-relay multilink hello 15

Related Commands

Command	Description
encapsulation frame-relay mfr	Creates a multilink Frame Relay bundle link and associates the link with a bundle.
frame-relay multilink ack	Configures the number of seconds that a bundle link will wait for a hello message acknowledgment before resending the hello message.
frame-relay multilink retry	Configures the maximum number of times that a bundle link will resend a hello message while waiting for an acknowledgment.

frame-relay multilink lid

To assign a bundle link identification (LID) name to a multilink Frame Relay bundle link, use the frame-relay multilink lid command in interface configuration mode. To reset the name to the default, use the no form of this command.

frame-relay multilink lid name

no frame-relay multilink lid

Syntax Description

name	Bundle link identification name. Maximum length is 49 characters.

Defaults

The default LID is the name of the physical interface.

Command Modes

Interface configuration

Command History

Release	Modification
12.0(17)S	This command was introduced.
12.2(8)T	This command was integrated into Cisco IOS Release 12.2(8)T.

Usage Guidelines

The frame-relay multilink lid command can be configured only on bundle link interfaces that have been associated with a bundle using the encapsulation frame-relay command with the mfr keyword.

---

Note You can enter the frame-relay multilink lid command at any time without affecting the current state of the interface; however, the LID will not go into effect until the interface has gone from the down state to the up state. One way to bring the interface down and back up again is by using the shut and no shut commands in interface configuration mode.

---

The LID will be used to identify the bundle link to peer devices and to enable the devices to identify which bundle links are associated with which bundles. The LID can also be assigned when the bundle link is created by using the encapsulation frame-relay command with the name argument. If the LID is not assigned, the default LID is the name of the physical interface.

The local and peer LIDs do not need to be unique.

Examples

The following example shows the LID "BL1" assigned to serial interface 0:

interface serial 0

 encapsulation frame-relay mfr0

 frame-relay multilink lid BL1

Related Commands

Command	Description
encapsulation frame-relay mfr	Creates a multilink Frame Relay bundle link and associates the link with a bundle.
frame-relay multilink bid	Assigns a BID name to a multilink Frame Relay bundle.
show frame-relay multilink	Displays configuration information and statistics about multilink Frame Relay bundles and bundle links.

frame-relay multilink output-threshold

To configure the number of bytes that a bundle link will transmit before the load-balancing mechanism causes transmission to roll over to the next available link, use the frame-relay multilink output-threshold command in interface configuration mode. To reset this value to the default setting, use the no form of this command.

frame-relay multilink output-threshold bytes

no frame-relay multilink output-threshold

Syntax Description

bytes

Number of bytes that a bundle link will transmit before the load-balancing mechanism causes transmission to roll over to the next link. The range is from 20 to 2147483647. The default is 300.

Defaults

300 bytes

Command Modes

Interface configuration

Command History

Release	Modification
12.2(8)T	This command was introduced.

Usage Guidelines

Multilink Frame Relay enables load balancing across bundle links that are in the same bundle. When a bundle link has reached its output threshold, transmission rolls over to the next available bundle link in the bundle.

The output threshold mechanism applies only when the bundle interface is using FIFO output queueing. When the bundle interface is not using FIFO output queuing, the algorithm for choosing a bundle link interface for output selects the bundle link with the empty or shortest output queue.

The default output threshold is 300 bytes. This default value will work effectively if all the bundle links in the bundle have the same speed. To efficiently use bundle links with varied speeds, use the frame-relay multilink output-threshold command to adjust the output threshold of the links as appropriate.

The frame-relay multilink output-threshold command can be used on the bundle interface and the bundle links. If the command is used on the bundle interface, the configured output threshold will apply to all bundle links in the bundle. If the command is used on a specific bundle link, the output threshold will overwrite the current setting for that bundle link.

Examples

The following example shows how to configure the bundle link output threshold at 600 bytes. When the bundle link reaches the threshold, transmission will roll over to the next link.

interface serial0

 encapsulation frame-relay mfr0

 frame-relay multilink output-threshold 600

Related Commands

Command	Description
encapsulation frame-relay mfr	Creates a multilink Frame Relay bundle link and associates the link with a bundle.

frame-relay multilink retry

To configure the maximum number of times a bundle link will resend a hello message while waiting for an acknowledgment, use the frame-relay multilink retry command in interface configuration mode. To reset this value to the default setting, use the no form of this command.

frame-relay multilink retry number

no frame-relay multilink retry

Syntax Description

number

Maximum number of times a bundle link will resend a hello message while waiting for an acknowledgment. The range is from 1 to 5.

Defaults

Number of retries: 2

Command Modes

Interface configuration

Command History

Release	Modification
12.0(17)S	This command was introduced.
12.2(8)T	This command was integrated into Cisco IOS Release 12.2(8)T.

Usage Guidelines

The frame-relay multilink retry command can be configured only on bundle link interfaces that have been associated with a bundle using the encapsulation frame-relay command with the mfr keyword.

If the bundle link sends the maximum number of hello messages without receiving an acknowledgment, the bundle link line protocol is considered down (unoperational).

The maximum number of retries configured on the local router is independent of the maximum number configured on the peer device.

Examples

The following example shows how to configure a bundle link to resend a hello message a maximum of 3 times while waiting for an acknowledgment:

interface serial0

 encapsulation frame-relay mfr0

 frame-relay multilink retry 3

Related Commands

Command	Description
encapsulation frame-relay mfr	Creates a multilink Frame Relay bundle link and associates the link with a bundle.
frame-relay multilink ack	Configures the number of seconds that a bundle link will wait for a hello message acknowledgment before resending the hello message.
frame-relay multilink hello	Configures the interval at which a bundle link will send out hello messages.

frame-relay payload-compression

To enable Stacker payload compression on a specified point-to-point interface or subinterface, use the frame-relay payload-compression command in interface configuration mode. To disable payload compression on a specified point-to-point interface or subinterface, use the no form of this command.

frame-relay 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 payload-compression {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. •If the router contains a CSA1 , compression is performed in the CSA hardware (hardware compression). •If the CSA is not available, compression is performed in the software installed on the VIP22 (distributed compression). •If the VIP2 is not available, compression is performed in the main processor of the router (software compression).
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)
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 that conforms to IBM partner conventions.
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.
data-stream stac	Enables data-stream compression using the Stacker method. •If the router contains a CSA, compression is performed in the CSA hardware (hardware compression). •If the CSA is not available, compression is performed in the main processor of the router (software compression).

1 CSA = compression service adapter 2 VIP2 = second-generation Versatile Interface Processor 3 CAIM = Compression Advanced Interface Module

Defaults

Payload compression is not enabled.

Command Modes

Interface configuration

Command History

Release	Modification
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.
12.2(4)T	The skip-zero-sync keyword was added.
12.2(13)T	The one-way-negotiation keyword was added.

Usage Guidelines

Use the frame-relay payload-compression 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/0

 no ip address

 no ip route-cache

 encapsulation frame-relay

 ip route-cache distributed

 no keepalive

 shutdown

!

interface serial2/0/0.500 point-to-point

 ip address 172.16.1.4 255.255.255.0

 no cdp enable

 frame-relay interface-dlci 500 ietf 

 frame-relay payload-compression frf9 stac

Data-Stream Compression Example

The following example shows the configuration of data-stream compression using the frame-relay payload-compression command:

 interface serial1/0

  encapsulation frame-relay

  frame-relay traffic-shaping

 !

 interface serial1/0.1 point-to-point

  ip address 10.0.0.1 255.0.0.0

  frame-relay interface-dlci 100

  frame-relay payload-compression data-stream stac 

Related Commands

Command	Description
frame-relay map	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 command in interface configuration mode. 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

Release	Modification
12.1(2)T	This command was introduced.

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 serial0

 frame-relay policing

Related Commands

Command	Description
frame-relay bc	Specifies the incoming or outgoing Bc for a Frame Relay virtual circuit.
frame-relay be	Specifies the incoming or outgoing Be for a Frame Relay virtual circuit.
frame-relay cir	Specifies the incoming or outgoing CIR for a Frame Relay virtual circuit.
frame-relay switching	Enables PVC switching on a Frame Relay DCE or NNI.
frame-relay tc	Specifies the measurement interval for policing incoming traffic when the CIR is zero.

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

group-number	Specific group number.
high-dlci	DLCI that is to have highest priority level.
medium-dlci	DLCI that is to have medium priority level.
normal-dlci	DLCI that is to have normal priority level.
low-dlci	DLCI that is to have lowest priority level.

Defaults

Disabled

Command Modes

Interface configuration

Command History

Release	Modification
11.0	This command was introduced.

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 50

frame-relay priority-dlci-group 1 40 50 50 50 

When 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 4