[j-nsp] Send default route via ospf to a specific area

[harry]

Yes, that would work.

This is not export policy, however, which was the point I hoped to make. The
same is true for a stub or totally stub area.

> -----Original Message-----
> From: Raymond Cheh [mailto:rcheh at juniper.net] 
> Sent: Friday, October 10, 2003 10:37 AM
> To: harry
> Cc: 'Michael Friedel'; juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] Send default route via ospf to a specific area
> 
> 
> What about using default-lsa in nssa area?
> 
> ospf {
>      area 0.0.0.0 {
>          interface lo0.0;
>      }
>      area 0.0.0.1 {
>          nssa {
>              default-lsa {
>                  default-metric 1;
>                  type-7;
>              }
>              interface ge-0/0/0.0;
>          }
>      }
> }
> 
> This will generate the 0.0.0.0 nssa lsa into area 1 only:
> 
> user at router>  show ospf database lsa-id 0.0.0.0 detail
> 
>      OSPF link state database, area 0.0.0.1
>   Type       ID               Adv Rtr           Seq      Age  
> Opt  Cksum 
>   Len
> NSSA     0.0.0.0          10.255.71.52     0x80000001    40  
> 0x0  0xe4e7  36
>    mask 0.0.0.0
>    Type 1, TOS 0x0, metric 1, fwd addr 0.0.0.0, tag 0.0.0.0
> 
> Hope this helps.
> 
> Raymond
> 
> harry wrote:
> > I think this is because injecting LSA into one area, bit 
> not another, 
> > is a function of area types, i.e., stub vs NSSA, as opposed 
> to policy. 
> > You cannot use export policy to filter LSAs from a given 
> area. Things 
> > like "to-area" are normally used to adjust the metric of a 
> route, not 
> > to perform filtering.
> > 
> > Also:
> > 
> >      term 2 {
> > 
> >>        from protocol ospf;
> >>        then accept;
> >>    }
> > 
> > 
> > Is the default and should not have any real impact.
> > 
> > 
> > The bottom line is that an ASBR will generate external LSAs 
> into all 
> > non-stub areas by protocol specification.
> > 
> > HTHs.
> > 
> > 
> > 
> > 
> >>-----Original Message-----
> >>From: juniper-nsp-bounces at puck.nether.net
> >>[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of 
> >>Michael Friedel
> >>Sent: Friday, October 10, 2003 10:13 AM
> >>To: juniper-nsp at puck.nether.net
> >>Subject: [j-nsp] Send default route via ospf to a specific area
> >>
> >>
> >>I saw a previous post on adding a default route and not
> >>having it in the forwarding table by using no-install. That 
> >>seems to work and the recieving machine gets the default 
> >>routes exported to it via ospf fine. But when I try and set 
> >>it to only send it to a specific area, it doesn't seem to 
> >>send the route (yes its the right area). I did add the 
> >>current bogons list to the martians (including 224.0.0.0/3 
> >>orlonger), but it shoudnt affect just that 1 area if ospf at 
> >>all. Any help would be much appreciated. Thanks ahead of time.
> >>  -Mike
> >>
> >>Heres some cuts from a test config:
> >>#routing options ...
> >>static {
> >>    route 0.0.0.0/0 {
> >>        discard;
> >>        no-install;
> >>    }
> >>}
> >>
> >>#protocol options.....
> >>ospf {
> >>    export ospf-exports;
> >>    area 0.0.0.0 {
> >>        interface fe-0/0/0.0;
> >>        interface fe-0/0/1.0;
> >>    }               
> >>    area 0.0.0.20 {
> >>        interface fe-0/0/2.0;
> >>        interface fe-0/0/3.0;
> >>    }
> >>}
> >>
> >>
> >>#policy options ....
> >>policy-statement ospf-exports {
> >>    term 1 {
> >>        from {
> >>            protocol static;
> >>            route-filter 0.0.0.0/0 exact;
> >>        }
> >>        to area 0.0.0.20;
> >>        then accept;
> >>    }
> >>    term 2 {
> >>        from protocol ospf;
> >>        then accept;
> >>    }
> >>    term end {
> >>        then reject;
> >>    }
> >>}
> >>
> >>_______________________________________________
> >>juniper-nsp mailing list juniper-nsp at puck.nether.net
> >>http://puck.nether.net/mailman/listinfo/junipe> r-nsp
> >>
> > 
> > 
> > 
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net 
> > http://puck.nether.net/mailman/listinfo/juniper-nsp
> > 
> > 
> 
>