Configuring a Cisco Content Engine > Cisco Content Engine console or telnet session
|
If you cannot access the Web-based interface, or prefer to use the command-line interface, use the procedure below to configure the Cisco Content Engine.
1.
2. Enter the global configuration mode with the configure command.Console# configure
3. To enable Websense URL filtering, use the url-filter global configuration command.url-filter http websense server {<ip-address>} [port <port-number>] [timeout <seconds>] [connections <number-of-connections>]
The host name or IP address of the machine running Filtering Service. The Filtering Service port you entered during the installation of Websense software. The amount of time (0-240) in seconds that the Content Engine waits for a response from Filtering Service. <number-of-connections> The number of persistent connections (1-250) per CPU. Use this option to configure the number of persistent connections to Filtering Service. The default is 40. Do not change from the default value unless you know for certain that a different value is required.
4. Use the url-filter http websense allowmode enable command to configure the Content Engine to permit requests after a Websense Filtering Service timeout.
5. Use the url-filter http websense enable command to enable Websense software as the current URL filtering scheme for HTTP.
a.
b. Enter write memory.
7. If Websense software is filtering on a cluster of Content Engines, configure each Content Engine as described in steps 1-6.Websense software is ready to filter Internet requests after the Websense Master Database is downloaded and the software is activated within the Cisco Content Engine.See the TRITON - Web Security Help for information about configuring Websense software and downloading the Master Database.
Configuring a Cisco Content Engine > Cisco Content Engine console or telnet session
|