From a stub area, I can't ping a redistributed EIGRP AS

[news2010a]

Imagine I have the following:

RouterA, s0=193.10.1.1/24

EIGRP AS#100

connected to

RouterB, s0/0=193.10.1.2/24

RouterB, s0/1=150.1.1.2/24

Connected to

RouterC, s0=150.1.1.3/24

OSPF process ID 300

Area1 configured as stub

File showing Configuration and show ip route output is attached.

Then my goal is to ping RouterC, which is an external AS from RouterB, the stub area. I know that since RouterB is in 'area 1 stub', Stub areas will not receive external LSA's.

But then suppose my Area1 is a branch office, but I still need to be able to reach the network on the RouterA-EIGRP-AS; I created a static, default route on "RouterB"-Area 1 Stub to reach RouterC-EIGRP-AS100, but I am still unable to reach RouterC-EIGRP-AS100.

What am I doing wrong ? From a stub area, I want to get out and reach the network on the RouterC external AS.

[sanjay.ccie]

Hi,

What I notice from your output is that router C does not have a route back to router B very obviously the echo reply cannot reach Router B.

[sanjay.ccie · Accepted solution]

Also the route to router C should have been via Ospf External route in Router B you can see its been added statically.so its a routing issue.

[fmasson]

I can't see the Loopback Interface of router C within the EIGRP network statement?

[fmasson · Accepted solution]

Hi,

pinging from RouterB to 193.10.1.1 (Serial0/0 of RouterC) is using address of Serial0/0 of RouterB (150.1.1.3).

I didn't see that RouterC knows Serial0/0 address (150.1.1.3) of RouterB.

I think you should propagate Loopback of RouterC (3.3.3.3) to EIGP100, also propagate Loopback of RouterB (2.2.2.2) to OSPF300 and last redistribute OSPF64 into EIGRP100 on RouterB.

Then you should reach Loopback of RouterC (3.3.3.3) using extended ping from RouterB (2.2.2.2) ...if i'm right...

regards

Frank