Frame Relay Guide

8/6/2019 Frame Relay Guide

1/73

Configuring and Troubleshooting Frame Relay

Document ID: 16563

Interactive:This document offers customized analysis of your Ciscodevice.

Introduction

Before You Begin

Conventions

Prerequisites

Components Used

Background Theory

Configuring Basic Frame Relay

Network Diagram

Configurations

debug and show Commands

Configuring Hub and Spoke Frame RelayNetwork Diagram

Configurations

show Commands

Connecting from Spoke to Spoke

Configurations

show Commands

Configuring Frame Relay Subinterfaces

PointtoPoint Subinterfaces

show Commands

Hub and Spoke Subinterfaces

show Commands

Configuring Dynamic and Static Mapping for Multipoint Subinterfaces

Network Diagram

Configurations


Configuring IP Unnumbered Frame Relay

Network Diagram

Configurations

show Commands

Configuring Frame Relay Backup

Frame Relay Backup over ISDN

Configuration Per DCLI Backup

Hub and Spoke with Dialer ProfilesConfiguring Frame Relay Switching

Network Diagram

Configurations

show Commands

Configuring Frame Relay DLCI Prioritization

Implementation Considerations

Network Diagram

Configurations


Frame Relay Broadcast Queue

Traffic Shaping


2/73

Traffic Shaping Parameters

Generic Traffic Shaping

Frame Relay Traffic Shaping

Commonly Used Frame Relay Commands

show framerelay pvc

show framerelay map

Frame Relay and Bridging

Frame Relay and Memory

Troubleshooting Frame Relay"Serial0 is down, line protocol is down"

"Serial0 is up, line protocol is down"

"Serial0 is up, line protocol is up"

Frame Relay Characteristics

IP Split Horizon Checking

Ping Your Own IP Address on a Multipoint Frame Relay

The Keyword broadcast

Reconfiguring a Subinterface

DLCI Limitations

IP/IPX/AT Address

RIP and IGRPKeepalive

Serial Interfaces

OSPF and Multipoint

Sources

Related Information

Introduction

Frame Relay is an industrystandard, switched data link layer protocol that handles multiple virtual circuits

using HighLevel Data Link Control (HDLC) encapsulation between connected devices. In many cases,

Frame Relay is more efficient than X.25, the protocol for which it is generally considered a replacement. Thefollowing figure illustrates a Frame Relay frame (ANSI T1.618).


3/73

Note in the above figure, Q.922 addresses, as presently defined, are two octets and contain a 10bit datalink

connection identifier (DLCI). In some networks Q.922 addresses may optionally be increased to three or four

octets.

The "flag" fields delimit the beginning and end of the frame. Following the leading "flag" field are two bytes

of address information. Ten bits of these two bytes make up the actual circuit ID (called the DLCI, for

datalink connection identifier).

The 10bit DLCI value is the heart of the Frame Relay header. It identifies the logical connection that ismultiplexed into the physical channel. In the basic (that is, not extended by the Local Management Interface

[LMI]) mode of addressing, DLCIs have local significance; that is, the end devices at two different ends of a

connection may use a different DLCI to refer to that same connection.

Before You Begin

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.


4/73

Prerequisites

For more information and definitions for the terms used in this document, please refer to the Frame Relay

Glossary.

Components Used

This document is not restricted to specific software and hardware versions.

The information presented in this document was created from devices in a specific lab environment. All of the

devices used in this document started with a cleared (default) configuration. If you are working in a live

network, ensure that you understand the potential impact of any command before using it.

Background Theory

Frame Relay was originally conceived as a protocol for use over ISDN interfaces. Initial proposals to this

effect were submitted to the International Telecommunication Union Telecommunication Standardization

Sector (ITUT) (formerly the Consultative Committee for International Telegraph and Telephone [CCITT])

in 1984. Work on Frame Relay was also undertaken in the ANSIaccredited T1S1 standards committee in theUnited States.

In 1990, Cisco Systems, StrataCom, Northern Telecom, and Digital Equipment Corporation formed a

consortium to focus Frame Relay technology development and accelerate the introduction of inter operable

Frame Relay products. They developed a specification conforming to the basic Frame Relay protocol being

discussed in T1S1 and ITUT, but extended it with features that provide additional capabilities for complex

internetworking environments. These Frame Relay extensions are referred to collectively as the LMI. This is

the "cisco" LMI in the router as opposed to the "ansi" or "q933a" LMI.

Frame Relay provides a packetswitching data communications capability that is used across the interface

between user devices (such as routers, bridges, host machines) and network equipment (such as switching

nodes). User devices are often referred to as data terminal equipment (DTE), while network equipment that

interfaces to DTE is often referred to as data circuitterminating equipment (DCE). The network providing

the Frame Relay interface can be either a carrierprovided public network or a network of privately owned

equipment serving a single enterprise.

Frame Relay differs significantly from X.25 in its functionality and format. In particular, Frame Relay is a

more streamlined protocol, facilitating higher performance and greater efficiency.

As an interface between user and network equipment, Frame Relay provides a means for statistically

multiplexing many logical data conversations (referred to as virtual circuits) over a single physical

transmission link. This contrasts with systems that use only timedivisionmultiplexing (TDM) techniques

for supporting multiple data streams. Frame Relay's statistical multiplexing provides more flexible andefficient use of available bandwidth. It can be used without TDM techniques or on top of channels provided

by TDM systems.

Another important characteristic of Frame Relay is that it exploits the recent advances in widearea network

(WAN) transmission technology. Earlier WAN protocols, such as X.25, were developed when analog

transmission systems and copper media were predominant. These links are much less reliable than the fiber

media/digital transmission links available today. Over links such as these, linklayer protocols can forego

timeconsuming error correction algorithms, leaving these to be performed at higher protocol layers. Greater

performance and efficiency is therefore possible without sacrificing data integrity. Frame Relay is designed

with this approach in mind. It includes a cyclic redundancy check (CRC) algorithm for detecting corrupted

bits (so the data can be discarded), but it does not include any protocol mechanisms for correcting bad data


5/73

(for example, by retransmitting it at this level of protocol).

Another difference between Frame Relay and X.25 is the absence of explicit, pervirtualcircuit flow control

in Frame Relay. Now that many upperlayer protocols are effectively executing their own flow control

