Filter
Top Products
Chapter 3: Feature-Specific Upgrade Behavior
19
On an upgrade, cached HTTP objects are usable. On a downgrade, cached HTTP objects fetched after
the upgrade are re-fetched.
Documentation References
• Chapter 6, “Configuring Proxies,” in the Blue Coat ProxySG Configuration and Management Guide
• The Blue Coat Content Policy Language Guide
Content Filtering
• Cerberian content filtering has changed its name to Blue Coat Web Filter (BCWF). No upgrade
issues exist. On a downgrade, the vendor
none is selected instead of any unsupported choice.
Note: During the 60-day SGOS trial period, no username or password is required to use Blue
Coat Web Filter. For more information, refer to “Configuring Blue Coat Web Filter” in
Chapter 18 of the Blue Coat ProxySG Configuration and Management Guide.
• Three new content filtering third-party vendors —InterSafe, Optenet, and Webwasher—have been
added in SGOS 4.x. These new vendors cause no upgrade issues. On a downgrade, the vendor
none is selected instead of any unsupported choice.
• The Websense log protocol changed from version 1 to version 3 in SGOS 3.2.x.
Documentation References
Chapter 18, “Content Filtering,” in the Blue Coat ProxySG Configuration and Management Guide
CPU Monitoring
You can enable CPU monitoring whenever you want to see the percentage of CPU being used by
specific functional groups. CPU monitoring is disabled by default.
You can also view CPU monitoring statistics through
Statistics>Advanced>Diagnostics.
CLI Commands
The following commands allow you to enable and manage CPU monitoring:
Documentation References
Appendix E, “Diagnostics,” in the Blue Coat ProxySG Configuration and Management Guide.
Table 3.3: New CLI Commands for CPU Monitor
Command Description
SGOS#(config diagnostics) cpu-monitor
{enable | disable}
Enables or disables the CPU monitor.
SGOS#(config diagnostics) cpu-monitor
interval seconds
Sets the interval between CPU monitoring.
SGOS#(config diagnostics) view cpu-monitor View CPU monitor statistics.