Cisco IOS Wide-Area Networking Command Reference

fdl

To set the Facility Data Link (FDL) exchange standard for CSU controllers or to set the FDL exchange standard for a T1 interface that uses the Extended Super Frame (ESF) framing format, use the fdl command in interface configuration mode. To disable FDL support or to specify that there is no ESF FDL, use the no form of this command.

Cisco 2600 Series and Cisco 3600 Series Routers

fdl {att | ansi | all | none}

no fdl {att | ansi | all | none}

Cisco 10000 Series Router

fdl {att | ansi}

no fdl {att | ansi}

Syntax Description

Defaults

ANSI T1.403 for ESF FDL exchange support

Command Modes

Interface configuration

Command History

Usage Guidelines

This command is available only for T1 links. This command sets the standard to be followed for FDL messaging through a 4-kbps out-of-band channel that a service provider uses to check for errors on the facility.

You must use the same FDL exchange standard as your service provider. If the setting is not correct, the link might not come up. You can configure a different standard on each T1 interface.

Note When using a multiport T1 ATM IMA network module on a Cisco 2600 series or Cisco 3600 series
router, ESF framing and binary eight zero substitution (B8ZS) line encoding are supported. When
using a multiport E1 ATM IMA network module on a Cisco 2600 series or Cisco 3600 series router,
CRC4 multiframe framing and HDB3 line encoding are supported. These are the parameters
specified by the ATM Forum, and they cannot be changed.

Examples

Cisco 2600 and Cisco 3600 Series Routers

The following example shows how to specify the ANSI standard and the AT&T standard for FDL exchange:

Router(config)# interface atm 0/2

Router(config-if)# fdl all

Cisco 10000 Series Router

The following example shows how to specify the AT&T standard for FDL exchange:

Router(config)# interface atm 1/0/0

Router(config-if)# fdl att 

flow monitor type mace

To configure a Flexible NetFlow (FNF) flow monitor of type MACE and to enter Flexible NetFlow flow monitor configuration mode, use the flow monitor type mace command in global configuration mode. To remove the flow monitor for the Measurement, Aggregation, and Correlation Engine (MACE), use the no form of this command.

flow monitor type mace name

no flow monitor type mace name

Syntax Description

Command Default

No flow monitor is configured for MACE.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

Use the flow monitor type mace command to define a set of metrics to be exported (flow record), the corresponding exporter information, and the cache timeout update. Use this command to configure a flow monitor for MACE and enter the FNF flow monitor configuration mode.

This mode accepts the following keywords:

•cache

•default

•description

•exporter

•record

Examples

The following example shows how to configure a flow monitor for MACE, mace1:

Router(config)# flow monitor type mace mace1 

Related Commands

flow record type mace

To configure a flow record for the Measurement, Aggregation, and Correlation Engine (MACE) and to enter Flexible NetFlow flow record configuration mode, use the flow record type mace command in global configuration mode. To remove the flow record for MACE, use the no form of this command.

flow record type mace name

no flow record type mace name

Syntax Description

Command Default

No flow record is configured for MACE.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

The flow record type mace command defines the key and non-key fields of MACE that are collected and exported. Use this command to configure a flow record for MACE and enter the FNF flow record configuration mode.

This mode accepts the following keywords:

•collect

•default

•description

•execute

Examples

The following example shows how to configure a flow record for MACE, mace1:

Router(config)# flow record type mace mace1 

Related Commands

frame-relay accounting adjust

To enable byte count adjustment at the permanent virtual circuit (PVC) level so that the number of bytes sent and received at the PVC corresponds to the actual number of bytes sent and received on the physical interface, use the frame-relay accounting adjust command in interface configuration mode. To disable byte count adjustment, use the no form of this command.

frame-relay accounting adjust

no frame-relay accounting adjust [frf9]

Syntax Description

frf9	(Optional) Payload compression using the Stacker method. Note Use the frf9 keyword only with the no form of this command.

Defaults

Byte count adjustment is enabled.

Command Modes

Interface configuration

Command History

Usage Guidelines

Use this command to return the number of bytes shown at the PVC level back to the number of bytes received at the PVC level without any adjustments. This command takes into consideration any dropped packets as well as compression and decompression that may occur after initial processing.

If you use the no frame-relay accounting adjust frf9 command, then byte count includes dropped packets and traffic shaping, but not compression and decompression savings from FRF.9.

Examples

The following example enables Frame-Relay accounting adjustment:

Router# configure terminal

Router(config)# interface serial3/0

Router(config-if) frame-relay accounting adjust

The following example disables Frame-Relay accounting adjustment:

Router# configure terminal

Router(config)# interface serial3/0

Router(config-if) no frame-relay accounting adjust

Router(config-if)# end

The following example verifies that Frame-Relay accounting adjustment is disabled:

Router# show run interface serial3/0

Building configuration...

Current configuration :266 bytes

!

interface Serial3/0

 no ip address

 encapsulation frame-relay

 no frame-relay accounting adjust

end

Related Commands

frame-relay adaptive-shaping

Note Effective with Cisco IOS XE Release 2.6, Cisco IOS Release 15.0(1)S, and Cisco IOS Release 15.1(3)T, the frame-relay adaptive-shaping becn and frame-relay adaptive-shaping foresight combinations of this command are hidden. Although these command combinations are still available in Cisco IOS software, the CLI interactive Help does not display them if you attempt to view them by entering a question mark at the command line.

These combinations of the command will be completely removed in a future release. For the frame-relay adaptive-shaping becn combination, this means that you will need to use the appropriate replacement command (or sequence of commands). For more information (including a list of replacement commands), see the Legacy QoS Command Deprecation feature document in the Cisco IOS XE Quality of Service Solutions Configuration Guide or the Legacy QoS Command Deprecation feature document in the Cisco IOS Quality of Service Solutions Configuration Guide. The frame-relay adaptive-shaping foresight combination of this command will not have a replacement command (or sequence of commands).

Note Effective with Cisco IOS XE Release 3.2S, the frame-relay adaptive-shaping becn combination of this command is replaced by a modular QoS CLI (MQC) command (or sequence of MQC commands). For the appropriate replacement command (or sequence of commands), see the Legacy QoS Command Deprecation feature document in the Cisco IOS XE Quality of Service Solutions Configuration Guide. The frame-relay adaptive-shaping foresight combination of this command does not have a replacement command (or sequence of commands).

To enable Frame Relay adaptive traffic shaping, use the frame-relay adaptive-shaping command in map-class configuration mode. To disable adaptive traffic shaping, use the no form of this command.

frame-relay adaptive-shaping {becn | foresight | interface-congestion [queue-depth]}

no frame-relay adaptive-shaping {becn | foresight | interface-congestion}

Syntax Description

Defaults

Frame Relay adaptive traffic shaping is not enabled.
Queue depth: 0 packets

Command Modes

Map-class configuration

Command History

Usage Guidelines

This command replaces the frame-relay becn-response-enable command. If you use the frame-relay becn-response-enable command in scripts, you should replace it with the frame-relay adaptive-shaping command.

The frame-relay adaptive-shaping command configures a router to adjust virtual circuit (VC) sending rates in response to BECN or ForeSight backward congestion notification messages or interface congestion.

Include this command in a map-class definition and apply the map class either to the main interface or to a subinterface.

Adaptive traffic shaping for interface congestion can be configured along with BECN or ForeSight. When adaptive shaping for interface congestion is used with BECN or ForeSight, if interface congestion exceeds the queue depth, then the PVC send rate is reduced to minimum committed information rate (minCIR). When interface congestion drops below the queue depth, then the send rate is adjusted in response to BECN or ForeSight.

Note For adaptive traffic shaping for interface congestion to work, the sum of the minCIR values for all PVCs on the interface must be less than the usable interface bandwidth.

Examples

ForeSight: Example

This example shows the map-class definition for a router configured with traffic shaping and Router ForeSight enabled:

interface Serial0

 no ip address

 encapsulation frame-relay

 frame-relay traffic-shaping

 frame-relay class control-A

!

map-class frame-relay control-A

 frame-relay adaptive-shaping foresight

 frame-relay cir 56000

 frame-relay bc 64000

Adaptive Shaping for Interface Congestion: Example

interface serial0

 encapsulation frame-relay

 frame-relay traffic-shaping

 frame-relay interface-dlci 200

 class adjust_vc_class_rate

!

map-class frame-relay adjust_vc_class_rate   

 frame-relay cir 64000

 frame-relay mincir 32000

 frame-relay adaptive-shaping interface-congestion 10

Related Commands

frame-relay address registration auto-address

To enable a router to automatically select a management IP address for Enhanced Local Management Interface (ELMI) address registration, use the frame-relay address registration auto-address command in global configuration mode. To disable automatic address selection, use the no form of this command.

frame-relay address registration auto-address

no frame-relay address registration auto-address

Syntax Description

This command has no arguments or keywords.

Defaults

Auto address selection is enabled.

Command Modes

Global configuration

Command History

Usage Guidelines

During system initialization, if no management IP address is configured, then the router automatically selects the IP address of one of the interfaces. The router will choose an Ethernet interface first and then serial and other interfaces. If you do not want the router to select a management IP address during system initialization, you can store the no form of this command in the configuration.

When automatic address selection is disabled and an IP address has not been configured using the frame-relay address registration ip global configuration command, the IP address for ELMI address registration will be set to 0.0.0.0.

The no frame-relay address registration ip command will set the IP address to 0.0.0.0, even when Frame Relay automatic address selection is enabled.

If you configure the IP address using the frame-relay address registration ip global configuration command, the IP address you configure will overwrite the IP address chosen automatically by the router.

If you enable automatic address selection after configuring the IP address using the frame-relay address registration ip global configuration command, the IP address chosen automatically by the router will overwrite the IP address you originally configured.

Examples

The following example shows ELMI enabled on serial interface 0. The automatic IP address selection mechanism is disabled, and no other management IP address has been configured, so the device will share a valid ifIndex and a management IP address of 0.0.0.0.

interface Serial 0

 no ip address

 encapsulation frame-relay

 frame-relay lmi-type ansi

 frame-relay qos-autosense

!

no frame-relay address registration auto-address

Related Commands

frame-relay address registration ip

To configure the IP address for Enhanced Local Management Interface (ELMI) address registration, use the frame-relay address registration ip command in global configuration mode. To set the IP address to 0.0.0.0, use the no form of this command.

frame-relay address registration ip address

no frame-relay address registration ip

Syntax Description

Defaults

No default behavior or values

Command Modes

Global configuration

Command History

Usage Guidelines

A management IP address configured by using the frame-relay address registration ip command will overwrite the IP address chosen by the router when automatic address selection is enabled.

The no frame-relay address registration ip command will disable automatic IP address selection and set the management IP address to 0.0.0.0.

If you enable automatic address selection with the frame-relay address registration auto-address global command after configuring the IP address using the frame-relay address registration ip global configuration command, the IP address chosen automatically by the router will overwrite the IP address you originally configured.

Examples

The following example shows ELMI enabled on serial interface 0. The IP address to be used for ELMI address registration is configured, so automatic IP address selection is disabled by default.

interface Serial 0

 no ip address

 encapsulation frame-relay

 frame-relay lmi-type ansi

 frame-relay qos-autosense

!

frame-relay address registration ip address 10.1.1.1

Related Commands

frame-relay address-reg enable

To enable Enhanced Local Management Interface (ELMI) address registration on an interface, use the frame-relay address-reg enable command in interface configuration mode. To disable ELMI address registration, use the no form of this command.

frame-relay address-reg enable

no frame-relay address-reg enable

Syntax Description

This command has no arguments or keywords.

Defaults

ELMI address registration is enabled.

Command Modes

Interface configuration

Command History

Usage Guidelines

ELMI address registration is enabled by default when ELMI is enabled.

Examples

The following example shows ELMI address registration disabled on serial interface 0.

interface Serial 0

 no ip address

 encapsulation frame-relay

 frame-relay lmi-type ansi

 frame-relay qos-autosense

 no frame-relay address-reg enable

Related Commands

frame-relay bc

Note Effective with Cisco IOS XE Release 2.6 and Cisco IOS Release 15.0(1)S, the frame-relay bc command is hidden. Although this command is still available in Cisco IOS software, the CLI interactive Help does not display it if you attempt to view it by entering a question mark at the command line.

This command will be completely removed in a future release, which means that you will need to use the appropriate replacement command (or sequence of commands). For more information (including a list of replacement commands), see the Legacy QoS Command Deprecation feature document in the Cisco IOS XE Quality of Service Solutions Configuration Guide or the Legacy QoS Command Deprecation feature document in the Cisco IOS Quality of Service Solutions Configuration Guide.

Note Effective with Cisco IOS XE Release 3.2S, the frame-relay bc command is hidden. Although this command is still available in Cisco IOS software, the CLI interactive command is replaced by a modular QoS CLI (MQC) command (or sequence of MQC commands). For the appropriate replacement command (or sequence of commands), see the Legacy QoS Command Deprecation feature document in the Cisco IOS XE Quality of Service Solutions Configuration Guide.

To specify the incoming or outgoing committed burst size (Bc) for a Frame Relay virtual circuit, use the frame-relay bc command in map-class configuration mode. To reset the committed burst size to the default, use the no form of this command.

frame-relay bc {in | out} bits

no frame-relay bc {in | out} bits

Syntax Description

Defaults

7000 bits

Command Modes

Map-class configuration

Command History

Usage Guidelines

The Frame Relay committed burst size is specified within a map class to request a certain burst rate for the circuit. Although it is specified in bits, an implicit time factor is the sampling interval Tc on the switch, which is defined as the burst size divided by the committed information rate (CIR).

Examples

In the following example, the serial interface already has a basic configuration, and a map group called "group1" has already been defined. The example shows a map-list configuration that defines the source and destination addresses for bermuda, provides IP and IPX addresses, and ties the map list definition to the map class called "class1". Then traffic-shaping parameters are defined for the map class.

map-list group1 local-addr X121 31383040703500 dest-addr X121 31383040709000

 ip 172.21.177.26 class class1 ietf

 ipx 123.0000.0c07.d530 class class1 ietf

map-class frame-relay class1

 frame-relay cir in 2000000

 frame-relay mincir in 1000000

 frame-relay cir out 15000

 frame-relay mincir out 10000

 frame-relay bc in 15000

 frame-relay bc out 9600

 frame-relay be in 10000

 frame-relay be out 10000

 frame-relay idle-timer 30

Related Commands

frame-relay be

Note Effective with Cisco IOS XE Release 2.6 and Cisco IOS Release 15.0(1)S, the frame-relay be command is hidden. Although this command is still available in Cisco IOS software, the CLI interactive Help does not display it if you attempt to view it by entering a question mark at the command line.

This command will be completely removed in a future release, which means that you will need to use the appropriate replacement command (or sequence of commands). For more information (including a list of replacement commands), see the Legacy QoS Command Deprecation feature document in the Cisco IOS XE Quality of Service Solutions Configuration Guide or the Legacy QoS Command Deprecation feature document in the Cisco IOS Quality of Service Solutions Configuration Guide.

Note Effective with Cisco IOS XE Release 3.2S, the frame-relay be command is hidden. Although this command is still available in Cisco IOS software, the CLI interactive command is replaced by a modular QoS CLI (MQC) command (or sequence of MQC commands). For the appropriate replacement command (or sequence of commands), see the Legacy QoS Command Deprecation feature document in the Cisco IOS XE Quality of Service Solutions Configuration Guide.

To set the incoming or outgoing excess burst size (Be) for a Frame Relay virtual circuit, use the frame-relay be command in map-class configuration mode. To reset the excess burst size to the default, use the no form of this command.

frame-relay be {in | out} bits

no frame-relay be {in | out} bits

Syntax Description

Defaults

7000 bits

Command Modes

Map-class configuration

Command History

Usage Guidelines

The Frame Relay excess burst size is specified within a map class to request a certain burst rate for the circuit. Although it is specified in bits, an implicit time factor is the sampling interval Tc on the switch, which is defined as the burst size divided by the committed information rate (CIR).

Examples

In the following example, the serial interface already has a basic configuration, and a map group called "bermuda" has already been defined. The example shows a map-list configuration that defines the source and destination addresses for bermuda, provides IP and IPX addresses, and ties the map list definition to the map class called "jamaica". Then traffic-shaping parameters are defined for the map class.

map-list bermuda local-addr X121 31383040703500 dest-addr X121 31383040709000

 ip 172.21.177.26 class jamaica ietf

 ipx 123.0000.0c07.d530 class jamaica ietf

map-class frame-relay jamaica

 frame-relay cir in 2000000

 frame-relay mincir in 1000000

 frame-relay cir out 15000

 frame-relay mincir out 10000

 frame-relay bc in 15000

 frame-relay bc out 9600

 frame-relay be in 10000

 frame-relay be out 10000

 frame-relay idle-timer 30

Related Commands

frame-relay broadcast-queue

To create a special queue for a specified interface to hold broadcast traffic that has been replicated for transmission on multiple data-link connection identifiers (DLCIs), use the frame-relay broadcast-queue command in interface configuration mode.

frame-relay broadcast-queue size byte-rate packet-rate

Syntax Description

Defaults

size: 64 packets
byte-rate: 256000 bytes per second
packet-rate: 36 packets per second

Command Modes

Interface configuration

Command History

Usage Guidelines

For purposes of the Frame Relay broadcast queue, broadcast traffic is defined as packets that have been replicated for transmission on multiple DLCIs. However, the broadcast traffic does not include the original routing packet or service access point (SAP) packet, which passes through the normal queue. Because of timing sensitivity, bridged broadcasts and spanning-tree packets are also sent through the normal queue. The Frame Relay broadcast queue is managed independently of the normal interface queue. It has its own buffers and a configurable service rate.

