[j-nsp] OSPF Export policy question
Sinan Ilkiz
sinan.ilkiz at borusantelekom.com
Mon Oct 3 10:10:19 EDT 2005
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.
***************************************************************************
More information about the juniper-nsp
mailing list