algorithms, the need for this functionality at the link layer has diminished. Frame Relay, therefore, does not

include explicit flow control procedures that duplicate those in higher layers. Instead, very simple congestion

notification mechanisms are provided to allow a network to inform a user device that the network resources

are close to a congested state. This notification can alert higherlayer protocols that flow control may be

needed.

Configuring Basic Frame Relay

Once you have reliable connections to the local Frame Relay switch at both ends of the permanent virtual

circuit (PVC), then it is time to start planning the Frame Relay configuration. In this first example, the Local

Management Interface (LMI)type defaults to "cisco" LMI on Spicey. An interface is by default a

"multipoint" interface so, framerelay inversearp is on (for pointtopoint, there is no Inverse ARP). IP

split horizon checking is disabled by default for Frame Relay encapsulation, so routing updates come in and

out the same interface. The routers learn the datalink connection identifiers (DLCIs) they need to use from

the Frame Relay switch via LMI updates. The routers then Inverse ARP for the remote IP address and create a

mapping of local DLCIs and their associated remote IP addresses.

Network Diagram

Configurations

Spicey

Prasit

Spicey

Spicey#show runningconfig

Building configuration...

Current configuration : 1705 bytes

!

version 12.1service timestamps debug datetime msec

service timestamps log datetime msec

no service passwordencryption

!

hostname Spicey

!

!

!

interface Ethernet0

ip address 124.124.124.1 255.255.255.0

!

interface Serial0

ip address 3.1.3.1 255.255.255.0

encapsulation framerelay


6/73

framerelay interfacedlci 140

!

!

router rip

network 3.0.0.0

network 124.0.0.0

!

line con 0

exectimeout 0 0

transport input none

line aux 0

line vty 0 4

login

!

end

Prasit

Prasit#show runningconfig



!

version 12.1

service timestamps debug datetime msec



!

hostname Prasit

!

!

!

interface Ethernet0

ip address 123.123.123.1 255.255.255.0

!

!

interface Serial1

ip address 3.1.3.2 255.255.255.0



!

!

router rip

network 3.0.0.0

network 123.0.0.0

!

!

!

line con 0

exectimeout 0 0


line aux 0line vty 0 4

login

!

end


Before issuing debug commands, please see Important Information on Debug Commands.

show framerelay map

show framerelay pvc

show framerelay lmi


7/73

ping

show ip route

Spicey

Spicey#show framerelay map

Serial0 (up): ip 3.1.3.2 dlci 140(0x8C,0x20C0), dynamic,

broadcast,, status defined, active

Spicey#show framerelay pvc

PVC Statistics for interface Serial0 (Frame Relay DTE)

Active Inactive Deleted Static

Local 1 0 0 0

Switched 0 0 0 0

Unused 0 0 0 0

DLCI = 140, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0

input pkts 83 output pkts 87 in bytes 8144

out bytes 8408 dropped pkts 0 in FECN pkts0

in BECN pkts 0 out FECN pkts 0 out BECN pkts0

in DE pkts 0 out DE pkts 0

out bcast pkts 41 out bcast bytes 3652

pvc create time 01:31:50, last time pvc status changed 01:28:28

Spicey#show framerelay lmi

LMI Statistics for interface Serial0 (Frame Relay DTE) LMI TYPE = CISCO

Invalid Unnumbered info 0 Invalid Prot Disc 0

Invalid dummy Call Ref 0 Invalid Msg Type 0

Invalid Status Message 0 Invalid Lock Shift 0

Invalid Information ID 0 Invalid Report IE Len 0

Invalid Report Request 0 Invalid Keep IE Len 0

Num Status Enq. Sent 550 Num Status msgs Rcvd 552

Num Update Status Rcvd 0 Num Status Timeouts 0

Spicey#ping 123.123.123.1

Type escape sequence to abort.

Sending 5, 100byte ICMP Echos to 123.123.123.1, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), roundtrip min/avg/max = 36/36/40 msSpicey#show ip route

Codes: C connected, S static, I IGRP, R RIP, M mobile, B BGP

D EIGRP, EX EIGRP external, O OSPF, IA OSPF inter area

N1 OSPF NSSA external type 1, N2 OSPF NSSA external type 2

E1 OSPF external type 1, E2 OSPF external type 2, E EGP

i ISIS, L1 ISIS level1, L2 ISIS level2, ia ISIS

inter area

* candidate default, U peruser static route, o ODR

P periodic downloaded static route

Gateway of last resort is not set

3.0.0.0/24 is subnetted, 1 subnets

C 3.1.3.0 is directly connected, Serial0

124.0.0.0/24 is subnetted, 1 subnetsC 124.124.124.0 is directly connected, Ethernet0

R 123.0.0.0/8 [120/1] via 3.1.3.2, 00:00:08, Serial0

Prasit

Prasit#show framerelay map

Serial1 (up): ip 3.1.3.1 dlci 150(0x96,0x2460), dynamic,


Prasit#show framerelay pvc



Local 1 0 0 0Switched 0 0 0 0


8/73

Unused 0 0 0 0



out bytes 8144 dropped pkts 0 in FECN pkts 0

in BECN pkts 0 out FECN pkts 0 out BECN pkts 0




Prasit#show framerelay lmi

LMI Statistics for interface Serial1 (Frame Relay DTE) LMI TYPE = CISCOInvalid Unnumbered info 0 Invalid Prot Disc 0

Invalid dummy Call Ref 0 Invalid Msg Type 0

Invalid Status Message 0 Invalid Lock Shift 0

Invalid Information ID 0 Invalid Report IE Len 0

Invalid Report Request 0 Invalid Keep IE Len 0

Num Status Enq. Sent 569 Num Status msgs Rcvd 570

Num Update Status Rcvd 0 Num Status Timeouts 0

Prasit#ping 124.124.124.1



!!!!!

Success rate is 100 percent (5/5), roundtrip min/avg/max = 36/36/36 ms

Prasit#show ip route






inter area





C 3.1.3.0 is directly connected, Serial1

R 124.0.0.0/8 [120/1] via 3.1.3.1, 00:00:19, Serial1


Configuring Hub and Spoke Frame Relay

In this example, the router learns which datalink connection identifiers (DLCIs) it uses from the Frame

Relay switch and assigns them to the main interface. Then the router will Inverse ARP for the remote IP

