<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2656.31">
<TITLE>RE: [j-nsp] Advertising a default route from JUNOS</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>I agree with 1 & 2.</FONT>
</P>
<P><FONT SIZE=2>But with 3, OSPF only allows you to export policies at the global level (unlike bgp global, group & neighbour import/export ability).</FONT></P>
<P><FONT SIZE=2>Need to keep the LSDB's the same.............</FONT>
</P>
<P><FONT SIZE=2>neil@lab001# set protocols ospf ?</FONT>
<BR><FONT SIZE=2>Possible completions:</FONT>
<BR><FONT SIZE=2>+ apply-groups Groups from which to inherit configuration data</FONT>
<BR><FONT SIZE=2>> area Configure an OSPF area</FONT>
<BR><FONT SIZE=2> disable Disable OSPF</FONT>
<BR><FONT SIZE=2>+ export Export policy</FONT>
<BR><FONT SIZE=2> external-preference Preference of external routes</FONT>
<BR><FONT SIZE=2>> graceful-restart Configure graceful restart attributes</FONT>
<BR><FONT SIZE=2>> overload Set the overload mode (repel transit traffic)</FONT>
<BR><FONT SIZE=2> preference Preference of internal routes</FONT>
<BR><FONT SIZE=2> reference-bandwidth Bandwidth for calculating metric defaults</FONT>
<BR><FONT SIZE=2> rib-group Routing table group for importing OSPF routes</FONT>
<BR><FONT SIZE=2> route-type-community Specify BGP extended community value to encode OSPF route type</FONT>
<BR><FONT SIZE=2>> traceoptions Trace options for OSPF</FONT>
<BR><FONT SIZE=2>> traffic-engineering Configure traffic engineering attributes</FONT>
</P>
<P><FONT SIZE=2>Neil.</FONT>
</P>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: Nicolas Fevrier [<A HREF="mailto:nicolas.fevrier@telindus.fr">mailto:nicolas.fevrier@telindus.fr</A>]</FONT>
<BR><FONT SIZE=2>Sent: 04 April 2003 14:13</FONT>
<BR><FONT SIZE=2>To: variable@ednet.co.uk; juniper-nsp@puck.nether.net</FONT>
<BR><FONT SIZE=2>Subject: RE: [j-nsp] Advertising a default route from JUNOS</FONT>
</P>
<BR>
<P><FONT SIZE=2>Hi Rich,</FONT>
</P>
<P><FONT SIZE=2>a Juniper's KB view note deals with the subject : Note 652</FONT>
<BR><FONT SIZE=2>(if you have access to the kb).</FONT>
</P>
<P><FONT SIZE=2>Roughly, here are the steps described in the note :</FONT>
<BR><FONT SIZE=2>1. create a static route w/0.0.0.0 and discard, </FONT>
<BR><FONT SIZE=2>2. create a policy to export that route, </FONT>
<BR><FONT SIZE=2>3. include the policy in the neighbor statement for the neighbor to whom you</FONT>
<BR><FONT SIZE=2>want this to apply. </FONT>
</P>
<P><FONT SIZE=2>Cheers,</FONT>
</P>
<P><FONT SIZE=2>Nicolas.</FONT>
</P>
<P><FONT SIZE=2># Hi,</FONT>
<BR><FONT SIZE=2># </FONT>
<BR><FONT SIZE=2># We've got a few M-40's handling our transit which get full internet </FONT>
<BR><FONT SIZE=2># routing tables via BGP. In turn, we want them to advertise a default </FONT>
<BR><FONT SIZE=2># route via OSPF to all the internal OSPF capable routers.</FONT>
<BR><FONT SIZE=2># </FONT>
<BR><FONT SIZE=2># I was wondering what's the best way to do this on a Juniper. </FONT>
<BR><FONT SIZE=2># Is there an</FONT>
<BR><FONT SIZE=2># equivalent of the "default-information originate" and </FONT>
<BR><FONT SIZE=2># "default-network"</FONT>
<BR><FONT SIZE=2># commands or is there a better implementation under Junos?</FONT>
<BR><FONT SIZE=2># </FONT>
<BR><FONT SIZE=2># Cheers,</FONT>
<BR><FONT SIZE=2># </FONT>
<BR><FONT SIZE=2># Rich</FONT>
</P>
<BR>
<BR>
<BR>
<BR>
<P><FONT SIZE=2>_______________________________________________</FONT>
<BR><FONT SIZE=2>juniper-nsp mailing list juniper-nsp@puck.nether.net</FONT>
<BR><FONT SIZE=2><A HREF="http://puck.nether.net/mailman/listinfo/juniper-nsp" TARGET="_blank">http://puck.nether.net/mailman/listinfo/juniper-nsp</A></FONT>
</P>
</BODY>
</HTML>