A broadcast queue is given a maximum transmission rate (throughput) limit measured in bytes per second and packets per second. The queue is serviced to ensure that only this maximum is provided. The broadcast queue has priority when transmitting at a rate below the configured maximum, and hence has a guaranteed minimum bandwidth allocation. The two transmission rate limits are intended to avoid flooding the interface with broadcasts. The actual limit in any second is the first rate limit that is reached.

Given the transmission rate restriction, additional buffering is required to store broadcast packets. The broadcast queue is configurable to store large numbers of broadcast packets.

The queue size should be set to avoid loss of broadcast routing update packets. The exact size will depend on the protocol being used and the number of packets required for each update. To be safe, set the queue size so that one complete routing update from each protocol and for each DLCI can be stored. As a general rule, start with 20 packets per DLCI. Typically, the byte rate should be less than both of the following:

•N/4 times the minimum remote access rate (measured in bytes per second), where N is the number of DLCIs to which the broadcast must be replicated.

•1/4 the local access rate (measured in bytes per second).

The packet rate is not critical if you set the byte rate conservatively. Set the packet rate at 250-byte packets.

Examples

The following example specifies a broadcast queue to hold 80 packets, to have a maximum byte transmission rate of 240000 bytes per second, and to have a maximum packet transmission rate of 160 packets per second:

frame-relay broadcast-queue 80 240000 160

frame-relay cir

Note Effective with Cisco IOS XE Release 2.6 and Cisco IOS Release 15.0(1)S, the frame-relay cir command is hidden. Although this command is still available in Cisco IOS software, the CLI interactive Help does not display it if you attempt to view it by entering a question mark at the command line.

This command will be completely removed in a future release, which means that you will need to use the appropriate replacement command (or sequence of commands). For more information (including a list of replacement commands), see the Legacy QoS Command Deprecation feature document in the Cisco IOS XE Quality of Service Solutions Configuration Guide or the Legacy QoS Command Deprecation feature document in the Cisco IOS Quality of Service Solutions Configuration Guide.

Note Effective with Cisco IOS XE Release 3.2S, the frame-relay cir command is hidden. Although this command is still available in Cisco IOS software, the CLI interactive command is replaced by a modular QoS CLI (MQC) command (or sequence of MQC commands). For the appropriate replacement command (or sequence of commands), see the Legacy QoS Command Deprecation feature document in the Cisco IOS XE Quality of Service Solutions Configuration Guide.

To specify the incoming or outgoing committed information rate (CIR) for a Frame Relay virtual circuit, use the frame-relay cir command in map-class configuration mode. To reset the CIR to the default, use the no form of this command.

frame-relay cir {in | out} bps

no frame-relay cir {in | out} bps

Syntax Description

Defaults

56000 bits per second

Command Modes

Map-class configuration

Command History

Usage Guidelines

Use this command to specify a CIR for an SVC. The specified CIR value is sent through the SETUP message to the switch, which then attempts to provision network resources to support this value.

Examples

The following example sets a higher committed information rate for incoming traffic than for outgoing traffic (which is going out on a slow WAN line):

frame-relay cir in 2000000

frame-relay cir out 9600

Related Commands

frame-relay class

To associate a map class with an interface or subinterface, use the frame-relay class command in interface configuration mode. To remove the association between the interface or subinterface and the named map class, use the no form of this command.

frame-relay class name

no frame-relay class name

Syntax Description

Defaults

No map class is defined.

Command Modes

Interface configuration

Command History

Usage Guidelines

This command can apply to interfaces or subinterfaces.

All relevant parameters defined in the name map class are inherited by each virtual circuit created on the interface or subinterface. For each virtual circuit, the precedence rules are as follows:

1. Use the map class associated with the virtual circuit if it exists.

2. If not, use the map class associated with the subinterface if the map class exists.

3. If not, use map class associated with interface if the map class exists.

4. If not, use the interface default parameters.

Examples

The following example associates the slow_vcs map class with the serial 0.1 subinterface and defines the slow_vcs map class to have an outbound CIR value of 9600:

interface serial 0.1

 frame-relay class slow_vcs

map-class frame-relay slow_vcs 

 frame-relay cir out 9600 

If a virtual circuit exists on the serial 0.1 interface and is associated with some other map class, the parameter values of the second map class override those defined in the slow_vc map class for that virtual circuit.

Related Commands

frame-relay congestion threshold de

Note Effective with Cisco IOS XE Release 2.6, Cisco IOS Release 15.0(1)S, and Cisco IOS Release 15.1(3)T, the frame-relay congestion threshold de command is hidden. Although this command is still available in Cisco IOS software, the CLI interactive Help does not display it if you attempt to view it by entering a question mark at the command line.

This command will be completely removed in a future release, which means that you will need to use the appropriate replacement command (or sequence of commands). For more information (including a list of replacement commands), see the Legacy QoS Command Deprecation feature document in the Cisco IOS XE Quality of Service Solutions Configuration Guide or the Legacy QoS Command Deprecation feature document in the Cisco IOS Quality of Service Solutions Configuration Guide.

Note Effective with Cisco IOS XE Release 3.2S, the frame-relay congestion threshold de command is replaced by a modular QoS CLI (MQC) command (or sequence of MQC commands). For the appropriate replacement command (or sequence of commands), see the Legacy QoS Command Deprecation feature document in the Cisco IOS XE Quality of Service Solutions Configuration Guide.

To configure the threshold at which discard-eligible (DE)-marked packets will be discarded from the traffic-shaping queue of a switched permanent virtual circuit (PVC), use the frame-relay congestion threshold de command in map-class configuration mode. To reconfigure the threshold, use the no form of this command.

frame-relay congestion threshold de percentage

no frame-relay congestion threshold de percentage

Syntax Description

Defaults

100%

Command Modes

Map-class configuration

Command History

Usage Guidelines

The frame-relay congestion threshold de command applies only to default FIFO traffic-shaping queues.

You must enable Frame Relay switching using the frame-relay switching global command before Frame Relay congestion management parameters will be effective on switched PVCs.

Examples

The following example illustrates the configuration of the DE congestion threshold in the Frame Relay map class called "perpvc_congestion":

map-class frame-relay perpvc_congestion

 frame-relay congestion threshold de 50

Related Commands

frame-relay congestion threshold ecn

Note Effective with Cisco IOS XE Release 2.6, Cisco IOS Release 15.0(1)S, and Cisco IOS Release 15.1(3)T, the frame-relay congestion threshold ecn command is hidden. Although this command is still available in Cisco IOS software, the CLI interactive Help does not display it if you attempt to view it by entering a question mark at the command line.

This command will be completely removed in a future release, which means that you will need to use the appropriate replacement command (or sequence of commands). For more information (including a list of replacement commands), see the Legacy QoS Command Deprecation feature document in the Cisco IOS XE Quality of Service Solutions Configuration Guide or the Legacy QoS Command Deprecation feature document in the Cisco IOS Quality of Service Solutions Configuration Guide.

Note Effective with Cisco IOS XE Release 3.2S, the frame-relay congestion threshold ecn command is replaced by a modular QoS CLI (MQC) command (or sequence of MQC commands). For the appropriate replacement command (or sequence of commands), see the Legacy QoS Command Deprecation feature document in the Cisco IOS XE Quality of Service Solutions Configuration Guide.

To configure the threshold at which explicit congestion notice (ECN) bits will be set on packets in the traffic-shaping queue of a switched permanent virtual circuit (PVC), use the frame-relay congestion threshold ecn command in map-class configuration mode. To reconfigure the threshold, use the no form of this command.

frame-relay congestion threshold ecn percentage

no frame-relay congestion threshold ecn percentage

Syntax Description

Defaults

100%

Command Modes

Map-class configuration

Command History

Usage Guidelines

The frame-relay congestion threshold ecn command applies only to default FIFO traffic-shaping queues.

One ECN threshold applies to all traffic on a traffic-shaping queue. You cannot configure separate thresholds for committed and excess traffic.

You must enable Frame Relay switching using the frame-relay switching global command before the frame-relay congestion threshold ecn command will be effective on switched PVCs.

Examples

The following example illustrates the configuration of the ECN congestion threshold in the Frame Relay map class called "perpvc_congestion":

map-class frame-relay perpvc_congestion

 frame-relay congestion threshold ecn 50

Related Commands

frame-relay congestion-management

To enable Frame Relay congestion management functions on all switched permanent virtual circuits (PVCs) on an interface, and to enter Frame Relay congestion management configuration mode, use the frame-relay congestion-management command in interface configuration mode. To disable Frame Relay congestion management, use the no form of this command.

frame-relay congestion-management

no frame-relay congestion-management

Syntax Description

