Specifications

2-13
Cisco TV CDS 2.5 ISA Software Configuration Guide
OL-24788-01
Chapter 2 Network Design
Vault Virtualization
Remote Site
Each remote CDS has a local Vault Group and communicates with a local BMS and local AMS located
at the headend or at another headend nearby. Each remote CDS is able to ingest local content through
the local Vaults and is able to access content stored in the central storage facility by way of the Caching
Nodes and Vaults in the VVI. The centrally stored content is abstracted from the BMS by means of the
local Content Store providing a virtual view of that content to the BMS. Both local and central content
are available to fulfill streaming requests received by the Streamers in a remote CDS.
The ISA Regionalization feature uses the existing ISA architecture, but extends the ISA content
component to support new behaviors associated with where content is physically located. Each CDS
operates with a local ISA Content Store, which is extended to manage both centrally and locally stored
content.
Real-time asset (RTA) content is not centralized, and is stored on local Vaults in each headend. The CDS
determines if content should be ingested centrally or locally based upon on the type of content (VOD or
RTA) that is being requested.
Note If the local Vaults are not available because they are down or have lost connectivity, then the master
Streamer in the headend automatically takes over as the Ingest Driver client. If this occurs, when the
local Vaults have been recovered and regained connectivity, the Ingest Driver client must be migrated
back to the local Vaults before RTA ingests can be restored.
To move the Ingest Driver client from the master Streamer back to the local Vaults, stop and restart the
statsd process on the master Streamer by entering the following commands:
pkill statsd
/home/stats/statsd -i <server_mgmt_IP_addr> -s <subnet mask> -d eth0
Ingest Driver
The ISA Regionalization feature introduces the Ingest Driver, which has a server-side and a client-side.
The Ingest Driver server is located at the central location, on the master Vault, and is responsible for
managing the content ingestion and deletion requests from the Ingest Driver clients located at the remote
sites.
Ingest Driver Server
The centralized Vaults run an internal Naming Service, Notification Service, and Content Store. This
Content Store is not associated with a remote BMS, and acts independently of all remote sites. The
Ingest Driver gets the Content Store factory from the internal Naming Service, ingests content using the
createServant and provision methods, and deletes content using destroy and removeServant.
The Ingest Driver server is started and stopped on the master Vault and is automatically restarted like
other ISA processes. When the server is started, it binds to a TCP socket and waits for requests. To
handle the requests quickly, there are several threads created to parse the requests and fulfill them. When
the server processes the request for each content, only one request is handled; that is, other simultaneous
requests for the same content are blocked.
The Ingest Driver server reads the isa.cfg file and incorporates the following Ingest Driver configuration
parameters set on the CDSM GUI:
• IngestDriverEnabled=1
• IngestDriverRole=1 (for server)