Policy missing after the upgrade from 6.X to 7.X

Products

• ProxySG Software - SGOS

Issue/Introduction

After the upgrade from 6.X to 7.X several VPM rules are missing.

Environment

• Migration from 6.X to 7.X

Cause

The SGOS software includes upgrade handlers designed to convert configuration settings between major release upgrades, such as upgrades from 6.x to 7.x. SGOS creates a new configuration file automatically the first time it boots to a new major version and retains a separate configuration file for each major release on the system. When you boot up a major release for which a configuration already exists on the system, the SGOS upgrade handler does not create a new configuration; the existing one is used.

This can create a problem under the following conditions:

1. You upgrade from 6.X to 7.X, but decide to roll back to 6.X
2. You make some changes to the config whilst on 6.X
3. After a while you upgrade to 7.X again
4. As a result, config changes made after the downgrade will not be present when you upgrade for the second time

Resolution

To avoid this issue you can remove the SGOS 7.X config before the upgrade. It will force Edge SWG to migrate the most recent config again.

In version 6.x, log into the CLI and run #remove-sgos7-config command.

Additional Information

More on this here: https://techdocs.broadcom.com/us/en/symantec-security-software/web-and-network-security/edge-swg/7-3/c-determine-upgrade-downgrade-path/t-upgrade-downgrade-steps/c-convert-settings.html