Cisco Internet CDN Software Configuration Guide
Chapter 3--Configuring CDN Devices
Download this chapter
Chapter 3--Configuring CDN DevicesChapter 3--Configuring CDN Devices
give_us_feedback

Table of Contents

Configuring CDN Devices

Configuring CDN Devices

Cisco Internet CDN Software is already installed on your CDN devices. This chapter tells you how to use the Internet CDN software to configure these devices on your network.

This chapter contains the following sections:

Content Services Switch Wiring Configuration

Content Services Switches are an optional component of the Cisco Internet CDN.

Before you attempt to configure your Content Services Switch, you must decide how your switch and the Content Engines located behind it will be connected to the switch and to the rest of the CDN.

Your Content Services Switch can be connected as follows:

  • Directly to the Content Engines

  • To a Catalyst switch with connections to the Content Engines

  • To a Catalyst switch with connections to the Content Engines and to a redundant Content Services Switch

In addition to the various physical wiring configurations available to you, Content Services Switches also support the deployment of multiple virtual LANs (VLANs), an arrangement that provides additional address space for Content Engines grouped behind Content Services Switches in deployments in which more than one Content Services Switch is deployed on the same CDN.

See the wiring diagrams that follow for more information on the different options available to you when configuring your Content Services Switch and structuring your Content Delivery Network. Also see the "Gathering Device Configuration Information" section for information on the configuration information you need to have before beginning configuration of the Content Services Switch.

Figure 3-1 illustrates deployment of redundant Content Services Switches on a CDN connected to Content Engines through a Catalyst switch, with a second VLAN (VLAN3) assigned to the uplink connection.

In Figure 3-1, both the master Content Services Switch and the backup Content Services Switch are connected using a crossover Ethernet cable connected to interface 1 on each switch. These devices communicate using unique redundancy addresses assigned to VLAN2, the default redundancy subnet.


Figure 3-1: Redundant Content Services Switches Connected to a Catalyst Switch with Two VLANs


Primary communication among the Content Services Switch, Catalyst switch, and Content Engines takes place on VLAN1, the default VLAN for the switch. Connections for VLAN1 are made to any Content Services Switch interface after interface 2.

VLAN3 is configured for the uplink connection from the Content Services Switch to the uplink subnet using interface 2 on both the master and the backup Content Services Switch.

Figure 3-2 illustrates deployment of redundant Content Services Switches on a CDN connected to Content Engines through a Catalyst switch, with a single VLAN (VLAN1) assigned to both internal communication and the uplink connection.

In Figure 3-2 both the master Content Services Switch and the backup Content Services Switch are connected using a crossover Ethernet cable connected to interface 1 on each switch. These devices communicate using unique redundancy addresses assigned to VLAN2, the default redundancy subnet.


Figure 3-2: Redundant Content Services Switches Connected to a Catalyst Switch with One VLAN


Primary communication among the Content Services Switch, Catalyst switch, and Content Engines takes place on VLAN1, the default VLAN for the switch. Connections for VLAN1 are made from any Content Services Switch interface after interface 2.

VLAN1 is also assigned to the uplink connection from the Content Services Switch to the uplink subnet using interface 2 on both the master and the backup Content Services Switch.

Figure 3-3 illustrates deployment of a nonredundant Content Services Switch on a CDN connected to Content Engines through a Catalyst switch, with a second VLAN (VLAN3) assigned to the uplink connection.

Primary communication among the Content Services Switch, Catalyst switch, and Content Engines takes place on VLAN1, the default VLAN for the switch. Connections for VLAN1 are made from any Content Services Switch interface after interface2.


Figure 3-3: Nonredundant Content Services Switch Connected to a Catalyst Switch with Two VLANs


VLAN3 is configured for the uplink connection from the Content Services Switch and the uplink subnet using interface 2 on both the master and the backup Content Services Switch.

Figure 3-4 illustrates deployment of a nonredundant Content Services Switch on a CDN connected directly to Content Engines through a Catalyst switch, with a second VLAN (VLAN3) assigned to the uplink connection (interface 2) on the Content Services Switch.

Primary communication among the Content Services Switch and Content Engines takes place on VLAN1, the default VLAN for the switch. Connections for VLAN1 are made from any Content Services Switch interface after interface 2.


Figure 3-4: Nonredundant Content Services Switch Connected to Content Engines with Two VLANs


Configuring the Content Services Switch

If you are deploying a Content Services Switch and will be creating supernodes that use the switch, you must set up the switch before configuring your Content Engines, creating supernodes, or creating Content Engine clusters.

See the "Configuring a Content Engine" section for information on configuring the Content Engines that will be grouped behind the switch. Also, refer to the "Activating and Defining Content Routers and Content Engines" and "Adding Supernodes and Content Engine Clusters" sections in Chapter 2 of the Cisco Internet CDN Software User Guide for information on activating Content Engines once they are configured, and on creating supernodes containing Content Engine clusters.

Before attempting to configure your Content Services Switch, make sure that you have reviewed the "Gathering Device Configuration Information" section.

Configuring the Content Services Switch Using the Configuration Script

In order to facilitate Content Services Switch configuration, we provide a configuration script that walks you through the steps required to properly configure your Content Services Switch for use with Cisco Internet CDN Software. This script uses simple prompts to collect the information necessary to configure a Content Services Switch.

It is also possible to manually configure your switch without using the script. See the "Manually Configuring the Content Services Switch" section for instructions on manually configuring a Content Services Switch.

