Installing a Software Image and Saving a Software Image Installation Operation

From the Images dialog box, you can install software images that have been imported into the Junos Scope software and downloaded to a device or a group of devices. You can install an image previously downloaded onto a device (supported only for Junos OS images) or use the image directly from the Junos Scope server. In case of dual routing engines systems, you can select the routing engine on which the software image should be installed.

Using Software Manager, the installation process occurs according to the installation options that you select; see Step 3. If you select the Archive Data and Executable Areas (Snapshot) option, Software Manager performs a request system snapshot command before installing the software. If the command fails, the Junos OS is not installed.

Once installation is complete, Software Manager reboots the device and reestablishes connection. Finally, Software Manager verifies that the software running on the device matches the software image installed.

This section covers the following topics:

Installing a Junos OS Image

You can save an install software image operation so that you can combine it with other operations or run it at a later time.

To install a Junos OS image and save an install software image operation, follow these steps:

  1. In the Junos Scope main window, click Software Management > Images.

    The Images dialog box appears.

    Image sw-images-dialog-box.gif
  2. Click the Install link for the Junos OS image that you want to install.

    The Install Image dialog box appears.

    Image s001464.gif
  3. Select the installation option(s) that you want.
    • Use Image Already Downloaded Onto Device—Installs an image that has already been downloaded to the /var/tmp directory of a device.
    • Archive Data And Executable Areas (Snapshot)—(Default) This option is the equivalent of the Junos OS request system snapshot command. The command backs up the currently running and active file system partitions on the router to standby partitions that are not running. Specifically, the root file system (/) is backed up to /altroot, and /config is backed up to /altconfig. The root and /config file systems are on the router’s flash drive, and the /altroot and /altconfig file systems are on the router’s hard drive. After you run the request system snapshot command, you cannot return to the previous version of the software, because the running and backup copies of the software are identical.

      The request system snapshot command can fail on J Series devices when there is no compact flash to back up the system.

    • Load Succeeds If At Least One Statement Is Valid —Activates a partial load and treats parsing errors as warnings instead of errors. Even if some of the statements (but not all) are invalid, the software installation succeeds. This option is the equivalent of using the request system software add <image> best-effort-load CLI command.
    • Remove The Package After Successful Installation—Allows the system to find enough room to upgrade a new software image. Use this option when installing a software image from a local directory on a device that has minimal storage space. This command is equivalent to the request system software add uplink CLI command.
  4. Select the routing engine (R.E.) on which the software image should be installed, from the Select Target RE (in case of Dual RE): list. The options are Current RE, Master RE, and Backup RE. The Current RE option is selected by default.
    • Master—If a Routing Engine is configured as master, it has full functionality. It receives and transmits routing information, builds and maintains routing tables, communicates with interfaces and Packet Forwarding Engine components, and has full control over the chassis. Once a Routing Engine becomes master, it resets the switch plane (SSB, SCB, and SFM) and downloads its current version of the microkernel to the Packet Forwarding Engine components, guaranteeing software compatibility.
    • Backup—If a Routing Engine is configured to be the backup, it does not maintain routing tables or communicate with Packet Forwarding Engine or chassis components. However, it runs through its memory check and boot sequence to the point of displaying a login prompt. A backup Routing Engine supports full management access through the Ethernet, console, and auxiliary ports, and can communicate with the master Routing Engine. Additionally, a backup Routing Engine responds to the Routing Engine request chassis routing-engine master switch command. The backup Routing Engine maintains a connection with the master Routing Engine and monitors the master Routing Engine. If the connection is broken, you can switch mastership by entering the switchover command. If the master Routing Engine is hot-swapped out of the system, the backup takes over control of the system as the new master Routing Engine. Once a Routing Engine becomes master, it resets the switch plane and downloads its own version of the microkernel to the Packet Forwarding Engine components.

    Note: The install operation fails if you select the backup RE option for a single RE device.

  5. Select the Group or Select Device(s) option button.
  6. Select the group or devices that you want from the Group or Select Device(s) list box. Shift+click to select multiple devices from the Select Device(s) drop-down list box.

    Note: When you have selected a Junos image for installation, only Junos devices are listed in the list of devices. If you choose a device group that contains devices that run operating systems other than Junos, the Status page shows “Operation Not Supported” status for such devices.

  7. In the Comment text box, type an optional descriptive comment about the software image installation operation.
  8. Select the Use Junos Scope IP address for image transfer option if you want the device(s)/group to connect to the Junos Scope server using the IP address of the Junos Scope server. The device(s)/group will use the IP address of the Junos Scope server instead of the Junos Scope server name.
  9. Select when you want the software image installation to occur and to save the operation by clicking the appropriate option button:
    • Now—(Default) Performs a software image installation immediately after you confirm it.
    • Save Operation as—Saves the current operation in the Settings > Saved Operations table so you can combine that operation with other Junos Scope operations or run that operation at a later time. Click the Save Operation as option button, then type an operation name in the text box.
    • Select Schedule—Performs a software image installation at the scheduled time interval. Select the Select Schedule option, then select the schedule that you want in the schedule table.
  10. Click Next.
    • If you selected the Now option, the Please Confirm—Install Image dialog box appears.
      Image s001465.gif
    • If you selected the Save Operation as option, the Please Confirm—Save Install Image dialog box appears.
      Image sw-image-install-save-confirm.gif
  11. Confirm that the software image install options that you selected are correct.
  12. Click Finish to confirm the software image install operation that you specified.
    • If you selected the Now option, software image installation occurs immediately.
    • If you selected the Save Operation as option, the operation is saved in the Settings > Saved Operations table. To view the saved operation, click Settings > Saved Operations. For more information about managing saved Junos Scope operations, see Using Task Manager (Saved Operations).
    • If you selected the Select Schedule option, the software image installation occurs when the operation is scheduled to be run.

      When the software image install process is complete, the Status—View Status Records dialog box appears.

      Image s001489.gif

      The Status—View Status Records dialog box lists the software image download operation by operation name, operation type, report name, username, operation status, last updated time, and operation system log message. The Archive operation status can be successful, failed, writing, pending, connecting, or working.

      The Software Manager reboots the device after the software is installed.

      After the device reboots, connection must be reestablished with the device. If connection is not established within a specified time, a “ could not open connection” error message appears in the View Status Records dialog box table.

      If connection is not established with the device it may because of one of the following reasons, and you may have to install the software manually:

      • The request system snapshot command may not work on some devices.
      • There may not be enough available disk space on the device.
      • The newly installed software may not be compatible with the existing configuration.
      • The newly installed software may not be compatible with the Physical Interface Cards (PICs) that are installed on the device.
  13. Click OK.

