Specifications

4-77
Cisco TV CDS 2.5 ISA Software Configuration Guide
OL-24788-01
Chapter 4 Configuring the CDS
Array Level Configuration
Note The Max Bandwidth fields represent the throughput for the pipe, which is defined per site
(Stream Group, Cache Group, and so on); not each server. For all existing thin pipes, only the
Max Transmit Bandwidth and Max Receive Bandwidth fields are allowed to be edited. All
other fields are read only.
If Site 1 has 2 Vault Groups with 2 Vaults each and Site 2 has 1 Cache Group with 2 Caching Nodes, and
the network design and physical link were such that it could support 500 Mbps throughput (that is, 500
Mbps transmit and 500 Mbps receive), then the maximum of the Transmit Max Bandwidth cannot
exceed 500 Mbps and the maximum of the Receive Max Bandwidth cannot exceed 500 Mbps. Further,
the sum of the bandwidths of all physical links configured for CCP among all sites must be less than the
bandwidth configured for the AF class reserved for CCP.
Note The bandwidth threshold for each server has an upper limit of 90 percent and a lower limit of 5
percent. For more information, see the “Bandwidth Manager for Thin Pipe” section on page 2-8.
Step 6 In the Available Remote Sites area, check the check box next to each remote site that you want to use
this maximum bandwidth restriction.
Step 7 Check the Limit traffic to all HTTP subnets check box if this thin pipe with the Max Bandwidth
settings configured is created to limit the bandwidth between the selected Local Site and the HTTP
Streamers in a VVI represented by the selected remote sites.
Note This field is only applicable if HTTP is the cache-fill protocol. HTTP as the cache-fill protocol
is only supported in RTSP environments.
Step 8 Alternatively, to apply the thin pipe settings to specific HTTP Streamer subnets, uncheck the Limit
traffic to all HTTP subnets check box and specify the subnets in the Subnet Configuration section.
Enter the Network and Subnet Mask for each subnet. To add more HTTP Streamer subnets, click the
plus icon in the Subnet Configuration section.
Note The Subnet Configuration section is only applicable if HTTP is the cache-fill protocol.
Step 9 Click Submit
To reset the field, click Reset.
To delete a thin pipe mapping, choose the pipe name from the Configured Pipes drop-down list, click
Select, and click Delete.
Configuring the Ingest Driver Client
The Ingest Driver Client page is used to configure the settings for the Ingest Driver client, which is
associated with the Stream Manager in a VVI with split-domain management. The Ingest Driver client
is used by the local Content Store at the headend to send requests to the Ingest Driver server at the
centralized storage facility and receive responses from the Ingest Driver server.