The setup script can be uploaded to the Content Services Switch manually or through the Content Distribution Manager user interface. From the Content Distribution Manager user interface, click Tools and choose Content Services Switch from the drop-down list. For more information on using the Content Distribution Manager user interface to upload the script, see the "Updating the Software on a Content Services Switch" section in Chapter 4 of the Cisco Internet CDN Software User Guide.

Use the following procedure to manually install and run the Content Services Switch configuration script.

Preparing the Content Services Switch and Uploading the Script

Before you can run the Content Services Switch setup script, you must first place the script on the Content Services Switch you wish to configure. In order to do this, you must:

  • Access the Content Services Switch device by connecting a terminal to the device, or using terminal emulation software installed on a desktop workstation.
  • Enable the File Transfer Protocol (FTP) on the Content Services Switch on which you will be running the setup script.

  • Access the Content Distribution Manager by connecting a terminal to the device, or using terminal emulation software installed on a desktop workstation.

  • Transfer the setup script from the Content Distribution Manager to the Content Services Switch using FTP.

Use the following procedure to upload the setup script from the Content Distribution Manager to the Content Services Switch:

Step 1   Log in to the Content Services Switch using the login admin and password system.

Step 2   Enter configuration mode by entering the configure command, as follows:

# configure

The # prompt changes to (config)#, indicating that you are in configuration mode.

Step 3   To enable FTP on the switch, enter the no restrict ftp command. For example:

(config)# no restrict ftp

Step 4   Exit configuration mode by entering the exit command, and then exit the Content Services Switch command-line interface by entering the exit command at the prompt. For example:

(config)# exit

# exit

Step 5   Log in to the Content Distribution Manager using the login admin and password default.

Step 6   Navigate to the /cisco/merlot/etc directory on the Content Distribution Manager. 

cdm-device-name> cd cisco/merlot/etc

Step 7   Locate the file merlot-css-setup. This is the Content Services Switch setup script.

Step 8   Launch FTP on the Content Distribution Manager and connect to the Content Services Switch. You need to provide a user login and password for the Content Services Switch. For example:

cdm-device-name> ftp Content Services Switch IP address
name: admin

password: system

Step 9   Navigate to the /script directory on the Content Services Switch. The setup script must be placed in the /script directory to work properly.

ftp> cd script

Step 10   Transfer the merlot-css-setup script file from the Content Distribution Manager to the Content Services Switch.

ftp> put merlot-css-setup

Step 11   If you are configuring a redundant Content Services Switch, repeat Step 8 through Step 10 for the redundant switch.

Step 12   Exit FTP by entering quit at the ftp prompt. You are returned to the Content Distribution Manager prompt.

Step 13   Exit the Content Distribution Manager command-line interface by entering the exit command.

You are now ready to log on to the Content Services Switch and begin setup of the device using the merlot-css-setup script. See the next section for details on running the Content Services Switch setup.

Running the Content Services Switch Setup Script

Use the following procedure to guide you in using the merlot-css-setup script. Entering q (quit) at any time aborts the setup procedure, saving any configuration settings already changed by the script.

Step 1   Log in to the Content Services Switch using the login admin and default password.

Step 2   From the prompt, discard any existing configuration settings using the clear running-config command as follows:

css-device-name> clear running-config

Step 3   From the prompt, launch the setup script by entering the following command:

css-device-name> script play merlot-css-setup

Step 4   When prompted to continue with setup, enter y (yes).

No startup-config was found, continue with the setup script [y/n]? y

Step 5   When prompted to indicate the number that will be used to identify the VLAN for the configuration and internal subnet, enter a number between 1 and 4095.

  • If you are using a Cisco Catalyst switch on your CDN, as well as the Content Services Switch, make sure that the VLAN number you choose is consistent with the number assigned to the same VLAN on the Catalyst switch.

  • If you are not deploying a Catalyst switch, choose any number that suits you. The default VLAN number is 1. Make sure that subsequent VLANs on this device are assigned different numbers.

Step 6   When prompted to identify the interfaces (or ports) that are assigned to this VLAN, enter the interface number in the proper format for the switch that you are configuring:

  • For CS-800 model switches, enter the slot and interface number for each interface. For example, if interfaces 1 and 2 on slot 2 belong to this VLAN, you would enter:

    2/1 2/2
  • For CS-500 model switches, enter the interface number in the format ethernet-x, where x is the number of the interface. For example, if interfaces 5, 6, and 7 belong to this VLAN, you would enter:

    ethernet-5 ethernet-6 ethernet-7
  • If you are unsure of the proper format for the device you are configuring, enter q to quit the setup script and then enter the show interface command to display information about your interfaces in the proper format. 

    css-device-name> show interface

Step 7   When prompted, enter the configuration IP address and subnet mask for the Content Services Switch. For example:

What is the CONFIGURATION address of this CSS? [default = 192.168.0.1] 
10.89.1.3

 
What is the CONFIGURATION subnet mask of this CSS? 
[default = 255.255.0.0] 255.255.240.0

Step 8   When prompted, enter the default gateway for the Content Services Switch. For example:

What is the default gateway of this CSS? [default = 
192.168.0.1] 10.89.0.1

Step 9   When prompted, enter the internal subnet and internal subnet mask for the Content Services Switch. For example:

What is the INTERNAL SUBNET of this CSS? [default = 192.168.0.0] 
192.168.1.0

The Content Services Switch setup script automatically sets the internal IP address (also referred to as the hidden address in the script) to the first available address in the subnet. For example, 

The hidden address of this CSS is set to the first address of this 
CSS: 192.168.1.1

 
What is the INTERNAL subnet mask of this CSS? [default = 255.255.0.0] 
255.255.255.0

