Cisco – EIGRP redistribute static issue

ciscoeigrp

I have an EIGRP issue hopefully someone can help me with. I have a 2821 router with three static routes to VLANs that exist on a switch it's connected to. I want to share these routes with the rest of my network. I thought a "redistribute static" command would do this, but it does not.

I can run a "show ip eigrp topology " on the router and other equipment in the eigrp network and the network information comes up, but I can't ping any of the VLANs from anything but the router. My EIGRP statement also includes "no auto-summary" but that does not help either. Below is the results of the "show ip eigrp topology" command.

router#sh ip eigrp XXX top 10.X.47.0 255.255.255.0
IP-EIGRP (AS XXX): Topology entry for 10.X.47.0/24
State is Passive, Query origin flag is 1, 1 Successor(s), FD is 28160
Routing Descriptor Blocks:
10.X.0.15, from Rstatic, Send flag is 0x0
Composite metric is (28160/0), Route is External
  Vector metric:
    Minimum bandwidth is 100000 Kbit
    Total delay is 100 microseconds
    Reliability is 255/255
    Load is 1/255
    Minimum MTU is 1500
    Hop count is 0
  External data:
    Originating router is 10.X.X.3 (this system)
    AS number of route is 0
    External protocol is Static, external metric is 0
    Administrator tag is 0 (0x00000000)

Best Answer

It sounds like you redistributed static without setting a metric. By default, routes redistributed into EIGRP have a metric of "unreachable".

You either need to specify a metric for the static routes in your "redistribute static" command, or you need to specify a default metric using the "default-metric" command.

Related Solutions

Cisco – Static redistribution into EIGRP as internal failure

You can inject static routes into EIGRP two ways:

The 'network' command
'redistribute static'

You only need one or the other; here you've used both. It seems that the redistribution command takes precedence over the network command so the route is appearing as static routes. Remove 'redistribute static' and the route should appear as internal.

Cisco Failover – How to Provide Failover for Space-Diversity T1

This is a fixed, unchanging network that serves only this dedicated application.

I think you’re finding that this is rarely the norm with networking, even with unchanging networks; hence, why you’re here asking how to automate this. Eventually, another link comes online that requires you to reengineer all of your previous efforts. This is, by definition, what the purpose of a routing protocol is. It’s to make sure you don’t have to use static routes everywhere!

Based on my tests the static routing has no way of employing that second T1.

You can setup a sort of IP SLA that can keep your system running how it is while still allowing for failover in case your Old T1 goes down.

An example of this type of configuration for R4 would be something like this.

R4(config)# ip sla 1
R4(config)# icmp-echo 10.1.1.9 source-interface Serial0/3/0
R4(config)# timeout 1000
R4(config)# threshold 2
R4(config)# frequency 3
R4(config)# ip sla schedule 1 life forever start-time now
R4(config)# track 1 ip sla 1 reachability
R4(config)# ip route 0.0.0.0 0.0.0.0 10.1.1.9 track 1
R4(config)# ip route 0.0.0.0 0.0.0.0 192.168.8.11 100

_{modified version of firewall.cx sample configuration.}

But, as you’re quickly finding out, is the less than ideal way of doing this. Automating this with EIGRP is probably your best bet since you have all Cisco hardware.

But if dynamic routing is the way to go it must be implemented in a way that does not disrupt service.

If you setup EIGRP in conjunction with your static routes. EIGRP neighbor relationships will be built and your routing tables will be populated with routes to the different locations. No outage should really occur, because your routers will have a fully populated routing table with knowledge of how to get to the other subnets.

Just remember, once everything is setup and running smoothly with both EIGRP and static routing, your still going to use your static routes until you remove them. Done properly, you shouldn’t even notice a blip in traffic flow.

Compare your previous configurations with an example EIGRP configuration for R4.

R4(config)#router eigrp 1
R4(config-router)#no auto-summary
R4(config-router)#network 10.1.1.8
R4(config-router)#network 192.168.8.0

It’s usually that simple for such a small network.

Related Topic