
ntarique at juniper
Nov 14, 2009, 4:56 AM
Post #7 of 7
(846 views)
Permalink
|
Hi Ramesh, Well, that should be your call. But till the time you make it & for time being with your current configuration, whenever you want to make any change to your import policy you can first deactivate NSR & then commit. NSR can be later reactivated. Thanks & Regards, Tarique A. Nalkhande ________________________________ From: Ramesh Karki [mailto:rameshkarki [at] gmail] Sent: Saturday, November 14, 2009 5:34 PM To: Nalkhande Tarique Abbas Cc: Chris Adams; juniper-nsp [at] puck Subject: Re: [j-nsp] BGP strange problem on M10i Hi, Thank for the response and for that Bug information. To achieve high availability we have configured Graceful Routing Engine Switchover with Non-Stop Routing (NSR). So, what do you like to suggest us ?, either change the configuration with Graceful Restart or upgrade the JunOS. Your help will be appreciated. Thank you Ramesh On Sat, Nov 14, 2009 at 1:07 AM, Nalkhande Tarique Abbas <ntarique [at] juniper> wrote: If you have NSR configured, then have a look at PR/396291 Thanks & Regards, Tarique A. Nalkhande -----Original Message----- From: juniper-nsp-bounces [at] puck [mailto:juniper-nsp-bounces [at] puck] On Behalf Of Ramesh Karki Sent: Friday, November 13, 2009 10:06 PM To: Chris Adams; juniper-nsp [at] puck Subject: Re: [j-nsp] BGP strange problem on M10i Hi, The version we are using is JunOS 9.2R2.15 I also supposed that Junos do not require any kind of reset, but when I add any new prefixes (ow n by AS or its customers) on policy-statement to block incoming via upstream and commit, it does not take effect. But when I hard reset the peer then only it takes on effect. Currently we peering with Tier One1 ISP with two location (Multi-homing to the single AS), and got a full BGP table from both side. Thank you Ramesh. On Fri, Nov 13, 2009 at 8:04 PM, Chris Adams <cmadams [at] hiwaay> wrote: > Once upon a time, Ramesh Karki <rameshkarki [at] gmail> said: > > First, we had to hard reset the bgp peer whenever we change the policies > > (inbound policy) that we had set. By just doing soft reset the router > will > > not take effect of that changed policies until we do hard reset. > > You shouldn't need to do any kind of reset; on JUNOS, policy changes are > applied on commit (although it can take a few seconds to work through a > full BGP table). > > You didn't mention what version of JUNOS you are running (always an > important thing to include when discussing possible bugs). > > -- > Chris Adams <cmadams [at] hiwaay> > Systems and Network Administrator - HiWAAY Internet Services > I don't speak for anybody but myself - that's enough trouble. > _______________________________________________ > juniper-nsp mailing list juniper-nsp [at] puck > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list juniper-nsp [at] puck https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp [at] puck https://puck.nether.net/mailman/listinfo/juniper-nsp
|