Step 10   When prompted, indicate whether you will be designating a separate VLAN for the uplink connection from the device to your CDN. For example:

Do you want a separate VLAN for the uplink? [y/n]? y

Step 11   Perform one of the following actions:

  • If you are not configuring a separate uplink VLAN, proceed to Step 13.

  • If you are configuring a separate VLAN for the uplink interface, enter a number between 1 and 4095 to identify the VLAN. For example: 

    What is the number [1-4095] of this VLAN? [default = 3] 200

Step 12   When prompted, identify the interfaces (or ports) that are assigned to the uplink VLAN; enter the interface number in the proper format for the switch that you are configuring:

  • For CS-800 model switches, enter the slot and interface number for each interface. For example, if interface 2 on slot 1 belongs to the uplink VLAN, you would enter:

    1/2
  • For CS-500 model switches, enter the interface number in the format ethernet-x, where x is the number of the interface. For example, if interface 2 belongs to the uplink VLAN, you would enter:

    ethernet-2
  • If you are unsure of the proper format for the device you are configuring, enter q to quit the setup script and then enter the show interface command to display information about your interfaces in the proper format. 

    css-device-name> show interface

Step 13   When prompted, enter the uplink IP address and subnet mask for the Content Services Switch. These are used by the Content Services Switch to communicate with the uplink subnet. For example:

What is the UPLINK IP address of this CSS? [default = 192.168.0.1] 
192.168.128.12

 
What is the subnet mask of the UPLINK? [default = 255.255.0.0] 
255.255.128.0

Step 14   When prompted to indicate whether you will be deploying a redundant Content Services Switch, enter y (yes) or n (no), depending on your own network configuration. For example:

Is this a redundant CSS configuration? [y/n]? y
Note   Enter y even if the Content Services Switch you are configuring is the master Content Services Switch. The setup program prompts you to configure the backup switch after you configure the master switch.

Redundancy addresses are configured on virtual LAN 2 (VLAN2).

Step 15   If you are not configuring a redundant Content Services Switch, you have successfully configured the Content Services Switch. The setup script ends, returning you to the Content Services Switch prompt.

If you are configuring a redundant Content Services Switch, continue with
Step 16.

Step 16   When prompted, enter a number between 1 and 4095 to identify the redundancy VLAN. For example:

What is the number [1-4095] of this VLAN? [default = 3] 300

Step 17   When prompted, identify the interface that is assigned to the redundancy VLAN; enter the interface number in the proper format for the switch you are configuring:

  • For CS-800 model switches, enter the slot and interface number for each interface. For example, if interface 1 on slot 1 is used as the redundancy interface VLAN, you would enter:

    1/1
  • For CS-500 model switches, enter the interface number in the format ethernet-x, where x is the number of the interface that will be used for redundancy. For example, if interface 1 is assigned to the redundancy VLAN, you would enter:

    ethernet-1
  • If you are unsure of the proper format for the device you are configuring, enter q to quit the setup script and then enter the show interface command to display information about your interfaces in the proper format. 

    css-device-name> show interface

Step 18   When prompted, enter the redundancy subnet and subnet mask of the Content Services Switch. The redundancy addresses are used for communication between master and backup Content Services Switches in a redundant Content Services Switch implementation. For example:

What is the redundancy subnet of this CSS? [default = 192.168.0.0] 
192.168.128.0

Once you have assigned the redundancy subnet, the setup script automatically assigns the redundancy address to both the master and the backup Content Services Switch, even if the backup Content Services Switch has not yet been configured. The master CSS address will always be the first available address on the redundancy subnet, and the backup CSS address will always be the second available address. For example:

Master CSS address: 192.168.128.1, backup CSS address: 192.168.128.2

 
What is the redundancy subnet mask of this CSS? 
[default = 255.255.0.0] 255.255.255.0

Step 19   When prompted, indicate whether the Content Services Switch is a master or backup switch. Enter y (yes) to indicate that it is a master switch. Enter n (no) to indicate that it is a backup switch. For example:

Is this master CSS? 'y' for master, 'n' for backup [y/n]? y

Step 20   If you are configuring a redundant Content Services Switch, connect a crossover Ethernet cable from interface 1 on the master Content Services Switch to interface 1 on the backup switch and then repeat Step 1 through Step 19 for the backup switch.

You have now completed configuration of your Content Services Switch. The setup script ends, returning you to the Content Services Switch prompt.

Manually Configuring the Content Services Switch

Use the following procedure to manually configure your nonredundant Content Services Switch for use in a one- or two-VLAN deployment.

Step 1   Log in to the Content Services Switch using the admin login with the default password, system.

Step 2   Clear the old configuration by entering the following command at the prompt:

# clear running-config

Step 3   Enter configuration mode by entering the config command as follows:

# configure

The # prompt changes to (config)#, indicating that you are in configuration mode.

Step 4   Configure global parameters using the ip route command as follows:

(config)# ip route 0.0.0.0 0.0.0.0 default gateway

You must now configure the Content Services Switch circuit using the circuit command.

Step 5   Enter the circuit command as follows.

The (config)# prompt changes to indicate that you are configuring the circuit:

(config)# circuit VLAN1

(config-circuit[VLAN1])#ip address configuration ip address 
configuration subnet mask

(config-circuit[VLAN1])# no redirects

(config-circuit[VLAN1])# exit

(config)# ip address internal-address internal-subnet-mask
(config)# exit

(config)# exit

Step 6   If you are implementing a second VLAN, configure it now by entering the circuit command again as follows:

(config)# circuit VLAN3

(config-circuit[VLAN3])# ip address uplink address uplink subnet mask
(config-circuit[VLAN3])# exit

