Configuring Content Replication

(config-owner-content[arrowpoint-rule1])# hotlist
 

(config-owner-content[arrowpoint-rule1])# no hotlist
 

• hotlist interval - Set the hotlist refresh interval. Enter the interval time from
  1 to 60 minutes. The default is 1. For example:

(config-owner-content[arrowpoint-rule1])# hotlist interval 10
 

To restore the hotlist interval to the default of 1, enter:

(config-owner-content[arrowpoint-rule1])# no hotlist interval
 

• hotlist size - Set the size of the hotlist. Enter the total number of entries maintained for this rule from 1 to 100. The default is 10. For example:

(config-owner-content[arrowpoint-rule1])# hotlist size 20
 

To restore the hotlist size to the default of 10, enter:

(config-owner-content[arrowpoint-rule1])# no hotlist size
 

• hotlist threshold - Set the hotlist threshold. Enter an integer from 0 to 65535 to specify the threshold above which a piece of content is considered hot. The default is 0. For example:

(config-owner-content[arrowpoint-rule1])# hotlist threshold 9
 

To restore the hotlist threshold default of 0, enter:

(config-owner-content[arrowpoint-rule1])# no hotlist threshold
 

• hotlist type hitCount - Set the hotlist type to hit count, which is how may times the content was accessed.

For example:

(config-owner-content[arrowpoint-rule1])# hotlist type hitcount
 

To restore the hotlist type to the default setting hitCount, enter:

(config-owner-content[arrowpoint-rule1])# no hotlist type

When you specify a service as type rep-cache-redir, the CSS uses the service as a cache server, caching hot content and sending requests to it. Once content is cached on the replication server, the CSS creates a dynamic content rule for the hot content and a dynamic service.

For example:

(config-service[serv1])# max age 10
 

To set the maximum age for replicated objects to its default value of 120, enter:

(config-service[serv1])# no max age

For example:

(config-service[serv1])# max content 50
 

To set the maximum content to its default value of 100, enter:

(config-service[serv1])# no max content

(config-service[serv1])# max usage 100
 

To set the maximum disk space to its default value of 1, enter:

ftp-record ftp_record ip_address or hostname username	["password"|encrypted-password password] base_directory
 

For example:

(config)# ftp-record ftp1 172.16.6.58 bobo "secret" /
 

The variables are:

• ftp_record - The name for this FTP record file. Enter an unquoted text string with no spaces and a maximum length of 32 characters.

• ip_address or hostname - The IP address or host name of the FTP server you want to access.

• username - A valid login username on the FTP server. Enter a case-sensitive unquoted text string with no spaces and a maximum of 32 characters.

• password - The password for the login username on the FTP server. Enter a case-sensitive quoted text string with no spaces and a maximum of
  16 characters.

• encrypted-password encrypted_password - The encrypted password for the valid login username on the FTP server. Enter a case-sensitive unquoted text string with no spaces and a maximum of 16 characters.

• base_directory - An optional base directory when using this record.

To delete an FTP record file from the CSS, use the no ftp-record command and the ftp record name. For example:

(config)# no ftp-record ftp1

When you use this command to associate an FTP access mechanism to a service, the base directory of an existing FTP record becomes the tree root. To maintain coherent mapping between WWW daemons and FTP daemons, make the FTP access base directory equivalent to the WWW daemon root directory as seen by clients.

Enter the access ftp_record as the name of an existing FTP record. Enter the FTP record name as an unquoted text string with no spaces and a maximum length of
16 characters.

Note   To create an FTP record, use the (config) ftp-record command.

For example:

(config-service[serv1])# access ftp myftprecord
 

To remove a service access mechanism, enter:

(config-service[serv1])# no access ftp

• CLI commands.

• Time of day using the Command Scheduler feature.

• Detected changes to specific content on the staging server. The CSS then replicates that content to the subscriber servers or caches dynamically.

The CSS detects changes to specific content by performing an FTP-based examination of file names, sizes, and file dates. The CSS performs this examination based on the configured publisher interval or by the replicate command. The subscriber knows how to interface to the publisher by virtue of the 'access ftp' associated with the publisher designated service.

You can configure the CSS to continually update content that has been replicated. For example, the CSS can replicate content associated with a breaking news story. You can post updates to the staging server and the updates will be replicated to all distributed locations automatically.