address.

Note: You will not be able to ping Prasit's serial IP address from Aton unless you explicitly add in Frame

Relay maps on each end. If routing is configured correctly, traffic originating on the LANs should not have a

problem. You will be able to ping if you use the Ethernet IP address as the source address in an extended ping.

When framerelay inversearp is enabled, broadcast IP traffic will go out over the connection by default.

Network Diagram


9/73

Configurations

Spicey

Prasit

Aton

Spicey

spicey#show runningconfig


!

version 12.1




!

hostname spicey

!

!

!

!

interface Ethernet0ip address 124.124.124.1 255.255.255.0

!

interface Serial0

ip address 3.1.3.1 255.255.255.0




!

!

router rip

network 3.0.0.0

network 124.0.0.0

!

line con 0exectimeout 0 0


line aux 0

line vty 0 4

login

!

end

Prasit

prasit#show runningconfig




10/73

!

version 12.1




!

hostname prasit

!

!

!

interface Ethernet0

ip address 123.123.123.1 255.255.255.0

!

interface Serial1

ip address 3.1.3.2 255.255.255.0



!

!

router rip

network 3.0.0.0

network 123.0.0.0

!

!line con 0

exectimeout 0 0


line aux 0

line vty 0 4

login

!

end

Aton

aton#show runningconfig


Current configuration:

!

version 12.0

service timestamps debug uptime

service timestamps log uptime


!

hostname aton

!

!

interface Ethernet0

ip address 122.122.122.1 255.255.255.0

!

interface Serial1ip address 3.1.3.3 255.255.255.0



!

router rip

network 3.0.0.0

network 122.0.0.0

!

!

line con 0

exectimeout 0 0


line aux 0

line vty 0 4


11/73

login

!

end

show Commands

show framerelay map

show framerelay pvc

ping

Spicey

spicey#show framerelay map

Serial0 (up): ip 3.1.3.2 dlci 140(0x8C,0x20C0), dynamic,




spicey#show framerelay pvc



Local 2 0 0 0

Switched 0 0 0 0

Unused 0 0 0 0















spicey#

spicey#ping 3.1.3.2



!!!!!


spicey#ping 3.1.3.3

Type escape sequence to abort.Sending 5, 100byte ICMP Echos to 3.1.3.3, timeout is 2 seconds:

!!!!!


Prasit

prasit#show framerelay map



prasit#show framerelay pvc

PVC Statistics for interface Serial1 (Frame Relay DTE)Active Inactive Deleted Static


12/73


13/73

Connecting from Spoke to Spoke

You cannot ping from one spoke to another spoke in a hub and spoke configuration using multipoint

interfaces because there is no mapping for the other spokes' IP addresses. Only the hub's address is learned via

the Inverse Address Resolution Protocol (IARP). If you configure a static map using the framerelay map

command for the IP address of a remote spoke to use the local data link connection identifier (DLCI), you can

ping the addresses of other spokes.

Configurations

Prasit

prasit#show runningconfig

interface Ethernet0

ip address 123.123.123.1 255.255.255.0

!

interface Serial

ip address 3.1.3.2 255.255.255.0


framerelay map ip 3.1.3.3 150


show Commands

show framerelay map

ping

show runningconfig

Prasit

prasit#show framerelay map

Serial1 (up): ip 3.1.3.1 dlci 150(0x96,0x2460), dynamic,broadcast,, status defined, active

Serial1 (up): ip 3.1.3.3 dlci 150(0x96,0x2460), static,

CISCO, status defined, active

prasit#ping 3.1.3.3



!!!!!


prasit#ping 122.122.122.1



!!!!!Success rate is 100 percent (5/5), roundtrip min/avg/max = 64/67/76 ms


14/73

Aton

aton#show runningconfig

interface Ethernet0

ip address 122.122.122.1 255.255.255.0

!

interface Serial1

ip address 3.1.3.3 255.255.255.0

no ip directedbroadcast

encapsulation framerelayframerelay map ip 3.1.3.2 160


aton#show framerelay map

Serial1 (up): ip 3.1.3.1 dlci 160(0xA0,0x2800), dynamic,


Serial1 (up): ip 3.1.3.2 dlci 160(0xA0,0x2800), static,


aton#ping 3.1.3.2

Type escape sequence to abort


!!!!!


aton#ping 123.123.123.1



!!!!!


Configuring 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, butnot 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

transmitted out the same interface even if the packet is received and transmitted on different virtual circuits.

Configuring Frame Relay subinterfaces ensures that a single physical interface is treated as multiple virtual

interfaces. This capability allows us to overcome split horizon rules. Packets received on one virtual interface

can now be forwarded out 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 partiallymeshed Frame Relay network into a number of smaller, fully meshed (or pointtopoint) 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 pointtopoint subinterfaces can be unnumbered for use with IP, reducing the

addressing burden that might otherwise result).

PointtoPoint Subinterfaces

Network Diagram


15/73

Configurations

Spicey

Prasit

Spicey




!

version 12.1


service timestamps log datetime msecno service passwordencryption

!

hostname Spicey

!

enable password ww

!

!

!

!

interface Ethernet0

ip address 124.124.124.1 255.255.255.0

!

interface Serial0

no ip address


!

interface Serial0.1 pointtopoint

ip address 3.1.3.1 255.255.255.0


!

!

router igrp 2

network 3.0.0.0

network 124.0.0.0

!

!



line aux 0

line vty 0 4

login

!

end

Prasit





16/73

!

version 12.1




!

hostname Prasit

!

!

!

interface Ethernet0

ip address 123.123.123.1 255.255.255.0

!

interface Serial1

no ip address


!


ip address 3.1.3.2 255.255.255.0


!

router igrp 2

network 3.0.0.0

network 123.0.0.0!

line con 0

exectimeout 0 0


line aux 0

line vty 0 4

login

!

end

show Commands

show framerelay map

show framerelay pvc

Spicey


Serial0.1 (up): pointtopoint dlci, dlci 140(0x8C,0x20C0), broadcast

status defined, active




Local 1 0 0 0

Switched 0 0 0 0

Unused 0 0 0 0

DLCI = 140, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0.1







Spicey#ping 123.123.123.1Type escape sequence to abort.


17/73


!!!!!


Prasit


