[j-nsp] Preventing NSSA LSAs from leaking into the backbone when part of a summary

Tore Anderson tore.anderson at redpill-linpro.com
Fri Sep 16 13:57:58 EDT 2011


* Vladimir Blazhkun

> Did you try using:
> 
> set protocols ospf area ${nssa_area_id} nssa area-range ${ipv4_prefix} restrict,
> 
> where ${nssa_area_id} is the NSSA ID, ${ipv4_prefix} - the prefix,
> containing the range you want to filter?

Nope, which is a *facepalm* to me as I _did_ play around with the
«restrict» keyword but for some reason it never ocurred to me to use it
within the nssa {} block.

It worked very well. Final config, does almost exactly what I want:

# show protocols ospf area 0.0.0.1
nssa {
    default-lsa default-metric 1;
    no-summaries;
    area-range 10.22.0.0/16 restrict;

}
area-range 10.22.0.0/16;
interface [...]

The only little thing I could have wanted more was for a type-5 LSA to
be flooded in the backbone IFF there's only type-7 LSAs in the
summarized prefix in area 1 because in that case no type-3 summary would
make it out. But that's not really a problem in my case.

Thanks to all who replied!

Best regards,
-- 
Tore Anderson
Redpill Linpro AS - http://www.redpill-linpro.com/


More information about the juniper-nsp mailing list