From: Hong Chan (howard.chan34@gmail.com)
Date: Tue Sep 23 2008 - 11:56:32 ART
I have no idea what make this happen.........but I want to have more info
about this lab because I want to know why also
1: debug ip ospf lsa-gen on R3
Just make sure the "no-redistribute" in nssa is working
2: Provide more information between R3 & R1 (and R2 relationship), just for
complete the story
3: if there is no "redistribute route" in nssa, then it should be caused by
the routing on SW4 look back to R3. I guess it maybe caused by the forward
address = 0.0.0.0. Does there any default route in area 0 and area
38?(no-redistribute + no-summary should generate a default route into the
NSSA area, correct me if I am wrong)
2008/9/23 Bogdan Sass <bogdan.sass@catc.ro>
> Peter Wolter wrote:
>
>> Dear Bogdan,
>>
>> Thanks your remind and I agree it's strange also.
>> Can you show the result of
>> show ip ospf database externa 158.1.0.0
>> on SW4? I wanna to know which router redistribute this route to SW4
>> Regards,
>> Howard
>>
>>
> I already replied to this - but just in case the reply didn't make it,
> here it is again:
>
> Of course - the subnet is redistributed by R3 (the router at the other
> end of the two areas), using a "redistribute connected" statement (in the
> original lab, the subnet was redistributed from EIGRP, with the same
> result).
>
> /Rack1SW4#sh ip ospf data ex 158.1.0.0
>
> OSPF Router with ID (150.1.10.10) (Process ID 1)
>
> Type-5 AS External Link States
>
> Routing Bit Set on this LSA
> LS age: 131
> Options: (No TOS-capability, DC)
> LS Type: AS External Link
> Link State ID: 158.1.0.0 (External Network Number )
> Advertising Router: 150.1.3.3
> LS Seq Number: 80000001
> Checksum: 0x5310
> Length: 36
> Network Mask: /24
> Metric Type: 2 (Larger than any link state path)
> TOS: 0
> Metric: 20
> Forward Address: 0.0.0.0
> External Route Tag: 0/
> The route is advertised by 150.1.3.3 (R3), with a forwarding address
> of 0.0.0.0 .
>
> SW4 has only one routing table entry for 150.1.3.3 (as expected, it only
> uses the intra-area route):
> /
> Rack1SW4#sh ip ro 150.1.3.3
> Routing entry for 150.1.3.3/32
> Known via "ospf 1", distance 110, metric 66, type intra area
> Last update from 158.1.1.1 on Vlan110, 00:03:07 ago
> Routing Descriptor Blocks:
> * 158.1.1.1, from 150.1.3.3, 00:03:07 ago, via Vlan110
> Route metric is 66, traffic share count is 1/
>
> However, it still installs two routes for the external address:
>
> /Rack1SW4#sh ip ro 158.1.0.0 255.255.255.0
> Routing entry for 158.1.0.0/24
> Known via "ospf 1", distance 110, metric 20, type extern 2, forward metric
> 65
> Last update from 158.1.1.1 on Vlan110, 00:05:03 ago
> Routing Descriptor Blocks:
> * 158.1.34.1, from 150.1.3.3, 00:05:03 ago, via FastEthernet1/13
> Route metric is 20, traffic share count is 1
> 158.1.1.1, from 150.1.3.3, 00:05:03 ago, via Vlan110
> Route metric is 20, traffic share count is 1
>
> / If you need any additional details/output, please let me know (I
> would also draw a diagram, but I really don't know how I could put this
> topology in ASCII format :) ).
>
> Thank you for your help,
>
>
>
> --
> Bogdan Sass
> CCAI,CCNP,CCSP,JNCIA-ER
> Information Systems Security Professional
> "Curiosity was framed - ignorance killed the cat"
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Sat Oct 04 2008 - 09:26:19 ART