From: Petr Lapukhov (petrsoft@gmail.com)
Date: Wed May 17 2006 - 10:02:35 ART
Hello,
AFAIK this happens because you apply "distribute-list" at ASBR,
and therefore immediately filter redistributed networks.
Try playing with "distribute-list xx out connected/static" to see the
difference.
HTH
Petr
2006/5/17, Gal Petru Cristian <cristian.gal@astral.ro>:
>
> Hi,
>
> I have a small issue with OSPF filtering. From what I understand
> distribute-list is used for filtering routes that are put in routing table
> without affecting the LSDB. My current configuration is like this:
>
> Thunder# sh run | be router ospf
> router ospf 6845
> router-id 194.102.255.75
> log-adjacency-changes detail
> redistribute connected subnets
> redistribute static subnets
> network 194.102.255.0 0.0.0.255 area 0
>
> Thunder# show ip access-lists ospf-out | be 123.1.
> 630 deny 10.123.1.0, wildcard bits 0.0.0.255 (1 match)
> 640 permit any (725 matches)
>
> Thunder#show ip route 10.123.1.0
> Routing entry for 10.123.1.0/24
> Known via "connected", distance 0, metric 0 (connected, via interface)
> Redistributing via ospf 6845
> Advertised by ospf 6845 subnets
> Routing Descriptor Blocks:
> * directly connected, via Bundle1
> Route metric is 0, traffic share count is 1
>
> On the neighbor:
> Vision#show ip ospf 6845 database | in 10.123.1.0
> 10.123.1.0 194.102.255.77 104 0x80000001 0x00B4EE 0
>
> After I apply distribute-list ospf-out out on the Thunder machine:
>
> Vision#show ip ospf 6845 database | in 10.123.1.0
>
> Does it really filter outbound LSA Type 5 ? Does this apply only on area 0
> or does it work on any area ? I cannot find any references on outbound
> filtering, except for type 3 on ABR.
>
> Thanks for any help.
>
> Cristian,
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Thu Jun 01 2006 - 06:33:21 ART