Cisco TV CDS 2.4 RTSP Software Configuration Guide for the Cisco ISM (Integrated Service Module) Line Card
Configuring the CDS
Downloads: This chapterpdf (PDF - 2.08MB) The complete bookPDF (PDF - 4.7MB) | Feedback

Table of Contents

Configuring the CDS

System Level Configuration

Configuring DNS Services

Configuring NTP Services

Configuring the Hosts Service

Configuring the Array Name

Configuring QAM Gateways

ARP

Configuring the Headend Setup

Configuring Stream Destinations

Configuring the Bandwidth Manager

Configuring the Ingest Manager

Configuring the Authentication Manager

Configuring the Redirect Server

Configuring Ingest Tuning

Configuring IP Nicknames

Configuring the Media Importer

Configuring Call Signs

Configuring Input Channels

Configuring Source Output Ports

Configuring Multiple SOPs

Array Level Configuration

Configuring the Array Level DNS

Configuring the Array Level NTP Server

Configuring Stream Groups

VVI with Split-Domain Management and HTTP Streamers

Locating Cache Groups

Configuring Vault Groups

Configuring SSV Groups

Configuring Cache Groups

Mapping Vault Groups to Cache Groups

Mapping Stream Groups to Cache-Fill Sources

Mapping Vault Groups for Redundancy

Configuring the Master Vault Group

Configuring the Control and Setup IPs

Configuring Cache-Fill Bandwidth Using Thin Pipe Mapping

Configuring the Media Scheduler

User Preferences

Scheduling Content for Ingest

Package Metadata Editor

Fixing Conflicts in the Media Scheduler

Server Level Configuration

Configuring the Interfaces

Configuring the Servers

Configuring QoS Settings

Configuring the Route Table

CServer Source Route Type

CServer Destination Route Type

Stream Control Route Type

Configuring the SNMP Agent

Configuring the Server Level DNS

Configuring the Server Level NTP

Other NTP Configurations

Configuring RTSP Setup

RTSP Deployment

Configuring FSI Setup

Configuring the CDS

This chapter provides information on configuring the CDS servers. The topics covered in this chapter include:


NoteIf Virtual Video Infrastructure (VVI) with split-domain management is enabled, the CDSM pages associated with the Vaults and Caching Nodes display only on the VVI Manager (VVIM), and the CDSM pages associated with the Streamers display only on the Stream Manager. For more information, see the If Virtual Video Infrastructure (VVI) with split-domain management is enabled, the CDSM pages associated with the Vaults and Caching Nodes display only on the VVI Manager (VVIM), and the CDSM pages associated with the Streamers display only on the Stream Manager. For more information, see the “Virtual Video Infrastructure” section.


System Level Configuration

The System Level tab has the following configuration options:


NoteThe System Level configuration settings are distributed to all arrays and servers in the CDS. The System Level configuration settings are distributed to all arrays and servers in the CDS.


Configuring DNS Services

The System DNS page is used to configure up to 16 domain suffixes and 16 DNS servers.

To view the current DNS System Level settings choose, Configure > System Level > System DNS .


NoteIf you are upgrading the TV CDS software to Release 2.2 from Release 2.0 or an earlier release, the system prompts you to If you are upgrading the TV CDS software to Release 2.2 from Release 2.0 or an earlier release, the system prompts you to Submit any settings that have previous domain suffixes to populate the new DNS database structure.


To configure the DNS service settings, do the following:


Step 1 Choose Configure > System Level > System DNS . The System DNS page is displayed.

Step 2 Enter the DNS system level settings as appropriate. See Table 3-1 for descriptions of the fields.

 

Table 3-1 DNS Service Fields

Field
Description

New Domain Suffix

Specify, if applicable, the internal domain that is used to fully qualify an unqualified hostname. For example, if you are using OpenStream as the BMS, specify a subdomain consistent with what OpenStream is using, for example, bms.n2bb.com. Accordingly, unqualified hostnames used in CORBA transactions, such as contentstore, resolve correctly to contentstore.bms.n2bb.com.

New DNS Server

IP address of the DNS server.

Step 3 Click Submit .

To clear the fields and start over, click Reset .


 

To delete the DNS settings, check the Delete check box and click Delete Entry .

Configuring NTP Services

The System NTP Server page is used to configure up to 16 NTP servers. The clocks on all CDS servers (Vault, Streamer, and Caching Node) and the CDSM and VVIM in a CDS must be synchronized in order to retrieve the statistics on to the CDSM and VVIM.

To view the current NTP System Level settings, choose Configure > System Level > System NTP Server .

To configure the NTP service settings, do the following:


Step 1 Choose Configure > System Level > System NTP Server . The System NTP Server page is displayed.

Step 2 In the New NTP Server field, enter the IP address of the NTP server.

Step 3 Click Submit .

To clear the fields and start over, click Reset .


 

To delete the NTP settings, check the Delete check box and click Delete Entry .

For information on setting the time zone on a CDS server or configuring NTP on a CDSM or VVIM, see “Other NTP Configurations” section.

Configuring the Hosts Service

The Host Service page offers the option to enter a hostname and associated IP address as an alternative or backup to the DNS service. The system searches the host service table before searching the DNS services. The host service settings are considered an alternative or backup to the DNS service.

To view the current host service settings, Choose Configure > Host Service . The hostnames currently configured are listed at the bottom of the page.

To configure the host service settings, do the following:


Step 1 Choose Configure > Host Service . The Host Service page is displayed.

Step 2 Enter the host service settings as appropriate. See Table 3-2 for descriptions of the fields.

 

Table 3-2 Host Service Fields

Field
Description

Hostname

Hostname of no more than 64 characters. Assigning hostnames is optional. The hostname does not have to be a fully-qualified domain name.

Host IP Address

IP address associated with the hostname.

Step 3 Click Submit . The new entry is added to the host table located at the bottom of the page.

To clear the fields and start over, click Reset .

Step 4 To add more hostnames to the host table, repeat Step 2 and Step 3.


 

To delete a host table entry, check the Delete check box associated with the entry and click Delete . To clear the Delete check boxes, click Reset .

Configuring the Array Name

The Array Name page is used to define Vault arrays, Streamer arrays, or ISV arrays. For more information about arrays, see the “Content Delivery System Architecture” section.


NoteCurrently the CDSM allows only for the creation of one Vault array. Currently the CDSM allows only for the creation of one Vault array.


To view the current Array Name listings, Choose Configure > Array Name . The array names currently configured are listed.

To configure an array name setting, do the following:


Step 1 Choose Configure > Array Name . The Array Name page is displayed.

Step 2 Enter the array name used to identify the group of servers.

To reset the field, click Reset .

Step 3 Click Submit .


 

Configuring QAM Gateways

The QAM Gateway page is used to identify the QAM gateway devices and the association between the Streamers and QAM device. A QAM gateway is typically a Layer 3 device.


NoteThe QAM Gateway page is not available if the Stream Destination is set to IPTV. For more information, see the The QAM Gateway page is not available if the Stream Destination is set to IPTV. For more information, see the “Stream Destination” section.


A QAM gateway is a device that sits between a Streamer and a QAM modulator. Depending on the design of your network, a QAM gateway is a Layer 3 routing device, gigabit quadrature amplitude modulation (GQAM), Narrowband Services Gateway (NSG), Path1, or a similar device.

Single-site steering is supported for an RTSP environment. Single-site steering uses only one Stream Group to serve streams to a QAM device.


NoteSingle-site steering assumes all Streamers in a Stream Group are located at the same geographical location. Single-site steering assumes all Streamers in a Stream Group are located at the same geographical location.


With single-site steering, you are given the option to set a Stream Group to High or None . Only one Stream Group can be set to High , all others are set to None . In a CDS network with single-site steering, if one Streamer in the Stream Group that is serving streams to a QAM device fails, another Streamer in the same group takes over.

ARP

The Address Resolution Protocol (ARP) is the method for finding a host MAC address when only its IP address is known. The QAM Gateway page allows you to specify the MAC address of an IP gateway. There are three reasons you may want to do this:

1. To statically configure the MAC address of an IP gateway.

2. ARP is disabled on the QAM gateway.

3. To statically configure all devices on the network to have all packets go to a specific IP gateway.

For single-site steering, the QAM Gateway page allows you to specify the MAC address of the IP gateway when you enter the IP address of the QAM gateway. All streams from the Stream Group with a high preference are routed to the IP gateway specified.


NoteWe recommend you leave all QAM MAC settings blank and allow ARP to determine the MAC address of the next Layer 3 device connected to the Streamer. To specify the next Layer 3 device, see the We recommend you leave all QAM MAC settings blank and allow ARP to determine the MAC address of the next Layer 3 device connected to the Streamer. To specify the next Layer 3 device, see the “Configuring the Route Table” section.


To view the current configuration for a QAM gateway, Choose Configure > QAM Gateway , choose the QAM IP address from the drop-down list, and click Next .

To configure a QAM gateway, do the following:


Step 1 Choose Configure > QAM Gateway . The QAM Gateway page is displayed (Figure 3-1).


Note If Bulk Configuration is enabled, the Configuration File Location field is displayed, along with the Browse and Import buttons. To import a Bulk Configuration XML file, click Browse to locate the file, then Import to import the file. The status of the import is displayed in the left panel.

For information on enabling the Bulk Configuration feature, see the “Bulk Configuration” section. For information about creating a Bulk Configuration file for QAM Gateways, see the “Creating QAM Gateway Bulk Configuration Files” section.


Step 2 From the drop-down list, choose enter new and click Next .

Figure 3-1 QAM Gateway Page

 

Step 3 Enter the QAM gateway settings as appropriate. See Table 3-3 for descriptions of the fields.

 

Table 3-3 QAM Gateway Fields

Field
Description

QAM IP

IP address of the QAM gateway.

QAM MAC

MAC address of the next Layer 3 device connected to the Streamer in the path to the QAM modulator. The MAC address can be entered with or without the colon separators.

We recommend you leave the QAM MAC setting blank and allow ARP to determine the MAC address of the next Layer 3 device. To specify the next Layer 3 device, see the “Configuring the Route Table” section.

Stream Group Preferences

Choose the preference for each Stream Group. The preferences are:

  • High—First preference of Streamer or Stream Group to stream to this QAM.
  • None—Do not use this Streamer or Stream Group to stream to this QAM.

For more information on creating Stream Groups, see the “Configuring Stream Groups” section.

Step 4 Click Submit .

To reset the fields, click Reset .


 

To edit a QAM gateway, choose the QAM IP address and click Next . Enter the new settings and click Submit .

To delete a QAM gateway, choose the QAM IP address, click Next , and then click Delete QAM .

Configuring the Headend Setup

The Headend Setup page is associated with the Service Group Steering optional feature.


NoteThe Headend Setup page is not available if the Stream Destination is set to IPTV. For more information, see the The Headend Setup page is not available if the Stream Destination is set to IPTV. For more information, see the “Stream Destination” section.


Service Group Steering is used to associate service groups with Stream Groups. The Headend Setup page offers more granularity than the QAM Gateway page. The QAM Gateway page allows you to assign preference to which Stream Groups serve which QAM Gateways. The Headend Setup page allows you to assign preference to which Stream Groups serve which service group.


NoteThe Headend Setup page is displayed only if the Service Group Steering feature is enabled. For more information, see the The Headend Setup page is displayed only if the Service Group Steering feature is enabled. For more information, see the “Service Group Steering” section



NoteYou must first configure the Stream Groups before you can configure the headend setup for a specific service group. See the You must first configure the Stream Groups before you can configure the headend setup for a specific service group. See the “Configuring Stream Groups” section.


To configure the headend setup, do the following:


Step 1 Choose Configure > Headend Setup . The Headend Setup page is displayed ( Figure 3-2).


Note If Bulk Configuration is enabled, the Configuration File Location field is displayed, along with the Browse and Import buttons. To import a Bulk Configuration XML file, click Browse to locate the file, then Import to import the file. The status of the import is displayed in the left panel.

For information on enabling the Bulk Configuration feature, see the “Bulk Configuration” section. For information about creating a Bulk Configuration file for QAM Gateways, see the “Creating Headend Setup Bulk Configuration Files” section.


Figure 3-2 Headend Setup Page

 

Step 2 From the Select Service Group drop-down list, choose Add New .

Step 3 In the New Service Group field, enter the service group name.

Step 4 Choose the preference for each Stream Group. The preferences are:

    • High—First preference of Streamer or Stream Group to stream to this service group.
    • Medium—Second preference of Streamer or Stream Group to stream to this service group.
    • Low—Lowest preference of Streamer or Stream Group to stream to this service group.
    • None—Do not use this Streamer or Stream Group to stream to this service group.

For more information on creating Stream Groups, see the “Configuring Stream Groups” section.

Step 5 Click Submit .


 

To delete a service group, choose it from the Select Service Group drop-down list and click Delete .

Configuring Stream Destinations

The Stream Destination page provides a way to associate subnetworks with Stream Groups. The Stream Destination page is an alternative to the QAM Gateway page and Headend Setup page where you associate a Stream Group with a specific QAM device and any applicable service groups. Mapping Stream Groups to specified subnets is appropriate for IPTV networks, where each end-user device has its own IP address.


NoteThe Stream Destination page is not available if the Stream Destination is set to Cable. For more information, see the The Stream Destination page is not available if the Stream Destination is set to Cable. For more information, see the “Stream Destination” section.


To configure the Stream Destination, do the following:


Step 1 Choose Configure > Stream Destination. The Stream Destination page is displayed (Figure 3-3).


Note If Bulk Configuration is enabled, the Configuration File Location field is displayed, along with the Action on Import option, and the Browse and Import buttons.

To import a Bulk Configuration XML file, click Browse to locate the file, select Add for the Action on Import, then Import to import the file. The status of the import is displayed in the left panel.

To delete the configurations defined in the Bulk Configuration XML file, click Browse to locate the file, select Delete for the Action on Import, then Import. All the subnets defined in the Bulk Configuration XML file are deleted and the status is displayed in the left panel.

For information on enabling the Bulk Configuration feature, see the “Bulk Configuration” section. For information about creating a Bulk Configuration file for QAM Gateways, see the “Creating Stream Destination Bulk Configuration Files” section.


Step 2 From the Subnet drop-down list, choose enter new .

To edit a subnet, choose the subnet from the Subnet drop-down list.

Figure 3-3 Stream Destination Page

 

Step 3 Enter the subnet address and subnet mask and click Submit .


Note If network address translation (NAT) is used for the STBs, be sure the IP subnet reflects the public, routeable IP address for the NAT device, not the internal private IP address of the STB.


Step 4 Choose the preference for each Stream Group. The preferences are:

    • High—First preference of Streamer or Stream Group to stream to this subnet.
    • Medium—Second preference of Streamer or Stream Group to stream to this subnet.
    • Low—Lowest preference of Streamer or Stream Group to stream to this subnet.
    • None—Do not use this Streamer or Stream Group to stream to this subnet.

Note If your CDS network is deployed with a single-site steering configuration, you only see High and None as Stream Group Preference options, and only one Stream Group can have a preference of high.


For more information on creating Stream Groups, see the “Configuring Stream Groups” section.

Step 5 Click Submit .

To reset the fields, click Reset .


 

To delete a subnet, choose the subnet from the Subnet drop-down list, and click Delete Subnet .

Configuring the Bandwidth Manager