Serial1.1 (up): pointtopoint dlci, dlci 150(0x96,0x2460), broadcast





Local 1 0 0 0

Switched 0 0 0 0

Unused 0 0 0 0

DLCI = 150, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE =

Serial1.1



in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0






!!!!!


Hub and Spoke Subinterfaces

The following hub and spoke sample configuration shows two pointtopoint subinterfaces and uses dynamic

address resolution on one remote site. Each subinterface is provided with an individual protocol address and

subnetmask, and the interfacedlci command associates the subinterface with a specified datalink

connection identifier (DLCI). Addresses of remote destinations for each pointtopoint subinterface are not

resolved since they are pointtopoint and traffic must be sent to the peer at the other end. The remote end

(Aton) uses Inverse ARP for its mapping and the main hub responds accordingly with the IP address of the

subinterface. This occurs because Frame Relay Inverse ARP is on by default for multipoint interfaces.

Network Diagram


18/73

Configurations

Spicey

Prasit

Aton

Spicey



!

version 12.1




!

hostname Spicey

!

!

!

!

interface Ethernet0

ip address 124.124.124.1 255.255.255.0!

interface Serial0

no ip address


!


ip address 4.0.1.1 255.255.255.0


!


ip address 3.1.3.1 255.255.255.0


!

router igrp 2network 3.0.0.0

network 4.0.0.0

network 124.0.0.0

!

line con 0

exectimeout 0 0


line aux 0

line vty 0 4

login

!

end

Prasit



version 12.1




!

hostname Prasit

!

interface Ethernet0

ip address 123.123.123.1 255.255.255.0


19/73

!

interface Serial1

no ip address


!


ip address 4.0.1.2 255.255.255.0


!

router igrp 2

network 4.0.0.0

network 123.0.0.0

!

!

line con 0

exectimeout 0 0


line aux 0

line vty 0 4

login

!

end

Aton

Aton#show runningconfig



!

version 12.0



!

hostname Aton

!

!

!

interface Ethernet0

ip address 122.122.122.1 255.255.255.0

!

interface Serial1

ip address 3.1.3.3 255.255.255.0



!

router igrp 2

network 3.0.0.0

network 122.0.0.0

!



line aux 0

line vty 0 4

login

!

end

show Commands

show framerelay map

show framerelay pvc


20/73

Spicey









Local 2 0 0 0

Switched 0 0 0 0

Unused 0 0 0 0






















!!!!!


Prasit







Local 1 0 0 0

Switched 0 0 0 0

Unused 0 0 0 0


Serial1.1




21/73








!!!!!


Aton

Aton#show framerelay map

Serial1 (up): ip 3.1.3.1 dlci 160(0xA0,0x2800), dynamic,


Aton#show framerelay pvc



Local 1 0 0 0

Switched 0 0 0 0

Unused 0 0 0 0








Aton#ping 124.124.124.1



!!!!!


Configuring Dynamic and Static Mapping for MultipointSubinterfaces

Dynamic address mapping uses Frame Relay Inverse ARP to request the next hop protocol address for a

specific connection, given a datalink connection identifier (DLCI). Responses to Inverse ARP requests are

entered in an addresstoDLCI 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 thatdistinguishes a subinterface from the physical interface and associates a specific subinterface with a specific

DLCI.

Inverse ARP is enabled by default for all protocols it supports, but can be disabled for specific protocolDLCI

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 protocolDLCI pair if you know the protocol is

not supported on the other end of the connection. 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.

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


22/73

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.

Network Diagram

We've already seen how to configure a Cisco router to do Inverse ARP. The following example shows how to

configure static maps in case you need them for multipoint interfaces or subinterfaces:

Configurations

Aton

Spicey

Prasit

Aton


Building configuration...Current configuration:

!

version 12.0




!

hostname Aton

!

!

interface Ethernet0

ip address 122.122.122.1 255.255.255.0

!

interface Serial1

no ip address


!

interface Serial1.1 multipoint

ip address 4.0.1.3 255.255.255.0

framerelay map ip 4.0.1.1 160 broadcast

!

router igrp 2

network 4.0.0.0

network 122.0.0.0

!

line con 0

exectimeout 0 0transport input none


23/73

line aux 0

line vty 0 4

login

!

end

Spicey


Building configuration...Current configuration : 1652 bytes!version 12.1




!

hostname Spicey

!

!

interface Ethernet0

ip address 124.124.124.1 255.255.255.0

!

interface Serial0

ip address 4.0.1.1 255.255.255.0




!

router igrp 2

network 4.0.0.0

network 124.0.0.0

!

!

line con 0

exectimeout 0 0


line aux 0

line vty 0 4

login

!

end

Prasit




!

version 12.1




!

hostname Prasit

!

!

!

interface Ethernet0

ip address 123.123.123.1 255.255.255.0

!

interface Serial1

no ip address


!

interface Serial1.1 multipoint

ip address 4.0.1.2 255.255.255.0


24/73


!

router igrp 2

network 4.0.0.0

network 123.0.0.0

!

line con 0

exectimeout 0 0


line aux 0

line vty 0 4

login

!

end


show framerelay map

show framerelay pvc

Aton


Serial1.1 (up): ip 4.0.1.1 dlci 160(0xA0,0x2800), static, broadcast,





Local 1 0 0 0

Switched 0 0 0 0

Unused 0 0 0 0


Serial1.1







Aton#ping 124.124.124.1



!!!!!


Spicey


Serial0 (up): ip 4.0.1.2 dlci 140(0x8C,0x20C0), static, broadcast,


Serial0 (up): ip 4.0.1.3 dlci 130(0x82,0x2020), static, broadcast,





Local 2 0 0 0

Switched 0 0 0 0


25/73


26/73

Configuring IP Unnumbered Frame Relay

If you do not have the IP address space to use many subinterfaces, you can use IP unnumbered on each

subinterface. If this is the case, you need to use static routes or dynamic routing so that your traffic is routed

as usual, and you must use pointtopoint subinterfaces.

Network Diagram

The example below illustrates this:

Configurations

Spicey

Prasit

Spicey




!

version 12.1



no service passwordencryption!

hostname Spicey

!

!

!

interface Ethernet0

ip address 124.124.124.1 255.255.255.0

!

interface Serial0

no ip address


!


ip unnumbered Ethernet0


!

router igrp 2

network 124.0.0.0

!

line con 0

exectimeout 0 0


line aux 0

line vty 0 4

login

!

end


27/73

Prasit




!

version 12.1




!

hostname Prasit

!

!

interface Ethernet0

ip address 123.123.123.1 255.255.255.0

!

interface Serial1

no ip address


!


ip unnumbered Ethernet0


!

router igrp 2

network 123.0.0.0

!

line con 0

exectimeout 0 0


line aux 0

line vty 0 4

login

!

end

show Commands

show framerelay map

show framerelay pvc

Spicey







Local 1 0 0 0

Switched 0 0 0 0

Unused 0 0 0 0


Serial0.1


out bytes 4952 dropped pkts 0 in FECN pkts 0in BECN pkts 0 out FECN pkts 0 out BECN pkts 0


28/73




Spicey#show ip route






inter area* candidate default, U peruser static route, o ODR




C 124.124.124.0 is directly connected, Ethernet0

123.0.0.0/8 is variably subnetted, 2 subnets, 2 masks

I 123.0.0.0/8 [100/8576] via 123.123.123.1, 00:01:11, Serial0.1

I 123.123.123.0/32 [100/8576] via 123.123.123.1, 00:01:11,

Serial0.1




!!!!!


Prasit







Local 1 0 0 0

Switched 0 0 0 0

Unused 0 0 0 0


Serial1.1













inter area





I 124.0.0.0/8 [100/8576] via 124.124.124.1, 00:00:18, Serial1.1I 124.124.124.0/32 [100/8576] via 124.124.124.1, 00:00:18,


29/73

Serial1.1






!!!!!


Configuring Frame Relay Backup

Frame Relay Backup over ISDN

You may want to back up Frame Relay circuits using ISDN. There are several ways to do this. The first, and

probably the best, is to use floating static routes that route traffic to a Basic Rate Interface (BRI) IP address

and use an appropriate routing metric. You can also use a backup interface on the main interface or on a

perdatalink connection identifier (DLCI) basis. It may not help much to back up the main interface because

you could lose permanent virtual circuits (PVCs) without the main interface going down. Remember, the

protocol is being exchanged with the local Frame Relay switch, not the remote router.

Configurations

Router 1

Router 2

Router 1

ROUTER1#

!

hostname ROUTER1

!

username ROUTER2 password same

isdn switchtype basicdms100

!

interface Ethernet 0

ip address 172.16.15.1 255.255.255.248

!

interface serial 0

ip address 172.16.24.129 255.255.255.128

encapsulation FRAMERELAY

!

interface BRI0

description Backup ISDN for framerelay

ip address 172.16.12.1 255.255.255.128

encapsulation PPP

dialer idletimeout 240

dialer waitforcarriertime 60

dialer map IP 172.16.12.2 name ROUTER2 broadcast 7086639706

ppp authentication chap

dialergroup 1


30/73


31/73

debug ppp neg

debug ppp auth

Try to make an ISDN call from the calling side to the central side without the backup commands. If this is

successful, add the backup commands to the calling side.

Note: To test the backup, do not use the shutdown command on the serial interface but emulate a real serial

line problem by pulling out the cable from the serial line.

Configuration Per DCLI Backup

Now let's assume that Spicey is the central side and that Prasit is the side making connections to the central

side (Spicey). Take care that you only add the backup commands to the side that is calling the central side.

Note: Backup load is not supported on subinterfaces. As we do not track traffic levels on subinterfaces, no

load is calculated.

Network Diagram

Configurations

Spicey

Prasit

Spicey




!

version 12.1


service timestamps log datetime msecno service passwordencryption

!

hostname Spicey

!

!

username Prasit password 0 cisco

!

!

isdn switchtype basicnet3

!

!

!

interface Ethernet0

ip address 124.124.124.1 255.255.255.0


32/73

!

interface Serial0

no ip address


!


ip address 4.0.1.1 255.255.255.0


!

interface BRI0

ip address 3.1.6.1 255.255.255.0

encapsulation ppp

dialer map ip 3.1.6.2 name Prasit broadcast

dialergroup 1


no peer default ip address

no cdp enable


!

router igrp 2

network 3.0.0.0

network 4.0.0.0

network 124.0.0.0

!ip classless

ip route 123.123.123.0 255.255.255.0 3.1.6.2 250

!

accesslist 101 deny igrp any any

accesslist 101 permit ip any any

dialerlist 1 protocol ip list 101

!

line con 0

exectimeout 0 0


line aux 0

line vty 0 4

login

!end

Prasit




!

version 12.1



no service passwordencryption!

hostname Prasit

!

username Spicey password 0 cisco

!

!


!

!

!

interface Ethernet0

ip address 123.123.123.1 255.255.255.0

!

interface Serial1


33/73

no ip address


!


backup delay 5 10

backup interface BRI0

ip address 4.0.1.2 255.255.255.0


!

interface BRI0

ip address 3.1.6.2 255.255.255.0

encapsulation ppp

dialer map ip 3.1.6.1 name Spicey broadcast 6106

dialergroup 1



!

router igrp 2

network 3.0.0.0

network 4.0.0.0

network 123.0.0.0

!

ip route 124.124.124.0 255.255.255.0 3.1.6.1 250

!accesslist 101 deny igrp any any



!

line con 0

exectimeout 0 0


line aux 0

line vty 0 4

login

!

end

show Commands

show framerelay map

show ip route

show isdn history

show isdn status

show interface bri 0

show isdn active

Spicey

Spicey#show framerelay mapSerial0.2 (up): pointtopoint dlci, dlci 130(0x82,0x2020), broadcast










inter area




34/73


3.0.0.0/24 is subnetted, 2 subnets C

3.1.3.0 is directly connected, Serial0.2 C

3.1.6.0 is directly connected, BRI0


4.0.1.0 is directly connected, Serial0.1


124.124.124.0 is directly connected, Ethernet0

123.0.0.0/8 is variably subnetted, 2 subnets, 2 masks I123.0.0.0/8 [100/8576] via 4.0.1.2, 00:00:00, Serial0.1 S

123.123.123.0/24 [250/0] via 3.1.6.2 I

122.0.0.0/8 [100/8576] via 3.1.3.3, 00:00:37, Serial0.2

Spicey#

