RIP Problem

XtendXtend Member Posts: 27 ■□□□□□□□□□
in CCNA & CCENT
I have 3 routers that i want to configure RIP on. Router HQ has 6 loopbacks, as well as router HR, and in middle as u can see in the topology i posted is Router Central with no loopbacks. My problem is this: i configured RIP on all 3 routers, but seems that the HQ loopbacks don't reach HR router, while HR routes reach HQ. I did a debug ip rip events to see what's going on and on HQ router all rip routes are advertised on fa0/0 (interface that connects to Central) while on HR, rip routes are advertise on each loopback. Dunno how to explain better, so i will give show the console output better:

HQ#debug ip rip events
RIP event debugging is on
HQ#
*Mar 1 02:14:38.459: RIP: sending v2 update to 224.0.0.9 via FastEthernet0/0 (192.168.10.2)
*Mar 1 02:14:38.463: RIP: Update contains 8 routes
*Mar 1 02:14:38.467: RIP: Update queued
*Mar 1 02:14:38.467: RIP: Update sent via FastEthernet0/0
HQ#
*Mar 1 02:14:50.387: RIP: received v2 update from 192.168.10.1 on FastEthernet0/0
*Mar 1 02:14:50.395: RIP: Update contains 7 routes
HQ#
*Mar 1 02:15:05.803: RIP: sending v2 update to 224.0.0.9 via FastEthernet0/0 (192.168.10.2)
*Mar 1 02:15:05.807: RIP: Update contains 8 routes
*Mar 1 02:15:05.811: RIP: Update queued
*Mar 1 02:15:05.811: RIP: Update sent via FastEthernet0/0
HQ#u all
HQ#sh ip route

192.168.10.0/24 is variably subnetted, 8 subnets, 2 masks
R 192.168.10.96/28 [120/2] via 192.168.10.1, 00:00:05, FastEthernet0/0
R 192.168.10.112/28 [120/2] via 192.168.10.1, 00:00:05, FastEthernet0/0
R 192.168.10.64/28 [120/2] via 192.168.10.1, 00:00:05, FastEthernet0/0
R 192.168.10.80/28 [120/2] via 192.168.10.1, 00:00:05, FastEthernet0/0
C 192.168.10.0/30 is directly connected, FastEthernet0/0
R 192.168.10.4/30 [120/1] via 192.168.10.1, 00:00:05, FastEthernet0/0
R 192.168.10.128/28 [120/2] via 192.168.10.1, 00:00:05, FastEthernet0/0
R 192.168.10.144/28 [120/2] via 192.168.10.1, 00:00:05, FastEthernet0/0
192.138.10.0/29 is subnetted, 6 subnets
C 192.138.10.8 is directly connected, Loopback0
C 192.138.10.16 is directly connected, Loopback1
C 192.138.10.24 is directly connected, Loopback2
C 192.138.10.32 is directly connected, Loopback3
C 192.138.10.40 is directly connected, Loopback4
C 192.138.10.48 is directly connected, Loopback5
78.0.0.0/30 is subnetted, 1 subnets
C 78.95.53.0 is directly connected, FastEthernet0/1
HQ#sh runn | s rip
router rip
version 2
network 192.168.10.0
no auto-summary
=====================
HR#debug ip rip events
RIP event debugging is on
HR#
*Mar 1 02:28:14.179: RIP: sending v2 update to 255.255.255.255 via FastEthernet0/1 (192.168.10.6)
*Mar 1 02:28:14.183: RIP: Update contains 8 routes
*Mar 1 02:28:14.183: RIP: Update queued
*Mar 1 02:28:14.183: RIP: Update sent via FastEthernet0/1
HR#
*Mar 1 02:28:16.811: RIP: sending v2 update to 224.0.0.9 via Loopback3 (192.168.10.113)
*Mar 1 02:28:16.815: RIP: Update contains 7 routes
*Mar 1 02:28:16.819: RIP: Update queued
*Mar 1 02:28:16.819: RIP: Update sent via Loopback3
*Mar 1 02:28:16.827: RIP: ignored v2 packet from 192.168.10.113 (sourced from one of our addresses)
HR#
*Mar 1 02:28:23.967: RIP: sending v2 update to 224.0.0.9 via Loopback1 (192.168.10.81)
*Mar 1 02:28:23.971: RIP: Update contains 7 routes
*Mar 1 02:28:23.971: RIP: Update queued
*Mar 1 02:28:23.975: RIP: Update sent via Loopback1
*Mar 1 02:28:23.991: RIP: ignored v2 packet from 192.168.10.81 (sourced from one of our addresses)
*Mar 1 02:28:24.139: RIP: sending v2 update to 224.0.0.9 via Loopback5 (192.168.10.145)
*Mar 1 02:28:24.143: RIP: Update contains 7 routes
*Mar 1 02:28:24.143: RIP: Update queued
*Mar 1 02:28:24.147: RIP: Update sent via Loopback5
*Mar 1 02:28:24.155: RIP: ignored v2 packet from 192.168.10.145 (sourced from one of our addresses)
HR#
*Mar 1 02:28:34.339: RIP: sending v2 update to 224.0.0.9 via Loopback0 (192.168.10.65)
*Mar 1 02:28:34.343: RIP: Update contains 7 routes
*Mar 1 02:28:34.347: RIP: Update queued
*Mar 1 02:28:34.347: RIP: Update sent via Loopback0
*Mar 1 02:28:34.355: RIP: ignored v2 packet from 192.168.10.65 (sourced from one of our addresses)
*Mar 1 02:28:34.567: RIP: sending v2 update to 224.0.0.9 via Loopback4 (192.168.10.129)
*Mar 1 02:28:34.567: RIP: Update contains 7 routes
*Mar 1 02:28:34.567: RIP: Update queued
*Mar 1 02:28:34.567: RIP: Update sent via Loopback4
*Mar 1 02:28:34.567: RIP: ignored v2 packet from 192.168.10.129 (sourced from one of our addresses)
HR#
*Mar 1 02:28:36.591: RIP: received v2 update from 192.168.10.5 on FastEthernet0/1
*Mar 1 02:28:36.595: RIP: Update contains 1 routes
*Mar 1 02:28:37.419: RIP: sending v2 update to 224.0.0.9 via Loopback2 (192.168.10.97)
*Mar 1 02:28:37.423: RIP: Update contains 7 routes
*Mar 1 02:28:37.423: RIP: Update queued
*Mar 1 02:28:37.427: RIP: Update sent via Loopback2
*Mar 1 02:28:37.443: RIP: ignored v2 packet from 192.168.10.97 (sourced from one of our addresses)
HR#
*Mar 1 02:28:43.615: RIP: sending v2 update to 255.255.255.255 via FastEthernet0/1 (192.168.10.6)
*Mar 1 02:28:43.619: RIP: Update contains 8 routes
*Mar 1 02:28:43.623: RIP: Update queued
*Mar 1 02:28:43.623: RIP: Update sent via FastEthernet0/1
HR#
*Mar 1 02:28:46.163: RIP: sending v2 update to 224.0.0.9 via Loopback3 (192.168.10.113)
*Mar 1 02:28:46.167: RIP: Update contains 7 routes
*Mar 1 02:28:46.171: RIP: Update queued
*Mar 1 02:28:46.171: RIP: Update sent via Loopback3
*Mar 1 02:28:46.179: RIP: ignored v2 packet from 192.168.10.113 (sourced from one of our addresses)
HR#sh ip route

192.168.10.0/24 is variably subnetted, 8 subnets, 2 masks
C 192.168.10.96/28 is directly connected, Loopback2
C 192.168.10.112/28 is directly connected, Loopback3
C 192.168.10.64/28 is directly connected, Loopback0
C 192.168.10.80/28 is directly connected, Loopback1
R 192.168.10.0/30 [120/1] via 192.168.10.5, 00:00:18, FastEthernet0/1
C 192.168.10.4/30 is directly connected, FastEthernet0/1
C 192.168.10.128/28 is directly connected, Loopback4
C 192.168.10.144/28 is directly connected, Loopback5
220.168.10.0/30 is subnetted, 1 subnets
C 220.168.10.0 is directly connected, FastEthernet0/0
HR#show running-config | s rip
ip rip v2-broadcast
ip rip send version 2
router rip
version 2
network 192.168.10.0
no auto-summary

What i'm doing wrong? icon_sad.gif

LE. i'll post the full topology of the lab, mb it's important, but the rest of the routers have onlly the ip's configured, nothing else.

capturewq.jpg

redlq.png

capturewq.jpg
· Share on FacebookShare on Twitter

