Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation
Table of Contents
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Upgrading Both Devices in a Chassis Cluster Using an ISSU

    For some platforms, devices in a chassis cluster can be upgraded without a service disruption using an in-service software upgrade (ISSU). The chassis cluster ISSU feature allows both devices in a cluster to be upgraded from supported Junos OS versions with a traffic impact similar to that of redundancy group failovers.

    Note: ISSU does not support software downgrades.

    Note: If you upgrade from a Junos OS version that supports only IPv4 to a version that supports both IPv4 and IPv6, the IPv4 traffic will continue to work during the upgrade process. If you upgrade from a Junos OS version that supports both IPv4 and IPv6 to a version that supports both IPv4 and IPv6, both the IPv4 and IPv6 traffic will continue to work during the upgrade process. Junos OS Release 10.2 and later releases support flow-based processing for IPv6 traffic.

    Before you begin, note the following:

    • The ISSUs are available only for Junos OS Release 9.6 and later.
    • Before starting an ISSU, you should fail over all redundancy groups so that they are all active on only one node. See Initiating a Chassis Cluster Manual Redundancy Group Failover.
    • We recommend that graceful restart for routing protocols be enabled before you start an ISSU.

    Once all redundancy groups are active on one node, the upgrade is initiated by using a request command:

    1. Fail over all redundancy groups to one node.
    2. Start the ISSU from the node that is primary for all the redundancy groups by entering the following command:
      user@host> request system software in-service-upgrade image_name reboot

      Note: For SRX1400, SRX3400, SRX3600, SRX5600, and SRX5800 devices you must include reboot in the command. If reboot is not included, the command fails. For SRX100, SRX210, SRX220, SRX240, SRX550, and SRX650 devices, the reboot parameter is not available because the devices in a cluster are automatically rebooted following an in-band cluster upgrade (ICU).

    3. Wait for both nodes to complete the upgrade, then verify that all policies, zones, redundancy groups, and other RTOs return to their correct states. Also verify that both devices in the cluster are running the new Junos OS build.

    Note: During the upgrade, both devices might experience redundancy group failovers, but traffic is not disrupted. Each device validates the package and checks version compatibility before doing the upgrade. If the system finds that the new package is not version compatible with the currently installed version, the device refuses the upgrade or prompts you to take corrective action. Sometimes a single feature is not compatible, in which case the upgrade software prompts you to either abort the upgrade or turn off the feature before doing the upgrade.

    This feature is available only through the command-line interface. See the “request system software in-service-upgrade” section of the Junos OS CLI Reference.

     

    Related Documentation

     

    Published: 2012-06-29

    Previous Page Next Page