We do not want the supernet to redistribute via static.. we dont want it to be an External Route.. We want the supernet as an internal route, but the FD is inaccessible..

Raj

Just because the Feasible Distance reports as inaccessible, this does not mean the subnet is not reachable or invalid.

Do you have your CCIE in Routing & Switching?

what has that got to do with your answer ?? are you a quad CCIE ??

Raj

Nothing what so ever! No i am not, I am working towards it. The reason I was asking is i was going to ask for some study advice for the R&S ccie, and you are the first CCIE rated person I have seen on the forums.

Which is why I was asking if your ccie is in R&S??

Hi Sachin,

If the supernet is a static route, how will you get into EIGRP without redistributing it, in which case it will become an external route. I didnt quite get that part.

Well if the FD is inaccessible, it means the Router is not using the EIGRP learnt  route for 192.168.96.0/19 in the routing table.  Could you also do show ip route for 192.168.96.0/19

http://supportwiki.cisco.com/ViewWiki/index.php/EIGRP_route_is_not_installed_in_the_routing_table

HTH

Lejoe

Raja,

I agree with Lejoe.. If the the supernet is a static route and is getting redistributed, EIGRP will always learn it as an external route.

The command router eigrp 1000 network 192.168.96.0 0.0.31.255 does not actually advertise the subnet to the neighbors . It merely starts the EIGRP process on that segment

However if you are just redistributing the static routes into eigrp , then the topology table should show it as Rstatic and not inaccessible which means the router is using other protocol to route the traffic to that subnet. A network topology and sh ip route from the routers woudl help.

If you want the route to be advertised as a eigrp internal route, then you can define a /32 loopback intrface from the ip subnet 192.168.96.x network and summarize it to /19 out the interface to the neighbors

int loopback 1000 

ip add 192.168.96.1 255.255.255.255

interface [ID]  

ip summary-address eigrp 1000 192.168.96.0 255.255.224.0

 Narayan

Hello Sachin,

I agree with Narayan the only way to build an internal EIGRP route is to have a component subnet advertised with a network command in the EIGRP process

int loop1

ip add 192.168.96.1 255.255.255.255

router eigrp 1000

network 192.169.96.0 0.0.0.0

on the interfaces from distribution to access

ip summary-address eigrp 1000 192.168.96.0 255.255.224.0

Actually I used network command in EIGRP for a static route to advertise the default network and it worked (I was surprised of this).

Verify if the static route you are referring to is some form of floating static route and the router is using other routing source to route to that prefix.

Hope to help

Giuseppe

Sachin,

Are you setting a default metric for the static route when you redistribute it into EIGRP?  If you do not, the EIGRP will assign it the infinite metric.

Static route redistribution into eigrp does not mandate a metric to be defined.

Narayan

Narayan,

I should have preface what I said.  Normally I would agree with you, but I have seen some problems in the past with redistributing static routes without setting a default metric.  I also agree we really need to see a show ip route to see if the correct route is installed in the routing table.

Hi Narayan,

I guess I missed something regarding the statement

If the the supernet is a static route and is getting redistributed, EIGRP will always learn it as an external route.

If we're using the network command instead of redistribute static, there's a difference.If the static route is pointed to an interface and the network command is used for the specifying the static route, EIGRP redistributes the route as if it were directly connected route, i.e to it's neigbours that route will appear with as D as opposed to D EX.

http://www.cisco.com/en/US/tech/tk365/technologies_white_paper09186a0080094cb7.shtml#statictointerface

But if the FD is inancessible for a route in EIGRP, it means the EIGRP route is not the one selected in the routing table. A show ip route might help to further troubleshoot the issue

Lejoe