Table of Contents

Working with Cisco Internet CDN Software

Working with Cisco Internet CDN Software

This chapter provides information about modifying CDNs and using the system tools for changing system passwords, setting up remote logging, and updating Cisco Internet CDN Software on your Cisco CDN devices.

This chapter contains the following sections:

• Working with Regions and Locations
  
  
• Working with Virtual Content Delivery Networks
  
  
• Working with Content Distribution Managers
  
  
• Working with Content Engines
  
  
• Working with Content Routers
  
  
• Working with Supernodes and Content Engine Clusters
  
  
• Working with Content Providers
  
  
• Working with Hosted Domains
  
  
• Printing and Exporting CDN Data
  
  

Working with Regions and Locations

By default, Content Engines and Content Routers are grouped by geographical region and location. Because physical proximity bears a direct relationship to response time when serving user requests, it is useful to be able to group your Content Routers and the Content Engines that will be serving content according to their physical location.

However, you may also need to group your CDN according to other criteria. Using the virtual CDN feature, you can group Content Engines in whatever manner suits your organization—by hardware type or any other criteria that seem appropriate. Refer to the "Creating a Virtual CDN" section for more information on setting up virtual Content Delivery Networks or the "Working with Virtual Content Delivery Networks" section for help modifying or removing virtual Content Delivery Networks.

Working with regions and locations entails:

• Modifying Regions
  
  
• Deleting Regions
  
  
• Modifying Locations
  
  
• Deleting Locations
  
  

Modifying Regions

To modify a region, follow these steps:

Step 2   From the drop-down list, choose Regions.

The View Regions page appears. (See Figure 2-3.)

Step 3   Click the edit icon next to the name of the region that you want to modify.

The Modify a Region page appears. (See Figure 3-1.)

Step 4   Enter a new name or description as needed in the Name field.

---

Note   Clicking Cancel returns all values to their previous settings when you last clicked Save.

---

Step 5   If needed, check or uncheck the Desirable check box to change the desirability of a region.

A desirable region is one to which you can route any end user request (regardless of the geographic origin of the request) because of the existence of robust network connectivity.

Most regions in the United States are desirable regions because network connectivity in the United States is generally very good. Network connectivity in other parts of the world may not be as robust, so if an end user request is received from Asia, you might not want to route the request to Africa, for example. However, routing the Asian request to anywhere in the United States would be acceptable.

Step 6   Click Save.

Deleting Regions

To delete a region, follow these steps:

Step 2   From the drop-down list, choose Regions.

The View Regions page appears. (See Figure 2-3.)

Step 3   Click the edit icon next to the region that you want to delete.

---

Note   A region can be deleted only if it does not have assigned locations. You can reassign a location from one region to another region if necessary. See the "Mo difying Locations" section.

---

Step 4   Click Delete. You are prompted to confirm your decision to delete the region.

Step 5   Click OK.

Modifying Locations

To modify a location, follow these steps:

Step 2   From the drop-down list, choose Locations.

The View Locations page appears. (See Figure 2-5.)

Step 3   Click the edit icon next to the name of the location that you want to modify.

The Modify a Location page appears. (See Figure 3-2.)

Step 4   Enter a new name or description as needed.

---

Note   Clicking Cancel returns all values to their previous settings when you last clicked Save.

---

Step 5   If needed, change the location to a different region by choosing a region from the Region drop-down list.

You must specify a region that is associated with the location.

Step 6   Click Save.

Deleting Locations

You can delete locations as needed, as long as they are not the root locations of activated Content Engines or Content Routers.

---

Note   If a location has a Content Engine or Content Router assigned to it, you can first assign the Content Engine or Content Router to another location and then delete the original location.

---

To delete a location, follow these steps:

Step 2   From the drop-down list, choose Locations.

The View Locations page appears. (See Figure 2-5.)

Step 3   Click the edit icon next to the location that you want to delete.

The Modify a Location page appears. (See Figure 3-2.)

Step 4   Click Delete. You are asked to confirm your decision to delete the location.

Step 5   Click OK.

Working with Virtual Content Delivery Networks

Using the virtual CDN feature of the Content Distribution Manager, you can modify information about a virtual Content Delivery Network (CDN) or remove a virtual CDN from the system.

You work with Virtual Content Delivery Networks by:

• Modifying a Virtual Content Delivery Network
  
  
• Deleting a Virtual Content Delivery Network
  
  

Modifying a Virtual Content Delivery Network

To modify a virtual Content Delivery Network:

Step 2   Click the edit icon next to the name of the virtual CDN that you wish to edit. The browser window refreshes, displaying the Modify a Virtual CDN page. (See Figure 2-21.)

Step 3   Modify the virtual CDN name by entering a new value in the Name field.

The name must be unique and should be a name that is useful in distinguishing the virtual CDN from others on your system.

Step 4   Optionally, enter any notes about the virtual CDN in the Comments field.

Step 5   If you want to modify the list of Content Engines or clusters assigned to the virtual CDN, see the next section, "Adding and Removing Content Engines from a Virtual CDN."

Step 6   Click Save to save your modifications to the virtual CDN. The browser window refreshes, listing the updated virtual CDNs.

Adding and Removing Content Engines from a Virtual CDN

To add or remove Content Engines or clusters from a virtual CDN:

Step 2   Click the edit icon next to the name of the virtual CDN that you wish to edit. The browser window refreshes, displaying the Modify a Virtual CDN page. (See Figure 2-21.)

Step 3   Click the Assign CEs by Region tab.

Step 4   Choose the region in which the Content Engines reside. A list of locations in the region or clusters in the virtual CDN appears.

