Table Of Contents

Content Engine GUI Menu Options

Content Engine GUI Tabs

WCCP Tab and Subtabs

Caching Tab and Subtabs

System Tab and Subtabs

Reporting Tab and Subtabs

Content Engine GUI Menu Options

---

This appendix describes the tabs and subtabs (menu options) that are available from the Content Engine GUI. This is an alternative method that you can use to configure and monitor standalone Content Engines.

This appendix includes the following sections:

•Content Engine GUI Tabs

•WCCP Tab and Subtabs

•Caching Tab and Subtabs

•System Tab and Subtabs

•Reporting Tab and Subtabs

---

Note For information about how to access the Content Engine GUI, see the "Logging in to the Content Engine GUI" section on page 4-55. 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.

---

Content Engine GUI Tabs

Table A-1 describes the four feature tabs and their associated functions.

Table A-1 Content Engine GUI Feature Tabs 

Tab	Description
WCCP	Enables WCCP on the Content Engine and configures WCCP-related parameters and services (for example, configures the Content Engine to support the web cache service).
Caching	Configures cache-related parameters (for example, content preloading) on the Content Engine.
System	Configures system-related parameters (for example, access lists, DNS, and Websense server parameters) on the Content Engine.
Reporting	Displays statistics (for example, disk statistics, performance statistics, and WMT streaming statistics) gathered by the Content Engine. Displays a hardware profile (model number, CPU, memory, disks, SCSI, and NICs) of the Content Engine, and the version of the ACNS software that is currently running on the Content Engine.

WCCP Tab and Subtabs

Table A-2 lists the ACNS 5.3.1 software or later features that can be configured from the WCCP tab and subtabs of the Content Engine GUI.

.

Table A-2 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 WCCP custom web cache service on the Content Engine. When the Content Engine is configured to support this WCCP Version 2 service, it acts as a transparent forward proxy server for HTTP requests that are transparently redirected to it by any of the WCCP-enabled routers on the specified router list. If the requested content is not it its local cache, the Content Engine retrieves it from the origin web server, stores a local copy for future requests, and sends the client the requested content. Subsequent requests for the same content is served from the local cache on the Content Engine.
Reverse Proxy	(For WCCP Version 2 configuration only) Configures the WCCP reverse proxy service on the Content Engine. When the Content Engine is configured to support this WCCP Version 2 service, it acts as a reverse proxy; the Content Engine acts as a proxy on behalf of the origin web server.
RTSP	(For WCCP Version 2 configuration only) Configures the WCCP RTSP media cache service on the Content Engine (a transparent forward proxy server). The Content Engine listens for redirected RTSP requests on the standard RTSP port (default port 554). To configure the Content Engine to listen for intercepted RTSP requests on ports other than the default port (port 554), configure a user-defined WCCP service (services 90-97). If the requested content is not it its local cache, the Content Engine retrieves it from the origin streaming server, stores a local copy for future requests, and sends the client the requested content. Subsequent requests for the same RTSP streaming content is served from the local cache on the Content Engine.
Services	(For WCCP Version 2 configuration only) Configures the Content Engine to cache web traffic using multiple ports, using the user-defined WCCP services (service 90 to 97). To configure these generic WCCP Version 2 services, use this WCCP Services window.
Web Cache	(WCCP Version 1 or Version 2 configuration) Configures the WCCP web-cache service (service 0) on the Content Engine (transparent forward proxy server). This service permits the Content Engine to accept transparently redirected HTTP requests on a single port (port 80). If the requested content is not it its local cache, the Content Engine retrieves it from the origin web server, stores a local copy for future requests, and sends the client the requested content. Subsequent requests for the same web content is served from the local cache on the Content Engine. Only a single WCCP router is supported with WCCP Version 1; multiple routers (router list) are supported with WCCP Version 2. To enable the Content Engine to listen for WCCP intercepted HTTP traffic on ports other than the default port, configure the custom-web-cache service or a user-defined WCCP service (services 90 to 97).
WMT-Streaming	(For WCCP Version 2 configuration only) Configures the WCCP WMT media caching service on the Content Engine (transparent forward proxy server). If the requested content is not it its local cache, the Content Engine retrieves it from the origin streaming server, stores a local copy for future requests, and sends the client the requested content. Subsequent requests for the same WMT streaming content is served from the local cache on the Content Engine.