(config)# exit

(config)# interface ethernet-2

(config)# bridge vlan 3

(config)# exit

Step 7   Exit configuration mode by entering exit as follows:

(config)# exit

You must now activate the SSH software installed on the Content Services Switch using the software license key supplied to you with the switch.

Step 8   From the # prompt, enter the license command as follows:

# license

You are prompted to enter the software license key.

Step 9   Enter the license key value supplied on the front cover of your Content Services Switch documentation.

Step 10   Save the configuration by entering the write memory command at the # prompt as follows:

# write memory

Step 11   End your command-line session by entering the exit command at the # prompt as follows:

# exit

Manually Configuring Content Services Switches with Redundancy

When configuring your Content Services Switch for use in an implementation with a redundant (backup) Content Services Switch, the configuration of the redundant Content Services Switch and the primary (or master) Content Services Switch should be identical, except that the IP address used in the redundancy protocol and ArrowPoint Peer (APP) session is the first address of the redundancy subnet for the master Content Services Switch and the second redundancy subnet address for the backup Content Services Switch.

For example, if the redundancy subnet is 192.168.128.0/17, then the Content Services Switch master address is:

192.168.128.1

and the Content Services Switch backup address is:

192.168.128.2

Use the following procedure to manually configure your redundant Content Services Switches for use in a one- or two-VLAN deployment:

Step 1   Log in to the Content Services Switch using the admin login with the default password, system.

Step 2   Clear the old configuration by entering the following command at the prompt:

# clear running-config

Step 3   Enter configuration mode by entering the configure command.

Step 4   Configure global parameters as follows:

(config)# ip route 0.0.0.0 0.0.0.0 default gateway

(config)# ip redundancy

(config)# app

(config)# app session backup-address

Step 5   Configure the Content Services Switch Ethernet port as follows:

(config) # interface ethernet-1