Publisher and Subscriber services are usually defined as type local. There is no need to change the service type.

The following sections describe how to configure publisher and subscriber services:

Note   When you configure content staging and replication, you must create the FTP record prior to configuring any other content staging and replication command or the feature will not work properly.

The syntax for this global configuration mode command is:

ftp-record ftp_record ip_address or hostname username	["password"|encrypted-password password] base_directory
 

For example:

(config)# ftp-record ftp1 172.16.6.58 bobo "secret" /
 

The variables are:

• ftp_record - The name for this FTP record file. Enter an unquoted text string with no spaces and a maximum length of 32 characters.

• ip_address or hostname - The IP address or host name of the FTP server you want to access.

• username - A valid login username on the FTP server. Enter a case-sensitive unquoted text string with no spaces and a maximum of 32 characters.

• password - The password for the login username on the FTP server. Enter a case-sensitive quoted text string with no spaces and a maximum of 16 characters.

• encrypted-password encrypted_password - The encrypted password for the valid login username on the FTP server. Enter a case-sensitive unquoted text string with no spaces and a maximum of 16 characters.

• base_directory - An optional base directory when using this record.

To delete an FTP record file from the CSS, enter:

(config)# no ftp-record ftp1

Enter the FTP record as the name of an existing FTP record. Enter the FTP record name as an unquoted text string with no spaces and a maximum length of 16 characters.

Note   To create an FTP record, use the (config) ftp-record command.

The syntax for this service mode command is:

(config-service[pubserver])# access ftp myftprecord
 

To remove a service access mechanism, enter:

(config-service[pubserver])# no access ftp

A publishing service synchronizes content among associated subscriber services.
To move the content during publishing activities, you must configure an access mechanism for the publisher service. Use the (config-service) access ftp
command defined earlier in this chapter to configure a mechanism for the
publisher service.

When you define the interval to synchronize the subscriber, the interval begins at the time you issue the command. Subscribers that are unavailable for synchronization are placed in an offline state and retried until the operation is completed.

Note   The publisher service does not become active until it has at least one configured subscriber. You do not need to configure the publisher before configuring the subscriber, but the publisher must be configured before the subscriber can receive any content synchronization updates.

The syntax and options for this service mode command are:

• publisher - Configure the service as a publishing service.

• publisher interval minutes - Define a recurrent interval in minutes to synchronize content among the subscribers. You can only issue this command after you configure this service as a publishing service. Enter the synchronization interval in minutes. Enter the number from 0 to 3600. The default is 0 which disables the interval.

• publisher interval minutes trigger_filename - Define a recurrent interval in minutes to synchronize content among the subscribers only when the specified trigger file is modified. Specify the trigger_filename from 1 to 64 characters in length. You can only issue this command after you configure the service as a publishing service.

To configure publishing on a service, enter:

(config-service[pubserver])# publisher
 

To remove publishing on a service, enter:

(config-service[pubserver])# no publisher
 

To configure a publisher resynchronization interval, enter:

(config-service[pubserver])# publisher interval 120
 

To disable the publisher resynchronization interval by setting it to its default of 0, enter:

(config-service[pubserver])# no publisher interval

• Use an URL to specify files.

• Use an URQL to define a static list of files.

Then add the subscriber services to the content rule.

Note   If you want all files in all directories replicated, you do not need to create a content rule. Create a content rule to specify only those files you want replicated.

For example, to specify a URL that matches all requests for content in the announcements directory with .html extensions, enter:

(config-owner-content[arrowpoint-products.html])# url "/announcements/*.html"
 

For a complete description on configuring URLs, refer to the Content Services Switch Basic Configuration Guide.

Enter the publisher_name as the name of the existing publisher. Enter the subscriber_name as the name of the subscriber associated with the publisher service.

The syntax and options are:

• replicate publisher_name - Resynchronize any changes to content between the specified publisher and its subscriber services. If the content has not changed, no resynchronization occurs.

• replicate publisher_name subscriber_name - Resynchronize any changes to content between the specified publisher and the specified subscriber service. If the content has not changed, no resynchronization occurs.

• replicate publisher_name subscriber_name force - Resynchronize all content between the specified publisher and the specified subscriber service whether or not content changes have occurred.

For example: