Thanks Jon, I appreciate the

sgalarza · ‎06-01-2017

Because of administrative distance will a static default route replace an external EIGRP advertised route? We are getting an advertised external EIGRP route coming in from our ISP's edge router located in our building, what I'm asking is, can we enter a static route as a default route and it take precedent over the external route being advertised, or is this a situation where we need to get our service provider involved? The route advertised externally is being advertised to 12 different sites all connected by an ASE circuit pointing traffic to our main site, the router at our main site has a manually entered static route that points all traffic out our sonic wall and to any external network.

Any insight would be greatly appreciated.

Thanks,

Steve

cofee · ‎06-01-2017

Static route will replace any route that is learned by a dynamic routing protocol as long as default administrative values are not manipulated and destination prefix/address is matched.

So yes static route will replace eigrp learned route in local RIB (routing information base) as long as destination address/prefix is matched.

For example:

eigrp route - 1.2.3.0/24

static route - 1.2.3.0/24

Only static route will be installed in local RIB.

sgalarza · ‎06-02-2017

Cofee,

Thanks for the input, I was just curious if there would be any issues if this external advertised route gets replaced with a static route. The thing is the external route being advertised is an internal path that we did not program into our gear. It is being advertised by our service provider, by their router within our premises.

Here is output from one of our routers getting that external route:

Gateway of last resort is 10.101.2.1 to network 0.0.0.0

10.0.0.0/24 is subnetted, 33 subnets
D 10.0.10.0 [90/3072] via 10.101.2.10, 14:46:03, Vlan102
D 10.1.10.0 [90/3072] via 10.101.2.10, 14:46:03, Vlan102
D 10.3.10.0 [90/3072] via 10.101.2.10, 14:46:03, Vlan102
D 10.3.13.0 [90/3072] via 10.101.2.13, 14:46:03, Vlan102
D 10.1.15.0 [90/3072] via 10.101.2.15, 14:46:03, Vlan102
D 10.0.14.0 [90/3072] via 10.101.2.14, 14:46:03, Vlan102
D 10.1.14.0 [90/3072] via 10.101.2.14, 14:46:03, Vlan102
D 10.0.15.0 [90/3072] via 10.101.2.15, 14:46:03, Vlan102
D 10.1.13.0 [90/3072] via 10.101.2.13, 14:46:03, Vlan102
D 10.3.14.0 [90/3072] via 10.101.2.14, 14:46:03, Vlan102
D 10.0.13.0 [90/3072] via 10.101.2.13, 14:46:03, Vlan102
D 10.1.3.0 [90/3072] via 10.101.2.3, 14:46:03, Vlan102
D 10.0.2.0 [90/3072] via 10.101.2.2, 14:46:03, Vlan102
D 10.1.2.0 [90/3072] via 10.101.2.2, 14:46:03, Vlan102
D 10.0.3.0 [90/3072] via 10.101.2.3, 14:46:03, Vlan102
D 10.1.1.0 [90/3072] via 10.101.2.1, 14:44:07, Vlan102
D 10.0.1.0 [90/3072] via 10.101.2.1, 14:44:05, Vlan102
D 10.3.5.0 [90/3072] via 10.101.2.5, 14:46:03, Vlan102
D 10.0.6.0 [90/3072] via 10.101.2.6, 14:46:03, Vlan102
D 10.3.4.0 [90/3072] via 10.101.2.4, 14:46:03, Vlan102
D 10.1.6.0 [90/3072] via 10.101.2.6, 14:46:03, Vlan102
D 10.1.5.0 [90/3072] via 10.101.2.5, 14:46:03, Vlan102
D 10.0.4.0 [90/3072] via 10.101.2.4, 14:46:03, Vlan102
D 10.3.6.0 [90/3072] via 10.101.2.6, 14:46:03, Vlan102
D 10.1.4.0 [90/3072] via 10.101.2.4, 14:46:03, Vlan102
D 10.0.5.0 [90/3072] via 10.101.2.5, 14:46:03, Vlan102
C 10.1.17.0 is directly connected, Vlan200
C 10.0.17.0 is directly connected, Vlan1
D 10.0.50.0 [90/3072] via 10.101.2.18, 14:46:03, Vlan102
D 10.1.50.0 [90/3072] via 10.101.2.18, 14:46:03, Vlan102
D 10.3.50.0 [90/3072] via 10.101.2.18, 14:46:03, Vlan102
C 10.10.99.0 is directly connected, Vlan99
C 10.101.2.0 is directly connected, Vlan102
D*EX 0.0.0.0/0 [170/3072] via 10.101.2.1, 14:44:05, Vlan102

And then here is the output from the router that everything gets pointed to:

Gateway of last resort is 10.0.1.2 to network 0.0.0.0

