This appendix describes the tabs and subtabs (menu options), which are available from the Content Engine GUI. This appendix includes the following sections:
Note For information about how to access the Content Engine GUI, see the "Accessing the Content Engine GUI" section. The Content Engine GUI has context-sensitive help that can be accessed by clicking the Help button at the bottom of the Content Engine GUI window.
WCCP Tab and Subtabs
Table A-1 lists the ACNS 5.1 software features that can be configured from the WCCP tab and subtabs of the Content Engine GUI.
.
Table A-1 Content Engine GUI WCCP Subtabs
Subtab Option
Description
Enable WCCP
Enables WCCP on the Content Engine. Use to enable WCCP Version 1 or WCCP Version 2 on the Content Engine.
Clustering
Sets parameters related to WCCP service clusters.
Custom Web Cache
(For WCCP Version 2 configuration only)
Configures the Content Engine to cache custom web traffic.
Reverse Proxy
(For WCCP Version 2 configuration only)
Configures the reverse proxy service on the Content Engine. When the Content Engine is configured to support this WCCP service, it acts as a reverse proxy; the Content Engine acts as a proxy on behalf of the origin web server.
This WCCP service is only available when WCCP Version 2 is enabled.
RTSP
(For WCCP Version 2 configuration only)
Configures the Content Engine to cache RTSP traffic.
Services
(For WCCP Version 2 configuration only)
To configure the Content Engine to cache web traffic using multiple ports, use WCCP Version 2 services 90 to 97. To configure these generic WCCP Version 2 services, use this WCCP Services page.
Web Cache
(For WCCP Version 2 configuration only)
Configures the Content Engine to cache standard web traffic.
WMT-Streaming
(For WCCP Version 2 configuration only)
Configures WMT streaming caching service on the Content Engine. When the Content Engine is configured to support this WCCP service, the Content Engine is configured to cache WMT streaming traffic.
Caching Tab and Subtabs
Table A-2 lists the ACNS 5.1 software features that can be configured from the Caching tab and subtab of the Content Engine GUI.
•Load bypass—If a Content Engine becomes overwhelmed with traffic, it can use the load bypass feature to re-route overload traffic back out to the Internet. The Content Engine can only bypass WCCP-redirected traffic, it can bypass proxy-style requests.
•Authentication bypass.—Some websites, due to IP authentication, may not allow the Content Engine to connect directly on behalf of the web client. In order to avoid a disruption of service, the Content Engine can use the authentication bypass feature to generate a dynamic access list for these client-server pairs. Authentication bypass triggers are also propagated upstream and downstream in the case of hierarchical caching.
Configures cache-on-abort features on the Content Engine. Determines the policy for object caching that the Content Engine should use if the web client aborts the download process.
If this option is enabled, the Content Engine uses a selective algorithm to determine whether to continue to cache an object if the web client has aborted the download. If disabled, the Content Engine will always continue to download an object to the cache even if a web client has aborted the download.
View or configure FTP object freshness factors for the Content Engine. For more information about this topic, see the "Setting FTP Cache Freshness" section.
FTP Proxy
Configures FTP incoming and outgoing proxies. Proxy mode enables the Content Engine to operate in environments where WCCP is not enabled, or where client browsers have previously been configured to use a legacy FTP proxy server. DNS must be configured in order to support incoming FTP proxy requests.
Configures HTTP incoming and outgoing proxies. Proxy mode enables the Content Engine to operate in environments where Cisco's WCCP is not enabled, or where client browsers have previously been configured to use a legacy proxy server. DNS must be configured in order to support incoming HTTP proxy requests.
Configures HTTPS incoming and outgoing proxies. HTTPS proxy mode enables the Content Engine to service HTTPS requests sent by web clients that are configured to use an HTTPS proxy server. DNS must be configured in order to support incoming HTTPS proxy requests.
Configures a Content Engine cluster to generate ICP queries before retrieving the requested objects from the Internet. For example, specify how long the Content Engine should wait before retrieving the needed data directly from the Internet. By default, the Content Engine waits for 2 seconds; however, you can change this default. The range is 1 to 30 seconds.
Configures a Content Engine to act as an ICP server. Specify whether the Content Engine is the parent server or sibling server for the designated ICP client. If the Content Engine is the parent ICP server and cannot satisfy the ICP client's request, it forwards the request to another server on the Internet. If the Content Engine is a sibling ICP server and cannot satisfy the ICP client's request, it will send a failed response back to the ICP client.
Configures the Content Engine to use an LDAP server for authentication purposes. To enable the Content Engine to use a specific LDAP server, enter the IP address of the LDAP server, and the port number that the LDAP server will be listening on. The default LDAP port number is 389. LDAP authentication is not performed if no LDAP servers are configured.
Configures the Content Engine to use an NTLM server for authentication purposes. To enable the Content Engine to use a specific NTLM server, enter the host information. For example, specify the domain name (the domain name in which the user should be authenticated) and the domain server (the IP address or host name of the NTLM server). NTLM authentication will not be performed if no NTLM servers are configured.
Configures persistent connections on the Content Engine. Persistent connections can be set for client-only, server-only, and all connections on the Content Engine.
If the Strip NTLM Authentication headers option is turned off in the Content Engine, the NTLM authentication headers will be sent to the client. The Content Engine will not support NTLM authentication if persistent connections for all is turned off.
Configures proxy protocols for the Content Engine. The default behavior is that the Content Engine will retrieve the objects from the origin web server itself, or, if configured to use an outgoing proxy for this protocol, will forward the request to its outgoing proxy.
RADIUS
Configures the Content Engine to use a remote RADIUS server for authentication purposes. Configure the network parameters required to access the remote RADIUS database.
RealProxy
Enables the RealProxy GUI Administration page. Note that Real Proxy must be configured properly using the ACLI in order to start the Real Proxy.
Enable and configure transaction logging. By default, transaction logging is disabled. For more information about transaction logs, see the "Transaction Logging" section.
Table A-3 lists the ACNS 5.1 software features that can be configured from theSystem tab and subtabs of the Content Engine GUI.
.
Table A-3 Content Engine GUI System Subtabs
Subtab Option
Description
Access Lists
Manage group name-based access lists on the Content Engine. In environments in which the Content Engine has been deployed as a standalone caching engine, the ACNS system administrator can use group-based access lists to control which groups of users can view specific content that is served by the Content Engine.
Configure the Content Engine to use a TACACS+ server for authentication and authorization. Configure the network parameters required to access the remote TACACS+ database. For more information on this topic, see the "Understanding TACACS+ Authentication and Authorization" section.
Add, delete, or modify user accounts and privileges. These entries are stored in the local database that resides on the Content Engine. For more information about this topic, see the "Managing User Accounts" section.
Websense Server
Use to start or stop the Websense server, and to view information about the local Websense server. For more information on this topic, see the "URL Filtering with the Websense Server" section.
Reporting Tab and Subtabs
Table A-4 lists the statistics and other information that are accessible from the Reporting tab and subtabs of the Content Engine GUI.
.
Table A-4 Content Engine GUI Reporting Subtabs
Subtab Option
Description
Disk Stats
View general CFS disk statistics for the Content Engine.
Hardware Info
View detailed information about the Content Engine hardware components (for example, model number and RAM size).
IMS Stats
View If-Modified-Since (IMS) request activity (for example, the total number of requests from clients to the Content Engine).
Java Monitor
Monitor the Content Engine resources; obtain a graphical depiction of Content Engine utilization.
Performance
View performance statistics for the Content Engine.
Request
View statistics on miscellaneous HTTP request data (for example, the number of forced reloads).
Savings
View the number of requests that have been served by the Content Engine.
TCP
View the amount of requests that have been served by the Content Engine.
Usage
View the resource utilization statistics for the Content Engine.