root@juniper> show system storage fpc0: -------------------------------------------------------------------------- Filesystem Size Used Avail Capacity Mounted on /dev/gpt/junos 1.3G 1.1G 139M 89% /.mount <-- Not enough space tmpfs 651M 48K 651M 0% /.mount/tmp tmpfs 324M 436K 324M 0% /.mount/mfs Then we can clear storage as follows: root@juniper> request system storage cleanup Note: For EX2300 and EX3400 please refer to the following KB: [EX] Not enough storage while upgrading Junos EX2300 and EX3400 2. Another check that is important for any upgrade, is to have console access. This will help access the device if any issue arise and also helps recover the device more quickly. 3. Based on the point above, is also import to record the session terminal so we can have the information during the upgrade process. For example for Putty is as follows: Note: This may vary depending the terminal you are using.
root@switch> show configuration | display set | no-more And then it can be copied to a notepad or any text editor. 5. To provide accurate RCA in case the upgrade fails, it's important to collect the RSI and logs before the procedure
root@switch> request support information | save /var/tmp/RSI.txt
root@switch> file archive compress source /var/log destination /var/tmp/logs This will create the files on the /var/tmp/ directory and can be collected via WinScp or any FTP method. 6. Another device that is useful to have during upgrades is an USB flash drive. This will help in case the images needs to be pushed to the device and also if the upgrade fails, the device can be recovered via format install using the flash drive. 7. Another point that is important to check is the integrity of the software that we are adding to the device and for that we can check it with the md5 checksum. Please refer to the following article for a detail explanation: [Junos] How to check MD5 checksum on a Junos installation package 8. Sometimes while transferring the image via WinScp or any other file server, there could be an error message when the transfer is being done by a non-root user. Non-root users/super-user may find that the file copy utility always stages the transfer of jinstall packages for Juniper Networks devices, or any other file to the user's home directory even when the destination path is specified as /var/tmp and for that is always better to use the root user. Please refer to the following article for a detail explanation: "file copy" destination defaults to /var/home for non-root user resulting in image transfer failure