[j-nsp] OSPF Export policy question

[Krasimir Avramski]

OSPF inbound route filtering introduced in 7.0 release.

------------------------------------------------------------------------



---Original Message----------------------------------
 FROM: rafal.szarecki at ericsson.com
 TO: sinan.ilkiz at borusantelekom.com
 SUBJECT: Re: RE: [j-nsp] OSPF Export policy question
 SENT: OCTOBER  3, 2005 05:15PM
 CC: juniper-nsp at puck.nether.net
--------------------------------------------------------
> 
> I not remember JUNOS version when this wos intriduced but in 7.3:
> 
> "OSPF import policy allows users to define policy to prevent adding OSPF routes to the routing table. This filtering happens when OSPF installs the route in the routing table. You can filter the routes, but not LSA flooding. The import policy can filter on any attribute of the OSPF route.
> 
> To filter OSPF routes from being added to the routing table, include the import statement:
> 
> [edit protocols (ospf | ospf3)]
> 
> import [ policy-names ]; "
> 
> http://www.juniper.net/techpubs/software/junos/junos73/swconfig73-routing/html/ospf-config35.html#1044743
> http://www.juniper.net/techpubs/software/junos/junos73/swconfig73-routing/html/ospf-summary18.html#1269569
> 
> Rafaі Szarecki JNCIE
> 
> skype me  
> 
> 
> 
> > -----Original Message-----
> > From: Sinan Ilkiz [mailto:sinan.ilkiz at borusantelekom.com]
> > Sent: Monday, October 03, 2005 4:47 PM
> > To: Rafal Szarecki (WA/EPO)
> > Subject: RE: [j-nsp] OSPF Export policy question
> > 
> > 
> > 
> > You are clearly rigth about LSDB. Perhaps someday JunOS will 
> > be able to
> > do that.
> > 
> > Thanks.
> > 
> > 
> > 
> > -----Original Message-----
> > From: Rafal Szarecki (WA/EPO) [mailto:rafal.szarecki at ericsson.com] 
> > Sent: Monday, October 03, 2005 5:18 PM
> > To: Sinan Ilkiz
> > Subject: RE: [j-nsp] OSPF Export policy question
> > 
> > However LSDB has to be equal on all routers, in moder JUNOS 
> > if should be
> > possible what routes will be imported from LSDB to RIB and 
> > then to FIB.
> > 
> > Rafal
> > 
> > > -----Original Message-----
> > > From: juniper-nsp-bounces at puck.nether.net
> > > [mailto:juniper-nsp-bounces at puck.nether.net]On Behalf Of Sinan Ilkiz
> > > Sent: Monday, October 03, 2005 4:10 PM
> > > To: Sabri Berisha
> > > Cc: juniper-nsp at puck.nether.net
> > > Subject: RE: [j-nsp] OSPF Export policy question
> > > 
> > > 
> > > 
> > > Ok Sabri, you are RFC wise rigth. But this is just a test 
> > scenario :-)
> > > 
> > > I think what i want is impossible due to the multicast 
> > nature of OSPF.
> > > 
> > > Thanks anyway. I get what i need :-)
> > >  
> > > 
> > > -----Original Message-----
> > > From: Sabri Berisha [mailto:sabri at cluecentral.net]
> > > Sent: Monday, October 03, 2005 2:47 PM
> > > To: Sinan Ilkiz
> > > Cc: juniper-nsp at puck.nether.net
> > > Subject: Re: [j-nsp] OSPF Export policy question
> > > 
> > > On Mon, Oct 03, 2005 at 02:32:07PM +0300, Sinan Ilkiz wrote:
> > > 
> > > Hi Sinan,
> > > 
> > > > I am trying to implement an OSPF export policy with the "neighbor"
> > > > statement. It seems that it does not have any effect on the 
> > > > distribution of routes. Configuration is as follows;
> > > >  
> > > > IMO, neighbor router should not get any route updates with this
> > > policy.
> > > > But M7i does not bother "to neighbor 1.2.3.4" statement and 
> > > > distributes its routes. Any thoughts or comments?
> > > 
> > > OSPF requires all routers in an area to have the same link-state 
> > > database. This prohibits you from creating 
> > policy-statements where you
> > 
> > > prohibit -some- neighbors in an area from receiving certain LSA's.
> > > 
> > > --
> > > Sabri
> > > 
> > > please do not throw salami pizza away
> > > 
> > > 
> > > UYARI/NOTIFICATION:
> > > **************************************************************
> > > *************
> > > Bu e-posta ve ekleri sadece gonderilen adres sahiplerine aittir. Bu 
> > > mesajin yanlislikla tarafiniza ulasmis olmasi halinde, lutfen 
> > > gondericiye derhal bilgi veriniz ve mesaji sisteminizden siliniz. 
> > > BORUSAN TELEKOM bu mesajin icerigi ve ekleri ile ilgili olarak 
> > > hukuksal hicbir sorumluluk kabul etmez.  Gonderen taraf hata veya 
> > > unutmalardan sorumluluk kabul etmez.
> > > 
> > > The information contained in this e-mail and any files transmitted 
> > > with it are intended solely for the use of the individual 
> > or entity to
> > 
> > > whom they are addressed.If you received this message in 
> > error, please 
> > > immediately notify the sender and delete it from your 
> > system.BORUSAN 
> > > TELEKOM doesn't accept any legal responsibility for the 
> > contents and 
> > > attachments of this message.The sender does not accept 
> > liability for 
> > > any errors or omissions.
> > > 
> > > **************************************************************
> > > *************
> > > 
> > > _______________________________________________
> > > juniper-nsp mailing list juniper-nsp at puck.nether.net 
> > > http://puck.nether.net/mailman/listinfo/juniper-nsp
> > > 
> > 
> > 
> > UYARI/NOTIFICATION:
> > **************************************************************
> > *************
> > Bu e-posta ve ekleri sadece gonderilen adres sahiplerine 
> > aittir. Bu mesajin yanlislikla tarafiniza ulasmis olmasi 
> > halinde, lutfen gondericiye derhal bilgi veriniz ve mesaji 
> > sisteminizden siliniz. BORUSAN TELEKOM bu mesajin icerigi ve 
> > ekleri ile ilgili olarak hukuksal hicbir sorumluluk kabul 
> > etmez.  Gonderen taraf hata veya unutmalardan sorumluluk kabul etmez.
> > 
> > The information contained in this e-mail and any files 
> > transmitted with it are intended solely for the use of the 
> > individual or entity to whom they are addressed.If you 
> > received this message in error, please immediately notify the 
> > sender and delete it from your system.BORUSAN TELEKOM doesn't 
> > accept any legal responsibility for the contents and 
> > attachments of this message.The sender does not accept 
> > liability for any errors or omissions.
> > 
> > **************************************************************
> > ************* 
> > 
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
> 
>