Table Of Contents
Frame Relay Hardware Configurations
Frame Relay Configuration Task List
Enabling Frame Relay Encapsulation on an Interface
Configuring Dynamic or Static Address Mapping
Explicitly Configuring the LMI
Setting the LMI Keepalive Interval
Setting the LMI Polling and Timer Intervals
Enabling Frame Relay SVC Service
Configuring SVCs on a Physical Interface
Configuring SVCs on a Subinterface
Configuring a Map Group with E.164 or X.121 Addresses
Associating the Map Class with Static Protocol Address Maps
Configuring Frame Relay Traffic Shaping
Defining VCs for Different Types of Traffic
Enabling Frame Relay Traffic Shaping on the Interface
Frame Relay ForeSight Prerequisites
Frame Relay Congestion Notification Methods
Enabling Enhanced Local Management Interface
Specifying a Traffic Shaping Map Class for the Interface
Defining a Map Class with Queueing and Traffic Shaping Parameters
Defining Priority Queue Lists for the Map Class
Defining Custom Queue Lists for the Map Class
Customizing Frame Relay for Your Network
Configuring Frame Relay End-to-End Keepalives
Verifying Frame Relay End-to-End Keepalives
Configuring PPP over Frame Relay
Configuring Frame Relay Subinterfaces
Understanding Frame Relay Subinterfaces
Defining Subinterface Addressing
Configuring Transparent Bridging for Frame Relay
Configuring a Backup Interface for a Subinterface
Configuring Frame Relay Switching
Enabling Frame Relay Switching
Configuring a Frame Relay DTE Device, DCE Switch, or NNI Support
Disabling or Reenabling Frame Relay Inverse ARP
Creating a Broadcast Queue for an Interface
Configuring Payload Compression
Configuring Standard-Based FRF.9 Compression
Selecting FRF.9 Compression Method
Configuring FRF.9 Compression Using Map Statements
Configuring FRF.9 Compression on the Subinterface
Configuring TCP/IP Header Compression
Configuring an Individual IP Map for TCP/IP Header Compression
Configuring an Interface for TCP/IP Header Compression
Disabling TCP/IP Header Compression
Configuring Real-Time Header Compression with Frame Relay Encapsulation
Configuring Discard Eligibility
Configuring DLCI Priority Levels
Monitoring and Maintaining the Frame Relay Connections
Frame Relay Configuration Examples
IETF Encapsulation on the Interface Example
IETF Encapsulation on a per-DLCI Basis Example
Static Address Mapping Examples
Two Routers in Static Mode Example
Frame Relay Multipoint Subinterface with Dynamic Addressing Example
IPX Routes over Frame Relay Subinterfaces Example
Unnumbered IP over a Point-to-Point Subinterface Example
Transparent Bridging Using Subinterfaces Example
Frame Relay Traffic Shaping Examples
Traffic Shaping with Three Point-to-Point Subinterfaces Example
Traffic Shaping with ForeSight Example
Enhanced Local Management Interface Example
Backward Compatibility Example
Booting from a Network Server over Frame Relay Example
Frame Relay End-to-End Keepalive Examples
End-to-End Keepalive Bidirectional Mode with Default Configuration Example
End-to-End Keepalive Request Mode with Default Configuration Example
End-to-End Keepalive Request Mode with Modified Configuration Example
PPP over Frame Relay DTE Example
PPP over Frame Relay DCE Example
Frame Relay Switching Examples
PVC Switching Configuration Example
Hybrid DTE/DCE PVC Switching Example
Switching over an IP Tunnel Example
FRF.9 Compression Configuration Examples
FRF.9 Compression for Subinterfaces Using the frame-relay map Command Example
FRF.9 Compression for Subinterfaces Example
TCP/IP Header Compression Examples
IP Map with Inherited TCP/IP Header Compression Example
Using an IP Map to Override TCP/IP Header Compression Example
Disabling TCP/IP Header Compression Examples
Disabling Inherited TCP/IP Header Compression Example
Disabling Explicit TCP/IP Header Compression Example
Configuring Frame Relay
This chapter describes the tasks for configuring Frame Relay on a router or access server. For further general information about Frame Relay, see the "Wide-Area Networking Overview" chapter at the beginning of this book. The following new features are included in this chapter:
•
Frame Relay end-to-end keepalives
•
For a complete description of the Frame Relay commands mentioned in this chapter, refer to the "Frame Relay Commands" chapter in the Cisco IOS Wide-Area Networking Command Reference. To locate documentation of other commands that appear in this chapter, use the command reference master index or search online.
See the following chapters in other Cisco publications for information on the topics indicated below:
Cisco Frame Relay MIB
The Cisco Frame Relay MIB adds extensions to the standard Frame Relay MIB (RFC 1315). It provides additional link-level and VC-level information and statistics that are mostly specific to Cisco Frame Relay implementation. This MIB provides SNMP network management access to most of the information covered by the show frame-relay commands, such as, show frame-relay lmi, show frame-relay pvc, show frame-relay map, and show frame-relay svc.
Frame Relay Hardware Configurations
You can create Frame Relay connections using one of the following hardware configurations:
•
•
Note
The CSU/DSU converts V.35 or RS-449 signals to the properly coded T1 transmission signal for successful reception by the Frame Relay network. Figure 13 illustrates the connections between the different components.
Figure 13 Typical Frame Relay Configuration
The Frame Relay interface actually consists of one physical connection between the network server and the switch that provides the service. This single physical connection provides direct connectivity to each device on a network.
Frame Relay Configuration Task List
You must follow certain required, basic steps to enable Frame Relay for your network. In addition, you can customize Frame Relay for your particular network needs and monitor Frame Relay connections. The following sections outline these tasks:
•
•
The tasks described in the following sections are used to enhance or customize your Frame Relay:
•
•
•
•
•
See the "Frame Relay Configuration Examples" section at the end of this chapter for ideas of how to configure Frame Relay on your network. See the "Frame Relay Commands" chapter in the Cisco IOS Wide-Area Networking Command Reference for information about the Frame Relay commands listed in the following tasks. Use the index or search online for documentation of other commands.
Enabling Frame Relay Encapsulation on an Interface
To enable Frame Relay encapsulation on the interface level, use the following commands beginning in global configuration mode:
Frame Relay supports encapsulation of all supported protocols in conformance with RFC 1490, allowing interoperability between multiple vendors. Use the Internet Engineering Task Force (IETF) form of Frame Relay encapsulation if your router or access server is connected to another vendor's equipment across a Frame Relay network. IETF encapsulation is supported either at the interface level or on a per-VC basis.
Shut down the interface prior to changing encapsulation types. Although shutting down the interface is not required, it ensures that the interface is reset for the new encapsulation.
For an example of enabling Frame Relay encapsulation on an interface, see the "IETF Encapsulation Examples" section later in this chapter.
Configuring Dynamic or Static Address Mapping
Dynamic address mapping uses Frame Relay Inverse ARP to request the next hop protocol address for a specific connection, given its known DLCI. Responses to Inverse ARP requests are entered in an address-to-DLCI mapping table on the router or access server; the table is then used to supply the next hop protocol address or the DLCI for outgoing traffic.
Inverse ARP is enabled by default for all protocols it supports, but can be disabled for specific protocol-DLCI pairs. As a result, you can use dynamic mapping for some protocols and static mapping for other protocols on the same DLCI. You can explicitly disable Inverse ARP for a protocol-DLCI pair if you know that the protocol is not supported on the other end of the connection. See the "Disabling or Reenabling Frame Relay Inverse ARP" section later in this chapter for more information.
See the following sections for further details on configuring dynamic or static address mapping:
Configuring Dynamic Mapping
Inverse ARP is enabled by default for all protocols enabled on the physical interface. Packets are not sent out for protocols that are not enabled on the interface.
Because Inverse ARP is enabled by default, no additional command is required to configure dynamic mapping on an interface.
Configuring Static Mapping
A static map links a specified next hop protocol address to a specified DLCI. Static mapping removes the need for Inverse ARP requests; when you supply a static map, Inverse ARP is automatically disabled for the specified protocol on the specified DLCI.
You must use static mapping if the router at the other end either does not support Inverse ARP at all or does not support Inverse ARP for a specific protocol that you want to use over Frame Relay.
To establish static mapping according to your network needs, use one of the following commands in interface configuration mode:
The supported protocols and the corresponding keywords to enable them are as follows:
•
•
•
•
•
•
•
You can greatly simplify the configuration for the Open Shortest Path First (OSPF) protocol by adding the optional broadcast keyword when doing this task. Refer to the frame-relay map command description in the Cisco IOS Wide-Area Networking Command Reference and the examples at the end of this chapter for more information about using the broadcast keyword.
For examples of establishing static address mapping, refer to the section "Static Address Mapping Examples" later in this chapter.
Configuring the LMI
Beginning with Cisco IOS Release 11.2, the software supports Local Management Interface (LMI) autosense, which enables the interface to determine the LMI type supported by the switch. Support for LMI autosense means that you are no longer required to configure the LMI explicitly.
See the following sections for further details on configuring the LMI:
•
For information on using Enhanced Local Management Interface with traffic shaping, see the "Configuring Frame Relay Traffic Shaping" section later in this chapter.
For an example of configuring the LMI, see the "Pure Frame Relay DCE Example" section later in this chapter.
Activating LMI Autosense
LMI autosense is active in the following situations:
•
•
•
•
See the following sections for additional information concerning activating LMI autosense:
Status Request
When LMI autosense is active, it sends out a full status request, in all three LMI flavors, to the switch. The order is ANSI, ITU, cisco but is done in rapid succession. Unlike previous software capability, we can now listen in on both DLCI 1023 (cisco LMI) and DLCI 0 (ANSI and ITU) simultaneously.
Status Messages
One or more of the status requests will elicit a reply (status message) from the switch. The router will decode the format of the reply and configure itself automatically. If more than one reply is received, the router will configure itself with the type of the last received reply. This is to accommodate intelligent switches that can handle multiple formats simultaneously.
LMI Autosense
If LMI autosense is unsuccessful, an intelligent retry scheme is built in. Every N391 interval (default is 60 seconds, which is 6 keep exchanges at 10 seconds each), LMI autosense will attempt to ascertain the LMI type. For more information about N391, see the frame-relay lmi-n391dte command in the "Frame Relay Commands" chapter of the Cisco IOS Wide-Area Networking Command Reference.
The only visible indication to the user that LMI autosense is underway is when debug frame lmi is turned on. Every N391 interval, the user will now see three rapid status enquiries coming out of the serial interface. One in ANSI, one in ITU and one in cisco LMI-type.
Configuration Options
No configuration options are provided; LMI autosense is transparent to the user. You can turn off LMI autosense by explicitly configuring an LMI type. The LMI type must be written into NVRAM so that next time the router powers up, LMI autosense will be inactive. At the end of autoinstall, a frame-relay lmi-type xxx statement is included within the interface configuration. This configuration is not automatically written to NVRAM; you must explicitly write the configuration to NVRAM by using the copy system:running-config or copy nvram:startup-config commands.
Explicitly Configuring the LMI
Frame Relay software supports the industry-accepted standards for addressing the LMI, including the Cisco specification. If you want to configure the LMI and thus deactivate LMI autosense, perform the tasks in the following sections:
•
•
•
Setting the LMI Type
If the router or access server is attached to a public data network (PDN), the LMI type must match the type used on the public network. Otherwise, the LMI type can be set to suit the needs of your private Frame Relay network.
You can set one of three types of LMIs on our devices: ANSI T1.617 Annex D, Cisco, and ITU-T Q.933 Annex A. To do so, use the following commands beginning in interface configuration mode:
Step 1
frame-relay lmi-type {ansi | cisco | q933a}
Sets the LMI type.
Step 2
copy nvram:startup-config destination
Writes the LMI type to NVRAM.
For an example of setting the LMI type, see the "Pure Frame Relay DCE Example" section later in this chapter.
Setting the LMI Keepalive Interval
A keepalive interval must be set to configure the LMI. By default, this interval is 10 seconds and, per the LMI protocol, must be less than the corresponding interval on the switch. To set the keepalive interval, use the following command in interface configuration mode:
To disable keepalives on networks that do not utilize LMI, use the no keepalive interface configuration command. For an example of how to specify an LMI keepalive interval, see the "Two Routers in Static Mode Example" section later in this chapter.
Setting the LMI Polling and Timer Intervals
You can set various optional counters, intervals, and thresholds to fine-tune the operation of your LMI DTE and DCE devices. Set these attributes by using one or more of the following commands in interface configuration mode:
See the "Frame Relay Commands" chapter in the Cisco IOS Wide-Area Networking Command Reference for polling and timing interval commands.
Configuring Frame Relay SVCs
Access to Frame Relay networks is made through private leased lines at speeds ranging from 56 kbps to 45 Mbps. Frame Relay is a connection-oriented packet-transfer mechanism that establishes VCs between endpoints.
Switched virtual circuits (SVCs) allow access through a Frame Relay network by setting up a path to the destination endpoints only when the need arises and tearing down the path when it is no longer needed.
SVCs can coexist with PVCs in the same sites and routers. For example, routers at remote branch offices might set up PVCs to the central headquarters for frequent communication, but set up SVCs with each other as needed for intermittent communication. As a result, any-to-any communication can be set up without any-to-any PVCs.
On SVCs, quality of service (QoS) elements can be specified on a call-by-call basis to request network resources.
SVC support is offered in the Enterprise image on Cisco platforms that include a serial or HSSI interface.
You must have the following services before Frame Relay SVCs can operate:
•
•
For examples of configuring Frame Relay SVCs, see the "SVC Configuration Examples" section later in this chapter.
Operating SVCs
SVC operation requires that the Data Link layer (Layer 2) be set up, running ITU-T Q.922 Link Access Procedures to Frame mode bearer services (LAPF), prior to signalling for an SVC. Layer 2 sets itself up as soon as SVC support is enabled on the interface, if both the line and the line protocol are up. When the SVCs are configured and demand for a path occurs, the Q.933 signalling sequence is initiated. Once the SVC is set up, data transfer begins.
Q.922 provides a reliable link layer for Q.933 operation. All Q.933 call control information is transmitted over DLCI 0; this DLCI is also used for the management protocols specified in ANSI T1.617 Annex D or Q.933 Annex A.
You must enable SVC operation at the interface level. Once it is enabled at the interface level, it is enabled on any subinterfaces on that interface. One signalling channel, DLCI 0, is set up for the interface, and all SVCs are controlled from the physical interface.
Enabling Frame Relay SVC Service
To enable Frame Relay SVC service and set up SVCs, perform the tasks in the following sections. The subinterface tasks are not required, but offer additional flexibility for SVC configuration and operation. The LAPF tasks are not required and not recommended unless you understand thoroughly the impacts on your network.
•
•
•
•
•
•
For examples of configuring Frame Relay SVCs, see the "SVC Configuration Examples" section later in this chapter.
Configuring SVCs on a Physical Interface
To enable SVC operation on a Frame Relay interface, use the following commands beginning in global configuration mode:
Map-group details are specified with the map-list command.
Configuring SVCs on a Subinterface
To configure Frame Relay SVCs on a subinterface, complete all the commands in the previous section, except assigning a the map group. After the physical interface is configured, use the following commands beginning in global configuration mode:
Configuring a Map Class
Perform the following tasks to configure a map class:
•
•
•
•
•
To configure a map class, use the following commands beginning in global configuration mode:
Step 1
map-class frame-relay map-class-name
Specifies Frame Relay map class name and enters map class configuration mode.
Step 2
frame-relay custom-queue-list list-number
Specifies a custom queue list to be used for the map class.
Step 3
frame-relay priority-group list-number
Assigns a priority queue to VCs associated with the map class.
Step 4
frame-relay adaptive-shaping [becn | foresight]1
Enables the type of BECN feedback to throttle the frame-transmission rate.
Step 5
frame-relay cir in bps
Specifies the inbound committed information rate (CIR).
Step 6
frame-relay cir out bps
Specifies the outbound committed information rate (CIR).
Step 7
frame-relay mincir in bps 2
Sets the minimum acceptable incoming CIR.
Step 8
frame-relay mincir out bps 2
Sets the minimum acceptable outgoing CIR.
Step 9
frame-relay bc in bits 2
Sets the incoming committed burst size (Bc).
Step 10
frame-relay bc out bits 2
Sets the outgoing committed burst size (Bc).
Step 11
frame-relay be in bits 2
Sets the incoming excess burst size (Be).
Step 12
frame-relay be out bits 2
Sets the outgoing excess burst size (Be).
Step 13
frame-relay idle-timer seconds 2
Sets the idle timeout interval.
1 This command replaces the frame-relay becn-response-enable command, which will be removed in a future Cisco IOS release. If you use the frame-relay becn-response-enable command in scripts, you should replace it with the frame-relay adaptive-shaping becn command.
2 The in and out keywords are optional. Configuring the command without the in and out keywords will apply that value to both the incoming and outgoing traffic values for the SVC setup. For example, frame-relay cir 56000 applies 56000 to both incoming and outgoing traffic values for setting up the SVC.
You can define multiple map classes. A map class is associated with a static map, not with the interface or subinterface itself. Because of the flexibility this association allows, you can define different map classes for different destinations.
Configuring a Map Group with E.164 or X.121 Addresses
After you have defined a map group for an interface, you can associate the map group with a specific source and destination address to be used. You can specify E.164 addresses or X.121 addresses for the source and destination. To specify the map group to be associated with a specific interface, use the following command in global configuration mode:
Associating the Map Class with Static Protocol Address Maps
To define the protocol addresses under a map-list command and associate each protocol address with a specified map class, use the class command. Use this command for each protocol address to be associated with a map class. To associate a map class with a protocol address, use the following command in map list configuration mode:
The ietf keyword specifies RFC 1490 encapsulation; the broadcast keyword specifies that broadcasts must be carried. The trigger keyword, which can be configured only if broadcast is also configured, enables a broadcast packet to trigger an SVC. If an SVC already exists that uses this map class, the SVC will carry the broadcast.
Configuring LAPF Parameters
Frame Relay Link Access Procedure for Frame Relay (LAPF) commands are used to tune Layer 2 system parameters to work well with the Frame Relay switch. Normally, you do not need to change the default settings. However, if the Frame Relay network indicates that it does not support the Frame Reject frame (FRMR) at the LAPF Frame Reject procedure, use the following command in interface configuration mode:
no frame-relay lapf frmr
Selects not to send FRMR frames at the LAPF Frame Reject procedure.
By default, the Frame Reject frame is sent at the LAPF Frame Reject procedure.
Note
If you must change Layer 2 parameters for your network environment and you understand the resulting functional change, use the following commands as needed:
Configuring Frame Relay Traffic Shaping
Traffic shaping applies to both PVCs and SVCs. For information about creating and configuring SVCs, see the "Configuring Frame Relay SVCs" section of this chapter.
To configure Frame Relay traffic shaping, perform the tasks in the following sections:
•
•
•
•
•
•
•
•
The following Frame Relay traffic shaping capabilities were introduced with Cisco IOS Release 11.2:
•
•
•
Note
For examples of configuring Frame Relay traffic shaping, see the "Frame Relay Traffic Shaping Examples" section later in this chapter.
Defining VCs for Different Types of Traffic
By defining separate VCs for different types of traffic and specifying queueing and an outbound traffic rate for each VC, you can provide guaranteed bandwidth for each type of traffic. By specifying different traffic rates for different VCs over the same line, you can perform virtual time division multiplexing. By throttling outbound traffic from high-speed lines in central offices to lower-speed lines in remote locations, you can ease congestion and data loss in the network; enhanced queueing also prevents congestion-caused data loss.
Enabling Frame Relay Traffic Shaping on the Interface
Enabling Frame Relay traffic shaping on an interface enables both traffic shaping and per-VC queueing on all the interface's PVCs and SVCs. Traffic shaping enables the router to control the circuit's output rate and react to congestion notification information if also configured.
To enable Frame Relay traffic shaping on the specified interface, use the following command in interface configuration mode:
frame-relay traffic-shaping
Enables Frame Relay traffic shaping and per-VC queueing.
Note
—When traffic shaping is enabled (by using the frame-relay traffic-shaping command), but a map class is not assigned to the VC
—When traffic shaping is enabled (by using the frame-relay traffic-shaping command) and a map class is assigned to the VC, but traffic-shaping parameters have not been defined in the map classTo configure a map class with traffic shaping and per-VC queueing parameters, see the sections "Specifying a Traffic Shaping Map Class for the Interface" and "Defining a Map Class with Queueing and Traffic Shaping Parameters".
Frame Relay ForeSight
ForeSight is the network traffic control software used in some Cisco switches. The Cisco Frame Relay switch can extend ForeSight messages over a User-to-Network Interface (UNI), passing the backward congestion notification for VCs.
ForeSight allows Cisco Frame Relay routers to process and react to ForeSight messages and adjust VC level traffic shaping in a timely manner.
ForeSight must be configured explicitly on both the Cisco router and the Cisco switch. ForeSight is enabled on the Cisco router when Frame Relay traffic shaping is configured. However, the router's response to ForeSight is not applied to any VC until the frame-relay adaptive-shaping foresight command is added to the VCs map-class. When ForeSight is enabled on the switch, the switch will periodically send out a ForeSight message based on the time value configured. The time interval can range from 40 to 5000 milliseconds.
When a Cisco router receives a ForeSight message indicating that certain DLCIs are experiencing congestion, the Cisco router reacts by activating its traffic shaping function to slow down the output rate. The router reacts as it would if it were to detect the congestion by receiving a packet with the backward explicit congestion notification (BECN) bit set.
When ForeSight is enabled, Frame Relay traffic shaping will adapt to ForeSight messages and BECN messages.
For an example of configuring Foresight, see the "Traffic Shaping with ForeSight Example" section later in this chapter.
Frame Relay ForeSight Prerequisites
For Router ForeSight to work, the following conditions must exist on the Cisco router:
•
•
The following additional condition must exist on the Cisco switch:
•
Frame Relay Router ForeSight is enabled automatically when you use the frame-relay traffic-shaping command. However, you must issue the map-class frame-relay command and the frame-relay adaptive-shaping foresight command before the router will respond to ForeSight and apply the traffic shaping effect on a specific interface, subinterface, or VC.
Frame Relay Congestion Notification Methods
The difference between the BECN and ForeSight congestion notification methods is that BECN requires a user packet to be sent in the direction of the congested DLCI to convey the signal. The sending of user packets is not predictable and, therefore, not reliable as a notification mechanism. Rather than waiting for user packets to provide the congestion notification, timed ForeSight messages guarantee that the router receives notification before congestion becomes a problem. Traffic can be slowed down in the direction of the congested DLCI.
Enabling Enhanced Local Management Interface
When used in conjunction with traffic shaping, the router can respond to changes in the network dynamically. Enhanced Local Management Interface (ELMI) allows the router to learn QoS parameters from the Cisco switch and use them for traffic shaping, configuration, or management purposes. ELMI also simplifies the process of configuring traffic shaping on the router. ELMI reduces chances of specifying inconsistent or incorrect values when configuring the router.
To configure ELMI, use the following commands beginning in interface configuration mode:
Note
It is not necessary to configure traffic shaping on the interface to enable ELMI, but you may want to do so in order to know the values being used by the switch. If you want the router to respond to the QoS information received from the switch by adjusting the output rate, you must configure traffic shaping on the interface. To configure traffic shaping, use the frame-relay traffic-shaping command in interface configuration mode
For an example of configuring a Frame Relay interface with QoS autosense enabled, see the section "Enhanced Local Management Interface Example" later in this chapter.
Specifying a Traffic Shaping Map Class for the Interface
If you specify a Frame Relay map class for a main interface, all the VCs on its subinterfaces inherit all the traffic shaping parameters defined for the class.
To specify a map class for the specified interface, use the following command in beginning interface configuration mode:
frame-relay class map-class-name
Specifies a Frame Relay map class for the interface.
You can override the default for a specific DLCI on a specific subinterface by using the class VC configuration command to assign the DLCI explicitly to a different class. See the "Configuring Frame Relay Subinterfaces" section for information about setting up subinterfaces.
For an example of assigning some subinterface DLCIs to the default class and assigning others explicitly to a different class, see the "Frame Relay Traffic Shaping Examples" section later in this chapter.
Defining a Map Class with Queueing and Traffic Shaping Parameters
When defining a map class for Frame Relay, you can specify the average and peak rates (in bits per second) allowed on VCs associated with the map class. You can also specify either a custom queue list or a priority queue group to use on VCs associated with the map class.
To define a map class, use the following commands beginning in global configuration mode:
Step 1
map-class frame-relay map-class-name
Specifies a map class to define.
Step 2
frame-relay traffic-rate average [peak]
Defines the traffic rate for the map class.
Step 3
frame-relay custom-queue-list list-number
Specifies a custom queue list.
Step 4
frame-relay priority-group list-number
Specifies a priority queue list.
Step 5
frame-relay adaptive-shaping {becn | foresight}1
Selects BECN or ForeSight as congestion backward-notification mechanism to which traffic shaping adapts.
1 This command replaces the frame-relay becn-response-enable command, which will be removed in a future Cisco IOS release. If you use the frame-relay becn-response-enable command in scripts, you should replace it with the frame-relay adaptive-shaping software command.
For an example of map class backward compatibility and interoperability, see the "Backward Compatibility Example" section later in this section.
Defining Access Lists
You can specify access lists and associate them with the custom queue list defined for any map class. The list number specified in the access list and the custom queue list tie them together. See the appropriate protocol chapters for information about defining access lists for the protocols you want to transmit on the Frame Relay network.
Defining Priority Queue Lists for the Map Class
You can define a priority list for a protocol and you can also define a default priority list. The number used for a specific priority list ties the list to the Frame Relay priority group defined for a specified map class.
For example, if you enter the frame relay priority-group 2 command for the map class fast_vcs and then you enter the priority-list 2 protocol decnet high command, that priority list is used for the fast_vcs map class. The average and peak traffic rates defined for the fast_vcs map class are used for DECnet traffic.
Defining Custom Queue Lists for the Map Class
You can define a queue list for a protocol and a default queue list. You can also specify the maximum number of bytes to be transmitted in any cycle. The number used for a specific queue list ties the list to the Frame Relay custom queue list defined for a specified map class.
For example, if you enter the frame relay custom-queue-list 1 command for the map class slow_vcs and then you enter the queue-list 1 protocol ip list 100 command, that queue list is used for the slow_vcs map class; access-list 100 definition is also used for that map class and queue. The average and peak traffic rates defined for the slow_vcs map class are used for IP traffic that meets the access list 100 criteria.
Customizing Frame Relay for Your Network
Perform the tasks in the following sections to customize Frame Relay:
•
•
•
•
•
•
•
•
•
•
•
•
Configuring Frame Relay End-to-End Keepalives
Frame Relay end-to-end keepalives enable monitoring of PVC status for network monitoring or backup applications and are configurable on a per-PVC basis with configurable timers. The Frame Relay switch within the local PVC segment deduces the status of the remote PVC segment through a Network-to-Network interface (NNI) and reports the status to the local router. If LMI support within the switch is not end-to-end, end-to-end keepalives are the only source of information about the remote router. End-to-end keepalives verify that data is getting through to a remote device via end-to-end communication.
Each PVC connecting two end devices needs two separate keepalive systems, because the upstream path may not be the same as the downstream path. One system sends out requests and handles responses to those requests—the send side—while the other system handles and replies to requests from the device at the other end of the PVC—the receive side. The send side on one device communicates with the receive side on the other device, and vice versa.
The send side sends out a keepalive request and waits for a reply to its request. If a reply is received before the timer expires, a send side, Frame Relay end-to-end keepalives is recorded. If no reply is received before the timer expires, an error event is recorded. A number of the most recently recorded events are examined. If enough error events are accumulated, the keepalive status of the VC is changed from up to down, or if enough consecutive successful replies are received, the keepalive status of the VC will be changed from down to up. The number of events that will be examined is called the event window.
The receive side is similar to the send side. The receive side waits for requests and sends out replies to those requests. If a request is received before the timer expires, a success event is recorded. If a request is not received, an error event is recorded. If enough error events occur in the event window, the PVC state will be changed from up to down. If enough consecutive success events occur, the state will be changed from down to up.
End-to-end keepalives can be configured in one of four modes: bidirectional, request, reply, or passive-reply.
•
•
•
•
Because end-to-end keepalives allow traffic flow in both directions, they can be used to carry control and configuration information from end-to-end. Consistency of information between end hosts is critical in applications such as those relating to prioritized traffic and Voice Over Frame Relay. While SVCs can convey such information within end-to-end signaling messages, PVCs will benefit from a bidirectional communication mechanism.
End-to-end keepalives are derived from the Frame Relay LMI protocol and work between peer Cisco communications devices. The key difference is that rather than run over the signaling channel, as is the case with LMI, end-to-end keepalives run over individual data channels.
Encapsulation of keepalive packets is proprietary; therefore, the feature is available only on Cisco devices running a software release that supports the Frame Relay End-to-End Keepalive feature.
You must configure both ends of a VC to send keepalives. If one end is configured as bidirectional, the other end must also be configured as bidirectional. If one end is configured as request, the other end must be configured as reply or passive-reply. If one end is configured as reply or passive-reply, the other end must be configured as request
To configure Frame Relay end-to-end keepalives, use the following commands beginning in global configuration mode:
The four modes determine the type of keepalive traffic each device sends and responds to:
•
•
•
•
For an example of configuring bidirectional or request modes with default values, see the sections "End-to-End Keepalive Bidirectional Mode with Default Configuration Example" or "End-to-End Keepalive Request Mode with Default Configuration Example," and for an example of configuring request mode with modified values, see the section "End-to-End Keepalive Request Mode with Modified Configuration Example" later in this chapter.
You can modify the end-to-end keepalives default parameter values by using any of the following map-class configuration commands:
Verifying Frame Relay End-to-End Keepalives
To monitor the status of Frame Relay end-to-end keepalives, use the following command in EXEC configuration mode:
Router# show frame-relay end-to-end keepalive interface
Shows the status of Frame Relay end-to-end keepalives.
Configuring PPP over Frame Relay
Point-to-point protocol (PPP) over Frame Relay allows a router to establish end-to-end PPP sessions over Frame Relay. This is done over a PVC, which is the only circuit currently supported. The PPP session does not occur unless the associated Frame Relay PVC is in an "active" state. The Frame Relay PVC can coexist with other circuits using different Frame Relay encapsulation methods, such as RFC 1490 and the Cisco proprietary method, over the same Frame Relay link. There can be multiple PPP over Frame Relay circuits on one Frame Relay link.
One PPP connection resides on one virtual access interface. This is internally created from a virtual template interface, which contains all necessary PPP and network protocol information and is shared by multiple virtual access interfaces. The virtual access interface is coexistent with the creation of the Frame Relay circuit when the corresponding DLCI is configured. Hardware compression and fancy queueing algorithms, such as weighted fair queueing, custom queueing, and priority queueing, are not applied to virtual access interfaces.
PPP over Frame Relay is only supported on IP. IP datagrams are transported over the PPP link using RFC 1973 compliant Frame Relay framing. The frame format is shown in Figure 14.
Figure 14 PPP over Frame Relay Frame Format
Table 6 lists the Frame Relay frame format components illustrated in Figure 14.
Figure 15 shows remote users running PPP to access their Frame Relay corporate networks.
Figure 15 PPP over Frame Relay Scenario
Enabling PPP over Frame Relay
Before configuring PPP over Frame Relay, Frame Relay must be enabled on the router using the encapsulation frame-relay command. The only task required to implement PPP over Frame Relay is to configure the interface with the locally terminated PVC and the associated virtual template for PPP and IP, as described in the following section.
After configuring Frame Relay encapsulation on the Cisco router or access server, you must configure the physical interface with the PVC and apply a virtual template with PPP encapsulation to the DLCI that it applies to.
To configure the physical interface that will carry the PPP session and link it to the appropriate virtual template interface, perform the following task in interface configuration mode:
Router(config-if)# frame-relay interface-dlci dlci [ppp virtual-template-name]
Defines the PVC and map it to the virtual template.
For an example of configuring PPP over Frame Relay, see the section "PPP over Frame Relay Examples" or "PPP over Frame Relay DCE Example" later in this chapter.
Configuring Frame Relay Subinterfaces
For a general explanation of Frame Relay Subinterfaces, read the following section "Understanding Frame Relay Subinterfaces."
To configure the Frame Relay subinterface and define subinterface addressing, perform the tasks in the following sections:
•
•
•
For a selection of subinterface configuration examples, see the "Subinterface Examples" section later in this chapter.
Understanding Frame Relay Subinterfaces
Frame Relay subinterfaces provide a mechanism for supporting partially meshed Frame Relay networks. Most protocols assume transitivity on a logical network; that is, if station A can talk to station B, and station B can talk to station C, then station A should be able to talk to station C directly. Transitivity is true on LANs, but not on Frame Relay networks unless A is directly connected to C.
Additionally, certain protocols such as AppleTalk and transparent bridging cannot be supported on partially meshed networks because they require "split horizon," in which a packet received on an interface cannot be sent from the same interface even if received and transmitted on different VCs.
Configuring Frame Relay subinterfaces ensures that a single physical interface is treated as multiple virtual interfaces, which allows you to overcome split horizon rules. Packets received on one virtual interface can be forwarded to another virtual interface, even if they are configured on the same physical interface.
Subinterfaces address the limitations of Frame Relay networks by providing a way to subdivide a partially meshed Frame Relay network into a number of smaller, fully meshed (or point-to-point) subnetworks. Each subnetwork is assigned its own network number and appears to the protocols as if it is reachable through a separate interface. (Note that point-to-point subinterfaces can be unnumbered for use with IP, reducing the addressing burden that might otherwise result.)
Figure 16 shows a five-node Frame Relay network that is partially meshed (Network A). If the entire network is viewed as a single subnetwork (with a single network number assigned), most protocols assume that node A can transmit a packet directly to node E, when in fact it must be relayed through nodes C and D. This network can be made to work with certain protocols (for example, IP) but will not work at all with other protocols (for example, AppleTalk) because nodes C and D will not relay the packet out the same interface on which it was received. One way to make this network work fully is to create a fully meshed network (Network B), but doing so requires a large number of PVCs, which may not be economically feasible.
Using subinterfaces, you can subdivide the Frame Relay network into three smaller subnetworks (Network C) with separate network numbers. Nodes A, B, and C are connected to a fully meshed network, and nodes C and D, as well as nodes D and E are connected via point-to-point networks. In this configuration, nodes C and D can access two subinterfaces and can, therefore, forward packets without violating split horizon rules. If transparent bridging is being used, each subinterface is viewed as a separate bridge port.
Subinterfaces can be configured for multipoint or point-to-point communication. (There is no default.) To configure subinterfaces on a Frame Relay network, use the following commands beginning in global configuration mode:
For an example of configuring Frame Relay subinterfaces, see the "Subinterface Examples" section later in this chapter.
Defining Subinterface Addressing
For point-to-point subinterfaces, the destination is presumed to be known and is identified or implied in the frame-relay interface-dlci command. For multipoint subinterfaces, the destinations can be dynamically resolved through the use of Frame Relay Inverse ARP or can be statically mapped through the use of the frame-relay map command.
See the following sections for further information about subinterface addressing:
•
•
•
•
For subinterface addressing examples, see the "Static Address Mapping Examples" section later in this chapter.
Figure 16 shows subinterfaces on a partially meshed Frame Relay network.
Figure 16 Using Subinterfaces to Provide Full Connectivity on a Partially Meshed
Frame Relay Network
Addressing on Point-to-Point Subinterfaces
If you specified a point-to-point subinterface in the preceding procedure, use the following command in subinterface configuration mode:
frame-relay interface-dlci dlci
Associates the selected point-to-point subinterface with a DLCI.
Note
For an explanation of the many available options for this command, refer to the Cisco IOS Wide-Area Networking Command Reference.
If you define a subinterface for point-to-point communication, you cannot reassign the same subinterface number to be used for multipoint communication without first rebooting the router or access server. Instead, you can simply avoid using that subinterface number and use a different subinterface number instead.
Addressing on Multipoint Subinterfaces
If you specified a multipoint subinterface in the preceding procedure, perform the configuration tasks in the following sections:
•
•
You can configure some protocols for dynamic address mapping and others for static address mapping.
Accepting Inverse ARP for Dynamic Address Mapping on Multipoint Subinterfaces
Dynamic address mapping uses Frame Relay Inverse ARP to request the next hop protocol address for a specific connection, given a DLCI. Responses to Inverse ARP requests are entered in an address-to-DLCI mapping table on the router or access server; the table is then used to supply the next hop protocol address or the DLCI for outgoing traffic.
Since the physical interface is now configured as multiple subinterfaces, you must provide information that distinguishes a subinterface from the physical interface and associates a specific subinterface with a specific DLCI.
To associate a specific multipoint subinterface with a specific DLCI, use the following command in interface configuration mode:
frame-relay interface-dlci dlci
Associates a specified multipoint subinterface with a DLCI.
Inverse ARP is enabled by default for all protocols it supports, but can be disabled for specific protocol-DLCI pairs. As a result, you can use dynamic mapping for some protocols and static mapping for other protocols on the same DLCI. You can explicitly disable Inverse ARP for a protocol-DLCI pair if you know the protocol is not supported on the other end of the connection. See the "Disabling or Reenabling Frame Relay Inverse ARP" section later in this chapter for more information.
Because Inverse ARP is enabled by default for all protocols that it supports, no additional command is required to configure dynamic address mapping on a subinterface.
For an example of configuring Frame Relay multipoint subinterfaces with dynamic address mapping, see the "Frame Relay Multipoint Subinterface with Dynamic Addressing Example" section later in this chapter.
Configuring Static Address Mapping on Multipoint Subinterfaces
A static map links a specified next hop protocol address to a specified DLCI. Static mapping removes the need for Inverse ARP requests; when you supply a static map, Inverse ARP is automatically disabled for the specified protocol on the specified DLCI.
You must use static mapping if the router at the other end either does not support Inverse ARP at all or does not support Inverse ARP for a specific protocol that you want to use over Frame Relay.
To establish static mapping according to your network needs, use one of the following commands in interface configuration mode:
The supported protocols and the corresponding keywords to enable them are as follows:
•
•
•
•
•
•
•
The broadcast keyword is required for routing protocols such as OSI protocols and the Open Shortest Path First (OSPF) protocol. See the frame-relay map command description in the Cisco IOS Wide-Area Networking Command Reference and the examples at the end of this chapter for more information about using the broadcast keyword.
For an example of establishing static address mapping on multipoint subinterfaces, see the "Two Routers in Static Mode Example," "AppleTalk Routing Example," "DECnet Routing Example," and "IPX Routing Example" sections later in this chapter.
Configuring Transparent Bridging for Frame Relay
You can configure transparent bridging for point-to-point or point-to-multipoint subinterfaces on Frame Relay encapsulated serial and HSSI interfaces. See the following sections for further information:
•
For an example of Frame Relay transparent bridging, see the section "Transparent Bridging Using Subinterfaces Example" later in this chapter.
Note
Point-to-Point Subinterfaces
To configure transparent bridging for point-to-point subinterfaces, use the following commands beginning in global configuration mode:
Point-to-Multipoint Interfaces
To configure transparent bridging for point-to-multipoint subinterfaces, use the following commands beginning in global configuration mode:
Configuring a Backup Interface for a Subinterface
Both point-to-point and multipoint Frame Relay subinterfaces can be configured with a backup interface. This approach allows individual PVCs to be backed up in case of failure rather than depending on the entire Frame Relay connection to fail before the backup takes over. You can configure a subinterface for backup on failure only, not for backup based on loading of the line.
If the main interface has a backup interface, it will have precedence over the subinterface's backup interface in the case of complete loss of connectivity with the Frame Relay network. As a result, a subinterface backup is activated only if the main interface is up, or if the interface is down and does not have a backup interface defined. If a subinterface fails while its backup interface is in use, and the main interface goes down, the backup subinterface remains connected.
To configure a backup interface for a Frame Relay subinterface, use the following commands beginning in global configuration mode:
Configuring Frame Relay Switching
Frame Relay switching is a means of switching packets based on the DLCI, which can be considered the Frame Relay equivalent of a MAC address. You perform switching by configuring your Cisco router or access server into a Frame Relay network. There are two parts to a Frame Relay network:
•
•
Figure 17 illustrates Frame Relay switched networks. Routers A, B, and C are Frame Relay DTEs connected to each other via a Frame Relay network.
Figure 17 Frame Relay Switched Network
To configure Frame Relay switching, perform the tasks in the following sections:
•
•
For an example of Frame Relay switching, see the section "Frame Relay Switching Examples" later in this chapter.
Enabling Frame Relay Switching
You must enable packet switching before you can configure it on a Frame Relay DTE or DCE, or with Network-to-Network Interface (NNI) support. Do so by using the following command in global configuration mode before configuring the switch type:
For a selection of Frame Relay switching examples, see the "Frame Relay Switching Examples" section later in this chapter.
Configuring a Frame Relay DTE Device, DCE Switch, or NNI Support
You can configure an interface as a DTE device or a DCE switch, or as a switch connected to a switch to support NNI connections. (DCE is the default.) To do so, use the following command in interface configuration mode:
frame-relay intf-type [dce | dte | nni]
Configures a Frame Relay DTE device or DCE switch.
For an example of configuring a DTE device or DCE switch, see the "Hybrid DTE/DCE PVC Switching Example" section later in this chapter. For an example of configuring NNI support, see the "Pure Frame Relay DCE Example" section later in this chapter.
Specifying the Static Route
You must specify a static route for PVC switching. To do so, use the following command in interface configuration mode:
frame-relay route in-dlci interface out-interface-type out-interface-number out-dlci
Specifies a static route for PVC switching.
For an example of specifying a static route, see the section "Pure Frame Relay DCE Example" later in this chapter.
Note
Disabling or Reenabling Frame Relay Inverse ARP
Frame Relay Inverse ARP is a method of building dynamic address mappings in Frame Relay networks running AppleTalk, Banyan VINES, DECnet, IP, Novell IPX, and XNS. Inverse ARP allows the router or access server to discover the protocol address of a device associated with the VC.
Inverse ARP creates dynamic address mappings, as contrasted with the frame-relay map command, which defines static mappings between a specific protocol address and a specific DLCI (see the section "Configuring Dynamic or Static Address Mapping" earlier in this chapter for further information).
Inverse ARP is enabled by default but can be disabled explicitly for a given protocol and DLCI pair. Disable or reenable Inverse ARP under the following conditions:
•
•
Note
You do not need to enable or disable Inverse ARP if you have a point-to-point interface, because there is only a single destination and discovery is not required.
To select Inverse ARP or disable it, use one of the following commands in interface configuration mode:
Creating a Broadcast Queue for an Interface
Very large Frame Relay networks might have performance problems when many DLCIs terminate in a single router or access server that must replicate routing updates and service advertising updates on each DLCI. The updates can consume access-link bandwidth and cause significant latency variations in user traffic; the updates can also consume interface buffers and lead to higher packet rate loss for both user data and routing updates.
To avoid such problems, you can create a special broadcast queue for an interface. The broadcast queue is managed independently of the normal interface queue, has its own buffers, and has a configurable size and service rate.
A broadcast queue is given a maximum transmission rate (throughput) limit measured in both bytes per second and packets per second. The queue is serviced to ensure that no more than 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 transmission rate limit in any second is the first of the two rate limits that is reached.
To create a broadcast queue, use the following command in interface configuration mode:
frame-relay broadcast-queue size byte-rate packet-rate
Creates a broadcast queue for an interface.
Configuring Payload Compression
You can configure payload compression on point-to-point or multipoint interfaces or subinterfaces. Payload compression uses the Stacker method to predict what the next character in the frame will be. Because the prediction is done packet-by-packet, the dictionary is not conserved across packet boundaries.
Payload compression on each VC consumes approximately 40 kilobytes for dictionary memory.
To configure payload compression on a specified multipoint interface or subinterface, use the following command in interface configuration mode:
frame-relay map protocol protocol-address dlci payload-compress packet-by-packet
Enables payload compression on a multipoint interface.
To configure payload compression on a specified point-to-point interface or subinterface, use the following command in interface configuration mode:
frame-relay payload-compress packet-by-packet
Enables payload compression on a point-to-point interface.
Configuring Standard-Based FRF.9 Compression
Frame Relay compression can now occur on the VIP board, on the Compression Service Adapter (CSA), or on the main CPU of the router. FRF9 is standard-based and, therefore, provides multivendor compatibility. FRF.9 compression uses higher compression ratios, allowing more data to be compressed for faster transmission. FRF.9 compression provides the ability to maintain multiple decompression/compression histories on a per-DLCI basis.
The CSA hardware has been in use on the Cisco 7200 series and Cisco 7500 series platforms, but it has had no support for Frame Relay compression. The CSA can be used in the Cisco 7200 series or in the second-generation Versatile Interface Processor (VIP2) in all Cisco 7500 series routers. The specific VIP2 model required for the CSA is VIP2-40, which has 2 MB of SRAM and 32 MB of DRAM.
See the following sections for further information on FRF.9 compression:
•
•
•
Selecting FRF.9 Compression Method
The router enables compression in the following order:
1.
2.
3.
Configuring FRF.9 Compression Using Map Statements
You can control where you want compression to occur by specifying a specific interface. To enable FRF.9 compression on a specific CSA, VIP CPU, or host CPU, use the following commands beginning in global configuration mode:
Configuring FRF.9 Compression on the Subinterface
To configure FRF.9 compression on the subinterface, use the following commands beginning in global configuration mode:
Configuring TCP/IP Header Compression
TCP/IP header compression, as described by RFC 1144, is designed to improve the efficiency of bandwidth utilization over low-speed serial links. A typical TCP/IP packet includes a 40-byte datagram header. Once a connection is established, the header information is redundant and need not be repeated in every packet that is sent. Reconstructing a smaller header that identifies the connection and indicates the fields that changed and the amount of change reduces the number of bytes transmitted. The average compressed header is 10 bytes long.
For this algorithm to function, packets must arrive in order. If packets arrive out of order, the reconstruction will appear to create regular TCP/IP packets but the packets will not match the original. Because priority queueing changes the order in which packets are transmitted, enabling priority queueing on the interface is not recommended.
See the following sections for configuring or disabling TCP/IP header compression:
•
•
•
Note
Configuring an Individual IP Map for TCP/IP Header Compression
Note
TCP/IP header compression requires Cisco encapsulation. If you need to have IETF encapsulation on an interface as a whole, you can still configure a specific IP map to use Cisco encapsulation and TCP header compression. In addition, even if you configure the interface to perform TCP/IP header compression, you can still configure a specific IP map not to compress TCP/IP headers.
You can specify whether TCP/IP header compression is active or passive. Active compression subjects every outgoing packet to TCP/IP header compression. Passive compression subjects an outgoing TCP/IP packet to header compression only if a packet had a compressed TCP/IP header when it was received.
To configure an IP map to use Cisco encapsulation and TCP/IP header compression, use the following command in interface configuration mode:
For an example of how to configure TCP header compression on an IP map, see the "FRF.9 Compression Configuration Examples" section later in this chapter.
Configuring an Interface for TCP/IP Header Compression
You can configure the interface with active or passive TCP/IP header compression. Active compression, the default, subjects all outgoing TCP/IP packets to header compression. Passive compression subjects an outgoing packet to header compression only if the packet had a compressed TCP/IP header when it was received on that interface.
To apply TCP/IP header compression to an interface, you must use the following commands in interface configuration mode:
Step 1
encapsulation frame-relay
Configures Cisco encapsulation on the interface.
Step 2
frame-relay ip tcp header-compression [passive]
Enables TCP/IP header compression.
Note
For an example of how to configure TCP header compression on an interface, see the "FRF.9 Compression Configuration Examples" section later in this chapter.
Disabling TCP/IP Header Compression
You can disable TCP/IP header compression by using either of two commands that have different effects, depending on whether Frame Relay IP maps have been explicitly configured for TCP/IP header compression or have inherited their compression characteristics from the interface.
Frame Relay IP maps that have explicitly configured TCP/IP header compression must also have TCP/IP header compression explicitly disabled.
To disable TCP/IP header compression, use one of the following commands in interface configuration mode:
For examples of turning off TCP/IP header compression, see the "Disabling Inherited TCP/IP Header Compression Example" and "Disabling Explicit TCP/IP Header Compression Example" sections later in this chapter.
Configuring Real-Time Header Compression with Frame Relay Encapsulation
Real-time Transport Protocol (RTP) is a protocol used for carrying packetized audio and video traffic over an IP network, providing end-to-end network transport functions intended for these real-time traffic applications and multicast or unicast network services. RTP is described in RFC 1889. RTP is not intended for data traffic, which uses TCP or UDP.
Although RTP header compression uses Frame Relay encapsulation, this feature is further described in the "Configuring IP Multicast Routing" chapter in the Cisco IOS IP and IP Routing Configuration Guide.
The commands for configuring this feature appear in the "IP Multicast Routing Commands" chapter of the Cisco IOS IP and IP Routing Command Reference.
Configuring Discard Eligibility
Some Frame Relay packets can be set with low priority or low time sensitivity. These will be the first to be dropped when a Frame Relay switch is congested. The mechanism that allows a Frame Relay switch to identify such packets is the discard eligibility (DE) bit.
Discard eligibility requires the Frame Relay network to be able to interpret the DE bit. Some networks take no action when the DE bit is set, and others use the DE bit to determine which packets to discard. The best interpretation is to use the DE bit to determine which packets should be dropped first and also which packets have lower time sensitivity.
You can create DE lists that identify the characteristics of packets to be eligible for discarding, and you can also specify DE groups to identify the DLCI that is affected.
To define a DE list specifying the packets that can be dropped when the Frame Relay switch is congested, use the following command in global configuration mode:
frame-relay de-list list-number {protocol protocol | interface type number} characteristic
Defines a DE list.
You can create DE lists based on the protocol or the interface, and on characteristics such as fragmentation of the packet, a specific TCP or User Datagram Protocol (UDP) port, an access list number, or a packet size. See the frame-relay de-list command in the Cisco IOS Wide-Area Networking Command Reference for further information.
To define a DE group specifying the DE list and DLCI affected, use the following command in interface configuration mode:
Configuring DLCI Priority Levels
DLCI priority levels allow you to separate different types of traffic and provides a traffic management tool for congestion problems caused by following situations:
•
•
Before you configure the DLCI priority levels, perform the following tasks:
•
•
•
•
•
Note
To configure DLCI priority levels, use the following command in interface configuration mode:
Note
Monitoring and Maintaining the Frame Relay Connections
To monitor Frame Relay connections, use any of the following commands in EXEC mode:
Frame Relay Configuration Examples
This section provides examples of Frame Relay configurations. More specific configuration examples can be found under some of the following sections:
•
•
•
•
•
•
•
•
•
•
IETF Encapsulation Examples
The following sections provide examples of IETF encapsulation on the interface level and on a per-DLCI basis:
•
•
IETF Encapsulation on the Interface Example
The following example sets IETF encapsulation at the interface level. The keyword ietf sets the default encapsulation method for all maps to IETF.
encapsulation frame-relay ietfframe-relay map ip 131.108.123.2 48 broadcastframe-relay map ip 131.108.123.3 49 broadcastIETF Encapsulation on a per-DLCI Basis Example
The following example configures IETF encapsulation on a per-DLCI basis. This configuration has the same result as the configuration in the first example.
encapsulation frame-relayframe-relay map ip 131.108.123.2 48 broadcast ietfframe-relay map ip 131.108.123.3 49 broadcast ietfStatic Address Mapping Examples
The following sections provide examples of static address mapping for two routers in static mode, and specific examples for IP, AppleTalk, DECnet, and IPX protocols:
•
Two Routers in Static Mode Example
The following example shows how to configure two routers for static mode:
Configuration for Router 1
interface serial 0ip address 131.108.64.2 255.255.255.0encapsulation frame-relaykeepalive 10frame-relay map ip 131.108.64.1 43Configuration for Router 2
interface serial 0ip address 131.108.64.1 255.255.255.0encapsulation frame-relaykeepalive 10frame-relay map ip 131.108.64.2 43AppleTalk Routing Example
The following example shows how to configure two routers to communicate with each other using AppleTalk over a Frame Relay network. Each router has a Frame Relay static address map for the other router. The use of the appletalk cable-range command indicates that this is extended AppleTalk (Phase II).
Configuration for Router 1
interface serial0ip address 172.21.59.24 255.255.255.0encapsulation frame-relayappletalk cable-range 10-20 18.47appletalk zone engframe-relay map appletalk 18.225 100 broadcastConfiguration for Router 2
interface serial2/3ip address 172.21.177.18 255.255.255.0encapsulation frame-relayappletalk cable-range 10-20 18.225appletalk zone engclockrate 2000000frame-relay map appletalk 18.47 100 broadcastDECnet Routing Example
The following example sends all DECnet packets destined for address 56.4 out on DLCI 101. In addition, any DECnet broadcasts for interface serial 1 will be sent on that DLCI.
decnet routing 32.6!interface serial 1encapsulation frame-relayframe-relay map decnet 56.4 101 broadcastIPX Routing Example
The following example shows how to send packets destined for IPX address 200.0000.0c00.7b21 out on DLCI 102:
ipx routing 000.0c00.7b3b!interface ethernet 0ipx network 2abc!interface serial 0ipx network 200encapsulation frame-relayframe-relay map ipx 200.0000.0c00.7b21 102 broadcastSubinterface Examples
The following sections provide Frame Relay subinterface examples and variations appropriate for different routed protocols and bridging:
•
•
•
•
Basic Subinterface Example
The following example shows subinterface 1 models a point-to-point subnet and subinterface 2 models a multipoint subnet:
interface serial 0encapsulation frame-relayinterface serial 0.1 point-to-pointip address 10.0.1.1 255.255.255.0frame-relay interface-dlci 42!interface serial 0.2 multipointip address 10.0.2.1 255.255.255.0frame-relay map ip 10.0.2.2 18Frame Relay Multipoint Subinterface with Dynamic Addressing Example
The following example configures two multipoint subinterfaces for dynamic address resolution. Each subinterface is provided with an individual protocol address and subnet mask, and the frame-relay interface-dlci command associates the subinterface with a specified DLCI. Addresses of remote destinations for each multipoint subinterface will be resolved dynamically.
interface serial0no ip addressencapsulation frame-relayframe-relay lmi-type ansi!interface serial0.103 multipointip address 172.21.177.18 255.255.255.0frame-relay interface-dlci 300!interface serial0.104 multipointip address 172.21.178.18 255.255.255.0frame-relay interface-dlci 400IPX Routes over Frame Relay Subinterfaces Example
The following example configures a serial interface for Frame Relay encapsulation and sets up multiple IPX virtual networks corresponding to Frame Relay subinterfaces:
ipx routing 0000.0c02.5f4f!interface serial 0encapsulation frame-relayinterface serial 0.1 multipointipx network 1frame-relay map ipx 1.000.0c07.d530 200 broadcastinterface serial 0.2 multipointipx network 2frame-relay map ipx 2.000.0c07.d530 300 broadcastFor subinterface serial 0.1, the router at the other end might be configured as follows:
ipx routinginterface serial 2 multipointipx network 1frame-relay map ipx 1.000.0c02.5f4f 200 broadcastUnnumbered IP over a Point-to-Point Subinterface Example
The following example sets up unnumbered IP over subinterfaces at both ends of a point-to-point connection. In this example, Router A functions as the DTE, and Router B functions as the DCE. Routers A and B are both attached to Token Ring networks.
Configuration for Router A
interface token-ring 0ip address 131.108.177.1 255.255.255.0!interface serial 0no ip addressencapsulation frame-relay IETF!interface serial0.2 point-to-pointip unnumbered TokenRing0ip pim sparse-modeframe-relay interface-dlci 20Configuration for Router B
frame-relay switching!interface token-ring 0ip address 131.108.178.1 255.255.255.0!interface serial 0no ip addressencapsulation frame-relay IETFbandwidth 384clockrate 4000000frame-relay intf-type dce!interface serial 0.2 point-to-pointip unnumbered TokenRing1ip pim sparse-mode!bandwidth 384frame-relay interface-dlci 20Transparent Bridging Using Subinterfaces Example
The following example shows Frame Relay DLCIs 42, 64, and 73 as separate point-to-point links with transparent bridging running over them. The bridging spanning tree views each PVC as a separate bridge port, and a frame arriving on the PVC can be relayed back out on a separate PVC.
interface serial 0encapsulation frame-relayinterface serial 0.1 point-to-pointbridge-group 1frame-relay interface-dlci 42interface serial 0.2 point-to-pointbridge-group 1frame-relay interface-dlci 64interface serial 0.3 point-to-pointbridge-group 1frame-relay interface-dlci 73SVC Configuration Examples
The following sections provide examples of Frame Relay SVC configuration for interfaces and subinterfaces:
SVC Interface Example
The following example configures a physical interface, applies a map group to the physical interface, and then defines the map group:
interface serial 0ip address 172.10.8.6encapsulation frame-relaymap-group bermudaframe-relay lmi-type q933aframe-relay svc!map-list bermuda source-addr E164 123456 dest-addr E164 654321ip 131.108.177.100 class hawaiiappletalk 1000.2 class rainbow!map-class frame-relay rainbowframe-relay idle-timer 60!map-class frame-relay hawaiiframe-relay cir in 64000frame-relay cir out 64000SVC Subinterface Example
The following example configures a point-to-point interface for SVC operation. It assumes that the main serial 0 interface has been configured for signaling and that SVC operation has been enabled on the main interface:
int s 0.1 point-point! Define the map-group; details are specified under the map-list holiday command.map-group holiday!! Associate the map-group with a specific source and destination.map-list holiday local-addr X121 <X121-addr> dest-addr E164 <E164-addr>! Specify destination protocol addresses for a map-class.ip 131.108.177.100 class hawaii IETFappletalk 1000.2 class rainbow IETF broadcast!! Define a map class and its QoS settings.map-class hawaiiframe-relay cir in 2000000frame-relay cir out 56000frame-relay be 9000!! Define another map class and its QoS settings.map-class rainbowframe-relay cir in 64000frame-relay idle-timer 2000Frame Relay Traffic Shaping Examples
The following sections provide examples of Frame Relay traffic shaping:
•
•
•
Traffic Shaping with Three Point-to-Point Subinterfaces Example
In the following example, VCs on subinterfaces Serial0.1 and Serial0.2 inherit class parameters from the main interface—namely, those defined in the map class "slow_vcs"—but the VC defined on subinterface Serial0.2 (DLCI 102) is specifically configured to use map class "fast_vcs".
Map class "slow_vcs" uses a peak rate of 9600 and average rate of 4800 bps. Because BECN feedback is enabled, the output rate will be cut back to as low as 2400 bps in response to received BECNs. This map class is configured to use custom queueing using queue-list 1. In this example, queue-list 1 has 3 queues, with the first two being controlled by access lists 100 and 115.
Map class "fast_vcs" uses a peak rate of 64000 and average rate of 16000 bps. Because BECN feedback is enabled, the output rate will be cut back to as low as 8000 bps in response to received BECNs. This map class is configured to use priority-queueing using priority-group 2.
interface serial0no ip addressencapsulation frame-relayframe-relay lmi-type ansiframe-relay traffic-shapingframe-relay class slow_vcs!interface serial0.1 point-to-pointip address 10.128.30.1 255.255.255.248ip ospf cost 200bandwidth 10frame-relay interface-dlci 101!interface serial0.2 point-to-pointip address 10.128.30.9 255.255.255.248ip ospf cost 400bandwidth 10frame-relay interface-dlci 102class fast_vcs!interface serial0.3 point-to-pointip address 10.128.30.17 255.255.255.248ip ospf cost 200bandwidth 10frame-relay interface-dlci 103!map-class frame-relay slow_vcsframe-relay traffic-rate 4800 9600frame-relay custom-queue-list 1frame-relay adaptive-shaping becn!map-class frame-relay fast_vcsframe-relay traffic-rate 16000 64000frame-relay priority-group 2frame-relay adaptive-shaping becn!access-list 100 permit tcp any any eq 2065access-list 115 permit tcp any any eq 256!priority-list 2 protocol decnet highpriority-list 2 ip normalpriority-list 2 default medium!queue-list 1 protocol ip 1 list 100queue-list 1 protocol ip 2 list 115queue-list 1 default 3queue-list 1 queue 1 byte-count 1600 limit 200queue-list 1 queue 2 byte-count 600 limit 200queue-list 1 queue 3 byte-count 500 limit 200Traffic Shaping with ForeSight Example
The following example illustrates a router configuration with traffic shaping enabled. DLCIs 100 and 101 on subinterfaces Serial 13.2 and Serial 13.3 inherit class parameters from the main interface. The traffic shaping for these two VCs will be adaptive to the ForeSight notification.
For Serial 0, the output rate for DLCI 103 will not be affected by the router ForeSight function.
interface Serial0no ip addressencapsulation frame-relayframe-relay lmi-type ansiframe-relay traffic-shaping!interface Serial0.2 point-to-pointip address 10.128.30.17 255.255.255.248frame-relay interface-dlci 102class fast_vcs!interface Serial0.3 point-to-pointip address 10.128.30.5 255.255.255.248ip ospf cost 200frame-relay interface-dlci 103class slow_vcs!interface serial 3no ip addressencapsulation frame-relayframe-relay traffic-shapingframe-relay class fast_vcs!interface Serial3.2 multipointip address 100.120.20.13 255.255.255.248frame-relay map ip 100.120.20.6 16 ietf broadcast!interface Serial3.3 point-to-pointip address 100.120.10.13 255.255.255.248frame-relay interface-dlci 101!map-class frame-relay slow_vcsframe-relay adaptive-shaping becnframe-relay traffic-rate 4800 9600!map-class frame-relay fast_vcsframe-relay adaptive-shaping foresightframe-relay traffic-rate 16000 64000frame-relay cir 56000frame-relay bc 64000Enhanced Local Management Interface Example
Figure 18 illustrates a Cisco switch and a Cisco router, both configured with the Enhanced Local Management Interface feature enabled. The switch sends QoS information to the router, which uses it for traffic rate enforcement.
Figure 18 Enhanced Local Management Interface—Sent Between the Cisco Switch and the Cisco Router
The following configuration shows a Frame-Relay interface enabled with QoS autosense. The router receives messages from the Cisco switch, which is also configured with QoS autosense enabled. When Enhanced Local Management Interface is configured in conjunction with traffic shaping, the router will receive congestion information through BECN or router ForeSight congestion signaling and reduce its output rate to the value specified in the traffic shaping configuration.
interface serial0no ip addressencapsulation frame-relayframe-relay lmi-type ansiframe-relay traffic-shapingframe-relay QoS-autosense!interface serial0.1 point-to-pointno ip addressframe-relay interface-dlci 101Backward Compatibility Example
The following configuration provides backward compatibility and interoperability with versions not compliant with RFC 1490. The ietf keyword is used to generate RFC 1490 traffic. This configuration is possible because of the flexibility provided by separately defining each map entry.
encapsulation frame-relayframe-relay map ip 131.108.123.2 48 broadcast ietf! interoperability is provided by IETF encapsulationframe-relay map ip 131.108.123.3 49 broadcast ietfframe-relay map ip 131.108.123.7 58 broadcast! this line allows the router to connect with a ! device running an older version of softwareframe-relay map decnet 21.7 49 broadcastBooting from a Network Server over Frame Relay Example
When booting from a Trivial File Transfer Protocol (TFTP) server over Frame Relay, you cannot boot from a network server via a broadcast. You must boot from a specific TFTP host. Also, a frame-relay map command must exist for the host that you will boot from.
For example, if file gs3-bfx is to be booted from a host with IP address 131.108.126.2, the following commands would need to be in the configuration:
boot system gs3-bfx 131.108.126.2!interface Serial 0encapsulation frame-relayframe-relay map IP 131.108.126.2 100 broadcastThe frame-relay map command is used to map an IP address into a DLCI address. To boot over Frame Relay, you must explicitly give the address of the network server to boot from, and a frame-relay map entry must exist for that site. For example, if file gs3-bfx.83-2.0 is to be booted from a host with IP address 131.108.126.111, the following commands must be in the configuration:
boot system gs3-bfx.83-2.0 131.108.13.111!interface Serial 1ip address 131.108.126.200 255.255.255.0encapsulation frame-relayframe-relay map ip 131.108.126.111 100 broadcastIn this case, 100 is the DLCI that can get to host 131.108.126.111.
The remote router must have the following frame-relay map entry:
frame-relay map ip 131.108.126.200 101 broadcastThis entry allows the remote router to return a boot image (from the network server) to the router booting over Frame Relay. Here, 101 is a DLCI of the router being booted.
Frame Relay End-to-End Keepalive Examples
The following sections provide examples of Frame Relay End-to-End Keepalive in different modes and configurations:
•
•
•
End-to-End Keepalive Bidirectional Mode with Default Configuration Example
In the following example, the devices at each end of a VC are configured so that a DLCI is assigned to a Frame Relay serial interface, a map class is associated with the interface, and Frame Relay end-to-end keepalive is configured in bidirectional mode using default values:
! router1router1(config) interface serial 0/0.1 point-to-pointrouter1(config-if) ip address 10.1.1.1 255.255.255.0router1(config-if) frame-relay interface-dlci 16router1(config-if) frame-relay class vcgrp1router1(config-if) exit!router1(config)# map-class frame-relay vcgrp1router1(config-map-class)# frame-relay end-to-end keepalive mode bidirectional! router2router2(config) interface serial 1/1.1 point-to-pointrouter2(config-if) ip address 10.1.1.2 255.255.255.0router2(config-if) frame-relay interface-dlci 16router2(config-if) frame-relay class vceekrouter1(config-if) exit!router2(config)# map-class frame-relay vceekrouter2(config-map-class)# frame-relay end-to-end keepalive mode bidirectionalEnd-to-End Keepalive Request Mode with Default Configuration Example
In the following example, the devices at each end of a VC are configured so that a DLCI is assigned to a Frame Relay serial interface and a map class is associated with the interface. One device is configured in request mode while the other end of the VC is configured in reply mode.
! router1router1(config) interface serial 0/0.1 point-to-pointrouter1(config-if) ip address 10.1.1.1 255.255.255.0router1(config-if) frame-relay interface-dlci 16router1(config-if) frame-relay class eekrouter1(config-if) exit!router1(config)# map-class frame-relay eekrouter1(config-map-class)# frame-relay end-to-end keepalive mode request! router2router2(config) interface serial 1/1.1 point-to-pointrouter2(config-if) ip address 10.1.1.2 255.255.255.0router2(config-if) frame-relay interface-dlci 16router2(config-if) frame-relay class group_3router1(config-if) exit!router2(config)# map-class frame-relay group_3router2(config-map-class)# frame-relay end-to-end keepalive mode replyEnd-to-End Keepalive Request Mode with Modified Configuration Example
In the following example, the devices at each end of a VC are configured so that a DLCI is assigned to a Frame Relay serial interface and a map class is associated with the interface. One device is configured in request mode while the other end of the VC is configured in reply mode. The event window, error threshold, and success events values are changed so that the interface will change state less frequently:
! router1router1(config) interface serial 0/0.1 point-to-pointrouter1(config-if) ip address 10.1.1.1 255.255.255.0router1(config-if) frame-relay interface-dlci 16router1(config-if) frame-relay class eekrouter1(config-if) exit!router1(config)# map-class frame-relay eekrouter1(config-map-class)# frame-relay end-to-end keepalive mode requestrouter1(config-map-class)# frame-relay end-to-end keepalive event-window send 5router1(config-map-class)# frame-relay end-to-end keepalive error-threshold send 3router1(config-map-class)# frame-relay end-to-end keepalive success-events send 3! router2router2(config) interface serial 1/1.1 point-to-pointrouter2(config-if) ip address 10.1.1.2 255.255.255.0router2(config-if) frame-relay interface-dlci 16router2(config-if) frame-relay class group_3router1(config-if) exit!router2(config)# map-class frame-relay group_3router2(config-map-class)# frame-relay end-to-end keepalive mode replyPPP over Frame Relay Examples
The following sections provide examples of PPP over Frame Relay from the DTE and DCE end of the network:
•
•
PPP over Frame Relay DTE Example
The following example configures a router as a DTE device for PPP over Frame Relay. Subinterface 2.1 contains the necessary DLCI and virtual template information. Interface Virtual-Template 1 contains the PPP information that is applied to the PPP session associated with DLCI 32 on serial subinterface 2.1. Refer to the Cisco IOS Wide-Area Configuration Guide and Cisco IOS Wide-Area Networking Command Reference for information about Frame Relay configuration options.
interface serial 2no ip addressencapsulation frame-relayframe-relay lmi-type ansi!interface serial 2.1 point-to-pointframe-relay interface-dlci 32 ppp virtual-template1!interface Virtual-Template1ip unnumbered ethernet 0ppp authentication chap pap
Note
PPP over Frame Relay DCE Example
The following example configures a router to act as a DCE device. Typically, a router is configured for a DCE if it is connecting directly to another router or if connected to a 90i D4 channel unit, which is connected to a telco channel bank. The three commands required for this type of configuration are the frame-relay switching, frame-relay intf-type dce, and frame-relay route commands:
frame-relay switching!interface Serial2/0:0no ip addressencapsulation frame-relay IETFframe-relay lmi-type ansiframe-relay intf-type dceframe-relay route 31 interface Serial1/2 100frame-relay interface-dlci 32 ppp Virtual-Template1!interface Serial2/0:0.2 point-to-pointno ip addressframe-relay interface-dlci 40 ppp Virtual-Template2!interface Virtual-Template1ip unnumbered Ethernet0/0peer default ip address pool defaultppp authentication chap pap!interface Virtual-Template2ip address 100.1.1.2 255.255.255.0ppp authentication chap pap
Note
Frame Relay Switching Examples
The following sections provide examples of configuring one or more routers as Frame Relay switches:
•
•
•
PVC Switching Configuration Example
You can configure your router as a dedicated, DCE-only Frame Relay switch. Switching is based on DLCIs. The incoming DLCI is examined, and the outgoing interface and DLCI are determined. Switching takes place when the incoming DLCI in the packet is replaced by the outgoing DLCI, and the packet is sent out the outgoing interface.
In Figure 19, the router switches two PVCs between interface serial 1 and 2. Frames with DLCI 100 received on serial 1 will be transmitted with DLCI 200 on serial 2.
Figure 19 PVC Switching Configuration
The following example shows one router with two interfaces configured as DCEs. The router switches frames from the incoming interface to the outgoing interface on the basis of the DLCI alone.
Configuration for Router A
frame-relay switching!interface Ethernet0ip address 131.108.160.58 255.255.255.0!interface Serial1no ip addressencapsulation frame-relaykeepalive 15frame-relay lmi-type ansiframe-relay intf-type dceframe-relay route 100 interface Serial2 200frame-relay route 101 interface Serial2 201clockrate 2000000!interface Serial2encapsulation frame-relaykeepalive 15frame-relay intf-type dceframe-relay route 200 interface Serial1 100frame-relay route 201 interface Serial1 101clockrate 64000Pure Frame Relay DCE Example
Using the PVC switching feature, it is possible to build an entire Frame Relay network using routers. In Figure 20, Router A and Router C act as Frame Relay switches implementing a two-node network. The standard Network-to-Network Interface (NNI) signaling protocol is used between Router A and Router C.
The following example shows a Frame Relay network with two routers functioning as switches and standard NNI signaling used between them.
Figure 20 Frame Relay DCE Configuration
Configuration for Router A
frame-relay switching!interface ethernet 0no ip addressshutdown :Interfaces not in use may be shut down; shut down is not required.!interface ethernet 1no ip addressshutdown!interface ethernet 2no ip addressshutdown!interface ethernet 3no ip addressshutdown!interface serial 0ip address 131.108.178.48 255.255.255.0shutdown!interface serial 1no ip addressencapsulation frame-relayframe-relay intf-type dceframe-relay lmi-type ansiframe-relay route 100 interface serial 2 200!interface serial 2no ip addressencapsulation frame-relayframe-relay intf-type nniframe-relay lmi-type q933aframe-relay route 200 interface serial 1 100clockrate 2048000!interface serial 3no ip addressshutdownConfiguration for Router C
frame-relay switching!interface ethernet 0no ip addressshutdown :Interfaces not in use may be shut down; shut down is not required.!interface ethernet1no ip addressshutdown!interface ethernet 2no ip addressshutdown!interface ethernet 3no ip addressshutdown!interface serial 0ip address 131.108.187.84 255.255.255.0shutdown!interface serial 1no ip addressencapsulation frame-relayframe-relay intf-type dceframe-relay route 300 interface serial 2 200!interface serial 2no ip addressencapsulation frame-relayframe-relay intf-type nniframe-relay lmi-type q933aframe-relay route 200 interface serial 1 300!interface serial 3no ip addressshutdownHybrid DTE/DCE PVC Switching Example
Routers can also be configured as hybrid DTE/DCE Frame Relay switches, as shown in Figure 21.
Figure 21 Hybrid DTE/DCE PVC Switching
The following example shows one router configured with both DCE and DTE interfaces (Router B acts as a hybrid DTE/DCE Frame Relay switch). It can switch frames between two DCE ports and between a DCE port and a DTE port. Traffic from the Frame Relay network can also be terminated locally. In the example, three PVCs are defined as follows:
•
•
•
DLCI 400 is also defined for locally terminated traffic.
Configuration for Router B
frame-relay switching!interface ethernet 0ip address 131.108.123.231 255.255.255.0!interface ethernet 1ip address 131.108.5.231 255.255.255.0!interface serial 0no ip addressshutdown :Interfaces not in use may be shut down; shut down is not required.!interface serial 1no ip addressencapsulation frame-relayframe-relay intf-type dceframe-relay route 102 interface serial 2 201frame-relay route 103 interface serial 3 301!interface serial 2no ip addressencapsulation frame-relayframe-relay intf-type dceframe-relay route 201 interface serial 1 102frame-relay route 203 interface serial 3 302!interface serial 3ip address 131.108.111.231encapsulation frame-relayframe-relay lmi-type ansiframe-relay route 301 interface serial 1 103frame-relay route 302 interface serial 1 203frame-relay map ip 131.108.111.4 400 broadcastSwitching over an IP Tunnel Example
You can achieve switching over an IP tunnel by creating a point-to-point tunnel across the internetwork over which PVC switching can take place, as shown in Figure 22.
Note
Figure 22 Frame Relay Switch over IP Tunnel
The following example shows two routers configured to switch Frame Relay PVCs over a point-to-point IP tunnel, which is the IP network configuration depicted in Figure 22.
Configuration for Router A
frame-relay switching!interface ethernet0ip address 108.131.123.231 255.255.255.0!interface ethernet1ip address 131.108.5.231 255.255.255.0!interface serial0no ip addressshutdown : Interfaces not in use may be shut down; shutdown is not required.!interface serial1ip address 131.108.222.231 255.255.255.0encapsulation frame-relayframe-relay map ip 131.108.222.4 400 broadcastframe-relay route 100 interface Tunnel1 200!interface tunnel1tunnel source Ethernet0tunnel destination 150.150.150.123Configuration for Router D
frame-relay switching!interface ethernet0ip address 131.108.231.123 255.255.255.0!interface ethernet1ip address 131.108.6.123 255.255.255.0!interface serial0ip address 150.150.150.123 255.255.255.0encapsulation ppp!interface tunnel1tunnel source Serial0tunnel destination 108.131.123.231!interface serial1ip address 131.108.7.123 255.255.255.0encapsulation frame-relayframe-relay intf-type dceframe-relay route 300 interface Tunnel1 200FRF.9 Compression Configuration Examples
The following sections provide examples of various methods of configuring FRF.9 compression:
•
•
Note
FRF.9 Compression for Subinterfaces Using the frame-relay map Command Example
The following example shows a subinterface being configured for FRF.9 compression using the frame-relay map command.
interface serial2/0/1ip address 172.16.1.4 255.255.255.0no ip route-cacheencapsulation frame-relay IETFno keepaliveframe-relay map ip 172.16.1.1 105 IETF payload-compression FRF9 stacFRF.9 Compression for Subinterfaces Example
The following example shows a subinterface being configured for FRF.9 compression:
interface serial2/0/0no ip addressno ip route-cacheencapsulation frame-relayip route-cache distributedno keepalive!interface serial2/0/0.500 point-to-pointip address 172.16.1.4 255.255.255.0no cdp enableframe-relay interface-dlci 500 IETFframe-relay payload-compression FRF9 stacTCP/IP Header Compression Examples
The following sections provide examples of configuring various combinations of TCP/IP header compression, encapsulation characteristics on the interface, and the effect on the inheritance of those characteristics on a Frame Relay IP map:
•
•
Note
IP Map with Inherited TCP/IP Header Compression Example
The following example shows an interface configured for TCP/IP header compression and an IP map that inherits the compression characteristics. Note that the Frame Relay IP map is not explicitly configured for header compression.
interface serial 1encapsulation frame-relayip address 131.108.177.178 255.255.255.0frame-relay map ip 131.108.177.177 177 broadcastframe-relay ip tcp header-compression passiveUse of the show frame-relay map command will display the resulting compression and encapsulation characteristics; the IP map has inherited passive TCP/IP header compression:
Router> show frame-relay mapSerial 1 (administratively down): ip 131.108.177.177dlci 177 (0xB1,0x2C10), static,broadcast,CISCOTCP/IP Header Compression (inherited), passive (inherited)This example also applies to dynamic mappings achieved with the use of inverse-arp on point-to-point subinterfaces where no Frame Relay maps are configured.
Using an IP Map to Override TCP/IP Header Compression Example
The following example shows the use of a Frame Relay IP map to override the compression set on the interface:
interface serial 1encapsulation frame-relayip address 131.108.177.178 255.255.255.0frame-relay map ip 131.108.177.177 177 broadcast nocompressframe-relay ip tcp header-compression passiveUse of the show frame-relay map command will display the resulting compression and encapsulation characteristics; the IP map has not inherited TCP header compression:
Serial 1 (administratively down): ip 131.108.177.177dlci 177 (0xB1,0x2C10), static,broadcast,CISCO
Note
Disabling TCP/IP Header Compression Examples
The following sections provide examples of various methods for disabling TCP/IP header compression:
•
•
The following examples illustrate the use of different commands to disable TCP/IP header compression.
Note
Disabling Inherited TCP/IP Header Compression Example
In this example, the following is the initial configuration:
interface serial 1encapsulation frame-relayip address 131.108.177.179 255.255.255.0frame-relay ip tcp header-compression passiveframe-relay map ip 131.108.177.177 177 broadcastframe-relay map ip 131.108.177.178 178 broadcast tcp header-compressionEnter the following commands to enable inherited TCP/IP header compression:
serial interface 1no frame-relay ip tcp header-compressionUse of the show frame-relay map command will display the resulting compression and encapsulation characteristics:
Router> show frame-relay mapSerial 1 (administratively down): ip 131.108.177.177 177dlci 177(0xB1, 0x2C10), static,broadcastCISCOSerial 1 (administratively down): ip 131.108.177.178 178dlci 178(0xB2,0x2C20), staticbroadcastCISCOTCP/IP Header Compression (enabled)As a result, header compression is disabled for the first map (with DLCI 177), which inherited its header compression characteristics from the interface. However, header compression is not disabled for the second map (DLCI 178), which is explicitly configured for header compression.
Disabling Explicit TCP/IP Header Compression Example
In this example, the initial configuration is the same as the preceding example, but you must enter the following set of commands to enable explicit TCP/IP header compression:
serial interface 1no frame-relay ip tcp header-compressionframe-relay map ip 131.108.177.178 178 nocompressUse of the show frame-relay map command will display the resulting compression and encapsulation characteristics:
Router> show frame-relay mapSerial 1 (administratively down): ip 131.108.177.177 177dlci 177(0xB1,0x2C10), static,broadcastCISCOSerial 1 (administratively down): ip 131.108.177.178 178dlci 178(0xB2,0x2C20), staticbroadcastCISCOThe result of the commands is to disable header compression for the first map (with DLCI 177), which inherited its header compression characteristics from the interface, and also explicitly to disable header compression for the second map (with DLCI 178), which was explicitly configured for header compression.
