Switching

 View Only

IMPORTANT MODERATION NOTICE

This community is currently under full moderation, meaning  all posts will be reviewed before appearing in the community. Please expect a brief delay—there is no need to post multiple times. If your post is rejected, you'll receive an email outlining the reason(s). We've implemented full moderation to control spam. Thank you for your patience and participation.



  • 1.  EX4300/4600 mixed chassis upgrade from 19.1R3.9 to 20.4R3-S1.3 disk space issues

    Posted 03-10-2022 13:14
    Good afternoon colleagues,

    I have a mixed VC stack of switches consisting of:

    2x EX4600-40F - routing engine
    2x EX4300-48T - line cards

    Currently running Junos 19.1.R3.9 which I had recently upgraded to but is causing issues, so I am now going to 20.4R3-S1.3 as recommended by Juniper.

    I tried the upgrade the other week by following my steps:

    1. Load both 4300 and 4600 images onto FAT32 usb key
    2. Insert key into top routing engine
    3. Mount usb key, copy files to /var/tmp/
    4. request system software add set [/path/to/4300-image.tgz /path/to/4600-image.tgz]

    The process would run then fail when validating fpc3 (4300), complaining about lack of disk space - complaining about roughly 14MB of space.

    I tried using "request system storage cleanup all-members" command but after running the software add command I still got the same result.

    I tried adding the images directly from the usb key - same result

    I tried adding the images by using 'no-copy' arguments - same result.

    Where do I go from there? I'd prefer not to go down the format install route but that does seem like the way I am going - is it possible for me to run the same command but only reference a single image for the designated switch i.e. request system software add /var/tmp/4300-image.tgz member x - and where x is, is the fpc number of the 4300 - then repeat it for the secondary 4300 then do the 4600s?

    Your time and help is appreciated. 

    Thank you.

    ------------------------------
    WILLIAM WAGER
    ------------------------------


  • 2.  RE: EX4300/4600 mixed chassis upgrade from 19.1R3.9 to 20.4R3-S1.3 disk space issues

    Posted 03-10-2022 19:49
    We had the same problem. Do the storage cleanup, but the solution in our case was to add 'no-validate' to the end of the 'request system software add' command


  • 3.  RE: EX4300/4600 mixed chassis upgrade from 19.1R3.9 to 20.4R3-S1.3 disk space issues

    Posted 03-11-2022 05:36
    Thanks cordcscott, so my original command with both image sets in it should do the trick with no-validate ?

    ------------------------------
    WILLIAM WAGER
    ------------------------------



  • 4.  RE: EX4300/4600 mixed chassis upgrade from 19.1R3.9 to 20.4R3-S1.3 disk space issues

    Posted 03-21-2022 10:13
    Thought I'd update my own thread to say no-validate didn't do the job, what I had to do was run the command 4 times for each switch member to load the software.

    On the 4600's I had to do a force-host to get the software to install.

    I then rebooted all the members at once and the upgrade completed.

    ------------------------------
    WILLIAM WAGER
    ------------------------------