The Bandwidth Manager runs on the master Streamer and keeps track of allocated streams and VOD network resources.


NoteThe Bandwidth Manager is an optional feature is not listed if it is not included in your deployment. For information on enabling the Bandwidth Manager feature, see the The Bandwidth Manager is an optional feature is not listed if it is not included in your deployment. For information on enabling the Bandwidth Manager feature, see the “Bandwidth Manager” section.


To configure the Bandwidth Manager, do the following:


Step 1 Choose Configure > Bandwidth Manager. The Bandwidth Manager page is displayed (Figure 3-4).

Figure 3-4 Bandwidth Manager Page

 

Step 2 Enter the Bandwidth Manager settings as appropriate. See Table 3-4 for descriptions of the fields.

 

Table 3-4 Bandwidth Manager Fields

Field
Description

Bandwidth Manager IP1

IP address of the network interface card (NIC) you want the Bandwidth Manager to bind to. Valid entry includes an asterisk (*) and 0.0.0.0, which signifies the Bandwidth Manager IP is set individually for each Streamer on the RTSP Setup page. See the “Configuring RTSP Setup” section for more information.

Bandwidth Manager Port 1

Port number to listen on for incoming connections from the RTSP server. The default is 7791. The lowest port number you can allocate is 150. The highest port number is 60000.

Database Thread Pool

Number of threads in the database connection pool. The default is 10. The minimum number of database threads is 1; the maximum is 100.

Server Thread Pool

Number of threads in the Bandwidth Manager server pool that are used to process RTSP requests for the duration of the connection. The default is 5. The minimum number of server thread pools is 1; the maximum is 100.

Sync Thread Pool

Number of threads available to synchronize sessions with the RTSP during a synchronization operation. The default is 2. The minimum number of synchronization thread pools is 2; the maximum is 50.

Sync Alarm

How often the synchronization alarm is triggered. The default is 864,000 seconds (10 days). The minimum amount of time the synchronization alarm trigger can be set to is 2400 seconds (40 minutes). The maximum amount of time is 4,294,967,296 (over 136 years).

1.Changes to this field affect the same field on the RTSP Setup page.

Step 3 Click Submit .

To clear the settings, click Reset .

Step 4 Reload the Bandwidth Manager service.

a. Choose Maintain > Services . The Services Restart page is displayed.

b. From the drop-down list, choose the IP address or nickname of the server and click Display .

c. Check the Reload Bandwidth Manager check box and click Submit .

To clear the fields and start over, click Reset .


 

Configuring the Ingest Manager

The Ingest Manager takes care of provisioned content objects by collecting the metadata, sending messages to the appropriate subsystem to ingest the content, and sending messages to expire the content when the expiration period is past.


NoteThe Ingest Manager is an optional feature. The Ingest Manager is not listed on the System Level left-panel menu if it is not included in your deployment. For information on enabling the Ingest Manager feature, see the The Ingest Manager is an optional feature. The Ingest Manager is not listed on the System Level left-panel menu if it is not included in your deployment. For information on enabling the Ingest Manager feature, see the “Ingest Manager” section.


To configure the Ingest Manager, do the following:


Step 1 Choose Configure > Ingest Manager . The Ingest Manager page is displayed (Figure 3-5).

Figure 3-5 Ingest Manager Page

 

Step 2 Enter the Ingest Manager settings as appropriate. See Table 3-5 for descriptions of the fields.

 

Table 3-5 Ingest Manager Fields

Field
Description
General Settings

Ingest Manager Host

Ingest Manager listener binds to this IP address. Enter an asterisk (*) if you want to listen to all IP addresses on the system.

Ingest Manager Port

Port number to use for listening for inbound connections.

Callback Port

Port number to use for File Services Interface (FSI) callbacks.

Additional Package Window

Additional time to wait after the package expiration window has been reached before destroying the content.

FTP Timeout

Maximum period (in seconds) the Ingest Manager waits before timing out an FTP session and terminating the process.

Use Asset ID

Choose Yes to use the Asset ID for the content name, otherwise choose No . The recommended setting is No . If set to No , the Ingest Manager uses the *.mpg as the content name when used in combination with the Media Scheduler.

Manage CORBA Services

Choose Yes to have the CDS manage the CORBA services, otherwise choose No .

Require Notify Service

Choose Yes to have the CDS require the use of the Notify Service, otherwise choose No .

Ingest Manager Debug

Choose Off to have the debug logging turned off. Choose Low to have minimal information and error logging. Choose Full for full debug logging information.

Meta Data Publish

Choose Enable from the drop-down list to publish the content metadata, otherwise choose Disable .

Meta Publish URL #1

URL where the metadata is published, typically the backoffice.

Meta Publish URL #2

URL of the backup server where the metadata is published.

Ingest Settings

Ingest Interface

Choose all the ingest interfaces that apply: ISA , Cisco SOAP , Prodis SOAP; otherwise choose Disable to disable the Ingest Manager.

Name Service IP and Port

IP address and port of the CORBA Naming Service used by the backoffice. ISA-only field.

Notify Service IP and Port

IP address and port of the CORBA Notification Service used by the backoffice. ISA-only field.

Notify Service Factory

Name used to locate the Notify Service through corbaloc protocol. The default name used is NotifyEventChannelFactory. ISA only-field.

Event Channel ID

Simple name that identifies the root directory of the Event Channel where all event channels need to register. The default is EventChannels. ISA-only field.

Event Channel Kind

Directory extension of the Event Channel ID. The default is Context. ISA-only field.

Factories ID

Simple name that identifies the root directory of the factories where all factories need to register. The default is Factories. ISA-only field.

Factories Kind

Factories ID extension. The default is Context. ISA-only field.

Package Channel ID

Simple name that identifies the Package Event Channel where all events concerning package objects are published. The default is PackageChannel. ISA-only field.

Package Channel Kind

Event Channel Package ID extension. The default is Factory. ISA-only field.

Package Factory ID

Simple name that identifies the root directory of the factories where all factories need to register. The default is PackageFactory. ISA-only field.

Package Factory Kind

Factories ID extension. The default is Factory. ISA-only field.

Package Factory Name

Name of the Package Factory that will be registered with the backoffice. The default is AVS_PackageFactory. ISA-only field.

Package Factory Server ID

Numeric value that identifies the Package Factory Server for all ingests. The default is 90. ISA-only field.

Cisco SOAP URL

IP address, port, and directory on the Vault used to receive content using the Cisco SOAP (Simple Object Access Protocol). You can specify the IP address and port number, but the directory must be “CiscoAIM.” An example of the Cisco SOAP URL is http://10.22.216.251:8793/CiscoAIM.

Prodis SOAP URL

IP address, port, and directory on the Vault used to receive content using the Prodis SOAP. You can specify the IP address and port number, but the directory must be “ProdisAIM.” An example of the Prodis SOAP URL is http://10.22.216.251:8793/ProdisAIM.

Backoffice Settings

Max Retries

Maximum number of times to retry a failed communication with the backoffice. The range is 0–1000. The default is 10.

Retry Interval

Amount of time (in minutes) to wait before retrying a failed communication. The range is 0–10080. The default is 10.

If the Retry Interval is set to zero, the Ingest Manager retries once every 6000 seconds (100 minutes).

Tip By default, the Ingest Manager does not retry an expired package. Set the Retry Interval, as well as the Publish Time Adjustment field on the Input Channel page, so that if publishing a package fails, a retry can happen at least once before the start time of the recording. See the “Configuring Input Channels” section for more information.

Backoffice Timeout

Amount of time (in seconds) to wait for the backoffice to respond to a communication attempt. The range is 0–3600. The default is 300.

Backoffice

Choose TotalManage to use the TotalManage backoffice support, otherwise choose Disable to disable backoffice support.

Backoffice URL

Location of the TotalManage backoffice.

Content Store Settings

Content Store

Choose the type of content store: ISA , FSI , or NGOD . To disable the content store, choose Disable .

Content Store URL

URL where the content store is located.

Encryption Settings

Encryption

Choose Verimatrix , or Widevine to use encryption. Choose Disable to disable encryption.

Encryption URL

Location on the encryption server used to send MPEG files for encryption. An example of the Encryption URL is http://192.168.128.54:7898/files/encrypted, where the IP address, port ,and directory is specified.

Encryption FTP URL

Location on the encryption server used to retrieve encrypted MPEG files. An example of the Encryption FTP URL is ftp://192.168.128.54:7899/files/encrypted, where the IP address, port, and directory is specified.

Step 3 Click Submit .

To clear the settings, click Reset .


 

Configuring the Authentication Manager


NoteThe Authentication Manager is an optional feature. The Authentication Manager is not listed on the System Level left-panel menu if it is not included in your deployment. For information on enabling the Authentication Manager feature, see the The Authentication Manager is an optional feature. The Authentication Manager is not listed on the System Level left-panel menu if it is not included in your deployment. For information on enabling the Authentication Manager feature, see the “Authentication Manager” section.


The Authentication Manager communicates with the backoffice to validate a request received from a set-top box (STB) before setting up a session. Before requesting a session setup from the CDS, the STB requests an entitlement key from the backoffice. The STB then passes the entitlement key as one of the parameters in the request to the CDS. The CDS in turn passes the entitlement key to the backoffice to validate the request. If the backoffice responds that the entitlement key is not valid, the session is not set up and the CDS returns an error status to the STB.

To configure the Authentication Manager, do the following:


Step 1 Choose Configure > Authentication Manager . The Authentication Manager page is displayed (Figure 3-6).


Note Depending on the Authentication Manager protocol selected (either Cisco or EventIS), the Authentication Manager displays different fields.


Figure 3-6 Authentication Manager Page—Cisco

 

Step 2 Enter the Authentication Manager settings as appropriate. See Table 3-6 for descriptions of the fields.

 

Table 3-6 Authentication Manager Fields

Field
Description
Protocol

Authentication Manager IP2

Authentication Manager resides on the master Streamer. Typically, the Authentication Manager IP address is the same as that of the master Streamer.

EventIS

Cisco

Authentication Manager Port 1

Authentication Manager port number default is 7794. This port number is determined by the properties specifications of the Authentication Manager. If you need to change the port number, contact Cisco technical support.

EventIS

Cisco

EventIS Hostname

Hostname or IP address of the EventIS server.

EventIS

EventIS Port

Port number on the EventIS server used to receive authentication requests.

EventIS

Authentication Server SOAP Interface

IP address, port, and logical partition on the Streamer used to receive messages about session teardowns in the following format: http://< ip_address >:< port >< path >

Cisco

Authentication Timeout

Time to wait, in seconds, for the authentication server to respond. The range is from 1 to 10.

EventIS

Cisco

Notification Retry Interval

Time to wait, in seconds, before attempting to connect to the authentication server again. The range is from 1 to 60.

Cisco

Debug Level

From the Debug Level drop-down list, choose ERROR to have the debug logging only reporting errors. Choose INFO to report minimal information and error logging. Choose HIGH for a high level of debug logging information. Choose HEX_DUMP for the highest debug level.

EventIS

Cisco

2.Changes to this field affect the same field on the RTSP Setup page.

Step 3 Click Submit .


 

Configuring the Redirect Server

The Redirect Server page allows you to configure the port used for RTSP redirects and allows you to enable or disable the debug level for logging.


NoteThe Redirect Server page is not available if the Redirect Server feature is not enabled. For more information, see the The Redirect Server page is not available if the Redirect Server feature is not enabled. For more information, see the “Redirect Server” section.


To configure the Redirect Server settings, do the following:


Step 1 Choose Configure > Redirect Server. The Redirect Server page is displayed.

Step 2 In the Redirect Server Port field, enter the port number to use for RTSP redirects.

Step 3 From the Debug Level drop-down list, choose OFF to disable the debug logging or choose ON to enable the debug logging.

Step 4 Click Submit .

To reset the field, click Reset .


 

Configuring Ingest Tuning

The Ingest Tuning page allows you to set the speeds of the trick-mode files created for each ingested content.

To view the current ingest tuning settings Choose Configure > Ingest Tuning .

To configure the ingest tuning, do the following:


Step 1 Choose Configure > Ingest Tuning . The Ingest Tuning page is displayed (Figure 3-7).

Figure 3-7 Ingest Tuning Page

 

Step 2 Enter the ingest tuning settings as appropriate. See Table 3-7 for descriptions of the fields.

 

Table 3-7 Ingest Tuning Fields

Field
Description
Trick-Mode Settings

Speed 1

You can set eight different trick-mode speeds for each ingested content. A trick-mode file, either fast-forward or rewind (–X), is created for each selected speed.

Choose the trick-mode speed from the drop-down list and click Submit . Available trick-mode speeds are 2, 4, 5, 6, 8, 10, 15, 30, 32, 60, and 127.

To reset the values and start over, click Reset .

Speed 2

Speed 3

Speed 4

Speed 5

Speed 6

Speed 7

Speed 8

Ingest MPEG Settings

Program ID Standardization

If Program Identifier (PID) Standardization is enabled, MPEG-2 video assets have their PIDs standardized at ingest so that most assets use the same PIDs.

It may be important that all assets use the same PIDs, for example, if multiple assets are going to be part of a playlist and you cannot guarantee that all assets were created with a consistent set of PIDs. The standard PID assignment follows the CableLabs recommendations (see MD-SP-VOD-CEP2.0-I02-070105). Any changes made to the asset is reversed if an FTP OUT is performed. Only standard audio/video assets that may be used in playlists have their PIDs standardized; data downloads, audio only, carousel files, and such other files are left unmodified. Changing the PIDs does not affect normal VOD playback of the asset.

PSI

When Program ID Standardization is enabled, you have an option to enable or disable PSI. Enabling Program ID Standardization only standardizes the PIDs, not the Program Specific Information (PSI). If you choose Enabled for PSI, the Program Association Table (PAT) and the Program Map Table (PMT) are standardized so that they do not vary at all between one piece of content and another. Use these settings progressively to try and resolve issues with playlists (black scree or no video after transitions, temporary glitches, and so on). Use Program ID Standardization only first, reingest the content, and play the content. If there are still problems, try both enabling Program ID Standardization and PSI . If there are problems playing the content back that was ingested with both of these options enabled, disable them and reingest the content to see if the issue resolves.

Sequence End Remove

If Sequence End Remove is enabled, a SEQ END header that is present at the end of the asset (and only at the end) is removed on ingest. Doing this allows fades between assets in a playlist , which can make the playlist appear more seamless. Any changes made to the asset is reversed if an FTP OUT is performed. Removing the SEQ END, if present, makes no difference to the VOD playback of the asset.

Rate Standardize

If Rate Standardize is enabled, MPEG-2 video assets have their rates standardized at ingest so that most assets use one of two standard rates, 3.75 Mbps for SD assets and 15 Mbps for HD assets. These settings follow CableLabs recommendations. Standardizing the rates can be helpful in certain configurations if playlists are going to be created containing multiple assets and you cannot guarantee that all assets were created with consistent rates. For example, some QAM devices do not handle rate changes during playout. Consult your QAM vendor for guidance on whether to enable Rate Standardize. Any changes to the asset are reversed if an FTP OUT is performed.

Step 3 Click Submit .

To clear the fields and start over, click Reset .


 

Configuring IP Nicknames

The IP nicknames are used as an alternative for the IP address in the CDSM drop-down lists.

To configure an IP nickname for a CDS server or QAM gateway, do the following:


Step 1 Choose Configure > IP Nickname . The IP Nicknames page is displayed (Figure 3-8).

Figure 3-8 IP Nicknames Page

 

Step 2 Choose the IP address from the applicable drop-down list, either Cisco CDSM IP Addresses or Configured QAM Gateway IP Addresses, and click Display .

Step 3 In the IP Nickname field, enter a nickname. The name can be from 5 to 20 characters in length and can consist of uppercase and lowercase letters, numbers, and the underscore (_) or hyphen (-) symbols.

Step 4 Click Submit .

To reset the field, click Reset .


 

To edit or view a current IP nickname association, choose an IP address or nickname from the drop-down list and click Display .

Configuring the Media Importer


NoteThe Media Importer is part of the MediaX Suite, which is an optional feature. The Media Importer is part of the MediaX Suite, which is an optional feature.


The Media Importer settings allows you to specify the data feed import type used in populating the Media Scheduler with data from an EPG file, as well as to configure the automatic import function.

To configure the Media Importer, do the following:


Step 1 Choose Configure > System Level > Media Importer . The Media Importer page is displayed (Figure 3-9).

Figure 3-9 Media Importer Page

 

Step 2 Enter the settings as appropriate. See Table 3-8 for descriptions of the fields.

 

Table 3-8 Media Importer Fields

Field
Description
Media Importer Settings

Importer Type

To upload the EPG using the CDSM, set the Importer Type to host . For information on uploading an EGP file, see the “Uploading an EPG File” section.

Transformer Type

Transformer Type is configured at the time of initial installation and specifies the EPG format of either OCN or SA Tribune. This is a read-only field.

Enable Auto Import

To automatically import the EPG information, check the Enable Auto Import check box. The Auto Import fields are displayed.

FTP Server IP

IP address of the FTP server that is used to send the EPG file.

FTP Path

Directory path of the location of the EPG files on the FTP server.

Username

Username, if required, to access the FTP server.

Password

Password, if required, to access the FTP server.

Retry Count

Number of times to retry connecting to the FTP server, if the connection fails.

Retry Interval

Number of seconds to wait before retrying the connection to the FTP server.

Auto Import Schedule

Daily

If daily is chosen (the default setting), enter the time of day the EPG file should be imported using the 24-hour clock format.

Weekly

If weekly is chosen, choose the days of the week and the time of day (24-hour clock format) when the EPG file should be imported.

Step 3 Click Submit .

To reset the field, click Reset .


 

Configuring Call Signs

The CallSign Setup page is used to configure the call signs of the program channels.


NoteThe CallSign Setup is an optional feature. The CallSign Setup is not listed on the System Level left-panel menu if it is not included in your deployment. The CallSign Setup is an optional feature. The CallSign Setup is not listed on the System Level left-panel menu if it is not included in your deployment.


A call sign is a unique identifier for a program channel. The channels, identified by their call signs, are mapped to a multicast IP address and port that a content provider or satellite uses to send content by using the Single-Program Transport Stream (SPTS) IP interface.

To configure a CallSign, do the following:


Step 1 Choose Configure > System Level > Callsign Setup . The CallSign Setup page is displayed (Figure 3-10).

Figure 3-10 CallSign Setup Page

 

Step 2 Enter the call sign settings as appropriate. See Table 3-9 for descriptions of the fields.

 

Table 3-9 CallSign Setup Fields

Field
Description

CallSign

CallSign is a unique identifier for a program channel (content source).

Multicast IP

Multicast IP address of the device sending a Single Program Transport Stream (SPTS).

Port

Port associated with the CallSign.

Step 3 Click Submit .


 

To edit a CallSign setting, enter the CallSign, the new settings, and click Submit . The new settings overwrite the previous settings and are displayed in the Configured CallSigns section.

To delete a CallSign setting, check the Delete check box associated with the entry and click Delete .

Configuring Input Channels


NoteThe Input Channels page is part of the MediaX Suite, which is an optional feature. The Input Channels page is part of the MediaX Suite, which is an optional feature.


The Input Channels page allows you to define channels mapped to a multicast group IP address and port, where scheduled content IS ingested. The Input Channels page also collects several values for metadata generation.

If you upload an EPG file, and you want to modify the metadata for all programs for a channel, then add the channel in the Input Channels page and enter the modifications in the fields provided. All scheduling information from the EPG file is listed on the Media Scheduler page. For more information, see the “Uploading an EPG File” section.


Caution All channel default values specified on the Input Channels page overwrites any metadata information for future ingested assets of the specified channel. The metadata for the assets already ingested are not affected.

To define a channel and set the metadata information, do the following:


Step 1 Choose Configure > System Level > Input Channels . The Input Channels page is displayed (Figure 3-11).

Figure 3-11 Input Channels Page

 

Step 2 From the Select Channel drop-down list, choose Add New Channel .


Note The Channel Name is automatically generated by combining the Provider and Channel ID fields with a hyphen (-) between the values.


Step 3 In the Multicast Group IP field, enter the multicast IP address that the Vault must join (by using IGMP) to ingest content.

Step 4 In the Port field, enter the port number the Vault should listen to for ingesting content.


Note The combination of the IP address and port must be unique for each channel.


Step 5 Enter the channel settings as appropriate. See Table 3-10 for descriptions of the fields.

 

Table 3-10 Input Channels Fields

Field
Description

Channel Code

Used to create the asset name and the category in the Asset Distribution Interface (ADI) metadata file. Maximum length is three characters.

Channel ID

Identifies the channel in the EPG file.

Category ID

Identifies the category corresponding to the channel (numeric only).

Catalog ID

Channel ID used in the catalog.

Product

Choose movie on demand (MOD), subscriber video on demand (SVOD), or Real-Time Innovations (RTI) as the product type for this channel.

Provider

Name of the provider.

Provider ID

Unique identifier for the provider of all assets in this channel. The Provider ID must be set to a registered Internet domain name that is restricted to at most 20 lowercase characters and belongs to the provider. For example, a valid Provider ID for CableLabs is “cablelabs-films.com.”

Preview Period

Amount of time (in seconds) the subscribers are allowed to preview assets on this channel before they are charged for viewing the asset.

Licensing Window Start

From the drop-down list, choose the number of days to add to the start date of the license window for all assets in this channel.

Licensing Window End

From the drop-down list, choose the number of days to add to the end date of the license window for all assets in this channel.

Encryption

If the assets on this channel are encrypted, choose Yes . Otherwise, choose No .

Rating

Motion Picture Association of America (MPAA) rating for all assets on this channel (G, PG, PG13, R, or NC-17).

Publish Time Adjustment

Amount of time to add to the start time for publishing each program on this channel to the backoffice. The Publish Time Adjustment must be longer than the value set for the Media Importer/Exporter Pre-Notification field.

Suggested Price

Suggested price for each asset on this channel. The format is xx.xx.

Billing ID

Billing ID for every asset on this channel. This field applies only to the SA Tribune transformer type.

Audio Type

Audio types available for all assets on this channel (Dolby ProLogic, Dolby Digital, Stereo, Mono, Dolby 5.1).

Step 6 Click Submit .

To reset the field, click Reset .


Note You cannot delete a channel that has future scheduled events.



 

To view, edit, or delete a current channel setup, from the Select Channel drop-down list choose the channel. The Channel Setup page refreshes with the configuration for the channel selected. To delete the channel, click Delete . To edit the channel configuration, edit the fields and click Submit .

Configuring Source Output Ports


NoteThe Source Output Port page is displayed when NGOD is selected as the RTSP Deployment Type on the CDSM Setup page. For more information, see the The Source Output Port page is displayed when NGOD is selected as the RTSP Deployment Type on the CDSM Setup page. For more information, see the “RTSP Deployment Type” section.


The Multiple SOPs feature introduces the ability to create SOP domains and associate a virtual IP address with each domain. The stream interfaces on the Streamer are grouped by using the Route Tables page and are associated with an SOP domain and virtual IP address. This allows for the grouping of the stream interfaces on a Streamer into two groups, each group associated with an SOP domain and virtual IP address, to direct traffic from the stream interfaces to two different routers.

The logical SOP appears to the other NGOD components as a single interface, but internally to the CDS, the logical SOP could represent multiple physical interfaces on multiple Streamers. All the physical interfaces of a logical SOP are directed to one router, while the interfaces of another logical SOP are directed to a different router. Each Streamer, defined by a logical SOP, connects to a different router.

In Release 2.1.1 and Previous Releases

In Release 2.1.1 and previous releases that were configured for an RTSP environment with an NGOD deployment, the CDSM provided a Server Level configuration page, the RTSP Setup page, which included configuration fields for the physical SOP IP and port and the logical SOP. The physical SOP IP and port were the IP address and port number of the gigabit Ethernet interface that was used as the SOP on the Streamer. The logical SOP was the domain name used for identification purposes to the On Demand Resource Manager (ODRM). The logical SOP (domain name of the SOP) was tied to the entire Streamer. The Streamer is part of a Stream Group, and a system can have multiple Stream Groups in a system, each supporting a different SOP.

The logical SOP domain name, maximum number of streams, and maximum bandwidth for each SOP are provided to the ODRM vendor, who uses this information along with the service group information, QAM device information, and so on, to configure the system.

In Release 2.1.2 and Later Releases

In Release 2.1.2 and later releases that were configured for an RTSP environment with an NGOD deployment, the SOP domain name and a virtual IP address are added through the Source Output Port page. Each group of stream interfaces on a Streamer are represented by a virtual IP address and SOP domain.

The stream interfaces (or stream/cache interfaces) on each Streamer connect to two routers, with half the interfaces directed to one router and the other half of the interfaces directed to the other router. This is accomplished by way of the Route Tables page. For more information, see the “Configuring the Route Table” section.

If there are three Streamers, for example, with stream interfaces 1 to 6 going to router 1 and stream interfaces 7 to 12 going to router 2, the following SOPs need to be created:

  • SOP A is defined as interfaces 1 to 6 on Streamer 1, 2, and 3.
  • SOP B is defined as interfaces 7 to 12 on Streamers 1, 2, and 3.

The Multiple SOP feature allows for stream routing control, provides balance across the routers, and provides redundancy in case of a transport network failure. If a stream interface fails, another stream interface in the same SOP takes over.

Configuring Multiple SOPs

The following rules apply for the Multiple SOP feature:

  • There is a one-to-one relationship between the SOP virtual IP address and domain name, and the stream interface subnet configured in the Route Tables page.
  • SOP virtual IP address and domain name cannot span multiple source subnets and a source subnet cannot span multiple SOPs.
  • SOP virtual IP address and domain name cannot span more than one Stream Group.

To configure the Multiple SOP feature, do the following:


Step 1 Choose Configure > System Level > Source Output Port. The Source Output Port page is displayed.

Step 2 In the SOP Name field, enter the domain name of this Streamer for identification purposes to the On Demand Resource Manager (ODRM). In Release 2.1.1 and previous releases, this was the Logical SOP field on the RTSP Setup page.

Step 3 In the Virtual IP field, enter the virtual IP address for this SOP.

Step 4 Click Submit .

Step 5 Repeat Step 2 to Step 4 for each SOP.

The configured SOPs are displayed in the bottom half of the page. To delete an SOP, check the Delete check box associated with the SOP and click Submit .


 

To complete the configuration of multiple SOPs, you must define each route in the Route Table page and choose CServer Source as the Route Type. For more information, see the “Configuring the Route Table” section.

Array Level Configuration

The Array Level tab has the following configuration options:


NoteThe Array Level configuration settings are distributed to all servers in the specified array. The Array Level configuration settings are distributed to all servers in the specified array.


Configuring the Array Level DNS

The Array DNS page is used to configure up to 16 domain suffixes and 16 DNS servers.

To view the current Array DNS settings for an Array Level, Choose Configure > Array Level > Array DNS , choose an array name from the drop-down list, and click Display .


NoteIf you are upgrading the TV CDS software to Release 2.2 from Release 2.0 or an earlier release, the system prompts you to If you are upgrading the TV CDS software to Release 2.2 from Release 2.0 or an earlier release, the system prompts you to Submit any settings that have previous domain suffixes to populate the new DNS database structure.


To configure the DNS settings for an Array Level, do the following:


Step 1 Choose Configure > Array Level > Array DNS . The Array DNS page is displayed.

Step 2 From the Array Name drop-down list, choose an array and click Display .

Step 3 Enter the DNS binding Array Level settings as appropriate. See Table 3-11 for descriptions of the fields.

 

Table 3-11 Array DNS Fields

Field
Description

New Domain Suffix

Specify, if applicable, the internal domain that is used to fully qualify an unqualified hostname. For example, if you are using OpenStream as the BMS, specify a subdomain consistent with what OpenStream is using, for example, bms.n2bb.com. Accordingly, unqualified hostnames used in CORBA transactions, such as contentstore, resolve correctly to contentstore.bms.n2bb.com.

New DNS Server

IP address of the DNS server.

Step 4 Click Submit .

To clear the fields and start over, click Reset .


 

To delete the DNS settings, check the Delete check box and click Delete Entry .

Configuring the Array Level NTP Server

The Array NTP Server page is used to configure up to 16 NTP servers.

To view the current NTP settings for an Array Level, choose Configure > Array Level > Array NTP Server , choose an array name from the drop-down list, and click Display .

To configure the NTP settings for an Array Level, do the following:


Step 1 Choose Configure > Array Level > Array NTP Server . The Array NTP Server page is displayed.

Step 2 From the Array Name drop-down list, choose an array and click Display .

Step 3 In the New NTP Server field, enter the IP address of the NTP server.

Step 4 Click Submit .

To clear the fields and start over, click Reset .


 

To delete the NTP settings, check the Delete check box and click Submit .

For information on setting the time zone on a CDS server or configuring NTP on a CDSM or VVIM, see “Other NTP Configurations” section.

Configuring Stream Groups

A Stream Group consists of one or more Streamers. Streamers within a Stream Group work as a team with regard to content caching, load distribution, and bandwidth usage. Stream Groups interact with other Stream Groups by passing streams among each other based on performance qualification and cost considerations. If a Stream Group must give up a stream to another group, Stream Group preferences set on the QAM Gateway page are followed. Stream Groups relate to QAM gateways or destination subnetwork by the Stream Group preference. For more information about Stream Group and QAM gateway associations, see the “Configuring QAM Gateways” section. For more information about destination subnetworks and Stream Groups, see the “Configuring Stream Destinations” section.

A Streamer can never be a member of more than one Stream Group.

When grouping Streamers you should take into account network cost to stream, bandwidth usage, and geographic locations of Streamers and QAM gateways. All Streamers in a group are considered to have the same cost to reach a destination.

VVI with Split-Domain Management and HTTP Streamers

A VVI with split-domain management has one manager (VVIM) that manages the Vaults and Caching Nodes, and one manager (Stream Manager) that manages the Streamers.

When you use CCP Streamers in a VVI, all group IDs and server IDs need to be unique among all servers in the VVI. The VVIM manages all the group IDs and server IDs for the VVI with CCP Streamers. The Stream Manager gets an allotment of group IDs from the VVIM in one of two ways:

  • During the initial installation, by way of the CDSM Setup page
  • In the first-time configuration of Stream Groups

Communication between the VVI Manager and the Stream Manager is accomplished through database replication when CCP is used as the protocol.

The CDSM Setup page for the Stream Manager has a field for the VVIM IP address. The VVIM IP address is used to send an HTTP GET request to the VVIM for a range of group IDs. If the Stream Manager is unable to reach the VVIM, either because port 80 is not open for communication or some other connectivity reason, the Stream Group page displays a field for entering the beginning group ID. The administrator of the Stream Manager gets the beginning group ID from the administrator of the VVIM. The VVIM gets the beginning group ID on the Configuration Generator page. For more information, see the “Identifying Server IDs and Group IDs for VVI with Split-Domain Management” section.

For more information about the VVI settings on the CDSM Setup page, see the “Virtual Video Infrastructure” section.


Caution The beginning group ID must be generated by the VVIM, and if manually entered, it must be entered correctly. Entering the wrong ID can cause cache-fill failures and other issues.

To configure a Stream Group, do the following:


Step 1 Choose Configure > Array Level > Stream Groups Setup . The Stream Groups page is displayed (Figure 3-12).

To edit a Stream Group, choose the Stream Group from the drop-down list and click Display .

Figure 3-12 Stream Groups Page

 

Step 2 From the Select Stream Group to View/Edit drop-down list, choose Add New Stream Group and click Display .

Step 3 In the New Stream Group Name field, enter the name of the Stream Group and click Submit .

You can use only alphanumeric characters (0–9, a–z, A–Z), the dash (-), and the underscore (_) to create a Stream Group name.

Step 4 Add the Streamers to the Stream Group.

The unassigned Streamers are listed along with a drop down-list for each that offers the options described in Table 3-12 .

 

Table 3-12 Unassigned Streamer Options

Unassigned Streamer Option
Description

No Change

Do not make any changes to the Stream Group assignment.

Stream Group Name

Add this Streamer to this Stream Group.

None

Remove this Streamer from this Stream Group. Applicable only to Streamers assigned to the selected Stream Group.

Step 5 Click Submit .

To reset the field, click Reset .


 

To view the members of a Stream Group, choose the Stream Group from the drop-down list and click Display .

To delete a Stream Group, first remove all Streamers from the group, then click Delete Group .


Caution If you delete a Stream Group or edit the members of a Stream Group, and the Stream Destination feature is enabled, you must re-submit each Stream Destination subnet that is associated with the Stream Group that you changed or deleted.

Locating Cache Groups

The Cache Group Locator page is used by the Stream Manager in a VVI with split-domain management to identify and locate the Cache Groups that are managed by the VVIM. Split-domain management uses port 80 to communicate group IDs and server IDs. The databases for each domain are separate.


NoteThe Cache Group Locator page is available only on the Stream Manager when VVI is enabled. For more information, see the The Cache Group Locator page is available only on the Stream Manager when VVI is enabled. For more information, see the “Virtual Video Infrastructure” section.


There are two methods on the Cache Group Locator page for getting the Cache Group information:

  • Import
  • Upload

The Import option uses an HTTP GET request to communicate with the VVIM in retrieving the Cache Groups. The Upload option uploads an XML file that was created by the VVIM. To use the Import option, the Stream Manager must know the IP address of the VVIM and must be able to communicate with the VVIM over port 80. The VVIM IP address is set on the CDSM Setup page. See the “Virtual Video Infrastructure” section for more information. To use the Upload option, the XML file must be downloaded from the VVIM and delivered to the administrator of the Stream Manager. For more information on downloading the XML file from the VVIM, see the “Identifying Server IDs and Group IDs for VVI with Split-Domain Management” section.

To identify and locate the Cache Groups, do the following:


Step 1 Choose Configure > Array Level > Cache Group Locator . The Cache Group Locator page is displayed ( Figure 3-13).

Figure 3-13 Cache Group Locator Page

 

Step 2 From the Configured Cache Locations drop-down list, choose Add Cache Group Locations .

Step 3 Choose either Import or Upload .

If you choose Import , do the following:

a. In the VVIM IP , enter the IP address of the VVIM.

If the VVIM IP address was provided in the CDSM Setup page, or previously on the Cache Group Locator page, it is displayed in the VVIM IP field.

b. Click Import Cache Group s.

The Stream Manager sends an HTTP GET request over port 80 to the VVIM for the Cache Group information. If the VVIM does not respond with the CacheGroupsConfig.xml file before the timeout period, the Cache Group Locator page displays the Upload option.

If you choose Upload , do the following:

a. Get the CacheGroupsConfig.xml file from the administrator of the VVIM and save it to a location you can access from the CDSM (for example, to your local machine).

b. Click Browse to locate the CacheGroupsConfig.xml file. The Choose File dialog box is displayed.

c. Navigate to the file and click Open . The path and filename are displayed in the Cache Groups File Location field.

d. Click Upload .

Step 4 After the CacheGroupsConfig.xml file is either imported or uploaded, the Cache Groups are listed in the Configured Cache Locations drop-down list.


 

To view, edit, or delete a Cache Group Location, do the following:


Step 1 Choose Configure > Array Level >Cache Group Locator . The Cache Group Locator page is displayed.

Step 2 From the Configured Cache Locations drop-down list, choose a Cache Group location. The page refreshes and the Cache Group information is displayed. The Location Virtual IP and Location Subnet fields are informational only.

Step 3 To rename the Cache Group Location, enter a new name in the Cache Location Name and click Submit . To reset the field, click Reset

Step 4 To delete a Cache Group location, click Delete .


 

Configuring Vault Groups

A Vault Group consists of one or more Vaults. Vaults within a Vault Group work as a team with regard to content ingest, cache-fill responses, load distribution, and bandwidth usage. Vault Groups interact with other Vault Groups by passing cache-fill requests among each other based on performance qualification and cost considerations. For more information on Vault Group redundancy, see the “Mapping Vault Groups for Redundancy” section.


NoteThe Vault Groups Setup page is part of the Vault Redundancy feature and is displayed only if Vault Redundancy is enabled. For more information, see the The Vault Groups Setup page is part of the Vault Redundancy feature and is displayed only if Vault Redundancy is enabled. For more information, see the “Vault Redundancy” section. If VVI is enabled, The Vault Groups Setup page is displayed only on the VVIM. For more information, see the “Virtual Video Infrastructure” section.


A Vault can never be a member of more than one Vault Group.

When grouping Vaults you should consider network costs, bandwidth usage, and geographic locations of Vaults, Caching Nodes, and Streamers. All Vaults in a group are considered to have the same cost to reach a destination.


NoteThe maximum number of Vault Groups is 20. The maximum number of Vault Groups is 20.


To configure a Vault Group, do the following:


Step 1 Choose Configure > Array Level > Vault Groups Setup . The Vault Groups Setup page is displayed ( Figure 3-14).

Figure 3-14 Vault Groups Setup Page

 

Step 2 From the Select Vault Group to View/Edit drop-down list, choose Add New Vault Group and click Display .

To edit a Vault Group, choose the Vault Group from the drop-down list and click Display .

Step 3 In the New Vault Group Name field, enter the name of the Vault Group and click Submit .

You can use only alphanumeric characters (0–9, a–z, A–Z), the dash (-), and the underscore (_) to create a Vault Group name.

Step 4 Add the Vaults to the Vault Group.

The unassigned Vaults are listed along with a drop down-list for each that offers the options described in Table 3-13 .

 

Table 3-13 Unassigned Vault Options

Unassigned Vault Option
Description

No Change

Do not make any changes to the Vault Group assignment.

Vault Group Name

Add this Vault to this Vault Group.

None

Remove this Vault from this Vault Group. Applicable only to Vaults assigned to the selected Vault Group.

Step 5 Click Submit .

To reset the field, click Reset .


 

To view the members of a Vault Group, choose the Vault Group from the drop-down list and click Display .

To delete a Vault Group, first remove all Vaults from the group, then click Delete Group .

Configuring SSV Groups

An SSV Group consists of one or more ISVs. ISVs within an SSV Group work as a team with regard to content ingest, cache-fill responses, load distribution, and bandwidth usage. SSV Groups interact with other SSV Groups by passing cache-fill requests among each other based on performance qualification and cost considerations.


NoteThe SSV Groups Setup page is part of the SSV Group feature and is displayed only if SSV Group is enabled. For more information, see the The SSV Groups Setup page is part of the SSV Group feature and is displayed only if SSV Group is enabled. For more information, see the “SSV Groups” section. The Vault Redundancy Map page and the Thin Pipe Map page are also displayed when SSV Groups is enabled. The Vault Redundancy Map page can be used to map SSV Groups for mirroring. For more information, see the “Mapping Vault Groups for Redundancy” section. The Thin Pipe Map page can be used to configure low-bandwidth connections among SSV Groups. For more information, see the “Configuring Cache-Fill Bandwidth Using Thin Pipe Mapping” section.


An ISV can never be a member of more than one SSV Group.


NoteThe term SSV used in the CDSM GUI is the same as the ISV. The terms are interchangeable. The term SSV used in the CDSM GUI is the same as the ISV. The terms are interchangeable.


When grouping ISVs you should consider network costs, bandwidth usage, and the geographic locations of the ISVs. All ISVs in a group are considered to have the same cost to reach a destination.


NoteThe maximum number of SSV Groups is 20. The maximum number of SSV Groups is 20.


To configure an SSV Group, do the following:


Step 1 Choose Configure > Array Level > SSV Groups Setup . The SSV Groups Setup page is displayed.

Step 2 From the Select SSV Group to View/Edit drop-down list, choose Add New SSV Group and click Display .

To edit an SSV Group, choose the SSV Group from the drop-down list and click Display .

Step 3 In the New SSV Group Name field, enter the name of the SSV Group and click Submit .

You can use only alphanumeric characters (0–9, a–z, A–Z), the dash (-), and the underscore (_) to create an SSV Group name.

Step 4 Add the SSVs (ISVs) to the SSV Group.

The unassigned SSVs are listed along with a drop down-list for each that offers the options described in Table 3-14 .

 

Table 3-14 SSV Options

SSV Option
Description

No Change

Do not make any changes to the SSV Group assignment.

Vault Group Name

Add this Vault to this SSV Group.

None

Remove this SSV from this SSV Group. Applicable only to SSVs assigned to the selected SSV Group.

Don’t Change

Do not assign this SSV to this SSV Group.

Step 5 Click Submit .

To reset the field, click Reset .


 

To view the members of an SSV Group, choose the SSV Group from the drop-down list and click Display .

To delete an SSV Group, first remove all SSVs from the group, then click Delete Group .

Configuring Cache Groups

A Cache Group consists of one or more Caching Nodes. Caching Nodes within a Cache Group work as a team with regard to content caching, load distribution, and bandwidth usage. Cache Groups interact with other Cache Groups by passing cache-fill requests among each other based on performance qualification and cost considerations. If a Cache Group must give up a cache-fill task to another group, Cache Group preferences set on the Stream to Cache Map page are followed.


NoteThe Cache Groups Setup page is part of the VVI feature and is displayed only on VVIMs. The Cache Groups Setup page is part of the VVI feature and is displayed only on VVIMs.


A Caching Node can never be a member of more than one Cache Group.

When grouping Caching Nodes you should take into account network costs, bandwidth usage, and geographic locations of Vaults, Caching Nodes, and Streamers. All Caching Nodes in a group are considered to have the same cost to reach a destination.

To configure a Cache Group, do the following:


Step 1 Choose Configure > Array Level > Cache Groups Setup . The Cache Groups Setup page is displayed (Figure 3-15).

Figure 3-15 Cache Groups Setup Page—HTTP Streamers

 

Step 2 From the Select Cache Group to View/Edit drop-down list, choose Add New Cache Group and click Display .

To edit a Cache Group, choose the Cache Group from the drop-down list and click Display .

Step 3 In the New Cache Group Name field, enter the name of the Cache Group and click Submit .

You can use only alphanumeric characters (0–9, a–z, A–Z), the dash (-), and the underscore (_) to create a Cache Group name.

Step 4 For a VVI that uses HTTP for communication between the Caching Nodes and Streamers, do the following:

a. In the Location Virtual IP field, enter the IP address this Cache Group uses as the virtual IP address for the Locate Port service. The virtual IP address is bound to the Locate IP and Port. For more information about the Locate Port service, see the “HTTP Streamers” section.

b. In the Location Subnet Mask field, enter the subnet mask for the Location IP address.

Step 5 Add the Caching Nodes to the Cache Group.

The unassigned Caching Nodes are listed along with a drop down-list for each that offers the options described in Table 3-15 .

 

Table 3-15 Unassigned Caching Node Options

Unassigned Caching Node Option
Description

No Change

Do not make any changes to the Cache Group assignment.

Cache Group Name

Add this Caching Node to this Cache Group.

None

Remove this Caching Node from this Cache Group. Applicable only to Caching Nodes assigned to the selected Cache Group.

Step 6 Click Submit .

To reset the field, click Reset .


 

To view the members of a Cache Group, choose the Cache Group from the drop-down list and click Display .

To delete a Cache Group, first remove all Caching Nodes from the group, then click Delete Group .

Mapping Vault Groups to Cache Groups

The Cache To Vault Map page is used to map Vault Groups to Cache Groups in a VVI. Before you can map Vault Groups to Cache Groups, you must create them. For more information, see the “Configuring Cache Groups” section and the “Configuring Vault Groups” section.


NoteThe Cache To Vault Map page only displays on the VVIM and is available only when Vault Redundancy and VVI are both enabled. For more information, see the The Cache To Vault Map page only displays on the VVIM and is available only when Vault Redundancy and VVI are both enabled. For more information, see the “Vault Redundancy” section and the “Virtual Video Infrastructure” section.


To map Vault Groups to Cache Groups, do the following:


Step 1 Choose Configure > Array Level > Cache To Vault Map . The Cache To Vault Map page is displayed.

Step 2 From the Cache Group drop-down list, choose a Cache Group and click Select . All available Vault Groups are displayed. By default, all preferences are set to None .

Step 3 Choose the preference setting for each Vault Group. Following are the possible preferences:

    • High—First preference as a source for cache-fill requests.
    • Medium—Second preference as a source for cache-fill requests.
    • Low—Lowest preference as a source for cache-fill requests.
    • None—Do not use this Vault Group as a cache-fill source.

Groups with the same preference level are considered equally as a cache-fill source. At least one Vault Group must have a preference higher than None.

Step 4 Click Submit .

To reset the field, click Reset .


 

To view the Vault Group mappings of a Cache Group, choose the Cache Group from the drop-down list and click Display .

To delete a Cache Group or a Vault Group, see the “Configuring Cache Groups” section or the “Configuring Vault Groups” section. When a Cache Group is deleted, the mapping for the Cache Group is also deleted, and any mapping to the Cache Group in the Stream To Cache Map page is also deleted. When a Vault Group is deleted, the Vault Group is removed from each Cache Group mapping; any mapping for the Vault Group in the Vault Redundancy Map page is also deleted.

Mapping Stream Groups to Cache-Fill Sources

The Stream To Cache Map page is used to map Cache Groups to Stream Groups in a VVI. Before you can map Cache Groups to Stream Groups, you must create them. See the “Configuring Stream Groups” section and the “Configuring Cache Groups” section for more information.

In a VVI with split-domain management, the Stream Manager must know about the Cache Groups to map the Stream Groups to the Cache Groups. See the “Locating Cache Groups” section for more information.


NoteThe Stream To Cache Map page is available only on the Stream Manager when VVI is enabled. For more information, see the The Stream To Cache Map page is available only on the Stream Manager when VVI is enabled. For more information, see the “Virtual Video Infrastructure” section.


Streamers can be used as cache-fill sources when Streamer is Cache is enabled on the Server Setup page (Configuring the Servers). A Stream Group is available on the Stream To Cache Map page when at least one Streamer in a Stream Group has Streamer is Cache enabled.

To map Cache Groups to Stream Groups, do the following:


Step 1 Choose Configure > Array Level > Stream To Cache Map . The Stream To Cache Map page is displayed (Figure 3-16).

Figure 3-16 Stream To Cache Map Page

 

Step 2 From the Stream Group drop-down list, choose a Stream Group and click Select . All available Cache Groups and Stream Groups are displayed. By default, all preferences are set to None .

Step 3 Choose the preference setting for each Cache Group and Stream Group. The possible preferences are:

    • High—First preference as a source for cache-fill requests.
    • Medium—Second preference as a source for cache-fill requests.
    • Low—Lowest preference as a source for cache-fill requests.
    • None—Do not use this Cache Group or Stream Group as a cache-fill source.

Groups with the same preference level are considered equally as a cache-fill source. At least one Cache Group must have a preference higher than None.

Step 4 Click Submit .

To reset the field, click Reset .


 

To view the Cache Group mappings of a Stream Group, choose the Stream Group from the drop-down list and click Display .

To delete a Stream Group or Cache Group, see the “Configuring Stream Groups” section or “Configuring Cache Groups” section. When a Stream Group is deleted, the mapping for the Stream Group is also deleted. When a Cache Group is deleted, the Cache Group is removed from each Stream Group mapping, and any mapping for that Cache Group in the Vault To Cache Map page is also deleted. When a Vault Group is deleted, the Vault Group is removed from each Stream Group mapping, and any mapping for the Vault Group in the Vault Redundancy Map page is also deleted.

Mapping Vault Groups for Redundancy

The Vault Redundancy Map page is used to map Vault Groups to each other. Before you can map Vault Groups for redundancy, you must create them. See the “Configuring Vault Groups” section for more information.


NoteThe Vault Redundancy Map page is part of the Vault Redundancy feature and is displayed only if Vault Redundancy is enabled. If VVI is enabled, The Vault Redundancy Map page is displayed only on the VVIM. For more information, see the The Vault Redundancy Map page is part of the Vault Redundancy feature and is displayed only if Vault Redundancy is enabled. If VVI is enabled, The Vault Redundancy Map page is displayed only on the VVIM. For more information, see the “Virtual Video Infrastructure” section and the “Vault Redundancy” section.



NoteIn Release 2.4, the maximum number of Vault Groups is 20. In Release 2.4, the maximum number of Vault Groups is 20.


Vault Groups interact with other Vault Groups by passing cache-fill requests among each other based on performance qualification and cost considerations. If a Vault Group must give up a cache-fill task to another group, Vault Group preferences set on the Vault Redundancy Map page are followed. For more information on Vault Group redundancy, see the “Vault Group Redundancy” section.

To map a Vault Group to another Vault Group, do the following:


Step 1 Choose Configure > Array Level > Vault Redundancy Map . The Vault Redundancy Map page is displayed (Figure 3-17).

Figure 3-17 Vault Redundancy Map Page

 

Step 2 From the Vault Group drop-down list, choose Vault Group and click Select . All available Vault Groups are displayed. By default, all preferences are set to Ignore .

Step 3 Choose the preference setting for the Vault Group. The possible preferences are:

    • Mirror —Content is mirrored to this Vault Group, and this Vault Group becomes the source for content requests from Streamers or Caching Nodes if the primary Vault Group becomes unavailable. You can select up to three Vault Groups to which to mirror content.

Note The Vault Mirror Copies field in the Server Setup page determines the number of mirrored copies kept in the CDS for the content stored on the specified Vault. See the “Configuring the Servers” section for more information. The Vault Redundancy Map page specifies which Vault Groups participate in the content mirroring.


    • Ignore —Do not use this Vault Group for mirroring or as a backup source of content.

Step 4 Click Submit .

To reset the field, click Reset .


 

To view the Vault Group mappings, choose the Vault Group from the drop-down list and click Display .

To delete a Vault Group, see the “Configuring Vault Groups” section. When a Vault Group is deleted, the mapping for the Vault Group is also deleted.

Configuring the Master Vault Group

The Master Vault Group page allows you to select the Vault Group that has the master Vault and the master IP address. One of the Vaults in the Master Vault Group is designated the master Vault. If the master Vault fails, another Vault in the Master Vault Group takes over as the master Vault.

The master IP address is set as part of the initial configuration (cdsconfig script) and the information is added to the statsd line in the rc.local file.

To locate the master Vault in the Master Vault Group, log in to each Vault as root and enter the ifconfig -a | more command. The master Vault has the virtual IP address (eth0:1) output as follows:

eth0:1 Link encap:Ethernet HWaddr 00:11:00:00:00:00
inet addr:172.22.98.54 Bcast:172.22.99.255 Mask:255.255.254.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Memory:b8820000-b8840000
 

The slave Vaults do not have the virtual IP address as up.


NoteThe Master Vault Group page is part of the Vault Redundancy feature and is displayed only if Vault Redundancy is enabled. If VVI is enabled, The Master Vault Group page is displayed only on the VVIM. For more information, see the The Master Vault Group page is part of the Vault Redundancy feature and is displayed only if Vault Redundancy is enabled. If VVI is enabled, The Master Vault Group page is displayed only on the VVIM. For more information, see the “Virtual Video Infrastructure” section and the “Vault Redundancy” section.


To configure the Master Vault Group, do the following:


Step 1 Choose Configure > Array Level > Master Vault Group . The Master Vault Group is displayed.

Step 2 Click the Master Vault Group radio button associated with the Vault Group.

Step 3 Click Submit .


Note After you have submitted the settings the first time, if you change the Master Vault Group, you must restart all the Vaults in the old Master Vault Group and the new Master Vault Group for the changes to take effect. See the “Restarting a Server” section for more information.



 

Configuring the Control and Setup IPs

A Streamer designated as the Setup server interfaces with the backoffice and forwards the setup messages to the appropriate Stream Group. There can only be one IP address designated as the Setup server for each Stream Group. In an RTSP environment, the Setup server and Control server must be the same server.


NoteIn an RTSP environment that uses VVI with split-domain management, each Stream Manager is allotted two Setup IDs for the Setup servers. If the Stream Manager uses both Setup IDs, it contacts the VVIM for additional Setup IDs. If the VVIM is unreachable, the Control/Setup IP page displays the Setup ID field for manual entry of the new Setup IDs. For more information, see the In an RTSP environment that uses VVI with split-domain management, each Stream Manager is allotted two Setup IDs for the Setup servers. If the Stream Manager uses both Setup IDs, it contacts the VVIM for additional Setup IDs. If the VVIM is unreachable, the Control/Setup IP page displays the Setup ID field for manual entry of the new Setup IDs. For more information, see the “Identifying Server IDs and Group IDs for VVI with Split-Domain Management” section.


The Control server is used to communicate with Lightweight Stream Control Protocol (LSCP) clients or Real Time Streaming Protocol (RTSP) clients. Each Control server handles up to 6000 clients. You must configure a Control server for each group of up to 6000 clients. For instance, if you have 7000 clients, you need to configure two Control servers. The Control servers are associated with each Stream Group. For this release there can only be one Control server for each Stream Group.

For more information about the Control and Setup servers, see the “Streamer Workflow” section.

To configure a Control/Setup IP, do the following:


Step 1 Choose Configure > Array Level > Control/Setup IP . The Control/Setup IP page is displayed ( Figure 3-18).

Figure 3-18 Control/Setup IP Page

 

Step 2 For each Stream Group, enter the IP address and subnet mask of the Control IP, Setup IP, or Control/Setup IP.

Step 3 From the IP Type drop-down list, choose an IP type. See Table 3-16 for descriptions of the types.

 

Table 3-16 Control/Setup Types

Type
Description

Control IP

IP address used only for LSCP or RTSP client control.

Setup IP

IP address of the Setup server.

Control/Setup IP

Control/Setup IP address used for LSCP or RTSP client control.

Step 4 Click Submit .

To reset the field, click Reset .


 


NoteAll currently configured Control/Setup IPs are listed in the Configured Control/Setup IPs section of the Control/Setup IP page. All currently configured Control/Setup IPs are listed in the Configured Control/Setup IPs section of the Control/Setup IP page.


To edit a Control/Setup IP, make any changes to the Control/Setup IP as necessary, and click Submit .

To delete a Control/Setup IP, check the Delete check box and click Submit .

Configuring Cache-Fill Bandwidth Using Thin Pipe Mapping

The Thin Pipe Map page allows you to configure low-bandwidth connections between local and remote groups. A local group consists of servers in the same group, for example, all the Streamers in a Stream Group are considered part of the same group, or local group. A local group consists of CDS servers in the same local area network (LAN). A remote group consists of all the servers in the other Stream Groups, Cache Groups, and Vault Groups. A remote group consists of all the CDS servers that are reachable by way of a wide area network (WAN).

There can be multiple thin pipes configured for each local group. As an example, a site with Caching Nodes organized into a Cache Group could have one 500-Mbps thin pipe going to a site with a Vault Group, and a second 500-Mbps thin pipe going to a location with a Stream Group. The thin pipes are completely independent of each other.

The Thin Pipe Map page also allows for the configuration of thin pipes in a hierarchy, where a remote group must be reached through several pipes. For example, a Cache Group could have a 500 Mbps thin pipe over which it streams to multiple Stream Groups. Each Stream Group could have separate 100 Mbps thin pipes. In this case, the Cache Group traffic on egress to all Stream Groups is limited to 500 Mbps, while ingress traffic to each Stream Group from this Cache Group is limited to 100 Mbps. In this example, the Cache Group would have four thin pipes configured: one 500 Mbps pipe to all three Stream Groups, and a total of three 100 Mbps pipes, one to each individual Stream Group.


NoteThe Thin Pipe Map page is displayed only if Thin Pipe Management is enabled. See the The Thin Pipe Map page is displayed only if Thin Pipe Management is enabled. See the “Thin Pipe Management” section for more information.


For CCP traffic to work properly in the CDS, the following configuration must exist:

  • Thin pipe mapping must be configured in the CDS.
  • DiffServ AF settings must be configured on the CDS servers.
  • Routers must support the bandwidths that are configured for the thin pipe mapping on the CDS.

NoteThe configured bandwidth for CCP on the Thin Pipe Map page must be the minimum bandwidth reserved for the AF class. 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. The configured bandwidth for CCP on the Thin Pipe Map page must be the minimum bandwidth reserved for the AF class. 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.


CCP is used as the protocol among Vaults and Caching Nodes in a VVI that uses HTTP, and among all servers in a VVI that uses CCP and in all non-VVIs. The AF class is configured on each CDS server. See the “Configuring the Servers” section for more information.

As an example, Figure 3-19 shows the maximum bandwidth available for the various groups in a Virtual Video Infrastructure (VVI) system with two super headends (SHEs), three caching sites, and one streaming site.

Figure 3-19 Thin Pipe Example

 


NoteThe maximum bandwidth available is dictated by the physical link, as well as by any network design constraints placed on bandwidth availability. If a switched network has further restrictions, for example, Vault Group 1 (VG1) to Vault Group 2 (VG2) and Cache Group 3 (CG3) share a 3 Gbps link on the route between VG1 and the other two sites, then another thin pipe must be configured to specify this 3-Gbps restriction. The maximum bandwidth available is dictated by the physical link, as well as by any network design constraints placed on bandwidth availability. If a switched network has further restrictions, for example, Vault Group 1 (VG1) to Vault Group 2 (VG2) and Cache Group 3 (CG3) share a 3 Gbps link on the route between VG1 and the other two sites, then another thin pipe must be configured to specify this 3-Gbps restriction.


Table 3-17 lists the thin pipe mappings that would be configured for the different Vault Groups illustrated in Figure 3-19.

 

Table 3-17 Thin Pipe Mappings for Thin Pipe Example

Thin Pipe Map
Remote Group
Bandwidth (Gbps)
Vault Group 1 (VG1)

VG1toAll

Vault Group 2, Cache Group 1, Cache Group 2, Cache Group 3

5

VG1toVG2

Vault Group 2

4

VG1toCG1

Cache Group 1

2

VG1toCG2

Cache Group 2

2

VG1toCG3

Cache Group 3

2

Vault Group 2 (VG2)

VG2toAll

Vault Group 1, Cache Group 1, Cache Group 2, Cache Group 3

4

VG2toCG1

Cache Group 1

2

VG2toCG2

Cache Group 2

2

VG2toCG3

Cache Group 3

2

Cache Group 1 (CG1)

CG1toAll

Vault Group 1, Vault Group 2, Cache Group 2, Cache Group 3

 

CG2toSG1

Stream Group 1

3

Cache Group 2 (CG2)

CG2toAll

Vault Group 1, Vault Group 2, Cache Group 1, Cache Group 3

2

Cache Group 3 (CG3)

CG3toAll

Vault Group 1, Vault Group 2, Cache Group 1, Cache Group 3

2

The thin pipes configured in Table 3-17 ensure that the bandwidth for Vault Group 1 never exceeds the maximum bandwidth available for Vault Group 1, which is 5 Gbps. This means that even if all remote groups were requesting cache fills from Vault Group 1, which would be a maximum throughput of 9 Gbps, the actual maximum bandwidth of cache-fill traffic coming from Vault Group 1 would never exceed 5 Gbps.

To configure a Thin Pipe Map, do the following:

Choose Configure > Array Level > Thin Pipe Map . The Thin Pipe Map page is displayed (Figure 3-20).

Figure 3-20 Thin Pipe Map Page

 

Step 5 From the Configured Pipes drop-down list, choose Create New Pipe and click Select .

To edit a Pipe Map, choose the Pipe Map from the drop-down list and click Select .

Step 6 From the Local Group drop-down list, choose the group you want to use as the local group for this thin pipe map.

Step 7 In the Pipe Name field, enter the name for the pipe map.

Step 8 In the Max Bandwidth field, enter the maximum megabits per second (Mbps) for this pipe.

The maximum bandwidth entered applies to each server in the group. For example, if the maximum bandwidth between two groups is designed as 5 Gbps (5000 Mbps) and there are two servers in each group, then the entered amount should be 2500 Mbps (5000 Mbps divided by the number of servers in the group).


Note The maximum bandwidth threshold is 75 percent of the Max Bandwidth field.


Step 9 In the Available Remote Groups area, check the check box next to each remote group that you want to use this maximum bandwidth restriction.

Step 10 Check the Limit HTTP check box if this thin pipe is to limit the bandwidth between Caching Nodes and Streamers in a VVI that uses HTTP as the caching protocol.

Step 11 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 Media Scheduler


NoteThe Media Scheduler page is part of the optional MediaX feature. The Media Scheduler page is part of the optional MediaX feature.


The Media Scheduler page allows you to schedule content for ingest and generate content metadata. The channels available in the Media Scheduler page are determined by the channels included in the uploaded EPG file and those configured on the Input Channels page. See the “Uploading an EPG File” section and the “Configuring Input Channels” section for more information.

The ingest time is calculated by adding the value of the ingest schedule start timeslot to the Publish Time Adjustment field from the Input Channels page.


NoteTo be able to schedule content, you must add the channels through the Input Channel page, and then either upload an EPG file to populate the cells in the Media Scheduler, or manually enter the metadata using the Media Scheduler Package Metadata window. To be able to schedule content, you must add the channels through the Input Channel page, and then either upload an EPG file to populate the cells in the Media Scheduler, or manually enter the metadata using the Media Scheduler Package Metadata window.


From the Media Scheduler page, you can perform the following tasks:

  • Choose the channels to schedule content ingest.
  • View the content metadata for each selected timeslot.
  • Schedule content to be ingested for a particular channel, provided all required ADI metadata values are available.
  • Add metadata values if they are not available, or modify the metadata values.
  • Resolve any conflicts in the EPG data.

The following procedure walks you through all these tasks.

User Preferences

To schedule content ingest and edit metadata information, do the following:


Step 1 Choose Configure > Array Level > Media Scheduler . The User Preferences for the Media Scheduler page is displayed (Figure 3-21).

Figure 3-21 Media Scheduler Page—User Preferences

 

Step 2 Choose either Hide On Return or Show On Return to display the user preferences each time you go to the Media Scheduler page.


Note You can change the user preferences at any time by clicking Edit Settings in the main Media Scheduler page or when the calendar is displayed. To have your settings recalled each time you log in to the CDSM, see the “Changing User Default Settings” section.


Step 3 For Action on Recurring Schedules , choose either Preserve Existing Schedules or Overwrite Existing Schedules . This option is only for user-generated schedules; this option is not for uploaded EPG data. For more information, see the “Package Metadata Editor” section.

Preserving Existing Schedules keeps any content that is currently scheduled for the day and channel you selected, and fills only the empty timeslots. Overwrite Existing Schedules overwrites any content that is currently scheduled for the day and channel you selected.

Step 4 When you schedule an event that originated from an uploaded EPG file, the Media Scheduler creates a package name combining the channel name, title brief, and the word “package.” For Package Name Auto-Generation, if the package name already exists and you want a new package name auto-generated, choose Enable and the start time is added to the package name. If the package name already exists and you want to create the package name using the Metadata Editor, choose Disable .

Step 5 Check the check boxes for the channels you want to schedule.


Note To create new channels, see the “Configuring Input Channels” section.


Step 6 Click Save to save the settings. The calendar is displayed (Figure 3-22).

Figure 3-22 Media Scheduler Page—Calendar

 

To clear the fields and start over, click Reset .


 

Scheduling Content for Ingest

To schedule content ingest and edit metadata information, do the following:


Step 1 Choose Configure > Array Level > Media Scheduler . If Hide On Return was selected in the User Preferences, the Media Scheduler calendar is displayed (Figure 3-22). If Show On Return was selected in the User Preferences, the User Preferences are displayed (Figure 3-21).

Step 2 From the calendar, click the day you want to schedule. If the month you are scheduling is not shown, use the left and right arrows on either side of the calendar to change the month.


Note Today’s date is displayed with a box around it.


The schedule for the day you selected is displayed (Figure 3-23).

Figure 3-23 Media Scheduler Page—Schedule

 

Depending on the status of the schedule, the schedule cells that contain data (programs) are displayed in different colors. When you first view the Media Scheduler page with uploaded EPG data, all the programs are in the “Not Scheduled” state. The Media Scheduler page displays a legend describing the different colors for the cells in the schedule.

Small timeslots are marked blue. To view the program information on small timeslots, click the timeslot. The page refreshes and the schedule for the small timeslot is displayed at the bottom of the page.


Tip To view information about a program, move the mouse pointer over a cell. A pop-up displays the program information (Figure 3-24).


Figure 3-24 Media Scheduler Page—Program Information

 

Step 3 Click each cell for each program you want to schedule.

If all the required information for metadata creation is available for the channel and the timeslot, the color of the cell changes to green, indicating that the timeslot is “Marked for Scheduling.”

If all the required information for metadata creation is not available, a new window opens and the Package Metadata Editor is displayed. See the “Package Metadata Editor” section.


Tip Alternatively, you can click the channel column heading to schedule all unscheduled events for that channel. If all required metadata information is available, this method automatically submits the changes and refreshes the page with all the timeslots marked “Scheduled.



Tip The Bulk Schedule option allows you to schedule the events for multiple channels at the same time. To schedule all channels or a group of channels for a whole day, click Bulk Schedule. The Bulk Schedule dialog box is displayed. Check the check box next to each channel and click Submit. If all required metadata information is available, this method schedules all the timeslots for the day. To check all the channels, check Select All. To uncheck all the channels, check Unselect All. The field alternates from Select All to Unselect All fields.



Note You can only schedule current and future timeslots. However, you can view past timeslots.


Step 4 Click Submit . The Media Scheduler page refreshes and all the “Marked for Scheduling” cells are changed to “Scheduled.”


Note Only current and future schedule entries can be edited.


To remove a scheduled ingest, click the scheduled timeslot. The timeslot changes from “Scheduled” to “Marked for Unscheduling.” Click Submit .


Tip You can mark timeslots for unscheduling and mark different timeslots for scheduling, and submit all the changes at one time.



 

Package Metadata Editor

The Package Metadata Editor allows you to edit or view existing metadata, or to enter new metadata for any future unused timeslot.

To use the Package Metadata Editor, do the following:


Step 1 To enter new metadata for any unused timeslot, click the unused timeslot. To edit existing metadata, double-click the scheduled timeslot. A new window opens and the Package Metadata Editor is displayed ( Figure 3-25).

Figure 3-25 Package Metadata Editor—User-Generated Timeslot

 

Metadata that originates from an EPG file is created using a combination of channel values (set in the Input Channels page) and data uploaded from the EPG file. If all the data is available, the metadata is generated, the content is scheduled for ingest, and the start time is set for publishing the content.

Step 2 For metadata created from user-generated schedules, there is an option for recurring schedules (Figure 3-26).

Figure 3-26 Recurring Schedule Options for User-Generated Schedules

 

Check the Recurring Schedules check box to copy the metadata information to the timeslots specified in the Recurring Schedule fields. See Table 3-18 for descriptions of the Recurring Schedule fields.

 

Table 3-18 Recurring Schedule Fields

Field
Option
Description

Recurrence Pattern

Daily

If Daily is selected, the metadata is copied to the same timeslot each day until the Recurrence End Time is reached.

Weekly

If Weekly is selected, the metadata is copied to the same timeslot on each day of the week selected (Sun, Mon, Tue, Wed, Thu, Fri, Sat) until the Recurrence End Time is reached.

Monthly

If Monthly is selected, the metadata is copied to the same timeslot on the week selected (1st, 2nd, 3rd, 4th, last) and day of the week selected (Sun, Mon, Tue, Wed, Thu, Fri, Sat) until the Recurrence End Time is reached.

Recurrence End Time

One year from start time

Recurrence Pattern is repeated for one year from the metadata Start Time.

End After

Recurrence Pattern is repeated the number of times you specify in the occurrences field.

End By

Recurrence Pattern is repeated until the date you specified in the End By field is reached.

Depending on the setting in the User Preferences settings, any existing metadata is preserved or overwritten. See the “User Preferences” section for more information.

Step 3 Fill in any missing information, or edit existing information, using the Package Metadata and click Submit .

For information on the fields displayed in the Package Metadata, see the CableLabs Video-On-Demand Content Specification Version 1.1 (MP-SP-VOD-CONTENT1.1-I03-040107) document at www.cablelabs.com .


 

Fixing Conflicts in the Media Scheduler

Conflicts can occur as a result of the following scenario:

  • Information was uploaded from an EPG file and the Media Scheduler is using this information. However, the schedule was modified.
  • The schedule information is updated with new entries for the same time and channel, but each entry has different content information.

To view these conflicts and schedule the latest information, do the following:


Step 1 Choose Configure > Array Level > Media Scheduler . The Media Scheduler page displays all the conflicts, including those events that have passed (Figure 3-27).

To go to the main Media Scheduler page, click Go To Scheduler .

Figure 3-27 Media Scheduler Page—Conflicts

 

Step 2 To fix a scheduling conflict, click the link for the record number. The Media Scheduler page refreshes and displays the channel of the selected conflict.

The timeslots that have conflicts are displayed with a brown color.

Step 3 To clear a conflict, click the timeslot. The timeslot gets the latest information and is displayed with the color green, indicating “Marked for Scheduling” if all the metadata information is available.

If all the required information for metadata creation is not available, a new window opens and the Package Metadata Editor is displayed (Figure 3-25). Fill in the metadata as required and click Submit . The Package Metadata Editor window closes.

Step 4 After all the conflicts have been cleared on the Media Scheduler page, click Submit to schedule all “Marked for Scheduling” timeslots.


 

Server Level Configuration

After a server has been initially configured (see the “Initially Configuring the Devices” section), the CDSM detects it and the IP address or nickname of the server is available for selection in the server drop-down lists.

The Server Level tab has the following configuration options:

Configuring the Interfaces

The Interface Setup page is used to configure the different interfaces on the CDS servers. The functionality of the Ethernet interfaces on the CDS servers is configurable. However, there is an optimal configuration for each server. The interface functions are described in Table 3-19 .

 

Table 3-19 CDS Interfaces

Type
Description

General

Reserves an Ethernet interface to allow optimal configuration.

Management

Communicates with other network devices with regards to condition of the server, stream control, and ISA communications.

Ingest

Establishes connectivity with a content provider system and to ingest content on to a Vault or an ISV.

Cache

Transports content between Vaults and Streamers, or in the case of VVI, between Vaults, Caching Nodes, and Streamers.

Stream/Cache

Used on the Streamer for both cache and streaming traffic. If an interface is configured for both cache and streaming traffic on a Streamer, priority with be given to the higher-bandwidth stream traffic provided cache traffic is able to transmit on other interfaces.

Stream

Transports streams to the QAM devices, or to subnets in the case of IPTV.

Stream Control

Transmits control messages between the STBs and the Streamers. Designating an interface as a stream control interface allows for the separation of stream control traffic from stream traffic. For more information about stream control, see the “Configuring the Control and Setup IPs” section. To configure a separate route subnet for stream control traffic, see the “Configuring the Route Table” section.

Locate

Used on the Caching Nodes to communicate with HTTP Streamers. One interface on the Caching Node must be set to Locate for HTTP Streamers. HTTP Streamers are supported only in a Virtual Video Infrastructure (VVI). For more information, see the “Caching Node Workflow” section.

For all CDE servers, the optimal configuration is:

  • eth0 as management
  • eth1 as ingest on Vaults and ISVs
  • All other interfaces are available for cache, stream, stream/cache, stream control, or locate, as appropriate for the server

To configure the interface settings, do the following:


Step 1 Choose Configure > Server Level > Interface Setup . The Interface Setup page is displayed (Figure 3-28).

Step 2 From the Server IP drop-down list, choose the IP address or nickname of the server and click Display .

Figure 3-28 Interface Setup Page—Vault Page

 

Step 3 Choose each interface setting as appropriate.

Step 4 Click Submit to save the settings.

To clear the fields and start over, click Reset .


 

Configuring the Servers

After a server has been initially configured, the CDSM detects it and the IP address or nickname of the server is available for selection in the server drop-down lists.

To configure the server settings, do the following:


Step 1 Choose Configure > Server Level > Server Setup . The Server Setup page is displayed.

Step 2 From the Server IP drop-down list, choose the IP address or nickname of the server and click Display .

Step 3 The fields differ for a Vault, Streamer, and ISV server. Figure 3-29 shows the Server Setup for a Vault. Figure 3-30 shows the Server Setup for a Streamer. The ISV server setup page has a combination of the Vault and Streamer fields. See Table 3-21 for descriptions of the fields and to which server they apply. The fields for the Caching Node setup page are described in Table 3-21 .

Table 3-20 lists the CDSM GUI ID names and maps them to the CServer names in the setupfile and .arroyorc files.

 

Table 3-20 ID Names in the CDSM GUI and CServer Files

CDSM GUI ID Name
CServer Files ID Name

Array ID on the Array Name page

groupid

Group ID on the Server-Level pages

groupid

Stream Group ID on the Server Setup page

arrayid

Cache Group ID on the Server Setup page

arrayid

Vault Group ID on the Server Setup page

arrayid

Stream Group ID on the Configuration Generator page

arrayid

Figure 3-29 Server Setup–Vault Server Page

 

Figure 3-30 Server Setup—Streamer Server Page

 

 

Table 3-21 Server Setup Fields

Field
Description
Server Type

Hostname

Fully qualified hostname for this server. The name can be up to 64 characters long. Assigning a hostname is optional.

The hostname must be fully qualified, for example: vault.cisco.com .

The DNS must be able to resolve the hostname to the IP address you select, with both forward and reverse lookups. If you enter a hostname that cannot be resolved, you may not be able to access the server.

All servers: Vault, Caching Node, Streamer, ISV

TTL

IP time to live (TTL) for data packets. The IP TTL default is 16 hops. Valid entries range from 0 to 255.

All servers

Null Streaming

From the Null Streaming drop-down list, choose Enabled to allow the streaming of null MPEG files, or Disabled to prevent the streaming of null MPEG files.

All servers

Default Stream/Cache Settings

Source IP

Default source IP address for all stream and cache interfaces. If the source IP address is left blank, the default of 192.168.207.65 is used.

All servers

Starting Transport Port

Beginning default UDP port number used for stream and stream/cache interfaces. If the starting transport port is left blank, the default of 48879 is used.

Streamer, ISV

Ending Transport Port

Ending default UDP port number used for stream and stream/cache interfaces. There is no default for the ending transport port number.

Streamer, ISV

Cache Port

Default UDP port number used for cache traffic between servers. If the cache port is left blank, the default of 48879 is used.

All servers

Ingest MPEG Settings

PID Standardization

This field is informational only. If this field is set to enable, then MPEG-2 video assets have their program identifiers (PIDs) standardized at ingest so that most assets use the same PIDs. To change the settings of the Ingest MPEG fields, see the “Configuring Ingest Tuning” section.

Vault

Sequence End Remove

This field is informational only. If this field is set to enable, a SEQ END header that is present at the end of the asset (and only at the end) is removed on ingest. To change the settings of the Ingest MPEG fields, see the “Configuring Ingest Tuning” section.

Vault

Rate Standardize

This field is informational only. If this field is set to enable, then MPEG-2 video assets have their rates standardized at ingest so that most assets use one of two standard rates, 3.75 Mbps for SD assets or 15 Mbps for HD assets. To change the settings of the Ingest MPEG fields, see the “Configuring Ingest Tuning” section.

Vault

Stream Group Information

Stream Group

Stream Group ID

These fields display the Stream Group and Stream Group ID the ISV or Streamer is a member of. The Stream Group and Stream Group ID are informational only. To configure Stream Groups, see the “Configuring Stream Groups” section.

Streamer, ISV

Streamer Is Cache

If Streamer Is Cache is enabled, the Streamer can be used as a possible cache-fill source by a Streamer in a different Stream Group. All Stream Groups that have at least one Streamer with Streamer is Cache enabled are displayed on the Stream to Cache Map page, where the Stream Group can be selected as a possible cache-fill source and given a preference. Only the Streamers with Streamer Is Cache enabled are used as possible cache-fill sources. The protocol used for cache-fill responses from Streamers is always CCP. For more information, see the “Mapping Stream Groups to Cache-Fill Sources” section.

Streamer

Cache Group Information

Cache Group

Cache Group ID

These fields display the Cache Group Name and Cache Group ID the Caching Node is a member of. The Cache Group Name is informational only. To configure Cache Groups, see the “Configuring Cache Groups” section.

Caching Node

Vault Group Information

Vault Group

Vault Group ID

These fields display the Vault Group Name and Vault Group ID the Vault is a member of. The Vault Group Name is informational only. To configure Vault Groups, see the “Configuring Vault Groups” section.

Vault

Jumbo Frames Support

Stream Jumbo Frames

By default, jumbo frames are disabled on stream interfaces. In this case, stream traffic adheres to standard frames, which have a maximum frame size of 1500 bytes.

If jumbo frames are enabled, you need to make sure that your switch is configured to support jumbo frames. The jumbo frame size must be set, at a minimum, to 8192 bytes.

Streamer, ISV

Cache Jumbo Frames

By default, jumbo frames are disabled on cache interfaces. In this case, cache traffic adheres to standard frames, which have a maximum frame size of 1500 bytes.

If jumbo frames are enabled, you need to make sure that your switch is configured to support jumbo frames to be able to communicate across the cache interfaces. The jumbo frame size must be set, at a minimum, to 8192 bytes.

All servers

Server Status

Server Offload

Server Offload shows the current offload status of the server. When Server Offload is enabled, the server is configured to reject new provisioning. Server offload is typically enabled when system maintenance needs to be performed, or when a server needs to be removed from service.

All servers

Vault Mirror Copies

Choose the number of copies from the drop-down list that ensures there is at least one copy of the content at each site. For example, if there are two different sites, each with two Vaults, set the Vault Mirror Copies to 3.

Vault, ISV

Vault Local Copies

From the drop-down list, choose the number of copies of content that are stored on this server.

Vault, ISV

Transport, Cache, and HTTP IP Packets

Transport Differentiated Services Code Point

–and–

Cache Differentiated Services Code Point

Differentiated Services Code Point (DSCP) uses six bits of the DiffServ field, which was originally the ToS octet, to mark all outgoing packets with a specific DSCP value. Cache or transport traffic may require certain forwarding behavior, known as the per-hop behavior (PHB), which is specified in the DSCP. The network gives priority to marked traffic. Generally, the lower number has lower priority and the higher number has higher priority. The valid entries are 0 to 63.

DSCP is set separately for cache and transport interfaces.

Note DSCP can also be set for HTTP Streamers when HTTP is selected as the cache-fill protocol for VVI on the CDSM Setup page.

All servers

Cache Priority

From the Cache Priority drop-down list, choose an AF class. For more information, see the “Configuring QoS Settings” section.

All servers

FTP Out Settings

FTP Out Interface

FTP out interface determines whether the management interface or the ingest interface is used for FTP pulls and FTP pushes. It is also used for the ISA 1.5 FTP Out feature.

Vault, ISV

FTP Out Bandwidth

Enter the maximum bandwidth (in Mbps) allowed for FTP functionality. Valid entries are 0 to 1000.

Vault, ISV

FTP Out Sessions

Enter the maximum number of FTP out sessions allowed. The range is from 1 to 10.

Vault, ISV

Management Interface

Management IP

IP address of the management interface on this server.

All servers

Gateway

IP address of the gateway to the network.

All servers

Subnet Mask

Subnet mask that defines the subnetwork for this server.

All servers

FTP Listener

Choose either the Management i nterface or the Ingest interface as the FTP listener. The FTP listener selected determines which interface is used for FTP pulls or FTP pushes.

Vault, ISV

Ingest Interface

Ingest IP

IP address of the ingest interface on this server. The ingest IP address is used to establish connectivity to the content provider system.

Vault, ISV

Ingest Subnet Mask

Subnet mask that defines the subnetwork for this interface.

Vault, ISV

Locate Interface

Locate Interface IP

IP address for this interface. The Locate Interface is used by the Locate Port service for communications with third-party streamers that use HTTP to communicate.

Caching Node

Locate Port

Port number used for communication with HTTP Streamers. CCP Streamers do not use the Locate Port; instead, they load-balance locate requests across fill sources. For more information on HTTP Streamers and CCP Streamers, see the “HTTP Streamers” section.

Caching Node

General Interface

IP

IP address for this interface.

All servers

Subnet Mask

Subnet mask that defines the subnetwork for this interface.

All servers

Stream/Cache Interface

Source IP

IP address for this interface. The IP address set for this interface overrides the default Source IP setting.

If you are using Layer 3 communication among Vaults, Caching Nodes, and Streamers, each cache or stream/cache interface must have an IP address.

If you are using Layer 2 communication among Vaults , Caching Nodes, and Streamers, IP addresses for cache and stream/cache interfaces are optional.

All servers

Transport Port

This setting applies only to stream or stream/cache interfaces. This is the UDP port number for stream traffic. The port number set for this interface overrides the default transport port setting.

Streamer, ISV

Cache Port

UDP port number for cache traffic. The port number set for this interface overrides the default cache port setting.

All servers

Stream Control Interface

Stream Control IP

IP address for this interface.

Streamer, ISV

Stream Control Subnet

Subnet mask that defines the subnetwork for this interface.

Streamer, ISV


Note The Auto Populate Source IPs button is available when the first applicable interface (for example, the first stream interface) is configured with an IP address. Clicking Auto Populate Source IPs automatically enters the next consecutive IP address as the Source IP for the next interface, and continues to populate all Source IPs until they are all filled. Any preexisting IP addresses in the Source IP fields are overwritten.



Note To configure an unconfigured interface, click the click here link. The Interface Setup page is displayed. Choose the setting for the interface you want to configure and then click Submit. The Server Setup page is displayed. Complete the interface configuration by filling in the fields as appropriate. See Table 3-21 for field descriptions.



Note The Streamer can have a maximum of 12 interfaces configured for stream traffic simultaneously, with a maximum of 12 interfaces configured for cache traffic, or any variation of the two (for example, 8 stream interfaces and 6 cache interfaces). If an interface is configured for both cache and streaming traffic on a Streamer, priority is given to the higher-bandwidth stream traffic provided that cache traffic is able to transmit on other interfaces.


Step 4 Click Submit to save the settings.

To clear the fields and start over, click Reset .


 

Configuring QoS Settings

There needs to be a dedicated Differentiated Services (DiffServ) Assured Forwarding (AF) class for the CCP traffic. The Assured Forwarding PHB guarantees a certain amount of bandwidth to an AF class and allows access to extra bandwidth, if available. There are four AF classes, AF1x through AF4x. Within each class, there are three drop probabilities (low, medium, and high).


NoteThe sum of all bandwidths configured for CCP traffic cannot exceed the bandwidth configured for the AF classes reserved for CCP. CCP is used as the protocol among Vaults and Caching Nodes in a VVI that uses HTTP, and among all servers in a VVI that uses CCP and in all non-VVIs. The sum of all bandwidths configured for CCP traffic cannot exceed the bandwidth configured for the AF classes reserved for CCP. CCP is used as the protocol among Vaults and Caching Nodes in a VVI that uses HTTP, and among all servers in a VVI that uses CCP and in all non-VVIs.


Table 3-22 lists the four AF classes and the data types for each drop probability. To set the AF class on each server, use the Cache Priority drop-down list in the Server Setup page.

 

Table 3-22 AF Class Drop Probability Configured on Each CDS Server

AF1x Class
AF2x Class
AF3x Class
AF4x Class
Data Types

AF11

AF21

AF31

AF41

The following data types are set to low drop probability:

  • Lost packet recovery for committed rate traffic (Vault or Caching Node or Streamer to Vault or Caching Node or Streamer)
  • High-priority lost packet recovery for committed rate traffic (Vault or Caching Node or Streamer to Vault or Caching Node or Streamer)
  • iGate and index file transmission (Vault or Caching Node to Streamer)
  • First part of mirror data going to a new Vault (Vault to Vault)
  • Control traffic

AF12

AF22

AF32

AF42

Committed rate traffic (Vault or Caching Node or Streamer to Vault or Caching Node or Streamer) is set for medium drop.

AF13

AF23

AF33

AF43

The following data types are set to high drop probability:

  • Remote smoothing traffic (Vault to Vault) and prefetched traffic (Vault to Caching Node to Streamer)
  • Mirroring traffic for creating additional mirrored copies (Vault to Vault)
  • Repair traffic that is recovering striped data lost because of a drive failure (Vault to Vault)
  • Mirroring of live ingest traffic (Vault to Vault)
  • Lost packet recovery of mirroring traffic (Vault to Vault)

Configuring the Route Table

In earlier releases, the Route Table included a section called “Network Information,” which had the default gateway and local network for cache traffic, and the default gateway and local network for stream traffic. The same default gateway and local network could be used for both stream and cache traffic. Interfaces were grouped into transport groups that could separate stream traffic to multiple transport networks. The transport mechanism did not work on cache-fill interfaces. The streaming network and cache-fill network were treated as distinct entities, which disallowed an interface to function as both a streaming interface and a cache-fill interface.

Release 2.1 introduced the ability to define multiple subnets on a server. Multiple subnets replace the transport group mechanism and applies equally to stream and cache-fill interfaces. With multiple subnets you have the ability to group interfaces into separate subnets. One of the uses for multiple subnets is to configure half of the interfaces on the server to connect to one switch or router, and the other half of the interfaces to connect to a different switch or router for redundancy. The Route Table page allows for multiple subnets for cache, stream, and stream/cache interfaces.

The Route Table page has three different route types:

  • CServer Source (written to the SubnetTable file)
  • CServer Destination (written to the RoutingTable file)
  • Stream Control (written to the Linux OS route table)

Each route type has a different function, and each route type is written to a different file on the CDS server.


NoteYou cannot have intersecting subnets for any defined routes for CServer Source or CServer Destination. You cannot have intersecting subnets for any defined routes for CServer Source or CServer Destination.


CServer Source Route Type

When CServer Source is selected from the Route Type drop-down list, a subnet is defined and written to the SubnetTable file. Subnets can only be defined for stream, cache, or stream/cache interfaces. Interfaces are defined on the Interface Setup page (Configuring the Interfaces), and IP addresses for the interfaces are set on the Server Setup page (Configuring the Servers). Figure 3-31 shows an example of interfaces configured for multiple subnets on a Streamer.

Figure 3-31 Subnet Configuration Example on Streamer

 

Table 3-23 shows the possible configuration settings to use to define the subnets described in Figure 3-31.

 

Table 3-23 Route Table Settings for CServer Source

Subnet
Network
Subnet Mask
Gateway
Route Type

Subnet 1

192.168.1.0

255.255.255.0

192.168.1.1

CServer Source

Subnet 2

192.168.2.0

255.255.255.0

192.168.2.1

CServer Source

The Route Table entry for the subnet is defined by a network and subnet mask, and also includes a default gateway. ARP is applied for any data packets that have a destination IP address within the defined subnet, and the MAC address is returned. Any data packets outside the subnet are sent to the default gateway.

CServer Destination Route Type

When CServer Destination is selected from the Route Type drop-down list, an alternate gateway for a destination subnet (based on the Network and Subnet Mask fields) is defined and written to the RoutingTable file. The alternate gateway is used whenever the destination IP address of the data packet falls within the destination subnet defined with the Route Type of CServer Destination .

Stream Control Route Type

When Stream Control is selected from the Route Type drop-down list, a subnet and default gateway is defined for all stream control traffic, and the information is written to the Linux OS routing table file. The Stream Control route type is available only when one of the interfaces is set to Stream Control in the Interface Setup page. See the “Configuring the Interfaces” section for more information. The Linux OS routing table file is also used to store route information for the ingest and management interfaces.


NoteAfter being upgraded to Release 2.1 or later, any servers with incompatible routes are listed in red in the drop-down list. You can review the Route Table configuration for each of these servers, modify or delete the routes, and click After being upgraded to Release 2.1 or later, any servers with incompatible routes are listed in red in the drop-down list. You can review the Route Table configuration for each of these servers, modify or delete the routes, and click Submit to apply the changes. The routes are converted to the Release 2.1 format and the server is listed in black. When all servers with incompatible routes are fixed, the warning message is removed and the entry in the system alarm drop-down list in the GUI banner is removed.


To configure a route, do the following:


Step 1 Choose Configure > Server Level > Route Tables . The Routing Table page is displayed (Figure 3-32).


Note If Bulk Configuration is enabled, the Configuration File Location field is displayed, along with the Browse and Import buttons. To import a Bulk Configuration XML file, click Browse to locate the file, then Import to import the file. The status of the import is displayed in the left panel.

For information on enabling the Bulk Configuration feature, see the “Bulk Configuration” section. For information about creating a Bulk Configuration file for QAM Gateways, see the “Creating Route Table Bulk Configuration Files” section.


Figure 3-32 Route Table Page—Layer 3 Network

 

Step 2 From the drop-down list, choose a server and click Display . Any configured routes are displayed.

Step 3 Enter the route settings as appropriate. See Table 3-24 for descriptions of the fields.

 

Table 3-24 Route Table Fields

Field
Description

Network

IP address of the network.

Subnet Mask

The subnet mask of the network.

Gateway

IP address of the next hop (primary datagram transmitter and receiver) along the route to the network.

Route Type

From the Route Type drop-down list, choose one of the following route types:

  • CServer Source —Used to configure a subnet and default gateway for a group of stream, cache, or stream/cache interfaces on this server.
  • CServer Destination —Used to configure a default gateway for a specified destination subnetwork. Typically this is used to configure the default gateway to reach the QAM devices.
  • Stream Control — Used when configuring a subnet route for the stream control traffic. This option is available only on Streamers, and is available only when one of the interfaces on the Streamer is configured as a Stream Control interface. See the “Configuring the Interfaces” section for more information.

Note For multiple SOPs used for NGOD RTSP deployments, you must choose CServer Source as the Route Type.

Step 4 Click Submit .

To reset the field, click Reset .


 

Configuring the SNMP Agent

The SNMP Agent sets up SNMP on the CDS. For more information about SNMP on the CDS, see Appendix C, “SNMP MIB and Trap Information.”

To configure the SNMP Agent settings for a new server, do the following:


Step 1 Choose Configure > Server Level > SNMP Agent . The SNMP Agent page is displayed (Figure 3-33).


Note If Bulk Configuration is enabled, the Configuration File Location field is displayed, along with the Browse and Import buttons. To import a Bulk Configuration XML file, click Browse to locate the file, then Import to import the file. The status of the import is displayed in the left panel.

For information on enabling the Bulk Configuration feature, see the “Bulk Configuration” section. For information about creating a Bulk Configuration file for QAM Gateways, see the “Creating SNMP Agent Bulk Configuration Files” section.


Figure 3-33 SNMP Agent Page

 

Step 2 Choose the IP address of the server from the drop-down list and click Display .

Step 3 Enter the settings as appropriate. The fields are described in Table 3-25 .

 

Table 3-25 SNMP Agent Fields

Field
Description

SNMP Contact

Specify a name used to identify the point of contact for this server. You may specify a name with up to 64 characters.

SNMP Location

Specify the location of the server. You may enter a name with up to 64 characters.

Community Name

Enter a community string that will have access to this server through SNMP.

Permissions

The permissions for the community are:

  • read-only
  • read/write

The default is read/write.

