Upgrading to software with FIPS mode
With Riverbed products, you can upgrade an appliance from a software version without FIPS to a software version that includes RCSM and FIPS mode. For upgrades not using FIPS mode, follow the standard software upgrade instructions provided on the Support site at https://support.riverbed.com.
When upgrading software, consider these factors:
• Baseline features are supported between peers with mixed software versions.
• Peers must be running in FIPS mode to ensure reliable application optimization support for encrypted applications.
• Maintain the configuration used with the oldest software version.
• Upgrade both peers to the same version before enabling additional features.
• Upgrade the server-side SteelHead first.
• Data store entries might not be fully compatible between older versions of RiOS.
When upgrading the Client Accelerator Controller, consider these factors:
• Before enabling FIPS on the Client Accelerator Controller, ensure that all client endpoints connecting to the Client Accelerator Controller are upgraded to Mobile Client Software 4.6. After enabling FIPS on the Client Accelerator Controller, the associated endpoints running pre-4.6 Mobile Client software silently ignore package upgrades due to hash mismatches. Therefore, Riverbed recommends that after upgrading the Client Accelerator Controller, allow the Client Accelerator Controller to run in non-FIPS mode until all the endpoints are auto-upgraded by the Client Accelerator Controller.
• In case there are client endpoints that are not auto-upgraded in the previous step, Riverbed recommends that the administrator download the Client Accelerator desktop package from the Client Accelerator Controller and save it to the company infrastructure (for example to a CIFS share). The administrator can then manually distribute the package and upgrade the client endpoints.
• You can sort on version in the endpoint report to verify if all connected client endpoints are upgraded.