01-18-2006 07:37 AM - edited 03-03-2019 11:29 AM
Hi everyone,
I am having some problems configuring frame-relay access between a cisco router 2600 and an eicon card c91 v2.
Apparently the configurations on both side are OK,the line is up, but the protocol is down and i still receive the DCE down message in debugging.
My router configuration for the interface is:
p address 192.168.1.1 255.255.255.252
encapsulation frame-relay IETF
frame-relay interface-dlci 16
frame-relay lmi-type ansi
frame-relay intf-type dce
the eicon is also configured to lmi annex d as DTE.
Does anyone have faced similar situations
I would apreciate any sugestions
Thank you in advance
David Almada
01-18-2006 08:26 AM
Hello,
You can turn on "debug frame-relay lmi" and watch out for incoming keepalives on the router.
Also give it a try and check connectivity when removing the lmi and setting no keepalive on the router interface (and respective config on the eicon).
The PVC is considered to be up all the time then and IP connectivity should be given, if the DLCI values are matching. They are 16 on both ends, aren´t they?
Hope this helps! Please rate all posts.
regards, Martin
P.S.: In case you get stuck with the debug output interpretation you can post the debug output for further analysis?
01-18-2006 09:09 AM
Hi Martin,
I did it, and now the link and protocol are up, but I still can´t ping the remote ip 192.168.1.2
the interface now looks like this:
interface Serial1/7
ip address 192.168.1.1 255.255.255.252
encapsulation frame-relay IETF
no keepalive
frame-relay interface-dlci 16
and debug give :
Serial1/7(o):Pkt sent on dlci 16(0x401), pkt encaps 0x300 0x8000 0x0 0x806 (ARP), datagramsize 30
Serial1/7(i): dlci 16(0x401), NLPID 0x3CC(IP), datagramsize 64
Serial1/7:Encaps failed--no map entry link 7(IP)
Serial1/7(o): dlci 16(0x401), pkt encaps 0x0300 0x8000 0x0000 0x806 (ARP), datagramsize 30
FR: Sending INARP Request on interface Serial1/7 dlci 16 for link 7(IP)
broadcast dequeue
when I try a ping:
Serial1/7(o):Pkt sent on dlci 16(0x401), pkt encaps 0x300 0x8000 0x0 0x806 (ARP), datagramsize 30
Serial1/7:Encaps failed--no map entry link 7(IP)
Serial1/7:Encaps failed--no map entry link 7(IP)
Serial1/7:Encaps failed--no map entry link 7(IP)
Serial1/7:Encaps failed--no map entry link 7(IP)
Serial1/7:Encaps failed--no map entry link 7(IP)
Thanks for your help
David
01-18-2006 09:19 AM
David,
I think you need to map to the other side, try to add the following command:
frame-relay map ip 192.168.1.2 16 broadcast
to the serial interface...
Regards,
GP
01-18-2006 09:39 AM
Hi, GP
few moments after I sent the debug I receveid this messages:
Serial1/7(i): dlci 16(0x401), pkt encaps 0x0300 0x8000 0x0000 0x806 (ARP), datagramsize 30
Serial1/7: FR ARP input
datagramstart = 0x1B0070E, datagramsize = 30
FR encap = 0x04010300
80 00 00 00 08 06 00 0F 08 00 02 04 00 01 00 00
C0 A8 CC 06 00 00 C0 A8 CC 06
after that i Try ping but it still fails ( the logg messages are):
Serial1/7(o): dlci 16(0x401), NLPID 0x3CC(IP), datagramsize 104
Serial1/7(o): dlci 16(0x401), NLPID 0x3CC(IP), datagramsize 104
Serial1/7(o): dlci 16(0x401), NLPID 0x3CC(IP), datagramsize 104
Serial1/7(o): dlci 16(0x401), NLPID 0x3CC(IP), datagramsize 104
Serial1/7(o): dlci 16(0x401), NLPID 0x3CC(IP), datagramsize 104
I get the same messages after the frame relay map
Thanks
David
01-18-2006 09:59 AM
Hello David,
I just had a look at the technical specs of the EICON card, but honestly I do not see the card supporting frame relay at all...maybe I am missing something.
By the way, do you have 'frame-relay switching' enabled globally on the Cisco router ?
Regards,
GP
01-18-2006 10:21 AM
GP,
I have another point -to-point link using the same devices,i.e, another interface on the same router and an eicon card with the same specifications. And it is working just fine.The strange thing is that I did exactly the same thing. I setup both the circuits.
David
01-18-2006 08:50 AM
Hello David,
usually, the DCE end of the connection needs the 'clock rate' command, you might want to try and configure this:
ip address 192.168.1.1 255.255.255.252
encapsulation frame-relay IETF
frame-relay interface-dlci 16
--> clock rate 125000
frame-relay lmi-type ansi
frame-relay intf-type dce
Regards,
GP
01-18-2006 09:02 AM
Hello GP,
just as a sidenote:
The "clock rate" command is needed on a Serial DCE side - OSI layer 1.
The "frame-relay intf-type dce" command specifies the Frame Relay DCE side - OSI layer 2.
They both do two different things and can be used independantly. You could have f.e. Serial DCE on one side and FR DCE on the other side.
But nevertheless this is a valid point, a missing "clock rate" can also prevent connectivity. The interface however is UP/DOWN, so I assume that the clock rate might not be the issue as I would expect a DOWN/DOWN in case this would be the origin of the problem.
Hope this helps! Please rate all posts.
Regards, Martin
01-18-2006 12:44 PM
Hi everyone,
The messages on debug reveal that I am receiving( and replying) ping from the remote location, but it seems that the remote location ( PC with windows XP with firewall deactivated)
does not accept my packets. The same when I do the Ping, a do not get replies.
ICMP: echo reply sent, src 192.168.1.1, dst 192.168.1.2
Serial1/7(o): dlci 16(0x401), NLPID 0x3CC(IP), datagramsize 64
Serial1/7(i): dlci 16(0x401), NLPID 0x3CC(IP), datagramsize 64
ICMP: echo reply sent, src 192.168.1.1, dst 192.168.1.2
Serial1/7(o): dlci 16(0x401), NLPID 0x3CC(IP), datagramsize 64
Serial1/7(i): dlci 16(0x401), NLPID 0x3CC(IP), datagramsize 64
ICMP: echo reply sent, src 192.168.1.1, dst 192.168.1.2
Serial1/7(o): dlci 16(0x401), NLPID 0x3CC(IP), datagramsize 64
Serial1/7(i): dlci 16(0x401), NLPID 0x3CC(IP), datagramsize 64
ICMP: echo reply sent, src 192.168.1.1, dst 192.168.1.2
Serial1/7(o): dlci 16(0x401), NLPID 0x3CC(IP), datagramsize 64
Thank y'all
12-02-2007 11:56 PM
dalmada,
I have exactly the same problem, did you get to fix this problem.
Thanks
MNOUR
12-03-2007 02:05 AM
Hi mnour,
Yes, it was a problem with clock/speed settings on modems ( Nokia BB 256K).
int s1/0
ip address x.x.x.x y.y.y.y
encapsulation frame-relay IETF
frame-relay interface-dlci 16
frame-relay intf-type dce
Hope it helps
David
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide