Upgrade Information

When you perform a software upgrade, you need to follow the paths presented in these Release Notes and use the same image types to achieve a hitless upgrade. This applies to both HA and non-HA deployments. The paths are presented below.

An example of different image types is upgrading a non-LI deployment with an LI image. Such non-hitless upgrades require that you reboot devices per your upgrade procedure, and then reboot all upgraded devices again to establish the new deployment type.

Supported Upgrade Paths

Always start the upgrade process with the latest patch version of your current release.

The SBC, Enterprise SBC, and Session Router support the following in-service (hitless) upgrade and rollback paths:

• S-Cz9.2.0p13 (or higher) to S-Cz10.1.0
• S-Cz9.3.0p9/S-Cz9.3.0p11 (or higher) to S-Cz10.1.0

  Note:

  S-Cz9.3.0p10 is not a supported upgrade path.
• S-Cz10.0.0p5 (or higher) to S-Cz10.1.0

The SBC, Enterprise SBC, and Session Router support the following out-of-service upgrade and rollback paths:

• S-Cz9.0.0p12 to S-Cz10.1.0
• S-Cz9.1.0p14 to S-Cz10.1.0

The Subscriber-Aware Load Balancer supports the following in-service (hitless) upgrade and rollback paths:

• S-Cz9.3.0p9/S-Cz9.3.0p11 (or higher) to S-Cz10.1.0

  Note:

  S-Cz9.3.0p10 is not a supported upgrade path.
• S-Cz10.0.0p5 to S-Cz10.1.0

Note:

This support pertains to software upgrades of nodes in existing HA clusters. It does not pertain to upgrade scenarios when the hardware is being upgraded, such as scenarios that include an upgrade from Oracle Server X7-2 to Oracle Server X9-2.

When upgrading to this release from a release older than the previous release, read all intermediate Release Notes for notification of incremental changes.