Step 5   Choose the name of the location for the Content Engines. A list of the Content Engines and clusters in that location appears.

---

Note   As you move down from regions to locations, your path is saved in the header area just above the Add Selected CEs button. Click the All Regions or location link to back up and change your location.

---

Step 6   Check the check box adjacent to the name of the cluster or Content Engine that you wish to associate with, or remove from, the virtual CDN.

---

Note   To choose all Content Engines, choose the topmost check box next to the Cluster or Content Engine heading.

---

Step 7   Click Add Selected CEs, and then click Save.

The list of clusters or Content Engines to which the hosted domain is assigned refreshes, listing the newly added Content Engine or cluster.

Step 8   To remove Content Engines, check the box next to the name of the Content Engine that you wish to remove from this list and click Remove Selected CEs.

Step 9   Click Save. The browser window refreshes, listing the updated virtual CDNs. The list of Content Engines shows the updated count for the virtual CDN.

Deleting a Virtual Content Delivery Network

To delete a virtual CDN:

Step 2   Click the edit icon next to the name of the virtual CDN that you wish to edit. The browser window refreshes, displaying the Modify a Virtual CDN page. (See Figure 2-21.)

Step 3   Click Delete. You are prompted to confirm your decision to delete the virtual CDN.

Step 4   Click OK. The browser window refreshes with an updated list of virtual CDNs.

Working with Content Distribution Managers

You work with Content Distribution Managers by deleting a warm standby Content Distribution Manager.

Deleting a Warm Standby Content Distribution Manager

You can delete a warm standby Content Distribution Manager from the CDN at any point after you have registered the device and before the device has come online as the primary Content Distribution Manager. Once the device has been called into use as the primary Content Distribution Manager, however, you cannot delete it using the Content Distribution Manager user interface.

Delete a warm standby Content Distribution Manager when the device is experiencing unresolvable problems or when its network address or configuration has changed and you need to add the device back to the CDN using its new address and configuration information.

When deleting a warm standby Content Distribution Manager from the CDN, you are effectively removing that device and the content it contains from the routing scheme that the CDN software uses to fill user requests. Should your primary Content Distribution Manager fail during the time that the warm standby is deleted, there will be no failover for the Content Distribution Manager.

To delete a warm standby Content Distribution Manager:

Step 2   From the drop-down list, choose Content Distribution Manager. The browser refreshes, listing the Content Distribution Managers on your CDN. The warm standby Content Distribution Manager is identified as Standby.

Step 3   Click the edit icon next to the name of the warm standby Content Distribution Manager that you wish to delete. The browser window refreshes, displaying the Modify a Content Distribution Manager page. (See Figure 3-3.)

Step 4   Click Delete. You are prompted to confirm your decision.

Step 5   Click OK to execute your request. You are returned to the View Content Distribution Managers page, which lists the remaining Content Distribution Manager on your CDN.

Step 6   To complete the process of deleting the warm standby Content Distribution Manager offline, shut down the device by logging directly in to the Content Distribution Manager you deleted and accessing the command-line interface (CLI) using the admin account and password:

device_name> enable

 