This command has no arguments or keywords.

Defaults

Frame Relay congestion management is not enabled on switched PVCs.

Command Modes

Interface configuration

Command History

Usage Guidelines

You must enable Frame Relay switching, using the frame-relay switching global command, before you can configure Frame Relay congestion management.

Frame Relay congestion management is supported only when the interface is configured with class-based weighted fair queuing (WFQ).

Examples

In the following example, the frame-relay congestion-management command enables Frame Relay congestion management on serial interface 1. The command also enters Frame Relay congestion management configuration mode so that congestion threshold parameters can be configured.

interface serial1

 encapsulation frame-relay

 frame-relay intf-type dce

 frame-relay congestion-management

  threshold ecn be 0

  threshold ecn bc 20

Related Commands

frame-relay custom-queue-list

Note Effective with Cisco IOS XE Release 2.6, Cisco IOS Release 15.0(1)S, and Cisco IOS Release 15.1(3)T, the frame-relay custom-queue-list command is hidden. Although this command is still available in Cisco IOS software, the CLI interactive Help does not display it if you attempt to view it by entering a question mark at the command line.

This command will be completely removed in a future release, which means that you will need to use the appropriate replacement command (or sequence of commands). For more information (including a list of replacement commands), see the Legacy QoS Command Deprecation feature document in the Cisco IOS XE Quality of Service Solutions Configuration Guide or the Legacy QoS Command Deprecation feature document in the Cisco IOS Quality of Service Solutions Configuration Guide.

Note Effective with Cisco IOS XE Release 3.2S, the frame-relay custom-queue-list command is replaced by a modular QoS CLI (MQC) command (or sequence of MQC commands). For the appropriate replacement command (or sequence of commands), see the Legacy QoS Command Deprecation feature document in the Cisco IOS XE Quality of Service Solutions Configuration Guide.

To specify a custom queue to be used for the virtual circuit queueing associated with a specified map class, use the frame-relay custom-queue-list command in map-class configuration mode. 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 custom-queue-list list-number

no frame-relay custom-queue-list list-number

Syntax Description

Defaults

If this command is not entered, the default queueing is first come, first served.

Command Modes

Map-class configuration

Command History

Usage Guidelines

Use the queue-list commands to define the custom queue.

Only one form of queueing can be associated with a particular map class; subsequent definitions overwrite previous ones.

Examples

The following example configures a custom queue list for the "fast_vcs" map class:

map-class frame-relay fast_vcs

 frame-relay custom-queue-list 1

queue-list 1 queue 4 byte-count 100

Related Commands

frame-relay de-group

To specify the discard eligibility (DE) group number to be used for a specified data-link connection identifier (DLCI), use the frame-relay de-group command in interface configuration mode. To disable a previously defined group number assigned to a specified DLCI, use the no form of this command with the relevant keyword and arguments.

frame-relay de-group group-number dlci

no frame-relay de-group [group-number] [dlci]

Syntax Description

Defaults

No DE group is defined.

Command Modes

Interface configuration

Command History

Usage Guidelines

To disable all previously defined group numbers, use the no form of this command with no arguments.

This command requires that Frame Relay be enabled.

Frame Relay DE group functionality is supported on process-switched packets only.

The DE bit is not set or recognized by the Frame Relay switching code, but must be recognized and interpreted by the Frame Relay network.

Note Frame Relay DE group functionality is being replaced by the Modular QoS CLI (MQC) DE marking functionality. For information about the MQC commands that are used to configure Frame Relay DE marking, refer to the Cisco IOS Quality of Service Configuration Guide and Cisco IOS Quality of Service Command Reference.

Examples

The following example specifies that group number 3 will be used for DLCI 170:

frame-relay de-group 3 170

Related Commands

frame-relay de-list

To define a discard eligibility (DE) list specifying the packets that have the DE bit set and thus are eligible for discarding when congestion occurs on the Frame Relay switch, use the frame-relay de-list command in global configuration mode. To delete a portion of a previously defined DE list, use the no form of this command.

frame-relay de-list list-number {protocol protocol | interface type number} characteristic

no frame-relay de-list list-number {protocol protocol | interface type number} characteristic

Syntax Description

Defaults

Discard eligibility is not defined.

Command Modes

Global configuration

Command History

Usage Guidelines

To remove an entire DE list, use the no form of this command with no options and arguments.

This prioritizing feature requires that the Frame Relay network be able to interpret the DE bit as indicating which packets can be dropped first in case of congestion, or which packets are less time sensitive, or both.

When you calculate packet size, include the data packet size, the ICMP header, the IP header, and the Frame Relay encapsulation bytes. For example, count 92 bytes of data, 8 bytes for the ICMP header, 20 bytes for the IP header, and 4 bytes for the Frame Relay encapsulation, which equals 124 bytes.

Examples

The following example specifies that IP packets larger than 512 bytes (including the 4-byte Frame Relay encapsulation) will have the DE bit set:

frame-relay de-list 1 protocol ip gt 512

frame-relay end-to-end keepalive error-threshold

To modify the keepalive error threshold value, use the frame-relay end-to-end keepalive error-threshold command in map-class configuration mode. To reset the error threshold value to its default, use the no form of this command.

frame-relay end-to-end keepalive error-threshold {send | receive} count

no frame-relay end-to-end keepalive error-threshold {send | receive}

Syntax Description

Defaults

The default value for both the send and receive error threshold is 2.

Command Modes

Map-class configuration

Command History

Usage Guidelines

The send-side value can be configured only in bidirectional and request modes. The receive-side value can be configured only in bidirectional and reply modes. See the frame-relay end-to-end keepalive mode command. When you configure the error threshold, also configure the event window. See the frame-relay end-to-end keepalive event-window command.

Examples

The following example shows increasing the receive-side error threshold to 4 and changing the event window to 7:

map-class frame-relay olga

  frame-relay end-to-end keepalive reply

  frame-relay end-to-end keepalive error-threshold receive 4

  frame-relay end-to-end keepalive event-window receive 7

Related Commands

frame-relay end-to-end keepalive event-window

To modify the keepalive event window value, use the frame-relay end-to-end keepalive event-window command in map-class configuration mode. To reset the event window size to the default, use the no form of this command.

frame-relay end-to-end keepalive event-window {send | receive} size

no frame-relay end-to-end keepalive event-window {send | receive}

Syntax Description

Defaults

The default value for both the send and receive event windows is 3.

Command Modes

Map-class configuration

Command History

Usage Guidelines

The send-side value can be configured only in bidirectional and request modes. The receive-side value can be configured only in bidirectional and reply modes. See the frame-relay end-to-end keepalive mode command. When you configure the event window, also configure the error-threshold. See the frame-relay end-to-end keepalive error-threshold command.

Examples

The following example shows increasing the receive-side error threshold to 4 and changing the event window to 7:

map-class frame-relay olga

 frame-relay end-to-end keepalive reply

 frame-relay end-to-end keepalive error-threshold receive 4

 frame-relay end-to-end keepalive event-window receive 7

Related Commands

frame-relay end-to-end keepalive mode

To enable Frame Relay end-to-end keepalives, use the frame-relay end-to-end keepalive mode command in map-class configuration mode. To disable Frame Relay end-to-end keepalives, use the no form of this command.

frame-relay end-to-end keepalive mode {bidirectional | request | reply | passive-reply}

no frame-relay end-to-end keepalive mode

Syntax Description

Defaults

When a Frame Relay end-to-end keepalive mode is enabled, default values depend on which mode is selected. For the meaning of the parameters, see the frame-relay end-to-end keepalive timer, frame-relay end-to-end keepalive event-window, frame-relay end-to-end keepalive error-threshold, and frame-relay end-to-end keepalive success-events commands.

Command Modes

Map-class configuration

Command History

Usage Guidelines

In bidirectional mode, both ends of a virtual circuit (VC) send keepalive requests and respond to keepalive requests. If one end of the VC is configured in the bidirectional mode, the other end must also be configured in the bidirectional mode.

In request mode, the router sends keepalive requests and expects replies from the other end of the VC. If one end of a VC is configured in the request mode, the other end must be configured in the reply or passive-reply mode.

In reply mode, the router does not send keepalive requests, but waits for keepalive requests from the other end of the VC and replies to them. If no keepalive request has arrived within the timer interval, the router times out and increments the error counter by 1. If one end of a VC is configured in the reply mode, the other end must be configured in the request mode.

In passive-reply mode, the router does not send keepalive requests, but waits for keepalive requests from the other end of the VC and replies to them. No timer is set when in this mode, and the error counter is not incremented. If one end of a VC is configured in the passive-reply mode, the other end must be configured in the request mode.

Table 13 displays parameter values for send and receive sides in bidirectional mode.

Table 14 displays parameter values for send- and receive-sides in request mode.

Table 15 displays parameter values for send- and receive-sides in reply mode.

Passive-Reply Mode

In passive-reply mode, no values are set.

