giuslar wrote:
Hello Ryan,
>> What is the easiest way to fix this?
on RB use
ip route 0.0.0.0 0.0.0.0  200
instead of
ip route 0.0.0.0 0.0.0.0  track 100
in this way also RB will use the received EIGRP default route you need to make the static a floating static route or it will be preferred over EIGRP default route.
Hope to help
Giuseppe

Guiseppe

Agreed, but then B would also use A to send traffic to the internet rather than use it's local ISP connection and i'm not sure that is what Ryan wants.

Jon

R.A can use the its ISP as primary and R.B and R.C can use as secondary.

R.C can use R.B's ISP as it's closer geographically.

If R.C's ISP is down I want R.C and R.B to use R.A's EIGRP default route.

What appears is that I need a summary-address to advertise the default route to R.C. R.B will need a track on the default route so if ISP on R.B fails it will remove the route and then R.B and R.C can then use R.A's advertised default route.

Is there something else that would make this eaiser? Is summary-address the right way to go?

Ryan

You could use a summary-address on B to C if you simply want to get C's traffic to B. Then as you say track the default-route on B and if it is removed then B will install A's route and both B & C will then use A.

Jon

jon.marshall wrote:

The problem you have is that router B will always use the locally configured default-route rather than the one received from router A and hence that is why it does not advertise router A default-route to router C.

Even though router B is not set to advertise static routes EIGRP on that router says drop the default route so router C can't see that advertisement? Seems odd that it drops it.

I wonder if it does the same thing for static route (non-default route) entries? Thus if router B had an entry for a ip route it could potential block router C from seeing it.

ryan.s.15 wrote:
jon.marshall wrote:

The problem you have is that router B will always use the locally configured default-route rather than the one received from router A and hence that is why it does not advertise router A default-route to router C.
 Even though router B is not set to advertise static routes EIGRP on that router says drop the default route so router C can't see that advertisement? Seems odd that it drops it.
I wonder if it does the same thing for static route (non-default route) entries? Thus if router B had an entry for a ip route it could potential block router C from seeing it.

Ryan

Router B will not use router A's default route because it has it's own. But you are not redistributing B's static route into EIGRP. So B receives the default-route from A but doesn't put it into the routing table because it has it's own default-route which has a much better AD. But this local default-route is not being redistributed into EIGRP so C will never get an advertisement for this route from B.

So B is not dropping A's advertisement, it simply doesn't use it because it has a better one.

Jon

Can you point me to a document possibly that states something to the effect:

"EIGRP default routes are not redistributed down stream if an upstream router has a static default route"

I understand that the default route in B will not redistribute in EIGRP, which is what I want. I'm trying to find the reasoning that there is a default route being distributed via EIGRP from A but it gets dropped at B, because C never sees it.

I appriciate all your help.