The ProxySG probably had SGOS 5.x installed on it at one time, even though it was immediately downgraded and never used. The ProxySG keeps separate SGOS 4.x and SGOS 5.x configurations. If all the SGOS 5.x OSes were removed or replaced from the ProxySG, there is still an SGOS 5.x configuration stored on the ProxySG. So when the ProxySG is upgraded, the SGOS 4.x configuration is not migrated because an existing SGOS 5.x configuration is present on the appliance. NOTE: Currently it is not possible to manage or delete the different profiles (SGOS 5.x profile or SGOS 4.x profile) on the ProxySG. An enhancement request has been entered regarding the ability to delete/manage the various profiles found on a ProxySG. Please contact your Blue Coat Sales Engineer (SE) if you feel this is an important feature request.
If the ProxySG never ran SGOS 5.x on it and it has always run only SGOS 4.x, then when the ProxySG is updated from SGOS 4 to 5, all the policy and configuration will be imported directly into the SGOS 5.x configuration.
Steps to resolve the issue:
- If the ProxySG is unreachable (the old SGOS 5.x configuration has an old IP address and it not reachable), then connect via the serial console and run through the initial configuration of the ProxySG via the command line interface (CLI). Assign IP addresses to the interface, setup enable passwords and so forth.
- Once the ProxySG is configured, enter enable mode.
- In enable mode, type in "restore-sgos4-config" (without quotes).
- You will receive a warning that your SGOS 5.x configuration will be removed and the appliance will be restarted. If you want to accept the command, type "y" (without quotes).
- The unit will reboot and your SGOS 4.x configuration will be updated/migrated into your SGOS 5.x configuration.
Sample CLI output:
Restoring SGOS 4.x configuration requires a restart to take effect.
The current configuration will be lost and the system will be restarted.
Continue with restoring? (y/n)[n]: y
Restoring configuration ...