Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Before You Upgrade or Reinstall Junos OS Evolved

SUMMARY Before you upgrade or reinstall Junos OS Evolved, you must save some system information, ensure enough disk space is available, and back up the current software and configuration.

You need to gather and to save information about the current state of the system so that you can compare the state before and after the upgrade to make sure the system is correctly configured and operating. You also need to take a snapshot of the system software and configuration before you upgrade, so that you are able to recover the system if necessary.

  1. To check if enough disk space is available for the installation, use the show system storage operational mode command.

    Various directories store the installed software versions and the data files, such as the log and core files. If the (/soft, /var, or /data) directories are at 90% capacity or more, the device does not have enough storage space to install a software package. A software installation could fail if these directories do not have sufficient space.

    We recommend that you store no more than 5 versions of software on the device. Please use the request system software delete operational mode command to delete older or unused versions of software. To delete all but the current and the rollback versions of the software, use the request system software delete archived operational mode command.

    Use the request system storage cleanup operational mode command if your storage area (the /var directory) is full. We recommend that you issue this command before you copy the new image into the /var/tmp directory as this command could remove the image if the /var partition is low on space.

    For more information, see Ensure Sufficient Disk Space for Upgrades.

    The sample output displays statistics about the amount of free disk space in the device's file system for the FPCs and Routing Engines.

  2. To save the system software information, use the show version detail | save filename and the show system software list operational mode commands.
    The save filename option saves the information in a file for you to look at later, after you upgrade the system, to compare to the current state.
    1. Issue the show version detail | save filename command.

      The sample output shows the contents of the saved file: the hostname, device model, current software package name, and the various Junos OS Evolved processes and their release numbers.

    2. Issue the show system software list | save filename command.

      The sample output shows the contents of the saved file: all the software versions in the persistent storage on the Routing Engines in the system and the current software version running on the FPCs. FPCs cannot store more than one version, because FPCs do not contain any persistent storage media.

  3. To save the active configuration on the device, which is the last committed configuration, use the show configuration | save filename operational mode command.

    If you need to make changes to the configuration before you install the software package, now is a good time to do so, before you capture any further information about your system. After you change the configuration and commit it, save a copy of it in the /var/tmp directory.

  4. To save information about the system alarms, use the show system alarms | save filename operational mode command.

    The sample output shows the contents of the saved file: information about the active alarms.

  5. To save information about the nodes in the system, use the show system nodes | save filename operational mode command.

    The sample output shows the contents of the saved file: node information about the FPCs and Routing Engines in the system.

  6. To save the hardware component information, use the show chassis hardware | save filename operational mode command.

    You will need the hardware information if the device cannot successfully reboot after the upgrade and so you cannot access the serial number for the Routing Engine. The Routing Engine serial number is necessary for the Juniper Networks Technical Assistance Center (JTAC) to issue a return to manufacturing authorization (RMA). Without the Routing Engine serial number, JTAC must dispatch an on-site technician to issue the RMA.

    You should then upload this file to an off-box location using scp.

    The output varies depending on the chassis components of the device. Refer to the hardware guides for information about the different chassis components. The sample output shows the contents of the saved file: the hardware inventory for a PTX10008 router.

  7. To save the chassis environment information, use the show chassis environment | save filename operational mode command.

    The sample output shows the contents of the saved file: environmental information about the chassis, including the temperature and status for the various chassis components as well as the fan speeds.

  8. To save the system boot-message information, use the show system boot-messages | save filename operational mode command.

    The sample output shows the contents of the saved file: the initial messages generated by the system kernel upon boot for FPCs and the Routing Engines; the contents of the /var/run/dmesg.boot file.

  9. To save information about the interfaces on the device, use the show interfaces terse | save filename operational mode command.

    The sample output shows the contents of the saved file: summary information about the physical and logical interfaces on the device.

  10. To save protocol information, use the show operational mode commands with the save filename option for the protocols configured for the device. To discover for which categories show commands are available, type show ? at the CLI operational mode prompt, and the system responds with a list of the available categories. Then choose a category, for example, bgp. Entering show bgp ? displays the list of show commands available for that category.

    This example shows the commands to save useful information about the Border Gateway Protocol (BGP), Intermediate System-to-Intermediate System (IS-IS), and Open Shortest Path First (OSPF) protocols. If you have other protocols configured, such as Address Resolution Protocol (ARP), Bidirectional Forwarding Detection (BFD), Link Layer Discovery Protocol (LLDP), MPLS, Resource Reservation Protocol (RSVP), or Protocol Independent Multicast (PIM), you also should save summary information for these protocols.

    The sample output shows the contents of the saved file: summary information about BGP.

    The sample output shows the contents of the saved file: brief information about the IS-IS adjacencies.

    The sample output shows the contents of the saved file: brief information about the OSPF neighbors.

  11. To check if you have a recent-enough backup copy of your software, file system, and configuration, use the show system snapshot | save filename operational mode command.

    The sample output shows the contents of the saved file: information about the snapshots saved on the system.

    We recommend that if you do not have a snapshot that is the version currently running on the system or one that is recent enough to have the latest configuration for the system, that you back up the currently running software, file system, and configuration. Use the request system snapshot operational mode command, using the instructions at Back Up and Recover Software with Snapshots .

Once you have a snapshot of your system and collected information about the system, you need to validate the configuration image before upgrading or downgrading your software. See Validate the Configuration against the Installation Image.

Related Documentation