Riverbed Software Licenses, Upgrades, and Image Signing
This chapter describes Riverbed licensing methods, software upgrades, and software image signing.
Customer keys and CLMF licensing do not apply to SCC.
SCC upgrade considerations
Consider these guidelines before upgrading SCC:
• If you’re running SCC 8.6 or earlier, you must perform a multistep upgrade. For example:
8.6.x > (9.0.x or 9.1.x or 9.2.x) > (9.5.x or 9.6.x or 9.7.x or 9.8.x) > 9.9.x > 9.10.x > 9.12.x
• Depending on your migration path, QoS rules might not be automatically applied to the upgraded software. In this case, a QoS migration wizard will assist you in migrating your QoS rules.
• If you mix RiOS software versions in your network, the releases might not fully support certain features (for example, QoS) and you cannot take full advantage of features that are not part of the prior software versions.
• When upgrading large deployments (that is, more than 1000 appliances) be aware that the initial upgrade may take several hours.
You can only directly upgrade the SCC to the next major version or to another minor version within a major version. Do not skip intermediate major versions. Multiversion upgrades and downgrades can result in database incompatibilities, potentially leading to data corruption.
Upon upgrading, clear your browser cache and cookies to ensure that the SCC Management Console displays correctly. Also upon upgrading, make sure none of the processes have exited due to an error. All new and existing processes should run as expected. Some processes are dependent on other processes so they might take time to run at start up.
Earlier version appliances are still connected and the SCC still manages health and alarms for these appliances. The SCC does not support policy pushes for SteelHead EX 2.0 and earlier and SteelHead CXs 8.0 and earlier.