Blue Coat SGOS 4.x Upgrade Guide
Summary of Changes to the Upgrade Process
•The upgrade path must include a system that shows all possible deprecation warnings, so that these can be corrected in advance of the upgrade, to avoid policy compilation failures after upgrading. Migrating through SGOS 3.2.4 or greater satisfies this requirement.
•If the currently installed policy issued deprecation warnings when compiled, downloads of systems in which that syntax has been abandoned will fail with the error " ". Which error message you see depends on whether you were using the Management Console or the CLI.
From the Management Console:
Policy deprecation warnings exist. Please resolve them prior to upgrading to the next major release of system software
From the CLI:
WARNING: The installed policy contains deprecation warnings. Please fix these warnings prior to upgrading to the next major release, or use load upgrade
This means that you cannot download major version upgrades while policy contains deprecated syntax.
Generally, the deprecation warnings indicate the appropriate corrective action. See "Policy Deprecation" on page 22 for instructions on how to view the deprecation warnings that indicate the syntax to be corrected.
Note: The Visual Policy Manager (VPM) automatically generates
You can force an upgrade while deprecation warnings are present using the CLI command load upgrade
•Any CPL local policy that performs operations such as ALLOW, DENY, Authenticate, or Redirect, or that modifies
Restoring to Previous Versions
When upgrading from the SGOS 3.2.4 or higher release, a copy of the settings is saved prior to any transformations by SGOS 4.x so that the original settings are available if the ProxySG is downgraded to SGOS 3.2.4.
Keep in mind that changes made after upgrade are not preserved on a downgrade. After an upgrade and a downgrade, the state is exactly what it was before the upgrade.
8