Upgrade and Downgrade Caveats

The following items provide key information about upgrading and downgrading with this software version.

Note:

Upgrading to this Release from releases earlier than S-Cz8.4.0:

The S-Cz8.4.0 release included significant changes that hardened the security posture of the SBC. These changes required your careful evaluation regarding functionality when upgrading to S-Cz8.4.0. These changes are also applicable to customers upgrading from releases prior to S-Cz8.4.0 to this release. Take care to review this information in the S-Cz8.4.0 Release Notes: Upgrade and Downgrade Caveats

SSH Keys

Before upgrading from a pre-8.4 release to this release, delete any imported public keys using the ssh-pub-key delete <key-name> command. Because the commands for SSH key management changed between 8.3 and 8.4, you will not be able to delete old 8.3-type SSH keys using 8.4 (or later) commands. After upgrading, re-import any required public keys. For example, if your ESBC pushes records to an SFTP server, import that server's public key as a known host.

If you're upgrading from 8.4 and you didn't previously import the public keys of your SFTP server, import them as a known-host key. Any public keys imported in 8.4 will be available in 9.0.

See "Manage SSH Keys" in the Configuration Guide.

Acme Packet 3950/4900 Slots

The Acme Packet 3950 and Acme Packet 4900 support:
  • 4 media interfaces: s0p0, s0p1, s0p2, and s0p3
  • 2 10G interfaces: s0p4 and s0p5
  • The optional TDM interface: s2p0

Because there is no slot 1, do not copy over a configuration which contains a phy-interface element that uses slot 1 unless you delete and reconfigure the phy-interfaces.

Encrypting the Surrogate Agent Password

If upgrading from any version prior to S-CZ8.4.0p5, run the spl save acli encr-surrogate-passwords command to save the surrogate-agent passwords in an encrypted format. Later versions do not require this command.

If performing an upgrade from any version prior to S-CZ8.4.0p5 in an HA environment:
  1. Run backup-config on both the active and standby ESBC.
  2. Upgrade the release on the standby ESBC.
  3. Perform a failover so that the standby becomes the active.
  4. Encrypt surrogate-agent passwords on the new active ESBC with the command:
    spl save acli encr-surrogate-passwords
  5. Upgrade the release on the new standby ESBC.

You do not need to run the same spl command on the new standby ESBC because it will sync with the new active ESBC.

Upgrade Version Caveat from Session Delivery Manager

The Session Delivery Manager cannot direct upgrades from SCZ910p6, SCZ900p8 or SCZ900p9 for HA deployments. See Knowledge Document # 2952935.1 for a detailed explanation.