Re: Lab 10 Volume 1

Does R5 know how to get to R2?

On Wed, Apr 14, 2010 at 5:03 PM, Di Bias, Steve <steve.dibias_at_uhsinc.com>wrote:

> *sorry email sent prematurely*
>
> Hey everyone,
>
> I'm having some strange issues with reachability with OSPF on Lab 10 that I
> can't figure out. Here is an example of something I'm seeing
>
> R2--s0/1/0.256---Frame Cloud---s0/1/0--R5-fa0/0--Ethernet-fa0/0--R7
>
> R2 has its s0/1/0.256 in Area 0
> R5 has its s0/1/0 in Area 0
> R5 has its fa0/0 in Area 567
> R7 has its fa0/0 in Area 567
>
> R5 is an ABR with interfaces in both areas and R7 has an interface in 567.
> So
> far no rules have been broken (area 567 touches area 0 on R5) and
> inter-area
> communication should be working between the three routers, but it doesn't.
> As
> a test on R7 I just added the loopback interface to the OSPF process in
> area
> 567
>
> R7(config)#router os 1
> R7(config-router)#net 200.0.0.7 0.0.0.0 area 567
>
> On R5 I verified the route and I can ping the loopback on R7
>
> R5#sh ip ro 200.0.0.7
> Routing entry for 200.0.0.7/32
> Known via "ospf 1", distance 110, metric 11, type intra area
> Last update from 150.100.220.7 on FastEthernet0/0, 00:03:51 ago
> Routing Descriptor Blocks:
> * 150.100.220.7, from 200.0.0.7, 00:03:51 ago, via FastEthernet0/0
> Route metric is 11, traffic share count is 1
>
> R5#ping 200.0.0.7
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 200.0.0.7, timeout is 2 seconds:
> !!!!!
>
> So we are good from R5 to R7 but not to R2 who has the route but can't ping
>
> R2#sh ip route 200.0.0.7
> Routing entry for 200.0.0.7/32
> Known via "ospf 1", distance 110, metric 1573, type inter area
> Last update from 150.100.100.5 on Serial0/1/0.256, 00:00:14 ago
> Routing Descriptor Blocks:
> * 150.100.100.5, from 200.0.0.5, 00:00:14 ago, via Serial0/1/0.256
> Route metric is 1573, traffic share count is 1
>
>
> R2#ping 200.0.0.7
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 200.0.0.7, timeout is 2 seconds:
> .....
> If I run a debug on R2 and then run a ping to 200.0.0.7 it shows routed vis
> FIB like this
>
> R2(config)#access-list 101 permit icmp any any
> R2(config)#do deb ip pack 101 de
> R2(config)#do ping 200.0.0.7
> Sending 5, 100-byte ICMP Echos to 200.0.0.7, timeout is 2 seconds:
>
> *May 13 00:29:37.057: IP: tableid=0, s=150.100.100.2 (local), d=200.0.0.7
> (Serial0/0.256), routed via FIB
>
> So it R2 knows how to get to R7 the issue must be that R7 doesn't know how
> to
> get to back to R2
>
> R7#sh ip ro 200.0.0.2
> % Subnet not in table
>
> It seems like Area 0 routes aren't coming over to Area 567, any ideas?
>
>
>
>
>
>
>
>
> UHS Confidentiality Notice: This e-mail message, including any
> attachments,
> is for the sole use of the intended recipient (s) and may contain
> confidential
> and privileged information. Any unauthorized review, use, disclosure or
> distribution of this information is prohibited. If this was sent to you in
> error, please notify the sender by reply e-mail and destroy all copies of
> the
> original message.
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>

-- 
Bryan Bartik
CCIE #23707 (R&S, SP), CCNP
Sr. Support Engineer - IPexpert, Inc.
URL: http://www.IPexpert.com
Blogs and organic groups at http://www.ccie.net