I'm not sure how long Arista can keep the single binary approach as they expand their portfolio and feature set. For example it makes very little sense to have full BNG code on EX access switches, imge would be huge.
As for JTAC recommended release, it's a very generic recommendation not taking specific use cases into consideration (Except for EVPN-VXLAN CRB/ERB) Typically Juniper considers R3 releases to be mainstream adoptable (reality is more like R3-S<latest>) but you will sleep better if you do proper testing and to avoid regression bugs etc. You can always ask your friendly SE for some guidance. /Roger On Wed, Aug 19, 2020 at 4:46 PM Colton Conor <[email protected]> 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 [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