Caching Tab and Subtabs

Table A-3 lists the ACNS 5.3.1 software or later features that can be configured from the Caching tab and subtab of the Content Engine GUI.

.

Table A-3 Content Engine GUI Caching Subtabs 

Subtab Option	Description
Auth. Cache	Configures cache authentication on the Content Engine. For more information, see the "Configuring Authenticated HTTP Cache Settings" section on page 7-12.
Bypass	(For WCCP Version 2 configuration only) Configures bypass on the Content Engine. For more information, see the "Configuring Bypass Settings on Standalone Content Engines" section on page 15-3.
Cache on Abort	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.
Content Preload	Configures content preloading on the Content Engine. For more information, see the "Configuring Content Preloading for Standalone Content Engines" section on page 11-2.
Customized Error Page	Creates HTTP customized error pages. If you create these customized pages, then the Content Engine displays the appropriate customized error page instead of the default error message when proxy errors occur. For more information, see the "Creating Custom Message Pages for Standalone Content Engines" section on page 5-14.
FTP Freshness	Views or configures FTP object freshness factors for FTP-over-HTTP caching for the Content Engine. For more information, see the "Configuring Nontransparent FTP-over-HTTP Caching on Standalone Content Engines" section on page 7-38.
FTP Proxy	Configures FTP incoming and outgoing proxies for FTP-over-HTTP requests. 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. For more information, see the "Configuring Nontransparent FTP-over-HTTP Caching on Standalone Content Engines" section on page 7-38.
HTTP Freshness	Views or configures freshness factors HTTP objects that are currently cached on the Content Engine. For more information, see the "Configuring HTTP Cache Freshness Settings" section on page 7-9.
HTTP Proxy	Configures HTTP incoming and outgoing proxies for the Content Engine. 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. For more information, see the "Configuring Nontransparent HTTP Forward Proxy Caching on Standalone Content Engines" section on page 7-8.
HTTPS Proxy	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. For more information, see the "Configuring HTTPS Proxy Caching for Standalone Content Engines" section on page 7-25.
ICP Client	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. For more information, see the "Configuring Standalone Content Engines as ICP Clients" section on page 7-73.
ICP Server	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. For more information, see the "Configuring Standalone Content Engines as ICP Servers" section on page 7-74.
LDAP	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. For more information, see the "Configuring the LDAP Authentication Service" section on page 10-21.
Native FTP Proxy	Configures FTP incoming and outgoing proxies for FTP native requests from such FTP clients as Reflection X or WS-FTP clients. For more information, see the "Configuring Nontransparent FTP Native Caching" section on page 7-42.
NTLM	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 hostname of the NTLM server). NTLM authentication will not be performed if no NTLM servers are configured. For more information, see the "Configuring the NTLM Authentication Service" section on page 10-38.
Persist. Connect.	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. For more information, see the "Configuring Standalone Content Engines to Send out TCP Keepalives" section on page 7-67.
Proxy Protocols	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 the specified 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. Real Proxy must be configured properly using the in order to start the Real Proxy. For more information, see the "Configuring RealProxy with the RealSystem Administrator GUI" section on page 8-21.
Transaction Logs	Enables and configures transaction logging. By default, transaction logging is disabled. For more information, see the "Monitoring Transactions with Standalone Content Engines" section on page 21-27.
URL Filtering	Configures URL filtering. For more information, see "Configuring URL Filtering on Standalone Content Engines" section on page 11-11.
WMT-Streaming	Enables WMT and configures WMT streaming parameters. For more information, see the Chapter 9, "Configuring WMT Streaming Media Services on Standalone Content Engines."

