Chapter 19 Content Distribution and Delivery

Reference

Table 19-5

Elements to Configure DMS-CD Deployment Thresholds

 

 

 

Element

 

Description

 

 

 

Number of

 

The maximum allowed number of FTP or SFTP threads, or sessions, that can run concurrently when

concurrent

 

DMS-CD provisions assets to DMPs.1 Therefore, the maximum number of DMS-CD deployments that

deployments

 

might possibly run concurrently in your WAN, if each such deployment targets only one DMP. Otherwise,

 

 

when any deployments target multiple DMPs, this constraint limits how many DMPs can possibly receive

 

 

deployments concurrently in your WAN.2

 

 

Tip

When you use DMS-CD, it is a best practice that none of your DMP groups should contain more than this

 

 

 

number of DMPs. If you ever reduce this value, check that doing so has not caused any of your DMP groups to contain

 

 

 

more DMPs than the new number.

 

 

The permitted value is any whole number in the range from 1 to 1000. The factory-default value is

 

 

100 threads. We recommend that you avoid using any value greater than 100. Each incrementally higher

 

 

value authorizes more concurrent DMS-CD deployments to DMPs and an increased load on your DMM

 

 

appliance. You might try reducing this value if you notice that the CPU load is high on your DMM

 

 

appliance during DMS-CD deployments.

 

 

Note

Any time that you change this value, you must restart your DMM appliance before the changed setting takes

 

 

 

effect on your DMPs.

 

 

Deployment time

The count of how many minutes will be allowed to elapse after a DMS-CD deployment package begins

limit per file (in

 

to provision any file. Upon reaching this threshold, the file moves to the back of the queue and its transfer

minutes)

 

is deferred.

 

 

The next file advances to the front of the queue and the deployment continues. DMS-CD applies this

 

 

threshold to a deployment package as many times as necessary until it has cycled through all of its files,

 

 

and then the transfer is resumed for a deferred file after it returns to the front of the queue. This threshold

 

 

might cause the transfer of any especially large file to be distributed across days. Bottlenecks are

 

 

prevented and as many assets are provisioned as can be provisioned.

 

 

When you derive this value from the maximum transfer rate, large files in DMS-CD deployment packages

 

 

are more likely to transfer quickly.

 

 

The permitted value is any whole number in the range from 1 to 10080, where 10,080 minutes is the same

 

 

as 168 hours or 7 days.The factory-default value is 1440 minutes, which is exactly 24 hours.

 

 

Deployment retry

The count of how many times DMS-CD should try again to restart a failed deployment, until DMS-CD

count

 

stops trying.

 

 

In combination with the deployment retry time, this setting has significant impact on how long it takes

 

 

DMS-CD to detect failed deployments. For example, 5 retries x 300 seconds = 1,500 seconds

 

 

(25 minutes), while 5 retries x 30 seconds = 150 seconds (2.5 minutes).

 

 

The permitted value is any whole number in the range from 1 to 100. The default value is 5 retries. We

 

 

recommend that you do not change this value.

 

 

 

 

 

User Guide for Cisco Digital Media Manager 5.2.x

19-22

OL-15762-03

Page 272
Image 272
Cisco Systems 5.2.x manual Appliance during DMS-CD deployments, 19-22, Effect on your DMPs