Frame-relay config help

[enzo288]

I am trying to configure a frame-relay switch for a lab setup connecting three other routers to the FR switch via V.35 DCE/DTE cables. The configuration has been checked and re-checked however, the routers will not communicate w/ one another. When I enter the sh frame lmi command, the num status timeouts field is usually around 30-60 while num update status recvd is 0. The Num Status Enq. Sent and Num Status msgs Rcvd are always equal. I think this may be the reason for the inability of the routers to ping one another. TIA

 

[KiscoKid]

You don't mention your frame-relay topology (e.g. point2point, hub&spoke etc) which would be helpful in determing whether you can utilise Inverse ARP (for dynamic IP address resolution) or frame relay mapping (for static IP).

From what you've said though it does look as if you are communicating successfully with your frame relay switch as you're seeing LMI Rcvd. Check all DCE routers to ensure this is the case.

What do you see when you use the following cmd: show frame-relay map? Depending on your topology, you should learn the peer IP address either dynamically (Inverse ARP) or statically (frame relay map) or not at all of course if incorrectly configured.

There's so many different permutations of frame relay configuration that I've posted a link below I've used before on many occasions for guidance in configuring and troubleshooting frame relay.

I hope this document helps you. If not, I may need significantly more info inc. topology overview and running configurations of the DTE routers.

http://www.cisco.com/en/US/tech/tk713/tk237/technologies_tech_note09186a008014f8a7.shtml#topic7

 

[enzo288]

Thank you for your response. I will include a basic FR config which I have recently used.

FRAME SWITCH:
hostname frame_switch
!
frame-relay switching
!
interface Ethernet0
no ip address
shutdown
!
interface Serial0
no ip address
encapsulation frame-relay
no fair-queue
clockrate 148000
frame-relay intf-type dce
frame-relay route 121 interface Serial1 120
frame-relay route 152 interface Serial5 151
!
interface Serial1
no ip address
encapsulation frame-relay
clockrate 148000
frame-relay intf-type dce
frame-relay route 110 interface Serial5 111
frame-relay route 120 interface Serial0 121
frame-relay route 130 interface Serial3 131
!
interface Serial2
no ip address
shutdown
!
interface Serial3
no ip address
encapsulation frame-relay
clockrate 64000
frame-relay intf-type dce
frame-relay route 131 interface Serial1 130
!
interface Serial4
no ip address
shutdown
!
interface Serial5
no ip address
encapsulation frame-relay
clockrate 64000
frame-relay intf-type dce
frame-relay route 111 interface Serial1 110
frame-relay route 151 interface Serial0 152

ROUTER 1:
interface Serial0
no ip address
encapsulation frame-relay
no ip mroute-cache
!
interface Serial0.1 multipoint
ip address 10.10.1.9 255.255.255.248
no ip split-horizon eigrp 666
frame-relay map ip 10.10.1.10 110 broadcast
frame-relay map ip 10.10.1.11 120 broadcast
!
interface Serial0.2 point-to-point
ip address 192.168.1.5 255.255.255.252
frame-relay interface-dlci 130
!
router eigrp 666
network 10.0.0.0
network 192.168.1.0
no auto-summary
!
________________________________________________________________
ROUTER 2:
ip subnet-zero
!
interface Serial0
ip address 10.10.1.10 255.255.255.248
no ip directed-broadcast
encapsulation frame-relay
no ip mroute-cache
no arp frame-relay
frame-relay map ip 10.10.1.9 111 broadcast
frame-relay map ip 10.10.1.11 111 broadcast
no frame-relay inverse-arp
!
interface TokenRing0
ip address 10.10.3.3 255.255.255.0
no ip directed-broadcast
ring-speed 16
!
router eigrp 666
network 10.0.0.0
________________________________________________________________
ROUTER 3:
ip subnet-zero
!
interface Ethernet0
ip address 10.10.5.5 255.255.255.0
no ip directed-broadcast
!
interface Serial0
ip address 10.10.1.11 255.255.255.248
no ip directed-broadcast
encapsulation frame-relay
no ip mroute-cache
no arp frame-relay
frame-relay map ip 10.10.1.9 121 broadcast
frame-relay map ip 10.10.1.10 121 broadcast
no frame-relay inverse-arp
!
router eigrp 666
network 10.0.0.0
________________________________________________________________
ROUTER 4
interface Ethernet0
ip address 10.10.6.6 255.255.255.0
!
interface Serial0
ip address 192.168.1.6 255.255.255.252
encapsulation frame-relay
frame-relay interface-dlci 131
!
router eigrp 666
network 10.0.0.0
network 192.168.1.0
no auto-summary

Even a simple and straight forward configuration like this and I cannot get the DTE routers to communicate w/ each other. I admit that I am relatively new to this and I realize that I may have overlooked something easy but I can't figure out what it is. In the meantime, I will parse through the link yo provided. Thanks.

 

[KiscoKid]

It is difficult to visalise your network given the info above but if I'm right (please confirm if I have this wrong)

router 1 attaches to s1 on fr switch
router 2 attaches to s5 on fr switch
router 3 attaches to s0 on fr switch
router 4 attaches to s3 on fr switch

That said, some comments:

1. You shouldn't map two frame relay peers via the same local DLCI. Case in point, on router 2 you are telling it that to get to router 1 and 3 use DLCI 111. However your switch only knows that to get to 111 ie point it out of serial1, i.e. router 1. Try defining individual DLCI's for each router you want to access from a device.

2. Try re-enabling frame-relay arp (i.e. negate the no arp frame-relay on some of the configs above.) With no Inverse ARP or indeed any ARP enabled, I'm not sure you're going to be able to resolve IP addresses.

3. I would try configuring a basic fr setup 1st, say between router 2 and router 3. Ensure you get connectivity before you progress to building more complex solutions.

4. Is there any reason why you've preferred to use static mapping over Inverse ARP? In your environment you could certainly run it and it makes configuration so much easier.

Let me know how you get on.