Route Redistribution with OSPF / RIP

Comments

• tomtom1 Member Posts: 375

  May 2015

  Is the metric for the routes redistributed into RIP not too high (remember the max hop count of 15, that also counts for redistributed routes. Presumeably, the reason you cannot ping is because the return route is missing.

  0 · Share on FacebookShare on Twitter
• tecnodog7 Member Posts: 129

  May 2015

  Exactly, and when i do a traceroute it stops at R1. Also the hop count isn't too far, only 3 hops.
  This my ASBR/ABR config
  router ospf 1
  router-id 1.1.1.1
  log-adjacency-changes
  redistribute connected subnets
  redistribute rip subnets
  network 1.1.1.1 0.0.0.0 area 1
  network 172.12.123.0 0.0.0.255 area 0
  neighbor 172.12.123.2
  neighbor 172.12.123.3
  !
  router rip
  redistribute connected metric 1
  redistribute ospf 1 metric 1
  network 15.0.0.0

  0 · Share on FacebookShare on Twitter
• OfWolfAndMan Member Posts: 923 ■■■■□□□□□□

  May 2015

  Can you advertise R4's loopback into OSPF please? Also, please display router 2 and 3's show run ospf commands.
  
  If all else fails, you may get by with using the #ip ospf network point-to-multipoint command.

  :study:Reading: Lab Books, Ansible Documentation, Python Cookbook 2018 Goals: More Ansible/Python work for Automation, IPSpace Automation Course [X], Build Jenkins Framework for Network Automation []

  0 · Share on FacebookShare on Twitter
• tecnodog7 Member Posts: 129

  May 2015

  OfWolfAndMan wrote: »

  Can you advertise R4's loopback into OSPF please? Also, please display router 2 and 3's show run ospf commands.
  
  If all else fails, you may get by with using the #ip ospf network point-to-multipoint command.

  
  Originally I planned to put R4's loopback into a different area but for now i'll put it in the same area. My network topology changed a bit so here is the new one. Made R4 a stub router and R6 a totally stub router.
  
  R2
  router ospf 1
  router-id 2.2.2.2
  log-adjacency-changes
  area 35 stub no-summary
  network 2.2.2.2 0.0.0.0 area 2
  network 172.12.123.0 0.0.0.255 area 0
  network 172.35.35.0 0.0.0.255 area 35
  
  R3
  router ospf 1
  router-id 3.3.3.3
  log-adjacency-changes
  area 34 stub
  network 3.3.3.3 0.0.0.0 area 3
  network 172.12.123.0 0.0.0.255 area 0
  network 172.34.34.0 0.0.0.255 area 34
  
  I have added the R4;s loopback and this is the routing table from R1's perspective
  1.0.0.0/32 is subnetted, 1 subnets
  C 1.1.1.1 is directly connected, Loopback1
  2.0.0.0/32 is subnetted, 1 subnets
  O IA 2.2.2.2 [110/65] via 172.12.123.2, 01:32:03, Serial2/0
  3.0.0.0/32 is subnetted, 1 subnets
  O IA 3.3.3.3 [110/65] via 172.12.123.3, 01:32:03, Serial2/0
  4.0.0.0/32 is subnetted, 1 subnets
  O IA 4.4.4.4 [110/66] via 172.12.123.3, 00:00:41, Serial2/0
  R 5.0.0.0/8 [120/1] via 15.1.1.5, 00:00:22, FastEthernet0/0
  R 6.0.0.0/8 [120/1] via 15.1.1.5, 00:00:22, FastEthernet0/0
  172.12.0.0/24 is subnetted, 1 subnets
  C 172.12.123.0 is directly connected, Serial2/0
  172.34.0.0/24 is subnetted, 1 subnets
  O IA 172.34.34.0 [110/65] via 172.12.123.3, 01:32:04, Serial2/0
  172.35.0.0/24 is subnetted, 1 subnets
  O IA 172.35.35.0 [110/65] via 172.12.123.2, 00:10:13, Serial2/0
  R 7.0.0.0/8 [120/1] via 15.1.1.5, 00:00:24, FastEthernet0/0
  C 15.0.0.0/8 is directly connected, FastEthernet0/0

  Capture.jpg 15.8K

  0 · Share on FacebookShare on Twitter
• _Gonzalo_ Member Posts: 113

  May 2015

  Well, I´d do a troubleshooting and check the results, hehehe
  
  I understood that you cannot ping from R4 to R5. First thing you need to do is find the fault. You should be making sure that:
  
  R4 can ping R3, to make sure that there is no problem with the switch and interfaces (you already did with the tracer)
  R4 can ping R1, to check the frame relay and OSPF (also done with tracer)
  
  So, by the troubleshooting you did, it looks like the fault is between R1 and R5. I wouldn´t be surprised if there is no connectivity between them. As RIP routes are being redistributed into OSPF, I´d also try first R5.
  
  Also, if the interface between R1 and R5 was down, no RIP routes would be available, so I would guess that you have a protocol down issue on it.

  0 · Share on FacebookShare on Twitter
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• tecnodog7 Member Posts: 129

  May 2015

  _Gonzalo_ wrote: »

  Well, I´d do a troubleshooting and check the results, hehehe
  
  I understood that you cannot ping from R4 to R5. First thing you need to do is find the fault. You should be making sure that:
  
  R4 can ping R3, to make sure that there is no problem with the switch and interfaces (you already did with the tracer)
  R4 can ping R1, to check the frame relay and OSPF (also done with tracer)
  
  So, by the troubleshooting you did, it looks like the fault is between R1 and R5. I wouldn´t be surprised if there is no connectivity between them. As RIP routes are being redistributed into OSPF, I´d also try first R5.
  
  Also, if the interface between R1 and R5 was down, no RIP routes would be available, so I would guess that you have a protocol down issue on it.

  
  So the problem is with packets coming to R1 and then stopping. When i ping from R4 interface to R1 on the RIP network it's working.
  Funny thing from R1 to R5 connectivity is there. R1 is able to see all the routes from R5 (three loopback interface created there) and it's able to ping it no issue.
  
  The issue is traffic from outside isn't able to ping R5 interface and that makes sense since R5 doesn't see the OSPF network routes

  0 · Share on FacebookShare on Twitter
• siggnation Member Posts: 182

  May 2015

  Hey tecno,
  
  As we discussed, everything looked peachy with all router configs until we delved into R1's configuration and saw that for the 15.0.0.0/8 network you wanted to ping from R4, R1 was running RIP v1 and not v2; so we corrected the auto-summary behavior.
  
  #show ip rip database indicated that particular subnet was under auto-summary and #show run confirmed no version 2 command.
  
  All in all, that was a nice lab. Keep it up!

  Currently Reading:
  
  CCIE Routing and Switching Written Exam v. 5.1
  CCIE Routing and Switching 5.0 OCG, Vol. I
  Cisco Lan Switching

  0 · Share on FacebookShare on Twitter
• tecnodog7 Member Posts: 129

  May 2015

  siggnation wrote: »

  Hey tecno,
  
  As we discussed, everything looked peachy with all router configs until we delved into R1's configuration and saw that for the 15.0.0.0/8 network you wanted to ping from R4, R1 was running RIP v1 and not v2; so we corrected the auto-summary behavior.
  
  #show ip rip database indicated that particular subnet was under auto-summary and #show run confirmed no version 2 command.
  
  All in all, that was a nice lab. Keep it up!

  
  Damn, feel like a dummy.
  
  Thanks Sigg

  0 · Share on FacebookShare on Twitter
• networker050184 Mod Posts: 11,962 Mod

  May 2015

  Trust me you're not the first person to stare at a lab so long you start missing the simple stuff. Sometimes a fresh perspective is all that's needed.

  An expert is a man who has made all the mistakes which can be made.

  0 · Share on FacebookShare on Twitter
• tecnodog7 Member Posts: 129

  May 2015

  networker050184 wrote: »

  Trust me you're not the first person to stare at a lab so long you start missing the simple stuff. Sometimes a fresh perspective is all that's needed.

  
  Haha Thanks networker, I am trying to incorporate as many moving parts as possible and make this as real as possible that the simple stuff just get's over looked.
  
  The thing that annoys me is that I should have known that RIP v1 is a classfull routing protocol so of course it wouldn't be able to redistribute routes which are classless, anyway it's good it was done in lab so i'm not sitting in production banging my head on the cubicle
  
  Awesome think about being part of the community is that there are people here to help you out when you get stuck!

  0 · Share on FacebookShare on Twitter