Comments

  • XtendXtend Member Posts: 27 ■□□□□□□□□□
    HQ#sh running-config
    Building configuration...

    Current configuration : 1179 bytes
    !
    version 12.4
    service timestamps debug datetime msec
    service timestamps log datetime msec
    no service password-encryption
    !
    hostname HQ
    !
    boot-start-marker
    boot-end-marker
    !
    !
    no aaa new-model
    memory-size iomem 5
    ip cef
    !
    !
    !
    no ip domain lookup
    !
    !
    interface Loopback0
    ip address 192.138.10.9 255.255.255.248
    !
    interface Loopback1
    ip address 192.138.10.17 255.255.255.248
    !
    interface Loopback2
    ip address 192.138.10.25 255.255.255.248
    !
    interface Loopback3
    ip address 192.138.10.33 255.255.255.248
    !
    interface Loopback4
    ip address 192.138.10.41 255.255.255.248
    !
    interface Loopback5
    ip address 192.138.10.49 255.255.255.248
    !
    interface FastEthernet0/0
    description TO_CENTRAL
    ip address 192.168.10.2 255.255.255.252
    no ip split-horizon
    duplex auto
    speed auto
    !
    interface FastEthernet0/1
    description TO_OMEGA
    ip address 78.95.53.2 255.255.255.252
    duplex auto
    speed auto
    !
    !
    router rip
    version 2
    network 192.168.10.0
    no auto-summary
    !
    !
    !
    no ip http server
    no ip http secure-server
    !
    !
    !
    control-plane
    !
    !
    line con 0
    exec-timeout 0 0
    logging synchronous
    line aux 0
    line vty 0 4
    login
    !
    !
    end
    · Share on FacebookShare on Twitter
  • XtendXtend Member Posts: 27 ■□□□□□□□□□
    i resolved the CDP problem, the RIP problem still exists:
    HQ#sh ip rip dat
    192.168.10.0/24 auto-summary
    192.168.10.0/30 directly connected, FastEthernet0/0
    192.168.10.4/30
    [1] via 192.168.10.1, 00:00:26, FastEthernet0/0
    192.168.10.64/28
    [2] via 192.168.10.1, 00:00:26, FastEthernet0/0
    192.168.10.80/28
    [2] via 192.168.10.1, 00:00:26, FastEthernet0/0
    192.168.10.96/28
    [2] via 192.168.10.1, 00:00:26, FastEthernet0/0
    192.168.10.112/28
    [2] via 192.168.10.1, 00:00:26, FastEthernet0/0
    192.168.10.128/28
    [2] via 192.168.10.1, 00:00:26, FastEthernet0/0
    192.168.10.144/28
    [2] via 192.168.10.1, 00:00:26, FastEthernet0/0
    Central#sh ip rip dat
    192.168.10.0/24 auto-summary
    192.168.10.0/30 directly connected, FastEthernet0/0
    192.168.10.4/30 directly connected, FastEthernet0/1
    192.168.10.64/28
    [1] via 192.168.10.6, 00:00:08, FastEthernet0/1
    192.168.10.80/28
    [1] via 192.168.10.6, 00:00:08, FastEthernet0/1
    192.168.10.96/28
    [1] via 192.168.10.6, 00:00:08, FastEthernet0/1
    192.168.10.112/28
    [1] via 192.168.10.6, 00:00:08, FastEthernet0/1
    192.168.10.128/28
    [1] via 192.168.10.6, 00:00:08, FastEthernet0/1
    192.168.10.144/28
    [1] via 192.168.10.6, 00:00:08, FastEthernet0/1
    HR#sh ip rip dat
    192.168.10.0/24 auto-summary
    192.168.10.0/30
    [1] via 192.168.10.5, 00:00:22, FastEthernet0/1
    192.168.10.4/30 directly connected, FastEthernet0/1
    192.168.10.64/28 directly connected, Loopback0
    192.168.10.80/28 directly connected, Loopback1
    192.168.10.96/28 directly connected, Loopback2
    192.168.10.112/28 directly connected, Loopback3
    192.168.10.128/28 directly connected, Loopback4
    192.168.10.144/28 directly connected, Loopback5

    why on the HR, i don't see the HQ loopbacks? icon_sad.gif
    · Share on FacebookShare on Twitter
Sign In or Register to comment.