I am trying to migrate an EIGRP network to OSPF. I thought I would do this by enabling OSPF across the network with admin dist of 180, then drop the AD on the Area 0 routers to get OSPF working in the core, then do the same in the leaf areas. What I found was that when I droped the admin dist of OSPF to 80 on the core/area 0, OSPF was also active for all routes on the leaf areas, which was a surprise. I thought OSPF and EIGRP were ships in the night routing, so changing admin dist locally on one router, shouldn't affect the EIGRP routing on another router.
1. EIGRP is running across all routers (with no redistribution)
2. Configure OSPF on all routers with areas as shown in diagram, with admin dist 180.
3. Check to confirm that all routes are still in EIGRP.
4. Set admin distance to 80 for OSPF on R2,R3.
At this stage I expect the route connected to R4 (10.1.1.0) to be in OSPF on R2,R3, but in EIGRP on R1. What I find is that R1 has the route in OSPF.
Debugging shows that when I set the R2,R3 OSPF distance to 80, R1 says there has been a route change, it does the EIGRP DUAL query for the successor, but R2 says I don't have an EIGRP route in my main routing table for 10.1.1.0 (the route is in OSPF), so R2 says I provide a successor, so R1 sets the route to an infinity metric and moves it to the DUAL passive state.
If this was true ships in the night routing, R2 would still have an EIGRP route in its local EIGRP routing table (not the main routing table) to reply to R1 with, it is just that this route is in the EIGRP table, but not in the main routing table. However R2 seems to check do I have a route, and is my EIGRP route in the main routing table, and if it is not in the main routing table, then don't respond to any EIGRP queries.
Has anyone seen this behavior before?
Is there any hidden command to make EIGRP and OSPF behave like ships in the night?
When you change the distance for ospf at R2, the routing table gets updated with the OSPF route
Now if you observe the eigrp topology closely, you should see that the FD would be shown as inaccessible at R2 (meaning that the route in the routing table is due to another routing protocol with a better admin distance). Since the FD is inaccessible at R2, R1 will not install the EIGRP route
You need to remember that EIGRP is a distance-vector protocol, if it's not installing a route in the routing table, it won't advertise the route, and it keeps the route in the local topo table with an infinite distance. There's a bog out to have a nerd knob make it so EIGRP can advertise routes which are in the local table, and in the local routing table, but that EIGRP isn't installing the route.
I had always been told that EIGRP and OSPF were ships in the night routing, but it looks like that is not the case, since EIGRP makes decisions based on whether its route is the route in the main routing table or not, creating a dependency between EIGRP and OSPF.
Russ, can you please tell me the command to activate the nerd knob to disable this behaviour?
There's no current command to activate it. :-( If you shoot me an email, I'll see if there's a way for you to track the state of the request, etc. I'm not certain there is--I might have to do some work to make it "trackable," since I think it's in a state right now where it's not visible to the outside world.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...