Cisco Internet Streamer CDS 2.5 Software Configuration Guide
Configuring the System
Downloads: This chapterpdf (PDF - 237.0KB) The complete bookPDF (PDF - 4.65MB) | Feedback

Configuring the System

Table Of Contents

Configuring the System

Configuring AAA

Creating, Editing, and Deleting Users

Creating, Editing, and Deleting Roles

Creating, Editing, and Deleting Domains

Changing a Password

Configuring System Settings

System Properties

Configuring Fast SE Offline Detection

Configuring Distribution QoS

Configuring Service Routing

Coverage Zone File Registration

Configuring Global Routing

CDN Selector File Registration

Service Rule File Registration


Configuring the System


This chapter provides information on configuring the system parameters of the CDS. This chapter has the following major topics:

Configuring AAA

Changing a Password

Configuring System Settings

For information on logs, see the "System Audit Logs" section. For information on upgrading the CDS software, see the "Software Upgrade" section. For information on the ports used by the CDS, see the "System Port Numbers" section.

Configuring AAA

Authentication determines who the user is and whether that user should be allowed access to the network or a particular device. It allows network administrators to bar intruders from their networks. It may use a simple database of users and passwords. It can also use one-time passwords.

Authorization determines what the user is allowed to do. It allows network managers to limit which network services are available to different users.

Accounting tracks what users did and when they did it. It can be used for an audit trail or for billing for connection time or resources used (bytes transferred).

Collectively, authentication, authorization, and accounting are sometimes referred to as AAA. Central management of AAA means the information is in a single, centralized, secure database, which is much easier to administer than information distributed across numerous devices.

In the CDS network, login authentication and authorization are used to control user access and configuration rights to the CDSM, SEs, and SRs. There are two levels of login authentication and authorization:

Device

CDSM

In a CDS network, user accounts can be created for access to the CDSM and, independently, for access to the SEs and SRs that are registered to the CDSM.

This section covers login authentication and authorization for the CDSM. For information about device login authentication and authorization, see the "Login Access Control" section and the "Authentication" section.

Login authentication is the process by which CDSM verifies whether the person who is attempting to log in has a valid username and password. The person logging in must have a user account registered with the device. User account information serves to authorize the user for login and configuration privileges. The user account information is stored in the AAA database. When the user attempts to log in, the CDSM compares the person's username, password, and privilege level to the user account information that is stored in the database.

Each user account can be assigned to a role and a domain. A role defines which CDSM configuration pages the user can access and which services the user has authority to configure or modify. A domain defines which entities in the network the user can access and configure or modify. You can assign a user account to zero or more roles, and to zero or more domains.

Creating, Editing, and Deleting Users


Note This section is addressed to users with administrator-level privileges (admin users) only.


Two default user accounts are preconfigured in the CDSM. The first account, called admin, is assigned the administrator role that allows access to all services and access to all entities in the system. This account cannot be deleted from the system, but it can be modified. Only the username and the role for this account are unchangeable. To change the password for this account, use the username admin password <password> command through the CLI.

The second preconfigured user account is called default. Any user account that is authenticated but has not been registered in the CDSM gets the access rights (role and domains) assigned to the default account. This account is configurable, but it cannot be deleted nor can its username be changed.

When you create a new user account in the CDSM, you have the option to create the user account in the CLI for the CDSM device at the same time. Using this option to create the new account in the CLI provides the following benefits:

User account is created in the primary and standby CDSM management databases and in the CDSM CLI from one central point.

Users can change their passwords, and the password changes are propagated to a standby CDSM.

If you choose to create the user account from the CDSM without creating the user account in the CDSM CLI at the same time, the following results apply:

User account is created in the primary and standby CDSM management databases.

No user account is created in the CDSM CLI, and the user cannot log in to the CDSM until an account is created from the CLI.

Local users cannot change their passwords using the CDSM.

Local users can change their passwords using the CLI; however, the password changes are not propagated from the CLI to the CDSM databases when the CLI user option is enabled in the CDSM.

If a user account has been created from the CLI only, when you log in to the CDSM for the first time, the Centralized Management System (CMS) database automatically creates a user account (with the same username as configured in the CLI) with default authorization and access control. However, to change the password in this scenario, the user account must be explicitly configured from the CDSM with the CLI user option enabled.

To create or edit a user account, do the following:


Step 1 Choose System > AAA > Users. The User Table page is displayed.

Table 6-1 describes the icons for the User Table page.

Table 6-1 User Table Icons 

Icon
Function

Creates a new entry.

Edits an entry.

Creates a filtered table. Filter the table based on the field values.

Views all table entries. Click this icon to view all entries after you have created a filtered table.

Refreshes the table.

Prints the current window.


Step 2 Click the Create New icon in the task bar. The User Account page is displayed.

To edit an account, click the Edit icon next to the username.


Note The User Account page can only be accessed by users with administrator-level privileges.


Step 3 In the Username field, enter the user account name. The username must be between 4 and 32 characters in length, and begin with a letter.

Step 4 If you want to create a local user account with a password and privilege level from the CDSM, check the Create CLI User check box. The user account is created automatically in the CLI. To prevent the creation of a CLI user account from the GUI, leave the check box unchecked.

Step 5 In the Password field, enter a password for the CLI user account, and re-enter the same password in the Confirm Password field.

The password strength must be a combination of alphabetic character, at least one number, at least one special character, and at least one uppercase character.

The following characters are not allowed: ?./;[]{}"@=|

Step 6 From the Privilege Level drop-down list, choose a privilege level for the CLI user account. The choices are 0 (zero) (normal user) or 15 (superuser). The default value is 0.


Note A superuser can use privileged-level EXEC commands, whereas a normal user can use only user-level EXEC commands.


Step 7 In the Username Information area, enter the following information about the user: First Name, Last Name, Phone Number, Email Address, Job Title, and Department.

Step 8 In the Comments field, enter any additional information about this account.

Step 9 Click Submit to save the settings.

Step 10 From the left-panel menu, click Role Management. The Role Management Table page is displayed.

Table 6-1 describes the icons for the Role Management page.

Table 6-2 Role Management Icons 

Icon
Function

Creates a new entry.

Edits an entry.

Creates a filtered table. Filter the table based on the field values.

Views all table entries. Click this icon to view all entries after you have created a filtered table.

Refreshes the table.

Assigns all roles.

Removes all roles.

Views read-only items.

Indicates that the current transaction was successfully completed.


To add roles, see the "Creating, Editing, and Deleting Roles" section.

To view the setting for the role, click the View (eyeglasses) icon next to the role.

Step 11 Click the Assign icon (blue cross mark) next to each role name you want to assign to the user account. To remove the role from the user account, click the Assign icon again.

To assign all roles, click the Assign all Roles icon in the task bar. To unassign all roles, click the Remove all Roles icon in the task bar.

Step 12 Click Submit to save the settings.

A green arrow wrapped around the blue cross mark indicates an SE assignment is ready to be submitted. To unassign an SE, click this icon.

Step 13 From the left-panel menu, click Domain Management. The Domain Management Table page is displayed.

To add domains, see the "Creating, Editing, and Deleting Domains" section.

To view the setting for the domain, click the View (eyeglasses) icon next to the domain.

Step 14 Click the Assign icon next to each domain name you want to assign to the user account.

To remove the domain from the user account, click the Assign icon again.

To assign all domains, click the Assign All icon in the task bar. To unassign all domains, click the Remove All icon in the task bar.

Step 15 Click Submit to save the settings.


To delete a user, in the User Table page, click the Edit icon next to the username, and from the User Account page, click the Delete icon in the task bar.


Note Deleting a user account from the CLI does not delete the corresponding account in the CDSM database. User accounts created in the CDSM should always be deleted from within the CDSM.


Creating, Editing, and Deleting Roles

Although the CDSM provides many types of services, not all users have access to all services. Users are assigned a role, which indicates the services to which they have access. A role is a set of enabled services.

Each user account can be assigned zero or more roles. Roles are not inherited or embedded. The CDSM provides one predefined role, known as the admin role. The admin role has access to all services and all CDS network entities.


Note The admin user account, by default, is assigned to the role that allows access to all domains and all entities in the system. It is not possible to change the role for this user account.


To create or edit a role, do the following:


Step 1 Choose System > AAA > Roles. The Roles Table page is displayed.

Step 2 Click the Create New icon in the task bar. The Role page is displayed.

To edit a role, click the Edit icon next to the role name.

Step 3 In the Name field, enter the name of the role.

Step 4 To enable read-only access for this role, check the Read-Only check box. Users assigned to this role are only be able to view the CDSM pages. They are not able to make any changes.

Step 5 To expand a listing of services under a category, click the folder, and then check the check box next to the service or services you want to enable for this role. To choose all the services under one category simultaneously, check the check box for the top-level folder.

Step 6 In the Comments field, enter any comments about this role.

Step 7 Click Submit to save the settings.


To delete a role, in the Roles Table page, click the Edit icon next to the role name. Once the Role page is displayed, click the Delete icon in the task bar.

Creating, Editing, and Deleting Domains

A domain is a set of CDS network entities or objects that make up the CDS network. Whereas a role defines which services a user can perform in the CDS network, a domain defines the entities to which the user has access. An entity can be a Service Engine, a device group, or a delivery service. These predefined entities are treated like services and can be enabled or disabled when you set up user roles.

When you configure a domain, you can choose to include Service Engines, device groups, or delivery services in the domain.

To create or edit a domain, do the following:


Step 1 Choose System > AAA > Domains. The Domains Table page is displayed.

Step 2 Click the Create New icon in the task bar. The Domain page is displayed.

To edit a domain, click the Edit icon next to the domain name.

Step 3 In the Name field, enter the name of the domain.

Step 4 From the Entity Type drop-down list, choose Service Engines, Device Groups, or Delivery Services.

Step 5 In the Comments field, enter any comments about this domain.

Step 6 Click Submit to save the settings. If the entity type you chose has not already been assigned to the domain, then a message displays indicating that the entity type has not been assigned.

Step 7 From the left-panel menu, click Entity Management. The Entity Management page is displayed.

Step 8 Click the Assign icon (blue cross mark) next to each entity name you want to include. A green arrow wrapped around the blue cross mark indicates an entity is assigned.

To assign all entities in the domain, click the Assign All icon in the task bar.

To remove an entity from the domain, click the Assign icon again.

To remove all entities from the domain, click the Remove All icon in the task bar.

Step 9 Click Submit to save the settings.


To delete a domain, in the Domain Table page click the Edit icon next to the domain name. Once the Domain page is displayed, click the Delete icon in the task bar.

Creating a Domain Example

Following is an example of the tasks need to create a domain for a non-administrator user to be able to see a playlist view and have rights access to the SE, delivery service, and device group assigned to the playlist:

1. Choose System > AAA > Domains, create a domain for entity type Delivery Services. Make sure the delivery service the playlist uses is assigned to this domain.

2. Choose System > AAA > Domains, create a domain for entity type Service Engine.Make sure the SE the playlist uses is assigned to this domain.

3. Choose System > AAA > Domains, create a domain for entity type Device Group. Make sure the Device Group the playlist uses is assigned to this domain.

Choose System > Users, select a user and assign the domains just configured to this user.

The non-administrator user should see the playlist.

Changing a Password

If you are a user without admin privileges and you are logged in to the CDSM, you can change your own CDSM and CLI user password if you meet the following requirements:

Your CLI user account and password were created in the CDSM and not in the CLI.

You are authorized to access the Password page.


Caution We do not recommend changing the CLI user password from the CLI. Any changes to CLI user passwords from the CLI are not updated in the management database and are not propagated to the standby CDSM. Therefore, passwords in the management database do not match a new password configured in the CLI.
The advantage of initially setting passwords from the CDSM is that both the primary and the standby CDSMs are synchronized, and CDSM users do not have to access the CLI to change their passwords.

To change the CDSM and CLI user password for the user account that is currently logged in to the CDSM, do the following:


Step 1 Choose System > Password. The Password page is displayed.

Step 2 In the New Password field, enter the changed password.

The following characters are not allowed: ?./;[]{}"@=|

Step 3 In the Confirm New Password field, re-enter the password for confirmation.

Step 4 Click Submit to save the settings.


Configuring System Settings

This section covers the following topics:

System Properties

Configuring Fast SE Offline Detection

Configuring Distribution QoS

Configuring Service Routing

CDN Selector File Registration

System Properties

To modify the system properties, do the following:


Step 1 Choose System > Configuration > System Properties. The System Properties page is displayed.

Step 2 Click the Edit icon next to the system property you want to change. The Modify Config Property page is displayed.

Step 3 For true or false values, choose a setting from the Value drop-down list. For other values, enter a new value. The range is displayed for each numeric value.

Table 6-3 describes the system properties.

Table 6-3 System Properties Fields 

Field
Description

cdsm.session.timeout

Length of a Content Distribution Manager session (in minutes). The default is 10. The range is from 5 to 120.

DeviceGroup.overlap

SE feature overlapping (enable or disable).

System.CmsUnsProgram
Sync.Interval

Interval by which CMS synchronizes program import UNS objects (in minutes). The default is 1440 minutes. The range is from 1 to 43200.

System.datafeed.pollRate

Poll rate between the SE or the SR and the CDSM (in seconds). The default is 300. The range is from 30 to 1800.

System.device.recovery.key

Device identity recovery key. This property enables a device to be replaced by another node in the CDS network.

System.healthmonitor.collect
Rate

Sets the collect and send rate in seconds for the CMS device health (or status) monitor. The default is 120. The range is from 5 to 3600.

System.Icm.enable

Local and CDSM feature (enable or disable). This property allows settings that are configured using the local device CLI or the CDSM to be stored as part of the CDS network configuration data.

System.monitoring.collect
Rate

Rate at which the SE collects and sends the monitoring report to the CDSM (in seconds). The default is 300 seconds. The range is from 30 to 1800.

System.monitoring.daily
ConsolidationHour

Hour at which the CDSM consolidates hourly and daily monitoring records. The default is 1. The range is from 0 to 23.

System.monitoring.enable

SE statistics monitoring (enable or disable).

System.monitoring.monthly
ConsolidationFrequency

Frequency (in days) with which the CDSM consolidates daily monitoring records into monthly records. The default is 14. The range is from 1 to 30.

System.monitoring.record
LimitDays

Maximum number of days of monitoring data to maintain in the system. The default is 1825. The range is from 0 to 7300.

System.repstatus.update
Enabled

Replication status periodic calculations on an SE (enable or disable).

System.repstatus.updateRate

Rate of replication status periodic updates calculated on an SE (in minutes). The default is 10. The range is from 5 to 1440.

System.repstatus.updateRate
Sec

Rate of replication status periodic updates calculated on an SE (in seconds). The default is 600 seconds. Setting this rate overrides the update rate set in minutes. The ranges is from 30 to 86400.

Note The rep_status_failed alarm gets triggered if the replication misses three times in a row. You can configure a lower value for the System.repstatus.updateRateSec to have the alarm trigger sooner.

System.repstatus.updateSync
Enabled

Sending summary replication status with requested detailed status (enable or disable).

System.security.minPasswordLength

Minimum number of characters required for a user password. The default is 6. The range is from 6 to 31.

System.security.minUser
NameLength

Minimum number of characters required for a user name. The default is 4. The range is from 1 to 32.


Step 4 Click Submit to save the settings.


Configuring Fast SE Offline Detection

You can detect offline SEs more quickly if you enable the Fast Detection of Offline SEs feature.

If Fast Detection of Offline SEs is not enabled, the CDSM waits for at least two "System.datafeed.pollRate" polling periods before declaring the SE offline.

If Fast Detection of Offline SEs is enabled, the CDSM waits until the value displayed in the Maximum Offline Detection Time field, located on the Configure Fast SE Offline Detection page, is exceeded.

Communication between the SE and CDSM using User Datagram Protocol (UDP) allows faster detection of SEs that have gone offline. UDP heartbeat packets are sent at a specified interval from each SE to the primary CDSM in a CDS network. The primary CDSM tracks the last time it received a UDP heartbeat packet from each SE. If the CDSM has not received the specified number of UDP packets, it displays the status of the nonresponsive SEs as offline. Because UDP heartbeats require less processing than a getUpdate request, they can be transmitted more frequently, and the CDSM can detect offline SEs much faster.

An SE is declared offline when it has failed to contact the CDSM for a getUpdate request (get configuration poll) for at least two polling periods.


Note In CDS networks with heavy traffic, dropped UDP packets can cause the CDSM to incorrectly report the status of SEs as offline. To avoid this problem, configure a higher value for dropped UDP heartbeat packets.


To configure Fast Detection of Offline SEs, do the following:


Step 1 Choose System > Configuration > Fast SE Offline Detection. The Configure Fast SE Offline Detection page is displayed.


Note The Fast Detection of Offline SEs feature is in effect only when the CDSM receives the first UDP heartbeat packet and a getUpdate request from an SE.


Step 2 Check the Enable check box to enable the CDSM to detect the offline status of SEs quickly.


Note SEs can have their software upgraded without any errors in the status being displayed in the CDSM if you disable Fast Detection of Offline SEs.


Step 3 In the Heartbeat Rate field, specify how often, in seconds, the SEs should transmit a UDP heartbeat packet to the CDSM. The default is 30. The range is from 30 to 3600.

Step 4 In the Heartbeat Fail Count field, specify the number of UDP heartbeat packets that can be dropped during transmission from SEs to the CDSM before an SE is declared offline. The default is 1. The range is from 1 to 100.

Step 5 In the Heartbeat UDP Port field, specify the CDSM port number that the SEs use to send UDP heartbeat packets. The default is 2000. The range is from 1000 to 10000.

The Maximum Offline Detection Time field displays the product of the failed heartbeat count and heartbeat rate, where:

Maximum Offline Detection Time = Failed heartbeat count * Heartbeat rate

If Fast Detection of Offline SEs is enabled, the CDSM detects SEs that are in network segments that do not support UDP and uses a getUpdate request (get configuration poll) to detect offline SEs.

If the CDSM does not receive regular keep-alive communication from an SE, the CDSM displays the SE as offline after a time period of 2 * (Heartbeat rate) * (Failed heartbeat count).

Step 6 Click Submit to save the settings.


Configuring Distribution QoS

The Distribution QoS settings allow you to configure system-wide QoS priorities for delivery service distribution and metadata replication. The delivery service distribution priority (low, medium, or high) is set on the definition page for each delivery service.


Note When a single URL is associated with more than one delivery service, the content is distributed only one time to all the Service Engines subscribed to each delivery service. When different QoS settings are configured for different delivery services that contain the same content, the delivery service priority setting determines which QoS settings are applied to the content distribution. The delivery service with the higher priority dictates which QoS settings are used.


To configure system-wide QoS settings, do the following:


Step 1 Choose System > Configuration > Distribution QoS. The Distribution QoS page is displayed.

Step 2 Check the Set QoS for Unicast Data check box to enable system-wide QoS settings for unicast data.

The unicast data refers to the ingest and distribution traffic among SEs.

Step 3 To set the QoS value for a delivery service with low priority, choose a Differentiated Service Code Point (SCDP) value from the QoS value with low priority drop-down list. Alternatively, enter a decimal value in the corresponding field.


Note See the next section, "Setting DSCP Values for QoS Packets,"for more information. You can override the system-wide settings for unicast data by configuring QoS settings on a per-delivery service basis. Sse the "Creating Delivery Service" section for more information.


Step 4 To set the QoS value for a delivery service with medium priority, choose a DSCP value from the QoS value with medium priority drop-down list. Alternatively, enter a decimal value in the corresponding field.

Step 5 To set the QoS value for a delivery service with high priority, choose a DSCP value from the QoS value with high priority drop-down list. Alternatively, enter a decimal value in the corresponding field.

Step 6 Set the QoS value for each priority (low, medium, and high) for a delivery service by choosing the Differentiated Service Code Point (DSCP) value from the QoS value drop-down list or by entering a decimal value in the corresponding field.

Step 7 Check the Set QoS for metadata check box to enable QoS settings for metadata replication.

Metadata is created based on the Manifest file and is part of the ingest and distribution traffic.

Step 8 Set the QoS value for metadata replication by choosing the DSCP value from the QoS value drop-down list or by entering a decimal value in the corresponding field.

Step 9 Click Submit to save the settings.


Setting DSCP Values for QoS Packets

The CDS allows you to set Differentiated Services Code Point (DSCP) values for Unicast QoS packets. DSCP values define relative priority levels for the packets. You can either choose a DSCP keyword from the drop-down list or enter a value in the corresponding field. (See Table 6-4.)

Table 6-4 DSCP Values 

Keyword
Description and Value

af11

Sets packets with AF11 DSCP (001010).

Note The number in parentheses denotes the DSCP value for each per-hop behavior keyword.

af12

Sets packets with AF12 DSCP (001100).

af13

Sets packets with AF13 DSCP (001110).

af21

Sets packets with AF21 DSCP (010010).

af22

Sets packets with AF22 DSCP (010100).

af23

Sets packets with AF23 DSCP (010110).

af31

Sets packets with AF31 DSCP (011010).

af32

Sets packets with AF32 DSCP (011100).

af33

Sets packets with AF33 DSCP (011110).

af41

Sets packets with AF41 DSCP (100010).

af42

Sets packets with AF42 DSCP (100100).

af43

Sets packets with AF43 DSCP (100110).

cs1

Sets packets with CS1 (precedence 1) DSCP (001000).

cs2

Sets packets with CS2 (precedence 2) DSCP (010000).

cs3

Sets packets with CS3 (precedence 3) DSCP (011000).

cs4

Sets packets with CS4 (precedence 4) DSCP (100000).

cs5

Sets packets with CS5 (precedence 5) DSCP (101000).

cs6

Sets packets with CS6 (precedence 6) DSCP (110000).

cs7

Sets packets with CS7 (precedence 7) DSCP (111000).

default

Sets packets with the default DSCP (000000).

ef

Sets packets with EF DSCP (101110).


Configuring Service Routing

The Service Routing menu options consist of the following:

Coverage Zone File Registration

Configuring Global Routing

Coverage Zone File Registration

A coverage zone can be associated with one or more SEs: each SE can have its own unique coverage zone, or SEs can be associated with more than one coverage zone and have overlapping coverage zones. For more information about coverage zones, see the "Coverage Zone File" section.

See "Creating Coverage Zone Files," for information about creating a Coverage Zone file.

The system administrator places a Coverage Zone file where the CDSM or individual devices can access the URL. The administrator then registers the Coverage Zone file URL in the CDSM. Coverage Zone files can be applied globally to the entire CDS network, or locally to a specific SR. If a Coverage Zone file is made global, then it is read and parsed by each SR that does not have a Coverage Zone file assigned. If the coverage zone is specified in an individual SR configuration, it is only applied to that particular SR.

You have the choice of using two types of coverage zones:

Default coverage zones

User-defined coverage zones

A default coverage zone consists of all the SEs that reside in the same local network segment, or subnet. The CDSM provides a check box to specify whether the default coverage zone is to be used.

A user-defined coverage zone consists of all the SEs that are specified in a Coverage Zone file. This file defines the network segments to be covered in the routing process. The Coverage Zone file is registered with the CDSM and then applied to an SR for routing definitions.

To apply a custom coverage zone to an SR, you first need to register a Coverage Zone file URL in the CDSM. After you have registered the Coverage Zone file URL with the CDSM, you can apply the Coverage Zone file in one of two ways:

Globally—Deploy the Coverage Zone file across the entire CDS network

Locally—Deploy the Coverage Zone file on a specific SR


Note If you apply a Coverage Zone file locally for a device, this file overwrites the global Coverage Zone file for that device.


To register a Coverage Zone file, do the following:


Step 1 Choose System > Configuration > Service Routing > Coverage Zone File Registration. The Coverage Zone File Table page is displayed.

Step 2 Click the Create New icon in the task bar. The Registering Coverage Zone File page is displayed.

To edit a Coverage Zone file registration, click the Edit icon next to the registration you want to edit.

Step 3 Choose a file import method from the File Import Method drop-down list:

Upload—The upload method allows you to upload a Coverage Zone file from any location that is accessible from your PC by using the browse feature.

Import—The import method allows you to import the Coverage Zone file from an external HTTP, HTTPS, FTP, or CIFS server.

When you choose a method, the page refreshes and displays the configuration fields that are associated with the method that you chose.

Step 4 Enter the fields as appropriate. Table 6-5 describes the upload method fields. Table 6-6 describes the import method fields.

Table 6-5 Upload Method for Coverage Zone Files 

Property
Description

Coverage Zone File Upload

Local directory path to the Coverage Zone file. To locate the file, use the Browse button. Click the Validate button to validate the Coverage Zone file.

Destination Filename

Name of the Coverage Zone file. This field is filled in automatically with the filename from the local directory path.


Table 6-6 Import Method for Coverage Zone Files

Property
Description

Coverage Zone File URL

The URL where the Coverage Zone file is located, including path and filename. Click the Validate button to validate the Coverage Zone file.

Destination File Name

Name of the Coverage Zone file.

Update Interval (minutes)

Frequency with which the CDSM looks for changes to the Coverage Zone file. The default value is 10 minutes.

Username

Name of the user to be authenticated when fetching the Coverage Zone file.

Password

User password for fetching the Coverage Zone file.

NTLM user Domain

NT LAN Manager (NTLM) user domain name for NTLM authentication.

Disable Basic Authentication

When checked, NTLM headers cannot be stripped off to allow fallback to the basic authentication method.

If you leave this check box unchecked, NTLM authentication headers can be stripped to allow fallback to the basic authentication method, and the username and password information can be passed to the origin server in clear text with a basic authentication header.


Step 5 To save the settings, click Submit.


Configuring Global Routing

After you have registered the Coverage Zone file, you can use this file as your global routing configuration.

To set a global Coverage Zone file, do the following:


Step 1 Choose System > Configuration > Service Routing > Global Routing Config. The Set Global Coverage Zone File page is displayed.

Step 2 From the Coverage Zone File drop-down list, choose a Coverage Zone file.

Step 3 In the DNS TTL field, configure the time period (in seconds) for caching DNS replies. Enter a number from 0 to 60. The default is 60 seconds.

Step 4 Click Submit to save settings.


To apply a Coverage Zone file to an individual SR for local coverage zone configuration, see the "Configuring the Service Router" section.

CDN Selector File Registration

A CDN Selector file is associated with one or more SRs. Each SR can have its own unique CDN Selector file or multiple SRs can have the same CDN Selector file.

CDN Selector must be enabled on the SR and a CDN Selector file must be selected for the SR. For more information about enabling CDN Selector, see the "Activating a Service Router" section. For more information about creating a CDN Selector file, see "Creating CDN Selector Files." To select a CDN Selector file for the SR, you first need to register the CDN Selector file in the CDSM.


Note CDN Selector is an early field trial (EFT) feature for Release 2.5.7 and later releases.


To register a CDN Selector file, do the following:


Step 1 Choose System > Configuration > CDN Selector File Registration. The CDN Selector File Table page is displayed.

Step 2 Click the Create New icon in the task bar. The Registering CDN Selector File page is displayed.

To edit a CDN Selector file registration, click the Edit icon next to the registration you want to edit.

Step 3 Choose a file import method from the File Import Method drop-down list:

Upload—The upload method allows you to upload a CDN Selector file from any location that is accessible from your PC by using the browse feature.

Import—The import method allows you to import the CDN Selector file from an external HTTP, HTTPS, FTP, or CIFS server.

When you choose a method, the page refreshes and displays the configuration fields that are associated with the method that you chose.

Step 4 Enter the fields as appropriate. Table 6-5 describes the upload method fields. Table 6-6 describes the import method fields.

Table 6-7 Upload Method for CDN Selector Files 

Property
Description

CDN Selector File Upload

Local directory path to the CDN Selector file. To locate the file, use the Browse button. Click the Validate button to validate the CDN Selector file.

Destination Filename

Name of the CDN Selector file. This field is filled in automatically with the filename from the local directory path.


Table 6-8 Import Method for CDN Selector Files

Property
Description

CDN Selector File URL

The URL where the CDN Selector file is located, including path and filename. Click the Validate button to validate the CDN Selector file.

Destination File Name

Name of the CDN Selector file.

Update Interval (minutes)

Frequency with which the CDSM looks for changes to the CDN Selector file. The default value is 10 minutes.

Username

Name of the user to be authenticated when fetching the CDN Selector file.

Password

User password for fetching the CDN Selector file.

NTLM user Domain

NT LAN Manager (NTLM) user domain name for NTLM authentication.

Disable Basic Authentication

When checked, NTLM headers cannot be stripped off to allow fallback to the basic authentication method.

If you leave this check box unchecked, NTLM authentication headers can be stripped to allow fallback to the basic authentication method, and the username and password information can be passed to the origin server in clear text with a basic authentication header.


Step 5 To save the settings, click Submit.


Service Rule File Registration

A Service Rule file is associated with one or more delivery services. Each delivery service can have its own unique Service Rule file or multiple delivery services can have the same Service Rule file.

A Service Rule must be selected for a delivery service. For more information about Service Rule configuration, see "Creating Service Rule Files." To select a Service Rule file for a delivery service, you first need to register the Service Rule file in the CDSM.

To register a Service Rule file, do the following:


Step 1 Choose System > Configuration > Service Rule File Registration. The Service Rule File Table page is displayed.

Step 2 Click the Create New icon in the task bar. The Registering Service Rule File page is displayed.

To edit a Service Rule file registration, click the Edit icon next to the registration you want to edit.

Step 3 From the File Import Method drop-down list, choose Upload.

The upload method allows you to upload a Service Rule file from any location that is accessible from your PC by using the browse feature.

When you choose a method, the page refreshes and displays the configuration fields that are associated with the method that you chose.

Step 4 Enter the fields as appropriate. Table 6-5 describes the upload method fields.

Table 6-9 Upload Method for Service Rule Files 

Property
Description

Service Rule File Upload

Local directory path to the Service Rule file. To locate the file, use the Browse button. Click the Validate button to validate the Service Rule file.

Destination Filename

Name of the Service Rule file. This field is filled in automatically with the filename from the local directory path.


Step 5 To save the settings, click Submit.