cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
818
Views
0
Helpful
8
Replies

missing rip routes

olakunle06
Level 1
Level 1

please i try to figure out what could be wrong but having issues. 2 nodes connected to switch 1 and 2,

I. from router 1 and 2 ROUTING TABLE,rip routes are not available why ?

2.i cant poing from node 1 to 2 but could do a telnet from 1 to2

3.i can ping fron node 2 to but sometimes have issue doing telnet to node1 it goes on and off.

please can anyone check config files and check where my mistakes are.thanks for anticipated help

8 Replies 8

andrew.prince
Level 10
Level 10

Cannot view the images - re-post in a png/jpg/bmp format.

find attached logs in text files.thanks for kind support

firstly - you are being creative with the 192.168.10.x subnet.

I take it this is a lab?

Secondly you are using layer 3 interfaces on the switches? I presume rt1 connects to sw1, then sw1 connects to sw2 and sw2 connects to rt2 ??

RIP ver 2 uses multicast to find neighbours.

RIP looks for a neighbor locally attached.

Enable rip on sw1 & sw2 - observe the results.

Tharak Abraham
Level 3
Level 3

You say that telnet is not consistent / flappy ?

1. Could you pls do a sh interface x and check for errors ?

2. Duplex mismatch ?

3. Any access-lists applied ?

no access rule applied but found errors as indicated below.so how can i rectify the problem,coulds be reason why i cant ping from node 1 to 2 but telnet and the flapping of telnet from 2 to 1.

Router2#sh int Fa0/3/0
FastEthernet0/3/0 is up, line protocol is up
  Hardware is Fast Ethernet, address is 0013.197e.bdf2 (bia 0013.197e.bdf2)
  MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 100Mb/s
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:00, output never, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 1000 bits/sec, 2 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     519009419 packets input, 3471320263 bytes, 0 no buffer
     Received 324459209 broadcasts, 0 runts, 0 giants, 0 throttles
     1 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 input packets with dribble condition detected
     84651618 packets output, 2180341204 bytes, 0 underruns
     0 output errors, 0 collisions, 1 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out

smc_switch2#show int fa0/4
FastEthernet0/4 is up, line protocol is up
  Hardware is Fast Ethernet, address is 0008.e3eb.a684 (bia 0008.e3eb.a684)
  MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive not set
  Auto-duplex (Full), Auto Speed (100), 100BaseTX/FX
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input never, output 00:00:00, output hang never
  Last clearing of "show interface" counters never
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 1000 bits/sec, 1 packets/sec
  5 minute output rate 2000 bits/sec, 2 packets/sec
     24447411 packets input, 246121532 bytes
     Received 10300265 broadcasts, 0 runts, 0 giants, 0 throttles
     54 input errors, 37 CRC, 17 frame, 0 overrun, 0 ignored
     0 watchdog, 3 multicast
     0 input packets with dribble condition detected
     39835744 packets output, 3061447006 bytes, 0 underruns
     0 output errors, 0 collisions, 1 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out

smc_switch1#show interfaces fa0/4
FastEthernet0/4 is up, line protocol is up
  Hardware is Fast Ethernet, address is 0008.e3eb.8e84 (bia 0008.e3eb.8e84)
  MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive not set
  Auto-duplex (Full), Auto Speed (100), 100BaseTX/FX
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input never, output 00:00:01, output hang never
  Last clearing of "show interface" counters never
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 2000 bits/sec, 3 packets/sec
     13597117 packets input, 1001816266 bytes
     Received 6735693 broadcasts, 0 runts, 0 giants, 0 throttles
     80 input errors, 46 CRC, 34 frame, 0 overrun, 0 ignored
     0 watchdog, 5 multicast
     0 input packets with dribble condition detected
     40231086 packets output, 2829649572 bytes, 0 underruns
     0 output errors, 0 collisions, 1 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out

thanks

Does RT1 DIRECTLY connect to RT2? not going thru any switches?

thanks for the feedback,r1 connects to r2 through the switch

Olkanule06,

I think you've got a couple of layer 1 and 2 problems as well as an underlaying design problem. Switch1 can only see switch2 from cdp which to me says you haven't got all the connectivity you need anyway. All your subnets that you have in your network are directly connected to both routers. thus you'll never see them as Rip routes anyway.

As this is a lab network remove the complexity to get the basics of level 1 and 2 connectivty down pat. I would remove 1 of the switches, and get the routers talking together on the same network. then add unique networks via loopbacks on R1 and R2 to see the subnets being advertised to it's opposite number.

hth

Tony

Getting Started

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:

Innovations in Cisco Full Stack Observability - A new webinar from Cisco