Please try this, a network command configured under EIGRP that covers a directly connected static routes (a static route with the outgoing interface only in the ip route command - which is seen as directly connected in the routing table), this will include that subnet for advertisement without the need of redistribute static or connected (advertised as an internal route not as an external route since no redistribution was used) - the outgoing interface needs not be running any routing protocol or included with any network command.
To practically illustrate my suggestion:
R5(config)#router eigrp 1
R5(config-router)#network 192.168.56.5 0.0.0.0
Trying R6 (192.168.1.17, 2038)... Open
R6#sh ip int br
R6#sh ip int brief
Interface IP-Address OK? Method Status Protocol
FastEthernet0/0 192.168.56.6 YES NVRAM up up
FastEthernet0/1 unassigned YES NVRAM administratively down down
Loopback0 18.104.22.168 YES NVRAM up up
Loopback6 22.214.171.124 YES NVRAM up up
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.56.5, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
Configuring from terminal, memory, or network [terminal]?
Enter configuration commands, one per line. End with CNTL/Z.
R6(config)#router eigrp 1
R6(config-router)#network 192.168.56.6 0.0.0.0
*Apr 23 22:53:52.398: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 192.168.56.5 (FastEthernet0/0) is up: new adjacency
R6(config)#ip route 126.96.36.199 255.255.255.0 Loopback6
R6(config)#router eigrp 1
R6(config-router)#network 188.8.131.52 0.0.0.0
[Resuming connection 1 to r5 ... ]
*Apr 23 23:19:18.654: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 192.168.56.6 (GigabitEthernet0/0) is up: new adjacency
R5(config-router)#do sh ip route eigrp
D 184.108.40.206/24 [90/156160] via 192.168.56.6, 00:00:09, GigabitEthernet0/0
You can restribute static into eigrp and then on the interface through which the routing update goes through, there u need to configure a summary address which has the route which is being restributed.
Working through a problem where eigrp won't redistribute some static routes. Here is what I have.
The FD Inaccessible is puzzling because the static route is on that specific switch. Other routes work fine. Those are not included but configured the same as below. No other routing protocols being used.
switch-1#sh ip eigrp top | inc 10.209.
P 10.209.32.0/20, 0 successors, FD is Inaccessible
switch-1# sh ip route 10.209.32.0
Routing entry for 10.209.32.0/20, supernet
Known via "static", distance 1, metric 0
Redistributing via eigrp 706
Routing Descriptor Blocks:
Route metric is 0, traffic share count is 1
router eigrp 106
network 10.214.0.0 0.0.255.255
distribute-list 11 out static
ip route 10.209.32.0 255.255.240.0 10.214.176.2
access-list 11 permit 10.209.32.0 0.0.15.255
You didn't configure a seed metric under the redistribute command, by default routes redistributed into EIGRP have an infinite metric:
eg redistribute static metric 1 1 1 1 1
Thanks, but I have 25 static routes and only 5 of the static routes do not redistribute with its current configuration.
You should always provide a redistribution metric when redistributing static routes. Theoretically, you don't have to, but I've always told folks that you should only leave the metric off if you don't care whether it works or not. The process of deriving the metric automatically is buggy and not to be trusted.
Sent from Cisco Technical Support iPad App
Great tip. Looking at a few examples here is what I came up with:
redistribute static metric 1000000 100 250 100 1500
Should be ok.
Note that the bandwidth is expressed in kilobits, delay as configured on the interface and only bandwidth and delay are taken into consideration by default.
Note the delay is configured in tens of microseconds and displayed in microsecs:
<1-16777215> Throughput delay (tens of microseconds)
R1#sh int fa0/0
FastEthernet0/0 is administratively down, line protocol is down
Hardware is Gt96k FE, address is c400.11bc.0000 (bia c400.11bc.0000)
MTU 1500 bytes, BW 10000 Kbit, DLY 100 usec,
This may or may not work in your case, but see this doc:
When you install a static route to an interface, and configure a network statement using router eigrp, which includes the static route, EIGRP redistributes this route as if it were a directly connected interface.
router eigrp 1
ip route 192.168.1.0 255.255.255.0 Null0 name STATIC-ADVERTISED-AS-EIGRP-INTERNAL
Since a) the route matches a network statement, and b) it routes to a interface (not a next hop IP), it will be internal.
sh eig topology 192.168.1.0 255.255.255.0
EIGRP-IPv4 (AS 5): Topology Default-IP-Routing-Table(0) entry for 192.168.1.0 255.255.255.0
State is Passive, Query origin flag is 1, 1 Successor(s), FD is 51456
Routing Descriptor Blocks:
220.127.116.11 (GigabitEthernet0/1), from 18.104.22.168, Send flag is 0x0
Composite metric is (51456/51200), Route is Internal
I'm hoping you are someone is still watching this thread. I have a question regarding the last tip.
If I create a null0 route for a static route that I already had, then I now have 2 equal cost routes to the target subnet (192.168.1.0 in your example).
Could this cause problems with some traffic getting sent to the null0 interface and other traffic getting sent to the next-hop IP?
I too have the need to advertise static routes as internal, but I'm concerned that load balancing may occur and I may end up dropping some packets to null0 unintentionally as others try to route traffic through the advertising router.
My take on this discussion is that you are correct. It looks to me like the example given by Thiland was created as an easy example of a static pointed to an interface. If you do configure a static route this way it may succeed in getting EIGRP to advertise the route to its neighbors as an Internal route but it will also put a route in the local routing table pointing this prefix to null0 and the result would be some packets get dropped.