Examples

The following example configures one end of a VC to send keepalive requests and respond to keepalive requests from the other end of the VC:

map-class frame-relay vcgrp1

 frame-relay end-to-end keepalive bidirectional

The following example configures one end of a VC to reply to keepalive requests and to increment its error counter if no keepalive requests are received 30 seconds after the latest request:

map-class frame-relay oro34

 frame-relay end-to-end keepalive reply

 frame-relay end-to-end keepalive timer receive 30

Related Commands

frame-relay end-to-end keepalive success-events

To modify the keepalive success events value, use the frame-relay end-to-end keepalive success-events command in map-class configuration mode. To reset the success events value to its default, use the no form of this command.

frame-relay end-to-end keepalive success-events {send | receive} count

no frame-relay end-to-end keepalive success-events {send | receive}

Syntax Description

Defaults

The default value for both the send and receive success events is 2.

Command Modes

Map-class configuration

Command History

Usage Guidelines

The send-side value can be configured only in bidirectional and request modes. The receive-side value can be configured only in the bidirectional and reply modes. See the frame-relay end-to-end keepalive mode command.

If the success events value is set low at the same time that a low value is set for the error threshold value of the frame-relay end-to-end keepalive error-threshold command, the keepalive state of the VC may flap from state to state.

Examples

The following example shows how to increase the success events value:

map-class frame-relay vcgrp4

 frame-relay end-to-end keepalive request

 frame-relay end-to-end keepalive success-events send 4

Related Commands

frame-relay end-to-end keepalive timer

To modify the keepalive timer value, use the frame-relay end-to-end keepalive timer command in map-class configuration mode. To reset the timer value to its default, use the no form of this command.

frame-relay end-to-end keepalive timer {send | receive} number

no frame-relay end-to-end keepalive timer {send | receive}

Syntax Description

Defaults

Send timer: 10 seconds
Receive timer: 15 seconds

Command Modes

Map-class configuration

Command History

Usage Guidelines

The send-side value can be configured only in bidirectional and request modes. The receive-side value can be configured only in the bidirectional and reply modes. See the frame-relay end-to-end keepalive mode command.

The send-side timer expires if a reply has not been received number seconds after a request is sent. The receive-side timer expires if a request has not been received number seconds after the previous request.

Examples

The following example shows how to set up one end of a virtual circuit (VC) to send a keepalive request every 15 seconds and increment the error counter if more than 22 seconds elapse between receiving keepalive responses:

map-class frame-relay vcgrp1

 frame-relay end-to-end keepalive bidirectional

 frame-relay end-to-end keepalive timer send 15

 frame-relay end-to-end keepalive timer receive 22

Related Commands

frame-relay fair-queue

Note Effective with Cisco IOS XE Release 2.6, Cisco IOS Release 15.0(1)S, and Cisco IOS Release 15.1(3)T, the frame-relay fair-queue command is hidden. Although this command is still available in Cisco IOS software, the CLI interactive Help does not display it if you attempt to view it by entering a question mark at the command line.

This command will be completely removed in a future release, which means that you will need to use the appropriate replacement command (or sequence of commands). For more information (including a list of replacement commands), see the Legacy QoS Command Deprecation feature document in the Cisco IOS XE Quality of Service Solutions Configuration Guide or the Legacy QoS Command Deprecation feature document in the Cisco IOS Quality of Service Solutions Configuration Guide.

Note Effective with Cisco IOS XE Release 3.2S, the frame-relay fair-queue command is replaced by a modular QoS CLI (MQC) command (or sequence of MQC commands). For the appropriate replacement command (or sequence of commands), see the Legacy QoS Command Deprecation feature document in the Cisco IOS XE Quality of Service Solutions Configuration Guide.

To enable weighted fair queueing for one or more Frame Relay permanent virtual circuits (PVCs), use the frame-relay fair-queue command in map-class configuration mode. To disable weighted fair queueing for a Frame Relay map class, use the no form of this command.

frame-relay fair-queue [congestive-discard-threshold [number-dynamic-conversation-queues [number-reservable-conversation-queues [max-buffer-size-for-fair-queues]]]]

no frame-relay fair-queue [congestive-discard-threshold [number-dynamic-conversation-queues [number-reservable-conversation-queues [max-buffer-size-for-fair-queues]]]]

Syntax Description

Defaults

Weighted fair queueing is not enabled.

Command Modes

Map-class configuration

Command History

Usage Guidelines

To use this command, you must first associate a Frame Relay map class with a specific data-link connection identifier (DLCI), and then enter map-class configuration mode and enable or disable weighted fair queueing for that map class.

When Frame Relay fragmentation is enabled, weighted fair queueing is the only queueing strategy allowed.

If this command is entered without any accompanying numbers, the default values for each of the four parameters will be set. If you desire to alter only the value of the first parameter (congestive_discard_ threshold), you only need to enter the desired value for that parameter. If you desire to alter only the value of the second, third, or fourth parameters, you must enter values for the preceding parameters as well as for the parameter you wish to change.

Examples

The following example shows how to enable weighted fair queueing and set the default parameter values for the "vofr" Frame Relay map class on a Cisco 2600 series, 3600 series, or 7200 series router or on a Cisco MC3810:

interface serial 1/1

 frame-relay interface-dlci 100

  class vofr

  exit

map-class frame-relay vofr

 frame-relay fair-queue

The following example shows how to enable weighted fair queueing and set the congestive_discard_ threshold parameter to a value other than the default value for the "vofr" Frame Relay map class on a Cisco 2600 series, 3600 series, or 7200 series router or on an MC3810 concentrator:

interface serial 1/1

 frame-relay interface-dlci 100

  class vofr

  exit

map-class frame-relay vofr

 frame-relay fair-queue 255

The following example shows how to enable weighted fair queueing and set the number_reservable_ conversation_queues to a value of 25 for the "vofr" Frame Relay map class on a Cisco 2600 series, 3600 series, or 7200 series router or on a Cisco MC3810:

interface serial 1/1

 frame-relay interface-dlci 100

  class vofr

  exit

map-class frame-relay vofr

 frame-relay fair-queue 64 256 25

Related Commands

frame-relay fecn-adapt

Note Effective with Cisco IOS XE Release 2.6, Cisco IOS Release 15.0(1)S, and Cisco IOS Release 15.1(3)T, the frame-relay fecn-adapt command is hidden. Although this command is still available in Cisco IOS software, the CLI interactive Help does not display it if you attempt to view it by entering a question mark at the command line.

This command will be completely removed in a future release, which means that you will need to use the appropriate replacement command (or sequence of commands). For more information (including a list of replacement commands), see the Legacy QoS Command Deprecation feature document in the Cisco IOS XE Quality of Service Solutions Configuration Guide or the Legacy QoS Command Deprecation feature document in the Cisco IOS Quality of Service Solutions Configuration Guide.

Note Effective with Cisco IOS XE Release 3.2S, the frame-relay fecn-adapt command is replaced by a modular QoS CLI (MQC) command (or sequence of MQC commands). For the appropriate replacement command (or sequence of commands), see the Legacy QoS Command Deprecation feature document in the Cisco IOS XE Quality of Service Solutions Configuration Guide.

To enable Frame Relay traffic-shaping reflection of forward explicit congestion notifications (FECNs) as backward explicit congestion notifications (BECNs), use the frame-relay fecn-adapt command in map-class configuration mode. To disable this reflection, use the no form of this command.

frame-relay fecn-adapt

no frame-relay fecn-adapt

Syntax Description

This command has no arguments or keywords.

Command Default

Frame Relay traffic-shaping reflection of FECNs as BECNs is disabled.

Command Modes

Map-class configuration (config-map-class)

Command History

Examples

The following example shows how to configure the frame-relay fecn-adapt command:

Router> enable

Router# configure terminal

Router(config)# map-class frame-relay class1

Router(config-map-class)# frame-relay fecn-adapt 

Router(config-map-class)# end

Related Commands

frame-relay fragment

To enable fragmentation of Frame Relay frames for a Frame Relay map class, use the frame-relay fragment command in map-class configuration mode. To disable Frame Relay fragmentation, use the no form of this command.

frame-relay fragment fragment-size [switched]

no frame-relay fragment

Syntax Description

Command Default

Fragmentation is disabled.

Command Modes

Map-class configuration

Command History

Usage Guidelines

You should enable fragmentation for low-speed links (meaning those operating at less than 768 kbps).

Frame Relay fragmentation is enabled on a per-PVC basis. Before enabling Frame Relay fragmentation, you must first associate a Frame Relay map class with a specific data-link connection identifier (DLCI) and then enter map-class configuration mode and enable or disable fragmentation for that map class. In addition, you must enable Frame Relay traffic shaping on the interface.

Selecting a Fragmentation Format

Frame Relay frames are fragmented using one of the following formats, depending on how the PVC is configured:

•Pure end-to-end FRF.12