(config-if(ethernet-1)# bridge vlan 2

(config-if(ethernet-1)# exit

Step 6   Configure circuit VLAN1 as follows:

Note   The internal address is the first address on the internal subnet. 
(config)# circuit VLAN1

(config-circuit[VLAN1])# redundancy

(config-circuit[VLAN1])# ip address configuration ip address 
configuration subnet mask

(config-circuit[VLAN1])# no redirects

(config-circuit[VLAN1])# exit

(config)# ip address internal-address internal-subnet-mask

(config)# exit

(config)# exit

Step 7   Configure circuit VLAN2 for the redundancy protocol as follows:

(config)# circuit VLAN2

(config)# ip address master-address redundancy subnet mask

(config)# redundancy protocol

(config)# exit

(config)# exit

Step 8   Configure an uplink to the default gateway to trigger failover when the switch is disconnected as follows:

(config)# service Upstream

(config)# ip address default gateway

(config)# type redundancy-up

(config)# exit

(config)# exit

Step 9   If you are using an uplink VLAN, configure it now, using the following commands:

(config)# circuit VLAN3

(config)# ip address uplink address uplink subnet mask

(config)# exit

(config)# exit

(config)# interface ethernet 2

(config)# bridge vlan 3

(config)# exit

Step 10   Exit configuration mode by entering the exit command.

(config)# exit

Step 11   Save changes by entering the write memory command as follows:

# write memory

Step 12   Configure the backup Content Services Switch by repeating Step 1 through
Step 11, substituting the backup address for the master address.

Configuring the Catalyst Switch

If you are connecting your Content Engines and redundant Content Services Switches through a Cisco Catalyst switch, you need to configure that device for one- or two-VLAN deployment, matching the configuration of your Content Services Switch.

Refer to the software configuration guide that shipped with the model of the Catalyst switch that you are deploying. For the most part, you can follow the configuration guidelines detailed in the configuration guide. However, see the following sections for specific settings that are required when configuring the Catalyst switch for use with Cisco Internet CDN Software.

Disabling VLAN Trunk Protocol

We recommend that you disable VLAN Trunk Protocol (VTP) on the Catalyst switch when using Cisco Internet CDN Software. Refer to the section "Disabling VTP (Virtual Transparent Mode)" in the Catalyst switch software configuration guide that shipped with your switch for instructions on disabling VTP.

Creating Multiple VLANs

If you are deploying multiple VLANs on your Content Services Switch (for example, a default VLAN in addition to a separate VLAN for the uplink connection to the uplink subnet), you need to configure your Catalyst switch to recognize those VLANs.

Refer to the section "Configuring VLANs" in the Catalyst switch software configuration guide that shipped with your switch for instructions on creating VLANs and assigning them to ports on your Catalyst switch. The following example shows a new VLAN, number 500 and named CSVLAN, being created and then assigned to the ports connecting both the Content Services Switch and Content Engines to the Catalyst switch. In Example 3-1:

  • VLAN 500 is the default VLAN.

  • The master Content Services Switch is connected to module 2, port 13 of the Catalyst switch.

  • The backup Content Services Switch is connected to module 2, port 16 of the Catalyst switch.

  • Content Engine 4 is connected to module 2, port 14 of the Catalyst switch.

  • Content Engine 5 is connected to module 2, port 15 of the Catalyst switch.


Example 3-1: Catalyst Switch Configured for Multiple VLAN Deployment 
cs-device> enable

cs-device>(enable) set vlan 500 name CSVLAN

cs-device>(enable) set vlan 500 2/13

cs-device>(enable) set vlan 500 2/14

cs-device>(enable) set vlan 500 2/15

cs-device>(enable) set vlan 500 2/16

For detailed explanations of Catalyst switch configuration syntax, refer to the software configuration guide that shipped with your Catalyst switch.

CDN Device Wiring Configuration

During the netsetup component of device configuration for your Content Distribution Manager, Content Engines, and Content Routers, you are prompted to assign primary and content IP addresses to one or more of the Ethernet interfaces on the CDN device you are configuring. In order to properly assign your primary and content IP addresses, you must first have decided how you wish to assign these addresses.

Note   The Content Distribution Manager is only assigned a primary IP address. It does not use a content IP address.

For devices with both 10/100 Ethernet/Fast Ethernet and Gigabit Ethernet interfaces, you are required to use interfaces of only one type. Mixing Ethernet interface types on the same device is not supported by Cisco Internet CDN Software.

Note that if you will be using the Gigabit Ethernet ports, only Ethernet port 0 is supported. Netsetup will configure your Gigabit Ethernet port as Ethernet port 0 (eth0).

Note   You need a connection to the 10/100 eth0 port when running the setup program. After the device reboots with Gigabit Ethernet support, the 10/100 ports are renumbered and are no longer needed.

Figure 3-5 illustrates the supported wiring configuration for CDN devices.


Figure 3-5: Supported Wiring Configurations for CDN Devices


Configuring the Content Distribution Manager

The Content Distribution Manager (CDM) is located at the logical central point of the network to control all operations associated with system policies, network device settings, content control, user interface, billing, and event logging. You may have more than one Content Distribution Manager on your CDN for failover purposes, but only one can serve as the primary Content Distribution Manager at any given time. A Content Distribution Manager is initially designated as primary or standby in the setup program. Subsequently, its status can be changed through the command-line interface. Refer to the "Activating a Warm Standby Content Distribution Manager" section in Chapter 2 of the Cisco Internet CDN Software User Guide for more information.

The following instructions explain how to configure a Content Distribution Manager. For information about configuring other devices, see the "Configuring the Content Services Switch" section, the "Configuring a Content Router" section, and the "Configuring a Content Engine" section.

Note   You should configure DNS before you begin configuring the Content Distribution Manager. For your CDN to deliver content, DNS must be configured. For information about configuring DNS, see the "Configurin g DNS" section.

To configure Cisco Internet CDN Software for the Content Distribution Manager, follow these steps:

Step 1   Boot the Content Distribution Manager.

Step 2   Log in as admin with the password default.

Step 3   At the administrative prompt, enter setup.

Step 4   You are prompted to change the default system password. To retain the default password, enter n. To change the system password, enter y.

Note   The new password that you enter is used as a temporary password until you access the Content Distribution Manager user interface and set the real system password.

Step 5   You are prompted to change the HTTP password. To retain the default password, enter n. To change the HTTP password, enter y.

Note   The new password that you enter is used as a temporary password until you access the Content Distribution Manager user interface to set the real HTTP password.

Step 6   Enter y if you want the Content Distribution Manager that you are configuring to serve as your primary Content Distribution Manager.

Step 7   When prompted by the setup program, enter a meaningful name for the Content Distribution Manager, for example:

OurcompanyCDM
Note   The Content Distribution Manager name cannot contain spaces.

Step 8   Enter a meaningful description for the Content Distribution Manager.

Step 9   Enter a fully qualified domain name for the Content Distribution Manager.

Step 10   When you are prompted for the database host name, enter the fully qualified domain name of the Oracle8i database server.

Note   Although you can also enter the IP address of the Oracle server at this point, we strongly recommend the use of the fully qualified domain name, which will continue to work even if the Oracle server address changes in the future.

Step 11   To accept the default database listener port number, press Enter.

This is the port that will be used by the Content Distribution Manager to communicate with the Oracle database containing Content Distribution Manager data. Alternatively, enter the port number that you specified when you installed the Oracle server listener.

Step 12   Enter the database service name that you specified when you installed the Oracle server listener.

Step 13   Enter a valid Oracle database username.

Note   This can be a username created when you set up the Oracle database, or a new account name that you create dynamically. This new account will be confirmed later during the dbsetup portion of the setup program.

Step 14   Enter the database password that you specified when you created the Oracle username. If you are creating a new Oracle database user, enter the new password here.

Step 15   Enter the tablespace used in the Oracle database.

Step 16   Enter the temporary tablespace used in the Oracle database.

Step 17   All the information you entered now appears so that you can confirm it or correct it if needed. If the displayed information is correct, enter y. If the displayed information is incorrect, enter n and provide the correct information.

Step 18   If this is the first time you are configuring your Content Distribution Manager, the setup program notifies you that it is generating a certificate. This certificate is used to ensure security in interdevice communication.

Step 19   You are prompted to choose whether or not you want to use the default Cisco signature on the certificates. To retain the default signature, enter y. To use your company information as the signature, enter n. If you choose n, you are prompted to enter the following information about your company: organizational unit, locality, organization, state, and country.

Step 20   The setup program now prompts you to run netsetup to set up the network. Enter y to run netsetup.

Note   You can run netsetup, which is the network-specific portion of the setup program, at any time by entering netsetup at the prompt.

Step 21   A list of Ethernet ports on the Content Distribution Manager is displayed.

Enter the number of the Ethernet interface that you want to use for the primary IP address. For example, to use eth0, the first Ethernet port, for the primary IP address, you would enter: 

0
Note   The default Ethernet port is eth0.

Step 22   Enter the fully qualified domain name or IP address of the Content Distribution Manager.

Note   We recommend using a domain name instead of the IP  address to identify the Content Distribution Manager, because this makes it easier to change the address of the device later.

Step 23   You are asked if you want to use a DHCP server to configure the primary IP address. Perform one of the following actions:

Caution   Every MAC address on the network must have a single, fixed IP address and fully qualified domain name associated with it. Do not use your DHCP server if it cannot assign static IP addresses.

Step 24   If a DHCP server provides the IP address information, press Enter. Alternatively, follow these steps:

   a. Enter the DNS server IP address for each DNS server.

   b. Press Enter to save the DNS server address. You are prompted to enter the address on another DNS server.

   c. When you have specified the last DNS server, press Enter.

The Content Distribution Manager must be able to resolve DNS names, or it will not function correctly.

Step 25   To bring the network online, enter y.

Step 26   To register the Content Distribution Manager, enter y.

Step 27   You are prompted to set up the Oracle policy database. Enter y to launch the dbsetup program.

  • If you set up the Oracle database before you began this configuration, the user exists. You are asked if you want to delete the user. Enter n to maintain the user.

  • If you created a new Oracle user during setup, you are asked to confirm the new user. Enter y to confirm the new Oracle user account and password.

Step 28   The dbsetup program now verifies whether database tables exist. You create them now unless you already created the database schema using the script that shipped with Cisco Internet CDN Software, described in the "Setting Up the Oracle 8i DBMS" section. To create the database tables, enter y.

Step 29   The dbsetup program now verifies whether the database tables have been initialized. To initialize the tables, enter y.

Step 30   Enter the database administrator username.

Step 31   Enter the database administrator password.

Step 32   When setup is complete, reboot the Content Distribution Manager.

Note   When you bring up the Content Distribution Manager user interface in your browser, you must ensure that you have cookies enabled in your browser.

If you have just configured a primary Content Distribution Manager, it will automatically start the software. However, if you have just configured a standby Content Distribution Manager, you will need to launch the software by entering the control start command. After this, you must activate the standby Content Distribution Manager from the Resources > Content Distribution Manager page of the primary Content Distribution Manager user interface.

You can now open the Content Distribution Manager user interface from your web browser by entering the following URL for the Content Distribution Manager: 

https://Name_of_Content_Distribution_Manager

or by entering the IP address:

https://IP_address_of_Content_Distribution_Manager

When you are prompted to accept the server certificate, click Yes.

A request for a username and password appears. If you did not change the default HTTP password during configuration, enter the default username admin and the default password default.If you chose to create a temporary HTTP password during configuration, enter the username admin and the HTTP password that you specified.

Note   Although you are provided with a default password for the admin account, you should change it as soon as possible after configuration is complete. Refer to the Cisco Internet CDN Software User Guide for instructions on changing system passwords.

Configuring a Content Router

Content Routers are deployed at strategic locations within the network and perform much of the work of routing by directing end user requests to a Content Engine that is authorized to store the requested content and is well positioned for that user.

Like all CDN devices, Content Routers must first be configured using the setup program before they can be deployed on a CDN.

For information about configuring other CDN devices, see the "Configuring the Content Distribution Manager" section and the "Configuring a Content Engine" section.

Note   You should configure DNS before you begin configuring Content Routers. In order for your CDN to deliver content, DNS must be configured. For information about configuring DNS, see the "Configurin g DNS" section.

To configure Cisco Internet CDN Software for a Content Router, follow these steps:

Step 1   Boot the Content Router.

Step 2   Log in as admin with the password default.

Step 3   At the prompt, enter setup.

Step 4   Enter a descriptive name for the Content Router.

Note   The Content Router name cannot contain spaces.

Step 5   Enter a meaningful description for the Content Router.

Step 6   Enter the fully qualified domain name of the Content Distribution Manager with which the Content Router will be associated.

Note   We recommend using a domain name instead of the IP address to identify the Content Distribution Manager, because this makes it easier to maintain connectivity should the Content Distribution Manager change addresses later.

Step 7   All the information you entered now appears so that you can confirm it or correct it if needed. If the displayed information is correct, enter y. If the displayed information is incorrect, enter n and then enter the correct information.

Step 8   The setup program now prompts you to run netsetup for setting up the network. Enter y to run netsetup.

Note   You can run netsetup, which is the network-specific portion of setup, at any time by entering netsetup at the prompt.

Step 9   A list of Ethernet ports on the Content Router is displayed. Enter the number of the Ethernet interface that you want to use for the primary IP address. For example, to use eth0, the first Ethernet port, for the primary IP address, enter 0.

See the "Primary Versus Content IP Address" section for a discussion of primary versus content IP addresses.

Step 10   Enter the fully qualified domain name or IP address of the Content Router.

Note   We recommend using a domain name instead of the IP address to identify the Content Router whenever possible. Using the domain name makes it possible to preserve connectivity with the Content Router if its network address changes.

Step 11   You are asked if you want to use a DHCP server to configure the primary IP address. Perform one of the following actions:

Caution   Every MAC address on the network must have a single, fixed IP address and fully qualified domain name associated with it. Do not use your DHCP server if it cannot assign static IP addresses.

Step 12   You are asked whether you want to configure the content IP address now, or do it later using the Content Distribution Manager graphical user interface. Perform one of the following actions:

  • To configure the content IP address now, enter y. Then do the following:

    • Enter the content IP DNS name that will be used by the Content Router. You are notified when the DNS successfully resolves to an IP address.

      Note   The content IP address can be changed later using the Content Distribution Manager graphical user interface. However, you will not be able to change the content IP address using netsetup after this initial configuration.
    • Enter the content netmask that will be used by the Content Router. You can either specify a netmask or press Enter to accept the default netmask that appears in square brackets.

  • To configure the content IP address later, enter n. You can configure the content IP address later using the Content Distribution Manager graphical user interface.

Step 13   Perform one of the following actions:

  • If the DHCP server provides the DNS information, press Enter.

  • If the DHCP server does not provide DNS information, enter the DNS server IP address for each DNS server, and when you have specified the last DNS server, press Enter.

The Content Router must be able to resolve DNS names, or it will not function correctly.

Step 14   To bring the network online, enter y.

Step 15   To register the Content Router, enter y.

Step 16   If this is the first time you are configuring your Content Router, the setup program notifies you that it is generating a certificate. This certificate is used to ensure security in inter device communication. You are prompted to choose whether or not you want to use the default Cisco signature on the certificates. Perform one of the following actions:

  • To retain the default signature, enter y.

  • To use your company information as the signature, enter n. If you choose n, you are prompted to enter the following information about your company: organizational unit, locality, organization, state, and country.

Step 17   At the prompt, reboot the Content Router.

Your Content Router is now configured and is ready to use with the CDN.

Note   Before it can begin routing content to other CDN devices, the Content Router must first be activated. Refer to the Cisco Internet CDN Software User Guide for instructions on activating Content Routers from the Content Distribution Manager graphical user interface.

Configuring a Content Engine

Content Engines contain the actual cached content that is being delivered to end users. Content Engines are responsible for storing, or pre-positioning, video-on-demand (VOD) content, and for delivering content to end users. Content Engines provide access to content through HTTP, RealMedia, Windows Media, and QuickTime format files.They also participate in routing under the direction of the Content Routers.

Note   If you are deploying supernodes on your CDN and intend to make this Content Engine part of a supernode, make sure that you have configured your Content Services Switch before configuring the Content Engine that will be assigned to it. Refer to the Cisco Internet CDN Software User Guide for instructions on creating and configuring supernodes.
Note   You should configure DNS before you begin configuring the Content Engines. For your CDN to deliver content, DNS must be configured. For information about configuring DNS, see the "Configurin g DNS" section.
Note   Even if you will be configuring your Content Engine to assign the primary and content IP addresses to a Gigabit Ethernet port, you are still required to connect to the device through a 10/100-MB Ethernet/Fast Ethernet port during initial setup and configuration. During setup, you indicate which Gigabit Ethernet ports you wish to use for each address. You must restart the device after setup, after which you will be able to connect to the Content Engine using the Gigabit Ethernet ports you selected.IR EFOBJ:1070388

For information about configuring other CDN devices, see the "Configuring the Content Distribution Manager" section and the "Configuring a Content Router" section.

Configuring a Standalone Content Engine

To configure a standalone Content Engine, follow these steps:

Step 1   Boot the Content Engine.

Step 2   Log in as admin with the password default.

Step 3   At the prompt, enter setup.

Step 4   You are prompted to change the default system password. To retain the default password, enter n. To change the system password, enter y.

Note   The new password that you enter is used as a temporary password until you set the real system password using the Content Distribution Manager user interface.

Step 5   You are prompted to change the HTTP password. To retain the default password, enter n. To change the HTTP password, enter y.

Note   The new password that you enter is used as a temporary password until you set the real HTTP password using the Content Distribution Manager user interface.

Step 6   You are prompted to confirm whether or not the Content Engine you are configuring is a member of a supernode. Enter n.

Step 7   Enter a meaningful name for the Content Engine.

Note   The Content Engine name cannot contain spaces.

Step 8   Enter a meaningful description for the Content Engine.

Step 9   Enter the fully qualified domain name of the Content Distribution Manager with which this Content Engine will be associated.

Note   We recommend using a domain name instead of the IP address to identify the Content Distribution Manager, because this makes it easier to maintain connectivity should the Content Distribution Manager address change later.

Step 10   All the information you entered now appears so that you can confirm it or correct it if needed. Perform one of the following actions:

  • If the displayed information is correct, enter y.

  • If the displayed information is incorrect, enter n. You have the opportunity to enter the correct information.

Step 11   The setup program now prompts you to run netsetup to set up the network. Enter y to run netsetup.

Step 12   Perform one of the following actions:

Step 13   Enter the fully qualified domain name of the Content Engine.

Step 14   You are asked if you want to use a DHCP server to configure the primary IP address. Perform one of the following actions:

Caution   Every MAC address on the network must have a single, fixed IP address and fully qualified domain name associated with it. Do not use your DHCP server if it cannot assign static IP addresses.

Step 15   If your Content Engine contains more than one Ethernet card, you are prompted to choose how you want those cards allocated:

  • Enter 1 to use a single Ethernet port for both the primary IP address and the content IP address.
  • Enter 2 to use one Ethernet port for the primary IP address and one Ethernet port for the content IP address.

Step 16   Perform one of the following actions:

  • To configure the Content Engine content IP address now, enter y and then enter the content IP DNS name and the content netmask when prompted.You are given a default content netmask in square brackets. You can accept this by pressing Enter, or you can specify a different netmask.

  • To configure the Content Engine content IP address later using the Content Distribution Manager graphical user interface, enter n.

Step 17   To bring the network online, enter y.

Step 18   To register the Content Engine, enter y.

Step 19   If this is the first time you are configuring your Content Engine, the setup program notifies you that it is generating a certificate. This certificate is used to ensure security in interdevice communication.

Step 20   You are prompted to choose whether or not you want to use the default Cisco signature on the certificates. Perform one of the following actions:

  • To retain the default signature, enter y.

  • To use your company information as the signature, enter n. If you choose n, you are prompted to enter the following information about your company: organizational unit, locality, organization, state, and country.

Step 21   At the prompt, reboot the Content Engine.

Your Content Engine is now configured and is ready to use with the CDN.

Note   Before it can begin receiving content to stream, however, it must first be activated. Refer to the Cisco Internet CDN Software User Guide for instructions on activating Content Engines from the Content Distribution Manager user interface.

Configuring a Content Engine as Part of a Supernode

To configure a Content Engine as part of a supernode, follow these steps:

Step 1   Boot the Content Engine.

Step 2   Log in as admin with the password default.

Step 3   At the prompt, enter setup.

Step 4   You are prompted to change the default system password. To retain the default password, enter n. To change the system password, enter y.

Note   The new password that you enter is used as a temporary password until you set the real system password using the Content Distribution Manager user interface.

Step 5   You are prompted to change the HTTP password. To retain the default password, enter n. To change the HTTP password, enter y.

Note   The new password that you enter is used as a temporary password until you set the real HTTP password using the Content Distribution Manager user interface.

Step 6   You are prompted to confirm whether or not the Content Engine you are configuring is a member of a supernode. Enter y.

Step 7   Enter a meaningful name for the Content Engine.

Note   The Content Engine name cannot contain spaces.

Step 8   Enter a meaningful description for the Content Engine.

Step 9   Enter the fully qualified domain name of the Content Distribution Manager with which this Content Engine will be associated.

Note   We recommend using a domain name instead of the IP address to identify the Content Distribution Manager, because this makes it easier to maintain connectivity should the Content Distribution Manager address change later.

Step 10   All the information you entered now appears so that you can confirm it or correct it if needed. Perform one of the following actions:

  • If the displayed information is correct, enter y.

  • If the displayed information is incorrect, enter n. You have the opportunity to enter the correct information.

Step 11   The setup program now prompts you to run netsetup to set up the network. Enter y to run netsetup.

Step 12   Perform one of the following actions:

Step 13   Enter the configuration IP address of the Content Services Switch that this Content Engine will be associated with. The configuration IP address will be the gateway for this Content Engine.

Step 14   Enter the fully qualified domain name of the Content Engine.

Step 15   Enter the primary IP address assigned to the Content Engine.

Step 16   Enter a primary netmask that represents your local-area subnet mask.

Step 17   If your Content Engine contains more than one Ethernet card, you are prompted to choose how you want those cards allocated:

  • Enter 1 to use a single Ethernet port for both the primary IP address and the content IP address.
  • Enter 2 to use one Ethernet port for the primary IP address and one Ethernet port for the content IP address.

Step 18   Perform one of the following actions:

  • If the DHCP server provides the DNS information, press Enter.
  • If the DHCP server does not provide DNS information, enter the DNS server IP address for each DNS server, and when you have specified the last DNS server, press Enter.

    Note   The Content Engine must be able to resolve DNS names or it will not function correctly.

Step 19   To bring the network online, enter y.

Step 20   To register the Content Engine, enter y.

Step 21   If this is the first time you are configuring your Content Engine, the setup program notifies you that it is generating a certificate. This certificate is used to ensure security in interdevice communication.

Step 22   You are prompted to choose whether or not you want to use the default Cisco signature on the certificates. Perform one of the following actions:

  • To retain the default signature, enter y.

  • To use your company information as the signature, enter n. If you choose n, you are prompted to enter the following information about your company: organizational unit, locality, organization, state, and country.

Step 23   At the prompt, reboot the Content Engine.

Your Content Engine is now configured and is ready to use with the CDN. Before it can begin receiving content to distribute, however, it must first be activated. Refer to the Cisco Internet CDN Software User Guide for instructions on activating Content Engines from the Content Distribution Manager user interface.

Configuring a Storage Array

The Cisco Storage Array 6 and Cisco Storage Array 12 are rack-mounted hard disk arrays that provide additional storage capacity to Cisco Content Engines. Once you have added a Storage Array for a Content Engine, there is no need to format or partition the drives.

The Cisco Storage Array 6 is compatible with a Content Engine CE-590-ICDN-K9 and CE-590-DC-ICDN-K9. The Cisco Storage Array 12 is compatible with a Content Engine CE-7320-ICDN-K9. Configurations that have multiple Storage Arrays cabled together or multiple Content Engines cabled to a single Storage Array are not supported.

To add a Storage Array to your Content Engine:

Step 1   Verify from the Resources > Content Engines page of the Content Distribution Manager user interface that the Content Engine is online.

Step 2   Attach a SCSI cable to the first SCSI bus connector of the Content Engine.

Note   Make sure to tighten the jackscrews on the SCSI cable.

Step 3   Attach the other end of the SCSI cable to your Storage Array.

  • If you are using a Storage Array 6, connect the cable to either the SCSI 0 or SCSI 1 port on the I/O module on the rear of the Storage Array.

  • If you are using a Storage Array 12, connect the cable to the SCSI Management Module I/O connector on the rear of the Storage Array.

Step 4   Move the Storage Array power switch to the on position.

Note   You will not see the additional storage capacity registered in any way on the Content Distribution Manager user interface until you reboot the Content Engine.

Step 5   Access the command-line interface of the Content Engine and enter the reboot command. For more information on using the command-line interface, refer to the Cisco Internet CDN Software Command Reference Version 2.1.

It takes several minutes for the Content Engine to come online on the Content Distribution Manager user interface. The total disk space figure on the Resources > Content Engines page now reflects the additional storage capacity. You can now configure as much of the total capacity for pre-positioned disk space as you would like. The following equation expresses the amount of disk space available for caching after you add a Storage Array.

Storage capacity used for caching =  Additional storage capacity not allocated for pre-positioned content - Overhead