Cisco ACNS Software Deployment and Configuration Guide, Release 5.0 - Chapter 7: Working with CDN Devices [Cisco Application and Content Networking System (ACNS) Software]

Table Of Contents

Working with CDN Devices

Working with Content Distribution Managers

Viewing the Content Distribution Manager Configuration

Configuring a Warm Standby Content Distribution Manager

Switching a Content Distribution Manager from Warm Standby to Primary

Deleting a Warm Standby Content Distribution Manager

Working with Content Engines

Viewing the Content Engine Configuration

Modifying Content Engine Properties

Adding New Acquisition and Distribution Bandwidth Settings

Rebooting a Content Engine

Deleting a Content Engine

Viewing Content Engine Channel Assignments

Commands Related to Content Acquisition and Distribution

Working with Content Routers

Modifying Content Router Properties

Deleting a Content Router

Viewing the Content Router Configuration

Working with Device Groups

Creating and Modifying Device Groups

Adding and Removing Content Engines from a Device Group

Enabling Device Group Overlap

Deleting a Device Group

Viewing Device Groups

Local Device Configuration Versus Central Management

Repurposing a CDN Device

Working with CDN Devices

This chapter provides information about configuring CDN device properties. It contains the following sections:

•Working with Content Distribution Managers

•Working with Content Engines

•Working with Content Routers

•Working with Device Groups

•Local Device Configuration Versus Central Management

•Repurposing a CDN Device

Working with Content Distribution Managers

You work with Content Distribution Managers by:

•Viewing the Content Distribution Manager Configuration

•Configuring a Warm Standby Content Distribution Manager

•Switching a Content Distribution Manager from Warm Standby to Primary

•Deleting a Warm Standby Content Distribution Manager

Viewing the Content Distribution Manager Configuration

To view the Content Distribution Manager configuration, follow these steps:

Step 1 From the Content Distribution Manager GUI, choose Devices > CDM.

Step 2 Click the Edit icon next to the name of the Content Distribution Manager that you want to view.

Step 3 The Modifying Content Distribution Manager window appears that shows the basic network settings that were configured at initial setup through the CLI.

Step 4 To view configuration settings, choose Show/Clear Commands > Show Commands in the Contents pane.

Step 5 Choose a show command from the drop-down list and click Submit.

A popup window appears, showing the CLI output for the command.

Configuring a Warm Standby Content Distribution Manager

To configure a device to be a warm standby Content Distribution Manager, follow these steps:

Step 1 If the device is not already configured as a Content Distribution Manager, set the device mode by using the device mode command.
DeviceName# configure
DeviceName(config)# device mode content-distribution-manager
See the "Repurposing a CDN Device" section.

Step 2 Determine the primary Content Distribution Manager clock setting by using the show clock command. For example,
PrimaryCDM# show clock
Fri Jan 31 15:02:28 UTC 2003
Step 3 Set the standby Content Distribution Manager clock to match the primary Content Distribution Manager by using the clock set EXEC command.
DeviceName(config)# exit
DeviceName# clock set 15:02:28 31 january 2003
Step 4 Configure the Content Distribution Manager to be in standby mode by using the global configuration cdm role standby command.
DeviceName# configure
DeviceName(config)# cdm role standby
Step 5 Specify the primary Content Distribution Manager IP address by using the global configuration cdm ip command.
DeviceName(config)# cdm ip ip_addr
Step 6 Register the device and enable management services by using the global configuration cms enable command.
DeviceName(config)# cms enable
Verify that the registration was successful. The output from this command should say whether the registration was successful or not.

Step 7 Before saving the configuration to Flash memory, use the show cms info command to verify the time of the last update.
CDM# show cms info
Registration information :
Device Mode                      = cdm
Model                            = CDM4630
Node Id                          = 96
Time of last update              = Fri Jan 31 15:59:28 2003
To be current, the update time should be between 1 and 5 minutes old. You are verifying that the standby Content Distribution Manager has fully replicated the primary Content Distribution Manager configuration. If the update time is not current, see if there is a connectivity problem or if the primary Content Distribution Manager is down. Fix the problem if necessary, and wait until the configuration has replicated as indicated by the time of the last update.

Also, use the show cms processes command to verify that all management services are running. For example:
CDM# show cms processes 
Service cms_httpd running
Service cms_ui running
Service cms_cdm running
Step 8 Save the configuration to Flash memory by using the copy running-config startup-config EXEC command.
DeviceName(config)# exit
DeviceName# copy running-config startup-config
Switching a Content Distribution Manager from Warm Standby to Primary

If your primary Content Distribution Manager becomes inoperable for some reason, you can manually reconfigure one of your warm standby Content Distribution Managers to be the primary Content Distribution Manager.

To switch a warm standby Content Distribution Manager to be a primary Content Distribution Manager, follow these steps:

Step 1 Check the status of recent updates from the primary Content Distribution Manager. Use the show cms info EXEC command and check the time of the last update.
DeviceName# show cms info
To be current, the update time should be between 1 and 5 minutes old. You are verifying that the standby Content Distribution Manager has fully replicated the primary Content Distribution Manager configuration. If the update time is not current, see if there is a connectivity problem or if the primary Content Distribution Manager is down. Fix the problem, if necessary, and wait until the configuration has replicated as indicated by the time of the last update.

Step 2 Make sure that both Content Distribution Managers have the same Coordinated Universal Time (UTC) configured. Use the show clock detail command to check the time on each device. For example,
CDM1# show clock detail
Local time: Thu Mar  6 19:03:25 UTC 2003
  UTC time: Thu Mar  6 19:03:25 UTC 2003
Epoch: 1046977405 seconds
UTC offset: 0 seconds (0 hours 0 minutes)
If the UTC time does not match, use the clock EXEC command to configure the time and then use the clock timezone UTC global configuration command to match the UTC offset. For example,
CDM2# clock set 19:03:25 mar 06 2003 
CDM2# configure
CDM2(config)# clock timezone UTC 0 0
Step 3 Configure the new role by using the global configuration cdm role primary command.
DeviceName# configure
DeviceName(config)# cdm role primary
This command changes the role from standby to primary and restarts the management service to recognize the change.

Step 4 Save the configuration to Flash memory by using the copy running-config startup-config EXEC command.
DeviceName(config)# exit
DeviceName# copy running-config startup-config
If you switch a warm standby Content Distribution Manager to primary while your primary Content Distribution Manager is still online and active, both Content Distribution Managers detect each other, automatically shut themselves down, and disable management services. The Content Distribution Managers are switched to halted role, which is automatically saved in Flash memory.

To return halted Content Distribution Managers to online status, follow these steps:

Step 1 Choose a role (active or standby) for each Content Distribution Manager.

Step 2 Change the role using the cdm role command.

Step 3 Enable management service using the cms enable command.

Step 4 Save the configuration using the copy running-config startup-config command.

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 on line 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 GUI.

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, follow these steps:

Step 1 Log in directly to the Content Distribution Manager CLI, and enter the cms deregister command.

If for some reason the deregistration fails, you can force the deregistration by using the cms deregister force command.

Step 2 From the Content Distribution Manager GUI, choose Devices > CDM.

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 Modifying Content Distribution Manager window.

Step 4 Click the Trash icon. You are prompted to confirm your decision.

Step 5 Click OK to execute your request.

Working with Content Engines

You work with Content Engines by:

•Viewing the Content Engine Configuration

•Modifying Content Engine Properties

•Rebooting a Content Engine

•Deleting a Content Engine

•Viewing Content Engine Channel Assignments

Viewing the Content Engine Configuration

To view the Content Engine configuration, follow these steps:

Step 1 From the Content Distribution Manager GUI, choose Devices > Content Engines.

Step 2 Click the Edit icon next to the name of the Content Engine that you want to view.

Step 3 In the Contents pane, choose CDN Settings > Status.

The View Network Configurations for Content Engine window appears that shows the basic network settings that were configured at initial setup through the CLI.

Figure 7-1 View Network Configurations for Content Engine Window

Step 4 Alternatively, in the Contents pane, choose Show/Clear Commands > Show Commands.

Step 5 Choose a show command from the drop-down list and click Submit.

A popup window appears, showing the CLI output for the command.

Modifying Content Engine Properties

Use the Content Distribution Manager GUI to make changes to Content Engine properties.

To modify the Content Engine properties, follow these steps:

Step 1 From the Content Distribution Manager GUI, choose Devices > Content Engines.

Step 2 Click the Edit icon next to the name of the Content Engine that you want to modify. The Modifying Content Engine window appears with fields for editing the properties of the selected Content Engine. (See Figure 7-2.)

Figure 7-2 Modifying Content Engine Window

Step 3 Enter the general configuration information about the Content Engine that you want to change.

•To change the name of the Content Engine, enter a new name in the Name field.

•To change the location of the Content Engine, choose a new location from the drop-down list.

•To modify the description used to identify the Content Engine, enter a new description in the Comments field at the bottom of the window.

Step 4 To enable routing on the Content Engine, check the Enable Request Routing check box.

Step 5 If you wish to have a local coverage zone file overwrite the CDN-wide coverage zone file on this routing-enabled Content Engine, you can choose a file from the Coverage Zone File drop-down list.

The Coverage Zone File drop-down list contains the destination paths of all valid coverage zone files registered to your CDN. When you select a coverage zone file from this list, the Content Engine uses this coverage zone file to redirect the user's request. (For information on registering and applying coverage zones, see the "Registering and Applying a User-Defined Coverage Zone" section.)

Step 6 Change the configuration properties as needed for content that is being acquired and distributed.

Table 7-1 describes the Content Engine configuration fields that you can modify.

Table 7-1 Content Engine Configuration Properties

Content Engine Configuration Property

Description

General Configuration

Name

Identifier for the Content Engine. This name is used by content routing and therefore must conform to the following rules:

•Use only alphanumeric characters and hyphens (-).

•The first and last character must be a letter or a digit.

•Maximum length is 63 characters.

•Names are case-insensitive.

Note The following characters are considered illegal and cannot be used when naming a device:
@, #, $,%, ^, &, *, (), |, \""/, <>.

Status

Content Engine status: online, pending, or inactive.

cdnfs

Current setting for cdnfs pre-positioned content disk space allocation. This value cannot be modified from this window. (See the "Updating Storage Capacity Through the Content Distribution Manager GUI" section.)

Set Default Coverage Zone file

When checked, generates a default coverage zone with the Content Engine serving the local subnet it resides on. The coverage zone is a CDN-wide mapping of user client addresses to the Content Engine addresses that should respond to requests for that client.

Locality

Location*¹

Location of the Content Engine.

Network topology locations organize and group Content Engines into virtual networks for content distribution. Locations must be configured beforehand. (See the "Creating and Modifying Locations" section.)

Acquisition and Distribution Information

Acquisition and Distribution Proxy Hostname

This feature is to be implemented in a future release of ACNS software.

Acquisition and Distribution Proxy Port

This feature is to be implemented in a future release of ACNS software.

Request Routing

Enable Request Routing

When checked, enables the Content Engine to act as a simplified hybrid content router as well as a Content Engine.

Coverage Zone File

Allows you to select an imported coverage zone file for simplified hybrid routing.

Default Bandwidth

Acquisition-in

Default bandwidth in kbps² for incoming content acquisition traffic from origin servers.

Multicast-out

Default multicast-out bandwidth setting. This setting is configured when you create or modify multicast clouds. (See the "Creating and Modifying Multicast Clouds" section.)

Distribution-in

Default bandwidth in kbps for incoming unicast content distribution traffic from Content Engines.

Distribution-out

Default bandwidth in kbps for outgoing unicast content distribution traffic to Content Engines.

¹* = this field is required.

²kbps = kilobits per second.

Step 7 Click Submit.

Adding New Acquisition and Distribution Bandwidth Settings

In addition to being able to set the default bandwidth limits for incoming and outgoing traffic on the Content Engine, you can use the Content Distribution Manager GUI to configure different limits for different time segments that form a week-long cycle. For example, you can configure the acquisition-in limit at a maximum of 100 kbps from 8:00 a.m. to 8:00 p.m., Monday through Friday, and extend that limit to as high as 10 Mbps during the nights from 8:00 p.m. to 8:00 a.m., Monday through Friday and all day Saturday and Sunday. These settings override the default value for the time and period that you specify.

Note For a schedule from 8:00 p.m. to 8:00 a.m., the administrator must configure two schedules in order to span the two days: one from 8:00 p.m. to 11:59 p.m. (20:00 to 23:59) and another from 12:00 a.m. to 8:00 a.m. (00:00 to 08:00).

Note Distribution bandwidth settings apply only to unicast distribution.

To configure custom bandwidth settings for specific days and times, follow these steps:

Step 1 From the Content Distribution Manager GUI, choose Devices > Content Engines. The Content Engines window appears.

Step 2 Click the Edit icon next to the name of the Content Engine that you want to view. The Modifying Content Engine window appears.

Step 3 In the Contents pane, choose CDN Settings > Acquisition & Distribution Bandwidth. The A&D Bandwidth Settings window appears.

Step 4 Click the Add Bandwidth Specification icon in the taskbar. The Add New A&D Bandwidth Settings window appears. (See Figure 7-3.)

Figure 7-3 Add New A&D Bandwidth Settings Window

Step 5 Choose a bandwidth type from the drop-down list.

Step 6 Enter the bandwidth rate, start time, end time, and day of the week in the appropriate fields. (See Table 7-2 for a description of each field. All fields are required.)

Table 7-2 Configuring Bandwidth Settings

Field

Description

Bandwidth Type*¹

Distribution-in—For incoming unicast content distribution traffic from Content Engines.

Distribution-out—For outgoing unicast content distribution traffic to Content Engines.

Acquisition-in—For incoming content acquisition traffic from origin servers.

Bandwidth Rate*

Maximum amount of bandwidth you want to allow in kbps.

Start Time*

Time of day for the bandwidth rate setting to begin, using a 24-hour clock in local time (hh:mm).

End Time*

Time of day for the bandwidth rate setting to end.

Day Selection*

Days on which bandwidth settings apply.

¹* = this field is required.

Step 7 Click Submit.

Rebooting a Content Engine

Using the Content Distribution Manager GUI, you can reboot a Content Engine or group of Content Engines remotely. This option causes the Content Distribution Manager to perform a controlled shutdown of all Content Engines and then restarts the operating system on each device.

To reboot an individual Content Engine, follow these steps:

Step 1 From the Content Distribution Manager GUI, choose Devices > Content Engines.

Step 2 Click the Edit icon next to the name of the Content Engine that you wish to reboot. The browser window refreshes, displaying the Modifying Content Engine window. (See Figure 7-2.)

Step 3 Click the Reboot icon. You are prompted to confirm your decision.

Step 4 Click OK to begin rebooting the Content Engine.

To reboot an entire device group, follow these steps:

Step 1 From the Content Distribution Manager GUI, choose Devices > Device Groups.

Step 2 Click the Edit icon next to the name of the device group that you want to reboot. The Device Group window appears.

Step 3 Click the Reboot icon. You are prompted to confirm your decision.

Step 4 Click OK to begin rebooting each Content Engine in the device group.

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 node and the content it contains from the routing scheme that the CDN software uses to fill user requests. Although ACNS 5.0 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 channel. If you receive an error referencing the root location for a channel, add more Content Engines to that location, or change the root location for the channel before attempting to delete the Content Engine again.

Before a node can be removed from the CDN, the following conditions must be met:

•The device must have been activated in the Content Distribution Manager. (See the "Activating Content Engines or Content Routers in the Content Distribution Manager GUI" section.)

•The Content Distribution Manager must be running.

•The device must have the correct Content Distribution Manager IP address or host name configured.

•The Content Distribution Manager IP address or host name must point to the primary Content Distribution Manager.

Deleting a Content Engine from the CDN involves using the CLI to remove the registration information from the Content Engine itself and remove the registration record from the Content Distribution Manager GUI.

If the Content Engine is being removed because of system disk failure, see the "Recovering from Missing Disk-Based Software" section.

Note Do not use the Content Distribution Manager GUI to delete a Content Engine while the Content Engine is still active and registered. The GUI delete feature only removes the Content Engine's registration record from the Content Distribution Manager; it does not deregister the device. The Content Engine retains its registration information and continues to contact the Content Distribution Manager; however, the Content Distribution Manager no longer recognizes the Content Engine.

If for some reason the Content Distribution Manager loses the registration record of a device, use the cms deregister force command on the device to remove all of its registration information. Then use the cms enable command to reregister the device with the Content Distribution Manager as though it were a new node in the CDN.

To delete a Content Engine, follow these steps:

Step 1 Open a Telnet session to the Content Engine CLI.

Step 2 Enter the no cms enable command in global configuration mode.
CE-507# configure
CE-507(config)# no cms enable
Step 3 Enter the cms deregister command in EXEC mode.
CE-507(config)# exit
CE-507# cms deregister
Note The cms deregister command cleans up the database automatically. You do not need to use the cms database delete command.

Step 4 If for some reason the deregistration fails, you can force the deregistration by using the cms deregister force command.
CE-507# cms deregister force
Note Ignore any messages stating that the deregistration failed. The cms deregister force command forces the deregistration to continue.

Step 5 To add the device back in to the CDN, reregister the device with the Content Distribution Manager by using the cms enable command in global configuration mode.
CE-507# configure
CE-507(config)# cms enable
Viewing Content Engine Channel Assignments

You can use the Modifying Content Engine page to view which channels a particular Content Engine is assigned to. You can view channel assignments for a bird's eye view of how a given Content Engine is deployed across your CDN—which channel it belongs to, the website, content provider, and manifest URL.

To view channel assignments for a Content Engine, follow these steps:

Step 1 From the Content Distribution Manager GUI, choose Devices > Content Engines.

Step 2 Click the Edit icon next to the name of the Content Engine for which you wish to view channel assignments. The Modifying Content Engine window appears.

Step 3 In the Contents pane, choose CDN Settings > Channels. The View Channels window appears, listing all the channels to which the Content Engine is assigned.

Commands Related to Content Acquisition and Distribution

Table 7-3 lists and describes the commands related to viewing content acquisition information. For complete descriptions of these commands, including usage guidelines and examples, refer to the Cisco ACNS Software Command Reference, Release 5.0 publication.

Table 7-3 Acquisition-Related Commands

Command

Syntax

Description

acquirer

start-channel

stop-channel

acquirer {start-channel {channel-id channel_num | channel-name channel-name} | stop-channel {channel-id channel_num | channel-name channel-name}}

Starts or stops content acquisition on a specified acquirer channel.

show acquirer

channels

progress

show acquirer channels {channel-id channel_num | channel-name channel-name} | progress {channel-id channel_num | channel-name channel-name}

Displays the acquirer information for the channels specified for which the Content Engine is the root Content Engine.

show statistics acquirer

channel-name

contents

errors

job-list

show statistics acquirer [channel-id channel-num | channel-name name | contents {channel-id channel-num | channel-name name} | errors {channel-id channel-num | channel-name name} | job-list {channel-id channel-num | channel-name name}]

Displays acquirer channel statistics for all the channels for which the Content Engine is the root Content Engine.

Table 7-4 lists and describes the commands related to viewing content distribution information. For complete descriptions of these commands, including usage guidelines and examples, refer to the Cisco ACNS Software Command Reference, Release 5.0 publication.

Table 7-4 Distribution-Related Commands

Command

Syntax

Description

show distribution

channel

forwarder-list

mcast-data-receiver

mcast-data-sender

processes

show distribution {channel {channel-id channel-num | channel-name name} | forwarder-list [detail] [channel-id channel-num [detail] | channel-name name [detail]] | mcast-data-receiver | mcast-data-sender | processes}

Displays the distribution information for a specified channel.

show statistics distribution

all

mcast-data-receiver

mcast-data-sender

metadata-receiver

metadata-sender

unicast-data-receiver

unicast-data-sender

show statistics distribution {all | mcast-data-receiver | mcast-data-sender | metadata-receiver| metadata-sender | unicast-data-receiver | unicast-data-sender}

Displays the statistics of the content distribution components.

debug distribution

all

mcast-data-receiver

mcast-data-sender

metadata-receiver

metadata-sender

unicast-data-receiver

unicast-data-sender

debug option

Monitors and records ACNS software distribution functions.

Note We recommend that the debug command be used only at the direction of Cisco Systems technical support personnel. Performance is impacted when you run the debug command.

Working with Content Routers

You work with Content Routers by:

•Modifying Content Router Properties

•Deleting a Content Router

•Viewing the Content Router Configuration

Modifying Content Router Properties

You use the Devices tab in the Content Distribution Manager GUI to make changes to a Content Router.

You can modify the following Content Router properties:

•Name

•Location

•Coverage zone file

•Description

To modify a Content Router, follow these steps:

Step 1 From the Content Distribution Manager GUI, choose Devices > Content Routers. The Content Routers window appears, listing all the Content Routers registered in your CDN.

Step 2 Click the Edit icon next to the name of the Content Router that you want to modify. The Modifying Content Router window appears. (See Figure 7-4.)

Figure 7-4 Modifying Content Router Window

Step 3 If you wish to change the location, choose a new location from the Locations drop-down list.

Step 4 If you wish to have a local coverage zone file overwrite the CDN-wide coverage zone file on this router, you can choose a file from the Coverage Zone File drop-down list.

The Coverage Zone File drop-down list contains the destination paths of all valid coverage zone files registered to your CDN. When you select a coverage zone file from this list, the Content Router uses this coverage zone file to redirect the user's request. (For information on registering and applying coverage zones, see the "Registering and Applying a User-Defined Coverage Zone" section.)

Step 5 If you wish to modify the description used to identify the Content Router, enter a new description in the Comments field.

Step 6 Click Submit. A message indicating that the transaction was successfully completed appears at the bottom of the window.

Deleting a Content Router

You can delete a Content Router if the device is experiencing unresolvable problems. If you are deleting the only Content Router in your CDN, you are effectively removing the ability of your CDN to fill user requests unless you have WCCP or proxy routing configured on your CDN.

Removing the node from the CDN involves using the CLI to shut down CDN services and deregister the node. If the node is being removed because of hardware failure and it cannot be accessed through its CLI, you can remove the node using the Content Distribution Manager GUI; however, the node continues to store its registration information until you deregister it in the CLI.

To remove and deregister a Content Router, follow these steps:

Step 1 Open a Telnet session to the Content Router CLI.

Step 2 Enter the no cms enable command in global configuration mode.
CR# configure
CR(config)# no cms enable
Step 3 Enter the cms deregister command in EXEC mode.
CR(config)# exit
CR# cms deregister
Note The cms deregister command cleans up the database automatically. You do not need to use the cms database delete command.

Step 4 If for some reason the deregistration fails, you can force the deregistration by using the cms deregister force command.
CR# cms deregister force
Note Ignore any messages stating that the deregistration failed. The cms deregister force command forces the deregistration to continue.

Step 5 To add the device back in to the CDN, reregister the device with the Content Distribution Manager by using the cms enable command in global configuration mode.
CR# onfigure
CR(config)# cms enable
In case of a hardware failure, you might need to remove the node from the CDN routing scheme using the Content Distribution Manager GUI.

Before a node can be removed from the CDN through the Content Distribution Manager GUI, the following conditions must be met:

•The device must have been activated in the Content Distribution Manager. (See the "Activating Content Engines or Content Routers in the Content Distribution Manager GUI" section.)

•The Content Distribution Manager must be running.

•The device must have the correct Content Distribution Manager IP address or host name configured.

•The Content Distribution Manager IP address or host name must point to the primary Content Distribution Manager.

To delete a Content Router using the Content Distribution Manager GUI, follow these steps:

Step 1 From the Cisco Content Distribution Manager GUI, choose Devices > Content Routers. The Content Routers window appears, listing the Content Routers in your CDN. (See Figure 7-5.)

The online status of the device is listed in the Status column.

Figure 7-5 Content Routers Window

Step 2 Click the Edit icon next to the name of the Content Router that you wish to delete. The Modifying Content Router window appears.

Step 3 Click the Trash icon. You are prompted to confirm your decision.

Step 4 Click OK to execute your request. The Content Router is removed from the Content Distribution Manager GUI.

Step 5 If possible, access the Content Router CLI to deregister the Content Router.

Step 6 Enter the cms deregister force command.

Note You must use the cms deregister force command after deleting a device in the Content Distribution Manager GUI, because once the device has been deleted, the Content Distribution Manager no longer has a record of the device.

Step 7 To add the device back in to the CDN, reregister the device with the Content Distribution Manager by using the cms enable command in global configuration mode.

Viewing the Content Router Configuration

You can use the Devices tab in the Content Distribution Manager GUI to view the configuration of a Content Router. To view the Content Router configuration, follow these steps:

Step 1 From the Content Distribution Manager GUI, choose Devices > Content Routers. The Content Routers window appears, listing all the Content Routers registered in your CDN.

Step 2 Click the Edit icon next to the name of the Content Router that you want to view. The Modifying Content Router window appears.

Step 3 In the Contents pane, choose CDN Settings > Status. The View Network Configurations for Content Router window appears. (See Figure 7-6.)

Figure 7-6 View Network Configurations for Content Router Window

Working with Device Groups

A device group is a set of similar devices (such as Content Engines) that share common qualities and capabilities. Some common qualities might include disk capacity, distribution minimum bandwidth, or routing properties.

Device groups are assigned to channels through the Content Distribution Manager GUI. Whenever a channel is created and additional device groups are added, or a channel assignment to the device group changes, devices in the group are notified of the changes and assignments.

Using the device group feature of the Content Distribution Manager, you can create a new device group definition, modify information about a device group, or remove a device group from the system.

You work with device groups by:

•Creating and Modifying Device Groups

•Deleting a Device Group

•Viewing Device Groups

Creating and Modifying Device Groups

To create or modify a device group, follow these steps:

Step 1 From the Content Distribution Manager GUI, choose Devices > Device Groups. The Device Groups window appears. (See Figure 7-7.)

Figure 7-7 Device Groups Window

Step 2 Click the Create New Device Group icon in the taskbar. The Creating New Device Group window appears. (See Figure 7-8.)

Figure 7-8 Creating New Device Group Window

Step 3 Enter the name of the device group in the Name field.

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

Step 4 If you wish, enter comments about the group in the Comments field. This field is optional.

Note If you want to modify the list of Content Engines assigned to the device group, see the "Adding and Removing Content Engines from a Device Group" section.

Step 5 Click Submit.

Step 6 To modify a device group, go to the Device Groups window and click the Edit icon next to the name of the device group that you want to modify. The Modifying Device Group window appears.

Step 7 Change the device group name or description as needed and click Submit.

Adding and Removing Content Engines from a Device Group

Note In ACNS 5.0 software, device groups only support Content Engines. Content Routers cannot be assigned to a device group.

To add or remove Content Engines from a device group, follow these steps:

Step 1 From the Content Distribution Manager GUI, choose Devices > Device Groups.

Step 2 Click the Edit icon next to the name of the device group that you want to edit. The Modifying Device Group window appears.

Step 3 In the Contents pane, click Assign Devices.

Step 4 Click a device location.

Step 5 Check the check box next to the device name or names that you want to assign to the device group and click Add Selected CEs and the click Submit.

Step 6 To view the device group for a Content Engine, choose Devices > Content Engines. Click the Edit icon next to the name of the device. In the Contents pane, choose Basic Settings > Device Groups.

Step 7 To remove a device from a device group, check the check box next to the device name and click Remove Selected CEs and then click Submit.

Enabling Device Group Overlap

If you want the ability to assign a device to more than one device group, you must enable device group overlap. Content Engines can be assigned to multiple device groups when device group overlap is enabled in the Content Distribution Manager GUI. To enable device group overlap, follow these steps:

Step 1 From the Content Distribution Manager GUI, choose System > System Configuration. The Config Properties window appears.

Step 2 Click the Edit icon next to the property name, DeviceGroup.overlap. The Modifying Config Property, DeviceGroup.overlap window appears.

Step 3 In the Value field, enter true. (The default is "false".)

You can return to the default at any time by entering false in the Value field. When you disable device group overlap, existing overlapping device groups are retained and continue to be handled as though overlap were enabled; however, any newly added groups disallow overlapping, and new devices cannot be added to the existing overlapping groups.

Step 4 Click Submit.

Deleting a Device Group

To delete a device group, follow these steps:

Step 1 From the Content Distribution Manager GUI, choose Devices > Device Groups. The Device Groups window appears. (See Figure 7-7.)

Step 2 Click the Edit icon next to the name of the device group that you want to delete. The Modifying Device Group window appears.

Step 3 Click the Trash icon in the taskbar. You are prompted to confirm your decision to delete the device group.

Step 4 Click OK to confirm your decision. The device group is removed from the CDN.

Viewing Device Groups

To view all the device groups in your CDN, follow these steps:

Step 1 From the Content Distribution Manager GUI, choose Devices > Device Groups. The Device Groups window appears. (See Figure 7-7.)

Step 2 Click the View All Device Groups icon in the taskbar to refresh the table.

The table also displays device type and comments. You can sort the columns by clicking the column heading.

Step 3 To print the table data, click the Printer icon in the taskbar.

Local Device Configuration Versus Central Management

Cisco ACNS 5.0 software uses certain CLI commands that are particularly important for CDN functionality, and which are likely to be managed using device groups. If you configure any of these commands from the Content Engine or Content Router, either through the Content Engine GUI or CLI, then the settings are not stored as part of the Content Distribution Manager's CDN-wide configuration data, and are likely to be overwritten by the Content Distribution Manager.

Note We recommend that you do not configure these centrally managed settings from the local device GUI or CLI.

Furthermore, if you configured any of these settings on your Content Engine or Content Router before you registered it with your Content Distribution Manager, you must reconfigure these settings in the Content Distribution Manager GUI.

These commands include the following:

cdp

ldap

logging

ntp

radius-server

tacacs

bandwidth

bypass

dns-cache

ftp

http

https

icp

multicast

ntlm

proxy-auto-config

proxy-protocols

rtsp

excluding:

rtsp server real-subscriber accept-license-agreement

rtsp proxy media-real accept-license-agreement

rtsp-proxy

rule

transaction-logs

url-filter

multicast accept-license-agreement

wmt

excluding:

wmt proxy

wmt accept-license-agreement

wmt live-url-stripping

authentication

error-handling

dns enable

Repurposing a CDN Device

Some hardware models allow you to change the device mode and redeploy the device in your network for a different purpose. For example, you might repurpose a Content Engine as a Content Distribution Manager for failover and redundancy.

The following hardware models support device mode changes:

•CE-7305

•CE-565

To change the device mode of your eligible device, you must be prepared to configure the disk space allocations, as required by the different device modes, and to reboot the device for the new configuration to take effect.

Devices that can be reconfigured using the device mode command are shipped from the factory by default as Content Engines. When you change the device mode of a Content Engine to a Content Router or a Content Distribution Manager, you need to configure the sysfs. (See the "Configuring Disk Space" section.)

If, however, you are changing the device mode of a Content Router or a Content Distribution Manager back to a Content Engine, you must configure disk space allocations for the sysfs, cfs, mediafs, and cdnfs that are used on the Content Engine. (See "Cisco ACNS Software Disk Space-Allocation Guidelines.") For example:
DeviceName# disk config sysfs 10% cfs 20% mediafs 10% cdnfs 60%
Note Enabling content routing on a Content Engine is not considered a device mode change. You do not need to follow this procedure to enable the content routing functionality. (To enable content routing on a Content Engine, see the "Modifying Content Engine Properties" section.)

To change the device mode of a device that is already operating as part of your CDN, follow these steps:

Step 1 Access the device CLI.

Step 2 Enter the show device-mode current command to view the current device mode.
DeviceName# show device-mode current
Current device mode: content-engine
Step 3 Configure the new device mode by using the device mode command in global configuration mode. For example:
DeviceName# configure
DeviceName(config)# device mode content-router
Step 4 Deregister the device by using the cms deregister force command.
DeviceName(config)# cms deregister force
Step 5 Save the configuration by issuing the write memory command or the copy running-config startup-config command.
DeviceName# write memory
DeviceName# copy running-config startup-config
Step 6 Use the restore factory-default preserve basic-config command to reload the software and apply the device mode configuration.
DeviceName# restore factory-default preserve basic-config
Note This command erases all existing content on the device; however, your network settings are preserved and the device is accessible through Telnet and Secure Shell (SSH) after it reboots.

Step 7 Verify the new configuration. Check that the current and configured device modes are the same. For example:
DeviceName# show device-mode configured
Configured Device mode: content-router
DeviceName# show device-mode current
Current device mode: content router
Step 8 Configure the disk space allocation based on the new device mode and needs of your network by using the disk config command.

Step 9 Follow the directions for configuring, registering, and activating new devices in "Setting Up and Registering CDN Devices."