[j-nsp] export policy Junos 9.0

[Mark Tinka]

On Tuesday 21 October 2008 09:29:13 
david.roy at orange-ftgroup.com wrote:

> But it's not clear for the export statement.

The following has been our experience:

The general idea is that changing parametres that affect the 
BGP session/peering itself (i.e., what causes the session 
to establish or get torn down) would likely cause a reset, 
e.g., ASN change, MD5 password change, e.t.c.

However, changes that affect the routing policy (i.e., what 
gets carried in the next BGP update) would not tear the 
session down.

Export/import policies affect the routing policy, not so 
much the actual session itself, e.g., modifying the 
LOCAL_PREF value under an import policy, and issuing a 
commit, would not tear the session(s).

Some vendors have distinguished these paradigms by allowing 
for session templates (those that affect the actual 
peering/session itself, i.e., is it up or down) and policy 
templates (those that affect what gets carried in the next 
BGP update, i.e., the routing policy).

Cheers,

Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: This is a digitally signed message part.
URL: <https://puck.nether.net/pipermail/juniper-nsp/attachments/20081021/26683d06/attachment.bin>