Since we're ventured into the strange... You could also run BGP with short timers and filter the routes there.
On Thu, Dec 2, 2010 at 10:35 AM, James S. Smith <[email protected]>wrote: > Just thinking about hacks, one way that might work would be to setup static > routes on the devices where you don't want these routes. For example: > > set routing-options static route 192.168.123.0/24 reject > > Since this is a static it will be preferred over the OSPF routes. > > > > -----Original Message----- > From: [email protected] [mailto: > [email protected]] On Behalf Of Phill Jolliffe > Sent: December 1, 2010 7:50 PM > To: [email protected] > Cc: [email protected] > Subject: Re: [j-nsp] OSPF IMPORT POLICIES > > If your end goal is to prevent the ospf prefixes from becoming active > in the PFE on a single chassis for then apply an export policy to the > forwarding table under routing-options. The routes can sit active in > the RIB but never make to the linecard. > > This is a dirty hack for several reason. Show route says one thing, > show route forwarding-table another. LSDB looks good but doesn't match > forwarding plane. Neighbor might compute paths across the router you > apply the policy to, forward traffic and be back holed. > > That all said a dirty hack is what is needed in till there is time to > re make the world pretty :-) > > On Thu, Dec 2, 2010 at 1:27 AM, Giuliano Cardozo Medalha > <[email protected]> wrote: > > Is it possible to put the internal LSA routes pointing to discard > next-hop ? > > > > We need to invalidate some routes ... > > > > Or is not possible to process it ? > > > > Is it only possible to set priority to the route ? > > > > Thanks a lot, > > > > > >> Only external LSA can be prevented from entering the RIB via ospf import > >> policy. > >> > >> > >> On Thu, Dec 2, 2010 at 12:10 AM, Giuliano Cardozo Medalha > >> <[email protected]> wrote: > >>> > >>> People, > >>> > >>> Hi, > >>> > >>> We are trying to filter OSPF Internal Routers from being installed into > >>> the > >>> RIB (Routing Table). > >>> > >>> JUNIPER has the correct command to filter input routes. > >>> > >>> set protocols ospf import<policy name> > >>> > >>> But when we create an import policy on our environment ... all the > >>> internal > >>> routes are not filtered and are installed onto the RIB. > >>> > >>> Is there any way to use policy routing to block the internal ospf > routes > >>> to > >>> be installed onto the RIB ? > >>> > >>> it is possible to use rib-groups to redirect the ospf internal routes > to > >>> another routing table ? > >>> > >>> Can you please give to me some guide ? > >>> > >>> Thanks a lot, > >>> > >>> Giuliano > >>> _______________________________________________ > >>> juniper-nsp mailing list [email protected] > >>> https://puck.nether.net/mailman/listinfo/juniper-nsp > >>> > >> > >> > > > > > > > > -- > Phill Jolliffe > > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > > This message contains confidential information and is intended only for the > individual named. If you are not the intended recipient you are notified > that disclosing, copying, distributing or taking any action in reliance on > the contents of this information is strictly prohibited. > > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
