cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1935
Views
17
Helpful
16
Replies

Frame-rely troubleshooting

chrisblaze
Level 1
Level 1

I have been trying to configure frame relay for the past two days, my protocol will not stay up. Below is my running config on both routers:

R1

sh run

Building configuration...

Current configuration : 1132 bytes

!

version 12.3

service timestamps debug datetime msec

service timestamps log datetime msec

no service password-encryption

!

hostname R1

!

boot-start-marker

boot-end-marker

!

enable secret 5 $1$uHaf$uhnNzXlrRKb2jSD7F1IFt/

!

username R2 password 0 cisco

memory-size iomem 10

no network-clock-participate slot 1

no network-clock-participate wic 0

no aaa new-model

ip subnet-zero

ip cef

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

interface FastEthernet0/0

ip address 10.0.0.1 255.255.255.128

duplex auto

speed auto

!

interface Serial0/0

ip address 172.16.0.1 255.255.255.252

encapsulation ppp

clockrate 64000

no fair-queue

ppp authentication chap

!

interface BRI0/0

no ip address

shutdown

!

interface Serial0/1

ip address 172.16.0.9 255.255.255.252

encapsulation frame-relay

frame-relay map ip 172.16.0.10 101 broadcast

frame-relay lmi-type ansi

!

router rip

version 2

network 10.0.0.0

network 172.16.0.0

!

ip http server

no ip http secure-server

ip classless

!

!

!

!

!

!

!

!

!

banner motd ^CHELP!!!^C

!

line con 0

password cisco

logging synchronous

login

line aux 0

line vty 0 4

password cisco

login

!

!

end

and here is R3:

sh run

Building configuration...

Current configuration : 1156 bytes

!

version 12.3

service timestamps debug datetime msec

service timestamps log datetime msec

no service password-encryption

!

hostname R3

!

boot-start-marker

boot-end-marker

!

enable secret 5 $1$Xi9C$K2BeD99qLoFVfZlMprcIk0

!

memory-size iomem 10

no network-clock-participate slot 1

no network-clock-participate wic 0

no aaa new-model

ip subnet-zero

ip cef

!

!

no ip domain lookup

!

!

!

!

!

!

!

!

!

!

!

!

interface FastEthernet0/0

no ip address

shutdown

duplex auto

speed auto

!

interface Serial0/0

bandwidth 64

ip address 172.16.0.10 255.255.255.252

encapsulation frame-relay

no fair-queue

frame-relay map ip 172.16.0.9 102 broadcast

frame-relay lmi-type ansi

!

interface BRI0/0

no ip address

shutdown

!

interface FastEthernet0/1

ip address 10.0.0.129 255.255.255.128

duplex auto

speed auto

!

interface Serial0/1

ip address 172.16.0.6 255.255.255.252

!

router rip

version 2

network 10.0.0.0

network 172.16.0.0

!

ip http server

no ip http secure-server

ip classless

!

!

!

!

!

!

!

!

!

banner motd ^CLast Lab!!!^C

!

line con 0

password cisco

logging synchronous

login

line aux 0

line vty 0 4

password cisco

login

!

!

end

Can someone tell me what I did wrong?

16 Replies 16

Christopher

If the router are connected back to back then there are 2 things that you must change.

- configure both serial interfaces with "no keepalive". Since the keepalive in Frame Relay is provided by LMI and since there is no LMI without a device operating as a frame relay switch, then you need to configure the interfaces to not use keepalives.

- the DLCI on both interfaces must be the same. They can be DLCI 100 or they can be DLCI 101. But you can not have 100 on one end and 101 on the other end if they are connected back to back with no frame relay switch. Having different DLCIs on the interface works fine if there is a frame relay switch. But with no frame relay switch both interfaces must have the same DLCI.

I am not sure that the frame relay map is correct (the way you have configured it the map on one router is pointing to the DLCI of the other router, but the map should point to the DLCI of the local router). But that is less important than fixing the keepalive and DLCI values. And when both interfaces are using the same DLCI then it will be obvious that both maps should have the same DLCI.

HTH

Rick

HTH

Rick

Thanks for all the help, the problem was because I had to different DLCIs on the same serial connections, also Rick hit it on the head, when I added the "no keeplive" to both ends along with matching DLCIs, the protocol came up.

Thanks!!!!