*Mar 1 00:59:12.527: %LINK3UPDOWN: Interface BRI0:1, changed state to up

*Mar 1 00:59:13.983: %LINEPROTO5UPDOWN: Line protocol on Interface

BRI0:1, changed state to up

*Mar 1 00:59:18.547: %ISDN6CONNECT: Interface BRI0:1 is now connected to 6105 Pra

Spicey#show isdn history

ISDN CALL HISTORY

Call History contains all active calls, and a maximum of 100 inactive calls.

Inactive call data will be retained for a maximum of 15 minutes.

Call Calling Called Remote Seconds Seconds Seconds

Charges

Type Number Number Name Used Left Idle Units/Currency

In 6105 6106 Prasit 31 90 29

Spicey#

*Mar 1 01:01:14.547: %ISDN6DISCONNECT: Interface BRI0:1 disconnected

from 6105 Prasit, call lasted 122 seconds*Mar 1 01:01:14.663: %LINK3UPDOWN: Interface BRI0:1, changed state to down


BRI0:1, changed state to down

Prasit







!!!!!








inter area





35/73

I 3.0.0.0/8 [100/10476] via 4.0.1.1, 00:00:55, Serial1.1


C 4.0.1.0 is directly connected, Serial1.1


S 124.124.124.0/24 [250/0] via 3.1.6.1

I 124.0.0.0/8 [100/8576] via 4.0.1.1, 00:00:55, Serial1.1



I 122.0.0.0/8 [100/10576] via 4.0.1.1, 00:00:55, Serial1.1

The serial line goes down.

Prasit#

*Mar 1 01:23:50.531: %LINK3UPDOWN: Interface Serial1, changed state to down


Serial1, changed state to down

*Mar 1 01:23:53.775: %LINK3UPDOWN: Interface BRI0:1, changed state to down


*Mar 1 01:23:53.827: %LINK3UPDOWN: Interface BRI0, changed state to up

*Mar 1 01:23:57.931: %ISDN6LAYER2UP: Layer 2 for Interface BR0, TEI 64 changed t


Codes: C connected, S static, I IGRP, R RIP, M mobile, B BGPD EIGRP, EX EIGRP external, O OSPF,IA OSPF inter area




inter area





C 3.1.6.0 is directly connected, BRI0


S 124.124.124.0 [250/0] via 3.1.6.1



Prasit#show isdn status

Global ISDN Switchtype = basicnet3

ISDN BRI0 interface

dsl 0, interface ISDN Switchtype = basicnet3

Layer 1 Status:

ACTIVE

Layer 2 Status:

TEI = 64, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED

Layer 3 Status:

0 Active Layer 3 Call(s)

Active dsl 0 CCBs = 0

The Free Channel Mask: 0x80000003

Total Allocated ISDN CCBs = 0




!

*Mar 1 01:25:47.383: %LINK3UPDOWN: Interface BRI0:1, changed state to up!!!


Prasit#




36/73

Prasit#

*Mar 1 01:25:53.407: %ISDN6CONNECT: Interface BRI0:1 is now connected

to 6106 Spicey



ISDN BRI0 interface


Layer 1 Status:

ACTIVE

Layer 2 Status:TEI = 64, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED

Layer 3 Status:


CCB:callid=8003, sapi=0, ces=1, Bchan=1, calltype=DATA




Prasit#show isdn active

ISDN ACTIVE CALLS

Call Calling Called Remote Seconds Seconds Seconds Charges

Type Number Number Name Used Left Idle Units/Currency

Out 6106 Spicey 21 100 19 0

Prasit#


from 6106 Spicey, call lasted 121 seconds




*Mar 1 01:28:09.215: %LINK3UPDOWN: Interface Serial1, changed state to up


Serial1, changed state to up*Mar 1 01:28:30.043: %ISDN6LAYER2DOWN: Layer 2 for Interface BRI0,

TEI 64 changed to down

*Mar 1 01:28:30.047: %ISDN6LAYER2DOWN: Layer 2 for Interface BR0, TEI

64 changed to down

*Mar 1 01:28:30.371: %LINK5CHANGED: Interface BRI0, changed state to standby mod



Prasit#

The serial connection is back again..



ISDN BRI0 interface


Layer 1 Status:

DEACTIVATED

Layer 2 Status:

Layer 2 NOT Activated

Layer 3 Status:





Prasit#show interface bri 0

BRI0 is standby mode, line protocol is downHardware is BRI


37/73


38/73

Aton




!

version 12.0




!

hostname Aton

!

!

username Spicey password 0 cisco

!


!

!

!

interface Ethernet0

ip address 122.122.122.1 255.255.255.0

!

!

interface Serial1

no ip address


!


ip address 3.1.3.3 255.255.255.0

backup delay 5 10

backup interface BRI0


!

interface BRI0

ip address 155.155.155.3 255.255.255.0

encapsulation pppno ip routecache

no ip mroutecache

dialer map ip 155.155.155.2 name Spicey broadcast 6106

dialergroup 1



!

router igrp 2

network 3.0.0.0

network 122.0.0.0

network 155.155.0.0

!

ip route 124.124.124.0 255.255.255.0 155.155.155.2 250

!accesslist 101 deny igrp any any



!

line con 0

exectimeout 0 0


line aux 0

line vty 0 4

login

!

end


39/73

Spicey




!

version 12.1




!

hostname Spicey

!

username Prasit password 0 cisco

username Aton password 0 cisco

!


!

!

!

interface Ethernet0

ip address 124.124.124.1 255.255.255.0

!

interface Serial0

no ip address


!


ip address 4.0.1.1 255.255.255.0


!


ip address 3.1.3.1 255.255.255.0


!

interface BRI0

no ip address

encapsulation pppno ip routecache

no ip mroutecache

dialer poolmember 2 maxlink 1

dialer poolmember 1 maxlink 1


no peer default ip address

no cdp enable


!

interface Dialer1

ip address 160.160.160.1 255.255.255.0

encapsulation ppp

no ip routecache

no ip mroutecachedialer pool 1

dialer remotename Prasit

dialergroup 1


!

interface Dialer2

ip address 155.155.155.2 255.255.255.0

encapsulation ppp

no ip routecache

no ip mroutecache

dialer pool 2

dialer remotename Aton

dialergroup 1



40/73


41/73