S* 0.0.0.0/0 [1/0] via 10.0.1.2
10.0.0.0/8 is variably subnetted, 36 subnets, 2 masks
C 10.0.1.0/24 is directly connected, Vlan1
L 10.0.1.1/32 is directly connected, Vlan1
D 10.0.2.0/24 [90/3072] via 10.101.2.2, 14:39:55, Vlan102
D 10.0.3.0/24 [90/3072] via 10.101.2.3, 14:39:55, Vlan102
D 10.0.4.0/24 [90/3072] via 10.101.2.4, 14:39:55, Vlan102
D 10.0.5.0/24 [90/3072] via 10.101.2.5, 14:39:55, Vlan102
D 10.0.6.0/24 [90/3072] via 10.101.2.6, 14:39:55, Vlan102
D 10.0.10.0/24 [90/3072] via 10.101.2.10, 14:39:55, Vlan102
D 10.0.13.0/24 [90/3072] via 10.101.2.13, 14:39:55, Vlan102
D 10.0.14.0/24 [90/3072] via 10.101.2.14, 14:39:55, Vlan102
D 10.0.15.0/24 [90/3072] via 10.101.2.15, 14:39:55, Vlan102
D 10.0.17.0/24 [90/3072] via 10.101.2.17, 14:39:55, Vlan102
D 10.0.50.0/24 [90/3072] via 10.101.2.18, 14:39:55, Vlan102
C 10.1.1.0/24 is directly connected, Vlan200
L 10.1.1.1/32 is directly connected, Vlan200
D 10.1.2.0/24 [90/3072] via 10.101.2.2, 14:39:55, Vlan102
D 10.1.3.0/24 [90/3072] via 10.101.2.3, 14:39:55, Vlan102
D 10.1.4.0/24 [90/3072] via 10.101.2.4, 14:39:55, Vlan102
D 10.1.5.0/24 [90/3072] via 10.101.2.5, 14:39:55, Vlan102
D 10.1.6.0/24 [90/3072] via 10.101.2.6, 14:39:55, Vlan102
D 10.1.10.0/24 [90/3072] via 10.101.2.10, 14:39:55, Vlan102
D 10.1.13.0/24 [90/3072] via 10.101.2.13, 14:39:55, Vlan102
D 10.1.14.0/24 [90/3072] via 10.101.2.14, 14:39:55, Vlan102
D 10.1.15.0/24 [90/3072] via 10.101.2.15, 14:39:55, Vlan102
D 10.1.17.0/24 [90/3072] via 10.101.2.17, 14:39:55, Vlan102
D 10.1.50.0/24 [90/3072] via 10.101.2.18, 14:39:55, Vlan102
D 10.3.4.0/24 [90/3072] via 10.101.2.4, 14:39:55, Vlan102
D 10.3.5.0/24 [90/3072] via 10.101.2.5, 14:39:55, Vlan102
D 10.3.6.0/24 [90/3072] via 10.101.2.6, 14:39:55, Vlan102
D 10.3.10.0/24 [90/3072] via 10.101.2.10, 14:39:55, Vlan102
D 10.3.13.0/24 [90/3072] via 10.101.2.13, 14:39:55, Vlan102
D 10.3.14.0/24 [90/3072] via 10.101.2.14, 14:39:55, Vlan102
D 10.3.50.0/24 [90/3072] via 10.101.2.18, 14:39:55, Vlan102
D 10.10.99.0/24 [90/3072] via 10.101.2.17, 14:39:55, Vlan102
C 10.101.2.0/24 is directly connected, Vlan102
L 10.101.2.1/32 is directly connected, Vlan102

Just to clarify, the output from the first router shows the external EIGRP route, we did not add that route ourselves. The 10.101.2.1 address in an internal route.

Thanks,

Jon Marshall · ‎06-02-2017

The first router's default gateway points to the second router.

Are you sure on the second router where you have the static route you do not have a "redistribute static" under the EIGRP process ?

Jon

sgalarza · ‎06-02-2017

Jon, we do have a redistribute static statement under our EIGRP. The second router then points to our SonicWall which is the 10.0.1.2 address. We have about 12 sites that are getting that External route, all pointing to our main router 10.101.2.1 then that router sends everything to the SonicWall.

Jon Marshall · ‎06-02-2017

So do you want traffic to go somewhere else ?

Jon

sgalarza · ‎06-02-2017

Eventually we do, I'm just wondering what happens to that external route? If we put a new static routing statement pointing to a new IP address. The external route will stay in the routing table correct? It would get overwritten if it was the same IP correct, because of AD?

Jon Marshall · ‎06-02-2017

If the static route is for the same prefix then it would replace the EIGRP route ie.it is the prefix that matters not the next hop IP address.

Note also that would mean that the route would not be passed to any EIGRP peers unless of course you redistributed under the EIGRP process.

Jon

sgalarza · ‎06-02-2017

Thanks Jon, I appreciate the input. This helps.

Kind Regards,

Steve

External EIGRP