•FRF.11 Annex C

•Cisco proprietary

Only pure end-to-end FRF.12 fragmentation can be configured on switched PVCs.

Cisco recommends pure end-to-end FRF.12 fragmentation on PVCs that are carrying VoIP packets and on PVCs that share the link with other PVCs carrying Voice over Frame Relay (VoFR) traffic.

In pure end-to-end FRF.12 fragmentation, Frame Relay frames having a payload less than the fragment size configured for that PVC are transmitted without the fragmentation header.

FRF.11 Annex C fragmentation and Cisco proprietary fragmentation are used when VoFR frames are transmitted on a PVC. When fragmentation is enabled on a PVC, and when command vofr is configured on that PVC, FRF.11 Annex C format is implemented. When command vofr cisco is configured, Cisco proprietary format is implemented.

In FRF.11 Annex C and Cisco proprietary fragmentation, VoFR frames are never fragmented, and all data packets (including VoIP packets) contain the fragmentation header regardless of the payload size.

Selecting a Fragment Size

You should set the fragment size based on the lowest port speed between the routers. For example, for a hub-and-spoke Frame Relay topology where the hub has a T1 speed and the remote routers have 64-kbps port speeds, the fragmentation size must be set for the 64-kbps speed on both routers. Any other PVCs that share the same physical interface must use the same fragmentation size used by the voice PVC.

With pure end-to-end FRF.12 fragmentation, you should select a fragment size that is larger than the voice packet size.

Table 16 shows the recommended fragmentation sizes for a serialization delay of 10 ms.

Examples

FRF.12 Fragmentation on a Switched PVC: Example

The following example shows how to configure pure end-to-end FRF.12 fragmentation in a map class that is named data. The map class is associated with switched PVC 20 on serial interface 3/3:

Router(config)# frame-relay switching

Router(config)# interface Serial3/2

Router(config-if)# encapsulation frame-relay

Router(config-if)# frame-relay intf-type dce

Router(config-if)# exit

Router(config)# interface Serial3/3

Router(config-if)# encapsulation frame-relay

Router(config-if)# frame-relay traffic-shaping

Router(config-if)# frame-relay interface-dlci 20 switched

Router(config-fr-dlci)# class data

Router(config-fr-dlci)# exit

Router(config-if)# frame-relay intf-type dce

Router(config-if)# exit

Router(config)# map-class frame-relay data

Router(config-map-class)# frame-relay fragment 80 switched

Router(config-map-class)# frame-relay cir 64000

Router(config-map-class)# frame-relay bc 640

Router(config-map-class)# exit

Router(config)# connect data Serial3/2 16 Serial3/3 20

End-to-End FRF.12 Fragmentation: Example

The following example shows how to enable pure end-to-end FRF.12 fragmentation for a map class. named frag. The fragment payload size is set to 40 bytes. Frame Relay traffic shaping is required on the PVC; the only queueing type supported on the PVC when fragmentation is configured is weighted fair queueing (WFQ).

Router(config)# interface serial 1/0/0

Router(config-if)# frame-relay traffic-shaping

Router(config-if)# frame-relay interface-dlci 100

Router(config-fr-dlci)# class frag

Router(config-fr-dlci)# exit

Router(config)# map-class frame-relay frag

Router(config-map-class)# frame-relay cir 128000

Router(config-map-class)# frame-relay bc 1280

Router(config-map-class)# frame-relay fragment 40

Router(config-map-class)# frame-relay fair-queue 
Router(config-map-class)# exit

The following example is for the same configuration on a VIP-enabled Cisco 7500 series router:

Router(config)# class-map frf

Router(config-cmap)# match protocol vofr

Router(config-cmap)# exit

Router(config)# policy-map llq

Router(config-pmap)# class frf

Router(config-pmap-c)# priority 2000

Router(config-pmap-c)# exit

Router(config-pmap)# exit

Router(config)# policy-map llq-shape

Router(config-pmap)# class class-default

Router(config-pmap-c)# shape average 1000 128000

Router(config-pmap-c)# service-policy llq

Router(config-pmap-c)# exit

Router(config-pmap)# exit

Router(config)# interface serial 1/0/0.1

Router(config-if)# frame-relay interface-dlci 100

Router(config-fr-dlci)# class frag

Router(config-fr-dlci)# exit

Router(config)# map-class frame-relay frag

Router(config-map-class)# frame-relay fragment 40

Router(config-map-class)# service-policy llq-shape

Router(config-map-class)# exit

FRF.11 Annex C Fragmentation Configuration: Example

The following example shows how to enable FRF.11 Annex C fragmentation for data on a Cisco MC3810 PVC configured for VoFR. Fragmentation must be configured if a VoFR PVC will carry data. The fragment payload size is set to 40 bytes. Frame Relay traffic shaping is required on the PVC; the only queueing type supported on the PVC when fragmentation is configured is weighted fair queueing (WFQ):

Router(config)# interface serial 1/1

Router(config-if)# frame-relay traffic-shaping

Router(config-if)# frame-relay interface-dlci 101

Router(config-fr-dlci)# vofr

Router(config-fr-dlci)# class frag

Router(config-fr-dlci)# exit

Router(config)# map-class frame-relay frag

Router(config-map-class)# frame-relay cir 128000

Router(config-map-class)# frame-relay bc 1280

Router(config-map-class)# frame-relay fragment 40

Router(config-map-class)# frame-relay fair-queue

Router(config-map-class)# exit

The following example is for the same configuration on a VIP-enabled Cisco 7500 series router:

Router(config)# class-map frf

Router(config-cmap)# match protocol vofr

Router(config-cmap)# exit

Router(config)# policy-map llq

Router(config-pmap)# class frf

Router(config-pmap-c)# priority 2000

Router(config-pmap-c)# exit

Router(config-pmap)# exit

Router(config)# policy-map llq-shape

Router(config-pmap)# class class-default

Router(config-pmap-c)# shape average 1000 128000

Router(config-pmap-c)# service-policy llq

Router(config-pmap-c)# exit

Router(config-pmap)# exit

Router(config)# interface serial 1/1/0.1

Router(config-if)# frame-relay interface-dlci 101

Router(config-fr-dlci)# class frag

Router(config-fr-dlci)# exit

Router(config)# map-class frame-relay frag

Router(config-map-class)# frame-relay fragment 40

Router(config-map-class)# service-policy llq-shape

Router(config-map-class)# exit

Cisco-Proprietary Fragmentation: Example

The following example shows how to enable Cisco-proprietary Frame Relay fragmentation for a Frame Relay map class named frag on a Cisco 2600 series, Cisco 3600 series, or Cisco 7200 series router, starting from global configuration mode. The fragment payload size is set to 40 bytes. Frame Relay traffic shaping is required on the PVC; the only queueing type supported on the PVC when fragmentation is configured is weighted fair queueing (WFQ):

Router(config)# interface serial 2/0/0

Router(config-if)# frame-relay traffic-shaping

Router(config-if)# frame-relay interface-dlci 102

Router(config-fr-dlci)# vofr cisco

Router(config-fr-dlci)# class frag

Router(config-fr-dlci)# exit

Router(config)# map-class frame-relay frag 
Router(config-map-class)# frame-relay cir 128000 
Router(config-map-class)# frame-relay bc 1280 
Router(config-map-class)# frame-relay fragment 40 
Router(config-map-class)# frame-relay fair-queue

The following example is for the same configuration on a VIP-enabled Cisco 7500 series router:

Router(config)# class-map frf

Router(config-cmap)# match protocol vofr

Router(config-cmap)# exit

Router(config)# policy-map llq

Router(config-pmap)# class frf

Router(config-pmap-c)# priority 2000

Router(config-pmap-c)# exit

Router(config-pmap)# exit

Router(config)# policy-map llq-shape

Router(config-pmap)# class class-default

Router(config-pmap-c)# shape average 1000 128000

Router(config-pmap-c)# service-policy llq

Router(config-pmap-c)# exit

Router(config-pmap)# exit

Router(config)# interface serial 2/0/0.1

Router(config-if)# frame-relay interface-dlci 102

Router(config-fr-dlci)# class frag

Router(config-fr-dlci)# exit

Router(config)# map-class frame-relay frag

Router(config-map-class)# frame-relay fragment 40

Router(config-map-class)# service-policy llq-shape

Related Commands

frame-relay fragment end-to-end

To enable fragmentation of Frame Relay frames on an interface, use the frame-relay fragment end-to-end command in interface configuration mode. To disable Frame Relay fragmentation on an interface, use the no form of this command.

frame-relay fragment fragment-size end-to-end

no frame-relay fragment end-to-end

Syntax Description

Command Default

Fragmentation is disabled.

Command Modes

Interface configuration

Command History

Usage Guidelines

Interface fragmentation and class-based fragmentation cannot be configured at the same time. To configure class-based fragmentation that can be applied to individual permanent virtual circuits (PVCs), use the frame-relay fragment command in map-class configuration mode.