Installing a BXOS Software Image

The BXOS software installation follows a process that is different from the Junos OS installation.

To install a BXOS software image from Junos Scope, follow these steps:

  1. In the Junos Scope main window, click Software Management > Images.

    The Images dialog box appears.

    Image sw-images-dialog-box.gif
  2. Click the Install link for the software image that you want to install.

    The Install Image dialog box appears.

  3. Choose the protocol, HTTP or HTTPS, for transferring the image from Junos Scope server to the device or device groups on which you want to install the image.
  4. Specify the Installation Options:
    • Create a Snapshot of Primary Image—Check this check box if you want to copy the primary image as the backup before installing the new image. If this option is checked, the backup image on the FLASH memory is replaced with a copy of the primary image.
    • Persist Running Configuration—Check this box if you want to copy the running configuration to the start up configuration before installing the new image. When this option is checked, the running configuration is copied to the start up configuration.
  5. Select the routing engine (R.E.) on which the software image should be installed. The options are Current RE , Master RE, and Backup RE. The Current RE is the default option.
    • Master—If a Routing Engine is configured as master, it has full functionality. It receives and transmits routing information, builds and maintains routing tables, communicates with interfaces and Packet Forwarding Engine components, and has full control over the chassis. Once a Routing Engine becomes master, it resets the switch plane (SSB, SCB, and SFM) and downloads its current version of the microkernel to the Packet Forwarding Engine components, guaranteeing software compatibility.
    • Backup—If a Routing Engine is configured to be the backup, it does not maintain routing tables or communicate with Packet Forwarding Engine or chassis components. However, it runs through its memory check and boot sequence to the point of displaying a login prompt. A backup Routing Engine supports full management access through the Ethernet, console, and auxiliary ports, and can communicate with the master Routing Engine. Additionally, a backup Routing Engine responds to the Routing Engine request chassis routing-engine master switch command. The backup Routing Engine maintains a connection with the master Routing Engine and monitors the master Routing Engine. If the connection is broken, you can switch mastership by entering the switchover command. If the master Routing Engine is hot-swapped out of the system, the backup takes over control of the system as the new master Routing Engine. Once a Routing Engine becomes master, it resets the switch plane and downloads its own version of the microkernel to the Packet Forwarding Engine components.

    Note: BXOS devices are single RE machines. If you select any RE other than the Current RE option, the operation will fail.

  6. Select the Group or Select Device(s) option button.
  7. Select the group or devices that you want from the Group or Select Device(s) list box. Shift+click to select multiple devices from the Select Device(s) drop-down list box.

    Note: When you have selected a BXOS image for installation, only BXOS devices are listed in the list of devices. If you choose a device groups that contains devices that run operating systems other than BXOS, the status page shows “Operation Not Supported” as the status for such devices.

  8. In the Comment text box, type an optional descriptive comment about the software image installation operation.
  9. Select when you want the software image installation to occur and to save the operation by clicking the appropriate option button:
    • Now—(Default) Performs a software image installation immediately after you confirm it.
    • Save Operation as—Saves the current operation in the Settings > Saved Operations table so you can combine that operation with other Junos Scope operations or run that operation at a later time. Click the Save Operation as option button, then type an operation name in the text box.
    • Select Schedule—Performs a software image installation at the scheduled time interval. Select the Select Schedule option, then select the schedule that you want in the schedule table.
  10. Click Next.
    • If you selected the Now option, the Please Confirm—Install Image dialog box appears.
    • If you selected the Save Operation as option, the Please Confirm—Save Install Image dialog box appears.
  11. Confirm that the software image install options that you selected are correct.
  12. Click Finish to confirm the software image install operation that you specified.
    • If you selected the Now option, software image installation occurs immediately.
    • If you selected the Save Operation as option, the operation is saved in the Settings > Saved Operations table. To view the saved operation, click Settings > Saved Operations. For more information about managing saved Junos Scope operations, see Using Task Manager (Saved Operations).
    • If you selected the Select Schedule option, the software image installation occurs when the operation is scheduled to be run.

      When the software image install process is complete, the Status—View Status Records dialog box appears.

      Image s001489.gif

      The Status—View Status Records dialog box lists the software image download operation by operation name, operation type, report name, username, operation status, last updated time, and operation system log message. The Archive operation status can be successful, failed, writing, pending, connecting, or working.

      The Software Manager reboots the device after the software is installed.

      After the device reboots, connection must be reestablished with the device. If connection is not established within a specified time, a “ could not open connection” error message appears in the View Status Records dialog box table.

      If connection is not established with the device it may because of one of the following reasons, and you may have to install the software manually:

      • The request system snapshot command may not work on some devices.
      • There may not be enough available disk space on the device.
      • The newly installed software may not be compatible with the existing configuration.
      • The newly installed software may not be compatible with the Physical Interface Cards (PICs) that are installed on the device.
  13. Click OK.