I have a lab setup for both eigrp and ospf. Attached is my network diagram. When using ospf it appears that it is interface aware even if the interface is not part of the network statement. If I try the same thing with EIGRP and shut down my S0/0/0 interface it seems not to care about any other interface beside the network statement that it is in. Is this a default behavior?
> When using ospf it appears that it is interface aware even if the
> interface is not part of the network statement.
I don't understand this statement, can you expand on this including the commands you are entering and the expected behavior ?
> If I try the same thing with EIGRP and shut down my S0/0/0 interface it seems not to care about any other interface
> beside the network statement that it is in. Is this a default behavior?
Same here, please
Attached in this post is my config for OSPF. These configs are from my test enviroment. Which is the same as my diagram with the excecption of my outside interface numbers.
I am injecting a default route with a lower metric from 3845-R1 and then a default route on 3845-R2 with a higher metric to my ASA, so i have only one route in the routing table. When i shut down the s2/1 on 3845-R1 it removes the default route from my ASA from 3845-R1 and loads the default route from 3845-R2 as my default gateway. This is the reaction i expect.
I wanted to implament EIGRP between the two routers and the ASA. When doing the same procedure with EIGRP it does not remove the route even though i have shutdown interface s2/1. Is there anyway i can create the same behaivor with EIGRP? I will upload the EIGRP configs in my next post.
Pretty interesting scenario, could you please paste the sh ip route output from both situations along with sh ip ospf, sh ip eigrp topo and sh ip route.
are you sure eigrp is running on ASA. I know that PIX/ASA doesnt support EIGRP till version 8.0.
This may be the reason ASA is learning routes exactly when ospf is run, while abnormal behaviour with EIGRP.
What i understands from your words is that you want automatic removal of the route, please correct me if i were worng. As i think we can do this with the eigrp you can make a policy in which you can map the another interface of router as soon as the interface is reachable the route will be shown in the routing table, as soon as the interface will down the route is not accessible by the router-map and it will get it out form the routing table.
Why i suggest the route-map because according to routing sequence route-map statements will be checked first.
yeah it works well. I had tested in my lab but the scenarios is different but i need the same you are looking for.
Instead of eigrp i played with ospf
I didnt see any serial interfaces in your design. However , if you want to acheive the same u can do by redistributing static-default route into Eigrp. u could do the same setup which has been done, make sure the (Bandwidth or Delay) from one router is higher than the other one so it will prefer ur desired.
This is acheived when configuring the seed metric (Redistributed route in Eigrp).
My EGP is BGP so i'm hoping that the ISP will include a default route in the eBGP from the routing table, so i would not like to add a static default route on the 3845's I do have the bandwidth set higher on one 3845 and lower on the other 3845.
u can creat a static default-route pointing to null0 interface with higher AD than the BGP, and then you can redistribute it into EIGRP.
The above shouldnt affect your Network
The issue you are facing is due to the summary address ip summary-address eigrp 1 0.0.0.0 0.0.0.0 configured on the interface towards the ASA.
Once you configure this, eigrp installs a null0 route to 0.0.0.0 which never gets removed from the RT.
So as suggested above the best way would be to redistribute BGP in eigrp something like this
access-list 1 permit 0.0.0.0
route-map test permit 10
match ip address 1
router eigrp 1
redistribute bgp 200 route-map test
default-metric 10000 10 255 1 1500