If you do not choose a permission setting for a community you are adding, read/write privileges are applied.

Trap Station

The IP address or Fully Qualified Domain Name (FQDN) of a network management station.

Version

The SNMP versions supported in the CDSM are:

  • v1
  • v2
  • v2-inform

SNMP v2-inform sends a message received to the NMS upon receiving an NMS message.

Note There is no default for the SNMP version. If you do not choose an SNMP version for a trap station you are adding, SNMP communication is not successful to that station.

Step 4 Click Submit to save the settings.

To clear the fields and start over, click Reset .

Step 5 To add another SNMP community or SNMP station, fill in the appropriate fields and click Submit .


 

To edit the SNMP information, choose the IP address of the server from the drop-down list, edit the fields, and click Submit .

The SNMP page allows for multiple entries of SNMP communities and stations. If you want to delete an SNMP community or station, check the Delete check box associated with the entry and click Submit .


NoteThe Cisco TV CDS MIBs are available for download at the bottom of the SNMP Agent page. The Cisco TV CDS MIBs are available for download at the bottom of the SNMP Agent page.


Configuring the Server Level DNS

The Server DNS page is used to up to 16 domain suffixes and 16 DNS servers.


NoteIf you are upgrading the TV CDS software to Release 2.2 from Release 2.0 or an earlier release, the system prompts you to If you are upgrading the TV CDS software to Release 2.2 from Release 2.0 or an earlier release, the system prompts you to Submit any settings that have previous domain suffixes to populate the new DNS database structure.


To configure the DNS settings for a server, do the following:


Step 1 Choose Configure > Server Level > Server DNS . The Server DNS page is displayed ( Figure 3-34).


Note If Bulk Configuration is enabled, the Configuration File Location field is displayed, along with the Browse and Import buttons. To import a Bulk Configuration XML file, click Browse to locate the file, then Import to import the file. The status of the import is displayed in the left panel.

For information on enabling the Bulk Configuration feature, see the “Bulk Configuration” section. For information about creating a Bulk Configuration file for QAM Gateways, see the “Creating DNS Server Bulk Configuration Files” section.


Figure 3-34 Server DNS Page

 

Step 2 Choose the IP address of the server from the drop-down list and click Display .

Step 3 Enter the DNS binding Server Level settings as appropriate. See Table 3-26 for descriptions of the DNS binding fields.

 

Table 3-26 DNS Binding Fields

Field
Description

New Domain Suffix

Specify, if applicable, the internal domain that is used to fully qualify an unqualified hostname. For example, if you are using OpenStream as the BMS, specify a subdomain consistent with what OpenStream is using, for example, bms.n2bb.com. Accordingly, unqualified hostnames used in CORBA transactions, such as contentstore, resolve correctly to contentstore.bms.n2bb.com.

New DNS Server

IP address of the DNS server.

Step 4 Click Submit .

To clear the fields and start over, click Reset .


 

To delete the DNS settings, check the Delete check box and click Delete Entry .

Configuring the Server Level NTP

The NTP Server page is used to configure up to 16 NTP servers. The clocks on all CDS servers (Vault, Streamer, and Caching Node) and the CDSM and VVIM in a CDS must be synchronized in order to retrieve the statistics on to the CDSM and VVIM.

To configure the NTP settings for a server, do the following:


Step 1 Choose Configure > Server Level > NTP Server . The NTP Server page is displayed.


Note If Bulk Configuration is enabled, the Configuration File Location field is displayed, along with the Browse and Import buttons. To import a Bulk Configuration XML file, click Browse to locate the file, then Import to import the file. The status of the import is displayed in the left panel.

For information on enabling the Bulk Configuration feature, see the “Bulk Configuration” section. For information about creating a Bulk Configuration file for QAM Gateways, see the “Creating NTP Server Bulk Configuration Files” section.


Step 2 Choose the IP address of the server from the drop-down list and click Display .

Step 3 In the New NTP Server field, enter the IP address of the NTP server.

Step 4 Click Submit .

To clear the fields and start over, click Reset .


 

To delete the NTP settings, check the Delete check box and click Delete Entry .

Other NTP Configurations

In addition to configuring the IP addresses of the NTP servers, you need to set the time zone on each CDS server, as well as configure the NTP servers for the CDSM and VVIM.

Setting the Time Zone on a CDS Server

To set the time zone on a CDS server, log in to the CDS server as root, and use the Linux link command to link the time zone to the /etc/localtime file.

The following are examples of the command used to set UTC and several different US time zones:

  • UTC option:
ln -sf /usr/share/zoneinfo/UTC /etc/localtime
 
  • EST option:
ln -sf /usr/share/zoneinfo/US/Eastern /etc/localtime
 
  • Central option:
ln -sf /usr/share/zoneinfo/US/Central /etc/localtime
 
  • Mountain option:
ln -sf /usr/share/zoneinfo/US/Mountain /etc/localtime
 
  • Pacific option:
ln -sf /usr/share/zoneinfo/US/Pacific /etc/localtime
 

Find the time zone for your specific location in the /usr/share/zoneinfo directory.

Configuring the NTP Server on the CDSM and VVIM

Configuring the NTP server on the CDSM or VVIM involves the following:

1. Adding the NTP servers to the /etc/ntp.conf file

2. Setting the run levels for the Network Time Protocol daemon (ntpd)

3. Setting the time zone

4. Setting the server date and time

5. Starting the NTP service

6. Synchronizing the server clock with the NTP server

7. Synchronizing the hardware clock on the server

Specific NTP configuration details should be obtained from your system administrator to add the NTP servers to the /etc/ntp.conf file.

To setup the NTP server on the CDSM or VVIM, do the following:


Step 1 Log in to the CDSM or VVIM as root.

Step 2 Set the run levels for the NTP service.

# chkconfig --level 2345 ntpd on
 

To check the run level settings, enter the following command:

# chkconfig --list ntpd
 

You will see the following:

ntpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
 

Step 3 Stop the ntpd service.

# service ntpd stop
 

Step 4 Set the time zone by linking the time zone to the /etc/localtime file. The following command shows an example of setting the time zone to UTC.

# ln -sf /usr/share/zoneinfo/UTC /etc/localtime
 

Find the time zone for your specific location in the /usr/share/zoneinfo directory.

Step 5 Set the system date and time to a date and time close to the NTP server date and time by entering the date -s command, for example:

# date -s "16:55:30 Nov 7, 2010"
 

Step 6 Synchronize the server clock to the NTP server.

# ntpd -q
 

Note If the system clock is off by a significant amount, the command takes a considerable amount of time to return.


Step 7 Start the ntpd service.

# service ntpd start
 

Step 8 Synchronize the hardware clock.

# /sbin/hwclock --systohc
 

Step 9 Check the NTP synchronization.

# ntpq -p
 

Step 10 Reboot the CDSM or VVIM.

# init 6
 


 

Configuring RTSP Setup

Real Time Streaming Protocol (RTSP) setup involves different parameters based on the RTSP deployment that was specified during the initial installation of the CDS. Table 3-27 describes each type of deployment.

 

Table 3-27 RTSP Deployment

Environment
RTSP Deployment Configuration
Description

Motorola

RTSP

Streamer acts as the RTSP client and the backoffice acts as the RTSP server.

IPTV

IPTV

IPTV uses multicasting with Internet Group Management Protocol (IGMP) version 2 for live television broadcasts and RTSP for on-demand programs.

Scientific Atlanta

DSM-CC

Streamer acts as the RTSP server and the backoffice acts as the RTSP client.

NGOD (Motorola)

NGOD

The Next Generation On Demand (NGOD) approach uses DSM-CC messaging in a Motorola environment.

Quative

Quative

The STB communicates with the backoffice to create a VOD session. Upon completion, the STB creates an RTSP session with the Streamers. The Streamer acts as an RTSP server and is responsible for accepting the request from the STB.

EventIS

EventIS

The STB communicates with the backoffice to initiate a purchase transaction and generate an entitlement ID. The STB then initiates an RTSP session with the Streamer. The Streamer authenticates the entitlement ID with the backoffice and allocates stream resources.

The Eventis deployment with “on vpath” is selected when both session and stream control messages go directly to the RTSP server from the STB. The EventIS deployment with “off vpath” is selected when control messages go through the backoffice before reaching the RTSP server, while the stream control messages go directly to the RTSP server.

Cable and IPTV

Cisco

Cisco RTSP defined protocol that supports both IPTV and cable STBs. Uses “on vpath” communication.

RTSP Deployment

To configure the RTSP settings, do the following:


Step 1 Choose Configure > Server Level > RTSP Setup . The RTSP Setup page is displayed.


Note If Bulk Configuration is enabled, the Configuration File Location field is displayed, along with the Browse and Import buttons. To import a Bulk Configuration XML file, click Browse to locate the file, then Import to import the file. The status of the import is displayed in the left panel.

For information on enabling the Bulk Configuration feature, see the “Bulk Configuration” section. For information about creating a Bulk Configuration file for QAM Gateways, see the “Creating RTSP Setup Bulk Configuration Files” section.


Step 2 From the Streamer Select drop-down list, choose a Streamer IP address and click Display . The RTSP settings for the specified server are displayed (Figure 3-35).

Figure 3-35 RTSP Setup Page for RTSP Deployment

 

Step 3 Enter the RTSP settings as appropriate. Table 3-28 describes each field and lists the associated RTSP deployment.

 

Table 3-28 RTSP Fields for All Deployment

Field
Description
RTSP Deployment

Master Streaming IP

Informational only. The IP address of the master Streamer. To configure the Master Streaming IP address, see the Configuring the Control and Setup IPs.

All

Looping Session Timeout

Activity timeout value for looping streams (carousels). If a GET_PARAMETER request (heartbeat) is received from the backoffice within the specified timeout period, the looping session remains active. If not, the looping session is torn down.

The default is 240000 milliseconds (4 minutes).

RTSP

Session Inactivity Timeout

Timeout value for tearing down a session. The default is 360000 milliseconds (6 minutes). If the Session Inactivity Timeout is set to zero (0), the session liveness is not checked.

RTSP, NGOD, IPTV, Quative, EventIS, Cisco

Callback Server IP

IP address of the callback server. The CDS sends announce messages to the callback server whenever an RTSP session is torn down and released by the RTSP server. Announce messages are sent for both normal (STB initiated) and abnormal (timeout) terminations.

Quative

Callback Server Port

UDP port number of the callback server.

Quative

Backoffice Timeout

Timeout value for closing a connection to the backoffice. If a message is not received from the backoffice within the time specified in the Backoffice Timeout, the TCP connection is closed. Setting the Backoffice Timeout to zero (0) is the same as disabling it and the connection is not closed.

DSM-CC, RTSP, NGOD, Quative, Cisco

RTSP Server IP

IP address of the server that communicates with this Streamer using RTSP.

DSM-CC, RTSP, NGOD, Quative

RTSP Server Port

TCP port number the RTSP server is listening on for communication with this Streamer.

DSM-CC, RTSP, NGOD, Quative

Authentication Manager IP3

Authentication Manager resides on the master Streamer. Typically, the Authentication Manager IP address is the same as that of the master Streamer. This field is only informational. To modify this field, see the “Configuring the Authentication Manager” section.

EventIS, Cisco

Authentication Manager Port 1

Authentication Manager port number is determined by the properties specifications of the Authentication Manager. If you need to change the port number, contact Cisco technical support. This field is only informational. If you must modify this field, see the “Configuring the Authentication Manager” section. The default is 7792.

EventIS, Cisco

Bandwidth Manager IP 1

Bandwidth Manager resides on the master Streamer. Typically, the Bandwidth Manager IP address is the same as that of the master Streamer. If the Bandwidth Manager IP address is set on the Bandwidth Manager page, then this field is only informational and if you must modify this field, see the “Configuring the Bandwidth Manager” section. If the Bandwidth Manager IP address on the Bandwidth Manager page is set to an asterisk (*) or 0.0.0.0, then you must enter the IP address for the Bandwidth Manager in this field for each Streamer.

EventIS on vpath

Bandwidth Manager Port 1

Bandwidth Manager port number default is 7791. This port number is determined by the configuration settings in the Bandwidth Manager. If the Bandwidth Manager IP address is set on the Bandwidth Manager page, then this field is only informational and if you must modify this field, see the “Configuring the Bandwidth Manager” section. If the Bandwidth Manager IP address on the Bandwidth Manager page is set to an asterisk (*) or 0.0.0.0, then you must enter the port number for the Bandwidth Manager in this field for each Streamer.

EventIS on vpath

Backup Bandwidth Manager IP 1

IP address of the network interface card (NIC) you want the Bandwidth Manager to bind to in case the primary Bandwidth Manager IP and port fail.

EventIS on vpath

Backup Bandwidth Manager Port 1

Port number to listen on for incoming connections from the RTSP server. The default is 7791. The minimum port number you can allocate is 150. The maximum port number is 60000.

EventIS on vpath

Session Resource Manager IP (or Server IP)

IP address used by the backoffice or Session Resource Manager (SRM) for communication of session control requests to the CDS RTSP server.

EventIS off vpath, Cisco

Session Resource Manager Port (or Server Port)

Port number used by the backoffice or SRM for communication of session control requests to the CDS RTSP server.

EventIS off vpath, Cisco

Backup Session Resource Manager IP

IP address of the network interface card (NIC) you want the SRM to bind to in case the primary SRM IP and port fail.

Cisco

Backup Session Resource Manager Port

Port number you want the SRM to use in case the primary SRM IP and port fail.

Cisco

Stream Control IP

IP address used by the STB for communication of trick-mode requests to the CDS RTSP server. This does not have to be the same IP address as the Control IP.

EventIS off vpath

Stream Control Port

Port number used by the STB for communication of trick-mode requests to the CDS RTSP server.

EventIS off vpath

Reconnect IP

Only for nABLE Motorola environments. The IP address on the Streamer used to receive the requests to reconnect to the backoffice server. After a connection has been established with the backoffice for RTSP communication, sometimes the backoffice sends a request to reconnect.

RTSP

Reconnect Port

Only for nABLE Motorola environments. The TCP port number on the Streamer used to receive the requests to reconnect.

RTSP

LSCP Listener IP

IP address on the Streamer used to receive LSCP requests.

DSM-CC, NGOD

LSCP Listener Port

TCP port number on the Streamer that is listening for LSCP commands from the set-top box. The default is 9000.

DSM-CC, NGOD

LSCP Response Pad

When LSCP Response Padding is enabled, three blank bytes are added to the end of the LSCP response. The default is disabled.

DSM-CC, NGOD

Component Name

Component name is the name of the master Streamer that is registered with the DNS server. This is a critical communication component and must match the table entry in the DNS server.

NGOD

Max History

Number of transactions (trick mode, play, pause) to maintain before sending the RTSP log message to the backoffice. If set to zero (0), the log message is not generated and the history is not returned upon session teardown.

RTSP

Log Level

From the Log Level drop-down list, choose one of the following:

  • Off—Logging is turned off.
  • Low—Logging messages are minimal in length (for example, RTSP message received).
  • High—Logging messages include all information concerning the event (for example, RTSP message with all syntax of the message).

All

Maintenance Mode

From the Maintenance Mode drop-down list, choose one of the following:

  • On—All current sessions continue until they are finished and all new SETUP requests receive a “Service Unavailable” response.
  • Off—The Streamer is available for new sessions and continues streaming current sessions.

All