Cisco ACNS Software Configuration Guide for Locally Managed Deployments, Release 5.2 - Chapter 3: Getting Started [Cisco Application and Content Networking System (ACNS) Software]

Table Of Contents

Getting Started

Overview of Configuring, Monitoring, and Troubleshooting Standalone Content Engines

Flowcharts of Configuring, Monitoring, and Troubleshooting Standalone Content Engines

Checklist for Configuring, Monitoring, and Troubleshooting Standalone Content Engines

Configuring a Basic Configuration on Standalone Content Engines with the Setup Utility

Commonly Used Caching Services Configurable Through the Setup Utility

Using the Setup Utility

Setup Utility Menu Options and Corresponding CLI Commands

Setup Utility Arrows and Keys

Deciding the Addressing Scheme for Standalone Content Engines

About Device Network Settings for Standalone Content Engines

Using the CLI Command Method to Configure General Settings for Standalone Content Engines

Launching the Setup Utility

Manually Launching the Setup Utility

Automatically Launching the Setup Utility

Using the Setup Utility to Configure a Basic Configuration on a Standalone Content Engine

Configuring Client Browsers and Media Players for Direct Proxy Routing

Pointing Client Browsers Directly to a Standalone Content Engine

Using PAC Files to Point Client Browsers Directly to a Standalone Content Engine

Manually Pointing Client Browsers to a Standalone Content Engine

Pointing Windows Media Players Directly to a Standalone Content Engine

Pointing RealMedia Players Directly to a Standalone Content Engine

Configuring WCCP Routers for Transparent Redirection

Verifying the Basic Configuration

Modifying the Basic Configuration Through the Setup Utility

Performing Other Basic Tasks

Logging in to Standalone Content Engines

Using Telnet or a Console Session to Log in to a Standalone Content Engine

Using Secure Shell Version 1 or Version 2 to Log in to a Standalone Content Engine

Using the Content Engine GUI to Log in to a Standalone Content Engine

Enabling or Disabling Access to the Content Engine GUI

Logging in to the Content Engine GUI

Logging out of the Content Engine GUI

Setting the System Clock

Managing Administrative Login Accounts

Adding or Modifying Administrative Login Accounts

Configuring Content Preloading for Standalone Content Engines

Creating a Preload URL List File

Enabling and Configuring Content Preloading on Standalone Content Engines

Stopping or Resuming Content Preloading on Standalone Content Engines

Saving the Current Configuration on Standalone Content Engines

Disabling Transparent Caching Services on Standalone Content Engines

Shutting Down Standalone Content Engines

Shutting Down Standalone Content Engines from the Command Line

Shutting Down and Rebooting Standalone Content Engines from the Content Engine GUI

Removing or Replacing a Content Engine

Getting Started

This chapter provides an overview of how to configure, monitor, and troubleshoot standalone Content Engines that are running ACNS software, Release 5.2 or later. It also describes how to use the ACNS software Setup utility to configure the general settings (device network settings and disk configuration) and a set of commonly used caching services (listed in Table 3-2) on a standalone Content Engine.

This chapter contains the following sections:

•Overview of Configuring, Monitoring, and Troubleshooting Standalone Content Engines

•Configuring a Basic Configuration on Standalone Content Engines with the Setup Utility

•Configuring Client Browsers and Media Players for Direct Proxy Routing

•Configuring WCCP Routers for Transparent Redirection

•Verifying the Basic Configuration

•Modifying the Basic Configuration Through the Setup Utility

•Performing Other Basic Tasks

The term "standalone Content Engines" is used throughout this guide to refer to Content Engines that ACNS administrators have intentionally not registered with the Content Distribution Manager so that they can configure, manage, and monitor these Content Engines as standalone devices. Multiple standalone Content Engines can be deployed (for example, you can deploy clusters of standalone Content Engines).

Note For complete syntax and usage information for the CLI commands used in this chapter, refer to the Cisco ACNS Software Command Reference, Release 5.2 publication. For information about how to configure Content Engines that are registered with a Content Distribution Manager, refer to the Cisco ACNS Software Configuration Guide for Centrally Managed Deployments, Release 5.2.

Overview of Configuring, Monitoring, and Troubleshooting Standalone Content Engines

This section provides an overview of how to configure, monitor, and troubleshoot standalone Content Engines as caching and streaming engines, and contains the following sections:

•Flowcharts of Configuring, Monitoring, and Troubleshooting Standalone Content Engines

•Checklist for Configuring, Monitoring, and Troubleshooting Standalone Content Engines

Flowcharts of Configuring, Monitoring, and Troubleshooting Standalone Content Engines

Figure 3-1 shows a high-level view of a typical workflow for configuring, monitoring, and troubleshooting a standalone Content Engine. Table 3-1 provides a checklist of tasks for completing the workflow that is shown in Figure 3-1.

Note As Figure 3-1 indicates, more detailed flowcharts are provided for configuring conventional caching services (Figure 3-2), WMT streaming and caching services (Figure 3-3 and Figure 3-4), and RTSP streaming and caching services (Figure 3-5).

Figure 3-1 High-Level View of Configuring, Monitoring, and Troubleshooting Standalone Content Engines

Figure 3-2 Detailed View of Configuring Conventional Caching Services for Standalone Content Engines

This chapter describes how to use the Setup utility to configure the following three commonly used conventional caching services on standalone Content Engines: HTTP reverse proxy caching, HTTP transparent caching using WCCP Version 2, and HTTP forward proxy caching. For information about how to use the Content Engine CLI method (instead of the Setup utility) to configure these three services as well as other conventional caching services (for example, DNS caching and FTP caching), see "Configuring Conventional Caching Services for Standalone Content Engines."

Figure 3-3 Detailed View of Configuring WMT Streaming and Caching Services for Standalone Content Engines (Part 1)

Figure 3-4 Detailed View of Configuring WMT Streaming and Caching Services for Standalone Content Engines (Part 2)

This chapter describes how to use the Setup utility to configure the following two commonly used WMT caching services on standalone Content Engines: WMT transparent caching and WMT proxy caching. For information about how to use the Content Engine CLI (instead of the Setup utility) to configure these caching services or other WMT services (for example, WMT streaming) on a standalone Content Engine, see "Configuring WMT Streaming Media Services on Standalone Content Engines."

Figure 3-5 Detailed View of Configuring RTSP Streaming and Caching Services for Standalone Content Engines

This chapter describes how to use the Setup utility to configure the following two commonly used RTSP caching services on standalone Content Engines: RealMedia transparent caching and RealMedia proxy caching. For information about how to use the Content Engine CLI (instead of the Setup utility) to configure these caching services or other RTSP services (for example, RealProxy live splitting) on standalone Content Engines, see "Configuring RTSP Media Services on Standalone Content Engines."

Checklist for Configuring, Monitoring, and Troubleshooting Standalone Content Engines

Table 3-1 is a checklist of tasks for configuring, monitoring, and troubleshooting standalone Content Engines that are running ACNS software, Release 5.2 or later.

Table 3-1 Checklist for Configuring, Monitoring, and Troubleshooting Standalone Content Engines

Task

Additional Information and Instructions

Start basic configuration

1. Decide which addressing scheme will be
used to initially configure this standalone
Content Engine.

The two supported addressing schemes are mutually exclusive:

•Manually specify a static IP address and network mask

•Dynamically assign an IP address using the interface-level DHCP addressing scheme

See the "Deciding the Addressing Scheme for Standalone Content Engines" section.

2. Decide which method will be used
to configure this standalone
Content Engine.

–Setup utility

–CLI command

This chapter describes how to use the Setup utility to expedite the basic configuration of standalone Content Engines. See the "Using the Setup Utility to Configure a Basic Configuration on a Standalone Content Engine" section.

A brief description of how to use the CLI method to configure general settings is provided in the "Using the CLI Command Method to Configure General Settings for Standalone Content Engines" section. For detailed information about the CLI commands used to configure general settings, refer to the Cisco ACNS Software Command Reference, Release 5.2 publication.

For information about how to use the CLI method to configure or modify one or more commonly used caching services and numerous other services (for example, DNS caching, FTP caching, WMT streaming, and RTSP streaming) running on standalone Content Engines, see the following chapters in this guide:

•"Configuring Conventional Caching Services for Standalone Content Engines"

•"Configuring WMT Streaming Media Services on Standalone Content Engines"

•"Configuring RTSP Media Services on Standalone Content Engines"

3. Power up this Content Engine and open
a console connection on one of its
serial ports.

After you physically install the hardware and power up the Content Engine, you can access the ACNS software (Setup utility or CLI commands) to perform a basic configuration of this standalone (unregistered) Content Engine (instead of a Content Engine that will be registered with a Content Distribution Manager).

4. Use the Setup utility or CLI commands
to configure the following general
settings on this standalone
Content Engine:

–Device network settings

–Disk configuration

To use the Setup utility to configure the general settings, see the "Using the Setup Utility to Configure a Basic Configuration on a Standalone Content Engine" section.

To use the CLI command method to configure the general settings, see the "Using the CLI Command Method to Configure General Settings for Standalone Content Engines" section.

5. Choose which services will be deployed
on this standalone Content Engine.

–Conventional caching services (DNS, HTTP, FTP, and HTTPS caching)

–WMT streaming and caching services

–RTSP streaming and caching services

See the "Overview of Configuring Conventional Caching Services" section.

See the "Configuring WMT Streaming and Caching Services for Standalone Content Engines" section.

See the "Configuring RealProxy Streaming and Caching Services for Standalone Content Engines" section.

6. Configure one or more of the following
routing methods to direct content requests
to this standalone Content Engine:

–Direct proxy routing
(nontransparent)

–Transparent redirection (WCCP
routing or Layer 4 switching)

For direct proxy routing, see the "Configuring Client Browsers and Media Players for Direct Proxy Routing" section.

For WCCP routing, see the "Configuring WCCP Services on a Router" section.

For Layer 4 switching, see the "Configuring Layer 4 Switching as a Redirection Method" section.

7. If direct proxy routing is to be used, is a
*.pac file to be used?

•If no, then manually configure each client browser to point directly to the standalone Content Engine as a direct proxy server, as described in the "Manually Pointing Client Browsers to a Standalone Content Engine" section.

•If yes, then configure the standalone Content Engine and the client browsers to use a proxy autoconfiguration (PAC) file, as described in the "Using PAC Files to Point Client Browsers Directly to a Standalone Content Engine" section.

8. Configure the chosen caching and
streaming services on this standalone
Content Engine.

The Setup utility allows you to configure a set of commonly used caching services (listed in Table 3-2) on a standalone Content Engine. We recommend that you use this utility to configure one or more of these caching services on your Content Engine. This allows you to get your Content Engine up and running a basic set of caching services. For more information, see the "Using the Setup Utility to Configure a Basic Configuration on a Standalone Content Engine" section.

9. Verify the basic configuration.

Now that the basic configuration is completed, verify that these caching services are working properly. See the "Verifying the Basic Configuration" section.

10. You can now do any of the following
tasks:

–Configure content services.

–Perform advanced configuration
on this Content Engine.

–Monitor and troubleshoot.

See tasks 11 through 23 below in this table.

Configure content services (optional)

After configuring caching and streaming services on the standalone Content Engine, you can configure such content services as access control, URL filtering, ICAP, and rules.

11. Decide if end user access to the Internet
is to be controlled (access control for
HTTP, HTTPS, and FTP-over-HTTP
requests).

•If no, then go to task 12.

•If yes, then configure authentication and authorization, as described in "Configuring Content Authentication and Authorization on Standalone Content Engines."

12. Decide if URL filtering is to be used.

•If no, then go to task 13.

•If yes, then configure URL filtering for HTTP, HTTPS, and FTP requests, as described in "Configuring URL Filtering on Standalone Content Engines."

13. Determine whether there is an
external ICAP server.

•If no, then go to task 14.

•If yes, then configure the Internet Content Adaptation Protocol (ICAP) for HTTP and FTP-over-HTTP requests, as described in "Configuring ICAP on Standalone Content Engines."

14. Determine if there are any special
requirements for processing
content requests.

•If no, then go to task 15.

•If yes, configure rules for HTTP, HTTPS, FTP-over-HTTP, WMT, and RTSP requests, as described in "Configuring the Rules Template on Standalone Content Engines."

Perform advanced configuration tasks (optional)

15. Configure advanced transparent caching
features (for example, traffic bypass,
overload bypass, flow protection, and
IP spoofing).

"Configuring Advanced Transparent Caching Features on Standalone Content Engines"

16. Set up additional network interfaces on
the standalone Content Engine.

"Configuring Additional Network Interfaces and Bandwidth on Standalone Content Engines"

17. Configure bandwidth for interfaces and
content services on this standalone
Content Engine.

"Configuring Additional Network Interfaces and Bandwidth on Standalone Content Engines"

18. Set up login authentication and
authorization on this standalone
Content Engine.

"Configuring Administrative Login Authentication and Authorization on Standalone Content Engines"

19. Configure this standalone
Content Engine for system accounting
with TACACS+.

"Configuring AAA Accounting on Standalone Content Engines"

20. Configure IP access control lists (ACLs)
on this standalone Content Engine.

"Creating and Managing IP Access Control Lists for Standalone Content Engines"

21. View or modify TCP stack parameters
for this standalone Content Engine.

"Viewing and Modifying TCP Stack Parameters on Standalone Content Engines"

22. View or modify the system logging
settings for this standalone
Content Engine.

See the "Using the System Logging Feature" section.

Monitor and troubleshoot

23. Monitor this standalone Content Engine
with SNMP or ACNS software alarms.

"Monitoring and Troubleshooting"

24. Use ACNS software logs and traceroute
for troubleshooting.

"Monitoring and Troubleshooting"

Configuring a Basic Configuration on Standalone Content Engines with the Setup Utility

This section provides an overview of the Setup utility and describes how to use this tool to configure a basic configuration on a standalone Content Engine in either of the situations:

•Case 1—The Content Engine is being booted up for the first time (for example, the Content Engine was purchased with ACNS 5.2 software), and you want to use the Setup utility to configure the basic configuration settings (the general settings [device network settings and disk configuration], and a set of commonly used caching services [listed in Table 3-2]).

•Case 2—The device is a standalone Content Engine with some basic configuration (for example, the Content Engine was upgraded to ACNS 5.2 software, and already has device network settings, disk configuration, and HTTP proxy caching configured). You want to use the Setup utility to complete the basic configuration of this standalone Content Engine (for example, configure some of the other commonly used caching services that are not yet configured).

In Case 1, the Setup utility is automatically launched when you initially boot up a device. Completing the initial basic configuration in this situation involves these tasks:

•Deciding the Addressing Scheme for Standalone Content Engines

•Using the Setup Utility to Configure a Basic Configuration on a Standalone Content Engine.

In Case 2, you manually launch the Setup utility with the setup privileged EXEC command. For more information on this topic, see the "Manually Launching the Setup Utility" section.

After completing this basic configuration, you must configure the client browsers and media players (see "Configuring Client Browsers and Media Players for Direct Proxy Routing") for direct proxy routing, and configure the WCCP routers for transparent redirection ("Configuring WCCP Routers for Transparent Redirection"). After verifying that this basic configuration is working properly, you can use the CLI commands or Content Engine GUI to configure additional caching services (for example, DNS caching, FTP caching, and HTTPS caching), streaming services (WMT streaming and RTSP streaming), or content services. You can also perform advanced configuration or monitor this Content Engine.

Note Throughout the rest of this chapter the term "WCCP Version 2-enabled router" denotes a router that is running WCCP Version 2.

Commonly Used Caching Services Configurable Through the Setup Utility

Table 3-2 lists the commonly used caching services that you can quickly configure on a standalone Content Engine through the Setup utility.

Table 3-2 Commonly Used Caching Services Configurable Through the Setup Utility

Caching Service

Description

HTTP forward
proxy caching

The standalone Content Engine functions as a nontransparent forward proxy server for HTTP requests. After receiving an HTTP request directly from a client browser, the Content Engine retrieves and caches the requested content if it is not already stored in its local cache, and sends the requested content to the requester (client browser).

HTTP transparent
caching

The standalone Content Engine functions as a transparent proxy server for HTTP requests. After receiving a redirected HTTP request, the Content Engine retrieves and caches the requested content if it is not already stored in its local cache, and sends the requested content to the requester (client browser). With the Setup utility, you can configure the Content Engine to accept redirected HTTP requests from a WCCP Version 2-enabled router. With the Content Engine CLI, you can configure the Content Engine to accept redirected HTTP requests from the WCCP Version 2-enabled router or a Layer 4 switch.

HTTP reverse proxy
caching

The standalone Content Engine functions as a transparent proxy server for specific web servers (for example, web servers in a web server farm) as opposed to acting as a proxy for end users (web clients). After receiving a redirected reverse proxy request, the Content Engine retrieves and caches the requested content if it is not already stored in its local cache, and sends the requested content to the requester (client browser). With the Setup utility, you can configure the Content Engine to accept redirected reverse proxy requests from a WCCP Version 2-enabled router. With the Content Engine CLI, you can configure the Content Engine to accept redirected reverse proxy requests from a WCCP Version 2-enabled router or a Layer 4 switch.

WMT proxy caching

The standalone Content Engine functions as a nontransparent proxy server for end users who are using Windows Media Player to request WMT content. After receiving a WMT request directly from a client Windows Media Player, the Content Engine retrieves the requested content if it is not already stored in its local cache, stores a copy locally whenever possible, and sends the requested content to the requester (client Windows Media Player).

WMT transparent
caching

The standalone Content Engine functions as a transparent proxy server for end users who are using Windows Media Player to request content. After receiving a transparently redirected WMT request, the Content Engine retrieves the requested content if it is not already stored in its local cache, stores a copy locally whenever possible, and sends the requested content to the requester (client Windows Media Player). With the Setup utility, you can configure the Content Engine to accept redirected WMT requests from a WCCP Version 2-enabled router. With the Content Engine CLI, you can configure the Content Engine to accept redirected WMT requests from a WCCP Version 2-enabled router or a Layer 4 switch.

RealMedia proxy
caching

The standalone Content Engine functions as a nontransparent proxy server for end users who are using a RealMedia player to request RTSP content. After receiving an RTSP request directly from a RealMedia player (for example, RealPlayer), the Content Engine retrieves the requested content if it is not already stored in its local cache, stores a copy locally whenever possible, and sends the requested content to the requester (the RealMedia player).

RealMedia transparent
caching

The standalone Content Engine functions as a transparent proxy server for end users who are using a RealMedia player to request content. After receiving a redirected RTSP request, the Content Engine retrieves requested content, stores a copy locally whenever possible, and sends requested content to the requester (the RealMedia player). With the Setup utility, you can configure the Content Engine to accept redirected RTSP requests from a WCCP Version 2-enabled router. With the Content Engine CLI, you can configure the Content Engine to accept redirected RTSP requests from a WCCP Version 2-enabled router or a Layer 4 switch.

Using the Setup Utility

The following are some important points when using the Setup utility:

•When the Setup utility is invoked on a Content Engine that supports device mode changes (for example, the CE-565 or the CE-7306), you are prompted to specify the device mode for that particular device. When prompted, press Enter or enter CE to specify the Content Engine device mode for this standalone Content Engine.
What is the mode of the device (CE/CR/CDM/PM) [CE]: CE
When prompted, enter no to specify that this Content Engine is not going to be managed by a Content Distribution Manager.
Is this CE going to be managed by a CDM (Content Distribution Manager)  
(y/n) [y]: no
•When a series of basic configuration questions appears, press Enter or enter y to indicate that you want to configure a particular caching service on this standalone Content Engine. (See Table 3-2 for a description of these services).

•After you respond to the series of basic configuration questions, a menu-based interface appears (see below). For a list of the Setup utility menu options, see Table 3-3.
           +-----------------------------------------------------+
           ¦                      Main Menu                      ¦
           +-----------------------------------------------------¦
           ¦	 -General Settings               :Incomplete	    ¦
           ¦    Caching Related Configurations :Incomplete       ¦
           ¦    Print Configuration                              ¦
           ¦    Exit (e)                                         ¦
           +-----------------------------------------------------+
           Main Menu
	Configure network settings, disks, etc
	Press '?' to see why this item is incomplete
•When you are prompted for a particular configuration setting, the default value is displayed. Press Enter to select the default value. For example, press Enter to specify that you want to use the default WCCP router (default gateway that has the IP address of 10.0.1.1) when prompted as follows:
Please enter the IP addresses of WCCP routers [10.0.1.1]:
•After you specify whether you want to configure a particular setting, the corresponding menu option is marked as "Complete" or "Incomplete." This helps you track which basic configuration settings you have configured and which ones still need to be configured on this standalone Content Engine.

•When you configure a particular setting by choosing a menu option in the Setup utility, the corresponding CLI command is configured. (See Table 3-3.) After you use the Setup utility to specify a specific basic configuration setting, a list of configured CLI commands appears (see below). When you are asked if you want to save this configuration, press Enter to save the displayed configuration.
NOTE: Please remember to configure web-cache service on the router.
Based on the input, the following CLIs will be configured:
       wccp router-list 1 10.0.1.1
       wccp version 2
       wccp web-cache router-list 1
Do you accept these configs (y/n) [y]:
•To display a list of constructed CLI commands at any time during a Setup utility session, choose the Print Configurations option from the Setup utility menu.

•After you specify a configuration setting, the Setup utility reports any dependencies or incompatibility between the specified options. For example, if you have enabled any of the streaming caching services, then you are informed that you should allocate disk space for the mediafs when you configure the disk.

•If any failure occurs when the Setup utility is applying the specified configuration settings (for example, the disk configurations and the corresponding CLI command), the Setup utility displays a message indicating which specific setting could not be applied. Error messages are also written to /local1/errorlog/setup_(clildisk)_config_error.

•A basic configuration (see below) is constructed based on the information that you specify through the Setup utility. The following is an example of a basic configuration for a standalone Content Engine that has all seven of the commonly used caching services configured:
Here is the current profile of this device
CDN device                    : No
HTTP Proxy Caching            : Yes
HTTP Tranparent Caching       : Yes
HTTP Reverse Proxy Caching    : Yes
WMT Proxy Caching             : Yes
WMT Transparent Caching       : Yes
Real Media Proxy Caching      : Yes
Real Media Transparent Caching: Yes
Do you want to change this (y/n) [n]:
Press the ESC key at any time to quit this session
This basic configuration is cached. A copy of the configurations generated through the Setup utility is stored on disk (/local/local1/setup_gen_config.txt).

•For information about how to launch the Setup utility, see the "Launching the Setup Utility" section.

Setup Utility Menu Options and Corresponding CLI Commands

The menu structure of the Setup utility is hierarchical. For example, after you choose the General Settings option from the main menu, the General Settings submenu appears. As the following example shows, your current location in the menu structure is displayed after the menu options.
               +---------------------------------------------+
               ¦              General Settings               ¦
               +---------------------------------------------¦
               ¦->  Network Configurations :Incomplete       ¦
               ¦    Disk Configurations    :Incomplete       ¦
               ¦    Print Configuration                      ¦
               ¦    Previous Menu (p)                        ¦
               ¦    Main Menu (m)                            ¦
               ¦    Exit (e)                                 ¦
               +---------------------------------------------+
               Main Menu
                  ---> General Settings
Table 3-3 lists the Setup utility menu option and the corresponding Content Engine CLI command. For 
detailed descriptions of the CLI commands you can use to configure network settings and disk 
configuration, refer to the Cisco ACNS Software Command Reference, Release 5.2 publication. 
Information about how to use the CLI method (instead of the Setup utility) to configure any of the 
commonly used caching services (listed in Table 3-2) and other features are provided in subsequent 
chapters of this guide. 
Table 3-3 Setup Utility Menu Options and Corresponding CLI Commands for Standalone Content Engines

Setup Utility Menu Option

Content Engine CLI Command

General Settings

Network Configuration

ip address {ip address netmask | dhcp}

ip default-gateway

hostname

ip name-servers

ip domain-name

Disk Configuration

disk config sysfs {remaining | disk-space}
[cfs {remaining | disk-space}] |
[mediafs {remaining | disk-space}]

Caching-Related Configurations

HTTP proxy caching

http proxy incoming

HTTP transparent caching

wccp router list

wccp web-cache router-list

wccp version 2

HTTP reverse proxy caching

wccp router list

wccp reverse-proxy router-list

wccp version 2

WMT proxy caching

wmt license-key

wmt evaluate

wmt accept-license-agreement

wmt enable

WMT transparent caching

wccp router list

wccp wmt router-list

wccp version 2

wmt license-key

wmt evaluate

wmt accept-license-agreement

wmt enable

RealMedia proxy caching

rtsp proxy media-real license-key

rtsp proxy media-real evaluate

rtsp proxy media-real accept-license-agreement

rtsp proxy media-real enable

RealMedia transparent caching

wccp router list

wccp rtsp router-list

wccp version 2

rtsp proxy media-real license-key

rtsp proxy media-real evaluate

rtsp proxy media-real accept-license-agreement

rtsp proxy media-real enable

Setup Utility Arrows and Keys

Table 3-4 describes the keys and arrows that you can use with the Setup utility.
Table 3-4 Keys and Arrows for the Setup Utility
Keys

Description

?

Displays information about why a particular menu item (for example, Network Configurations) is currently listed as "Incomplete."

ESC

Quits the current dialog session and to return to the previous menu.
e
From a menu, use this hot key to exit the menu interface (to exit the current Setup utility session).
+---------------------------------------------+
¦ General Settings ¦
+---------------------------------------------¦
¦-> Network Configurations :Incomplete ¦
¦ Disk Configurations :Incomplete ¦
¦ Print Configuration ¦
¦ Previous Menu (p) ¦
¦ Main Menu (m) ¦
¦ Exit (e) ¦
+---------------------------------------------+
If any of the required options are incomplete, the following prompt appears:
Some of the configurations are still incomplete.
Do you want to go back and complete them (y/n) [y]:
Press Enter to return to the main menu and complete the configuration of the required options, or enter n to quit the Setup utility session without completing the required options.
m

Returns to main menu from a submenu.

p

Returns to the previous menu from a submenu.

Enter

Selects the highlighted menu option or to select the default option that is displayed.

Up arrow

Moves the cursor up one line.

Down arrow

Moves the cursor down one line.
Deciding the Addressing Scheme for Standalone Content Engines

Before beginning the initial configuration of a Content Engine as a standalone device, you should decide which addressing scheme will be used for this Content Engine. The two supported addressing schemes for standalone Content Engines that are running ACNS 5.x software are mutually exclusive:

•Manually specify a static IP address and network mask.

•Dynamically assign an IP address using the interface-level DHCP addressing scheme.

Note Autoregistration needs to be disabled on the Content Engine before you can configure a Content Engine interface with interface-level DHCP or a static IP address. For information about how to disable autoregistration through the Setup utility, see Step 1 of Using the Setup Utility to Configure a Basic Configuration on a Standalone Content Engine.

If you do not enable interface-level DHCP on the Content Engine, you must manually specify a static IP address and network mask for the Content Engine. If the Content Engine moves to another location in another part of the network, you must manually enter a new static IP address and network mask for this Content Engine.

If you want to enable DHCP and are using the Setup utility to configure a standalone Content Engine, answer y when prompted (as described in Step 7 of Using the Setup Utility to Configure a Basic Configuration on a Standalone Content Engine).
Do you want to enable DHCP on this interface? (y/n) [y]:y
If you are using the CLI method (instead of the Setup utility) to configure a standalone Content Engine, use the ip address dhcp interface configuration to enable interface-level DHCP on a standalone Content Engine.

About Device Network Settings for Standalone Content Engines

In order to deploy a device as a standalone Content Engine on your network, you must initially configure a set of network settings on the Content Engine. These settings are collectively referred to as "device network settings." After the device network settings are defined for the standalone Content Engine, it can become active on your network.

The device network settings that you should have before you start the basic configuration include the following:

•Host name of the Content Engine (for example, if you assign the Content Engine the name CE7305, the prompt will appear as:
CE7305(config)#)
•Internet Protocol (IP) domain name (for example, cisco.com)

•Administrator password

•IP addresses for the Content Engine

If a static IP address is assigned to this Content Engine (for example, 10.0.1.2 as shown in Figure 3-6) then you must also assign it an IP address network mask (for example, 255.255.255.0).

Tip You also have the option of using interface-level DHCP to dynamically assign an IP address to a Content Engine interface instead of manually assigning a static IP address and network mask.

•Default gateway (for example, the router with address 10.0.1.1 is the default gateway for the Content Engine shown in Figure 3-6).

•DNS name server (for example, in Figure 3-6, the Content Engine will use the DNS server with the address 172.16.0.2 for domain name resolution).

Figure 3-6 Configuring Device Network Settings on Standalone Content Engines

.

Note Throughout the rest of this chapter, the term "general settings" is used to refer collectively to device network settings and disk configuration.

ACNS 5.x software provides a Common Interface File System (CIFS) client and a Network File System (NFS) client for Content Engines to communicate with network attached storage (NAS) devices. Content Engines can be attached to NAS devices to increase their storage space. These Content Engines function as NFS or CIFS clients while accessing the NAS servers. NAS servers include UNIX-mode NFS servers or Microsoft Windows systems for CIFS sharing. ACNS CLI commands can be used to attach a Content Engine (standalone as well as registered) to a NAS device. For information about how to use the CLI to attach a Content Engine to a NAS device, refer to the Cisco ACNS Software Configuration Guide for Centrally Managed Deployments, Release 5.2.

Using the CLI Command Method to Configure General Settings for Standalone Content Engines

To use the CLI command method (instead of the Setup utility) to configure the general settings on a standalone Content Engine, follow these steps:

Step 1 Open a console connection on the Content Engine, and log in to the Content Engine CLI using an ACNS system account that has superuser privileges (see the "Logging in to Standalone Content Engines" section.)

Step 2 From privileged EXEC mode, enter global configuration mode to specify the general settings for this standalone Content Engine:
CE# config
Step 3 Use the ip address {ip address netmask | dhcp} global configuration command to configure the Ethernet interface on this Content Engine. You must do one of the following:

•To assign a static IP address and network mask (and not enable DHCP on this interface), enter the following command:
CE(config)# interface {FastEthernet | GigabitEthernet} slot/port  
ip address ip-address netmask
•To enable interface-level DHCP, enter the following command:
CE(config)# interface {FastEthernet | GigabitEthernet}  
slot/port ip address dhcp
If you configure your Ethernet interface using interface-level DHCP, then the remainder of the device network settings for this standalone Content Engine are automatically configured and you are finished with the configuration of the device network settings. If you manually assigned a static IP address, use the ip default-gateway, ip name-server, hostname, ip domain-name, and primary-interface global configuration commands to specify the remaining device network settings. Use the disk config sysfs global configuration command to use the Content Engine CLI command method to configure disk space.

Launching the Setup Utility

The Setup utility can be launched in these ways:

•Manually at any time by entering the setup privileged EXEC command at the CLI prompt

•Automatically when you initially boot up a device

Note A Content Engine that is running ACNS software comes with a single predefined superuser user account (root administrator). This predefined account can be used to invoke the Setup utility. The username for this predefined superuser user account is admin and the default password is default. If these defaults have been changed by another ACNS system administrator, you must obtain the new username and password.

Manually Launching the Setup Utility

To launch the Setup utility manually on a standalone Content Engine that already has its device network settings defined, follow these steps:

Step 1 Using a login account that has the superuser privilege rights (privilege level of 15), log in to the Content Engine CLI through Telnet or Secure Shell (SSH) Version 1 or Version 2.

Note For more information about logging in to the Content Engine CLI, see the "Logging in to Standalone Content Engines" section. For more information about the different CLI modes, see the "ACNS Software CLI Command Modes for Standalone Content Engines" section.

Step 2 From privileged EXEC mode, enter the setup command to launch the Setup utility manually to configure one or more of the commonly used caching services (listed in Table 3-2).
ContentEngine# setup
The current basic configuration for this standalone Content Engine appears.

The displayed basic configuration also indicates which of the commonly used caching services are already configured on this Content Engine. In this case, only the HTTP proxy caching service is currently configured on this Content Engine.
Here is the current profile of this device
CDN device                    : No
HTTP Proxy Caching            : Yes
HTTP Tranparent Caching       : No
HTTP Reverse Proxy Caching    : No
WMT Proxy Caching             : No
WMT Transparent Caching       : No
Real Media Proxy Caching      : No
Real Media Transparent Caching: No
Note The displayed basic configuration indicates that this Content Engine is not a "CDN device." This is because the standalone Content Engine is intentionally not registered with a Content Distribution Manager.

You can quickly modify the basic configuration of this standalone Content Engine by entering y when prompted as shown below.
Do you want to change this (y/n) [n]:y
For more information about how you can use the Setup utility to configure or modify the basic configuration of this Content Engine, see the "Using the Setup Utility to Configure a Basic Configuration on a Standalone Content Engine" section.

Automatically Launching the Setup Utility

When you initially boot up a device, follow these steps to launch the Setup utility automatically:

Step 1 Power up the Content Engine and open a console connection.

You must use a console connection rather than a Telnet session for initial configuration of these device network settings on the Content Engine. However, once you have used a console connection to define the device network settings, you can then use a Telnet session to perform subsequent configuration tasks on this Content Engine.

Step 2 After the operating system boots up, the following prompt appears:
ACNS boot:detected no saved system configuration
  Do you want to enter basic configuration now?
  hit RETURN to enter basic configuration:0019
At the appearance of this prompt, a 30-second countdown begins, during which you can launch the Setup utility.

Step 3 Press Enter.

Step 4 When prompted, enter the administrator password and press Enter.
admin password:
This is the case-sensitive password for the predefined superuser account. The password can include any printable character. By default, the username is admin and the password is default. The administrator password can be up to 20 characters long and is case sensitive. Each Content Engine in a farm must have a password. You must enter a password before pressing Enter.

Step 5 When prompted, reenter the administrator password and press Enter.
re-enter password:
The Setup utility is automatically launched, and you are prompted to specify the device mode for this particular device. When the Setup utility is launched on a Content Engine that supports device mode changes (for example, the CE-565), you are prompted to specify the device mode for that particular device.

Step 6 When prompted, press Enter or enter CE to specify the Content Engine device mode for this standalone Content Engine.
What is the mode of the device (CE/CR/CDM/PM) [CE]: CE
Step 7 When prompted, enter no to specify that this Content Engine is not going to be managed by a Content Distribution Manager.

Is this CE going to be managed by a CDM (Content Distribution Manager)
(y/n) [y]: no

For more information about how to use the Setup utility after booting up a device for the first time, see the "Using the Setup Utility to Configure a Basic Configuration on a Standalone Content Engine" section.

Using the Setup Utility to Configure a Basic Configuration on a Standalone Content Engine

To use the Setup utility to configure a basic configuration on a standalone Content Engine, follow these steps:

Step 1 Launch the Setup utility.

•If this is the first time that the device is being booted up, follow these steps:

–Power up the device, open a console connection, and automatically invoke the Setup utility. (See the "Automatically Launching the Setup Utility" section for detailed instructions.)

–When the Setup utility is launched on a Content Engine that supports device mode changes (for example, the CE-565), you are prompted to specify the device mode for that particular device. When prompted, press Enter or enter CE to specify the Content Engine device mode for this standalone Content Engine.
What is the mode of the device (CE/CR/CDM/PM) [CE]: CE
–When prompted, enter n to specify that this Content Engine is not going to be managed by a Content Distribution Manager.
Is this CE going to be managed by a CDM (Content Distribution Manager)  
(y/n) [y]:n
By default, the autoregistration is enabled on a Content Engine. When autoregistration is enabled on a Content Engine, the Content Engine automatically searches for and register with the Content Distribution Manager on the network. Because you want to deploy your Content Engine as a "standalone" device that is not registered with a Content Distribution Manager, you must specify n to disable autoregistration on this Content Engine.

Note If you are using the CLI method to configure a standalone Content Engine (instead of the Setup utility), you can manually disable autoregistration by specifying the no auto-register enable global configuration command.

–Proceed to Step 2 below.

•If the standalone Content Engine is running ACNS 5.2 software and already has some of its basic configuration settings configured, follow these steps:

–Manually invoke the Setup utility, as described in the "Manually Launching the Setup Utility" section.

–Proceed to Step 2 below.
Step 2 When prompted, press Enter or enter y to indicate that you want to configure one or more of the seven commonly used caching services on this standalone Content Engine.
Do you want to configure this CE for doing HTTP Proxy Caching (y/n) [y]:y
Do you want to configure this CE for doing HTTP Transparent Caching  
using WCCP (y/n) [y]:y
Do you want to configure this CE for doing HTTP Reverse Proxy Caching  
using WCCP (y/n) [y]:y
Do you want to configure this CE for doing WMT Proxy Caching (y/n) [y]:y
Do you want to configure this CE for doing WMT Transparent Caching  
using WCCP (y/n) [y]:y
Do you want to configure this CE for doing Real Media Proxy Caching (y/n) [y]:y
Do you want to configure this CE for doing Real Media Transparent Caching  
using WCCP (y/n) [y]:y
The main menu of the Setup utility for a standalone Content Engine appears with the General Settings menu option highlighted. In the following example, the General Settings and Caching Related Configurations are currently reported as "Incomplete."
           +-----------------------------------------------------+
           ¦                      Main Menu                      ¦
           +-----------------------------------------------------¦
           ¦->  General Settings               :Incomplete       ¦
           ¦    Caching Related Configurations :Incomplete       ¦
           ¦    Print Configuration                              ¦
           ¦    Exit (e)                                         ¦
           +-----------------------------------------------------+
           Main Menu
	Configure network settings, disks, etc
	Press '?' to see why this item is incomplete
Note Even if you manually launch the Setup utility on this standalone Content Engine because the Content Engine already had some settings configured (for example, the device network settings, disk configuration, and HTTP proxy caching), the status of these configurations is listed as "Incomplete." You must first use the Setup utility to accept the default (currently configured) values before the setting will be reported as "Complete" in a Setup menu. (When you are prompted for a value, any currently configured value is displayed as the default value. You can quickly accept the default value by pressing Enter.)
Step 3 If the general settings (device network settings and disk configuration) are already configured on this Content Engine, go to Step 10 to configure one or more of the commonly used caching services on this Content Engine. Otherwise, complete Step 4 through Step 9 to configure the general settings for this standalone Content Engine.

Step 4 In the main menu, press Enter to choose the highlighted General Settings menu option. The General Settings submenu appears with the Network Configurations option highlighted.
               +---------------------------------------------+
               ¦              General Settings               ¦
               +---------------------------------------------¦
               ¦->  Network Configurations :Incomplete       ¦
               ¦    Disk Configurations    :Incomplete       ¦
               ¦    Print Configuration                      ¦
               ¦    Previous Menu (p)                        ¦
               ¦    Main Menu (m)                            ¦
               ¦    Exit (e)                                 ¦
               +---------------------------------------------+
               Main Menu
                  ---> General Settings
         Configure IP address, default gateway, name servers, domain name, etc
         Press '?' to see why this item is incomplete
Step 5 Press Enter to choose the highlighted Network Configurations menu option.

The following warning appears.
WARNING: Changing any of the network settings from a
telnet session may render the device inaccessible on
the network. Therefore it is suggested that you have
access to the console before modifying the network settings.
Step 6 After the warning appears, you are prompted to choose an interface identifier for the initial configuration of this Content Engine. Enter an interface identifier (for example, enter 1 to specify the Gigabit Ethernet 1/0 interface).
Please choose an interface to configure from the following list:
1: GigabitEthernet 1/0
2: GigabitEthernet 2/0
Enter choice:1
Press the ESC key at any time to quit this session
Note You can configure additional interfaces for this Content Engine through CLI commands at a later time, as described in the "Configuring Additional Network Interfaces" section.

Step 7 After specifying an interface identifier, you are asked if you want to enable interface-level DHCP on this particular interface.

•To not enable DHCP on this interface, go to Step 8.

•To enable DHCP on this interface, when prompted, enter y:
Do you want to enable DHCP on this interface? (y/n) [y]:y
Based on the input, the following CLIs will be configured:
       interface GigabitEthernet 1/0
        ip address dhcp
        exit
Do you accept these configs (y/n) [y]:y
When you enter it again to accept the configuration, the remainder of your device network settings are automatically configured for this Content Engine. The main menu of the Setup utility appears and indicates that the configuration of the device network settings (Network Configuration) for this Content Engine is now "Complete." Go to Step 9.

Step 8 Alternatively, to continue the configuration process using the static IP address method (and not enable interface-level DHCP on this Content Engine), follow these steps:

a. When prompted, enter n:
Do you want to enable DHCP on this interface? (y/n) [y]:n
b. When prompted for a local IP address, specify a static IP address (for example, 10.0.1.2).
Please enter the IP address of this interface:10.0.1.2
c. When prompted, specify the network mask (for example, 255.255.255.0)
Please enter the netmask of this interface:255.255.255.0
d. When prompted, specify the IP address of the gateway (for example, 10.0.1.1).
Please enter the default gateway:10.0.1.1
e. When prompted, specify the IP address of the DNS server (for example, 172.16.0.2).
Please enter the domain name server IP:172.16.0.2
f. When prompted, specify the IP domain name of this Content Engine (for example, cisco.com).
Please enter the domain name:cisco.com
g. When prompted, specify the host name of this Content Engine (for example, CE7305).
Please enter the hostname:CE7305
A message appears, indicating which CLI commands will be configured based on your input.
Based on the input, the following CLIs will be configured:
       interface GigabitEthernet 1/0
        ip address 10.0.1.2 255.255.255.0
        exit
       ip default-gateway 10.0.1.1
       ip name-server 172.16.0.2
       ip domain-name cisco.com
       hostname CE7305
h. When prompted, enter y to save these network configurations on this standalone Content Engine.
Do you accept these configs (y/n) [y]:y
The main menu appears, indicating that the configuration of the device network settings (network configuration) for this standalone Content Engine is now complete.

Note You are now finished with the configuration of the device network settings for this Content Engine, which is now standalone. The next step is to configure the disk space on this standalone Content Engine. Go to Step 9.

Step 9 Configure the disk configuration for this standalone Content Engine, as follows:

a. From the main menu, choose the General Settings option. In the displayed General Settings submenu, choose the Disk Configurations option. The current storage allocation for this standalone Content Engine appears as shown in the following example.
Here is the current storage allocation scheme:
  SYSFS                 1.0GB
  CFS                   0.0GB
  MEDIAFS               0.5GB
  CDNFS                15.6GB
Disk space in ACNS software is allocated on a per-file system basis, rather than on a per-disk basis. You can configure your overall disk storage allocations according to the kinds of client protocols you expect to use and the amount of storage that you need to provide for each of the functions, as described below.

Disk Storage Type

Function

sysfs (system file system)

Stores log files, including transaction logs, syslogs, and internal debugging logs. Also can store image files and configuration files.

cfs (cache file system)

Caches HTTP and FTP objects.

mediafs (media file system)

Caches content that is fetched through the two streaming protocols (RTSP and WMT). By default 30 per cent of the mediafs space is reserved for RTSP streaming content, and 70 per cent is reserved for WMT streaming content.

b. When prompted, enter y to change the current storage allocations on this Content Engine.
Do you want to change this (y/n) [n]:y
The following questions will prompt you how the available
storage is to be allocated to different file systems.
You can either enter an absolute amount of storage in
GB or MB, or a percentage of the available storage.
In the former case, the desired amount should be entered
followed by either 'GB' or 'MB', and in the latter case,
the number should be followed by '%'
c. When prompted, enter the amount of storage to be allocated to the system file system (sysfs). For example, enter 2GB.
Please enter the amount of storage to be allocated
to SYSFS (This file system is used for storing user
and logging files; at least 1GB required):2GB
d. When prompted, enter the amount of storage to be allocated to the cache file system (cfs). For example, enter 20MB.
Please enter the amount of storage to be allocated
to CFS (This file system is used for storing HTTP
objects):20MB
e. When prompted, enter 0GB or 0% to specify that no amount of storage is to be allocated to the cdnfs.
Please enter the amount of storage
to CDNFS (This file system is use
prepositioned content):0GB
Note You do not want to allocate any storage to the cdnfs because this file system is used to store pre-positioned content on a registered Content Engine. You cannot pre-position content on a standalone Content Engine. However, you can preload content on a standalone Content Engine at a later time, as described in the "Configuring Content Preloading for Standalone Content Engines" section.

f. When prompted, enter the amount of storage to be allocated to the media file system (mediafs). If you plan to enable WMT caching or RTSP caching on this standalone Content Engine, then you must allocate storage for the mediafs. For example, enter 10MB.
Please enter the amount of storage to be allocated
to MEDIAFS (This file system is used for storing WMT
and Real media content):10MB
The new disk configuration for this standalone Content Engine appears, as shown in the following example.
Here is the new disk configuration:
       SYSFS             2GB
       CFS               20MB
       CDNFS             0GB
       MEDIAFS           10MB
g. When prompted, enter y to accept the new disk configuration.
Do you accept these configs (y/n) [y]:y
The General Settings submenu appears and the Disk Configurations option is now reported as "Complete." The general settings (network configuration settings and the disk configurations) are now configured on this standalone Content Engine.
               +---------------------------------------------+
               ¦              General Settings               ¦
               +---------------------------------------------¦
               ¦->  Network Configurations :Complete         ¦
               ¦    Disk Configurations    :Complete         ¦
               ¦    Print Configuration                      ¦
               ¦    Previous Menu (p)                        ¦
               ¦    Main Menu (m)                            ¦
               ¦    Exit (e)                                 ¦
               +---------------------------------------------+
               Main Menu
                  ---> General Settings
         Configure IP address, default gateway, name servers, domain name, etc
Step 10 Configure one or more of the commonly used caching services (see Table 3-2 for list) on this standalone Content Engine, as follows:

a. Use one of the following methods to display the Caching Related Configurations submenu.

–From the General Settings submenu, choose the Main Menu option to return to the main menu. The Caching Related Configurations menu option is currently reported as "Incomplete" because you have not configured any caching services on this Content Engine yet.

–From the main menu, choose the Caching Related Configurations option to configure one or more commonly used caching services on this Content Engine. The Caching Related Configurations submenu appears with a list of the caching services that you previously selected. Note that in the following example, all of these caching services are listed as "Incomplete" because you have not configured any of them yet.
            +-----------------------------------------------------+
            ¦           Caching Related Configurations            ¦
            +-----------------------------------------------------¦
            ¦->  HTTP Caching                   :Incomplete       ¦
            ¦    WMT Caching                    :Incomplete       ¦
            ¦    Real Media Caching             :Incomplete       ¦
            ¦    Print Configuration                              ¦
            ¦    Previous Menu (p)                                ¦
            ¦    Main Menu (m)                                    ¦
            ¦    Exit (e)                                         ¦
            +-----------------------------------------------------+
            Main Menu
               ---> Caching Related Configurations
			Configure HTTP Caching
b. To configure HTTP caching on this standalone Content Engine, complete Step 11.

c. To configure WMT caching on this standalone Content Engine, complete Step 15.

d. To configure RealMedia caching on this standalone Content Engine, complete Step 18.

Step 11 Configure HTTP caching as follows:

a. From the Caching Related Configurations submenu, choose the HTTP Caching option.

The HTTP Caching submenu appears with options for each of the available HTTP caching services. In the following example, all three of the HTTP caching services (HTTP proxy caching, HTTP transparent caching, and HTTP reverse proxy caching) are to be configured on this Content Engine.
              +-------------------------------------------------+
              ¦                  HTTP Caching                   ¦
              +-------------------------------------------------¦
              ¦->  HTTP Proxy Caching         :Incomplete       ¦
              ¦    HTTP Transparent Caching   :Incomplete       ¦
              ¦    HTTP Reverse Proxy Caching :Incomplete       ¦
              ¦    Print Configuration                          ¦
              ¦    Previous Menu (p)                            ¦
              ¦    Main Menu (m)                                ¦
              ¦    Exit (e)                                     ¦
              +-------------------------------------------------+
              Main Menu
                 ---> Caching Related Configurations
                    ---> HTTP Caching
          Configure this CE for doing HTTP Proxy caching
b. To configure HTTP proxy caching, complete Step 12.

c. To configure HTTP transparent caching using WCCP, complete Step 13.

d. To configure HTTP reverse proxy caching, complete Step 14.

Step 12 Configure HTTP proxy caching as follows:

a. From the HTTP Caching submenu, choose the HTTP Proxy Caching option.

b. When prompted, specify the incoming proxy ports for proxy-style HTTP requests from client browsers. These are the port numbers on which this standalone Content Engine will accept incoming proxy-style HTTP requests. These are also the ports that the Content Engine will use to serve the requested content to the requester (the client browser). For HTTP proxy caching, this standalone Content Engine is functioning as a nontransparent forward proxy server that receives HTTP requests directly from the client browsers.

The incoming proxy port numbers can be from 1 to 65535. You can specify up to eight incoming proxy ports, each separated by a space. The incoming proxy ports can be the same ports that are used by transparent mode services (for example, HTTP transparent caching) on this standalone Content Engine.
Please enter all the HTTP Proxy incoming ports
(up to 8, separated by spaces) [80 8080]:80 8080 8081
A list of the configured CLI commands appears and you are asked if you want save this configuration. Enter y to accept this configuration.
Based on the input, the following CLIs will be configured:
       http proxy incoming 80 8080 8081
c. When prompted, enter y to accept this configuration.
Do you accept these configs (y/n) [y]:y
The specified settings are saved and the HTTP Caching submenu reappears. Note that the HTTP Proxy Caching option is now listed as "Complete." Remember that you still must configure the client browsers to point directly to this Content Engine as their HTTP proxy server, as described in the "Pointing Client Browsers Directly to a Standalone Content Engine" section.

Step 13 Configure HTTP transparent caching using WCCP as follows:

a. From the HTTP Caching submenu, choose the HTTP Transparent Caching option.

b. When prompted, specify the IP addresses of the WCCP Version 2-enabled routers that will transparently redirect HTTP requests to this standalone Content Engine on port 80 only, or press Enter to use the default gateway. In this case, the default gateway (the WCCP Version 2-enabled router that was specified as this Content Engine's default gateway) has an IP address of 10.0.1.1.
Please enter the IP addresses of WCCP routers [10.0.1.1]:
c. Enter y to enable HTTP transparent caching on this Content Engine.
Do you want to enable HTTP transparent caching (y/n) [y]:y
A list of the configured CLI commands appears, along with a reminder that you must configure the web-cache service (WCCP service 0) on the WCCP Version 2-enabled router.
NOTE: Please remember to configure web-cache service on the router.
Based on the input, the following CLIs will be configured:
       wccp router-list 1 10.0.1.1
       wccp version 2
       wccp web-cache router-list 1
d. Enter y to accept this configuration.
Do you accept these configs (y/n) [y]:y
The specified settings are saved and the HTTP Caching submenu reappears. Note that the HTTP Transparent Caching option is now listed as "Complete." Remember that you still must configure the web-cache service (WCCP service 0) on the WCCP Version 2-enabled routers, as described in the "Configuring WCCP Services on a Router" section.

Step 14 Configure HTTP reverse proxy caching using WCCP as follows:

a. From the HTTP Caching submenu, choose the HTTP Reverse Proxy Caching option.

b. When prompted, specify the IP addresses of the WCCP Version 2-enabled routers that will redirect reverse proxy packets to this Content Engine, or press Enter to use the default gateway (for example, the WCCP Version 2-enabled router with the IP address of 10.0.1.1).
Please enter the IP addresses of WCCP routers [10.0.1.1]:
c. Enter y to enable HTTP reverse proxy caching on this Content Engine.
Do you want to enable HTTP reverse proxy caching (y/n) [y]:y
A list of the configured CLI commands appears, along with a reminder that you must still configure WCCP service 99 (reverse proxy caching) on the WCCP Version 2-enabled router.
NOTE: Please remember to configure service 99 on the router.
Based on the input, the following CLIs will be configured:
       wccp router-list 1 10.0.1.1
       wccp version 2
       wccp reverse-proxy router-list 1
d. Enter y to accept this configuration.
Do you accept these configs (y/n) [y]:y
The specified settings are saved and the HTTP Caching submenu reappears. Note that the HTTP Reverse Proxy Caching option is now listed as "Complete." Remember to configure the reverse proxy caching service (WCCP service 99) on the WCCP Version 2-enabled router, as described in the "Configuring the Reverse Proxy Service (Service 99) on a Router" section.

Step 15 Configure WMT caching as follows:

a. Use one of the following methods to display the WMT Caching submenu.

–From the HTTP Caching submenu, choose the Previous Menu option and then choose the WMT Caching option from the Caching Related Configurations submenu.

–From the Caching Related Configurations submenu, choose the WMT Caching option.

–From the main menu, choose the Caching Related Configurations option and then choose the WMT Caching option from the Caching Related Configurations submenu.

In the following example, both WMT caching services (WMT proxy caching and WMT transparent caching) are to be configured on this standalone Content Engine.
              +----------------------------------------------+
              ¦                 WMT Caching                  ¦
              +----------------------------------------------¦
              ¦->  WMT Proxy Caching       :Incomplete       ¦
              ¦    WMT Transparent Caching :Incomplete       ¦
              ¦    Print Configuration                       ¦
              ¦    Previous Menu (p)                         ¦
              ¦    Main Menu (m)                             ¦
              ¦    Exit (e)                                  ¦
              +----------------------------------------------+
              Main Menu
                 ---> Caching Related Configurations
                    ---> WMT Caching
        Configure this CE for doing WMT Proxy caching
b. To configure WMT proxy caching, complete Step 16.

c. To configure WMT transparent caching using WCCP Version 2, complete Step 17.

Step 16 Configure WMT proxy caching, as follows:

a. From the WMT caching submenu, choose the WMT Proxy Caching option.

b. If there is a WMT license already installed on this Content Engine, enter n when the following prompt appears:
WMT license key is already installed. Do you want to install
a different license key (y/n) [n]:n
Otherwise, specify whether or not you have a license key for WMT when prompted. If you have your Cisco license key for the WMT product, then enter y. Otherwise, enter n to use the evaluation license for the WMT feature on this standalone Content Engine (as shown below).
Do you have the license key for WMT (y/n) [y]:n
Do you want to evaluate WMT (y/n) [y]:y
Note When you use the Setup utility to configure WMT proxy caching, the Content Engine automatically is configured to use the default port (port 1755) to listen for incoming WMT requests.

A list of the configured CLI commands appears, and you are asked if you want save this configuration. If you used the evaluation license to enable WMT on this Content Engine, the wmt evaluate command is included in the list of constructed CLI commands. If you used your Cisco WMT license, then the wmt license-key command is listed instead of the wmt evaluate command.
Based on the input, the following CLIs will be configured:
       wmt evaluate
       wmt accept-license-agreement
       wmt enable
c. When prompted, enter y to accept this configuration.
Do you accept these configs (y/n) [y]:y
The specified settings are saved and the WMT Caching submenu reappears. Note that the WMT Proxy Caching option is now listed as "Complete." Remember that you still must configure Windows Media Player on the end user desktops to point directly to this Content Engine as their proxy server, as described in the "Pointing Windows Media Players Directly to a Standalone Content Engine" section.

Tip You can also use the Content Engine CLI to configure WMT streaming on this Content Engine at a later time, as described in "Configuring WMT Streaming Media Services on Standalone Content Engines."

Step 17 Configure WMT transparent caching as follows:

a. From the WMT caching menu, choose the WMT Transparent Caching option.

b. When prompted, specify the IP addresses of the WCCP Version 2-enabled routers that will redirect WMT requests to this Content Engine. Press Enter to use the default gateway, or enter the IP addresses of other WCCP Version 2-enabled routers that you want to redirect WMT requests to this Content Engine. In this case, the default gateway (the WCCP Version 2-enabled router that was specified as this Content Engine's default gateway) has an IP address of 10.0.1.1.
Please enter the IP addresses of WCCP routers [10.0.1.1]:
c. If there is a WMT license already installed on this Content Engine, enter n when the following prompt appears:
WMT license key is already installed. Do you want to install
a different license key (y/n) [n]:n
Otherwise, specify whether or not you have a license key for WMT when prompted. If you have your Cisco license key for the WMT product, then enter y. Otherwise, enter n to use the evaluation license for the WMT feature on this standalone Content Engine (as shown below).
Do you have the license key for WMT (y/n) [y]:n
Do you want to evaluate WMT (y/n) [y]:y
d. When prompted, enter y to enable WMT transparent caching on this Content Engine.
Do you want to enable WMT transparent caching (y/n) [y]:y
A list of the configured CLI commands appears, along with a reminder that you still must configure the mmst service (service 81) and the mmsu service (service 82) on the WCCP Version 2-enabled router. If you used the evaluation license to enable WMT on this Content Engine, the wmt evaluate command is included in the list of configured CLI commands. If you used your Cisco WMT license, then the wmt license-key command is listed instead of the wmt evaluate command.
NOTE: Please remember to configure services 81 and 82 on the router.
Based on the input, the following CLIs will be configured:
       wmt evaluate
       wmt accept-license-agreement
       wmt enable
       wccp router-list 1 10.0.1.1
       wccp version 2
       wccp wmt router-list 1
e. When prompted, enter y to accept this configuration.
Do you accept these configs (y/n) [y]:y
The specified settings are saved and the WMT Caching submenu appears. Note that the WMT Transparent Caching option is now listed as "Complete." Remember that you still must configure the WCCP services 81 (the mmst service) and 82 (the mmsu service) on the WCCP Version 2-enabled router, as described in the "Configuring the MMST Service (Service 81) on a Router" section and the "Configuring the MMSU Service (Service 82) on a Router" section respectively.

Step 18 Configure RealMedia caching, as follows:

a. Use one of the following methods to display the RealMedia Caching submenu.

–From the WMT Caching submenu, choose the Previous Menu option and then choose the WMT Caching option from the Caching Related Configurations submenu (shown below).

–From the Caching Related Configurations submenu, choose the Real Media Caching option.

–From the main menu, choose the Caching Related Configurations option and then choose the Real Media Caching option from the Caching Related Configurations submenu.

In the following example, both RealMedia caching services (RealMedia proxy caching and Real Media transparent caching using WCCP Version 2) are to be configured on this standalone Content Engine.
              +-----------------------------------------------+
              ¦              Real Media Caching               ¦
              +-----------------------------------------------¦
              ¦-> Caching       :Incomplete                   ¦
              ¦    Real Transparent Caching :Incomplete       ¦
              ¦    Print Configuration                        ¦
              ¦    Previous Menu (p)                          ¦
              ¦    Main Menu (m)                              ¦
              ¦    Exit (e)                                   ¦
              +-----------------------------------------------+
              Main Menu
                 ---> Caching Related Configurations
                    ---> Real Media Caching
         Configure this CE for doing Real Proxy caching
         Press '?' to see why this item is incomplete
b. To configure RealMedia proxy caching, complete Step 19.

c. To configure RealMedia transparent caching using WCCP Version 2, complete Step 20.

Step 19 Configure RealMedia proxy caching, as follows:

a. From the RealMedia Caching submenu, choose the Real Proxy Caching option.

b. If there a RealProxy license already installed on this Content Engine, enter n when the following prompt appears:
Real Proxy license key is already installed. Do you
want to install a different license key (y/n) [n]:n
Otherwise, specify whether or not you have a RealProxy license key. If you have your Cisco RealProxy license key, then enter y. Otherwise, enter n to use the RealProxy evaluation license for this standalone Content Engine (as shown below).
Do you have the license key for Real Proxy (y/n) [y]:n
Do you want to evaluate Real Proxy (y/n) [y]:y
A list of the configured CLI commands appears, and you are asked if you want save this configuration. If you used the evaluation license to enable the RTSP proxy for RealMedia requests, the rtsp proxy media-real evaluate command is included in the list of configured CLI commands.
Based on the input, the following CLIs will be configured:
rtsp proxy media-real accept-license-agreement
  rtsp proxy media-real enable
  rtsp proxy media-real evaluate
c. When prompted, enter y to accept this configuration.
Do you accept these configs (y/n) [y]:y
Note When you use the Setup utility to configure RealMedia proxy caching, the Content Engine automatically is configured to use the standard RTSP port (default port 554) to listen for incoming RealMedia requests. The RTSP gateway is the single point of entry for RTSP messages on the standalone Content Engine. The RTSP gateway runs on the Content Engine and is automatically enabled. By default, the RTSP gateway listens on port 554 for incoming RTSP requests. If you want to configure the RTSP gateway to listen for incoming RTSP requests on a port other than the default port (port 554), you must change the incoming RTSP port. You must use the Content Engine CLI (the rtsp port incoming rtsp-gateway-incoming-port-number global configuration command) to change the RTSP incoming port on a standalone Content Engine. For more information, see the "Configuring Basic Settings for the RTSP Gateway" section.

The specified settings are saved and the RealMedia Caching submenu reappears. Note that the RealProxy Caching option is now listed as "Complete." Remember that you still must configure the RealMedia players on the client desktops to point directly to this Content Engine as their proxy server, as described in the "Pointing RealMedia Players Directly to a Standalone Content Engine" section.

Tip You can also configure RealMedia streaming (VOD files and live splitting) on this Content Engine at a later time, as described in "Configuring RTSP Media Services on Standalone Content Engines."

Step 20 Configure RealMedia transparent caching using WCCP as follows:

a. From the RealMedia Caching submenu, choose the Real Transparent Caching option.

b. When prompted, specify the IP addresses of the WCCP Version 2-enabled routers that will redirect RealMedia requests to this Content Engine. Press Enter to use the default gateway, or enter the IP addresses of other WCCP Version 2-enabled routers that you want to redirect RealMedia requests to this Content Engine. In this case, the default gateway has an IP address of 10.0.1.1 (the WCCP Version 2-enabled router that was specified as this Content Engine's default gateway).
Please enter the IP addresses of WCCP routers [10.0.1.1]:
c. If there is a RealProxy license already installed on this Content Engine, enter n when the following prompt appears:
Real Proxy license key is already installed. Do you
want to install a different license key (y/n) [n]:n
Otherwise, specify whether or not you have a RealProxy license key. If you have your Cisco RealProxy license key, then enter y. Otherwise, enter n to use the RealProxy evaluation license for this standalone Content Engine (as shown below).
Do you have the license key for Real Proxy (y/n) [y]:n
Do you want to evaluate Real Proxy (y/n) [y]:y
d. Enter y to enable RealMedia transparent caching on this Content Engine.
Do you want to enable Real Media transparent caching (y/n) [y]:y
A list of the configured CLI commands appears along with a reminder that you still must configure the rtsp service (service 80) on the WCCP Version 2-enabled router. If you used the evaluation license to enable the RTSP proxy for RealMedia requests, the rtsp proxy media-real evaluate command is included in the list of configured CLI commands.
NOTE: Please remember to configure service 80 on the router.
Based on the input, the following CLIs will be configured:
       rtsp proxy media-real accept-license-agreement
       rtsp proxy media-real enable
       wccp router-list 1 10.0.1.1
       wccp version 2
       wccp rtsp router-list 1
e. When prompted, enter y to accept this configuration.
Do you accept these configs (y/n) [y]:y
The specified settings are saved and the RealMedia Caching submenu reappears. Note that the Real Transparent Caching option is now listed as "Complete." Remember that you still must configure the rtsp service (service 80) on the WCCP Version 2-enabled router, as described in the "Configuring the RTSP Service (Service 80) on a Router" section.

Note If the Content Engine is behind a network address translation (NAT)-enabled router, you must also specify the IP address of the RTSP gateway. After you have used the Setup utility to complete the basic configuration of a Content Engine, you can exit the Setup utility and then use the Content Engine CLI to specify the IP address of the RTSP gateway. To specify the IP address of the RTSP gateway, use the rtsp ip-address rtsp-gateway-ip-address global configuration command, as described in the "Configuring Basic Settings for the RTSP Gateway" section.

Configuring Client Browsers and Media Players for Direct Proxy Routing

Remember that after you configure the standalone Content Engine for nontransparent (proxy) caching, you must configure the client browsers and media players to route their content requests directly to this Content Engine (direct proxy routing). For information about how to point client browsers or media players to a standalone Content Engine that is functioning as a nontransparent proxy server for these clients, see Table 3-5.

Table 3-5 Configuring Client Browsers and Media Players to Support Direct Proxy Routing of Content Requests

Nontransparent
Caching

Additional Information and Instructions

HTTP proxy caching

Pointing Client Browsers Directly to a Standalone Content Engine

HTTPS proxy caching

Pointing Client Browsers Directly to a Standalone Content Engine

WMT proxy caching

Pointing Windows Media Players Directly to a Standalone Content Engine

RealMedia
proxy caching

Pointing RealMedia Players Directly to a Standalone Content Engine

Pointing Client Browsers Directly to a Standalone Content Engine

If nontransparent caching is to be used to direct content requests to a standalone Content Engine that is functioning as a nontransparent proxy server, you must configure the client browsers to point directly to this Content Engine. To point a client browser to a Content Engine you can use proxy autoconfiguration (PAC) files, or you can manually configure the browser to point to a specific standalone Content Engine.

For more information on these two different methods, see the following sections:

•Using PAC Files to Point Client Browsers Directly to a Standalone Content Engine

•Manually Pointing Client Browsers to a Standalone Content Engine

Using PAC Files to Point Client Browsers Directly to a Standalone Content Engine

ACNS 5.x software provides support for PAC files to point client browsers directly to a standalone Content Engine (nontransparent forward proxy server for these client browsers). A PAC file is a configuration file that is written in JavaScript and stored on an FTP server in your intranet. To use PAC files to point client browsers directly to a standalone Content Engine:

1. Create the PAC file on an FTP server.

2. Download the PAC file from the FTP server to the Content Engine that will act as the proxy server for the client browsers.

Each time you download a new PAC file to a standalone Content Engine, follow these steps:

a. Disable proxy autoconfiguration on the Content Engine (no proxy-auto-config enable command).

b. Download the new PAC file to the Content Engine.

Note You must configure disks /local1 or /local2 as a sysfs volume on the Content Engine before downloading the autoconfiguration file to either of these two disk locations.

c. Enter the proxy-auto-config enable command to reenable the automatic proxy configuration feature on the Content Engine.

3. Manually configure the browser for automatic proxy configuration by explicitly specifying the Content Engine's IP address, incoming port number, file directory, and the name of the PAC file in the browser.

Note Microsoft Internet Explorer and Netscape browsers support the use of PAC files.

4. If a browser is configured for automatic proxy configuration, then when the browser starts up, it will obtain the necessary proxy information (for example, the proxy server's IP address and port configuration information) from the PAC file (.pac file).

The following is an example of how to use a PAC file to point client browsers to the Content Engine:

Step 1 Create a PAC file on an FTP server.

The following is an example of a very simple PAC file named proxyfile.pac. In this case, there is only one proxy (one standalone Content Engine) and traffic that is not destined for "cisco.com" is sent to the proxy server (Content Engine) for all Internet requests.
Example #1: Use proxy for everything except local hosts
This would work in Netscape's environment. All hosts which aren't fully
qualified, or the ones that are in local domain, will be connected to
directly. Everything else will go through w3proxy:8080. If the proxy goes
down, connections become automatically direct.
    function FindProxyForURL(url, host)
    {
        if (isPlainHostName(host) ||
            dnsDomainIs(host, ".cisco.com"))
            return "DIRECT";
        else
            return "PROXY ce1.cisco.com:8080; DIRECT";
    }Note: This is the simplest and most efficient autoconfig file for cases
where there's only one proxy.
Step 2 Use the proxy-auto-config download EXEC command to download the PAC file from the specified FTP server to the Content Engine. By default, the PAC file is downloaded to the present working directory of the Content Engine.

This example demonstrates how to download a PAC file named the proxyfile.pac from an FTP server that has an IP address of 172.16.10.10 to the Content Engine. The Content Engine is functioning as a PAC file server because the client browsers will be pointed to this PAC file when the browsers are started up.
ContentEngine# proxy-auto-config download 172.16.10.10 remotedirname proxyfile.pac
Step 3 Use the proxy-auto-config enable global configuration command to enable the browser autoconfiguration feature on this standalone Content Engine.
ContentEngine(config)# proxy-auto-config enable
Step 4 Manually configure each client browser for automatic proxy configuration. If a browser is configured for automatic proxy configuration, the browser will obtain the necessary information from the specified .pac file on the Content Engine each time the browser starts up. You must explicitly specify the Content Engine's IP address, incoming port number, file directory, and name of the .pac file in the browser.

The following shows how to perform this task from Internet Explorer Version 6.0.

a. From the Internet Explorer GUI, choose Tools > Internet Options. The Internet Options window appears. (See Figure 3-7.)

Figure 3-7 Internet Options Window

b. At the top of the Internet Options window, click the Connections tab to bring this tab to the front. (See Figure 3-8.)

Figure 3-8 Connections Tab Window

c. On the Connections tab, click the Settings button. The Settings window appears. (See Figure 3-9.)

Figure 3-9 Settings Window

d. Check the Use automatic configuration script check box.

e. In the Address field, enter the URL of the .pac file that this browser should use to determine which proxy server (the Content Engine) it should direct its content requests to.
http://ContentEngine-IPaddress:portnumber/pac filename
In the following example, the URL of the .pac file specifies that the .pac file is named proxyfile.pac, and is stored on a Content Engine (nontransparent forward proxy server) that has an IP address of 172.16.10.10 and 8080 as an incoming port of 8080.
http://172.16.10.10:8080/proxyfile.pac
Note When specifying the port number in the URL of the .pac file, use the same port number that was specified as the proxy's incoming port number (through the http proxy incoming portnumber global configuration command, or the Setup utility as described in Step 12 of "Using the Setup Utility to Configure a Basic Configuration on a Standalone Content Engine"). For instance, if port 8080 is specified with the http proxy incoming 8080 command, then use 8080 as your port number in the URL of the .pac file.

f. Click OK to save the settings and close the Settings window.

Step 5 If NTLM is used in this environment to control user Internet access, you must change the default setting for user authentication in the client browser to prevent the user from being prompted by a popup window to log in every time the user attempts to access a new website. The following shows how to change this default setting in Internet Explorer Version 6.0.

a. In the Internet Options window (Figure 3-7), click the Security tab. The Security tab appears with the Internet selected as the web content zone. (See Figure 3-10).

Figure 3-10 Security Tab

b. Click the Custom Level button. The Security Settings window appears.

c. In the Security Settings window, scroll down to the User Authentication section of the window. (See Figure 3-11.)

Figure 3-11 Security Settings Window

Figure 3-11 shows that the default user authentication setting is for automatic logon for an intranet zone only.

d. Change the default user authentication setting by clicking the Automatic logon with current username and password radio button. (See Figure 3-12).

Figure 3-12 Changing the Default User Authentication Setting

e. Click OK to close the Security Settings window.

Manually Pointing Client Browsers to a Standalone Content Engine

To manually point a client browser to a standalone Content Engine instead of using proxy autoconfiguration (PAC) files, you must explicitly specify the IP address and port number of the Content Engine (nontransparent proxy server for this client browser) in the browser.

The following example describes how to perform this task from Internet Explorer, Version 6.0.

Step 1 From the Internet Explorer GUI, choose Tools > Internet Options. The Internet Options window appears. (See Figure 3-7.)

Step 2 At the top of the Internet Options window, click the Connections tab to bring it to the front. (See Figure 3-8.)

Step 3 On the Connections tab, click the Settings button. The Settings window appears. (See Figure 3-9.)

Step 4 In the Settings window, check the Use a proxy server for this connection check box to manually point the browser directly to a Content Engine. (See Figure 3-13.)

Figure 3-13 Manually Pointing a Browser Directly to a Content Engine

Step 5 In the Address field, enter the IP address of the Content Engine that you want this browser to point to.

This is the Content Engine that acts as the direct proxy server for this client browser, and the Content Engine to which the browser will directly send its content requests. For example, to specify the Content Engine that has an IP address of 172.16.10.10 as the direct proxy server, enter 172.16.10.10 into the Address field.

Step 6 In the Port field, enter the port number of the standalone Content Engine that will be the proxy server for this browser.

Note Use one of the port numbers that you specified as an incoming proxy port when you configured HTTP proxy caching on the standalone Content Engine (through the Setup utility as described in Step 12 of "Using the Setup Utility to Configure a Basic Configuration on a Standalone Content Engine", or by entering the http proxy incoming portnumber global configuration command). For instance, if port 8080 is specified as the incoming proxy port (http proxy incoming 8080 command), then enter 8080 as your port number in the Port field.

Step 7 Click OK.

Step 8 If NTLM is used in this environment to control user Internet access, you must change the default setting for user authentication in the client browser to prevent the user from being prompted by a popup window to log in every time the user attempts to access a new website.

For an example of how to change this default setting in Internet Explorer Version 6.0, see Step 5 .
Pointing Windows Media Players Directly to a Standalone Content Engine

If direct proxy routing is being used instead of WMT transparent redirection to direct client requests for WMT content directly to a standalone Content Engine, you must configure Windows Media Player on client desktops to point directly to the Content Engine (a nontransparent WMT proxy server for these web clients).

To explicitly configure Windows Media Player on client desktops to point directly to a specific standalone Content Engine, follow these steps:

Step 1 Open Windows Media Player on the client desktops.

Step 2 In the Windows Media Player menu bar, choose Tools > Options. The Options window appears.

Step 3 In the Options window, click the Network tab. (See Figure 3-14.)

Step 4 On the Network tab under Streaming protocols, click the Multicast, UDP, TCP and HTTP check boxes if they are not already selected.

Figure 3-14 Network Options Tab

f. On the Network tab, under Streaming proxy settings, choose MMS, and click Configure. The Configure Protocol window appears. (See Figure 3-15.)

Figure 3-15 Configure Protocol Window

g. Click the Use the following proxy server radio button.

h. In the Address field, enter the IP address of the Content Engine (the nontransparent WMT proxy server for this Windows Media player).

i. In the Port field, enter the port number on which the Content Engine will accept WMT incoming requests. Port 1755 is the default port for WMT incoming requests.

Note When you use the Setup utility to configure WMT proxy caching, the Content Engine automatically is configured to use the default port (port 1755) to accept incoming WMT requests.

j. Click OK to close the Configure Protocol window.

k. Click OK to close the Options window.

Pointing RealMedia Players Directly to a Standalone Content Engine

If direct proxy routing is being used instead of RTSP transparent redirection is being used to direct client requests for RTSP content directly to a standalone Content Engine, you must configure the RealMedia players (RealPlayer or RealOne player) on client desktops to point directly to this Content Engine (a nontransparent RealProxy server for these web clients).

To explicitly configure the RealMedia player (RealPlayer Version 8.02 or 9.0) on the client desktops to point directly to a specific standalone Content Engine as their RTSP proxy server, follow these steps:

Step 1 Open RealPlayer on the client desktop.

Step 2 From the RealPlayer menu, choose View > Preferences.

Step 3 Click the Proxy option under Category settings.

Step 4 Under Streaming Settings, click Change Settings.

Step 5 Click the Use proxies radio button.

Step 6 In the RTSP Proxy address field, enter the IP address of the standalone Content Engine that you have configured for RealMedia proxy caching.

Step 7 In the Port field, enter the port number on which the Content Engine will accept RTSP incoming requests.

Port 554 is the default port for RTSP incoming requests. When you use the Setup utility to configure RealMedia proxy caching, the Content Engine automatically is configured to use the default port (port 554) to accept incoming RTSP requests.

Step 8 Click OK.

Configuring WCCP Routers for Transparent Redirection

Remember that after you configure a standalone Content Engine for transparent proxy caching, you must configure the WCCP Version 2-enabled routers to intercept and redirect content requests transparently to this Content Engine. For information about how to configure the necessary WCCP service on a WCCP Version 2-enabled router, see Table 3-6.

Table 3-6 Configuring WCCP Routers to Support Transparent Proxy Routing of Content Requests

Transparent Caching
Using WCCP

Additional Information and Instructions

HTTP transparent caching

Configuring the Standard Web Cache Service (Service 0) on a Router

Configuring the Custom Web Cache Service (Service 98) on a Router

HTTP reverse proxy caching

Configuring the Reverse Proxy Service (Service 99) on a Router

WMT transparent caching

Configuring the MMSU Service (Service 82) on a Router

Configuring the MMST Service (Service 81) on a Router

RealMedia transparent
caching

Configuring the RTSP Service (Service 80) on a Router

Verifying the Basic Configuration

This section provides an example of how to verify the basic configuration on a standalone Content Engine. This is a sample scenario of how to verify the configuration of the web-cache service (HTTP transparent caching through WCCP) on a standalone Content Engine. In this scenario the following assumption applies:

•There is a single standalone Content Engine (Content Engine A) that has WCCP Version 2 enabled on it.

•There is a single WCCP Version 2-enabled router (Router A) that has been configured to redirect HTTP requests to Content Engine A (transparent proxy server).

•The HTTP transparent caching service has been enabled on Content Engine A, and Content Engine A is configured to accept redirected HTTP requests from Router A.

•The Client A and Client B browsers are not configured to point directly to Content Engine A.

•Client A and Client B are on the same subnet.

To verify that the web-cache service (HTTP transparent caching through WCCP) is working properly, follow these steps:

Step 1 From Client A, use the client browser to open various web pages on the Internet or your intranet. Request the pages more than once. The web servers you connect to must be on a different subnet than Client A, so that the HTTP requests that the Client A browser issues are routed to Router A.

Step 2 Using a login account that has administrator privileges (privilege level of 15), log in to the Content Engine CLI on Content Engine A.

For more information about how to log in to a standalone Content Engine through the Content Engine CLI, see the "Logging in to Standalone Content Engines" section.

Step 3 From Content Engine A, enter the show statistics http savings EXEC command to display the HTTP caching saving statistics for this Content Engine.
ContentEngineA# show statistics http savings
                         Statistics - Savings
                        Requests                          Bytes
         -----------------------------------------------------------
  Total:               525980242                    79047534484
   Hits:                 1966223                    19865155481
   Miss:               524014019                    59182379003
Savings:                     0.4 %                         25.1 %
Tip You can also display these statistics by choosing Reporting > Savings from the Content Engine GUI. For information about how to log in to the Content Engine GUI, see the "Logging in to the Content Engine GUI" section.

Step 4 From Content Engine A, enter the show statistics http requests EXEC command to display the number of HTTP requests that this Content Engine has received.
ContentEngineA# show statistics http requests
Step 5 From Client B, use the browser to request the same web pages that you just requested from Client A.

This step allows you to check whether Content Engine A is storing a copy of the requested web pages in its local cache instead of retrieving the web pages again from the origin web servers.

•The number of cache hits displayed in the output of the show statistics http savings command should increase as you use the Client B browser to request the same web pages that you just requested from Client A.

•The number of HTTP requests displayed in the output of the show statistics http requests command should increase as you use the Client B browser to request the same web pages that you just requested from Client A.

Step 6 On Router A, open a console or Telnet session.

Step 7 On Router A, enter the show ip wccp EXEC command to display statistics and status information for Router A.

The statistics should show a number greater than 0 for packets redirected. Also, check for hash assignments, which indicate at the very least that Content Engine A is registered and communicating with Router A.

Step 8 Check to see if Router A shows that packets are being redirected to Content Engine A.

•If Router A shows that there are packets being redirected to Content Engine A, the service (transparent redirection of HTTP requests) is operating properly on Content Engine A and Router A.

•If Router A shows that no packets are being redirected to Content Engine A, the web cache service is not operating properly. In this case, you should troubleshoot the problems with your configuration of the web cache service. The following are some examples of how to do this.

–From Content Engine A, enter the show wccp services EXEC command to display the list of WCCP services that are currently configured on Content Engine A. See if the standard web-cache service (Web Cache) is listed. Partial sample output is shown below.
ContentEngineA# show wccp services
Services configured on this Content Engine
        Web Cache
        RTSP
        FTP
ContentEngine#
–From Content Engine A, enter the show wccp routers EXEC command to display a list of WCCP-enabled routers that recognize Content Engine A. Check the command output to determine if Router A is on the list of WCCP-enabled routers that recognize Content Engine A. Partial sample output is shown below.
ContentEngineA# show wccp routers
Routers Seeing this Content Engine
                Router Id          Sent To
                10.0.0.0         10.1.1.1
        Routers not Seeing this Cache Engine
                10.1.1.1
        Routers Notified of but not Configured
                -NONE-
–From Content Engine A, enter the show wccp gre EXEC command to display WCCP generic routing encapsulation (GRS) packet-related information for Content Engine A. Check the command output to view the number of redirected packets that Content Engine A has rejected and accepted. See if the number of accepted packets is increasing as you continue to request web pages that are on web servers located on different subnets than the requesting client (Client A and Client B).
ContentEngineA# show wccp gre
Note For information about how to use the ACNS software logs for troubleshooting, see "Monitoring and Troubleshooting."

Modifying the Basic Configuration Through the Setup Utility

If you have previously run the Setup utility on a Content Engine, then when you subsequently launch the Setup utility manually (using setup privileged EXEC command), the current basic configuration for the standalone Content Engine appears. You can quickly change the current basic configuration through the Setup utility by entering y when prompted, as shown below.
Here is the current profile of this device
CDN device                  
No
HTTP Proxy Caching            : Yes
HTTP Tranparent Caching       : Yes
HTTP Reverse Proxy Caching    : Yes
WMT Proxy Caching             : Yes
WMT Transparent Caching       : Yes
Real Media Proxy Caching      : Yes
Real Media Transparent Caching: Yes
Do you want to change this (y/n) [n]:y
Performing Other Basic Tasks

After you have done a basic configuration on a standalone Content Engine, you can perform other basic tasks such as the following:

•Logging in to Standalone Content Engines

•Managing Administrative Login Accounts

•Removing or Replacing a Content Engine

•Configuring Content Preloading for Standalone Content Engines

•Saving the Current Configuration on Standalone Content Engines

•Disabling Transparent Caching Services on Standalone Content Engines

•Shutting Down Standalone Content Engines

•Removing or Replacing a Content Engine

Logging in to Standalone Content Engines

This section provides an overview of how to use any of the following methods to log in to a standalone Content Engine:

•Using Telnet or a Console Session to Log in to a Standalone Content Engine

•Using Secure Shell Version 1 or Version 2 to Log in to a Standalone Content Engine

•Using the Content Engine GUI to Log in to a Standalone Content Engine

The ACNS software comes with a single predefined login account (root administrator) that can be used to access the Content Engine initially and then to add other users to the system. This login account has superuser privilege rights (privilege level of 15). The username for this predefined login account is admin and the default password is default. If these defaults have been changed by another ACNS system administrator, you must obtain the new username and password.

Using Telnet or a Console Session to Log in to a Standalone Content Engine

To log in to a standalone Content Engine using Telnet or a console session, follow these steps:

Step 1 Log in to the Content Engine using Telnet or a console connected to the Content Engine serial port. For example, after starting a Telnet session, use the open command to specify the Content Engine that you want to log in to:
Microsoft Telnet> open IP_address_of_Content_Engine
Step 2 When prompted for a login, enter a username and password. (See Figure 3-16.)

Figure 3-16 Example of the Telnet Session Login Window

Step 3 After you have successfully logged in, the Content Engine CLI displays one of the following prompts depending on the privilege level of the login account:

•Privileged EXEC mode (privilege level of 15):
ContentEngine# 
•User EXEC mode (privilege level of 0):
ContentEngine> 
where ContentEngine is the host name of the Content Engine.

Figure 3-17 shows an example of the system prompt for privileged EXEC mode.

Figure 3-17 CLI System Prompt for Privileged EXEC Mode

Tip A Telnet session with the Content Engine can remain open and inactive for the interval of time specified by the exec-timeout global configuration command. The default timeout is 15 minutes; valid values are 0-44640 minutes. When the exec-timeout interval elapses, the Content Engine automatically closes the Telnet session.

Step 4 Use the Content Engine CLI commands to launch the Setup utility (enter the setup privileged EXEC command) or to use CLI commands to configure or monitor this standalone Content Engine.

See the "ACNS Software CLI Command Modes for Standalone Content Engines" section for a description of the different command modes you can work in when using the ACNS software CLI to configure or monitor a standalone Content Engine. See the "ACNS Software CLI Online Help and Keyboard Shortcuts" section for information about using online help and keyboard shortcuts.

Note The ACNS software device mode determines whether the device is functioning as a Content Engine, Content Distribution Manager, Content Router, or IP/TV Program Manager. The commands available from a specific CLI mode are determined by the ACNS software device mode in effect. The default device operation mode is Content Engine.

Step 5 To end the CLI session at any time, enter the logout or exit EXEC commands.

A Telnet session with the Content Engine can remain open and inactive for the interval of time specified by the exec-timeout global configuration command. The default timeout is 15 minutes; valid values are 0-44, or 640 minutes. When the exec-timeout interval elapses, the Content Engine automatically closes the Telnet session.

Using Secure Shell Version 1 or Version 2 to Log in to a Standalone Content Engine

Secure Shell (SSH) enables login access to the Content Engine through a secure and encrypted channel. SSH consists of a server and a client program. Like Telnet, you can use the client program to remotely log on to a machine that is running the SSH server, but unlike Telnet, messages transported between the client and the server are encrypted. The functionality of SSH includes user authentication, message encryption, and message authentication.

Before you enable the sshd command, use the ssh-key-generate global configuration command to generate a private and a public host key, which the client programs use to verify the server's identity.

When a user runs an SSH client and logs in to the Content Engine, the public key for the SSH daemon running on the Content Engine is recorded in the client machine known_hosts file in the user's home directory. If the Content Engine administrator subsequently regenerates the host key by issuing the ssh-key-generate command, the user must delete the old public key entry associated with the Content Engine in the known_hosts file before running the SSH client program to log in to the Content Engine. When the user runs the SSH client program after deleting the old entry, the known_hosts file is updated with the new SSH public key for the Content Engine.

Note The Telnet daemon can still be used with the Content Engine. SSH does not replace Telnet.

This example generates an SSH public key and then enables the SSH service.
Console(config)# ssh-key-generate
Ssh host key generated successfully
Saving the host key to box...
Host key saved successfully
Console(config)# sshd enable
Starting ssh daemon ..
Ssh daemon started successfully
Using the Content Engine GUI to Log in to a Standalone Content Engine

The Content Engine GUI (Figure 3-18) is the web portal for configuring a standalone Content Engine as a caching and streaming engine.

Figure 3-18 Content Engine GUI

Note The Content Engine GUI provides access to all of the administrative and operator functions that are accessible to the specific user logged in to the GUI.

After the ACNS software is installed on the Content Engine, use a standard web browser to log in and access the Content Engine GUI.

Before logging in to the Content Engine GUI, check that you have the following information:

•Name or IP address of the Content Engine that you want to log in to.

•Login account (username and password) that you want to log in to the Content Engine for configuration, monitoring, or troubleshooting purposes. If you do not have a login account, your ACNS system administrator must create one for you.

•Type of access enabled on the Content Engine GUI (secure or nonsecure).

Note For more information about enabling secure or nonsecure access to the Content Engine GUI, see the "Enabling or Disabling Access to the Content Engine GUI" section.

Enabling or Disabling Access to the Content Engine GUI

You can configure secure or nonsecure access to the Content Engine GUI. Secure access is the default. Either secure or nonsecure access to the Content Engine GUI is possible but not both. For example, if the secured Content Engine GUI is enabled (for example, https:// access on port 8003), then nonsecure access to the Content Engine GUI (for example, http:// access on port 8001) is not allowed.

To enable or specify the port number of the Content Engine GUI server, use the gui-server global configuration command.
ContentEngine(config)# gui-server {enable | port port |  
secure {enable | port port}}
•To enable secure access to the Content Engine GUI, use the gui-server secure enable port global configuration command.
ContentEngine(config)# gui-server secure enable port 8003
The port number can be between 1 and 65535. The default port for secure access to the GUI is 8003. In this example, secure access to the Content Engine GUI is enabled on the default port number 8003.

•To enable nonsecure access to the Content Engine GUI, use the gui-server enable port global configuration command.
ContentEngine(config)# gui-server enable port 8001
The port number can be between 1 and 65535. The default port for nonsecure access to the GUI is 8001. In this example, nonsecure access to the Content Engine GUI is enabled on the default port number 8001.

Note When secure or nonsecure access to the Content Engine GUI is enabled, you can access the GUI as described in the "Logging in to the Content Engine GUI" section.

To disable the Content Engine GUI, use the no gui-server global configuration command:

no gui-server {enable | port | secure {enable | port port}}

For example, if secure access to the Content Engine GUI is enabled on port 8003, enter the following command to disable it:
ContentEngine(config)# no gui-server secure enable port 8003
In the following example, nonsecure access to the Content Engine on port 8001 is being disabled:
ContentEngine(config)# no gui-server enable port 8001
Logging in to the Content Engine GUI

To log in to the Content Engine GUI, follow these steps:

Step 1 Start a web browser on a device that has access to the network on which the Content Engine resides.

Tip If you are using Microsoft Internet Explorer (IE), verify that Java, JavaScript, and Cascading Style Sheets are enabled on IE. If you are using Netscape, use Version 4.0 or later.

Step 2 In the web browser, enter the URL or IP address of the Content Engine. Append the port number.

The URL (location) of the Content Engine is determined during the installation of the ACNS software. If your network supports DNS and the IP address of the Content Engine has been added to your DNS table, you can access the Content Engine GUI by using the DNS name of the Content Engine.

The port number of the Content Engine GUI is determined when ACNS software is installed on the Content Engine. The default port number for nonsecure access is 8001. The default port number for secure access is 8003. Secure access to the Content Engine GUI is enabled on the default port number 8003. Note that HTTP is used for nonsecure access and HTTPS is used for secure access.

The following example shows the URL for accessing the Content Engine GUI in nonsecure mode if nonsecure mode is enabled on the default port (port 8001):
http://ContentEngine-name:8001
Alternatively, enter the IP address:
http://ContentEngine-IP-address:8001
The following example shows the URL for accessing the Content Engine GUI in secure mode if secure mode is enabled on the default port (port 8003):
https://ContentEngine-name:8003
Alternatively, enter the IP address:
https://ContentEngine-IP-address:8003
Step 3 If you specified secure access, then the Security Alert window appears. Click Yes to accept the security certificate. The Enter Network Password window appears.

Step 4 Enter your username in the Username field. Enter your password in the Password field and click OK.
Username: admin
Password: password
Step 5 After the system verifies the specified login information, the main window for the Content Engine GUI appears in your browser. If you are the default administrator, you should create login accounts for your ACNS system administrators or other ACNS administrative who need to access the Content Engine for configuration, monitoring, or troubleshooting purposes.

When you access the Content Engine GUI, it appears with a window (page) that is referred to as the Content Engine main window. (See Figure 3-19.)

Figure 3-19 Content Engine GUI Main Window

As Figure 3-19 shows, the Content Engine GUI has a set of tabs and buttons. For a descriptive list of menu options, see "Content Engine GUI Menu Options."

Tip The lock icon in the lower-right corner of the browser window indicates that the Content Engine GUI has been accessed in secure mode instead of nonsecure mode. For information about enabling secure or nonsecure access to the Content Engine GUI, see the "Enabling or Disabling Access to the Content Engine GUI" section.

Table 3-7 describes the main buttons of the Content Engine GUI and their associated function.

Table 3-7 Content Engine GUI Buttons

Button

Description

Clear

Removes all cacheable objects from the Content Engine memory and hard disks.

Reboot

Reboots the Content Engine.

Save Config

Saves the running system configuration to the startup system configuration.

Update

Applies the changes specified in the current Content Engine GUI window to the running system configuration.

Help

Displays context-sensitive help for the particular Content Engine GUI window. Click the Back button in the Help window to return to the Content Engine GUI window from which you launched the context-sensitive help.

Step 6 To return to the main window, click the words "Content Engine" in the upper-left corner of any Content Engine window (see Figure 3-20).

Figure 3-20 Content Engine GUI Navigation Bar

Step 7 To navigate to another window in the Content Engine GUI, click one of the tabs to display its subtabs. Click a subtab to choose it (see Figure 3-21).

Figure 3-21 Content Engine GUI Tabs and Subtabs

Logging out of the Content Engine GUI

To log out of the Content Engine GUI, follow these steps:

Step 1 Click the Update button to save any changes that you made in the current Content Engine window, or click Cancel to cancel these changes.

Step 2 Return to the Content Engine main window (Figure 3-18) by clicking the words "Content Engine" in the upper-left corner of the current Content Engine window.

Step 3 If you want to save any changes made during this current session before logging out, click the Save Config button in the Content Engine main window.

Step 4 Choose File > Close, or click the browser Close button.

Setting the System Clock

If you have an outside source on your network that provides time services (such as a Network Time Protocol [NTP] server), you do not need to set the system clock manually. When setting the clock, enter the local time. The Content Engine calculates Coordinated Universal Time (UTC) based on the time zone specified in the clock timezone global configuration command.

Two clocks exist in the system: the software clock and the hardware clock. The software uses the software clock. The hardware clock is used only at bootup to initialize the software clock.

To set or clear clock functions or update the calendar, use the clock EXEC command.

clock {read-calendar | set time day month year | update-calendar}

where:

read-calendar

Reads the calendar and updates the system clock.

set

Sets the time and date of the software clock.

time

Current time in hh:mm:ss format (hh: 00-23; mm: 00-59; ss: 00-59).

day

Day of the month (1-31).

month

Month of the year (January, February, March, April, May, June, July, August, September, October, November, December).

year

Year (1993-2035).

update-calendar

Updates the calendar with the system clock.

For example:
ContentEngine# clock set 13:32:00 01 February 2000
To set the summer daylight saving time and time zone for display purposes, use the clock global configuration command. To set and display the local and UTC current time of day without an NTP server, use the clock timezone global configuration command with the clock set EXEC command. The clock timezone parameter specifies the difference between UTC and local time, which is set with the clock set EXEC command. The UTC and local time are displayed with the show clock detail EXEC command.

Managing Administrative Login Accounts

A Content Engine that is running ACNS software comes with a single predefined superuser login account (root administrator). This predefined administrative login account can be used to access the Content Engine GUI initially in order to perform a basic configuration on a standalone Content Engine and then add other login accounts.

Note The username for this predefined superuser account is admin and the default password is default. If these defaults have been changed by another ACNS system administrator, you need to obtain the new username and password.

You must assign a privilege profile to each new administrative login account that you create on your standalone Content Engine. Privilege profiles determine which tasks an ACNS software administrators can perform, and the level of access granted to them based on the administrative login account that they used to log in to the Content Engine.

The two types of predefined privilege profiles are:

•Normal-level administrator—Privilege level of 0. Has read access, and can see some of the Content Engine configuration settings.

•Superuser administrator—Privilege level of 15. Has administrative privileges such as running the Setup utility, creating new administrative login accounts, and modifying any of the Content Engine configuration settings.

You can use the Content Engine GUI or CLI to change the password for this predefined superuser account or to create additional login accounts for other ACNS system administrators. After you have used the predefined superuser login account to perform a basic configuration on a standalone Content Engine, it is recommended that you change the password for this superuser login account. For information about adding or modifying an administrative login account, see the next section, "Adding or Modifying Administrative Login Accounts."

ACNS 5.x software also supports various login authentication methods (local, RADIUS, or TACACS+ authentication). This enables you to configure a standalone Content Engine to use one or more of these authentication methods when it processes an administrative login request. For more information, see "Configuring Administrative Login Authentication and Authorization on Standalone Content Engines."

Note Content authentication and authorization, which controls end users' access to the requested content that is served through a standalone Content Engine, is independent of the administrative login authentication and authorization for the Content Engine that controls the level of access for users who log in to the Content Engine for configuration, monitoring, or troubleshooting purposes. For information about content authentication and authorization, see "Configuring Content Authentication and Authorization on Standalone Content Engines."

Adding or Modifying Administrative Login Accounts

After you have used the predefined superuser login account to perform a basic configuration on a standalone Content Engine, we recommend that you change the password for this superuser login account.

From the Content Engine GUI, choose System > Users. Use the displayed Users window to modify a password for this predefined superuser login account. You can also use the Users window to create additional administrative login accounts (normal administrative user or superuser accounts). For information about using this window, click the HELP button to access context-sensitive help. For more information about accessing the Content Engine GUI, see the "Logging in to the Content Engine GUI" section.

To use the Content Engine CLI to add or modify an ACNS system administrative login account on a standalone Content Engine, follow these steps:

Step 1 Access the Content Engine CLI in global configuration mode.

Step 2 Configure the entries for the group name-based access list with the username global configuration command.
ContentEngine(config)# username name {cifs-password {0 plainword |1 lancrypto ntcrypto}| 
password {0 plainword | 1 cryptoword} uid uid} | privilege {0|15}}
Table 3-8 describes the parameters for the username global configuration command.

Table 3-8 Parameters for the username CLI Command

Parameter

Description

username

Sets the username for the administrative login account.

name

Username for the administrative login account.

cifs-password

Sets the Windows file-sharing user password.

0

Specifies that an unencrypted Windows file sharing password will follow.

plainword

Clear-text user Windows file sharing password.

1

Specifies that a hidden Windows file sharing password will follow.

lancrypto

Encrypted password for LAN Manager networks.

ntcrypto

Encrypted password for Windows NT networks.

password

Sets the user password for the administrative login account.

0

Specifies that an unencrypted user password will follow.

1

Specifies that a hidden user password will follow.

cryptoword

Encrypted user password.

uid

Sets the user ID for the password.

uid

Text password user ID (2001-65535).

uid

Sets the user ID for an encrypted password.

uid

Encrypted password user ID (2001-65535).

privilege

Sets the user privilege level of an ACNS network administrative login account.

0

User privilege level for a normal-level administrator (ACNS system administrative users who are not superusers).

15

User privilege level for ACNS system administrators who have superuser access.

This example shows how you can use the username EXEC command to modify passwords and privilege levels for administrative login accounts on a standalone Content Engine.
ContentEngine# show user username jrdoe
Uid                 : 2003
Username            : jrdoe
Password            : ghQ.GyGhP96K6
Privilege           : normal user
ContentEngine(config)# username jrdoe privilege 15
User's privilege changed to super user (=15) 
ContentEngine# show user username jrdoe
Uid                 : 2003
Username            : jrdoe
Password            : ghQ.GyGhP96K6
Privilege           : super user 
Configuring Content Preloading for Standalone Content Engines

This section provides an overview of content preloading for standalone Content Engines that are running ACNS software (Release 5.2 or later). It also provides instructions on how to configure this feature on a standalone Content Engine.

Preloaded content is content that is retrieved and stored on a standalone Content Engine because the administrator of that Content Engine scheduled a retrieval of specific content in anticipation of user requests for that content. Content preloading is done by configuring the standalone Content Engine to create a cache request for all the content located at the origin web server that stores the primary content.

You can specify bandwidth limits for the preload process to ensure that bandwidth consumption does not exceed the specified bandwidth limits during the preload process. During the preload process, the Content Engine scans websites several link levels down for content, retrieves the specified content, and stores it locally for future requests. At a specified time, the Content Engine scans several levels of websites to verify that its content is still current, and it updates any content that has changed.

ACNS 5.x software can read a file of URLs and preload the specified URL content on the standalone Content Engine. The following type of content can be preloaded on a standalone Content Engine: HTTP URLs, FTP-over-HTTP URLs, and MMS URLs (WMT streaming media files). This URL list is referred to as the "preload URL list file."

Note All configured HTTP, FTP-over-HTTP, and MMS parameters and rules apply to the preloaded objects.

In ACNS 5.1 software, support for preloading NTLM authenticated objects was added. This feature allows NTLM authenticated objects (authenticated objects that reside on the servers that authenticate NTLM only) to be preloaded on a Content Engine.

An entry in a URL list file has the following format:

URL [depth] [domain-name:host-name:host-domain-name]

hostname and host-domain-name can be null; however, the domain name is required if NTLM credentials have been configured. (The separator is required.)
http//www.cisco.com 3 apac::
If NTLM-related information is not present in the preload URL list file entry, the authentication scheme falls back to basic authentication.

By default, the Content Engine does not cache basic and NTLM authenticated objects. To enable a standalone Content Engine to fetch specific objects and cache these objects that are authenticated with any authentication scheme (basic authentication or NTLM authentication), issue the http cache-authenticated all global configuration command.
ContentEngine(config)# http cache-authenticated all
To configure the Content Engine to cache only NTLM authenticated objects, issue the http cache-authenticated ntlm global configuration command. The cached objects are tagged as "NTLM protected" so that subsequent requests for these same objects are subjected to authentication before the Content Engine can serve the content to the client.

Before you preload WMT streaming media files on the Content Engine, you must enable the WMT feature on your Content Engine. If you used the Setup utility to configure WMT caching (as described in Step 15 of the "Using the Setup Utility to Configure a Basic Configuration on a Standalone Content Engine") on your Content Engine, then WMT is already enabled on the Content Engine. Otherwise, see the "Enabling WMT on Standalone Content Engines" section for instructions on how to use the Content Engine CLI (instead of the Setup utility) to enable WMT on a standalone Content Engine before you enable the preloading of WMT streaming media files for this Content Engine.

Creating a Preload URL List File

The preload URL list file lists the URLs (HTTP, FTP-over-HTTP, or MMS URLs) to be preloaded on the Content Engine. This file is maintained by the administrator and must be created on a remote system. This file can be transferred to the standalone Content Engine for preloading access, or accessed from the remote server. The pre-load url-list-file path global configuration command specifies the path of this file.

Note In the pre-load url-list-file path global configuration command, the value for path can be a URL or a local file path.

You can place the list of URLs in a file on a local disk. You can also use the mkdir EXEC command to make a subdirectory that contains the preload URL list file. For instance, the mkdir /local1/preload-directory command creates a subdirectory called preload-directory on local disk /local1.

Each URL in the preload URL list file has an optional depth parameter. The depth parameter specifies how many levels down the preloading will be performed. For example, http://www.espn.com 3 means download http://www.espn.com and all content three levels deep. If the depth level is not specified, then the preload depth level default of 3 is used. The URLs are delimited with a carriage return as follows:
<cr>
. . . 
http://www.cnn.com  3 <cr>
ftp://ftp.lehigh.edu/  2 <cr>
mms://www.aol.com/<dir>/<streaming-file>
http://www.yahoo.com <cr>
. . .
<cr>
If you want to preload authenticated content to a Content Engine, the URL list file entry must be written as follows:
http://username:password@www.authenticatedsite.com/ depth level
When configuring a preload URL list file through the Content Engine CLI, the pre-load url-list-file global configuration command only had the HTTP or FTP option in ACNS 5.1.x software earlier than Release 5.1.5. There was no mechanism in place to fetch the preload URL list file securely.

In ACNS 5.1.5 software, the ability to fetch the preload URL file over HTTPS was added. If a preload URL list file contains usernames and passwords, organizations are now able to fetch the preload URL list file over HTTPS. Note that the actual preloading of HTTPS links is not supported; only the downloading of the preload URL list file through the HTTPS protocol.

Enabling and Configuring Content Preloading on Standalone Content Engines

You can enable and configure content preloading on a standalone Content Engine from either the Content Engine GUI or the CLI.

Note From the Content Engine GUI, choose Caching > Content Preload. Use the displayed Content Preload window to enable and configure this feature on this standalone Content Engine. For more information about how to use the Content Preload window to perform this task, click the HELP button in the window.

To use the Content Engine CLI to enable and configure content preloading on a standalone Content Engine, follow these steps:

Step 1 Use the pre-load enable global configuration command to enable content preloading on this standalone Content Engine.
ContentEngine(config)# pre-load enable
Step 2 Create the preload URL list file, as described in the "Creating a Preload URL List File" section.

Step 3 Use the pre-load concurrent-requests global configuration command to specify the maximum number of concurrent requests for the URL retrieval. You can specify a value from 1 to 30 (for example, 24). The default is 10. If the number of URLs in the preload URL list file is less than the number of specified concurrent requests, then the lesser number is active.
ContentEngine(config)# pre-load concurrent-requests 24
Step 4 Use the pre-load depth-level-default global configuration command to specify the default depth level for the URL retrieval (for example, four levels deep). You can specify a value from 0 to 20. The default is 3. Setting the depth level default to 0 would be useful if you have specified URLs in preload.txt files and you do not want the Content Engine to try to preload other URLs.
ContentEngine(config)# pre-load depth-level-default 4
Step 5 Use the pre-load url-list-file global configuration command to specify the path of the file that contains the URL list or a URL.
ContentEngine(config)# pre-load url-list-file path
where path is the path of the file that contains the URL list or a URL.

For example:
pre-load url-list-file /local1/myurllist
pre-load url-list-file ftp://ftpserver/ftpdirectory/urllist.txt
pre-load url-list-file http://server/directory/urllist.txt
pre-load url-list-file https://httpsserver/directory/urllist.txt
Note The actual preloading of HTTPS links is not supported; only the downloading of the preload URL list file through the HTTPS protocol, as shown in the preceding example.

Step 6 Use the pre-load fetch domain global configuration command to specify the domains to be fetched during the preload process (for example, cisco.com).
ContentEngine(config)# pre-load fetch domain cisco.com
Step 7 Use the pre-load traverse-other-domains global configuration command to specify that other domains in an HTML page should be traversed. By default, other domains in an HTML page are not traversed during the content preload.
ContentEngine(config)# pre-load traverse-other-domains
Step 8 Use the pre-load no-fetch suffix global configuration command to specify the suffixes to be excluded from the preload operation. This creates a filter for the objects that are to be excluded.
ContentEngine(config)# pre-load no-fetch suffix .mil .su .ca
Step 9 Use the pre-load max-bandwidth global configuration command to configure a maximum bandwidth for the preloading process (for example, 50,000 kbps).
ContentEngine(config)# pre-load max-bandwidth 50000
Note With ACNS 5.x software, you can preload WMT streaming media files that may have different bit rates at the URL specified for content preloading. You can also control WMT bandwidth and bit rates using the wmt max-bandwidth and wmt max-bitrate global configuration commands.

Step 10 To trigger a content preload immediately, enter the pre-load force EXEC command.

Step 11 To configure the Content Engine to preload specific content for a future time, use the pre-load schedule global configuration command. The Content Engine accesses the specified preload URL list file with a frequency set by the specified preloading schedule (set through the pre-load schedule global configuration command or the Content Engine GUI [Caching > Content Preloading]).

The default start time for the preloading operation is 00:00 (that is, the start of the day). If the end time is not specified, the preload operation is completed after all the objects have been downloaded. If you wish to change this default, note the following:

a. To specify the start and end times for daily or weekly preloads, use hh:mm (where hh is the hour, and mm is the minutes, for example, 01:00). For hourly preloads, use mm to specify the start and end times. The following example shows how to specify a daily interval for scheduling the content preload. In this example, the preload operation starts every day at 1:00 AM and ends every day at 2:00 AM.
ContentEngine(config)# pre-load schedule every-day  
start-time 01:00 end-time 02:00 
b. To specify the start time and end times for hourly preloads, the start time should be 0 and the end time should be 59. For daily and weekly preloads, the start time should be from 0 to 23, and the end time should be from 0 to 59. If the endtime option is not specified, the preload operation will continue until completion.
To configure a preload on more than one day of the week, use the pre-load schedule every-week global configuration command. The following example shows how to schedule a preload operation every week on Sunday and Wednesday from 1:00 AM to 6:00 AM.
ContentEngine#(config)# pre-load schedule every-week Sun Wed  
start-time 01:00 end-time 06:00
Step 12 Use the pre-load dscp global configuration command to set the Type of Service (ToS) value as well as the differentiated services code point (DSCP) for all preload traffic.

Setting the ToS or DSCP is called packet marking, allowing you to partition network data into multiple priority levels or types of service. You can set the ToS or DSCP values in IP packets based on a URL match, a file type, a domain, a destination IP address, a source IP address, or a destination port.

ACNS 5.x software includes ToS or DSCP support for HTTP, FTP, and MMS preload traffic. Because content preloading is initiated by the Content Engine and not by the requesting client when a connection is made to an origin server, the ToS or DSCP code point on the traffic going toward the server needs to be set before contact is made with the origin server.

This example shows how to set Type of Service support to normal.
ContentEngine(config)# pre-load set-tos normal
Note Using the pre-load dscp global configuration command takes precedence over any use of the Rules Template configuration commands involving DSCP server configurations.

Table 3-9 describes the DSCP values.

Table 3-9 DSCP Values

DSCP Value

Description

<0-63>

Valid DSCP value range

af11

Packets with AF11 dscp (001010)

af12

Packets with AF12 dscp (001110)

af13

Packets with AF13 dscp (001110)

af21

Packets with AF21 dscp (011010)

af22

Packets with AF22 dscp (010110)

af23

Packets with AF23 dscp (010110)

af31

Packets with AF31 dscp (011010)

af32

Packets with AF32 dscp (011110)

af33

Packets with AF33 dscp (011110)

af41

Packets with AF41 dscp (110010)

af42

Packets with AF42 dscp (110110)

af43

Packets with AF43 dscp (110110)

cs1

Packets with CS1 (precedence 1) dscp (001100)

cs2

Packets with CS2 (precedence 2) dscp (011000)

cs3

Packets with CS3 (precedence 3) dscp (011100)

cs4

Packets with CS4 (precedence 4) dscp (110000)

cs5

Packets with CS5 (precedence 5) dscp (101100)

cs6

Packets with CS6 (precedence 6) dscp (111000)

cs7

Packets with CS7 (precedence 7) dscp (111100)

default

Packets with default dscp (000000)

ef

Packets with EF dscp (101110)

Table 3-10 describes the TOS values.

Table 3-10 TOS Values

TOS Value

Description

<0-127>

Valid ToS value range

critical

Packets with critical precedence (110)

flash

Packets with flash precedence (48)

flash-override

Packets with flash override precedence (64)

immediate

Packets with immediate precedence (32)

internet

Packets with internetwork control precedence (96)

max-reliability

Packets with maximum reliable ToS (2)

max-throughput

Packets with maximum throughput ToS (4)

min-delay

Packets with minimum delay ToS (8)

min-monetary-cost

Packets with minimum monetary cost ToS (1)

network

Packets with network control precedence (112)

normal

Packets with normal ToS (0)

priority

Packets with priority precedence (16)

Step 13 Use the show pre-load EXEC command to view the status of the current preloading operation.

This example shows the status of the current preloading operation after using the pre-load set-tos and pre-load max-bandwidth commands.
ContentEngine# show pre-load
Preloading is enabled
Number of concurrent sessions: 10
Depth level: 4
URL List File: /local1/url.txt
DSCP: set-tos normal 
Max Bandwidth: 50000 Kbps
Previous preloading operation will be continued.
Preload will not traverse other domains.
Fetch Domains: 
Fetch Suffix: 
Fetch Directory: 
No-fetch Domain: 
No-Fetch Suffix: 
No-Fetch Directory: 
Scheduling on all days
	Start Time: 00:00
	End Time  : Till completion
Step 14 After the preload has started, use the show statistics pre-load EXEC command to view the statistics associated with the current preloading.
ContentEngine# show statistics pre-load
Statistics of last Preloading operation
---------------------------------------
Preloading is in progress.
List of preloaded URLs are in /local1/preload_dir/downloaded_urls.
83 objects downloaded, 2842292 bytes transferred.
Step 15 Inform your end users what the URLs of the preloaded files are so that they can use their browsers or media players to access this preloaded content.

For an example of how you can verify if the preloaded VOD files are being cached and properly distributed to clients, see the "Verifying That Preloading WMT VOD Files Are Cached and Properly Distributed to Clients" section.

Stopping or Resuming Content Preloading on Standalone Content Engines

Use the no pre-load enable global configuration command to stop a preload process that is currently in progress on a standalone Content Engine.

If the content preloading is not completed before the scheduled end time, you can resume the preloading process to capture content using the pre-load resume global configuration command. Using this command allows you to resume downloading from the breakpoint of the previous preload, instead of starting again from the very beginning of the preload URL list file.

Note If the pre-load resume global configuration command is not set up on the Content Engine and content preloading is aborted before the scheduled end time, the next scheduled content preloading starts from the beginning of the preload URL list file.

Saving the Current Configuration on Standalone Content Engines

A standalone Content Engine has two types of system configuration:

•Startup system configuration that is stored in nonvolatile memory

•Running system configuration

To use the Content Engine CLI to save the current running configuration as the startup configuration, use the copy running-config global configuration command. The running system configuration can be saved to the sysfs partition, flash memory, or TFTP server. For example, enter the following to save the running configuration to flash memory:
ContentEngine (config)# copy running-config startup-config
Note The copy running-config startup-config command is equivalent to the write memory command.

To save the current configuration during a Setup utility session, enter y when asked if you want to save the current configuration.

Disabling Transparent Caching Services on Standalone Content Engines

To disable transparent caching on a standalone Content Engine in a WCCP environment without powering down the Content Engine, disable the running version of WCCP on the Content Engine by entering the no wccp version global configuration command (for example, use the no wccp version 2 command to disable WCCP Version 2). The Content Engine will still service proxy-style requests, if so configured, and preserve its configuration settings.

Shutting Down Standalone Content Engines

A controlled shutdown is used to refer to the process of properly shutting down a Content Engine without turning off the power on the device. With a controlled shutdown, all of the application activities and the operating system are properly stopped on a standalone Content Engine but the power is still on. Controlled shutdowns of a standalone Content Engine can help you minimize the downtime when the Content Engine is being serviced.

Caution If a controlled shutdown is not performed, the Content Engine file system can be corrupted. It also takes longer to reboot the Content Engine if the Content Engine is not properly shut down.

In ACNS Release 5.2.1, the shutdown EXEC command was added. This command enables you to shut down and optionally power off a Content Engine.

•"Shutdown" means that all application activities (applications and operating system) are stopped, but the power is still on. This is a shutdown only, and is similar to the Linux halt command.

•"Shutdown poweroff" means that the Content Engine is powered down by the ACNS software (Release 5.2.1 or later) after being shut down. This operation is also referred to as a "software poweroff." The implementation of the shutdown poweroff feature uses the advanced configuration and power interface (ACPI) power management interface.

When a shutdown poweroff is performed on a standalone Content Engine, these conditions result:

–All application activities are stopped on the Content Engine, and the Content Engine is shut down through the ACNS software.

–Power is turned off through a software power off.

–The fan is not running; however, the power LED is flashing on the Content Engine.

Note Content Engines cannot be powered on again through software after a software poweroff. You must press the power button once on these Content Engines to bring these Content Engines back online.

Table 3-11 describes the shutdown-only operation and the shutdown poweroff operation for standalone Content Engines.
Table 3-11 Shutting Down Standalone Content Engines Through CLI Commands
Activity

All Content Engine Models
Supported in ACNS 5.2 Software

Content Engines with
Power Management Capability
in ACNS Release 5.2
User performs a
shutdown operation on
the Content Engine
Shutdown only
ContentEngine# shutdown
Shutdown poweroff
ContentEngine# shutdown poweroff
User intervention to
bring Content Engine
back online

To bring a Content Engine that has an on/off switch on the back (for example, the CE-507, CE-507AV, CE-560, CE-560AV, or the CE-590) back online after a shutdown operation, turn the on/off switch twice.

To bring a Content Engine that has a power button (instead of an on/off switch on the back) back online after a shutdown operation: first press and hold the power button for several seconds to power off these models, and then press the power button once again.

After a shutdown poweroff, you must press the power button once to bring the Content Engine back online.

File system check

Will not be performed after you turn the power on again and reboot the Content Engine.

Will not be performed after you turn the power on again and reboot the Content Engine.
All of the Content Engine models that are supported in the ACNS 5.2 release support this new shutdown feature (the shutdown EXEC command). However, the shutdown poweroff feature (the shutdown poweroff EXEC command) is only supported on the newer Content Engine models that support the power management capability (for example, the CE-510, CE-510A, CE-511, CE-511A, CE-565, CE-565A, CE-566, CE-566A, CE-7305, CE-7305A, CE-7320, and the CE-7325).

Note Refer to the Release Notes for Cisco ACNS Software, Release 5.2 for a list of hardware platforms that are supported in ACNS software, Release 5.2.

The shutdown EXEC command is supported in all device modes (Content Distribution Manager, Content Engine, Content Router, and IP/TV Program Manager). For a description of how to use the shutdown EXEC command with a standalone Content Engine (a Content Engine that is not registered with a Content Distribution Manager), see the next section, "Shutting Down Standalone Content Engines from the Command Line." For information about how to use the shutdown EXEC command with other types of devices (for example, a Content Distribution Manager, a Content Engine that is registered with a Content Distribution Manager, or a Content Router), refer to the Cisco ACNS Software Command Reference, Release 5.2 publication.

Shutting Down Standalone Content Engines from the Command Line

You can enter the shutdown EXEC command from a console session or from a remote session (Telnet or SSH Version 1 or Version 2) to shut down a standalone Content Engine.

To perform a shutdown on a standalone Content Engine, follow these steps:

Step 1 From the Content Engine CLI command line, enter the shutdown EXEC command.
ContentEngine# shutdown
Step 2 When you are asked if you want to save the system configuration, enter yes.
System configuration has been modified. Save?[yes]:yes
Step 3 When you are asked if you want to proceed with the shutdown, press Enter to proceed with the shutdown operation.
Device can not be powered on again through software after shutdown.
Proceed with shutdown?[confirm]
A message appears, reporting that all services are being shut down on this Content Engine.

Shutting down all services, will timeout in 15 minutes.

shutdown in progress ..System halted.
Step 4 After the system is shut down (the system has halted), an ACNS software shutdown shell displays the current state of the system (for example, "System has been shut down") on the console. You are asked whether you want to perform a software power off (the Power down system by software option), or if you want to reload the system through the software.
================= SHUTDOWN SHELL =================
System has been shut down.
You can either
   Power down system by pressing and holding power button
or
1. Reload system through software
2. Power down system through software
Step 5 To power down the Content Engine, press and hold the power button on the Content Engine, or use one of the following methods to perform a shutdown poweroff:

•From the console command line, enter 2 when prompted, as follows:
================= SHUTDOWN SHELL =================
System has been shut down.
You can either
   Power down system by pressing and holding power button
or
1. Reload system through software
2. Power down system through software
•From the Content Engine CLI, follow these steps:

a. Enter the shutdown poweroff EXEC command.
ContentEngine# shutdown poweroff 
b. When you are asked if you want to save the system configuration, enter yes.
System configuration has been modified. Save?[yes]:yes
c. When you are asked to confirm your decision, press Enter.
Device can not be powered on again through software after poweroff.
Proceed with poweroff?[confirm]
Shutting down all services, will timeout in 15 minutes.
poweroff in progress ..Power down.
Shutting Down and Rebooting Standalone Content Engines from the Content Engine GUI

You can use the Content Engine GUI to perform a controlled shutdown on a standalone Content Engine. The Content Engine performs a controlled shutdown and then restarts the operating system on the Content Engine.

The Content Engine releases all WCCP connections to a router during the reboot process if these conditions exist:

•The Clean WCCP shutdown check box is checked in the main window of the Content Engine GUI.

•WCCP Version 2 is enabled on the Content Engine.

To use the Content Engine GUI to perform a controlled shutdown on a standalone Content Engine, follow these steps:

Step 1 From the Content Engine GUI, click the Reboot button in the Content Engine main window (Figure 3-18).

Step 2 The Content Engine performs the controlled shutdown and then restarts the operating system on the Content Engine.

Step 3 To reboot this standalone Content Engine, click the Reboot button in the Content Engine main window.

Tip If the Content Engine main window (Figure 3-18) is not currently displayed in your browser, click the words "Content Engine" in the upper-left corner any Content Engine GUI window to return to the Content Engine main window.

Step 4 When you are prompted to confirm your decision, click OK to begin rebooting this standalone Content Engine.

Removing or Replacing a Content Engine

Refer to the Content Engine hardware documentation for instructions on physically removing a Content Engine from an active network.

The router and the Content Engine are in constant communication when WCCP is enabled; thus, when the router notices that the Content Engine is no longer responding to it, the router stops sending requests to the Content Engine. This is transparent to users. If other Content Engines are attached to the router, the router continues sending requests to the other Content Engines.