Interface fragmentation supports the following fragment formats:

•End-to-end FRF.12

•FRF.11 Annex C

•Cisco proprietary

When fragmentation is enabled on an interface, all PVCs on the main interface and its subinterfaces will have fragmentation enabled with the same configured fragment size.

All the fragments of a Frame Relay frame except the last fragment will have a payload size equal to fragment-size; the last fragment will have a payload less than or equal to fragment-size.

When configuring fragmentation on an interface that has low-latency queueing, configure the fragment size to be greater than the largest high-priority frame that is expected. This configuration prevents higher-priority traffic from being fragmented and queued behind lower-priority fragmented frames. If the size of a high-priority frame is larger than the configured fragment size, the high-priority frame is fragmented.

Local Management Interface (LMI) traffic is fragmented.

Interface fragmentation and Frame Relay traffic shaping cannot be configured at the same time.

Examples

The following example shows the configuration of low-latency queueing, FRF.12 fragmentation, and shaping on serial interface 3/2. Traffic from the priority queue will not be interleaved with fragments from the class-default queue, because shaping is configured.

class-map voice

 match access-group 101

policy-map llq

 class voice

  priority 64

policy-map shaper

 class class-default 

  shape average 96000

  service-policy llq

interface serial 3/2

 ip address 10.0.0.1 255.0.0.0

 encapsulation frame-relay

 bandwidth 128

 clock rate 128000

 service-policy output shaper

 frame-relay fragment 80 end-to-end

access-list 101 match ip any host 10.0.0.2

Related Commands

frame-relay fragmentation voice-adaptive

To enable voice-adaptive Frame Relay fragmentation, use the frame-relay fragmentation voice-adaptive command in interface configuration mode. To disable voice-adaptive Frame Relay fragmentation, use the no form of this command.

frame-relay fragmentation voice-adaptive [deactivation seconds]

no frame-relay fragmentation voice-adaptive

Syntax Description

Defaults

Voice-adaptive Frame Relay fragmentation is not enabled.
Seconds: 30

Command Modes

Interface configuration

Command History

Usage Guidelines

Frame Relay voice-adaptive fragmentation can be used in conjunction with Frame Relay voice-adaptive traffic shaping to reduce network congestion and improve voice transmission quality.

The frame-relay fragmentation voice-adaptive command can be used only on main interfaces. This command is not supported on subinterfaces.

Frame Relay voice-adaptive fragmentation enables a router to fragment large packets whenever packets (usually voice) are detected in the low latency queueing priority queue or H.323 call setup signaling packets are present. When there are no packets in the priority queue for a configured period of time and signaling packets are not present, fragmentation is stopped.

Note Although the priority queue is generally used for voice traffic, Frame Relay voice-adaptive fragmentation will respond to any packets (voice or data) in the priority queue.

Note the following prerequisites for Frame Relay voice-adaptive fragmentation:

•End-to-end fragmentation must be configured in a map class by using the frame-relay fragment command or on the interface by using the frame-relay fragment end-to-end command.

•Frame Relay traffic shaping or traffic shaping using the Modular QoS CLI (MQC) must be configured. If end-to-end fragmentation is configured on the interface, traffic shaping using the MQC must be configured.

•Low latency queueing must be configured.

Frame Relay voice-adaptive fragmentation supports FRF.12 fragmentation only. Neither FRF.11 Annex C nor Cisco proprietary fragmentation is supported.

Examples

The following examples show the configuration of Frame Relay voice-adaptive traffic shaping and fragmentation. The first example shows end-to-end fragmentation configured in a map class that is associated with PVC 100. In the second example, end-to-end fragmentation is configured directly on the interface.

With both example configurations, priority-queue packets or H.323 call setup signaling packets destined for PVC 100 will result in the reduction of the sending rate from the committed information rate (CIR) to the minimum CIR and the activation of FRF.12 end-to-end fragmentation. If signaling packets and priority-queue packets are not detected for 50 seconds, the sending rate will increase to CIR and fragmentation will be deactivated.

Frame Relay Voice-Adaptive Fragmentation with End-to-End Fragmentation Configured in a Map Class: Example

interface serial0

 encapsulation frame-relay

 frame-relay fragmentation voice-adaptive deactivation 50

 frame-relay interface-dlci 100

  class voice_adaptive_class

! 

map-class frame-relay voice_adaptive_class

 frame-relay fair-queue

 frame-relay fragment 80 

 service-policy output shape

Frame Relay Voice-Adaptive Fragmentation with End-to-End Fragmentation Configured on the Interface: Example

interface serial0

 encapsulation frame-relay

 frame-relay fragmentation voice-adaptive deactivation 50

 frame-relay fragment 80 end-to-end

 frame-relay interface-dlci 100

  class voice_adaptive_class

Related Commands

frame-relay holdq

To configure the maximum size of a traffic-shaping queue on a switched permanent virtual circuit (PVC), use the frame-relay holdq command in map-class configuration mode. To reconfigure the size of the queue, use the no form of this command.

frame-relay holdq queue-size

no frame-relay holdq queue-size

Syntax Description

Defaults

40 packets for FIFO and 600 packets for CBWFQ

Command Modes

Map-class configuration

Command History

Usage Guidelines

You must enable Frame Relay traffic shaping, using the frame-relay traffic-shaping interface command, before frame-relay holdq and other traffic-shaping map-class commands will be effective.

You must enable Frame Relay switching, using the frame-relay switching global command, before the frame-relay holdq command will be effective on switched PVCs.

The frame-relay holdq command can be applied to switched PVCs that use FIFO default queueing.

Examples

The following example illustrates the configuration of the maximum size of the traffic-shaping queue on a switched PVC. The queue size is configured in a map class called "perpvc_congestion":

map-class frame-relay perpvc_congestion

 frame-relay holdq 100

Related Commands

frame-relay idle-timer

To specify the idle timeout interval for a switched virtual circuit (SVC), use the frame-relay idle-timer command in map-class configuration mode. To reset the idle timer to its default interval, use the no form of this command.

frame-relay idle-timer [in | out] seconds

no frame-relay idle-timer seconds

Syntax Description

Defaults

120 seconds

Command Modes

Map-class configuration

Command History

Usage Guidelines

The frame-relay idle-timer command applies to switched virtual circuits that are associated with the map class where the idle-timer is defined.

The idle timer must be tuned for each application. Routing protocols such as Routing Information Protocol (RIP) might keep the SVC up indefinitely because updates go out every 10 seconds.

Beginning in Cisco IOS Release 11.3, if in and out are not specified in the command, the timeout interval applies to both timers. In Cisco IOS Release 11.2, the timeout interval applies to the outbound timer.

Examples

The following example defines the traffic rate and idle timer for the fast_vcs map class and applies those values to DLCI 100, which is associated with that map class:

interface serial 0

 frame-relay interface-dlci 100

  class fast_vc

map-class frame-relay fast_vcs

 frame-relay traffic-rate 56000 128000

 frame-relay idle-timer 30

Related Commands

frame-relay ifmib-counter64

To enable 64-bit interface counter support on Frame Relay interfaces and subinterfaces that have a line speed of less than 20 Mbps, use the frame-relay ifmib-counter64 command in interface configuration mode. To disable 64-bit counter support on Frame Relay interfaces and subinterfaces that have a line speed of less than 20 Mbps, use the no form of this command.

frame-relay ifmib-counter64 [if | subif]

no frame-relay ifmib-counter64 [if | subif]

Syntax Description

Command Default

64-bit interface counters are not supported for interfaces that have a line speed of less than 20 Mbps.

Command Modes

Interface configuration

Command History

Usage Guidelines

Entering the frame-relay ifmib-counter64 command with no keyword produces the same result as entering the frame-relay ifmib-counter64 command with the if keyword.

Examples

The following example shows how to enable support for 64-bit interface counters on serial interface 5/3 and associated subinterfaces:

interface Serial 5/3

 no ip address

 no ip directed-broadcast

 encapsulation frame-relay

 no ip mroute-cache

 load-interval 30

 no keepalive

 frame-relay ifmib-counter64

Related Commands

frame-relay interface-dlci

To assign a data-link connection identifier (DLCI) to a specified Frame Relay subinterface on the router or access server, to assign a specific permanent virtual circuit (PVC) to a DLCI, or to apply a virtual template configuration for a PPP session, use the frame-relay interface-dlci command in interface configuration mode or subinterface configuration mode. To remove this assignment, use the no form of this command.

frame-relay interface-dlci dlci [ietf | cisco] [voice-cir cir] [ppp virtual-template-name]

no frame-relay interface-dlci dlci [ietf | cisco] [voice-cir cir] [ppp virtual-template-name]

BOOTP Server Only

frame-relay interface-dlci dlci [protocol ip ip-address]

no frame-relay interface-dlci dlci [protocol ip ip-address]

Cisco ASR 1000 Router

frame-relay interface-dlci dlci

no frame-relay interface-dlci dlci

Syntax Description

Command Default

No DLCI is assigned.

Command Modes

Interface configuration (config-if)
Subinterface configuration (config-subif)

Command History

Usage Guidelines

This command is typically used for subinterfaces; however, it can also be used on main interfaces. Using the frame-relay interface-dlci command on main interfaces will enable the use of routing protocols on interfaces that use Inverse Addresss Resolution Protocol (ARP). The frame-relay interface-dlci command on a main interface is also valuable for assigning a specific class to a single PVC where special characteristics are desired. Subinterfaces are logical interfaces associated with a physical interface. You must specify the interface and subinterface before you can use this command to assign any DLCIs and any encapsulation or broadcast options.

A DLCI cannot be configured on a subinterface if the same DLCI has already been configured on the main interface. If the same DLCI is to be configured on the subinterface as on the main interface, the DLCI on the main interface must be removed first before it is configured on the subinterface. The DLCI on the main interface can be removed by using the no frame-relay interface-dlci command on the main interface.

This command is required for all point-to-point subinterfaces; it is also required for multipoint subinterfaces for which dynamic address resolution is enabled. It is not required for multipoint subinterfaces configured with static address mappings.

Use the protocol ip ip-address option only when this router or access server will act as the BOOTP server for auto installation over Frame Relay.

By issuing the frame-relay interface-dlci interface configuration command, you enter Frame Relay DLCI interface configuration mode. This gives you the following command options, which must be used with the relevant class or X.25-profile names you previously assigned:

•class name—Assigns a map class to a DLCI.

•default—Sets a command to its defaults.

•no {class name | x25-profile name}—Cancels the relevant class or X.25 profile.

•x25-profile name—Assigns an X.25 profile to a DLCI. (Annex G.)

A Frame Relay DLCI configured for Annex G can be thought of as a single logical X.25 or Link Access Procedure, Balanced (LAPB) interface. Therefore, any number of X.25 routes may be configured to route X.25 calls to that logical interface.

The voice-cir option on the Cisco MC3810 provides call admission control; it does not provide traffic shaping. A call setup will be refused if the unallocated bandwidth available at the time of the request is not at least equal to the value of the voice-cir option.

When configuring the voice-cir option on the Cisco MC3810 for Voice over Frame Relay, do not set the value of this option to be higher than the physical link speed. If Frame Relay traffic shaping is enabled for a PVC that is sharing voice and data, do not configure the voice-cir option to be higher than the value set with the frame-relay mincir command.

Note On the Cisco MC3810 only, the voice-cir option performs the same function as the frame-relay voice bandwidth map class configuration command introduced in Cisco IOS Release 12.0(3)XG.

Examples

The following example assigns DLCI 100 to serial subinterface 5.17:

! Enter interface configuration and begin assignments on interface serial 5.

interface serial 5

! Enter subinterface configuration by assigning subinterface 17.

interface serial 5.17

! Now assign a DLCI number to subinterface 5.17.

frame-relay interface-dlci 100

The following example specifies DLCI 26 over serial subinterface 1.1 and assigns the characteristics under virtual-template 2 to this PPP connection:

Router(config)# interface serial1.1 point-to-point

Router(config-if)# frame-relay interface-dlci 26 ppp virtual-template2

The following example shows an Annex G connection being created by assigning the X.25 profile "NetworkNodeA" to Frame Relay DLCI interface 20 on serial interface 1 (having enabled Frame Relay encapsulation on that interface):

Router(config)# interface serial 1

Router(config-if)# encapsulation frame-relay

Router(config-if)# frame-relay interface-dlci 20

Router(config-fr-dlci)# x25-profile NetworkNodeA

The following example assigns DLCI 100 to serial subinterface 5.17:

Router(config)# interface serial 5

Router(config-if)# interface serial 5.17

Router(config-if)# frame-relay interface-dlci 100

The following example assigns DLCI 80 to the main interface first and then removes it before assigning the same DLCI to the subinterface. The DLCI must be removed from the main interface first, because the same DLCI cannot be assigned to the subinterface after already being assigned to the main interface:

Router(config)# interface serial 2/0

Router(config-if)# encapsulation frame-relay

Router(config-if)# frame-relay interface-dlci 80

Router(config-fr-dlci)# exit

Router(config-if)# interface serial 2/0

Router(config-if)# no frame-relay interface-dlci 80

Router(config-if)# interface serial 2/0.1

Router(config-subif)# frame-relay interface-dlci 80

Related Commands

frame-relay interface-dlci switched

To indicate that a Frame Relay data-link connection identifier (DLCI) is switched, use the frame-relay interface-dlci switched command in interface configuration mode. To remove this assignment, use the no form of this command.

frame-relay interface-dlci dlci switched

no frame-relay interface-dlci dlci switched

Syntax Description

Defaults

No DLCI is assigned.
The default PVC type is terminated.

Command Modes

Interface configuration

Command History

Usage Guidelines

Use the frame-relay interface-dlci switched command to allow a map class to be associated with a switched permanent virtual circuit (PVC).

You cannot change an existing PVC from terminated to switched or vice versa. You must delete the PVC and recreate it in order to change the type.

Use the frame-relay interface-dlci switched command to create switched PVCs for configuring Frame Relay-ATM network interworking (FRF.5) and Frame Relay-ATM service interworking (FRF.8).

By issuing the frame-relay interface-dlci switched interface configuration command, you enter Frame Relay DLCI interface configuration mode (see the example below).

Examples

In the following example, DLCI 16 on serial interface 0 is identified as a switched PVC and is associated with a map class called shape256K.

Router(config) # interface serial0

Router(config-if) # encapsulation frame-relay

Router(config-if) # frame-relay interface-dlci 16 switched

Router(config-fr-dlci) # class shape256K

Related Commands

frame-relay intf-type

To configure a Frame Relay switch type, use the frame-relay intf-type command in interface configuration mode. To disable the switch, use the no form of this command.

frame-relay intf-type [dce | dte | nni]

no frame-relay intf-type [dce | dte | nni]

Syntax Description

Defaults

The router or access server is connected to a Frame Relay network.

Command Modes

Interface configuration

Command History

Usage Guidelines

This command can be used only if Frame Relay switching has previously been enabled globally by means of the frame-relay switching command.

Examples

The following example configures a DTE switch type:

frame-relay switching

!

interface serial 2

 frame-relay intf-type dte

frame-relay inverse-arp

To reenable Inverse Address Resolution Protocol (Inverse ARP) on a specified interface, subinterface, data-link connection identifier (DLCI), or Frame Relay permanent virtual circuit (PVC) bundle if Inverse ARP was previously disabled, use the frame-relay inverse-arp command in interface configuration mode. To disable Inverse ARP, use the no form of this command.

frame-relay inverse-arp [protocol] [dlci | vc-bundle vc-bundle-name]

no frame-relay inverse-arp [protocol] [dlci | vc-bundle vc-bundle-name]

Syntax Description

Defaults

Inverse ARP is enabled.

Command Modes

Interface configuration

Command History

Usage Guidelines

To enable Inverse ARP for all protocols that were enabled before the prior no frame-relay inverse-arp command was issued, use the frame-relay inverse-arp command without arguments. To disable Inverse ARP for all protocols supported on an interface, use the no frame-relay inverse-arp command without arguments.

To enable or disable Inverse ARP for a specific protocol and DLCI pair, use both the protocol and dlci arguments. To enable or disable Inverse ARP for a specific protocol and Frame Relay PVC bundle (consisting of up to eight DLCIs), use both the protocol and vc-bundle vc-bundle-name elements.

To enable or disable Inverse ARP for all protocols on a DLCI or Frame Relay PVC bundle, use either the dlci argument by itself or the vc-bundle vc-bundle-name keyword and argument pair by itself. To enable or disable Inverse ARP for a specific protocol for all DLCIs on the specified interface or subinterface, use only the protocol argument.

When a Frame Relay PVC bundle is specified, only one member of the PVC bundle will handle Inverse ARP packets. By default, the bundle member PVC that handles precedence or EXP level 6 or DSCP level 63 handles Inverse ARP packets. Use the inarp command to configure a different PVC bundle member to handle Inverse ARP packets.

This implementation of Inverse ARP is based on RFC 1293. It allows a router or access server running Frame Relay to discover the protocol address at the other side of a virtual circuit.

The show frame-relay map command displays the word "dynamic" to flag virtual circuits that are created dynamically by Inverse ARP.

Examples

The following example sets Inverse ARP on DLCI 100 on an interface running IPX:

interface serial 0

 frame-relay inverse-arp ipx 100

Related Commands

frame-relay ip tcp compression-connections

To specify the maximum number of TCP header compression connections that can exist on a Frame Relay interface, use the frame-relay ip tcp compression-connections command in interface configuration mode. To restore the default, use the no form of this command.