Director: Unable to copy policy from an existing proxy to a new proxy Unable to push policy from an existing proxy to a new proxy The existing proxy has content filtering enabled on it The new proxy does not have content filtering installed or enabled on it.
If you are using Content Filtering on one ProxySG appliance, make sure to create the database and download the database on another device before executing an overlay that depends on the database. The policy will fail to load on the second ProxySG if you do not install the content filter database because the policy contains references to filtering categories that the new proxy does not recognize.
Use the following guidelines:
Create a profile for that has minimal configuration; that way, you know the device’s starting configuration but introduce a minimum number of variables to troubleshoot in the event of problems. Because executing a profile first backs up the device, you can restore from backup later in the event of problems.
Create an overlay that downloads the database.
You can do this either using the device’s Management Console or using its command line.
If you use the command line, see the description of the content-filter command and subcommands in Chapter 3, Privileged Mode Configure Commands, in Volume 11: Command Line Interface Reference in the ProxySG Appliance Configuration and Management Guide.
For example, to download the Blue Coat Web Filtering database, use the following commands in the overlay:
content-filter bluecoat download get-now
Create a job that executes the database-loading overlay.
Creating the job is straightforward; however, when you view the job results later, ignore timeouts. Timeout errors when loading a large database are usually harmless. Schedule the job during a time when there is minimal network activity.
For additional details, see the Director Configuration and Management Guide.
Imported Document ID: 000009016
Subscribing will provide email updates when this Article is updated. Login is required.