network 160.160.0.0

!

ip route 124.124.124.0 255.255.255.0 160.160.160.1 250

!

accesslist 101 deny igrp any any



!

line con 0

exectimeout 0 0


line aux 0

line vty 0 4

login

!

end

show Commands

show framerelay map

show ip route

show frame map

show framerelay pvc

Aton


Serial1.1 (up): pointtopoint dlci, dlci 160(0xA0,0x2800), broadcast


Aton#ping 124.124.124.1



!!!!!


Aton#show ip route





i ISIS, L1 ISIS level1, L2 ISIS level2, * candidate default

U peruser static route, o ODR, P periodic downloaded static route

T traffic engineered route


I 155.155.0.0/16 [100/182571] via 3.1.3.1, Serial1.1

3.0.0.0/24 is subnetted, 1 subnetsC 3.1.3.0 is directly connected, Serial1.1

I 4.0.0.0/8 [100/10476] via 3.1.3.1, Serial1.1

I 160.160.0.0/16 [100/182571] via 3.1.3.1, Serial1.1


S 124.124.124.0/24 [250/0] via 155.155.155.2

I 124.0.0.0/8 [100/8576] via 3.1.3.1, Serial1.1

I 123.0.0.0/8 [100/10576] via 3.1.3.1, Serial1.1



Aton#

Serial 1 is going down.

Aton#


42/73

01:16:33: %LINK3UPDOWN: Interface Serial1, changed state to down

01:16:34: %LINEPROTO5UPDOWN: Line protocol on Interface Serial1,

changed state to down

01:16:37: %LINK3UPDOWN: Interface BRI0:1, changed state to down


01:16:37: %LINK3UPDOWN: Interface BRI0, changed state to up

01:16:41: %ISDN6LAYER2UP: Layer 2 for Interface BR0, TEI 64 changed to up

Aton#show ip route


D EIGRP, EX EIGRP external, O OSPF, IA OSPF inter areaN1 OSPF NSSA external type 1, N2 OSPF NSSA external type 2


i ISIS, L1 ISIS level1, L2 ISIS level2, * candidate default

U peruser static route, o ODR, P periodic downloaded static route

T traffic engineered route





S 124.124.124.0 [250/0] via 155.155.155.2



Aton#ping 124.124.124.1



01:21:33: %LINK3UPDOWN: Interface BRI0:1, changed state to up.!!!!


Aton#

01:21:34: %LINEPROTO5UPDOWN: Line protocol on Interface BRI0:1,

changed state to up

01:21:39: %ISDN6CONNECT: Interface BRI0:1 is now connected to 6106

Spicey

Aton#ping 124.124.124.1



!!!!!


Aton#

Serial 1 becomes active again

Aton#

01:24:02: %ISDN6DISCONNECT: Interface BRI0:1 disconnected from 6106

Spicey, call lasted 149 seconds


01:24:03: %LINEPROTO5UPDOWN: Line protocol on Interface BRI0:1,

changed state to down

Aton#show frame map

Serial1.1 (down): pointtopoint dlci, dlci 160(0xA0,0x2800), broadcast

status deleted

Aton#

01:26:35: %LINK3UPDOWN: Interface Serial1, changed state to up

01:26:36: %LINEPROTO5UPDOWN: Line protocol on Interface Serial1,

changed state to up

01:26:56: %ISDN6LAYER2DOWN: Layer 2 for Interface BRI0, TEI 64 changed

to down

01:26:56: %ISDN6LAYER2DOWN: Layer 2 for Interface BR0, TEI 64 changed

to down01:26:56: %LINK5CHANGED: Interface BRI0, changed state to standby mode


43/73



Aton#show frame map

Serial1.1 (up): pointtopoint dlci, dlci 160(0xA0,0x2800), broadcast


Aton#ping 124.124.124.1




Aton#ping 124.124.124.1




Local 1 0 0 0

Switched 0 0 0 0

Unused 0 0 0 0


Serial1.1







Spicey









!!!!!





!!!!!








inter area





C 155.155.155.0 is directly connected, Dialer2


C 3.1.3.0 is directly connected, Serial0.24.0.0.0/24 is subnetted, 1 subnets


44/73

C 4.0.1.0 is directly connected, Serial0.1


C 160.160.160.0 is directly connected, Dialer1



I 123.0.0.0/8 [100/8576] via 4.0.1.2, 00:00:55, Serial0.1

I 122.0.0.0/8 [100/8576] via 3.1.3.3, 00:00:35, Serial0.2

Both serial lines from the calling sides are going down.

Spicey#

*Mar 1 01:21:30.171: %LINK3UPDOWN: Interface BRI0:1, changed state toup

*Mar 1 01:21:30.627: %DIALER6BIND: Interface BR0:1 bound to profile Di2




to 6104 Aton

*Mar 1 01:21:40.923: %LINK3UPDOWN: Interface BRI0:2, changed state to up

*Mar 1 01:21:41.359: %DIALER6BIND: Interface BR0:2 bound to profile Di1




to 6105 Prasit*Mar 1 01:23:59.819: %DIALER6UNBIND: Interface BR0:1 unbound from

profile Di2


from 6104 Aton, call lasted 149 seconds




*Mar 1 01:24:03.015: %DIALER6UNBIND: Interface BR0:2 unbound from

profile Di1


from 6105 Prasit, call lasted 142 seconds




Spicey#show frame map

Serial0.1 (down): pointtopoint dlci, dlci 140(0x8C,0x20C0), broadcast

status defined, inactive

Serial0.2 (down): pointtopoint dlci, dlci 130(0x82,0x2020), broadcast

status defined, inactive

Spicey#

Both serial lines are available again.

Spicey#show frame pvc



Local 2 0 0 0

Switched 0 0 0 0

Unused 0 0 0 0


Serial0.2








45/73


46/73

inter area







S 124.124.124.0 [250/0] via 160.160.160.1





*Mar 1 01:21:38.967: %LINK3UPDOWN: Interface BRI0:1, changed state to

up.!!!!


Prasit#




to 6106 Spicey




!!!!!


Prasit#

Serial 1 becomes active again.

Prasit#

*Mar 1 01:26:40.579: %LINK3UPDOWN: Interface Serial1, changed state to up


Serial1, changed state to up

