On Fri, Oct 24, 2008 at 08:43:26AM +0200, [EMAIL PROTECTED] wrote:
Thank you,
I've opened a Case and I had the same response : normal behavior.
Juniper's BGP implementation is heavily built around the concept of
update groups. This optimization helps reduce CPU load in the common
case
): code 6 (Cease) subcode 3 (Peer Unconfigured), Reason:
Peer Deletion
Regards,
David
-Message d'origine-
De : Mark Tinka [mailto:[EMAIL PROTECTED]
Envoyé : mardi 21 octobre 2008 03:51
À : juniper-nsp@puck.nether.net
Cc : ROY David DTF/DERX
Objet : Re: [j-nsp] export policy Junos
Hi all,
Do you know, if in Junos 9.0 when you modify the export policy of a BGP
peer : for example adding a new policy in the export list, the BGP
session is coming down ?
We encountered this issue.
Junos doc :
Note: Changing configuration statements that affect BGP peerings, such
as
On Tuesday 21 October 2008 09:29:13
[EMAIL PROTECTED] 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
2008 03:51
À : juniper-nsp@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
[EMAIL PROTECTED] wrote:
But it's not clear for the export statement.
The following has been our experience:
The general idea is that changing
5 matches
Mail list logo