Cisco ACNS Software Configuration Guide for Locally Managed Deployments, Release 5.5 - Chapter 4: 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 9 Players Directly to a Standalone Content Engine for WMT RTSP Requests

Pointing Windows Media Players Directly to a Standalone Content Engine for WMT MMS Requests

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

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

Secure File Transfer Protocol Access for Nonadministrative Users

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

Getting Started

This chapter provides an overview of how to configure, monitor, and troubleshoot standalone Content Engines that are running the ACNS 5.4.1 software and later releases. 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 4-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

•Logging in to Standalone Content Engines

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).

After you have done a basic configuration on a standalone Content Engine, you can perform other basic tasks such as the setting the system clock, managing login accounts, and managing and monitoring disks. For more information on this topic, see Chapter 5, "Performing Other Basic Tasks for Standalone Content Engines."

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

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 4-1 shows a high-level view of a typical workflow for configuring, monitoring, and troubleshooting a standalone Content Engine. Table 4-1 provides a checklist of tasks for completing the workflow that is shown in Figure 4-1.

Note As the legend in Figure 4-1 indicates, more detailed flowcharts are provided for configuring conventional caching services (Figure 4-2) and RealMedia streaming and caching services (Figure 4-3).

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

Figure 4-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 Chapter 7, "Configuring Conventional Caching Services for Standalone Content Engines."

This chapter describes how to use the Setup utility to configure the following two commonly used WMT MMS 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, other WMT RTSP services on a standalone Content Engine, see Chapter 9, "Configuring WMT Streaming Media Services on Standalone Content Engines."

Figure 4-3 Detailed View of Configuring RealMedia Streaming and Caching Services for Standalone Content Engines

This chapter describes how to use the Setup utility to configure the following two commonly used RealMedia 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 RealMedia services (for example, RealProxy live splitting) on standalone Content Engines, see Chapter 8, "Configuring RealMedia Services on Standalone Content Engines."

Checklist for Configuring, Monitoring, and Troubleshooting Standalone Content Engines

Table 4-1 is a checklist of tasks for configuring, monitoring, and troubleshooting standalone Content Engines that are running the ACNS 5.4.1 software and later releases.

Table 4-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, see the Cisco ACNS Software Command Reference, Release 5.5 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 RealMedia streaming services) running on standalone Content Engines, see the following chapters in this guide:

•Chapter 7, "Configuring Conventional Caching Services for Standalone Content Engines"

•Chapter 8, "Configuring RealMedia Services on Standalone Content Engines"

•Chapter 9, "Configuring WMT Streaming 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)

–RealMedia streaming and caching services

–WMT streaming and caching services

See the "Overview of Configuring Conventional Caching Services" section on page 7-2.

See Chapter 8, "Configuring RealMedia Services on Standalone Content Engines."

See Chapter 9, "Configuring WMT Streaming Media Services on Standalone Content Engines."

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 on page 6-27.

For Layer 4 switching, see the "Configuring Layer 4 Switching as a Redirection Method" section on page 6-50.

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 4-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 Chapter 10, "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 Chapter 11, "Configuring Content Preloading and 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 Chapter 12, "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 Chapter 13, "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).

Chapter 15, "Configuring Advanced Transparent Caching Features on Standalone Content Engines"

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

Chapter 16, "Configuring Additional Network Interfaces and Bandwidth on Standalone Content Engines"

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

Chapter 16, "Configuring Additional Network Interfaces and Bandwidth on Standalone Content Engines"

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

Chapter 17, "Configuring Administrative Login Authentication and Authorization on Standalone Content Engines"

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

Chapter 18, "Configuring AAA Accounting on Standalone Content Engines"

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

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

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

Chapter 20, "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 "Monitoring the Performance of Specific URLs" section on page 21-52.

Monitor and troubleshoot

23. Monitor this standalone Content Engine
with SNMP, the ACNS software alarms, and the ACNS software logs.

Chapter 21, "Monitoring Standalone Content Engines and Transactions"

24. Use the traceroute and the other supported diagnostic tools for troubleshooting.

Chapter 22, "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 the ACNS 5.4 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 4-2]).

•Case 2—The device is a standalone Content Engine with some basic configuration (for example, the Content Engine was upgraded to the ACNS 5.4 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 (see "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 4-2 lists the commonly used caching services that you can quickly configure on a standalone Content Engine through the Setup utility.

Table 4-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 4-2 for a description of these services).

•After you respond to the series of basic configuration questions, a menu-based interface appears.
           +-----------------------------------------------------+
           ¦                      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
For a list of the Setup utility menu options, see Table 4-3.
•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 4-3.) After you use the Setup utility to specify a specific basic configuration setting, a list of configured CLI commands appears (see example). 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 media file system (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 example) 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 4-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, see the Cisco ACNS Software Command Reference, Release 5.4 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 4-2) and other features are provided in subsequent 
chapters of this guide. 
Table 4-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 4-4 describes the keys and arrows that you can use with the Setup utility.
Table 4-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 the 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 in the "Using the Setup Utility to Configure a Basic Configuration on a Standalone Content Engine" section.

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 in the "Using the Setup Utility to Configure a Basic Configuration on a Standalone Content Engine" section).
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 4-4,) 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 4-4)

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

Figure 4-4 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.

The 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. For more information on this topic, see the "Mounting to a Network Attached Storage Device" section on page 5-13.

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. For more information see the "Using Telnet or a Console Session to Log in to a Standalone Content Engine" 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 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 the 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 "Using Telnet or a Console Session to Log in to a Standalone Content Engine" section. For more information about the different CLI modes, see the "ACNS Software CLI Command Modes for Standalone Content Engines" section on page B-8.

Step 2 Launch the Setup utility manually to configure one or more of the commonly used caching services (listed in Table 4-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. For more information about using a console connection, see the "Using Telnet or a Console Session to Log in to a Standalone Content Engine" section.

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 2 Press Enter.

Step 3 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 4 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 5 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 6 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. (For detailed instructions, see the "Automatically Launching the Setup Utility" section.)

–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 the ACNS 5.4 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.