Frame Relay not pinging

[akafinal]

Hi all, 

This is my first post, please be gentle. 

I have 3 routers (All ISR4321 routers) with these configs: 

---------------R1-----------------

int s0/1/0
ip add 10.1.1.1 255.255.255.252
en frame-relay
no frame-relay inverse-arp
frame-relay map ip 10.1.1.2 103 broadcast
frame-relay map ip 10.1.1.1 103
no shut

---------------R2-----------------
frame-relay switching
int s0/1/0
en frame-relay
frame-relay intf-type dce
frame-relay route 103 int s0/1/1 301
no shut

int s0/1/1
en frame-relay
frame-relay intf-type dce
frame-relay route 301 int s0/1/0 103
no shut

---------------R3-----------------

int s0/1/1
ip add 10.1.1.2 255.255.255.252
en frame-relay
no frame-relay inverse-arp
frame-relay map ip 10.1.1.1 301 broadcast
frame-relay map ip 10.1.1.2 301
no shut

I know it's a very simple set up but I'm still not able to ping from R1 to R3: 

R1#ping 10.1.1.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.2, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)

I have gone through some troubleshooting myself with these commands: 

  show frame-relay pvc
  show frame-relay map
  show frame-relay route
  debug frame-relay lmi

Everything's up like in the docos (unless i'm missing something) but still not pinging. 

I've also attached the Cisco lab file here just in case. 

Any help will be much appreciated, 

Dan 

[Georg Pauwen]

Very odd indeed. I wonder if it has to do with the 4321 and/or the NIM with the seral interfaces...

Either way, try and disable keepalives ('no keepalive') on all serial interfaces on all three routers and check if that makes a difference...

[akafinal]

Yeah, I looked up keepalive and turned it off on all routers. Still a no. I may have to discuss this with my supervisor if we need to get in touch with Cisco. Anyway, thanks Georg

[Georg Pauwen]

Hello,

I read through your lab file again, did you actually set the clock rate on tthe DCE interfaces:

frame-relay switching
int s0/1/0
en frame-relay

clock rate 128000
frame-relay intf-type dce
frame-relay route 103 int s0/1/1 301
no shut

int s0/1/1
en frame-relay

clock rate 128000
frame-relay intf-type dce
frame-relay route 301 int s0/1/0 103
no shut

[akafinal]

Hi Georg,
I've re-read the lab file again. It doesn't require to configure clock rate on the hub router (R2) as the DCE here is only logical. Also, I've tried same commands on another three 2811 Routers (running IOS Version 15.1(4)M10, RELEASE SOFTWARE (fc2)), worked straight away. So I'm leaning towards the conclusion that it's a bug on IOS 16.7.1.

[Georg Pauwen]

Hello,

which interface/NIM are you using on the 4321 routers ? I just remembered that, if you use the Fourth-Generation T1/E1 Voice and WAN Network Interface Modules (NIMs), you need to globally configure:

network-clock synchronization automatic

which is disabled by default...

Check this link for reference:

https://www.cisco.com/c/en/us/td/docs/routers/access/4400/feature/guide/isr4400netclock.html

[akafinal]

Hi Georg,

Sorry I'm not sure what NIM version it is but I've attached the result of show inventory to this post.
I've configured 'network-clock synchronization automatic' on all routers but still same result.
Thanks Georg anw for replying to my post.

[Georg Pauwen]

What if you set the clock source to primary under the controller settings of R2 ?

controller [t1|e1] slot/bay/port

clock source line primary

[akafinal]

Hey I've tried but it doesn't have a controller option on any modes (enable, global or interface)

[paul driver]

Hello

Your problem seems to be the cabling between R1 and R2 

The serial interface types on R1 is showing as DCE  and R2 it is showing DTE , these should be the other away around.

You could try manually setting it on R1 or  try testing connectivity using Serial0/1/1 instead but i am thinking its the physical cabling from what the controller interface output is showing

R1
int ser0/1/0

frame-relay intf-type dte

---------------------------------R1------------------------------------
Serial0/1/0 - (NIM-2T) is up
Encapsulation : Frame Relay
Cable type: V.35 DCE <--------------------------Should be DTE
mtu 1500, max_buffer_size 1524, max_pak_size 1608 enc 84
loopback: Off, crc: 16, invert_data: Off
nrzi: Off, idle char: Flag
dce_terminal_timing_enable: Off ignore_dtr: Off
serial_clockrate: 2000000bps, serial_clock_index: 0
serial_restartdelay:60000, serial_restartdelay_def:60000

RTS up, CTS up, DTR up, DCD up, DSR up

---------------------------------R2------------------------------------
Serial0/1/0 - (NIM-2T) is up
Encapsulation : Frame Relay
Cable type: V.35 DTE
mtu 1500, max_buffer_size 1524, max_pak_size 1608 enc 84
loopback: Off, crc: 16, invert_data: Off
nrzi: Off, idle char: Flag
tx_invert_clk: Off, ignore_dcd: Off
rx_clockrate: 2015947, rx_clock_threshold: 0
serial_restartdelay:60000, serial_restartdelay_def:60000

RTS up, CTS up, DTR up, DCD up, DSR up

[akafinal]

Hi Paul,

Physically, R1 S0/1/0 is DCE and R2 S0/1/0 is DTE - that's normal set up in my lab. In the lab file, the instructions say to make all R2 interfaces logical DCE hence the conflicts. However, it also explains in the lab (page 4) that:
"Changing the interface type to DCE tells the router to send Local Management Interface (LMI) keepalives and allows
Frame Relay route statements to be applied.
Note: Frame Relay interface types do not need to match the underlying physical interface type. A physical DTE serial
interface can act as a Frame Relay DCE interface, and a physical DCE interface can act as a logical Frame Relay
DTE interface. "
So I think the conflict here would not matter that much but please correct me if that's wrong.

[paul driver]

Hello

Regardless of the physical nature of the interface, What I see if you have (R2) as the FR switch and its interface towards R1 needs to be set as a DCE as its providing the clocking otherwise it will not work.