*Mar 1 01:27:01.051: %ISDN6LAYER2DOWN: Layer 2 for Interface BRI0,

TEI 64 changed to down

*Mar 1 01:27:01.055: %ISDN6LAYER2DOWN: Layer 2 for Interface BR0, TEI

64 changed to down

*Mar 1 01:27:01.363: %LINK5CHANGED: Interface BRI0, changed state to standby mod



Prasit#show frame map






!!!!!





Local 1 0 0 0Switched 0 0 0 0


47/73

Unused 0 0 0 0


Serial1.1







Configuring Frame Relay Switching

Frame Relay switching is a means of switching packets based on the datalink connection identifier (DLCI).

We can look on this as the Frame Relay equivalent of a Media Access Control (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:

Frame Relay data terminal equipment (DTE) the router or access server.

Frame Relay data circuitterminating equipment (DCE) switch.

Note: In Cisco IOS Software release 12.1(2)T and later, the frame route command has been replaced by the

connect command.

Let's look at a sample configuration. In the configuration below, we are using the router America as a Frame

Relay switch. We are using Spicey as a hub router and Prasit and Aton as spoke routers. We have connected

them as follows:

Prasit serial 1 (s1) DTE is connected to America serial 1/4 (s1/4) DCE.

Spicey serial 0 (s0) DTE is connected to America serial 1/5 (s1/5) DCE.

Aton serial 1 (s1) DTE is connected to America serial 3/4 (s3/4) DCE.

Network Diagram

This document is based on the following configuration:

Configurations

Spicey

Prasit


48/73


49/73

!

router rip

network 3.0.0.0

network 123.0.0.0

!

!

line con 0

exectimeout 0 0


line aux 0

line vty 0 4

login

!

end

Aton




!

version 12.0




!

hostname Aton

!

!

!

interface Ethernet0

ip address 122.122.122.1 255.255.255.0

!

interface Serial1

ip address 3.1.3.3 255.255.255.0



!

router rip

network 3.0.0.0

network 122.0.0.0

!

!

line con 0

exectimeout 0 0


line aux 0

line vty 0 4

login

!

end

America

america#show runningconfig



!

!




!

hostname america

!


50/73


51/73










Prasit







Local 1 0 0 0

Switched 0 0 0 0Unused 0 0 0








Aton


Serial1 (up): ip 3.1.3.1 dlci 160(0xA0,0x2800), dynamic, broadcast, status defined, act




Local 1 0 0 0

Switched 0 0 0 0

Unused 0 0 0 0

DLCI = 160, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial


out bytes 3366 dropped pkts 0 in FECN pkt 0





Configuring Frame Relay DLCI Prioritization

Datalink connection identifier (DLCI) prioritization is the process whereby different traffic types are placed

upon separate DLCIs so that a Frame Relay network can provide a different committed information rate for

each traffic type. It can be used in conjunction with either custom queuing or priority queuing to provide

bandwidth management control over the access link to the Frame Relay network. In addition, some Frame

Relay service providers and Frame Relay switches (such as the Stratacom Internetwork Packet Exchange

[IPX], IGX and BPX or AXIS switches) actually provide prioritization within the Frame Relay cloud based on

this priority setting.


52/73

Implementation Considerations

When implementing DLCI prioritization, please note the following points:

If a secondary DLCI goes down, you lose traffic destined for that queue only.

If you lose the primary DLCI, the subinterface goes down and you lose all traffic.

Network Diagram

In order to use this setup, you need to have four DLCIs for the side that will use the DLCI prioritization. In

this example, we have configured Spicey for priority queueing as follows:

Ping is in the highpriority queue.

Telnet is in the mediumpriority queue.

File Transfer Protocol (FTP) is in the normalpriority queue.

All other IP traffic is in the lowpriority queue.

Note: Make sure you configure the DLCIs to correspond with the priority list, or the system will not use the

correct queue.

Configurations

Spicey

Prasit

Spicey




!

version 12.1


service timestamps log datetime msec!

hostname Spicey

!

!

interface Ethernet0

ip address 124.124.124.1 255.255.255.0

!

interface Serial0

no ip address


prioritygroup 1

!


ip address 4.0.1.1 255.255.255.0


53/73

framerelay prioritydlcigroup 1 140 180 190 200


!

router igrp 2

network 4.0.0.0

network 124.0.0.0

!

accesslist 102 permit icmp any any

prioritylist 1 protocol ip high list 102

prioritylist 1 protocol ip medium tcp telnet

prioritylist 1 protocol ip normal tcp ftp

prioritylist 1 protocol ip low

!

line con 0

exectimeout 0 0


line aux 0

line vty 0 4

login

!

end

PrasitPrasit#show runningconfig


!

version 12.1



!

hostname Prasit

!

!

!

interface Ethernet0

ip address 123.123.123.1 255.255.255.0

!

interface Serial1

ip address 4.0.1.2 255.255.255.0


!

router igrp 2

network 4.0.0.0

network 123.0.0.0

!

line con 0

exectimeout 0 0


line aux 0line vty 0 4

login

!

end


Use the following show and debug commands to test that your network is operating properly. Before issuing

debug commands, please see Important Information on Debug Commands.

show framerelay pvc

show framerelay map


54/73

show queueing priority

debug priority

The output shown below is a result of entering these commands on the devices we are using in this sample

configuration.

Spicey

Spicey#show framerelay pvcPVC Statistics for interface Serial0 (Frame Relay DTE)


Local 4 0 0 0

Switched 0 0 0 0

Unused 0 0 0 0






out bcast pkts 0 out bcast bytes 0pvc create time 00:29:22, last time pvc status changed 00:20:37

Priority DLCI Group 1, DLCI 140 (HIGH), DLCI 180 (MEDIUM)

DLCI 190 (NORMAL), DLCI 200 (LOW)


















in BECN pkts 0 out FECN pkts 0 out BECN pkts 0in DE pkts 0 out DE pkts 0






Priority DLCI Group 1, DLCI 140 (HIGH), DLCI 180 (MEDIUM)

DLCI 190 (NORMAL), DLCI 200 (LOW)

Spicey#show queueing priority

Current priority queue configuration:

List Queue Args1 high protocol ip list 102


55/73

1 medium protocol ip tcp port telnet

1 normal protocol ip tcp port ftp

Documents

Frame Relay Guide