The prompt changes to a pound sign (#) to indicate that you are in administrative mode.

Working with Content Engines

You work with Content Engines by:

• Modifying Content Engines
  
  
• Modifying Content Engine Passwords
  
  
• Stopping, Shutting Down, Restarting, and Rebooting a Content Engine
  
  
• Deleting a Content Engine
  
  
• Viewing Content Engine Statistics
  
  

Modifying Content Engines

Use the resources feature of the Content Distribution Manager to make changes to the name of a Content Engine from the Content Distribution Manager user interface.

You can modify a Content Engine by changing the following items:

• Name
  
  
• Location
  
  
• Root and HTTP passwords
  
  
• Description
  
  
• Content IP address
  
  
• Content host name
  
  
• Pre-positioned disk space
  
  

  ---

  Note   Changing the location of pre-positioned disk space will cause the Content Engine to restart.

  ---

To modify a Content Engine, follow these steps:

Step 2   From the drop-down list, choose Content Engines. The View Content Engines page (see Figure 2-10) appears, listing the Content Engines on your CDN.

Step 3   Click the edit icon next to the name of the Content Engine that you wish to edit. The browser window refreshes, displaying the Modify a Content Engine page. (See Figure 2-11.) Fields for editing the selected Content Engine appear.

Step 4   If you choose to, enter the new name of the Content Engine in the Content Engine Name field. Otherwise, proceed to the next step.

Step 5   If you choose to, modify the description used to identify the Content Engine by entering a new description in the Comments field. Otherwise, proceed to the next step.

Step 6   Enter the new Content Engine IP address in the Content IP Address field. This is the static content IP address from your DNS server that will be used to communicate with the Content Engine.

Step 7   If you choose to, enter the new host name in the Content Hostname field. Otherwise, proceed to the next step.

This is the DNS address that can be used to reach the Content Engine. Otherwise, proceed to the next step.

Step 8   If you choose to, click the Location drop-down list, and choose a new CDN location for the Content Engine. Otherwise, proceed to the next step.

Depending on the location you choose, the Region field will change to reflect the region containing that location.

Step 9   If you choose to, change the pre-positioned disk space. Otherwise, proceed to the next step.

Enter a value (in gigabytes, up to 24 gigabytes) representing the disk space allocated to pre-positioning content on the Content Engine. Changing the pre-positioned disk space causes the Content Engine to restart.

Step 10   Click Save. You are returned to the View Content Engines page (see Figure 2-10), which lists Content Engines on your CDN.

Modifying Content Engine Passwords

Both Content Engines and Content Routers maintain two sets of passwords:

• Root password—This password controls access to the CDN device console using direct login or remote login using the Telnet or SSH command interfaces.
  
  
• HTTP password—This password controls access to device configuration features accessible from the Content Distribution Manager.
  

To modify the root or HTTP password:

Step 2   From the drop-down list, choose Content Engines. The View Content Engines page appears (see Figure 2-10), listing the Content Engines on your CDN.

Step 3   Click the edit icon next to the name of the Content Engine that you wish to edit. The browser window refreshes, displaying the Modify a Content Engine page. (See Figure 2-11.)

Step 4   Locate the fields for modifying the current password. Fields for modifying the root password and HTTP password are grouped in columns under the appropriate heading.

Step 5   Enter the current password (that you wish to change) in the Old Password field.

If you have forgotten the current password for this device, you can enter the current system password in its place and then proceed with changing the password to a new value. See the "Changing System Passwords" section for more information on maintaining your system passwords.

Step 6   Move your cursor to the New Password field, and enter the password you wish to begin using.

---

Note   Passwords should be eight characters long.

---

Step 7   Move your cursor to the Re-type New Password field and reenter the new password to confirm your decision.

Step 8   Click Save. The password is updated for the selected Content Engine.

The Modify a Content Engine page refreshes. If the password was successfully changed, a green circle with a check mark is displayed on the user interface next to the affected password field. See the "Exiting the Content Distribution Manager User Interface" section for details.

Stopping, Shutting Down, Restarting, and Rebooting a Content Engine

Using the resources feature of the Content Distribution Manager, you can stop, restart, reboot, or shut down a Content Engine remotely, with the following consequences:

• Reboot CE—This option causes the device to perform a controlled shutdown of all CDN servers and then restarts the operating system on the device.
  
• Restart Software—This option halts and then restarts the CDN servers on the device.
  
• Shutdown CE—This option causes the device to perform a controlled shutdown of all CDN servers, requiring a manual reboot of the device. Clicking Shutdown CE is equivalent to issuing a node exit command, or a control exit command in Linux.
  

Once a device has been shut down, you will not be able to access it remotely using Telnet or SSH, nor will you be able to issue commands using the command-line interface. To bring a device back online, gain physical access to the device and cycle the power off and then on again.

• Stop Software—This option is equivalent to issuing a node stop command from the command-line interface; clicking Stop halts the CDN servers on the device, bringing the device offline.
  

To bring a device back online that has been stopped from the Content Distribution Manager, it is necessary to remotely access the device using SSH or Telnet (if Telnet has been enabled on the device). After logging on to the device using the admin account and secure password, use commands issued through the Cisco Internet CDN Software command-line interface (CLI) to restart the CDN processes on the device. For example:

cdn-device> enable

cdn-device# node start

cdn-device# exit

cdn-device> exit

 

Refer to the Cisco Internet CDN Software Command Reference for more information on the node command, or using the CDN command-line interface.

To stop, restart, reboot, or shut down a Content Engine:

Step 2   From the drop-down list, choose Content Engines. The View Content Engines page appears (see Figure 2-10), listing the Content Engines on your CDN. The online status of the device is listed under the heading Node status.

Step 3   Click the edit icon next to the name of the Content Engine that you wish to stop, shut down, reboot, or restart. The browser window refreshes, displaying the Modify a Content Engine page. (See Figure 2-11.)

Step 4   Click the appropriate button to stop, shut down, restart, or reboot the Content Engine. You are prompted to confirm your decision.

• If you are shutting down the Content Engine, you are asked to confirm your decision. Click OK to confirm.
  
  
• If you are stopping, restarting, or rebooting the Content Engine, click the Yes Continue button to execute your request.
  
  

You are returned to the View Content Engines page, which lists the Content Engines on your CDN.

Deleting a Content Engine

Delete a Content Engine when the device is experiencing unresolvable problems or when its network address or configuration has changed and you need to add the device back to the CDN using its new address and configuration information.

When deleting a Content Engine from the CDN, you are effectively removing that device and the content it contains from the routing scheme that the CDN software uses to fill user requests. Although the CDN software is designed to route requests around Content Engines that are busy, offline, or missing, removing a Content Engine may affect the speed with which the CDN can serve user requests.

Note   You cannot delete a Content Engine if it is the last node assigned to a location that is designated as the root location for a hosted domain. If you receive an error referencing the root location for a hosted domain, add more Content Engines to that location, or change the root location for the hosted domain before attempting to delete the Content Engine again.

To delete a Content Engine:

Step 2   From the drop-down list, choose Content Engines. The View Content Engines page appears (see Figure 2-10), listing the Content Engines on your CDN. The online status of the device is listed under the heading Node status.

Step 3   Click the edit icon next to the name of the Content Engine that you wish to delete. The browser window refreshes, displaying the Modify a Content Engine page. (See Figure 2-11.)

Step 4   Click Delete. You are prompted to confirm your decision.

Step 5   Click OK to execute your request. You are returned to the View Content Engines page (see Figure 2-10), which lists the remaining Content Engines on your CDN.

Step 6   You now need to log in directly to the Content Engine you deleted and access the command-line interface (CLI) using the admin account and password.

Step 7   At the prompt, enter enable to enable the administrative mode. For example:

device_name> enable

 

The prompt changes to a pound sign (#) to indicate that you are in administrative mode.

Step 8   Enter shutdown to stop the Cisco Internet CDN Software and shut down the device.

Viewing Content Engine Statistics

It is often useful to be able to get a picture of the performance of Content Engines across your network. You can do this using the Content Engine Statistics feature, available from the Tools area of the Content Distribution Manager user interface.

The Content Engines Statistics feature enables you to view, at a glance, which Content Engines are online, as well as assess their available resources, the volume of traffic being routed to them, and their performance in serving requests. The information displayed using the Content Engine Statistics tool is based on a snapshot of your CDN taken on the quarter hour. The statistics displayed represent the state of your Content Engines for the previous quarter hour.

Using the tabs provided, you view statistics for all Content Engines on your CDN, or look at the overall performance of the Content Engines in your hosted domains and virtual CDNs.

See Table 3-1 for information on the meaning of each Content Engine statistic presented in the table.

To view Content Engine statistics for your CDN:

Step 2   From the drop-down list, choose Content Engine Statistics. The browser refreshes, displaying the Content Engine Statistics page.

Step 3   Click the tab corresponding to the way you would like to view your Content Engine statistics.

• To view the statistics for each Content Engine on your CDN, click the Content Engines tab.
  
  
• To view the overall performance of the Content Engines in your hosted domains, click the Hosted Domains tab.
  
  
• To view the overall performance of the Content Engines in your virtual CDNs, click the virtual CDNs tab.
  
  

The Content Engine Statistics tool displays the information you requested.

Step 4   See the "Printing and Exporting CDN Data" section for information on reporting on your Content Engine statistics.

Viewing Hosted Domain Assignments

You can use the Modify a Content Engine page to view which hosted domains a particular Content Engine is assigned to. You can view hosted domain assignments for a bird's eye view of how a given Content Engine is deployed across your CDN—which hosted domains it belongs to, the root location and amount of pre-positioned disk space required in each hosted domain, and the number of Content Engines also assigned to each hosted domain.

To view hosted domain assignments for a Content Engine:

Step 2   From the drop-down list, choose Content Engines. The View Content Engines page appears (see Figure 2-10), listing the Content Engines on your CDN. The online status of the device is listed under the heading Node status.

Step 3   Click the edit icon next to the name of the Content Engine for which you wish to view hosted domain assignments. The browser window refreshes, displaying the Modify a Content Engine page. (See Figure 2-11.)

Step 4   Under the heading Locality, click the note pad icon. A listing of the Content Engine's hosted domain assignments appears in a separate window.

Working with Content Routers

You work with Content Routers by:

• Modifying Content Routers
  
  
• Modifying Content Router Passwords
  
  
• Stopping, Shutting Down, Restarting, and Rebooting a Content Router
  
  
• Deleting a Content Router
  
  

Modifying Content Routers

You use the resources feature of the Content Distribution Manager to make changes to a Content Router.

You can modify the following Content Router properties:

• Name
  
  
• Location
  
  
• Root and HTTP passwords
  
  
• Description
  
  
• Content IP address
  
  
• Content host name
  
  

  ---

  Note   Changing the location will cause the Content Router to restart.

  ---

To modify a Content Router, follow these steps:

Step 2   From the drop-down list, choose Content Routers. The View Content Routers page appears (see Figure 2-8), listing the Content Routers on your CDN.

Step 3   Click the edit icon next to the name of the Content Router that you wish to edit. The browser window refreshes, displaying the Modify a Content Router page. (See Figure 2-9.) Fields for editing the selected Content Router appear.

Step 4   If you wish to, enter the new name of the Content Router in the Content Router Name field. Otherwise, proceed to the next step.

Step 5   If you wish to, modify the description used to identify the Content Router by entering a new description in the Comments field. Otherwise, proceed to the next step.

Step 6   Enter the new Content Router IP address in the Content IP Address field. This is the static content IP address from your DNS server that will be used to communicate with the Content Router.

Step 7   If you wish to, enter the new host name in the Content Hostname field. Otherwise, proceed to the next step.

This is the DNS address that can be used to reach the Content Router.

Step 8   If you wish to, click the Location drop-down list and choose a new CDN location for the Content Router. Otherwise, proceed to the next step.

Depending on the location you choose, the Region field will change to reflect the region containing that location.

Step 9   Click Save. You will be returned to the View Content Routers page (see Figure 2-8), which lists Content Routers on your CDN.

Modifying Content Router Passwords

Both Content Routers and Content Engines maintain two sets of passwords:

• Root password—This password controls remote access to the CDN device console using direct login or remote login using the Telnet or SSH command interfaces.
  
• HTTP password—This password controls access to device configuration features accessible from the Content Distribution Manager.
  

To modify the root or HTTP password:

Step 2   From the drop-down list, choose Content Routers. The View Content Routers page appears (see Figure 2-8), listing the Content Routers on your CDN.

Step 3   Click the edit icon next to the name of the Content Router that you wish to edit. The Modify a Content Router page appears. (See Figure 2-9.)

Step 4   Locate the fields for modifying the current password. Fields for modifying the root password and HTTP password are grouped in columns under the appropriate heading.

Step 5   Enter the current password (that you wish to change) in the Old Password field.

If you have forgotten the current password for this device, you can enter the current system password in its place, and then proceed with changing the password to a new one. See the "Changing System Passwords" section for more information on maintaining your system passwords.

---

Note   Passwords should be eight characters long.

---

Step 6   Move your cursor to the New Password field, and enter the password that you wish to begin using.

Step 7   Move your cursor to the Re-type New Password field and enter the new password a second time to confirm your decision.

Step 8   Click Save. The password is updated for the selected Content Router.

The Modify a Content Router page refreshes. If the password was successfully changed, a green circle with a check mark is displayed on the user interface next to the affected password field. See the "Exiting the Content Distribution Manager User Interface" section for details.

Stopping, Shutting Down, Restarting, and Rebooting a Content Router

As with Content Engines, you can use the resources feature of the Content Distribution Manager to stop, restart, reboot, or shut down a Content Router remotely.

See the instructions in the "Stopping, Shutting Down, Restarting, and Rebooting a Content Engine" section for a more detailed discussion of the effect of stopping, shutting down, restarting, or rebooting a CDN device.

The instructions presented in that section also apply to Content Routers.

Deleting a Content Router

Delete a Content Router when the device is experiencing unresolvable problems or when its network address or configuration has changed and you need to add the device back to the CDN using its new address and configuration information.

When deleting a Content Router from the CDN, you are effectively removing that device from the routing scheme that the CDN software uses to fill user requests. Although the CDN software is designed to route requests around Content Routers that are busy, offline, or missing, removing a Content Router may affect the speed with which the CDN can serve user requests.

To delete a Content Router:

Step 2   From the drop-down list, choose Content Routers. The View Content Routers page appears (see Figure 2-8), listing the Content Routers on your CDN. The online status of the device is listed under the heading Node status.

Step 3   Click the edit icon next to the name of the Content Router that you wish to delete. The Modify a Content Router page appears (see Figure 2-9), displaying fields for editing the selected Content Router.

Step 4   Click Delete. You are prompted to confirm your decision.

Step 5   Click Yes Continue to execute your request. You are returned to the View Content Routers page (see Figure 2-8), which lists the remaining Content Routers on your CDN.

Step 6   You now need to log in directly to the Content Router you deleted and access the command-line interface using the admin account and password.

Step 7   At the prompt, enter enable to enable the administrative mode. For example:

device_name> enable

 

The prompt changes to a pound sign (#) to indicate that you are in administrative mode.

Step 8   Enter shutdown to stop the Cisco Internet CDN Software and shut down the device.

Working with Supernodes and Content Engine Clusters

Using the resources feature of the Content Distribution Manager, you can modify supernodes, as well as the Content Services Switch and Content Engine clusters assigned to them.

You can work with supernodes and clusters by:

• Modifying a Supernode
  
  
• Deleting a Supernode
  
  
• Modifying a Cluster
  
  
• Deleting a Cluster
  
  

Modifying a Supernode

It is possible to edit a supernode name and the location and region with which the supernode is associated on a CDN. In addition, you can modify the address of the Content Services Switch and the administrative password used to access the Content Services Switch. These changes can be made directly from the Content Distribution Manager user interface.

Modifying the Supernode Name, Location, and Region

To modify the supernode name, location, or region:

Step 2   From the drop-down list, choose SuperNodes. The View Supernodes page appears. (See Figure 2-12.)

Step 3   Click the icon next to the supernode you wish to edit. The Modify a Supernode page appears. (See Figure 3-4.)

• To edit the name of the supernode (this is the user-friendly name that identifies the supernode within the Content Distribution Manager user interface and elsewhere), enter a new name in the SuperNode Name field.
  
• To modify the location with which the supernode is associated, from the Location drop-down list, choose a new location. The region may change depending on what location you choose.
  
• To add a new cluster to the supernode or delete a cluster from the supernode, see the "Creating a Cluster" section.
  
  

Step 4   Click Save to update your changes to the supernode name and location. You are returned to the View Supernodes page. The status of the supernode that you just modified is configuring until your name and location changes have been integrated.

Step 5   Wait until the changes have been incorporated and the status returns to online before making additional changes to the supernode configuration.

.

Updating the Content Services Switch Password

If the password for the CLI for the Content Services Switch has changed, use the Content Distribution Manager user interface to update the CDN with the new password information.

To update the root password information for your Content Services Switch:

Step 2   From the drop-down list, choose SuperNodes.

The View Supernodes page appears (See Figure 2-12.) The IP address of the Content Services Switch associated with the supernode is provided in the column labeled CSS Configuration IP Address.

Step 3   Click the icon next to the supernode corresponding to the Content Services Switch with the CLI password that you wish to modify. The Modify a Supernode page appears. (See Figure 3-4.)

Step 4   Enter the new password information for the Content Services Switch CLI in the Password field.

Step 5   Verify the new password by entering it again in the Re-type Password field.

Step 6   Click Save to update the Content Services Switch CLI password. You are returned to the View Supernodes page.

The status of the supernode that you just modified is configuring until your password changes have been integrated.

Modifying the Content Services Switch Internal Address

The Content Services Switch maintains an internal subnet of content IP addresses referred to as the internal subnet. It is from this list of addresses that the Content Services Switch chooses Content Engines to serve content. Using the Modify Supernode page on the Content Distribution Manager user interface, you can change the Content Services Switch internal IP address and subnet mask.

Note   Changing the internal IP address information for the Content Services Switch causes a temporary disruption in service from the Content Engines assigned to the supernode, because these devices will be assigned new content IP addresses.

To modify the Content Services Switch internal IP address:

Step 2   From the drop-down list, choose SuperNodes.

The View Supernodes page appears (See Figure 2-12.) The IP address of the Content Services Switch associated with the supernode is provided in the column labeled CSS Configuration IP Address. This is the actual network address of the device.

Step 3   Click the icon next to the supernode corresponding to the Content Services Switch you wish to modify. The Modify a Supernode page appears. (See Figure 3-4.)

Step 4   Under the heading CSS Internal Address, enter the IP address and subnet mask that will be used by the Content Services Switch to assign content address to the Content Engines grouped behind it.

Step 5   Click Save to update the Content Services Switch internal IP address information. You will be asked to confirm your decision to change the internal IP address information.

Step 6   Click OK. You are returned to the View Supernodes page.

The status of the supernode that you just modified is configuring until your internal IP address changes have been integrated.

Deleting a Supernode

Deleting a supernode from the CDN effectively removes all content served from the Content Engines in that supernode from the CDN. User requests for that content will be routed to other nodes or supernodes on the CDN, if they exist.

After you delete the supernode, the associated Content Engines continue to appear on the Content Distribution Manager user interface, listed with the other Content Engines on your CDN, but with an inactive status. To remove these Content Engines from the CDN, follow the instructions for deleting Content Engines in the "Deleting a Content Engine" section.

Note   You cannot delete a supernode if any of its Content Engines are the last node assigned to a location that is designated as the root location for a hosted domain. If you receive an error referencing the root location for a hosted domain, add more Content Engines to that location, or change the root location for the hosted domain before attempting to delete the supernode again.

To delete a supernode:

Step 2   From the drop-down list, choose SuperNodes. The View Supernodes page appears. (See Figure 2-12.)

Step 3   Click the icon next to the supernode that you wish to delete. The Modify a Supernode page appears. (See Figure 3-4.)

Step 4   Click Delete Supernode. You are prompted to confirm your decision to remove the supernode from the CDN.

Step 5   Click OK. You are returned to the View Supernodes page.

Modifying a Cluster

Once they are created, the name or description of Content Engine clusters can be changed, as well as the virtual IP address or virtual host name designation. In addition, Content Engines can be removed from the cluster and associated with a different cluster behind the same Content Services Switch.

To modify a cluster:

Step 2   From the drop-down list, choose Clusters. The View Clusters page appears. (See Figure 2-14.)

Step 3   Click the icon next to the cluster you wish to edit. The Modify a Cluster page appears. (See Figure 3-5.)

• To edit the cluster name (this is the user-friendly name that identifies the cluster within the Content Distribution Manager user interface and elsewhere), enter a new name in the Cluster Name field.
  
  
• To modify the virtual IP address or host name for the cluster, enter the new address information in the fields provided. Refer to the "CDN Device Network Addressing" section in Chapter 2 of the Cisco Internet CDN Software Configuration Guide for an explanation of the role of the cluster's virtual IP address.
  

  ---

  Note   If the virtual IP address is resolvable back to the DNS server, no virtual host name is required.

  ---

• To modify the pre-positioned disk space available on each of the Content Engines in this cluster, enter a new number (representing the number of gigabytes of pre-positioned disk space) in the Pre-position Disk Space field provided. This is the amount of space that will be allocated on each Content Engine, and must be less than the amount of available disk space on each of the assigned Content Engines.
  

  ---

  Note   The amount of pre-positioned disk space assigned to Content Engines through the cluster will overwrite any other pre-positioned disk space designation for the device.

  ---

Step 4   Click Save to save your changes to the selected cluster.

Deleting a Cluster

When you delete a cluster, the Content Engines in that cluster remain on the CDN and can be reassigned to different clusters on the supernode. See the
"Deleting a Content Engine" section for instructions on deleting the Content Engines.

Note   You cannot delete a cluster if any of its Content Engines are the last node assigned to a location that is designated as the root location for a hosted domain. If you receive an error referencing the root location for a hosted domain, add more Content Engines to that location, or change the root location for the hosted domain before attempting to delete the cluster again.

To delete a cluster:

Step 2   From the drop-down list, choose SuperNodes. The View Supernodes page appears. (See Figure 2-12.)

Step 3   Click the edit icon next to the name of the supernode containing the cluster you wish to delete. The Modify a Supernode page appears. (See Figure 3-4.)

Step 4   Click the icon next to the name of the cluster you wish to edit. The Modify a Cluster page appears. (See Figure 3-5.)

Step 5   Click the Delete button. You are prompted to confirm your decision to remove the cluster from the CDN.

Step 6   Click OK. You are returned to the View Supernodes page.

Working with Content Providers

You work with content providers by:

• Modifying Content Providers
  
  
• Deleting Content Providers
  
  

Modifying Content Providers

You can modify a content provider by changing the company name and address, the primary contact information, or the optional secondary contact information.

To modify a content provider, follow these steps:

The View Content Providers page appears. (See Figure 2-1.)

Step 2   Click the edit icon next to the content provider name that you want to modify.

The Modify a Content Provider page appears. (See Figure 3-6.)

Step 3   Enter any changes you want to make to the company name and address, the primary contact information, or the optional secondary contact information.

---

Note   Clicking Cancel returns all values to their previous settings when you last clicked Save.

---

Step 4   Click Save.

Deleting Content Providers

You can delete content providers as needed.

---

Note   When you delete a content provider, all hosted domains that have been added for the content provider are also deleted.

---

To delete a content provider, follow these steps:

The View Content Providers page appears. (See Figure 2-1.)

Step 2   Check the check box next to the content providers that you want to delete.

Step 3   Click Delete.

Working with Hosted Domains

Using the features of the Content Distribution Manager, you can modify or remove hosted domains that have been created. Keep in mind that modifying your hosted domain may affect the availability of content on the CDN.

You work with hosted domains by:

• Viewing Hosted Domains
  
  
• Modifying Hosted Domains
  
  
• Deleting Hosted Domains
  
  
• Updating Hosted Domain Content
  
  
• Purging Hosted Domains
  
  
• Viewing the Status of Content Replication to a Hosted Domain
  
  

Viewing Hosted Domains

You can view hosted domains across your CDN, or according to the content provider with which they are associated.

Viewing All Hosted Domains on Your CDN

To view hosted domains across your CDN:

Step 2   Choose Hosted Domains from the drop-down list.

The View Hosted Domains page appears. (See Figure 2-16.)

The content provider with which the hosted domains are associated is listed in the Content Provider column.

Viewing Hosted Domains Belonging to a Content Provider

To view hosted domains sorted by content provider:

The View Content Providers page (see Figure 2-1) appears, displaying a list of all content providers on your CDN.

Step 2   Click the content provider name. The screen refreshes, displaying a list of hosted domains associated with the selected content provider.

Modifying Hosted Domains

You can modify a hosted domain by changing the following items:

• Hosted domain name
  
  
• Hosted domain alias
  
  
• Origin server
  
  
• Content provider
  
  
• Manifest file (identifying hosted content)
  
  

To modify a hosted domain, follow these steps:

Step 2   Choose Hosted Domains from the drop-down list.

The View Hosted Domains page appears. (See Figure 2-16.)

Step 3   Click the icon adjacent to the name of the hosted domain that you want to change. The Modify a Hosted Domain page appears. (See Figure 3-7.)

Step 4   Use the fields provided under the Hosted Domain heading to modify the hosted domain name, origin server for the hosted domain content, or CDN content provider that the hosted domain is associated with. Refer to the following guidelines when necessary:

• Your origin server field cannot contain a path to a subdirectory on the server. For example:
  
  

www.cisco.com 

is a valid origin server address, whereas the following address is not:

www.cisco.com/support 

• A valid CDN hosted domain name must use the following format:
  
  • The hosted domain name must be a valid, fourth-level domain name. For example:
    

  www.cdn.cisco.com
   
  

  • The first part of the domain name (www in the example above) is open, and can be defined by you when you create the hosted domain name.
    
    
  • The remaining subdomain (the three segments after the first dot) must correspond to entries on your DNS server to provide a functional mapping for the Content Routers.
    
    
  • The CDN must be given the right to act as the authoritative DNS server for the subdomain you specify.
    

    ---

    Note   The hosted domain name cannot contain underscore (_) characters.

    ---

Step 5   In the Alias field, enter an optional alias for the hosted domain. For example, if your hosted domain name is:

www.cdn.cisco.com

but you want to use a third-level instead of a fourth-level domain name on all your published links, you can use the Alias field to map a third-level domain name to your host domain name such as:

www.cisco-cdn.com

---

Note   You must provide a CNAME mapping between the delegated domain and your alias on the DNS server before aliasing will work. Entering your alias on the hosted domains page is not sufficient to enable hosted domain aliasing.

---

Step 6   Use the fields provided under the Manifest heading to modify the location or information identifying the manifest file for the hosted domain. The manifest file provides information about live and video-on-demand (VOD) content served from the hosted domain. See the "Creating a Manifest File for Importing Media" section for instructions on creating a manifest file for your hosted domain.

• The URL field contains the address of the manifest file for the hosted domain.
  
  
• The Space Required field identifies the amount of disk space reserved on your Content Engines for content identified in the manifest.
  
• The Refresh Time field identifies the frequency with which the Content Engines assigned to the hosted domain check for updates to the manifest file.
  
• The Username and Password fields allow you to enter any secure login information needed to access the manifest file at its remote location.
  
  

Step 7   Under the DNS Trace heading, enter the length of time (in minutes) that the DNS Trace feature will be enabled on the Content Engines assigned to the hosted domain. See the "Enabling and Disabling DNS Trace" section for detailed information on using the DNS trace feature.

Step 8   If you wish to add comments regarding the hosted domain for the benefit of other Content Distribution Manager users, enter them in the Comments field provided.

Step 9   Click Save to save any changes you have made to the hosted domain configuration. The Content Distribution Manager updates the hosted domain information.

Adding and Removing Content Engines from a Hosted Domain

To add Content Engines to a hosted domain:

Step 2   Click the Assign CEs by Region or Assign CEs by Virtual CDN tab, depending on how you wish to locate the Content Engines you are adding.

---

Note   Content Engines can be added to the hosted domain from more than one virtual CDN or region.

---

Step 3   Select the region or virtual CDN in which the Content Engines reside.

• If you are searching for Content Engines by region, a list of locations in the region appears. Click the location of the region in which the Content Engines are located.
  
  
• If you are searching for Content Engines by virtual CDN, a list of virtual CDNs appears.
  
  

Step 4   Click the name of the location or virtual CDN in which the Content Engines you wish to add are located. A list of the Content Engines and clusters in that location appears.

---

Note   As you move down into virtual CDNs, or from regions to locations, your path is saved in the header area just above the Add Selected CEs button. Click the link at any point in the path to return to that point.

---

Step 5   Check the box adjacent to the name of the cluster or Content Engine that you wish to associate with the hosted domain.

---

Note   To choose all Content Engines, you can choose the topmost check box (next to the Cluster or Content Engine heading).

---

Step 6   Click Add Selected CEs and then click Save to add the Content Engines to your hosted domain.

The list of clusters or Content Engines to which the hosted domain is assigned refreshes, listing the newly added Content Engine or cluster.

Step 7   To remove Content Engines, check the box next to the name of the Content Engines you wish to remove from this list and click Remove Selected CEs.

Step 8   If you wish to locate Content Engines in a different region or virtual CDN, repeat Step 2 through Step 6 for each Content Engine that you wish to add.

Step 9   To change the root location for the hosted domain, choose a new location from the Root Location drop-down list. The root location must contain a minimum of one node.

Step 10   Click Save. The browser window refreshes, listing the updated hosted domains. The list of Content Engines in the hosted domain shows the updated count.

Deleting Hosted Domains

To delete a hosted domain, follow these steps:

Step 2   From the drop-down list, choose Hosted Domains.

The View Hosted Domains page appears. (See Figure 2-16.)

Step 3   Click the icon adjacent to the name of the hosted domain that you want to delete.

The Modify a Hosted Domain page appears. (See Figure 3-7.)

Step 4   Click Delete. You are prompted to confirm your decision to delete the hosted domain.

Step 5   Click OK to confirm your decision. The hosted domain is removed from the CDN.

Updating Hosted Domain Content

At any point after you have replicated content to the Content Engines that are associated with your hosted domain, you can update that content using the fetch manifest feature. For example, if you modify your manifest file to point to new content or remove references to content that you want to make obsolete, you must fetch the manifest file to begin replication of any new hosted domain content, and to sever connections to content that you want to make obsolete.

Note   Content that is removed from the manifest file is made unavailable as soon as that updated manifest file is fetched. Obsolete content is not immediately deleted from the hosted domain cache but is eventually removed to make room for new hosted domain content.

To fetch updated content from your origin server and replicate it to your Content Engines:

Step 2   From the drop-down list, choose Hosted Domains.

The View Hosted Domains page appears. (See Figure 2-16.)

Step 3   Follow the instructions for modifying an existing hosted domain in the "Modifying Hosted Domains" section to open your hosted domain for editing.

Step 4   Verify that the URL field points to the correct manifest file for the hosted domain.

Step 5   Click Fetch Manifest. You are prompted to confirm your decision to begin copying the updated content named by the manifest file to the Content Engines assigned to the hosted domain.

Step 6   Click OK. You are returned to the View Hosted Domains page. (See Figure 2-16.)

Step 7   You can view the status of media replication from the origin server to your Content Engines at any time. See the "Viewing the Status of Content Replication to a Hosted Domain" section for instructions.

Purging Hosted Domains

You can purge a hosted domain as needed. Purging a hosted domain deletes the content from all Content Engines that store the hosted domain content, making room for new content.

To purge a hosted domain, follow these steps:

Step 2   From the drop-down list, choose Hosted Domains.

The View Hosted Domains page appears. (See Figure 2-16.)

Step 3   Click the icon next to the hosted domain that you want to purge. The Modify a Hosted Domain page appears. (See Figure 3-7.)

Step 4   Click Purge Content. You are prompted to confirm your decision to remove all cached content from the hosted domain.

Step 5   Click OK to confirm your decision.

Viewing the Status of Content Replication to a Hosted Domain

For any hosted domain, you can view the status of content replication to the Content Engines on that hosted domain.

To view the replication status of your hosted domain:

Step 2   From the drop-down list, choose Hosted Domains.

The View Hosted Domains page appears. (See Figure 2-16.)

Step 3   Click the edit icon next to the name of the hosted domain you wish to edit. The browser window refreshes, displaying the Modify a Hosted Domain page. (See Figure 3-7.) Fields for editing the selected hosted domain appear.

Step 4   Click the Replication Status button. The View Content Replication Status page appears, which provides a graphic representation of the progress of content replication for each Content Engine.

Step 5   Click Update to refresh your screen and obtain current replication status information.

---

Note   It may take a few moments for the replication status to be updated on the Replication Status display when a Content Engine encounters errors in a manifest file.

---

Viewing the Content Replication Log for a Content Engine

Content Engines log each piece of content that is replicated to or purged from them in a text-format log file. Replication log files take the name of the hosted domain to which they apply, and are maintained for each Content Engine in the hosted domain. For example:

hosted_domain_name.log
 

You can use the replication log to review the replication activity for a given device and determine which content items were and were not successfully copied from your origin server to the Content Engine. For example:

Thu May 10 19:04:45 GMT 2001 Filler [I]:  
/www.cdn.cisco.com/SeaLion.mpeg#23 Imported.
Thu May 10 19:05:02 GMT 2001 Filler [I]:  
/www.cdn.cisco.com/Madonna-Music.mpeg#19 Imported.
Thu May 10 19:05:06 GMT 2001 Filler [I]:  
/www.cdn.cisco.com/Everclear-Wonderful.mpeg#22 Imported.
 

To view the content replication log for a Content Engine on your hosted domain:

Step 2   From the drop-down list, choose Hosted Domains.

The View Hosted Domains page appears. (See Figure 2-16.)

Step 3   Click the edit icon next to the name of the hosted domain you wish to edit. The browser window refreshes, displaying the Modify a Hosted Domain page. (See Figure 3-7.) Fields for editing the selected hosted domain appear.

Step 4   Click the Replication Status button. The View Content Replication Status page appears, which provides graphic representations of the progress of content replication for each Content Engine.

Step 5   Click the Update button to display the most current replication status information.

Step 6   Adjacent to the name of the Content Engine for which you wish to view the replication log, click the page icon. You are prompted to download the file from the Content Engine.

Step 7   Click the Open File or Save to File button and click OK. You can view the log file using any ASCII text editor.

Printing and Exporting CDN Data

Using the features of the Content Distribution Manager, you can output any tabular data on your CDN network in either printed or electronic format. This includes lists of customers, virtual CDNs, regions and locations, or any of the resources of your CDN, such as Content Engines, hosted domains, and so on.

Once output, your CDN data can be incorporated into presentations or, in electronic format, imported into spreadsheets or other third-party applications.

To print or export data from the Content Distribution Manager:

For example, if you wanted to print or export data on the regions defined for your CDN, you would click networks to display the list of all regions for the CDN. Alternatively, you could click resources and then choose Regions from the drop-down list to achieve the same result.

Step 2   With the data you would like to print or export displayed on the Content Distribution Manager, click the appropriate button above the displayed data:

• To print your CDN data using the default printer on your operating system, click Print.
  
  
• To export your CDN data to a comma-separated file that can be imported to a spreadsheet or other third-party application, click Export. You are prompted to save or open a file named exportcsv.jsp. This is your comma-separated file containing the data from the table.
  
  

Step 3   Click Save and choose a location on your workstation or network for the file.