Start with the highest code version supported on the hardware that has all the features you need. Subtract 2 from the major revision number. Pick a .3 version of that major revision. Work towards current from there depending on test results, security needs, etc.
On Wed, Aug 19, 2020 at 10:47 AM Colton Conor <colton.co...@gmail.com> wrote: > How do you plan which JUNOS version to deploy on your network? Do you stick > to the KB21476 - JTAC Recommended Junos Software Versions or go a different > route? Some of the JTAC recommended code seems to be very dated, but that > is probably by design for stability. > > https://kb.juniper.net/InfoCenter/index?page=content&id=KB21476&actp=METADATA > > Just wondering if JUNOS will ever go to a unified code model like Arista > does? The amount of PR's and bug issues in JUNOS seems overwhelming. Is > this standard across vendors? I am impressed that Juniper takes the times > to keep track of all these issues, but I am unimpressed that there are this > many bugs. > _______________________________________________ > 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