[j-nsp] Advertising a default route from JUNOS

[MPuras at solunet.com]

You could create a generate route like such:

    generate {   
        route 0.0.0.0/0 policy if-upstream-routes-exist;
    }


    policy-statement if-upstream-routes-exist {
        term only-certain-contributing-routes {
            from {

                route-filter 10.100.0.0/17 exact;
            }
            then accept;
        }                                                                
        term reject-all-other-routes { 
            then reject;
        }
    }

then just follow the remaining instructions for advertising it into OSPF.


Thanks, 

Mario Puras 
SoluNet Technical Support
Mailto: mpuras at solunet.com
Direct: (321) 309-1410  
888.449.5766 (USA) / 888.SOLUNET (Canada) 



-----Original Message-----
From: variable at ednet.co.uk [mailto:variable at ednet.co.uk]
Sent: Friday, April 04, 2003 11:22 AM
To: juniper-nsp at puck.nether.net
Subject: RE: [j-nsp] Advertising a default route from JUNOS


On Fri, 4 Apr 2003, Neil Stirling wrote:

> I agree with 1 & 2.
> 
> But with 3, OSPF only allows you to export policies at the global level
> (unlike bgp global, group & neighbour import/export ability).
> Need to keep the LSDB's the same.............

That's fine, but nailing up static routes isn't a great idea.  Is there 
any way I can get the Juniper to stop announcing the default route if it 
loses a particular peering session/interface goes down?

Cheers,

Rich

_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp