Table Of Contents
Working with Device Configurations
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 Device Locations
Creating and Modifying Locations
Deleting Locations
Viewing the Location Tree
Working with Content Engines
Modifying Content Engine Properties
Rebooting a Content Engine
Deleting a Content Engine
Viewing Content Engine Channel Assignments
Commands Related to Content Acquisition and Distribution
Configuring the Content Engine Common Internet File System Server
Configuring CIFS Server Settings
Configuring CIFS Server Website Access Control Settings
Customizing the CIFS Share Name
Working with Content Routers
Modifying Content Router Properties
Deleting a Content Router
Configuring Services on Content Routers
Working with Device Groups
Creating a Device Group
Assigning Content Engines to the Device Group
Enabling Device Group Overlap
Deleting a Device Group
Viewing Device Groups
Working with Baseline Groups
Configuring a Baseline Group for a Service
Assigning Content Engines to the Baseline Group
Configuring the Service Settings for the Baseline Group
Forcing the Baseline Group Service Settings on All Content Engines in the Baseline Group
Switching the Baseline Group for a Service
Viewing Configured Service Settings for a Device Group
Local Device Configuration Versus Central Management
Repurposing an ACNS Network Device
Working with Device Configurations
An ACNS network is a coordinated system made up of three types of devices: Content Distribution Managers, Content Engines, and, if necessary, Content Routers. To deliver requested content using these devices, proper configuration is necessary. ACNS 5.x software also allows you to configure Content Engines into device groups using the Content Distribution Manager GUI so that content services can be configured for an entire group of Content Engines at one time. Device groups and Content Engines share the same configuration features and options.
This chapter provides information about configuring ACNS network device properties. It contains the following sections:
•
Working with Content Distribution Managers
•Working with Device Locations
•Working with Content Engines
•Working with Content Routers
•Working with Device Groups
•Working with Baseline Groups
•Local Device Configuration Versus Central Management
•Repurposing an ACNS Network Device
Working with Content Distribution Managers
You can work with Content Distribution Managers by performing these tasks:
•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 > Devices.
Step 2 Click the Edit icon next to the name of the Content Distribution Manager that you want to view. The Device Home window appears.
Step 3 To display the entire table of contents, click the Show All button above the Contents pane.
Step 4 In the Contents pane, choose Device Activation. The Modifying Content Distribution Manager window appears, which shows the basic network settings that were configured at initial setup through the CLI.
Step 5 To view configuration settings, choose Monitoring > Show/Clear Commands > Show Commands in the Contents pane.
Step 6 From the drop-down list, choose a show command, and click Submit.
A popup window appears, showing the CLI output for the command.
Configuring a Warm Standby Content Distribution Manager
Note Primary and standby Content Distribution Managers must be running the same ACNS software release. If they are not, the standby Content Distribution Manager detects this problem and shuts down the Centralized Management System (CMS) until the problem is corrected. We recommend that you upgrade your standby Content Distribution Manager first and then upgrade your primary 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(config)# device mode content-distribution-manager
See the "Repurposing an ACNS Network Device" section.
Step 2 Obtain the primary Content Distribution Manager clock setting by using the show clock command, as shown in this example:
Fri Jan 31 15:02:28 UTC 2003
Step 3 Set the standby Content Distribution Manager clock to match the primary Content Distribution Manager clock by using the clock set EXEC command.
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(config)# cdm role standby
Step 5 Specify the primary Content Distribution Manager IP address by using the cdm ip ip_addr global configuration 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 or not the registration was successful.
Step 7 Before saving the configuration to flash memory, use the show cms info command to verify the time of the last update.
Registration information :
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, determine whether or not 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, as shown in this example:
Service cms_httpd running
Step 8 Save the configuration to flash memory by using the copy running-config startup-config EXEC command.
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, check whether 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, as shown in this example:
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 on the two devices, use the clock EXEC command to configure the time and then use the clock timezone UTC global configuration command to match the UTC offset., as shown in this example:
CDM2# clock set 19:03:25 mar 06 2003
CDM2(config)# clock timezone UTC 0 0
Step 3 Configure the new role by using the global configuration cdm role primary command.
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# 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 services 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 ACNS network 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 ACNS network using its new address and configuration information.
When deleting a warm standby Content Distribution Manager from the ACNS network, you are effectively removing that device and the content it contains from the routing scheme that the ACNS 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 > Devices.
The browser refreshes, listing the Content Distribution Managers on your ACNS network. 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 Device Home window appears.
Step 4 In the Contents pane, choose Device Activation. The browser window refreshes, displaying the Modifying Content Distribution Manager window.
Step 5 In the taskbar, click the Trash icon. You are prompted to confirm your decision.
Step 6 To execute your request, click OK.
Working with Device Locations
You can work with locations by performing these tasks:
•Creating and Modifying Locations
•Deleting Locations
•Viewing the Location Tree
Creating and Modifying Locations
Locations are set up in the Content Distribution Manager GUI, and they organize and group Content Engines into virtual networks for distribution of content through channels.
Locations need to be configured before you can activate Content Engines and Content Routers and bring them online in the ACNS network.
To create a new location or modify an existing one, follow these steps:
Step 1 From the Content Distribution Manager GUI, choose Devices > Locations. The Locations window appears. (See Figure 13-1.)
Figure 13-1 Locations Window
Step 2 In the taskbar, click the Create New Location icon. The Creating New Location window appears. (See Figure 13-2.)
Figure 13-2 Creating New Location Window
Step 3 In the Name field, enter a location name.
Note Fields marked with an asterisk are required.
Step 4 From the Parent Location drop-down list, choose a parent location (or choose None).
A location with no parent location assigned is a level 1 location. A location with a level 1 parent becomes a level 2 location, and so forth. The location level is displayed after you choose a parent location (or choose None) and click Submit to save the configuration.
Step 5 In the Comments field, enter comments about the location. This step is optional.
Step 6 To save your settings. click Submit.
Step 7 To modify a location, go to the Locations window, and click the Edit icon next to the name of the location you want to modify.
Step 8 Change the location name, parent location, or description as needed, and click Submit to save the changes.
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 1 From the Content Distribution Manager GUI, choose Devices > Locations. The Locations window appears.
Step 2 Click the Edit icon next to the location that you want to delete.
The Modifying Location window appears.
Step 3 In the taskbar, click the Trash icon. You are asked to confirm your decision to delete the location.
Step 4 To confirm the action, click OK. The location is deleted.
Viewing the Location Tree
The location tree represents the network topology you configured when you assigned a parent to each location. The Content Distribution Manager GUI graphically displays the relationships between the locations configured in your ACNS network.
To view the location tree, choose Devices > Locations. Then in the taskbar, click the Location Trees button. The location tree is displayed.
Working with Content Engines
You can work with Content Engines by performing these tasks:
•Modifying Content Engine Properties
•Rebooting a Content Engine
•Deleting a Content Engine
•Viewing Content Engine Channel Assignments
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 > Devices.
Step 2 Click the Edit icon next to the name of the Content Engine that you want to modify. The Device Home window appears.
Step 3 In the Contents pane, chose Device Activation. The Device Activation window appears with fields for editing the properties of the selected Content Engine. (See Figure 13-3.)
Figure 13-3 Device Activation Window for Modifying Content Engine Properties
Step 4 Under the General Configuration heading, set or modify Content Engine properties.
•To change the hostname of the Content Engine, enter a new name in the Name field.
•To activate or deactivate the Content Engine check or uncheck the Activate check box.
•To set the default coverage zone, check the Set Default Coverage Zone File check box.
Step 5 Under the Locality heading, set or change the location information by choosing a new location from the Location drop-down list.
Step 6 Under the Request Routing Heading, set or modify routing properties.
•To enable routing on the Content Engine, check the Enable Request Routing check box.
•If you wish to have a local coverage zone file overwrite the ACNS network-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 ACNS network. 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 about registering and applying coverage zones, see the "Registering and Applying a User-Defined Coverage Zone" section on page 4-44.)
•To enable the Content Engine as a PAC file server, check the Enable PAC File Server check box.
Step 7 Under the NAT Configuration heading, configure the NAT settings.
•To use the IP address configured on the primary interface of the Content Engine as the management IP address. check the Use CE's primary IP Address check box.
•To allow the Content Distribution Manager to communicate with devices in the ACNS network that are behind the NAT firewall using an explicitly configured IP address, enter the NAT address of the Content Engine in the NAT Address field.
•In the Port field, enter the port number for the NAT address.
Note If the Content Distribution Manager cannot contact a device using the primary IP address, it will attempt to communicate using NAT IP address.
Table 13-1 describes the Content Engine configuration fields that you can either view or modify.
Table 13-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 must conform to the following rules:
•The name must 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
|
Read only. Content Engine status: online, pending, or inactive.
|
Activate
|
When checked, activates the Content Engine for centralized management through the Content Distribution Manager GUI.
|
cdnfs
|
Read only. 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 in the Cisco ACNS Software Update and Maintenance Guide.)
|
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 an ACNS network-wide mapping of user client addresses to the Content Engine addresses that should respond to requests for that client.
|
Locality
|
Location1
|
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 on page 5-3.)
|
Request Routing
|
Enable Request Routing
|
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.
|
Enable PAC File Server
|
Enables the Content Engine to function as a proxy autoconfiguration file server.
|
NAT Configuration
|
Use CE's primary IP Address
|
Enables the Content Distribution Manager to use the IP address configured on the primary interface of the Content Engine to communicate with devices in the ACNS network that are behind a NAT firewall.
|
Use IP Address
|
When checked lets you manually configure a management IP address for the Content Distribution Manager to communicate with devices behind NAT firewall.
If the Content Distribution Manager cannot contact a device using the current management IP address, it will not attempt to communicate using alternative IP addresses.
|
Port
|
Port number to enable communication between the Content Distribution Manager and devices behind a NAT firewall.
|
Step 8 To save your settings. 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 > Devices.
Step 2 Click the Edit icon next to the name of the Content Engine that you wish to reboot. The Device Home window appears.
Step 3 In the taskbar, click the Reload Content Engine icon. You are prompted to confirm your decision.
Step 4 To begin rebooting the Content Engine, click OK.
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 Modifying Device Group window appears.
Step 3 In the taskbar, click the Reboot All Devices in Device Group icon. You are prompted to confirm your decision.
Step 4 To begin rebooting each Content Engine in the device group, click OK.
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 ACNS network using its new address and configuration information.
When you delete a Content Engine from the ACNS network, you are removing that node and the content it contains from the routing scheme that the ACNS software uses to fill user requests. Although ACNS 5.x software routes requests around Content Engines that are busy, offline, or missing, removing a Content Engine may affect the speed at which the ACNS network 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 ACNS network, the following conditions must be met:
•The device must have been activated in the Content Distribution Manager. (See the "Activating Devices in the Content Distribution Manager GUI" section on page 2-21.)
•The Content Distribution Manager must be operating.
•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 be that of the primary Content Distribution Manager.
Deleting a Content Engine from the ACNS network involves using the CLI to remove the registration information from the Content Engine itself and removing the registration record from the Content Distribution Manager GUI.
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 removes only 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 ACNS network.
If the Content Engine is being removed because of system disk failure, see the "Recovering from Missing Disk-Based Software" section in the Cisco ACNS Software Update and Maintenance Guide.
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(config)# no cms enable
Note Issuing the no cms enable command does not disable a primary sender Content Engine and activate the backup sender (or the reverse) if the backup sender is the active Content Engine being removed from the network; however, issuing the cms deregister command does disable the communication between the two multicast senders. The cms deregister command disables the CMS, all acquisition and distribution services, and all routing communications to and from this device.
Step 3 Enter the cms deregister command in EXEC mode.
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 ACNS network, reregister the device with the Content Distribution Manager by using the cms enable command in global configuration mode.
CE-507(config)# cms enable
Viewing Content Engine Channel Assignments
You can use the Device Home page to view the number of channels to which a particular Content Engine is assigned. You can view channel assignments for an overview of how a given Content Engine is deployed across your ACNS network (to which channel it belongs, the channel quota, the website, and the content provider).
To view channel assignments for a Content Engine, follow these steps:
Step 1 From the Content Distribution Manager GUI, choose Devices > Devices.
Step 2 Click the Edit icon next to the name of the Content Engine for which you wish to view channel assignments. The Device Home window appears.
Step 3 In the Device Home window, under Assignments: This Devicename belongs to n Channels, click the Channels link, or in the Contents pane, choose Assignments. The Channel assignments for Content Engine window appears, listing all the channels to which the Content Engine is assigned.
Commands Related to Content Acquisition and Distribution
Table 13-2 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.4 publication.
Table 13-2 Acquisition-Related Commands
Command
|
Syntax
|
Description
|
acquirer
check-time-for-old-
content
start-channel
stop-channel
test-url
|
acquirer {check-time-for-old-content [channel-id channel-num | channel-name channel-name] [correct [channel-id channel-num | channel-name channel-name]] | start-channel {channel-id channel-num | channel-name channel-name} | stop-channel {channel-id channel-num | channel-name channel-name} | test-url url [use-http-proxy url | use-ntlm-domain domain-name | use-smb-options smb-options]}
|
Starts or stops content acquisition on a specified acquirer channel.
|
show acquirer
channels
progress
proxy authentication
|
show acquirer [channels [channel-id channel-num | channel-name channel-name] | progress [channel-id channel-num | channel-name channel-name | streams] | proxy authentication]
|
Displays the acquirer information for the channels specified for which the Content Engine is the root Content Engine.
|
show statistics acquirer
channel-id
channel-name
contents
errors
job-list
|
show statistics acquirer [channel-id channel-num | channel-name channel-name | contents {channel-id channel-num | channel-name channel-name} | errors {channel-id channel-num | channel-name channel-name} | job-list {channel-id channel-num | channel-name channel-name}]
|
Displays acquirer channel statistics for all the channels for which the Content Engine is the root Content Engine.
|
Table 13-3 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.4 publication.
Table 13-3 Distribution-Related Commands
Command
|
Syntax
|
Description
|
show distribution
channels
forwarder-list
location
mcast-data-receiver
mcast-data-sender
object-status
processes
remote
|
show distribution [channels [channel-id channel-num | channel-name name]]
show distribution {forwarder-list [channel-id channel-num [detail] | channel-name name [detail] | detail]}
show distribution location {forwarder-load-weight | live-load-weight | location-loader-preference}[channel-id channel-num | channel-name channel-name]
show distribution mcast-data-receiver
show distribution mcast-data-sender
show distribution object-status object-url
show distribution processes
show distribution remote ip-address {metadata-center channel-id channel-num [start-generation-id gen-id end-generation-id gen-id] | unicast-sender channel-id channel-num {cdn-url | probe | relative-cdn-url} cdn-url}
show distribution remote traceroute {forwarder-next-hop channel-id channel-num {max-hop maxhop_num | trace-till-good | trace-till-root} | unicast-sender channel-id channel-num {cdn-url | probe | relative-cdn-url} cdn-url {max-hop maxhop_num | trace-till-good | trace-till-root}}
|
Displays the distribution information for a specified channel.
|
show statistics distribution
all
errors
mcast-data-receiver
mcast-data-sender
metadata-receiver
metadata-sender
unicast-data-receiver
unicast-data-sender
|
show statistics distribution {all | errors | 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.
|
Configuring the Content Engine Common Internet File System Server
When the Content Engine Common Internet File System (CIFS) server is enabled, Windows clients can request pre-positioned content from the Content Engine by using the Windows file-sharing protocol Server Message Blocks (SMB) or CIFS. The Content Engine CIFS server uses the SMB protocol to serve Windows clients.
You can configure, modify, and view the CIFS server and control access of pre-positioned website content for Content Engines and device groups using the Content Distribution Manager GUI.
Note All Content Engine settings in this section can also be configured for device groups by choosing Devices > Device Groups instead of Devices > Content Engines in the Content Distribution Manager GUI.
Configuring CIFS Server Settings
To configure the CIFS server settings for the Content Engine, follow these steps:
Step 1 Choose Devices > Devices. The Devices window appears.
Step 2 Click the Edit icon next to the Content Engine for which you want to configure CIFS settings. The Content Engine Device Home window appears with the Contents pane on the left.
Step 3 In the Contents pane, choose Applications > File Sharing > CIFS Server Configuration. The CIFS Server Settings for Content Engine window appears. (See Figure 13-4.)
Figure 13-4 CIFS Server Settings Window
Under the CIFS Server Settings panel, the currently applied settings details, such as whether or not default settings have been applied or settings have been derived from the device or device group, are displayed to enable you to identify the source information for the settings. The selected settings will be applied to the CIFS server configurations.
Step 4 To enable the CIFS server on the Content Engine, check the Enable CIFS Server check box, and set the default mode of authentication for file sharing to ce-user.
Step 5 From the Authentication Mode drop-down list, choose the Windows file sharing authentication mode. See Table 13-4 for a description of the options displayed in the list.
Note The login authentication method must be set to local on the Content Engine to use the ce-user mode. By default, the CIFS authentication mode is set to ce-user.
Note CIFS authentication modes ce-user, password-server, and ldap-server do not work well with Windows operating systems. If you have a problem authenticating Windows-based users in these modes, we recommend that you use public or cifs-user authentication mode on the Content Engine.
The domain name and IP address of the NTLM servers that are configured in the NTLM Server Settings for Content Engine window become applicable when the password-server authentication mode is selected.
Table 13-4 Authentication Mode Settings
Authentication Mode
|
Description
|
ce-user
|
Enables the default CIFS authentication mode in ACNS software and allows a user to log in using the user account configured on the Content Engine to access file sharing. This mode is different from the CIFS user mode in earlier releases of ACNS software. You need not maintain two different passwords for the same user account.
|
public
|
Enables any user who is able to access the Content Engine using IP to browse all unprotected pre-positioned content on the cdnfs.
|
password-server
|
Enables NTLM authentication mode, in which the Content Engine relies on the password database stored on an NTLM password server to authenticate users. Password servers are Windows domain controllers. Choosing this option defines the domain or workgroup in which the Content Engine and Windows clients are configured and the server that stores the password database.
|
ldap-server
|
Enables the LDAP server for Windows file sharing authentication.
|
Step 6 In the Max Number of Connections field, enter the maximum number of simultaneous connections for pre-positioned content sharing. The default value is 16 to suit basic browsing requirements. The range is 1 to 65536.
Step 7 To save the settings, click Submit.
A "Click to Submit" message appears in red next to the Current Settings when there are pending changes to be saved after you have applied default or device group settings. You can also revert to the previously configured window settings by clicking Reset. The Reset button is visible only when you apply default or device group settings to change the current device settings but the settings have not yet been submitted.
Configuring CIFS Server Website Access Control Settings
If no website is explicitly configured to be shared, all websites that have been previously defined are shared by default. In other words, all cdnfs content is shared through CIFS file sharing. The maximum number of websites that can be shared is 16.
If you choose the access level as share (see Figure 13-5) and set the authentication mode as public (see Figure 13-4), a warning message displays because all protected content will be accessible to any user who is able to access the Content Engine using IP.
To configure access control for certain pre-positioned websites on the cdnfs, follow these steps:
Step 1 Choose Devices > Devices. The Devices window appears.
Step 2 Click the Edit icon next to the Content Engine for which you want to configure access control. The Content Engine Device Home window appears with the Contents pane on the left.
Step 3 In the Contents pane, choose General Settings > File Sharing > CIFS Server Access Control. The CIFS Server Website Access Control for Content Engine window appears, listing all websites for which access control has been defined.
Note When a device is associated with one or many device groups that have been configured with the settings displayed in this window, if you want to apply the group settings to the device, you can select the device group name from the Select a Device Group drop-down list that appears in the taskbar. A "Click Submit to Save" message appears in red next to the current settings when there are pending changes to be saved after you have applied default and device group settings. You can also revert to the previously configured window settings by clicking Reset. The Reset button is visible only when you apply default or device group settings to change the current device settings when the settings have not yet been submitted.
The currently applied settings details, such as whether or not default settings have been applied or whether or not settings have been derived from the device or device group, display so that you can identify the source information for the settings.
Step 4 If you want all websites that have been created to be shared, check the Share All WebSites check box. All individual websites for which access levels have been specified will be deleted. Click Submit. The system displays a dialog box prompting you to confirm your decision. Click OK to continue.
Step 5 In the taskbar, click the Create New CIFS Website icon. The Creating New CIFS Website for Content Engine window appears. (See Figure 13-5.)
Figure 13-5 Creating New CIFS Website Window
Step 6 From the Website Name drop-down list, choose the websites for which you wish to limit access to pre-positioned cdnfs content. The websites must have been previously defined in the Creating Web Site window.
Step 7 In the Path field, enter the first-level component of the selected websites. This component will be combined with the FQDN of the origin server specified in the Creating Web Site window. The base name of the path or the first-level component of a particular website must be unique. For example, if the path is entered as www.domain.com/subdomain, subdomain refers to the base name of the path and must not be the same for two websites.
Step 8 From the Access Level drop-down list, choose the level of access to be allowed for the websites. Choose share if you wish to share protected cdnfs content. Otherwise, choose protect to deny access to protected cdnfs content.
Step 9 To save the settings, click Submit.
Customizing the CIFS Share Name
ACNS 5.4 software allows you to change the CIFS share name by using the share-name option of the network-filesystem server cifs share-web-site global configuration command.
Note This option first became available in the ACNS 5.3 software release. You cannot use the share-name option in ACNS 5.0, 5.1, and 5.2 software.
The command syntax is as follows:
network-filesystem server cifs share-web-site website [{protect-auth-content | share-auth-content}] [share-name sharename]
The share-name option is shown in the following example:
CE(config)# network-filesystem server cifs share-web-site www.cisco.com share-name cco
Note Share names must be limited to 64 characters or less and may contain only alphanumeric characters. The special characters permitted are "-", "_", and ".".
Working with Content Routers
You can work with Content Routers by performing these tasks:
•Modifying Content Router Properties
•Deleting a Content Router
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:
•Location
•Coverage zone file
•Description
To modify a Content Router, follow these steps:
Step 1 From the Content Distribution Manager GUI, choose Devices > Devices. The Devices window appears, listing all the Content Routers registered in your ACNS network.
Step 2 Click the Edit icon next to the name of the Content Router that you want to modify. The Content Router Device Home window appears.
Step 3 In the Contents pane, choose Device Activation. The Modifying Content Router window appears. (See Figure 13-6.)
Figure 13-6 Modifying Content Router Window
Step 4 If the Content Router is in Inactive status, check the Activate check box. If the Content Router is in Online status, this check box will be checked by default.
Step 5 If you want a Content Router in Active status to be inactivated, click the Deactivate Device icon in the taskbar.
Step 6 To change the location, choose a new location from the Locations drop-down list.
Step 7 To have a local coverage zone file overwrite the ACNS network-wide coverage zone file on this router, you can choose a file from the Coverage Zone File drop-down list. Otherwise, choose None.
The Coverage Zone File drop-down list contains the destination paths of all valid coverage zone files registered to your ACNS network. When you choose a coverage zone file from this list, the Content Router uses this coverage zone file to redirect the user's request. (For information about registering and applying coverage zones, see the "Registering and Applying a User-Defined Coverage Zone" section on page 4-44.)
Step 8 To modify the description used to identify the Content Router, enter a new description in the Comments field.
Step 9 To save your settings, 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 delete the only Content Router in your ACNS network, you are removing the ability of your ACNS network to fill user requests unless you have WCCP or proxy routing configured on your ACNS network.
Removing the node from the ACNS network involves using the CLI to shut down ACNS network services and deregister the node. If you are removing the node because of hardware failure and it cannot be accessed through its CLI, you can remove the node by using the Content Distribution Manager GUI; however, the node continues to store its registration information until you deregister it by using 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(config)# no cms enable
Note Issuing the no cms enable command does not disable acquisition and distribution services on the device; however, issuing the cms deregister command does. The cms deregister command disables the CMS, all acquisition and distribution services, and all routing communications to and from this device.
Step 3 Enter the cms deregister command in EXEC mode.
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.
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 ACNS network, reregister the device with the Content Distribution Manager by using the cms enable command in global configuration mode.
In case of a hardware failure, you might need to remove the node from the ACNS network routing scheme by using the Content Distribution Manager GUI.
Before a node can be removed from the ACNS network 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 Devices in the Content Distribution Manager GUI" section on page 2-21.)
•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 > Devices. The Devices window appears, listing the Content Routers in your ACNS network. The online status of the device is listed in the Status column.
Step 2 Click the Edit icon next to the name of the Content Router that you wish to delete. The Content Router Device Home window appears.
Step 3 In the taskbar, click the Delete Device (Trash) icon. You are prompted to confirm your decision.
Step 4 To execute your request, click OK. 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 In the CLI, 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 ACNS network, reregister the device with the Content Distribution Manager by using the cms enable command in global configuration mode.
Configuring Services on Content Routers
The process of configuring services on Content Routers differs from that of configuring services on Content Engines and device groups in that only platform configuration and authentication services need to be enabled on Content Routers.
The configuration windows for these features are the same windows as those used for Content Engines and device groups. See the following sections and pages for configuration information.
For platform configuration, see the following sections:
•Configuring NTP Settings, page 20-11
•Configuring CDP Settings, page 20-7
For authentication and authorization, see the following sections:
•Configuring Devices for Login Authentication and Authorization, page 12-7
•Configuring Request Authentication on Centrally Managed Content Engines, page 15-14
For more information regarding the use of Content Routers in the ACNS network environment, see Chapter 4, "Setting Up Content Request Routing in the ACNS Network."
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 can work with device groups by performing the following tasks:
•Creating a Device Group
•Deleting a Device Group
•Viewing Device Groups
Creating a Device Group
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 13-7.)
Figure 13-7 Device Groups Window
Step 2 In the taskbar, click the Create New Device Group icon. The Creating New Device Group window appears. (See Figure 13-8.)
Figure 13-8 Creating New Device Group Window
Step 3 In the Name field, enter the name of the device group.
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 To set the device group as the default device group for all newly activated devices, check the Automatically assign all newly activated devices to this group check box.
Step 5 To define a regular device group, click the Regular Group radio button.
(To define a baseline group, see the "Configuring a Baseline Group for a Service" section.)
Step 6 To view configuration information about an existing device group, click the Pages configured for this device group arrow. The window displays a list of GUI pages that are configured for that device group.
Step 7 To customize the Contents pane for the device group, click the Select pages to hide from table of contents for this device group arrow, and check the windows that you want to hide.
Note Use this feature to remove from view any configuration windows that you do not need for that particular device group. Hiding a configured window to keep it from showing in the Contents pane does not affect the settings that are configured already.
Step 8 You may 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 "Assigning Content Engines to the Device Group" section.
Step 9 To save the settings, click Submit.
Step 10 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 11 Change the device group properties as needed, and click Submit.
Assigning Content Engines to the Device Group
Note In ACNS 5.x software, device groups support only Content Engines. Content Routers cannot be assigned to device groups.
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, choose Assignments > Devices. The Content Engine assignment to DG window appears, displaying the Content Engines assigned to various locations.
Step 4 Click the Assign icon (blue cross mark) next to the name of the Content Engine that you wish to add to the device group. Alternatively, to perform a bulk addition of all Content Engines in various locations to the device group, click the Assign all Content Engines icon in the taskbar.
Step 5 To add the Content Engines to the device group, click Submit. Upon submission, a green tick mark appears next to the assigned Content Engine.
Step 6 To remove Content Engines, click the Unassign icon (green tick mark) next to the name of the Content Engine that you want to remove from the device group. Alternatively, you can click the Unassign all Content Engines icon in the taskbar to perform a bulk removal of all Content Engines from the selected device group.
Step 7 To remove the Content Engines from the device group that you are working on, click Submit. The list of Content Engines in the device group shows a blue cross mark that appears next to the name of the removed Content Engine.
Step 8 To display a subset of Content Engines assigned to device groups, click the Filter Table icon in the taskbar. You can choose to filter Content Engines by name, location, and status. After setting the filtering criteria, click Submit.
Step 9 To revert to the display of all Content Engines in the ACNS network, click the View All Content Engines icon in the taskbar.
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 > 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 From the Value drop-down list, choose true. (The default is false.)
You can return to the default at any time by choosing false from the Value drop-down list. 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 do not allow overlapping, and new devices cannot be added to the existing overlapping groups.
Step 4 To save the settings, 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 13-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 In the taskbar, click the Trash icon. You are prompted to confirm your decision to delete the device group.
Step 4 To confirm your decision, click OK. The device group is removed from the ACNS network.
Viewing Device Groups
To view all the device groups in your ACNS network, follow these steps:
Step 1 From the Content Distribution Manager GUI, choose Devices > Device Groups. The Device Groups window appears. (See Figure 13-7.)
Step 2 To refresh the table, click the View All Device Groups icon in the taskbar.
The table also displays device type and comments. You can sort the columns in ascending or descending order by clicking the column heading.
Step 3 To print the table data, click the Printer icon in the taskbar.
Working with Baseline Groups
A baseline group is a special type of device group used for configuring a particular service, such as web, video, or platform. Cisco ACNS software has three predefined baseline groups for your convenience, one for each ACNS service area:
•WebBaselineGroup
•VideoBaselineGroup
•PlatformBaselineGroup
You can use these predefined baseline groups to configure the elements that are necessary for setting up the particular service. When a baseline group is configured for a service, all the devices in the group can be configured for that service and share the same baseline settings. You can associate a baseline group with one or more services. However, a particular service can have only one baseline group associated with it at any given time.
A baseline group is configured in the same way and behaves in the same manner as a device group. You configure the baseline group and then assign Content Engines to the group. Next, you can configure or modify service settings through the baseline service group and apply these settings to all the Content Engines that are associated with the group.
You can also switch the baseline group that is associated with a particular service, if you need to, so that, for example, you can run a particular service on a different subnet of Content Engines in your network and use service settings, such as bandwidth or request filtering, that meet the requirements of that segment of your network.
When you are working with baseline groups, you can perform the following tasks:
•Configuring a Baseline Group for a Service
•Assigning Content Engines to the Baseline Group
•Configuring the Service Settings for the Baseline Group
•Forcing the Baseline Group Service Settings on All Content Engines in the Baseline Group
•Switching the Baseline Group for a Service
•Viewing Configured Service Settings for a Device Group
Configuring a Baseline Group for a Service
Because ACNS software contains three preconfigured baseline groups, before you can configure a new one, you must first delete the existing baseline group. (See the "Deleting a Device Group" section.)
The ACNS 5.4 Content Distribution Manager GUI provides several navigation paths to the baseline group configuration window. You can configure a new baseline group from a service Baseline Settings configuration window in the Services tab or from a Device Groups configuration window in the Devices tab.
To configure a baseline group from a service configuration window, follow these steps:
Step 1 From the Content Distribution Manager GUI, choose Services > Web or Video or Platform > Baseline Settings. The Selecting the (Web, Video, or Platform) Baseline Group window for the chosen service appears.
•If a baseline group is already configured for the service, the Modify Device Group Settings window appears. If you want to delete the baseline group and configure a new one, click the Trash icon in the taskbar.
•If there is no baseline group configured for the service, the Content Distribution Manager displays a message that there is no baseline group configured for that service and provides a drop-down list from which you can choose an existing device group as the baseline group for the service, or you can create a new one.
Step 2 Choose a device group, or choose the Create New Device Group option from the drop-down list, and click Submit.
•If you choose an existing group as baseline group for the service, the Modify Device Group Settings window for the chosen device group opens. From the Modify Device Group Settings window, you can choose to modify the setting options, or leave them alone. If you make changes to any of the settings, click Submit to save the changes.
•If you choose to create a new device group, the Create New Device Group window opens.
Step 3 In the Name field, enter the name of the baseline group.
The name must be unique and should be a name that is useful in distinguishing the baseline group from others on your system. Names with spaces are invalid.
Step 4 To set the baseline group as the default device group for all newly activated devices, check the Automatically assign all newly activated devices to this group check box.
Step 5 To define a baseline group, click the Baseline Group radio button, and choose a service area by checking either the Web, Video, or Platform check box.
Note Once a baseline group has been chosen for a service, that selection is no longer available.
Step 6 To customize the Contents pane for the baseline group, click the Select pages to hide from table of contents for this device group arrow, and check the check boxes for the windows that you want to hide.
Note Use this feature to remove from view any configuration windows that you do not need for that particular device group. Hiding a configured window to keep it from showing in the Contents pane does not affect the settings that are configured already.
Step 7 To give the baseline group a description, enter comments about the group in the Comments field. This field is optional.
Step 8 To save the settings, click Submit.
After you click Submit, the Modify Device Group Settings window appears. The baseline group has been configured. Proceed to the next section, "Assigning Content Engines to the Baseline Group."
Note To configure a baseline group from a Device Groups configuration window, choose Devices > Device Groups. Then click the Create New Device Group icon in the taskbar. The Creating New Device Group window appears. (See Figure 13-8.) Proceed as described in the preceding steps.
Assigning Content Engines to the Baseline Group
Note In ACNS 5.x software, device groups support only Content Engines. Content Routers cannot be assigned to device groups.
To add or remove Content Engines from a baseline 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 baseline group that you want to edit. The Modifying Device Group window appears.
Step 3 In the Contents pane, choose Assignments > Devices. The Content Engine assignment to DG window appears, displaying the Content Engines assigned to various locations.
Step 4 Click the Assign icon (blue cross mark) next to the name of the Content Engine that you wish to add to the baseline group. Alternatively, to perform a bulk addition of all Content Engines in various locations to the baseline group, click the Assign all Content Engines icon in the taskbar.
Step 5 To add the Content Engines to the baseline group, click Submit. Upon submission, a green tick mark appears next to the assigned Content Engine.
Step 6 To remove Content Engines, click the Unassign icon (green tick mark) next to the name of the Content Engine that you want to remove from the baseline group. Alternatively, you can click the Unassign all Content Engines icon in the taskbar to perform a bulk removal of all Content Engines from the selected baseline group.
Step 7 To remove the Content Engines from the baseline group that you are working on, click Submit. The list of Content Engines in the baseline group shows a blue cross mark that appears next to the name of the removed Content Engine.
Step 8 To display a subset of Content Engines assigned to baseline groups, click the Filter Table icon in the taskbar. You can choose to filter Content Engines by name, location, and status. After setting the filtering criteria, click Submit.
Step 9 To revert to the display of all Content Engines in the ACNS network, click the View All Content Engines icon in the taskbar.
You can now configure the service settings for this baseline group. (See the next section, "Configuring the Service Settings for the Baseline Group.")
Configuring the Service Settings for the Baseline Group
To configure service settings, for a baseline group, follow these steps:
Step 1 From the Content Distribution Manager GUI, choose Services > Web or Video or Platform > Baseline Settings. The Modifying Device Group window for the chosen service appears.
Step 2 Alternatively, choose Devices > Device Groups. Click the Edit icon next to the name of the baseline group that is associated with the service that you want to configure. The Modifying Device Group window appears.
Step 3 To view which GUI windows have already been configured for the baseline group, click the Pages configured for this device group arrow button. The GUI displays the list of pages that are configured for that device group. If you are creating a new baseline group or if there are no pages configured for that device group, the GUI displays, Null.
Step 4 If you have not already done so, you can hide any configuration windows in the Contents pane that you do not want to include as part of the baseline group service settings. To customize the Contents pane for the baseline group, click the Select pages to hide from table of contents for this device group arrow, and check the check boxes for the windows that you want to hide.
Step 5 Use the Contents pane to navigate to each configuration window that you want to include as part of the baseline group settings. After a particular setting is configured, the configuration window is listed under Pages configured for this device group in the Modifying Device Group window.
Forcing the Baseline Group Service Settings on All Content Engines in the Baseline Group
Cisco ACNS software allows you to force the complete set of configurations made for a device group to all devices that are associated with that group.
To force the device group configurations across all devices in a device group, follow these steps:
Step 1 From the Content Distribution Manager GUI, choose Devices > Device Groups. The Device Groups listing window appears.
Step 2 Click the Edit icon of the device group that you want to configure.
Step 3 In the taskbar, click the Force Group Settings icon.
The Content Distribution Manager returns the following message:
The action will apply all settings configured for this device group to all the Content
Engines assigned to it. Do you wish to continue?
Step 4 To force group settings across all devices in the device group, click Yes.
Step 5 To save the changes, click Submit.
Switching the Baseline Group for a Service
Cisco ACNS software allows you to switch the baseline group that is associated with a particular service, if you need to, so that, for example, you can run a particular service on a different subnet of Content Engines in your network and use service settings, such as bandwidth or request filtering, that meet the requirements of that segment of your network.
When you switch a baseline group, you must choose a regular device group to take its place. During the switch, the regular device group that you choose is converted to a baseline group, and the baseline group that you remove is converted to a regular device group.
To remove a baseline group from a service and associate another baseline group in its place, follow these steps:
Step 1 Choose Services > Web or Video or Platform > Baseline Settings. The Modify Device Group window for the chosen service appears.
Step 2 From the taskbar, click the Switch Baseline Group icon. The Content Distribution Manager returns the following message:
This action will remove this device group as the Baseline Group for this service. You can
then select another device group or create a new one to the Baseline Group for this
service. Do you wish to Continue?
Step 3 To remove the device group from the service, click OK. The Content Distribution Manager displays the Selecting the Baseline Group window for the chosen service.
Step 4 From the Select a Device Group to be the Baseline Group drop-down list, choose a device group, or choose the Create New Device Group option.
•If you choose a device group to be the baseline group for that service, the Content Distribution Manager takes you to the Modify Device Group window for that device group.
•If you choose the Create New Device Group option, the Content Distribution Manager takes you to the Create New Device Group window.
Viewing Configured Service Settings for a Device Group
To view configuration information about an existing device group, click the Pages configured for this device group arrow. The window displays a list of GUI pages that are configured for that device group.
Local Device Configuration Versus Central Management
Cisco ACNS 5.x software uses certain CLI commands that are particularly important for ACNS network functionality, which is likely to be managed by 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 ACNS network-wide configuration data and are likely to be overwritten by the Content Distribution Manager.
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.
We recommend that you do not configure the following centrally managed settings from the local device GUI or CLI:
authentication
|
logging
|
tacacs
|
bandwidth
|
multicast
|
rule
|
bypass
|
ntlm
|
transaction-logs
|
cdp
|
ntp
|
multicast accept-license-agreement
|
dns-cache
|
proxy-auto-config
|
wmt
excluding:
wmt proxy
wmt
accept-license-agreement
wmt live-url-stripping
|
dns enable
|
proxy-protocols
|
error-handling
|
ldap
|
ftp
|
radius-server
|
http
|
rtsp
excluding:
rtsp server real-subscriber accept-license-agreement
rtsp proxy media-real accept-license-agreement
rtsp-proxy
|
https
|
icpurl-filter
|
ldap
|
|
Repurposing an ACNS Network 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
•CE-566
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 on page 2-18.)
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, as shown in this example:
DeviceName# disk config sysfs 10% cfs 20% mediafs 10% cdnfs 60%
(See the Cisco ACNS Software Update and Maintenance Guide.)
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 ACNS network, 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, as shown in this example:
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# 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, as shown in this 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 Chapter 2, "Getting Started."
