05-06-2009 07:46 PM - edited 03-04-2019 04:40 AM
Hello all,
I am having an issue with frame relay and rip. For some reason I cannot send pings to R3 over frame relay. Here are my configs
Here are the configs for R1
router rip
version 2
redistribute connected
passive-interface FastEthernet0/1
network 10.0.0.0
network 172.16.0.0
default-information originate
no auto-summary
interface Serial0/0/1
ip address 172.16.0.9 255.255.255.252
encapsulation frame-relay
frame-relay map ip 172.16.0.10 103 broadcast
frame-relay interface-dlci 103
frame-relay lmi-type ansi
no keepalive
Configs for R3
interface Serial0/0/0
ip address 172.16.0.10 255.255.255.252
encapsulation frame-relay
frame-relay map ip 172.16.0.9 301 broadcast
frame-relay interface-dlci 301
frame-relay lmi-type ansi
no keepalive
clock rate 4000000
router rip
version 2
redistribute connected
passive-interface FastEthernet0/1
network 10.0.0.0
network 172.16.0.0
default-information originate
no auto-summary
I was told that there was supposed to be 7 entries for RIP, but I am not sure what I am missing. Can any of you point me in the right direction please?
05-07-2009 04:50 AM
Hello Joshua,
I would remove frame-relay interface-dlci XX commands they are good for point-to-point subinterfaces and you are using the main interfaces.
Notice that if the two are directy connected to each other (I see you have the clock on one side) the DLCI cannot change and one of the two should use
frame-relay intf-type dce
Hope to help
Giuseppe
05-07-2009 08:34 PM
so your saying my frame relay dcli 103 and 301 commands should not be in there?
Does it matter which two use
frame-relay intf-type dce ?
also what does that command do?
05-07-2009 08:52 PM
I tried entering that command and in the packet tracer file it says the command is unreconized
05-07-2009 09:37 PM
I can upload the packet tracer file that I been practicing on
05-07-2009 10:04 PM
Packet Tracer does not handle alot of Frame relay commands. You can use the 'cloud', but as for commands like frame-reley switching and other commands, it wont work for that.
05-07-2009 10:17 PM
ic ic.
Right now there is not frame relay switching going on. Its just two serial links (its part of a lab I am testing out).
05-08-2009 11:55 AM
I plugged in your config and troubleshot it for about an hour, no good....the output below shows it 'should' work...but sometimes with PacketTracer you have to be careful, you could be doing everything right, but PT will say your wrong...I will plug the configs into a lab enviroment Monday or Tuesday and let you know how it goes then.
R1#sh frame-relay map
Serial1/0 (up): ip 172.16.0.10 dlci 103, static, broadcast, CISCO, status defined, active
Serial1/0 (up): ip 172.16.0.9 dlci 103, static, CISCO, status defined, active
R1#sh frame-relay pvc
PVC Statistics for interface Serial1/0 (Frame Relay DTE)
DLCI = 103, DLCI USAGE = LOCAL, PVC STATUS = STATIC, INTERFACE = Serial1/0
input pkts 14055 output pkts 32795 in bytes 1096228
out bytes 6216155 dropped pkts 0 in FECN pkts 0
in BECN pkts 0 out FECN pkts 0 out BECN pkts 0
in DE pkts 0 out DE pkts 0
out bcast pkts 32795 out bcast bytes 6216155
R1#ping 172.16.0.9
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.0.9, timeout is 2 seconds:
.....
05-08-2009 03:10 PM
thank you jim, I appreciate you helping me out>
05-08-2009 05:59 PM
I started a new thread:
I never could get it working (on real routers), so I am only left to believe it cant. Did you lab say it should work? Was it a cisco netacad lab?
05-10-2009 07:07 AM
This got solved by another member in the thread listed above. It wasnt an issue with Packet Tracer, but more so an error in logic between my keyboard and the seat of my chair :P
05-10-2009 07:50 AM
It was a cisco netacad lab. I will check out the thread you linked above.
thx for all your help!
05-10-2009 07:52 AM
What do you mean maped to the same dlci's?
05-10-2009 08:06 AM
Dont get too caught up in getting this to work, as I understand it in the real world you would have a dedicated FR Switch, not a router mimicking one. PT still didnt take the no frame-relay inverse arp, but I got the config below working in the on real 2811s.
Here are my configs:
For one:
interface Serial0/0
ip address 172.16.0.10 255.255.255.252
encapsulation frame-relay
no keepalive
no fair-queue
clock rate 64000
frame-relay map ip 172.16.0.9 103 broadcast
frame-relay map ip 172.16.0.10 103
no frame-relay inverse-arp
end
For the other:
Current configuration : 216 bytes
!
interface Serial0/1
ip address 172.16.0.9 255.255.255.252
encapsulation frame-relay
no keepalive
frame-relay map ip 172.16.0.9 103
frame-relay map ip 172.16.0.10 103 broadcast
no frame-relay inverse-arp
end
05-10-2009 02:47 PM
I appreciate all the help. I understand that in this lab we do not have a frame relay switch (in the other labs we did have one).
Ya no frame relay inverse-arp does not work on PT (not sure if it works in Packet Tracer 5.1).
the no fair-queue whats that? I never used that command. Other than that I have similar commands entered on the PT routers.
I wonder if the frame relay inverse arp is whats keeping Packet tracer from completing it all?
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: