Cisco Cisco Web Security Appliance S360 Fehlerbehebungsanleitung

Contributed by Jakob Dohrmann and Siddharth Rajpathak, Cisco TAC
Engineers.

Jul 31, 2014

What policy changes result in WCCP reset or proxy restarts?

Environment: Cisco Web Security appliance (WSA) running AsyncOS versions 6.x, 7.1, 7.5 and newer

Certain configuration changes on the WSA appliance require a proxy service restart.

On AsyncOS versions 7.1.x and below, any proxy service restart will cause WCCP negotiation to
drop and re−sync as well..

1. 

On AsyncOS versions 7.5.x and above, WCCP negotiation is handled by a different process. Hence a
proxy service restart will not cause WCCP to drop and re−negotiate.

2. 

Additionally on AsyncOS versions 7.5.x and above, while committing changes, WSA will show the below
notification on Web GUI when a configuration change triggers a proxy service restart

−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−− 
In order to process these changes, the proxy process will restart after Commit. This will cause a brief
interruption in service. Additionally, the authentication cache will be cleared, which might require some users
to authenticate again.

−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−

The table below lists some configurations and whether they result in a proxy service restart.

Adding auth realm

 yes

 yes

Deleting auth realm

 yes

 yes

Adding identity policy

 no

 no

Editing identity policy

 no

 no

Deleting identity policy

 no

 no

Enabling HTTPS proxy

 yes

 yes

Disabling HTTPS proxy

 yes

 yes