EX2300 and EX3400 switches are equipped with a 2GB flash disk whose disk size is sufficient to be able to store release images, system files, and logs. However, when storage space becomes more heavily utilized over time, there may not be enough disk space available to complete a software update.
This article is written to provide guidance on how to manage storage space and potentially overcome any obstacles tied to space that are encountered in a software update.
If for any reason the information in this article does not address the issues tied to disk space that are encountered during a software update, contact theSupportfor further assistance.
Run therequest system storage cleanupcommand. This will remove any unnecessary files but keep everything under/rootintact:
root@juniper> request system storage cleanup
Run therequest system snapshot delete snap*command. This will delete any existing recovery snapshots that are stored on the system.
root@juniper> request system snapshot delete snap*
Install the two packages by using therequest system software add" command:
root@juniper> request system software add /var/tmp/os-package.tgz
root@juniper> request system software add /var/tmp/package-hooks-ex.tgz
Install theJunos OS release softwareby using theno-copy,unlink, andforceoptions under therequest system software addcommand:
root@juniper> request system software add /var/tmp/junos-arm-32-18.4R1.8.tgz force unlink no-copy
Theunlinkoption is available in Junos OS Release 18.1R2. It removes the.tgzfile immediately after the unpack so that the image size calculation takes into account the freed up space tied to the image deletion. This effectively reduces the amount of space needed by the process to 2X instead of 3X. Note that there are some occasions where the add will fail. Try it a second time before moving on.
Reboot the system to complete the Junos OS release SW installation process.
After the upgrade is complete, remove the two packages and reboot the system. Theshow versioncommand will provide information about install packages as shown in the below example.
root@juniper> show version
JUNOS OS Kernel 32-bit [20191022.14c2ad5_builder_stable_11]
JUNOS OS libs [20191022.14c2ad5_builder_stable_11]
JUNOS OS runtime [20191022.14c2ad5_builder_stable_11]
JUNOS OS time zone information [20191022.14c2ad5_builder_stable_11]
JUNOS py extensions [20191029.212835_builder_junos_182_r3_s2]
JUNOS py base [20191029.212835_builder_junos_182_r3_s2]
JUNOS network stack and utilities [20191029.212835_builder_junos_182_r3_s2]
JUNOS libs [20191029.212835_builder_junos_182_r3_s2]
JUNOS runtime [20191029.212835_builder_junos_182_r3_s2]
JUNOS package hooks ex [20191022.160523_sjg_dev_common]JUNOS OS package [20191113.002318_sjg_stable_11]
JUNOS OS crypto [20191022.14c2ad5_builder_stable_11]
JUNOS Web Management Platform Package [20191029.212835_builder_junos_182_r3_s2]
Delete the two packages by using therequest system software deletecommand:
root@juniper> request system software delete os-package
root@juniper> request system software delete package-hooks-platform
Now reboot the system to complete the uninstallation process for the packages:
Hello, Regarding the update for the EX2300 it is know that they have limited space.
In order to upgrade that switch succesfully you can try the Request system storage clean up, However the space will be free until the device is rebooted, you can also add the force up no copy over to the Upgrade command.
Request system software add /var/tmp/(Image name ) force unlink no-copy so the upgrade does not uses the space available on the switch and should be able to go through.
In last resort as the upgrade still does not works we will need to make the format proccess in order to have the device upgraded but all config will be lost so take a copy of it before doing this proccess :
Also as a side note in case you use the format proccess you can go directly from version 14 over to 18 using this proccess, but remember to add the Set system services ssh root login allow so you do not lose the SSH access to the siwtch as on version 18 there is a implicit root ssh login denied on this software.
Hope this helps.
Please mark "Accept as solution" if this answers your query.