System Tab and Subtabs

Table A-4 lists the ACNS 5.3.1 software or later features that can be configured from the System tab and subtabs of the Content Engine GUI.

.

Table A-4 Content Engine GUI System Subtabs 

Subtab Option	Description
Access Lists	Manages group name-based access lists on the Content Engine. In environments in which the Content Engine has been deployed as a standalone caching engine, you can use group-based access lists to control which groups of users can view specific content that is served by the Content Engine. For more information, see the "Configuring the RADIUS Authentication Service" section on page 10-19.
Accounting	Configures authentication, authorization, and accounting (AAA). AAA accounting is the action of keeping track of administrative user activities for system accounting purposes. For more information, see Chapter 18, "Configuring AAA Accounting on Standalone Content Engines."
Authentication	Configures how the Content Engine is to authenticate and authorize administrative users. For more information, see Chapter 17, "Configuring Administrative Login Authentication and Authorization on Standalone Content Engines."
Basic Networking	Adjusts the network settings (the default gateway and the hostname) for the Content Engine.
CDP	Configures the Cisco Discovery Protocol (CDP) for the Content Engine. By default, CDP is enabled on a Content Engine.
DNS	Configures DNS name servers for the Content Engine to use for domain name resolution, and enable DNS caching on the Content Engine. For more information about this topic, see the "Configuring DNS Caching for Standalone Content Engines" section on page 7-62.
File System	Displays information about the currently configured file systems.
NTP	Sets the Content Engine time and date.
Real Subscriber	Displays Real Subscriber activities. Real Subscriber is only supported with Content Engines that are registered with a Content Distribution Manager. Real Subscriber is not supported with standalone Content Engines.
Routing	Adds a new entry to the routing table.
Rules Template	Configures or modifies the Rules Template on the Content Engine. For more information, see Chapter 13, "Configuring the Rules Template on Standalone Content Engines."
SNMP	Configures SNMP on the Content Engine. For more information, see the "Monitoring Standalone Content Engines with SNMP" section on page 21-2.
Syslog	Configures the Content Engine to send varying levels of event messages to a syslog host. For more information, see the "Configuring System Logging on Standalone Content Engines" section on page 21-22.
TACACS+	Configures 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, see the "Understanding TACACS+ Authentication and Authorization" section on page 17-7.
TCP	Changes the default TCP settings on the Content Engine. For more information, see Chapter 20, "Viewing and Modifying TCP Stack Parameters on Standalone Content Engines."
Users	Adds, deletes, or modifies user accounts and privileges. These entries are stored in the local database that resides on the Content Engine. For more information, see Chapter 17, "Configuring Administrative Login Authentication and Authorization on Standalone Content Engines."
Websense Server	Starts or stops the Websense server. Also displays information about the local Websense server. For more information, see the "Configuring Standalone Content Engines for Websense URL Filtering" section on page 11-21.

Reporting Tab and Subtabs

Table A-5 lists the statistics and other information that are accessible from the Reporting tab and subtabs of the Content Engine GUI in ACNS 5.3.1 software or later.

.

Table A-5 Content Engine GUI Reporting Subtabs 

Subtab Option	Description
Disk Stats	Displays general CFS disk statistics for the Content Engine.
Hardware Info	Displays detailed information about the Content Engine hardware components (for example, model number and RAM size).
IMS Stats	Displays If-Modified-Since (IMS) request activity (for example, the total number of requests from clients to the Content Engine).
Java Monitor	Displays the Content Engine resources; displays a graphical depiction of Content Engine utilization.
Performance	Displays performance statistics for the Content Engine.
Requests	Displays statistics on miscellaneous HTTP request data (for example, the number of forced reloads).
Savings	Displays the number of requests that have been served by the Content Engine.
TCP	Displays the amount of requests that have been served by the Content Engine.
Usage	Displays the resource utilization statistics for the Content Engine.
WMT-Streaming	Displays WMT streaming statistics.