[j-nsp] External routes in OSPF database

[Keegan Holley]

2011/7/9 Alex D. <listensammler at gmx.de>

> Thanks for the replies.
>
>
>
>

>
> > Are you sure that it is all the BGP routes?
> I didn't examine all routes in detail, but the quantity brought me to that
> conclusion.
>
>
> >Should be easy to confirm from where the externals are originating
> >through its router-id.
> > Your probably learning them from the customer
> The CPE router is also under my control and only advertise it's local
> networks. There's only "redistribute connected" under "router ospf 1"
> configured. The externals originate from the PE-routers itself and i don't
> find a reason why they appear only when adjacency is up.


The PE routers facing the customers or the PE routers facing your upstreams?
 You only show 14k external LSA's in the database which is much smaller than
a full BGP feed.  Are the above snippets from the PE router that is
originating the external LSA's?  Have you confirmed that the next hop on
that PE router is actually learned from BGP and not from static or
aggregate? Could there be inherited config from something else?



>
> > If you wish *only* a default and type 1/2 lsas (and a type 3 for the >
> default) you may consider setting as a totally stubby network (which >
> should not be area 0)
> Hmm, is it possible to configure OSPF only with e.g. area 0.0.0.1 without
> having an area 0.0.0.0 ? I didn't try that before and thought that area
> 0.0.0.0 is always needed.
>

You can have only an area 1 but it would be isolated from other areas and
not ideal.  It would be better to have your network and edge routers in area
0 and customers in different areas.  The trade-off would be keeping your
customer interfaces out of the backbone flooding domain vs. scaling and the
number of areas you'd have to create.  You could also use routing-instances
but that would be equally as messy.  As most others have said the best thing
would be to require BGP or static routes.


> Regards,
> Alex
>
>
>
> ______________________________**_________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/**mailman/listinfo/juniper-nsp<https://puck.nether.net/mailman/listinfo/juniper-nsp>
>
>