Nick, Why does it say *Resolved In* 16.2R1-S7 16.2R3 17.1R2 17.1R3 17.2R2 *17.3R1* 17.3R1 came before the now current JTAC recommend *17.3R2 right? *
On Wed, Jul 11, 2018 at 6:39 AM, Nick Ryce <nick.r...@commsworld.com> wrote: > Sorry I thought I had. > > > > We hit this https://prsearch.juniper.net/InfoCenter/index?page= > prcontent&id=PR1280492 > > > > This is being resolved in 17.3R3 which is due for release in a couple of > weeks. > > > > N > > > > *From: *Colton Conor <colton.co...@gmail.com> > *Date: *Wednesday, 11 July 2018 at 12:30 > *To: *Nick Ryce <nick.r...@commsworld.com> > *Cc: *Gustavo Santos <gustkil...@gmail.com>, Aaron <aar...@gvtc.com>, > Juniper List <juniper-nsp@puck.nether.net> > *Subject: *Re: [j-nsp] QFX5100 vs ACX5048 > > > > Nick, > > > > Did you find the PR for this memory leak? > > > > On Wed, Jul 4, 2018 at 11:02 AM, Nick Ryce <nick.r...@commsworld.com> > wrote: > > If you use BFD, do not upgrade to 17.3R2 as there is a memory leak. Will > find the PR. > > N > > > On 04/07/2018, 15:31, "juniper-nsp on behalf of Colton Conor" < > juniper-nsp-boun...@puck.nether.net on behalf of colton.co...@gmail.com> > wrote: > > Gustavo, > > We you say " Another problem was upgrading to the lastest Junos JTAC > recommended that made the ACX5048 unusable... ( Junos was unable to > find > the physical ports..) We had to downgrade to get it back working > again.." > what version was this as JTAC recently changed their recommended > version? > It seem everyone on this thread is talking about software train > 15.1X54. > > However, the current JTAC recommended version is Junos 17.3R2 as of 14 > May > 2018. Why is everyone running 15.1X54 code? > > Has anyone upgraded to Junos 17.3R2 on the ACX's? No matter the > model, all > ACX's current recommended is now Junos 17.3R2 > > > On Mon, Jul 2, 2018 at 8:11 AM, Gustavo Santos <gustkil...@gmail.com> > wrote: > > > I had some issues with ACX5048 , the most noticable was arp packets > from > > pure L2 vlans and VPLS punting to CPU and flooding the default arp > policer > > police.. > > JTAC was able to reproduce the issue and gave us an option to disable > > default arp policer until they release a service release to fix this > issue > > that was solved indeed. > > > > Another problem was upgrading to the lastest Junos JTAC recommended > that > > made the ACX5048 unusable... ( Junos was unable to find the physical > > ports..) We had to downgrade to get it back working again.. > > > > On Sun, Jul 1, 2018 at 8:05 PM Alexandre Guimaraes < > > alexandre.guimar...@ascenty.com> wrote: > > > >> Better in terms of concept. In term of usage, i still investing in > qfx5100 > >> > >> Acx5058 Suppose to be a promise of a new future, unfortunately, > with all > >> problematic of the qfx5100 hardware, the acx5048 leak vlan till the > last > >> breath of cpu.... after that, all deamons and services going > down.... up > >> and down, up and down. > >> > >> I never more brought one peace ACX5048 after jtac didnt responds > why and > >> solution for the leaking...( I have only two acx5048 and hundreds on > >> QFX...). > >> > >> The new promise is the new acx5448. No vlan leaking, a good load > >> balance(ae) algorithm, full of this.... full of that.... a lot of > promise. > >> > >> Let’s see... > >> > >> att > >> Alexandre > >> > >> Em 1 de jul de 2018, à(s) 19:31, Colton Conor < > colton.co...@gmail.com> > >> escreveu: > >> > >> > What is the main difference between these two boxes? Hardware > wise they > >> > look identical. Is there anything on the hardware side that makes > the > >> > ACX5048 better than a QFX5100, or is it only software related? > >> > _______________________________________________ > >> > juniper-nsp mailing list juniper-nsp@puck.nether.net > >> > https://puck.nether.net/mailman/listinfo/juniper-nsp > >> _______________________________________________ > >> juniper-nsp mailing list juniper-nsp@puck.nether.net > >> https://puck.nether.net/mailman/listinfo/juniper-nsp > >> > > > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > > > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp