Cisco router using RIP however no output from show ip route ip

JockVSJockJockVSJock Member Posts: 1,118
in CCNA & CCENT
Greetings, I built a basic topology (see attached picture) for three routers (c7200) in GNS3. For the IOS I'm using 12.4(4)T1.

I'm using RIPv2 to build routing tables for all routers, I can run the following commands ok from the East and West Router
east#show ip protocols
Routing Protocol is "rip"
  Outgoing update filter list for all interfaces is not set
  Incoming update filter list for all interfaces is not set
  Sending updates every 30 seconds, next due in 7 seconds
  Invalid after 180 seconds, hold down 180, flushed after 240
  Redistributing: rip
  Default version control: send version 2, receive version 2
    Interface             Send  Recv  Triggered RIP  Key-chain
    Serial1/0             2     2
  Automatic network summarization is not in effect
  Maximum path: 4
  Routing for Networks:
    10.0.0.0
  Routing Information Sources:
    Gateway         Distance      Last Update
    10.0.1.1             120      00:00:16
  Distance: (default is 120)




east#show ip route rip
     10.0.0.0/24 is subnetted, 2 subnets
R       10.0.0.0 [120/1] via 10.0.1.1, 00:00:12, Serial1/0

However from my Central Router, I am unable to get any output when I run the same command that runs ok on the other two routers. Even though they are all using the same IOS.
show ip route rip

I don't understand why?
***Freedom of Speech, Just Watch What You Say*** Example, Beware of CompTIA Certs (Deleted From Google Cached)

"Its easier to deceive the masses then to convince the masses that they have been deceived."
-unknown
· Share on FacebookShare on Twitter

Comments

  • JoshyJJoshyJ Member Posts: 32 ■■□□□□□□□□
    What is the IP address of the interfaces? also do all three routers have ripv2 enabled? Need more information please.
    · Share on FacebookShare on Twitter
  • dpjackal89dpjackal89 Member Posts: 81 ■■□□□□□□□□
    You can't see RIP because it doesn't need any RIP routes. The East and West routers are directly connected. Directly connected routers always beat RIP routes (administrative distance). Add a 4th router into the mix and you will start seeing RIP routes.
    · Share on FacebookShare on Twitter
  • JoshyJJoshyJ Member Posts: 32 ■■□□□□□□□□
    dpjackal89 wrote: »
    You can't see RIP because it doesn't need any RIP routes. The East and West routers are directly connected. Directly connected routers always beat RIP routes (administrative distance). Add a 4th router into the mix and you will start seeing RIP routes.

    Very true I didn't even think about that.
    · Share on FacebookShare on Twitter
  • JockVSJockJockVSJock Member Posts: 1,118
    dpjackal89 wrote: »
    The East and West routers are directly connected.

    The East and West routers are connected via Central Router.
    ***Freedom of Speech, Just Watch What You Say*** Example, Beware of CompTIA Certs (Deleted From Google Cached)

    "Its easier to deceive the masses then to convince the masses that they have been deceived."
    -unknown
    · Share on FacebookShare on Twitter
  • dpjackal89dpjackal89 Member Posts: 81 ■■□□□□□□□□
    JockVSJock wrote: »
    The East and West routers are connected via Central Router.

    Yes. They are.
    · Share on FacebookShare on Twitter
  • chXchX Member Posts: 100 ■■■□□□□□□□
    Can you post the running-configs for each router?
    2019 Goals:
    [ ] Recertify CCNA
    · Share on FacebookShare on Twitter
  • canojcanoj Member Posts: 33 ■■□□□□□□□□
    JockVSJock wrote: »
    The East and West routers are connected via Central Router.

    The central Router will not display the Rip routes for East and West because it is directly connected to East and West.

    Do a "show ip route" command and you will see East and West in the routing table with a "c" for directly connected.
    · Share on FacebookShare on Twitter
  • PCHoldmannPCHoldmann Member Posts: 450
    You could also put loopbacks on the East and West routers, and advertise them into RIP. You should see those routes in RIP, and the actual interfaces as connected routes.
    There's no place like ^$
    Visit me at Route, Switch, Blog
    · Share on FacebookShare on Twitter
Sign In or Register to comment.