Specifications

2-7
Cisco TV CDS 2.5 ISA Software Configuration Guide
OL-24788-01
Chapter 2 Network Design
CDS Workflow
Centralized Management
Centralized management uses one Virtual Video Infrastructure Manager (VVIM) to manage the Vaults,
Caching Nodes, and Streamers in a VVI.
Split-Domain Management
Split-domain management uses one VVIM to manage the domain of Vaults and Caching Nodes, and
separate managers, the Stream Managers, to manage each domain of Streamers. The Stream Managers
communicate with the VVIM over port 80. If port 80 is not open for communication, the managers
cannot communicate with each other and configuration settings need to be uploaded to the Stream
Managers from information downloaded from the VVIM.
In a split-domain VVI that uses HTTP for communication between the Caching Nodes and Streamers,
the databases for each domain are separate. The information stored in each database is not shared with
the servers in the other domains.
In an ISA environment with a split-domain VVI that uses CCP for communication between the Caching
Nodes and Streamers, the database is replicated among all servers in the Vault/Cache domain and the
Stream domains. Because the VVI allows intercommunication among different Cache Groups and
Stream Groups when CCP Streamers are used, the server ID and group ID must be unique across the
system.
Note Split-domain management is supported in an RTSP environment, and an ISA environment with the
Content Storage feature and CCP Streamers.
CDS Workflow
Content is ingested and stored in the Vault array. The Vault array can consist of two Vault Groups, which
in turn consists of two or more Vaults that are either colocated or distributed to multiple locations across
an Ethernet network. Content ingest is initiated by the backoffice based on a subscriber request, and
based on schedule or barker channel content. Manual ingest, which is operator initiated, is also offered
as an optional feature.
Note The ability to differentiate between a DVD asset and a video asset to support ingest, trick-play creation,
and streaming of content files as large as 120 GB is supported. The content files could span multiple
days.
As the content is ingested into the Vault, any necessary trick-mode files are created. The content and
trick-mode files are then mirrored within the same Vault or across the Vault array. The replication of
content allows for data recovery should a Vault undergo a failure.
Content is delivered from the Vault array to the Stream Group in response to cache-fill calls from the
Streamers. Content is also distributed across the network in response to scheduled or barker stream
content fulfillment.
As Streamers need to fill content, they issue locate requests to the Vaults for the specific content. The
Streamer makes a decision on which Vault to pull content from based on the responses. The process of
determining where to pull content from includes memory capacity and disk capacity of the Vault, as well
as network capacity.