Junos OS

Expand all | Collapse all

Upgrade path for JUNOS/EX

  • 1.  Upgrade path for JUNOS/EX

    Posted 04-24-2019 13:19

    I currently have 3 models of switches in my environment and am searching for the appropriate Junos Upgrade path to take everything up to current. Can anyone tell me if there is anything I cant or shouldnt do? 

     

    I plan to: 

    EX2300: currently 15.1x53-D590.1 > to 19.1R1

    EX3300: currently 15.1R6-S2.1 > 15.1R7.9

    EX4600: currently 17.3R1.10 > to 19.1R1

     

    PS: Is there a reason that JTAC still doesnt recommend a release higher than 15.1



  • 2.  RE: Upgrade path for JUNOS/EX

    Posted 04-24-2019 13:30

    Hi Brad,

     

    the rule of thumb is not more than 3 releases on one jump:

     

    EX2300: currently 15.1x53-D590.1 > to 19.1R1------> go to a 17 version first, then 17 to 19 should be good 

    EX3300: currently 15.1R6-S2.1 > 15.1R7.9------> direct

    EX4600: currently 17.3R1.10 > to 19.1R1-----> this one can be done directly as well 

     

    hope that helps!



  • 3.  RE: Upgrade path for JUNOS/EX

     
    Posted 04-24-2019 13:54

    The path for EX3300 is correct but for EX2300 and EX4600 you need to do two steps.

     

    EX2300:

     

    There are 5 releases between 15.1X53 and 19.1 (15.1X53, 18.1, 18.2, 18.3, 18.4 and 19.1), so upgrade path is something like:

    15.1X53 -> 18.2 or 18.3 -> 19.1

     

    EX4600:

     

    There are 7 releases between 17.3 and 19.1 (17.3, 17.4, 18.1, 18.2, 18.3, 18.4 and 19.1), so upgrade path is something like:

    17.3 -> 18.2 -> 19.1

     



  • 4.  RE: Upgrade path for JUNOS/EX

    Posted 04-24-2019 14:43

    And as far as releases go, have there been any significant changes to configs that would break existing configs? 



  • 5.  RE: Upgrade path for JUNOS/EX

    Posted 04-24-2019 14:59

    Brad,

     

    About that my tests have shown that this upgrade is the one that can give you more troubles:

     

    EX2300: currently 15.1x53-D590.1 > to 19.1R1

     

    This is part of some tests I did for a case, that time it was proven that an empty configuration avoided the problems the customer was running in to (device stuck on db>)

    Configuration?

    15.1X53D30 to 17.3R3

    empty configuration

    success

    empty configuration

    success

    empty configuration

    success

    empty configuration

    success

     

     

     

     

    This problem however should be fixed from 15.1X53D210 onwards.