[j-nsp] export policy Junos 9.0

[david.roy at orange-ftgroup.com]

Thank you,
 
I've opened a Case and I had the same response : normal behavior. 
David
 


________________________________

	De : Benny Sumitro [mailto:benny.sumitro at gmail.com] 
	Envoyé : vendredi 24 octobre 2008 06:56
	À : ROY David DTF/DERX
	Cc : mtinka at globaltransit.net; juniper-nsp at puck.nether.net
	Objet : Re: [j-nsp] export policy Junos 9.0
	
	
	Hi,
	
	I once experienced this case too and already open a case with JTAC with no satisfying answer. One thing that a workaround is by creating the export policy not in the peer hierarchy but in the group hierarchy. If you have multiple peer in the group statement and need to have different policy for its member peer then maybe you need to separate them into different groups.
	
	Hope that helps.
	
	Best regards,
	Benny
	
	
	On Tue, Oct 21, 2008 at 8:59 AM, <david.roy at orange-ftgroup.com> wrote:
	


		Thank you Mark,
		
		More detail :
		
		I've one peer X.X.X.X with the following export policy
		
		peer X.X.X.X {
		  description mypeer
		  export POLY1 POLY2
		}
		
		When I try to add the POLY3
		
		set peer X.X.X.X export POLY3
		
		show
		
		peer X.X.X.X {
		  description mypeer
		  export POLY1 POLY2 POLY3
		}
		
		Commit sync
		
		I've this message :
		
		Oct 21 02:31:34.888543 bgp_peer_delete: NOTIFICATION sent to X.X.X.X (Internal AS YYYY): code 6 (Cease) subcode 3 (Peer Unconfigured), Reason: Peer Deletion
		
		Regards,
		David
		
		
		-----Message d'origine-----
		De : Mark Tinka [mailto:mtinka at globaltransit.net]
		Envoyé : mardi 21 octobre 2008 03:51
		À : juniper-nsp at puck.nether.net
		Cc : ROY David DTF/DERX
		Objet : Re: [j-nsp] export policy Junos 9.0
		

		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.
		
		
		*********************************
		This message and any attachments (the "message") are confidential and intended solely for the addressees.
		Any unauthorised use or dissemination is prohibited.
		Messages are susceptible to alteration.
		France Telecom Group shall not be liable for the message if altered, changed or falsified.
		If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
		********************************
		_______________________________________________
		juniper-nsp mailing list juniper-nsp at puck.nether.net
		https://puck.nether.net/mailman/listinfo/juniper-nsp
		




*********************************
This message and any attachments (the "message") are confidential and intended solely for the addressees. 
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration. 
France Telecom Group shall not be liable for the message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
********************************