4 Configuring the VDS

4 Configuring the VDS
CH A P T E R
4
Configuring the VDS
This chapter provides information on configuring the VDS servers. The topics covered in this chapter
include:
Note
•
System Level Configuration, page 4-1
•
Array Level Configuration, page 4-32
•
Server Level Configuration, page 4-65
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
Virtual Video Infrastructure, page F-8.
System Level Configuration
The System Level tab has the following configuration options:
•
Configuring System Level DNS Services
•
Configuring System Level NTP Services
•
Configuring the Hosts Service
•
Configuring the Array Name
•
Configuring QAM Gateways
•
Configuring the Headend Setup
•
Configuring Stream Destinations
•
Configuring the Ingest Manager
•
Configuring the Authentication Manager
•
Configuring Ingest Tuning
•
Configuring MPEG Tuning
•
Configuring Shared Recorder Settings
•
Configuring IP Nicknames
Cisco VDS-VR 4.1 Software Configuration Guide
4-1
Chapter 4
Configuring the VDS
System Level Configuration
Note
•
Configuring the Media Importer
•
Configuring Call Signs
•
Configuring Input Channels
•
Configuring Source Output Ports
•
Configuring the System Level Logging
•
Configuring the System Level Syslog
•
Configuring System Level Error Repair
The System Level configuration settings are distributed to all arrays and servers in the VDS.
Configuring System Level 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.
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 4-1 for descriptions of the fields.
Table 4-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
Step 3
IP address of the DNS server.
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.
Cisco VDS-VR 4.1 Software Configuration Guide
4-2
Chapter 4
Configuring the VDS
System Level Configuration
Configuring System Level NTP Services
The System NTP Server page is used to configure up to 16 NTP servers. The clocks on all VDS servers
(Vault, Streamer, and Caching Node) and the CDSM and VVIM in a VDS 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 VDS server or configuring NTP on a CDSM or VVIM, see
Other NTP Configurations, page 4-86.
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 > System Level > 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 > System Level > Host Service. The Host Service page is displayed.
Step 2
Enter the host service settings as appropriate. See Table 4-2 for descriptions of the fields.
Table 4-2
Step 3
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.
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.
Cisco VDS-VR 4.1 Software Configuration Guide
4-3
Chapter 4
Configuring the VDS
System Level Configuration
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 Content Delivery System Architecture, page 1-14.
Note
Currently, the CDSM allows only for the creation of one Vault array.
To view the current Array Name listings, Choose Configure > System Level > Array Name. The array
names currently configured are listed.
To configure an array name setting, do the following:
Step 1
Choose Configure > System Level > 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.
Note
The QAM Gateway page is not available if the Stream Destination is set to IPTV. For more information,
see Stream Destination, page F-3.
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.
Note
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 VDS 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.
Cisco VDS-VR 4.1 Software Configuration Guide
4-4
Chapter 4
Configuring the VDS
System Level Configuration
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.
Note
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 Configuring
the Route Table, page 4-78.
To view the current configuration for a QAM gateway, Choose Configure > System Level > 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 > System Level > QAM Gateway. The QAM Gateway page is
displayed(Figure 4-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 Bulk Import/Export
Configuration, page F-4. For information about creating a Bulk Configuration file for QAM
Gateways, see Creating QAM Gateway Bulk Configuration Files, page B-6.
Step 2
From the drop-down list, choose enter new and click Next.
Cisco VDS-VR 4.1 Software Configuration Guide
4-5
Chapter 4
Configuring the VDS
System Level Configuration
Figure 4-1
Step 3
QAM Gateway Page
Enter the QAM gateway settings as appropriate. See Table 4-3 for descriptions of the fields.
Table 4-3
QAM Gateway Fields
Field
Description
QAM Subnet
To enter QAM subnet, check the QAM Subnet check box
QAM
IP/QAM
Subnet IP
IP address of the QAM gateway or Subnet IP address of the QAM gateway if QAM
Subnet check box is selected
Subnet Mask
Subnet Mask of the QAM gateway
Cisco VDS-VR 4.1 Software Configuration Guide
4-6
Chapter 4
Configuring the VDS
System Level Configuration
Table 4-3
QAM Gateway Fields (continued)
Field
Description
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
Configuring the Route Table, page 4-78.
Stream Group Choose the preference for each Stream Group. The preferences are:
Preferences
• 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 Configuring Stream Groups,
page 4-34.
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.
Note
The Headend Setup page is not available if the Stream Destination is set to IPTV. For more information,
see Stream Destination, page F-3.
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.
Note
The Headend Setup page is displayed only if the Service Group Steering feature is enabled. For more
information, see Service Group Steering, page F-15
Note
You must first configure the Stream Groups before you can configure the headend setup for a specific
service group. See Configuring Stream Groups, page 4-34.
Cisco VDS-VR 4.1 Software Configuration Guide
4-7
Chapter 4
Configuring the VDS
System Level Configuration
To configure the headend setup, do the following:
Step 1
Choose Configure > System Level > Headend Setup. The Headend Setup page is displayed
(Figure 4-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 Bulk Import/Export
Configuration, page F-4. For information about creating a Bulk Configuration file for QAM
Gateways, see Creating Headend Setup Bulk Configuration Files, page B-7.
Figure 4-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 Configuring Stream Groups, page 4-34.
Step 5
Click Submit.
To delete a service group, choose it from the Select Service Group drop-down list and click Delete.
Cisco VDS-VR 4.1 Software Configuration Guide
4-8
Chapter 4
Configuring the VDS
System Level Configuration
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.
Note
The Stream Destination page is not available if the Stream Destination is set to Cable. For more
information, see Stream Destination, page F-3.
To configure the Stream Destination, do the following:
Step 1
Choose Configure > System Level > Stream Destination. The Stream Destination page is displayed
(Figure 4-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 Bulk Import/Export
Configuration, page F-4. For information about creating a Bulk Configuration file for QAM
Gateways, see Creating Stream Destination Bulk Configuration Files, page B-8.
Step 2
From the Subnet drop-down list, choose enter new.
To edit a subnet, choose the subnet from the Subnet drop-down list.
Cisco VDS-VR 4.1 Software Configuration Guide
4-9
Chapter 4
Configuring the VDS
System Level Configuration
Figure 4-3
Step 3
Enter the subnet address and subnet mask and click Submit.
Note
Step 4
Stream Destination Page
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.
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 VDS 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 Configuring Stream Groups, page 4-34.
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.
Cisco VDS-VR 4.1 Software Configuration Guide
4-10
Chapter 4
Configuring the VDS
System Level Configuration
Configuring the Ingest Manager
The Ingest Manager takes care of provisioned content objects by collecting the metadata and sending
messages to the appropriate subsystem to ingest the content. When the content expiration period has
ended, the Ingest Manager deletes the content after the additional license window has expired. The
additional license window is the license window end time plus the Additional Package Window.
Note
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 Ingest Manager, page F-14.
To configure the Ingest Manager, do the following:
Step 1
Choose Configure > System Level > Ingest Manager. The Ingest Manager page is displayed.
Step 2
Enter the Ingest Manager settings as appropriate. See Table 4-4 for descriptions of the fields.
Table 4-4
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.
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.
For Media Scheduler, Use Asset ID must be No; otherwise, the recording does
not succeed.
Manage CORBA
Services
ISA only field. Choose Yes to have the VDS manage the CORBA services,
otherwise choose No.
Require Notify
Service
ISA only field. Choose Yes to have the VDS require the use of the Notify
Service, otherwise choose No.
Meta Data Publish
Choose Enable from the drop-down list to publish the content metadata,
otherwise choose Disable.
Meta Publish URL #1
URL is typically the FTP server on CDSM itself. The example for this FTP
server to publish packages by Ingest Manager is:
ftp://aimmgr:aim123@192.168.16.25:21/.
Meta Publish URL #2
URL of the backup server where the metadata is published.
Cisco VDS-VR 4.1 Software Configuration Guide
4-11
Chapter 4
Configuring the VDS
System Level Configuration
Table 4-4
Ingest Manager Fields (continued)
Field
Description
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.
Cisco VDS-VR 4.1 Software Configuration Guide
4-12
Chapter 4
Configuring the VDS
System Level Configuration
Table 4-4
Ingest Manager Fields (continued)
Field
Description
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
Configuring Input Channels, page 4-26 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
Step 3
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.
Click Submit.
To clear the settings, click Reset.
Cisco VDS-VR 4.1 Software Configuration Guide
4-13
Chapter 4
Configuring the VDS
System Level Configuration
Configuring the Authentication Manager
Note
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 Authentication Manager, page F-14.
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 VDS, 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 VDS. The VDS 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 VDS returns an error status to the STB.
To configure the Authentication Manager, do the following:
Step 1
Choose Configure > System Level > Authentication Manager. The Authentication Manager page is
displayed (Figure 4-4).
Note
Depending on the Authentication Manager protocol selected (either Cisco or EventIS), the
Authentication Manager displays different fields.
Figure 4-4
Step 2
Authentication Manager Page—Cisco
Enter the Authentication Manager settings as appropriate. See Table 4-5 for descriptions of the fields.
Cisco VDS-VR 4.1 Software Configuration Guide
4-14
Chapter 4
Configuring the VDS
System Level Configuration
Table 4-5
Authentication Manager Fields
Field
Description
Protocol
Authentication
Manager IP1
Authentication Manager resides on the master Streamer. Typically, EventIS
the Authentication Manager IP address is the same as that of the
Cisco
master Streamer.
Authentication
Manager Port1
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
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 authentication server Cisco
in the following format: http://<ip_address>:<port><path>, which
is used to receive authentication requests (such as
IsAuthorizedRequest, SETUP and TEARDOWN
SessionNotification).
Authentication
Timeout
Time to wait, in seconds, for the authentication server to respond. EventIS
The range is from 1 to 10.
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
Cisco
1. Changes to this field affect the same field on the RTSP Setup page.
Step 3
Click Submit.
Configuring Ingest Tuning
The Ingest Tuning page allows you to set the speeds of the trick-mode files created for each ingested
content and configure the ingest error detection settings in the Fail Ingest Settings section.
For NGOD deployments, if Dynamic Trickmodes is enabled on the MPEG Tuning page, then the Ingest
Tuning page displays on the Stream Manager and is used to set the trick-mode speeds that the Streamer
uses to generate trick-mode files.
Note
The Fail Ingest Settings section is only displayed if the Fail Ingest Tuning feature is enabled. The Fail
Ingest Tuning feature is enabled by default. For more information, see Fail Ingest Tuning, page F-5.
To view the current ingest tuning settings, choose Configure > System Level > Ingest Tuning.
To configure the ingest tuning, do the following:
Step 1
Choose Configure > System Level > Ingest Tuning. The Ingest Tuning page is displayed.
Step 2
Enter the ingest tuning settings as appropriate. See Table 4-6 for descriptions of the fields.
Cisco VDS-VR 4.1 Software Configuration Guide
4-15
Chapter 4
Configuring the VDS
System Level Configuration
Table 4-6
Ingest Tuning Fields
Field
Description
Trick-Mode Settings
Speed 1–Speed
10
You can set ten 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.
To reset the values and start over, click Reset.
Fail Ingest Settings
PSI Errors
When program specific information (PSI) errors setting is enabled and the VDS
software cannot find the PAT and PMT, the ingest fails. The default for PSI Errors
is Disabled.
Bit Rate Errors
If Bit Rate Errors is enabled, and the VDS cannot determine the bit rate, cannot
find the Program Clock Reference (PCR), or determine the PCR PID; the ingest
fails.
If the VDS software cannot determine the bit rate, it tries the bit rate of 3.75 Mbps,
which may be correct and allows the ingest to continue.
This parameter is not applicable when using the nABLE backoffice.
The default setting is Disabled.
Error Count
Method
If Error Count Method is enabled, the errors are counted every n minutes, where
n is specified in the Number of Minutes field. The error count applies to the
following thresholds:
•
Discontinuity Rate
•
Number of Picture Gaps
•
Picture Gap Duration
•
Continuity Counter Errors
•
Number of Sync Loss Errors
•
Sync Loss Duration.
If a threshold is reached, the ingest fails. The default setting is Disabled.
Number of
Minutes
Number of Minutes applies to the Error Count Method. The default setting is 30.
If a threshold is reached within the specified minutes, the ingest fails.
Discontinuity
Rate
Discontinuity Rate threshold sets the number of discontinuities that constitutes a
failure. Discontinuities may appear if content is spliced together before ingest, also
many discontinuities appear near the beginning of a sample; therefore, the default
setting is Ignore.
Number of
Picture Gaps
Picture gap is when two pictures appear more than one second apart in a transport
stream. The Number of Picture Gaps threshold sets the number of picture gaps that
constitutes a failure. The default is 3.
Cisco VDS-VR 4.1 Software Configuration Guide
4-16
Chapter 4
Configuring the VDS
System Level Configuration
Table 4-6
Ingest Tuning Fields (continued)
Field
Description
Picture Gap
Duration
Picture Gap Duration allows you to specify the maximum time that defines a
picture gap. A picture gap occurs whenever two pictures are more than one second
apart. Even if they are 15 minutes apart, it is still only counted as one picture gap.
If a picture gap exceeds the Picture Gap Duration, the ingest fails. The default is
5 seconds.
Continuity
Counter Errors
Sets the Continuity Counter Errors threshold. The default is Ignore.
Each transport-stream packet header has a 4-bit continuity counter, which
increments for each transport-stream packet with the same PID. The continuity
counter wraps around to zero when it reaches its maximum value of F
(hexadecimal). It is used to determine if any packets are lost, repeated, or out of
sequence. The MPEG-2 specification allows the continuity counter to be
discontinuous in order to accommodate local insertion of data packets and splicing.
As a consequence, the continuity counter can be discontinuous even in an error-free
transmission.
Click Submit.
Step 3
To clear the fields and start over, click Reset.
Configuring MPEG Tuning
The MPEG Tuning page allows you to configure the settings for various aspects of MPEG tuning.
To view the current settings, choose Configure > System Level > MPEG Tuning.
To configure the settings, do the following:
Step 1
Choose Configure > System Level > MPEG Tuning. The MPEG Tuning page is displayed.
Step 2
Enter the settings as appropriate. See Table 4-7 for descriptions of the fields.
Table 4-7
Field
MPEG Tuning Fields
Description
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.
Cisco VDS-VR 4.1 Software Configuration Guide
4-17
Chapter 4
Configuring the VDS
System Level Configuration
Table 4-7
MPEG Tuning Fields (continued)
Field
Description
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 screen 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.
MPEG File Index Format
MPEG Index
Format
From the drop-down list, choose NGOD or ATIS.
NGOD — NextGen On Demand index format.
ATIS — Alliance for Telecommunications Industry Solutions index format.
Playlist Trick-Mode Restrictions
Rewind Skip
When Rewind Skip is enabled, if a rewind trick-mode command is issued and a rewind-restricted segment
is encountered, it is skipped and rewinding continues on the next segment.
When Rewind Skip is disabled (default setting), if a rewind trick-mode command is issued and a
rewind-restricted segment is encountered from an unrestricted segment, the rewinding stops and the
unrestricted segment is played at normal play speed.
As an example, Segment 2 is unrestricted and Segment 1 has the rewind trick-mode speed restricted. If a
rewind command is issued during the playing of Segment 2, rewinding of Segment 2 occurs until the end
of Segment 1 is encountered where the rewind trick-mode is restricted. Rewinding stops and the
unrestricted Segment 2 begins to play at normal speed.
Forward Jump
If forward-trick restrictions are enabled AND forward-jump restrictions are enabled, forward jumps will
be disallowed if the jump begins on an forward-trick-restricted playlist segment.
Cisco VDS-VR 4.1 Software Configuration Guide
4-18
Chapter 4
Configuring the VDS
System Level Configuration
Table 4-7
MPEG Tuning Fields (continued)
Field
Description
Skipping Stone
Mode
If forward-jump restrictions are enabled, the Skipping-Stone Mode parameter controls the behavior of
forward-jump restrictions when the jump begins in an unrestricted playlist segment, but there is one or
more forward-trick-restricted playlist segments between the beginning and end of the jump.
When Skipping-Stone Mode is enabled, the jump will skip to the beginning of an intervening
forward-trick-restricted playlist segment, switch to 1x playback for the duration of the segment, and jump
to the jump's original end or the beginning of the next forward-trick-restricted segment, whichever comes
first.
When Skipping Stone Mode is disabled, a jump will switch to 1x playback at the beginning of the first
intervening forward-restricted segment and will remain at 1x until a new play command is received.
Cache to Application Settings
Library Timeout A network partition could cause the Setup server to wait forever for the remote Stream Groups to respond
to the application for setup requests. The Library Timeout sets the time interval (in microseconds) that the
SetStreamInfo API should wait before considering the remote Stream Group unavailable.
The range is from 1000 to 5000. The default is 2000 (2 seconds).
Dynamic Trick Modes
Dynamic
Trickmodes
Select Enabled to enable trick-mode file generation for DVR content. For more information, see nDVR
Support for NGOD Deployments, page 2-13.
If Streamers are found that have a current Dynamic Trickmode value that is different than the value on the
MPEG Tuning page, an alert is displayed in the sidebar indicating the issue and listing the Streamer IP
addresses or host names.
Playlist Range Conversion Mode
Conversion
Mode
Select Based on Display Order to use the PTS values for mid-roll placement of advertisements. Select
Based on File Order to use the file offsets for mid-roll placement of advertisements. For more information,
see Mid-Roll Advertisement Placement Accuracy, page 1-6.
Step 3
Click Submit.
To clear the fields and start over, click Reset.
Configuring Shared Recorder Settings
The Shared Recorder Settings page is used to configure the Recorders in an nDVR system. For more
information, see nDVR Support for NGOD Deployments, page 2-13.
The settings on the Shared Recorder Settings page are applied to all Recorders in the VDS. The Shared
Recorder Settings page is used to configure large numbers of Recorders quickly and with less errors than
manual configuration. Individual settings made on the Recorder Setup page override any Shared
Recorder Settings.
Any changes to the Shared Recorder Settings page are propagated to all Recorders, except the settings
of Recorders that have individual settings. Any Recorder settings that were modified with the Recorder
Setup page (that is, different settings than the Shared Recorder Settings page) are not overwritten by the
Shared Recorder Settings page.
Cisco VDS-VR 4.1 Software Configuration Guide
4-19
Chapter 4
Configuring the VDS
System Level Configuration
Note
All configuration changes to the Recorder requires the Recorder be restarted. To restart the Recorder,
log in to Linux operating system of the Recorder, shut down the database (the db_shutdown command)
and enter the reboot command.
To configure the shared Recorder settings, do the following:
Step 1
Login to the CDSM GUI, and choose Configure > System Level > Shared Recorder Settings. The
Shared Recorder Settings page is displayed.
Step 2
Enter the settings as appropriate. See Table 4-8 for descriptions of the fields.
Table 4-8
Shared Recorder Settings Fields
Field
Description
General Recorder Settings
Recorder Manager
IP address of the Recorder Manager. The Recorder Manager port is port
number 80.
Retry Status Attempts
The number of times the Recorder tries to send undelivered or
unprocessed status messages to the Recorder Manager. A status
message is undelivered if the Recorder cannot connect to the Recorder
Manager. A status message is unprocessed if the Recorder Manager
responds with a HTTP 500 status.
This field can have a value in the range 0 through 100. A value of 0
disables the retry status message delivery feature.
The default value for this field is 3.
Retry Status Interval
The time in seconds between successive attempts by the Recorder to
send undelivered or unprocessed status messages to the Recorder
Manager.
This field can have a value in the range 60 through 3600 seconds.
The default value for this field is 60 seconds.
Recording Validation Age
When it receives a validation request, the Recorder lists the COIDs of
all recordings older than the value of this field for validation by the
Recorder Manager.
The value of this field must be specified as a number of days. The value
must be in the range of 1 through 10 days.
The default value of this field is 3 days.
NTP Server
IP address of NTP server.
Heartbeat Interval
Amount of time (in seconds) to wait between sending heartbeat
messages to the Recorder Manager. The range is from 2 to 30. The
default is 5.
Recorder Location
Name of the location of the Recorder. The name can be from 1 to 128
characters in length.
Cisco VDS-VR 4.1 Software Configuration Guide
4-20
Chapter 4
Configuring the VDS
System Level Configuration
Table 4-8
Shared Recorder Settings Fields (continued)
Field
Description
Recording Modify
Time window (in seconds) before a recording starts in which an operator
cannot modify recording parameters. The end time can be modified even
after the configured time window has passed. If the change to the end
time specifies a time that is before the current time, the Recorder stops
the recording.
The range is from 1 to 60. The default is 5.
SCTE-35 Ad Markers
Choose either to Retain or Discard the SCTE-35 Ad markers. If
SCTE-35 markers are discarded, both the PID in the PMT and the data
are removed. If the SCTE-35 markers are preserved, the Recorder places
the SCTE-35 Ad markers in the index file.
Recorder Port
Port number on the Recorder used for management communications
with the Recorder Manager. The range is from 50005 to 65535. The
default is 50005.
Protocol Version
Communication protocol version of the interface between the Recorder
and Recorder Manager.
You can choose one of the following from the drop-down list:
•
I02 - Comcast R8 I02 protocol.
•
I04 - Comcast R8 I04 protocol.
The default is I02.
Threadpool Size
Read-only field. Number of message processing threads of the
Recorder. The default is 16.
Status Report Interval
Read-only field. How often (in seconds) the Recorder reports status
information to the Recorder Manager. The default is 60.
HTTP Request Timeout
Read-only field. Time that the Recorder application waits for an HTTP
request after it is signaled. The default is 5 seconds.
HTTP Response Timeout
Read-only field. Time that the Recorder application waits for an HTTP
response. The default is 5 seconds.
Manager Notify Thresholds
Recording Bandwidth
Threshold, as a percentage, for recording bandwidth. If this threshold is
exceeded (that is, if the bandwidth used for ingesting recordings
exceeds the configured percentage), the Recorder sends a notification to
the Recorder Manager. The range is from 1 to 100. The default is 1.
Delivery Bandwidth
Threshold, as a percentage, for delivery bandwidth. If threshold is
exceeded (that is, if the bandwidth used for delivering recordings
exceeds the configured percentage), the Recorder sends a notification to
the Recorder Manager. The range is from 1 to 100. The default is 1.
Storage Capacity
Threshold, as a percentage, for storage capacity. If threshold is exceeded
(that is, if the disk storage used on the Recorder exceeds the configured
percentage), the Recorder sends a notification to the Recorder Manager.
The range is from 1 to 100. The default is 1.
Cisco VDS-VR 4.1 Software Configuration Guide
4-21
Chapter 4
Configuring the VDS
System Level Configuration
Table 4-8
Shared Recorder Settings Fields (continued)
Field
Description
Location Virtual IP
Location Virtual IP
IP address the Recorders use 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 in the Product Overview chapter of this guide.
Location Subnet Mask
Subnet mask for the Location Virtual IP.
IP Packet Priority
HTTP DSCP
DSCP value for the transmitted HTTP IP packet. The range is from 0 to
63 and the default value is 36.
Media Capture Engine
Step 3
Media Capture IP
The IP address of the MCE+ component. This is a read only field, and
its value is set to 127.0.0.1
Media Capture Port
The port on which MCE+ runs the HTTP server utility.
Media Capture UDS Dir
The directory to which Unix domain socket downloads the ATS
segments.
Click Submit to save the settings.
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 VDS server or QAM gateway, do the following:
Step 1
Choose Configure > System Level > IP Nickname. The IP Nicknames page is displayed(Figure 4-5).
Figure 4-5
IP Nicknames Page
Cisco VDS-VR 4.1 Software Configuration Guide
4-22
Chapter 4
Configuring the VDS
System Level Configuration
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
Note
The Media Importer is part of the Media Scheduler, which is an optional feature.
There are two ways to import an EPG file, one is to manually upload the file by using the EPG Upload
page (see Uploading an EPG File, page 7-22), the other is to automatically import the EPG file using the
Media Importer page.
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 of the EPG
files from an FTP server.
To configure the Media Importer, do the following:
Step 1
Choose Configure > System Level > Media Importer. The Media Importer page is displayed.
Step 2
Enter the settings as appropriate. See Table 4-9 for descriptions of the fields.
Table 4-9
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 Uploading an EPG File, page 7-22.
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. Enter the
relative or absolute path according to the configuration of the FTP server.
Mismatching the configuration could result in failure of Auto Import function.
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.
Cisco VDS-VR 4.1 Software Configuration Guide
4-23
Chapter 4
Configuring the VDS
System Level Configuration
Table 4-9
Media Importer Fields (continued)
Field
Description
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.
Note
Step 3
If the Media Importer is importing, any configuration changes to the Auto Import feature take
effect after current auto import is complete.
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.
Note
The CallSign Setup is part of the Real Time Capture Type (non-Media Scheduler) optional feature.
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 4-6).
Cisco VDS-VR 4.1 Software Configuration Guide
4-24
Chapter 4
Configuring the VDS
System Level Configuration
Figure 4-6
Step 2
Enter the call sign settings as appropriate. See Table 4-10 for descriptions of the fields.
Table 4-10
Step 3
CallSign Setup Page
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.
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.
Cisco VDS-VR 4.1 Software Configuration Guide
4-25
Chapter 4
Configuring the VDS
System Level Configuration
Configuring Input Channels
Note
The Input Channels page is part of the Media Scheduler 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
Uploading an EPG File, page 7-22.
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 4-7).
Figure 4-7
Step 2
Input Channels Page
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.
Cisco VDS-VR 4.1 Software Configuration Guide
4-26
Chapter 4
Configuring the VDS
System Level Configuration
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
Step 5
The combination of the IP address and port must be unique for each channel.
Enter the channel settings as appropriate. See Table 4-11 for descriptions of the fields.
Table 4-11
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 for every asset on this channel. This field applies only to the SA
Tribune transformer type.
Billing ID
Audio Type
Step 6
Input Channels Fields
Audio types available for all assets on this channel (Dolby ProLogic, Dolby
Digital, Stereo, Mono, Dolby 5.1).
Click Submit.
To reset the field, click Reset.
Cisco VDS-VR 4.1 Software Configuration Guide
4-27
Chapter 4
Configuring the VDS
System Level Configuration
Note
In OCN deployment using MediaX, you cannot delete a channel that has future scheduled events
but the channel gets deleted after start of the recording
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
Note
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 RTSP Deployment Type, page F-14.
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 VDS,
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.
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 Configuring the Route Table,
page 4-78.
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 should not span more than one Stream Group.
Cisco VDS-VR 4.1 Software Configuration Guide
4-28
Chapter 4
Configuring the VDS
System Level Configuration
Note
A logical SOP, which is an SOP virtual IP address and domain name, can span multiple source subnets.
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).
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 Configuring the Route Table,
page 4-78.
Configuring the System Level Logging
All logs are located in the /arroyo/log directory. The log files are rotated at least once a day and time
stamps are added to the filenames. Some log files that grow rapidly are rotated more frequently
(determined by file size); this rotation may happen up to once an hour. Most log files have the following
suffix: log.<YYYYMMDD.> The time zone for log rotation and filename suffixes is coordinated
universal time (UTC). As part of the new log entry format, the log level and facility are included.
All log entries have the following changes:
•
Stream handle is represented in decimal format
•
IP addresses are represented in dotted-decimal format
•
Clear identification of where a stream is going rather than a MAC address
•
Time is represented in UTC
•
Global Object ID (GOID) is represented in hexadecimal
Stream Trace
Log messages currently in the streamevent.log file are converted to a structured message and assigned
the “stream trace” facility number. Other messages that record stream creation, routing, or playout are
converted to a structured message and assigned the “stream trace” facility number. This enhancement,
along with configuring syslog-ng to direct all “stream trace” facility messages to a single, centralized
log server, provides a coherent set of log messages that describe stream history.
Facility Information, and Associated Log File and Debug Flags
For information on each facility and associated log file and debug flags, use the loginfo tool. The loginfo
tool can run on any VDS server, including the CDSM. Start a Telnet or SSH session, log in to the VDS
server, and enter the loginfo command without any arguments. Information on each facility is listed.
Cisco VDS-VR 4.1 Software Configuration Guide
4-29
Chapter 4
Configuring the VDS
System Level Configuration
Configuring Logging Levels
All logging is configured at the System Level or Server Level. The configuration of the logging levels
at the Server Level overrides the System Level settings.
To set a log level for a facility at the System Level, do the following:
Step 1
Choose Configure > System Level > Logging. The Log page is displayed.
Step 2
From the Facility Name drop-down list, select a facility and click Display. The Log Level fields are
displayed.
The facilities list is based on the configuration of the system.
Step 3
Enter the Log Level settings as appropriate. See Table 4-12 for descriptions of the fields.
Table 4-12
Log Level Fields
Field
Description
Local Log Level
The Local Log Level drop-down list has the following options:
•
Emergency (0)
•
Alert (1)
•
Critical (2)
•
Error (3)
•
Warning (4)
•
Notice (5)
•
Informational (6)
A log level setting includes all the more urgent levels. For example, if the log
level is set to Error (3), then Alert (2), Critical (1), and Emergency (0) log entries
are included as well as Error (3).
Step 4
Remote Log Level
To enable remote logging for the selected facility, select the appropriate log level
from the Remote Log Level drop-down list. The default setting is disable.
Debug Flags
Debug messages, if applicable, are configured by setting one or more debug
flags. To select or deselect debug flags, you have the following options:
•
To select one debug flag, click the flag.
•
To select multiple debug flags, hold down the Ctrl key and click each flag,
or hold down the Shift key and click the beginning flag and ending flag.
•
To deselect a debug flag when a group of debug flags are selected, hold
down the Ctrl key and click the flag.
Click Submit.
To clear the fields and start over, click Reset.
To delete the log level settings for a facility, select the facility from the drop-down list and click Delete.
Cisco VDS-VR 4.1 Software Configuration Guide
4-30
Chapter 4
Configuring the VDS
System Level Configuration
Configuring the System Level Syslog
The Syslog configuration page at the System Level and Server Level is used to configure the IP address
and port of the server that is to receive remote logging. The configuration of the syslog server at the
Server Level overrides the System Level settings. For remote logging information to be sent for a facility,
the Remote Log Level must be set on the Logging page. See Configuring the System Level Logging,
page 4-29 for more information.
To configure the remote logging server, do the following:
Step 1
Choose Configure > System Level > Syslog. The Syslog page is displayed.
Step 2
Check the Enable Remote Logging check box.
Step 3
In the IP Address field, enter the IP address of the remote server that is to receive syslog messages.
Step 4
In the Port field, enter the port of the remote server that is to receive syslog messages.
Step 5
Click Submit.
To clear the fields and start over, click Reset.
To delete the remote server settings, click Delete.
Configuring System Level Error Repair
The VOD Error Repair settings can be configured on the System Level, Array Level, and the Server
Level. Settings configured at the Array Level take precedence over System Level settings, and settings
at the Server Level take precedence over Array Level or System Level settings.
Note
VOD Error Repair is a licensed feature. VOD Error Repair requires the LSCP Client Protocol be set to
Cisco (RTSP) and the STB have the Cisco Visual Quality Experience Client (VQE-C) software running
on it. For more information, see VOD Error Repair, page F-7.
To configure error repair at the System Level, do the following:
Step 1
Choose Configure > System Level > Error Repair. The Error Repair page is displayed.
Step 2
Enter the Error Repair settings as appropriate. See Table 4-13 for descriptions of the fields.
Table 4-13
VOD Error Repair Fields
Field
Description
Error Repair Mode
ER Enable
To enable Error Repair, check the ER Enable check box.
RTP Encapsulation Enable
To enable RTP encapsulation, check the RTP Encapsulation Enable
check box. TV VDS supports both UDP and RTP encapsulation. If
the RTP Encapsulation Enable check box is not checked, the VDS is
configured to only handle UDP encapsulation.
Repair Packets DSCP
Cisco VDS-VR 4.1 Software Configuration Guide
4-31
Chapter 4
Configuring the VDS
Array Level Configuration
Table 4-13
VOD Error Repair Fields (continued)
Field
Description
DSCP of Repair Packets Sent
DSCP value for the transmitted RTP and RTCP packets sent for error
repair. The range is from 0 to 63. The default is 0.
RTCP Report Exporting
Step 3
Exporting
Click the Enabled radio button to enable exporting of the RTCP
reports. The RTCP reports can be exported to a third-party analysis
application.
IP Address
Enter the IP address or the domain name of the server hosting the
analysis application.
TCP Ports
Enter the TCP port number that is used to receive the reports on the
server hosting the analysis application.
Click Submit.
To clear the fields and start over, click Reset.
To return the settings to the factory default values, click Factory.
To monitor the VOD Error Repair feature, use the Application Monitoring Tool (AMT). For more
information, see Using the VDS Streamer Application Monitoring Tool, page E-1
Array Level Configuration
The Array Level tab has the following configuration options:
•
Configuring the Array Level DNS
•
Configuring the Array Level NTP Server
•
Configuring Stream Groups
•
Locating Cache Groups
•
Configuring Vault Groups
•
Configuring Ingest Steering
•
Configuring SSV Groups
•
Configuring Cache Groups
•
Mapping Vault Groups to Cache Groups
•
Mapping Cache 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 Sites
•
Configuring Cache-Fill Bandwidth Using Thin Pipe Mapping
Cisco VDS-VR 4.1 Software Configuration Guide
4-32
Chapter 4
Configuring the VDS
Array Level Configuration
Note
•
Configuring the Media Scheduler
•
Configuring Array Level Error Repair
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.
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 4-14 for descriptions of the fields.
Table 4-14
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.
Cisco VDS-VR 4.1 Software Configuration Guide
4-33
Chapter 4
Configuring the VDS
Array Level Configuration
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 VDS server or configuring NTP on a CDSM or VVIM, see
Other NTP Configurations, page 4-86.
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 Configuring QAM Gateways, page 4-4. For more information about
destination subnetworks and Stream Groups, see Configuring Stream Destinations, page 4-9.
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.
Beginning with VDS-VR (formerly TV VDS) Release 3.4, ISR Stream groups are also configured via
Stream Groups page.
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 Identifying Server IDs and Group IDs for VVI with Split-Domain Management,
page 7-23.
For more information about the VVI settings on the CDSM Setup page, see Virtual Video Infrastructure,
page F-8.
Cisco VDS-VR 4.1 Software Configuration Guide
4-34
Chapter 4
Configuring the VDS
Array Level Configuration
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 4-8).
To edit a Stream Group, choose the Stream Group from the drop-down list and click Display.
Note
For ISR Stream Group, user is provided an option to enable or disable Fade Frame Support.
Figure 4-8
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.
Note
Step 4
You can use only alphanumeric characters (0–9, a–z, A–Z), the dash (-), and the underscore (_) to create
a Stream Group name.
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 4-15.
Cisco VDS-VR 4.1 Software Configuration Guide
4-35
Chapter 4
Configuring the VDS
Array Level Configuration
Table 4-15
Step 5
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.
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.
Note
The Cache Group Locator page is available only on the Stream Manager when VVI is enabled. For more
information, see Virtual Video Infrastructure, page F-8.
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 Virtual Video
Infrastructure, page F-8 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 Identifying Server IDs and Group IDs
for VVI with Split-Domain Management, page 7-23.
Cisco VDS-VR 4.1 Software Configuration Guide
4-36
Chapter 4
Configuring the VDS
Array Level Configuration
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 4-9).
Figure 4-9
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 Groups.
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:
Step 4
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.
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.
Cisco VDS-VR 4.1 Software Configuration Guide
4-37
Chapter 4
Configuring the VDS
Array Level Configuration
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 Mapping
Vault Groups for Redundancy, page 4-48.
Note
The Vault Groups Setup page is part of the Vault Groups feature and is displayed only if Vault Groups
is enabled. For more information, see Vault Groups, page F-6. If VVI is enabled, The Vault Groups Setup
page is displayed only on the VVIM. For more information, see Virtual Video Infrastructure, page F-8.
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.
Note
The maximum number of Vault Groups is 20.
Cisco VDS-VR 4.1 Software Configuration Guide
4-38
Chapter 4
Configuring the VDS
Array Level Configuration
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 4-10).
Figure 4-10
Step 2
Vault Groups Setup Page
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 4-16.
Table 4-16
Step 5
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.
Click Submit.
To reset the field, click Reset.
Cisco VDS-VR 4.1 Software Configuration Guide
4-39
Chapter 4
Configuring the VDS
Array Level Configuration
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 Ingest Steering
The Ingest Steering page allows you to have specific Vault Groups ingest content with specified Product
IDs. For example, if you have a Vault Group that you want to be responsible for ingesting all the live
ingests, you can use the Product ID to direct that content to that Vault Group.
The backoffice uses the Ingest Manager to ingest packages, including content. As specified in the ADI
1.1 Specification, there is an ADI XML file for each package and the Product ID is one attribute in this
ADI XML file.
Every Product ID maps to only one Vault Group. The Product ID is included in the ADI.XML for FTP
pull content, additionally, the Product ID can be configured in the Input Channels page for MediaX live
content. Ingestion with such Product ID information is correctly dispatched to the Vault Group mapped
in Ingest Steering.
For more information, see Steering Ingests, page 2-22.
Note
The Ingest Steering page is not available if the Ingest Steering feature is not enabled. For more
information, see CDSM or VVIM NAV Setup, page F-15. The Ingest Steering feature requires Vault
Groups to be enabled.
Note
Enabling or disabling Ingest Steering requires restarting the FSI process on all Vaults. If Ingest Steering
has been enabled and has taken effect, the changes to the Ingest Steering configuration do not take effect
immediately.
•
If there is ingest activity, wait two hours for FSI to reload the new configuration.
•
If there is no ingest activity, restarting the FSI process on all Vaults could make the changes take
effect immediately.
To configure Ingest Steering, do the following:
Step 1
Choose Configure > Array Level > Ingest Steering. The Ingest Steering page is displayed
(Figure 4-11).
Cisco VDS-VR 4.1 Software Configuration Guide
4-40
Chapter 4
Configuring the VDS
Array Level Configuration
Figure 4-11
Step 2
Ingest Steering page
In the New Product ID field, enter the product ID and click Add. The product ID is listed in the
Unassigned Products text box.
Repeat for each product ID.
Step 3
From the Select Vault Group to assign products drop-down list, choose a Vault Group and click
Display.
Step 4
To assign the product IDs to the selected Vault Group, click the product ID to highlight it and click the
> button.
To assign all product IDs, click the >> button.
To remove all product IDs from the Assigned Products text box, click the << button.
To remove one product ID from the Assigned Products text box, click the product ID to highlight it and
click the < button.
To delete a group of product IDs, click the first product ID, then hold the Ctrl key and click the
remaining product IDs, then click Delete.
To delete one product ID, click the product ID to highlight it and click Delete.
Step 5
When you have finished assigning the product IDs for the Vault Group displayed, click Submit.
Cisco VDS-VR 4.1 Software Configuration Guide
4-41
Chapter 4
Configuring the VDS
Array Level Configuration
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.
Note
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 SSV Groups, page F-5. 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 Mapping Vault Groups for
Redundancy, page 4-48. The Thin Pipe Map page can be used to configure low-bandwidth connections
among SSV Groups. For more information, see Configuring Cache-Fill Bandwidth Using Thin Pipe
Mapping, page 4-52.
An ISV can never be a member of more than one SSV Group.
Note
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.
Note
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 4-17.
Table 4-17
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.
Cisco VDS-VR 4.1 Software Configuration Guide
4-42
Chapter 4
Configuring the VDS
Array Level Configuration
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.
Note
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 4-12).
Figure 4-12
Cache Groups Setup Page—HTTP Streamers
Cisco VDS-VR 4.1 Software Configuration Guide
4-43
Chapter 4
Configuring the VDS
Array Level Configuration
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
Step 5
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 HTTP Streamers, page 2-12.
b.
In the Location Subnet Mask field, enter the subnet mask for the Location IP address.
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 4-18.
Table 4-18
Step 6
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.
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 Configuring Cache
Groups, page 4-43 and Configuring Vault Groups, page 4-38.
Note
The Cache To Vault Map page only displays on the VVIM and is available only when Vault Groups and
VVI are both enabled. For more information, see Vault Groups, page F-6 and Virtual Video
Infrastructure, page F-8.
To map Vault Groups to Cache Groups, do the following:
Cisco VDS-VR 4.1 Software Configuration Guide
4-44
Chapter 4
Configuring the VDS
Array Level Configuration
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 Configuring Cache Groups, page 4-43 or Configuring
Vault Groups, page 4-38. 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 Cache Groups to Cache Groups
The Cache To Cache Map page is used to map Cache Groups to Cache Groups in a VVI. Before you can
map Cache Groups to Cache Groups, you must create them. For more information, see Configuring
Cache Groups, page 4-43.
Note
The Cache To Cache Map page only displays on the VVIM. For more information, see Virtual Video
Infrastructure, page F-8.
To map Cache Groups to Cache Groups, do the following:
Step 1
Choose Configure > Array Level > Cache To Cache Map. The Cache To Cache Map page is displayed.
Step 2
From the Cache Group drop-down list, choose a Cache Group and click Select. All available Cache
Groups are displayed.
Step 3
Choose the preference setting for each Cache 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 Cache Group as a cache-fill source.
Cisco VDS-VR 4.1 Software Configuration Guide
4-45
Chapter 4
Configuring the VDS
Array Level Configuration
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 Cache Group, choose the Cache Group from the drop-down list
and click Select.
To delete a Cache Group, see Configuring Cache Groups, page 4-43. When a Cache Group is deleted,
the mapping for the Cache Group is also deleted, and any other mappings to the Cache Group are 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 Configuring Stream Groups,
page 4-34 and Configuring Cache Groups, page 4-43 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 Locating Cache Groups, page 4-36 for more
information.
Note
The Stream To Cache Map page is available only on the Stream Manager when VVI is enabled. For more
information, see Virtual Video Infrastructure, page F-8.
Streamers can be used as cache-fill sources when Streamer is Cache is enabled on the Server Setup page
(see Configuring the Servers, page 4-69). 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 4-13).
Cisco VDS-VR 4.1 Software Configuration Guide
4-46
Chapter 4
Configuring the VDS
Array Level Configuration
Figure 4-13
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.
Note
The Stream to Cache Map page is associated with the configuration file FillSourceConfig in /arroyo/test
directory. After submitting the Stream to Cache Map page, the FillSourceConfig file is updated.
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 Configuring Stream Groups, page 4-34 or Configuring
Cache Groups, page 4-43. 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.
Cisco VDS-VR 4.1 Software Configuration Guide
4-47
Chapter 4
Configuring the VDS
Array Level Configuration
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 Configuring Vault Groups, page 4-38 for more
information.
Note
The Vault Redundancy Map page is part of the Vault Groups feature and is displayed only if Vault Groups
is enabled. If VVI is enabled, The Vault Redundancy Map page is displayed only on the VVIM. For more
information, see Virtual Video Infrastructure, page F-8 and Vault Groups, page F-6.
Note
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 Vault Group Redundancy, page 1-20.
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 4-14).
Figure 4-14
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:
Cisco VDS-VR 4.1 Software Configuration Guide
4-48
Chapter 4
Configuring the VDS
Array Level Configuration
•
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
•
Step 4
The Vault Mirror Copies field in the Server Setup page determines the number of mirrored
copies kept in the VDS for the content stored on the specified Vault. See Configuring the
Servers, page 4-69 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.
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 Configuring Vault Groups, page 4-38. 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.
Note
All Vaults in the Master Vault Group must be in the same network; otherwise, the master Vault failover
fails.
The master IP address is set as part of the initial configuration (VDSconfig 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, go to the System Health page (Monitor > System
Health).
Note
The Master Vault Group page is part of the Vault Groups feature and is displayed only if Vault Groups
is enabled. If VVI is enabled, The Master Vault Group page is displayed only on the VVIM. For more
information, see Virtual Video Infrastructure, page F-8 and Vault Groups, page F-6.
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
Check the Master Vault Group check box associated with the Vault Group.
Step 3
Click Submit.
Cisco VDS-VR 4.1 Software Configuration Guide
4-49
Chapter 4
Configuring the VDS
Array Level Configuration
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 Restarting a Server, page 7-11 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.
Note
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 Identifying Server IDs and Group
IDs for VVI with Split-Domain Management, page 7-23.
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 18,000 sessions. You
must configure a Control server for each group of up to 18,000 sessions. For instance, if you have 19,000
sessions, 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 Streamer Workflow, page 2-9.
Beginning with VDS-VR (formerly TV VDS) Release 3.4, Control and Setup IPs are also configured for
ISR Stream Groups.
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 4-15).
Figure 4-15
Control/Setup IP Page
Cisco VDS-VR 4.1 Software Configuration Guide
4-50
Chapter 4
Configuring the VDS
Array Level Configuration
Step 2
For each Stream Group, enter the IP address, subnet mask of the Control IP, Setup IP, or Control/Setup
IP and the Setup ID.
Step 3
From the IP Type drop-down list, choose an IP type. See Table 4-19 for descriptions of the types.
Table 4-19
Step 4
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.
Click Submit.
To reset the field, click Reset.
Note
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 Sites
The Site Setup page allows you to create sites and assign Stream Groups, Cache Groups, and Vault
Groups to them for configuring thin pipe maps. To configure thin pipe maps, you must first configure
the sites.
To configure a site, do the following:
Step 1
Choose Configure > Array Level > Site Setup. The Site Setup page is displayed.
Step 2
From the Select Site to View/Edit drop-down list, choose Add New Site and click Display.
To edit a site, choose the site from the drop-down list and click Display.
Step 3
In the New Site Name field, enter the name of the site and click Submit.
You can use only alphanumeric characters (0-9, a-z, A-Z), the dash (-), and the underscore (_) to create
a Site name.
Step 4
Add the appropriate Stream Groups, Vault Groups, and Cache Groups to the site.
The unassigned groups are listed along with a drop down-list for each that offers the options described
in Table 4-18.
Cisco VDS-VR 4.1 Software Configuration Guide
4-51
Chapter 4
Configuring the VDS
Array Level Configuration
Table 4-20
Step 5
Group Options
Group Option
Description
No Change
Do not make any changes to the site assignment.
Site Name
Add this group to this site.
None
Remove this group from this site. Applicable only to groups
assigned to the selected site.
Don’t Change
Do not assign this group to this site.
Click Submit.
To reset the field, click Reset.
To view the members of a site, choose the site from the drop-down list and click Display.
To delete a site, first remove all groups from the site, then click Delete Site.
Configuring Cache-Fill Bandwidth Using Thin Pipe Mapping
The Thin Pipe Map page allows you to configure low-bandwidth connections between local and remote
sites. A local site consists of groups of servers in the same site, for example, all the Streamers in a Stream
Group are considered part of the same site, or local site. A remote site consists of groups of servers in
other Stream Groups, Cache Groups, and Vault Groups. Before you can configure thin pipes, you must
define the sites. For more information, see Configuring Sites, page 4-51.
There can be multiple thin pipes configured for each local site. 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 site with a Stream Group. The thin pipes are completely
independent of each other. Additionally, thin pipes can be created among servers at the same site by
selecting the same site for Local Site and Available Remote Site.
The Thin Pipe Map page also allows for the configuration of thin pipes in a hierarchy, where a remote
site 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.
Note
The Thin Pipe Map page is displayed only if Thin Pipe Management is enabled. See Thin Pipe
Management, page F-7 for more information.
For CCP traffic to work properly in the VDS, the following configuration must exist:
•
Thin pipe mapping must be configured in the VDS.
•
DiffServ AF settings must be configured on the VDS servers.
•
Routers must support the bandwidths that are configured for the thin pipe mapping on the VDS.
Cisco VDS-VR 4.1 Software Configuration Guide
4-52
Chapter 4
Configuring the VDS
Array Level Configuration
Note
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 VDS server. See
Configuring the Servers, page 4-69 for more information.
As an example, Figure 4-16 shows the maximum bandwidth available for the various groups in a Virtual
Video Infrastructure (VVI) system with two super headends (SHEs) and three caching sites.
Figure 4-16
Note
Thin Pipe Example
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,
Super Headend 1(SHE1) to Super Headend 2 (SHE2) and Cache Site 3 share a 3 Gbps link on the route
between SHE1 and the other two sites, then another thin pipe must be configured to specify this 3-Gbps
restriction.
Table 4-21 lists the thin pipe mappings that would be configured for the different Vault Groups
illustrated in Figure 4-16.
Table 4-21
Thin Pipe Map
Thin Pipe Mappings for Thin Pipe Example
Bandwidth
(Gbps)
Remote Site
Super Headend 1 (SHE1)
SHE1toAll
SHE2, Cache Site 1, Cache Site 2, Cache Site 3
5
SHE1toSHE2
SHE2
4
SHE1toCS1
Cache Site 1
2
Cisco VDS-VR 4.1 Software Configuration Guide
4-53
Chapter 4
Configuring the VDS
Array Level Configuration
Table 4-21
Thin Pipe Mappings for Thin Pipe Example (continued)
Thin Pipe Map
Remote Site
Bandwidth
(Gbps)
SHE1toCS2
Cache Site 2
2
SHE1toCS3
Cache Site 3
2
Super Headend 2 (SHE2)
SHE2toAll
SHE1, Cache Site 1, Cache Site 2, Cache Site 3
4
SHE2toCS1
Cache Site 1
2
SHE2toCS2
Cache Site 2
2
SHE2toCS3
Cache Site 3
2
Cache Site 1 (CS1)
CS1toAll
SHE1, SHE2, Cache Site 2, Cache Site 3
Cache Site 2 (CS2)
CS2toAll
SHE1, SHE2, Cache Site 1, Cache Site 3
2
SHE1, SHE2, Cache Site 1, Cache Site 2
2
Cache Site 3 (CS3)
CS3toAll
The thin pipes configured in Table 4-21 ensure that the bandwidth for SHE1 never exceeds the maximum
bandwidth available for SHE1, which is 5 Gbps. This means that even if all remote groups were
requesting cache fills from SHE1, which would be a maximum throughput of 9 Gbps, the actual
maximum bandwidth of cache-fill traffic coming from SHE1 would never exceed 5 Gbps.
One server in the site is elected as the bandwidth manager for all servers in the site. The bandwidth
manager controls the traffic leaving the site to any other site and queries all the VDS servers in the site
for the thin pipe mapping configuration of each VDS server. For more information about the bandwidth
manager, see Bandwidth Manager for Thin Pipe, page 2-8.
Note
Before you can configure thin pipes, you must define the sites. For more information, see Configuring
Sites, page 4-51.
To configure a Thin Pipe Map, do the following:
Step 1
Choose Configure > Array Level > Thin Pipe Map. The Thin Pipe Map page is displayed.
Step 2
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 3
From the Local Site drop-down list, choose the site you want to use as the local site for this thin pipe
map.
Step 4
In the Pipe Name field, enter the name for the pipe map.
Step 5
In the Max Transmit Bandwidth field and the Max Receive Bandwidth field, enter the maximum
transmit and receive megabits per second (Mbps) for this pipe.
Cisco VDS-VR 4.1 Software Configuration Guide
4-54
Chapter 4
Configuring the VDS
Array Level Configuration
Note
The Max Bandwidth fields represent the throughput for the pipe, which is defined per site
(Stream Group, Cache Group, and so on); not each server. For all existing thin pipes, only the
Max Transmit Bandwidth and Max Receive Bandwidth fields are allowed to be edited. All
other fields are read only.
If Site 1 has 2 Vault Groups with 2 Vaults each and Site 2 has 1 Cache Group with 2 Caching Nodes, and
the network design and physical link were such that it could support 500 Mbps throughput (that is, 500
Mbps transmit and 500 Mbps receive), then the maximum of the Transmit Max Bandwidth cannot
exceed 500 Mbps and the maximum of the Receive Max Bandwidth cannot exceed 500 Mbps. Further,
the sum of the bandwidths of all physical links configured for CCP among all sites must be less than the
bandwidth configured for the AF class reserved for CCP.
Note
The bandwidth threshold for each server has an upper limit of 90 percent and a lower limit of 5
percent. For more information, see Bandwidth Manager for Thin Pipe, page 2-8.
Step 6
In the Available Remote Sites area, check the check box next to each remote site that you want to use
this maximum bandwidth restriction.
Step 7
Check the Limit traffic to all HTTP subnets check box if this thin pipe with the Max Bandwidth
settings configured is created to limit the bandwidth between the selected Local Site and the HTTP
Streamers in a VVI represented by the selected remote sites.
Note
Step 8
Alternatively, to apply the thin pipe settings to specific HTTP Streamer subnets, uncheck the Limit
traffic to all HTTP subnets check box and specify the subnets in the Subnet Configuration section.
Enter the Network and Subnet Mask for each subnet. To add more HTTP Streamer subnets, click the
plus icon in the Subnet Configuration section.
Note
Step 9
This field is only applicable if HTTP is the cache-fill protocol. HTTP as the cache-fill protocol
is only supported in RTSP environments.
The Subnet Configuration section is only applicable if HTTP is the cache-fill protocol.
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.
Cisco VDS-VR 4.1 Software Configuration Guide
4-55
Chapter 4
Configuring the VDS
Array Level Configuration
Configuring the Media Scheduler
Note
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 Uploading an EPG File, page 7-22 and
Configuring Input Channels, page 4-26 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.
Note
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 4-17).
Cisco VDS-VR 4.1 Software Configuration Guide
4-56
Chapter 4
Configuring the VDS
Array Level Configuration
Figure 4-17
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
Step 3
Media Scheduler Page—User Preferences
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 Changing User Default Settings, page 7-6.
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 Package Metadata Editor, page 4-61.
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 Configuring Input Channels, page 4-26.
Cisco VDS-VR 4.1 Software Configuration Guide
4-57
Chapter 4
Configuring the VDS
Array Level Configuration
Step 6
Click Save to save the settings. The calendar is displayed (Figure 4-18).
Figure 4-18
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 4-18). If Show On Return was selected
in the User Preferences, the User Preferences are displayed (Figure 4-17).
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 4-19).
Cisco VDS-VR 4.1 Software Configuration Guide
4-58
Chapter 4
Configuring the VDS
Array Level Configuration
Figure 4-19
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 4-20).
Figure 4-20
Media Scheduler Page—Program Information
Cisco VDS-VR 4.1 Software Configuration Guide
4-59
Chapter 4
Configuring the VDS
Array Level Configuration
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, page 4-61.
Step 4
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.
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.
Cisco VDS-VR 4.1 Software Configuration Guide
4-60
Chapter 4
Configuring the VDS
Array Level Configuration
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 4-21).
Figure 4-21
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.
Cisco VDS-VR 4.1 Software Configuration Guide
4-61
Chapter 4
Configuring the VDS
Array Level Configuration
Step 2
For metadata created from user-generated schedules, there is an option for recurring schedules
(Figure 4-22).
Figure 4-22
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 4-22 for descriptions of the Recurring Schedule fields.
Table 4-22
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.
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.
Recurrence End
Time
Depending on the setting in the User Preferences settings, any existing metadata is preserved or
overwritten. See User Preferences, page 4-56 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
http://www.cablelabs.com.
Cisco VDS-VR 4.1 Software Configuration Guide
4-62
Chapter 4
Configuring the VDS
Array Level Configuration
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 4-23).
To go to the main Media Scheduler page, click Go To Scheduler.
Figure 4-23
Step 2
Media Scheduler Page—Conflicts
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 4-21). 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.
Cisco VDS-VR 4.1 Software Configuration Guide
4-63
Chapter 4
Configuring the VDS
Array Level Configuration
Configuring Array Level Error Repair
The VOD Error Repair settings can be configured on the System Level, Array Level, and the Server
Level. Settings configured at the Array Level take precedence over System Level settings, and settings
at the Server Level take precedence over Array Level or System Level settings.
Note
VOD Error Repair is a licensed feature. VOD Error Repair requires the LSCP Client Protocol be set to
Cisco (RTSP) and the STB have the Cisco Visual Quality Experience Client (VQE-C) software running
on it. For more information, see VOD Error Repair, page F-7.
To configure error repair at the Array Level, do the following:
Step 1
Choose Configure > Array Level > Error Repair. The Error Repair page is displayed.
Step 2
From the Select Stream Group to View/Edit, select a Stream Group and click Display.
Step 3
Enter the Error Repair settings as appropriate. See Table 4-23 for descriptions of the fields.
Table 4-23
VOD Error Repair Fields
Field
Description
Error Repair Mode
ER Enable
To enable Error Repair, check the ER Enable check box.
RTP Encapsulation Enable
To enable RTP encapsulation, check the RTP Encapsulation Enable
check box. TV VDS supports both UDP and RTP encapsulation. If
the RTP Encapsulation Enable check box is not checked, the VDS is
configured to only handle UDP encapsulation.
Repair Packets DSCP
DSCP of Repair Packets Sent
DSCP value for the transmitted RTP and RTCP packets sent for error
repair. The range is from 0 to 63. The default is 0.
RTCP Report Exporting
Step 4
Exporting
Click the Enabled radio button to enable exporting of the RTCP
reports. The RTCP reports can be exported to a third-party analysis
application.
IP Address
Enter the IP address or the domain name of the server hosting the
analysis application.
TCP Ports
Enter the TCP port number that is used to receive the reports on the
server hosting the analysis application.
Click Submit.
To clear the fields and start over, click Reset.
To return the settings to the factory default values, click Factory.
To monitor the VOD Error Repair feature, use the Application Monitoring Tool (AMT). For more
information, see Using the VDS Streamer Application Monitoring Tool, page E-1
Cisco VDS-VR 4.1 Software Configuration Guide
4-64
Chapter 4
Configuring the VDS
Server Level Configuration
Server Level Configuration
After a server has been initially configured (see Initially Configuring the Devices, page 3-1), 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
•
Configuring the Servers
•
Configuring Individual Recorder Settings
•
Configuring the Route Table
•
Configuring the SNMP Agent
•
Configuring the Server Level DNS
•
Configuring the Server Level NTP
•
Configuring RTSP Setup
•
Configuring FSI Setup
•
Configuring the Server Level Logging
•
Configuring the Server Level Syslog
•
Configuring Server Level Error Repair
•
Configuring Live Database Backup
Configuring the Interfaces
The Interface Setup page is used to configure the different interfaces on the VDS servers. The
functionality of the Ethernet interfaces on the VDS servers is configurable. However, there is an optimal
configuration for each server. The interface functions are described in Table 4-24.
Table 4-24
VDS Interfaces
Type
Description
Not Used
This Interface is not being used.
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 to ingest content on to a
Vault or an ISV.
Stream
Transports streams to the QAM devices, or to subnets in the case of IPTV.
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 is given to
the higher-bandwidth stream traffic provided cache traffic is able to transmit on
other interfaces.
General
Reserves an Ethernet interface to allow optimal configuration.
Cisco VDS-VR 4.1 Software Configuration Guide
4-65
Chapter 4
Configuring the VDS
Server Level Configuration
Table 4-24
VDS Interfaces (continued)
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
Configuring the Control and Setup IPs, page 4-50. To configure a separate route
subnet for stream control traffic, see Configuring the Route Table, page 4-78.
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).
The Locate interface and port are used by the Locate Port service for
communications with third-party streamers that use HTTP to communicate.
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 Caching Node Workflow, page 2-12.
Default
Control
This interface is used when the user requires a separate interface for control traffic
that is delivered on a network not reachable from management interface (eth0). The
Default Control interface can be configured only on a single interface, it cannot be
configured for multiple interfaces. Although not restricted, ideally the “Default
Control” interface should be configured on a 1GigE interface, and not a 10GigE.
Ingest/Stream/ The Ingest/Stream/Cache interface can be used on a Streamer-Recorder for ingest,
Cache
streaming and caching.
Ingest/Cache
The Ingest/Cache interface can be used on a Streamer-Recorder for ingest and
caching traffic.
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 4-24).
Step 2
From the Server IP drop-down list, choose the IP address or nickname of the server and click Display.
Cisco VDS-VR 4.1 Software Configuration Guide
4-66
Chapter 4
Configuring the VDS
Server Level Configuration
Figure 4-24
Step 3
Interface Setup Page—Vault Page
Enter the interface settings as appropriate. See Table 4-25 for descriptions of the fields.
Cisco VDS-VR 4.1 Software Configuration Guide
4-67
Chapter 4
Configuring the VDS
Server Level Configuration
Table 4-25
Interface Fields
Field
Description
Setting
Choose each interface setting as appropriate. See Table 4-24 for descriptions
of the different interface types.
IP Address
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.
Subnet Mask
Subnet mask for this interface.
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.
Cache Port
UDP port number for cache traffic. The port number set for this interface
overrides the default cache port setting.
Note
Step 4
The Auto Populate IPs check box is available when the first applicable interface (for example,
the first stream interface) is configured with an IP address. If the Setting has been selected for
each of the remaining interfaces, checking the Auto Populate IPs check box and clicking Auto
Populate Now automatically enters the next consecutive IP address as the IP Address for the
next interface, and continues to populate all IP Address fields until they are all filled. Any
preexisting IP addresses in the IP Address fields are overwritten.
Click Submit to save the settings.
To clear the fields and start over, click Reset.
Cisco VDS-VR 4.1 Software Configuration Guide
4-68
Chapter 4
Configuring the VDS
Server Level Configuration
Configuring the Servers
Beginning with VDS-VR (formerly TV VDS) Release 3.4, the Server Setup page is also used to
configure the ISR.
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.
Note
If Bulk Configuration is enabled, the Configuration File Location field is displayed, along with
the Browse, Import, and Export buttons. To export the configuration of this page for all VDS
servers in the system, click Export. To import a Bulk Configuration XML file, click Browse to
locate the file, then click 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 Bulk Import/Export
Configuration, page F-4. For information about the Bulk Configuration feature and creating a
Bulk Configuration file for the Server Setup page and Interface Setup page, see Creating Bulk
Configuration Files, page B-1
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, ISR and ISV server. The ISV server setup page has a combination
of the Vault and Streamer fields. See Table 4-27 for descriptions of the fields and to which server they
apply.
Table 4-26 lists the CDSM GUI ID names and maps them to the CServer names in the setupfile and
.arroyorc files.
Table 4-26
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
Cisco VDS-VR 4.1 Software Configuration Guide
4-69
Chapter 4
Configuring the VDS
Server Level Configuration
Table 4-27
Server Setup Fields
Field
Description
Server Type
Host Name
Fully qualified hostname for this server. The name can be up to 64 characters long.
Assigning a hostname is optional.
All servers:
Vault, Caching
Node,
Streamer, ISV.
ISR
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.
TTL
IP time to live (TTL) for data packets. The IP TTL default is 16 hops. Valid entries range All servers
from 0 to 255.
Null Streaming
From the Null Streaming drop-down list, choose Enabled to allow the streaming of null Streamer, ISV,
MPEG files, or Disabled to prevent the streaming of null MPEG files.
ISR
Live Playback
Playlist
Trick-mode
Restriction
Informational only. Displays the settings for the Playlist Trick-mode Restrictions. For
information on setting this field, see Configuring MPEG Tuning, page 4-17.
Streamer, ISV,
ISR
Dynamic
Trickmodes
Informational only. Displays the settings for the Dynamic Trickmodes. For information on Streamer, ISV,
setting this field, see Configuring MPEG Tuning, page 4-17.
ISR
Playlist Range
Conversion
Mode
Informational only. Displays the settings for the Playlist Range Conversion Mode. For
information on setting this field, see Configuring MPEG Tuning, page 4-17.
STUN Play
Error Delay
Session Traversal Utilities for NAT (STUN) Play Error Delay field is available when NAT Streamer, ISV
is enabled through the CDSM Setup page. The NAT feature is part of the Stream
Destination feature. NAT is available only for RTSP environments with the Cisco RTSP
Deployment Type. See NAT Support, page F-4 for more information.
Streamer, ISV,
ISR
The STUN Play Error Delay is the time allowed to complete the connectivity handshake
between each callback to the control application by the CServer. The range is from 1 to
2999 milliseconds. The default is 1000.
Session Traversal Utilities for NAT (STUN) Play Timeout field is available when NAT is Streamer, ISV
enabled through the CDSM Setup page. The NAT feature is part of the Stream Destination
feature.
STUN Play
Timeout
The STUN Play Timeout is the total time the CServer waits before the connectivity check
fails. The range is from 1 to 299 seconds. The default is 10.
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,
ISR
Ending
Transport Port
Ending default UDP port number used for stream and stream/cache interfaces. There is no Streamer,
default for the ending transport port number.
ISV,ISR
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.
Allow TCP
Traffic
Cisco VDS-VR 4.1 Software Configuration Guide
4-70
All servers
Chapter 4
Configuring the VDS
Server Level Configuration
Table 4-27
Field
Server Setup Fields (continued)
Description
Server Type
Ingest MPEG Settings
PID
Standardization
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 Configuring Ingest Tuning,
page 4-15.
Vault, ISV
Sequence End
Remove
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 Configuring Ingest Tuning, page 4-15.
Vault, ISV
Rate
Standardize
Informational only. If this field is set to enable, then MPEG-2 video assets have their rates Vault, ISV
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
Configuring Ingest Tuning, page 4-15.
Fail Ingest Settings
Fail Ingest
Settings Status
Informational only. If the server settings are out of synchronization with the Fail Ingest
Vault, ISV
configuration settings, a warning message to resubmit the Ingest Tuning page is displayed.
Stream Group Information
Stream Group
Stream Group
ID
Streamer Is
Cache
These fields display the Stream Group and Stream Group ID that the ISV or Streamer is a Streamer, ISV,
member of. The Stream Group and Stream Group ID are informational only. To configure ISR
Stream Groups, see Configuring Stream Groups, page 4-34.
If Streamer Is Cache is enabled, the Streamer can be used as a possible cache-fill source Streamer, ISV,
ISR
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 Mapping Stream Groups to Cache-Fill Sources,
page 4-46.
Cache Group Information
Cache Group
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,
Cache Group ID
see Configuring Cache Groups, page 4-43.
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. Vault, ISV
The Vault Group Name is informational only. To configure Vault Groups, see Configuring
Vault Groups, page 4-38.
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.
Streamer, ISV,
ISR
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.
Cisco VDS-VR 4.1 Software Configuration Guide
4-71
Chapter 4
Configuring the VDS
Server Level Configuration
Table 4-27
Server Setup Fields (continued)
Field
Description
Server Type
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.
All servers
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.
Server Status
All servers
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. For more information, see Offloading a Server, page 7-12.
Vault Mirror
Copies
From the drop-down list, choose the number of copies of content to store in the Vaults in Vault, ISV
the array or site. Vault Mirror Copies defines the number of copies that should be
maintained within the array. The range is from 0 to 10.
Vault Local
Copies
From the drop-down list, choose the number of copies of content that are stored on this
server. The range is from 1 to 4.
Vault, ISV
Transport, Cache, and HTTP IP Packets
DSCP Marking
Method
From the DSCP Marking Method drop-down list, select one of the following options:
•
Simple
•
AutoAF1x, AutoAF2x, AutoAF3x, or AutoAF4x
•
Custom
All servers
For more information about the options and associated fields, see Configuring QoS
Settings, page 4-73.
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.
FTP Out Settings
FTP Out
Interface
Choose either the Management interface or the Ingest interface as the FTP out interface. Vault, ISV
This setting is overridden by the interface the remote FTP client uses to send requests. The
response to the FTP client request always uses the same interface the request came in on.
FTP Out
Bandwidth
Enter the maximum bandwidth (in Mbps) allowed for FTP functionality. Valid entries are Vault, ISV
0 to 1000.
FTP Out
Sessions
Enter the maximum number of FTP out sessions allowed. The range is from 1 to 10.
FTP Listener
Choose either the Management interface or the Ingest interface as the FTP listener. The Vault, ISV
FTP listener selected determines which interface is used for FTP pulls, FTP pushes, and
UDP live ingests. The data transfer for FTP pull depends on how the FTP server at the
remote site is configured. If the FTP server is configured to use eth1 (Ingest), then data
transfer is through eth1. The TV VDS is not directly affected by this setting; however,
most FTP servers use eth1 to send data; therefore, the FTP listener is used for both FTP
pull and FTP push data transfers. With FTP pull ingest, the original title is kept on a FTP
server (catcher) for a period of time, and mechanisms are in place to initiate ingests until
they have successfully completed. Choose either Management (eth0) or Ingest (eth1) as
the interface for FTP in and configure the data source to use the same interface.
Cisco VDS-VR 4.1 Software Configuration Guide
4-72
Vault, ISV
Chapter 4
Configuring the VDS
Server Level Configuration
Table 4-27
Server Setup Fields (continued)
Field
Description
Server Type
IP address of the gateway to the network.
All servers
Network Settings
Gateway
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.
Note
Step 4
Click Submit to save the settings.
To clear the fields and start over, click Reset.
Configuring QoS Settings
The DSCP Marking Method field allows you to set one of the following marking methods:
•
Simple
•
AF Class
•
Custom
Simple
The Simple DSCP Marking Method option allows you to set the DSCP for each of the following types
of traffic:
•
Control DSCP
•
Data DSCP
•
Stream DSCP
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. Control, data, or stream 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 control, data, and stream traffic.
Custom
The Custom DSCP Marking Method option allows you to set the DSCP for each of the following types
of traffic:
•
Control Traffic
•
Stream Traffic
•
Highest Priority Retransmit Traffic
•
Committed Rate Lost Packet Recovery
Cisco VDS-VR 4.1 Software Configuration Guide
4-73
Chapter 4
Configuring the VDS
Server Level Configuration
•
Committed Rate Traffic
•
Mirroring Lost Packet Recovery (Vault only)
•
Mirroring Live Ingest Traffic
•
Drive Failure Repair Traffic (Vault only)
•
Mirroring Traffic (Vault only)
•
Lowest Priority Data Smoothing Traffic (Vault only)
AF Class
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).
DSCP can also be set for HTTP Streamers when HTTP is selected as the cache-fill protocol for VVI on
the CDSM Setup page.
Note
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 4-28 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 4-28
AF Class Drop Probability Configured on Each VDS 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:
Cisco VDS-VR 4.1 Software Configuration Guide
4-74
•
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
Chapter 4
Configuring the VDS
Server Level Configuration
Table 4-28
AF Class Drop Probability Configured on Each VDS Server (continued)
AF1x
Class
AF2x
Class
AF3x
Class
AF4x
Class Data Types
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 Individual Recorder Settings
The Shared Recorder Settings page is used to configure the Recorders in an nDVR system. For more
information, see nDVR Support for NGOD Deployments, page 2-13.
Beginning with VDS-VR (formerly TV VDS) Release 3.4, the Recorder Setup page is used to configure
the recording settings for an ISR.
The Recorder Setup page is used to set individual settings on a Recorder or a ISR and consists of
parameters specific to each Recorder (for example, host name, gateway, component name, and model
name), and shared parameters that can be individualized (for example, Recorder Manager IP address and
port, communication intervals, and thresholds).
When a new Recorder is added to the VDS, the shared Recorder settings are applied to the new Recorder
when the new Recorder is selected on the Recorder Setup page. To apply the shared Recorder settings to
a new Recorder, choose Configure > Server Level > Recorder Setup, from the Recorder IP drop-down
list, select the IP address of the Recorder, and click Display. When the process is complete, a message
displays in the left-panel stating that the Shared Recorder Settings have been applied.
To configure individual settings on a Recorder, do the following:
Step 1
Choose Configure > Server Level > Recorder Setup. The Recorder Setup page is displayed.
Note
If Bulk Configuration is enabled, the Configuration File Location field is displayed, along with
the Browse, Import, and Export buttons. To export the configuration of this page for all VDS
servers in the system, click Export. To import a Bulk Configuration XML file, click Browse to
locate the file, then click 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 Bulk Import/Export
Configuration, page F-4. For information about the Bulk Configuration feature and creating a
Bulk Configuration file, see Creating Bulk Configuration Files, page B-1
Cisco VDS-VR 4.1 Software Configuration Guide
4-75
Chapter 4
Configuring the VDS
Server Level Configuration
Step 2
Note
Step 3
From the Recorder IP drop-down list, choose the IP address or host name of the server and click
Display. The Recorder Setup fields current settings are displayed with the shared settings displayed
where applicable.
If you change the "Current Setting" for fields marked with a “*” those values will over-ride the Shared
Recorder Settings ("Shared Settings" below) set on the Configure > System Level > Shared Recorder
Settings page. To overwrite this Recorder's current values with the Shared Recorder Settings click the
Sync button below.
Enter the settings as appropriate. See Table 4-29 for descriptions of the fields.
Table 4-29
Recorder Setup Fields
Field
Description
Recorder Management
Host Name
Fully qualified hostname for this server. The name can be up to 64
characters long. Assigning a hostname is optional.
Gateway
IP address of the gateway to the network.
HTTP DSCP
DSCP value for the transmitted HTTP IP packet. The range is from 0 to
63 and the default value is 36.
Recorder Status
Read-only field. Recorder status is one of the following:
•
Operational
•
Offline
•
Failed
C2 HTTP Index Setting
Informational only. The C2 HTTP index is enabled or disabled.
Dynamic Trickmodes
Informational only. Displays the settings for the Dynamic Trickmodes.
For more information on setting this field, see the Configuring MPEG
Tuning section in the Configuring the VDS chapter of this guide.
Recorder Behavior
Component Name
Read-only field. The system name given to this Recorder.
Model Name
Read-only field. The CDE model of this Recorder.
Recorder Manager
IP address of the Recorder Manager. The Recorder Manager port is port
number 80.
Retry Status Attempts
The number of times the Recorder tries to send undelivered or
unprocessed status messages to the Recorder Manager. A status
message is undelivered if the Recorder cannot connect to the Recorder
Manager. A status message is unprocessed if the Recorder Manager
responds with a HTTP 500 status.
This field can have a value in the range 0 through 100. A value of 0
disables the retry status message delivery feature.
The default value for this field is 3.
Cisco VDS-VR 4.1 Software Configuration Guide
4-76
Chapter 4
Configuring the VDS
Server Level Configuration
Table 4-29
Recorder Setup Fields (continued)
Field
Description
Retry Status Interval
The time in seconds between successive attempts by the Recorder to
send undelivered or unprocessed status messages to the Recorder
Manager.
This field can have a value in the range 60 through 3600 seconds.
The default value for this field is 60 seconds.
Recording Validation Age
When it receives a validation request, the Recorder lists the COIDs of
all recordings older than the value of this field for validation by the
Recorder Manager.
The value of this field must be specified as a number of days. The value
must be in the range of 1 through 10 days.
The default value of this field is 3 days.
NTP Server
IP address of NTP server.
Heartbeat Interval
Amount of time (in seconds) to wait between sending heartbeat
messages to the Recorder Manager. The range is from 2 to 30. The
default is 5.
Recorder Location
Name of the location of the Recorder. The name can be from 1 to 128
characters in length.
Recording Modify
Time window (in seconds) before a recording starts in which an operator
can modify recording parameters; after which, any changes will be
rejected (except end time). The end time can be modified even after the
configured time window has passed. If the change to the end time
specifies a time that is before the current time, the Recorder stops the
recording.
The range is from 1 to 60. The default is 5.
SCTE-35 Ad Markers
Choose either to Retain or Discard the SCTE-35 Ad markers. If
SCTE-35 markers are discarded, both the PID in the PMT and the data
are removed. If the SCTE-35 markers are preserved, the Recorder places
the SCTE-35 Ad markers in the index file.
Recorder Port
Port number on the Recorder used for management communications
with the Recorder Manager. The range is from 50005 to 65535. The
default is 50005.
Protocol Version
Communication protocol version of the interface between the Recorder
and Recorder Manager.
You can choose one of the following from the drop-down list:
•
I02 - Comcast R8 I02 protocol.
•
I04 - Comcast R8 I04 protocol.
The default is I02.
Threadpool Size
Read-only field. Number of message processing threads of the
Recorder. The default is 16.
Status Report Interval
Read-only field. How often (in seconds) the Recorder reports status
information to the Recorder Manager. The default is 60.
Cisco VDS-VR 4.1 Software Configuration Guide
4-77
Chapter 4
Configuring the VDS
Server Level Configuration
Table 4-29
Recorder Setup Fields (continued)
Field
Description
HTTP Request Timeout
Read-only field. Time that the Recorder application waits for an HTTP
request after it is signaled. The default is 5 seconds.
HTTP Response Timeout
Read-only field. Time that the Recorder application waits for an HTTP
response. The default is 5 seconds.
Manager Notify Thresholds
Recording Bandwidth
Threshold, as a percentage, for recording bandwidth. If this threshold is
exceeded (that is, if the bandwidth used for ingesting recordings
exceeds the configured percentage), the Recorder sends a notification to
the Recorder Manager. The range is from 1 to 100. The default is 1.
Delivery Bandwidth
Threshold, as a percentage, for delivery bandwidth. If threshold is
exceeded (that is, if the bandwidth used for delivering recordings
exceeds the configured percentage), the Recorder sends a notification to
the Recorder Manager. The range is from 1 to 100. The default is 1.
Storage Capacity
Threshold, as a percentage, for storage capacity. If threshold is exceeded
(that is, if the disk storage used on the Recorder exceeds the configured
percentage), the Recorder sends a notification to the Recorder Manager.
The range is from 1 to 100. The default is 1.
Location Virtual IP
Location Virtual IP
IP address the Recorders use 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 in the Product Overview chapter of this guide.
Location Subnet Mask
Subnet mask for the Location Virtual IP.
Media Capture Engine
Step 4
Media Capture IP
The IP address of the MCE+ component.
Media Capture Port
The port on which MCE+ runs the HTTP server utility.
Media Capture UDS Dir
The directory to which Unix domain socket downloads the ATS
segments.
Click Submit to save the settings.
Configuring the Route Table
The Route Table provides the ability to define multiple subnets on a server that apply 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 four different route types:
Cisco VDS-VR 4.1 Software Configuration Guide
4-78
Chapter 4
Configuring the VDS
Server Level Configuration
•
CServer Source (written to the SubnetTable file)
•
CServer Destination (written to the RoutingTable file)
•
Linux Destination
•
Linux Source
Each route type has a different function, and each route type is written to a different file on the VDS
server.
Note
Beginning with VDS-VR (formerly TV VDS) Release 3.4, the Stream Control Route type has been
replaced with a more general procedure of creating Linux Source and Linux Destination routes for
Stream Control interface.
Note
You cannot have intersecting subnets for any defined routes for CServer Source or CServer
Destination.Similarly, you cannot have intersecting subnets for any defined routes for Linux Source and
Linux Destination subnets.
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 (see Configuring the Interfaces, page 4-65), and IP
addresses for the interfaces are set on the Server Setup page (see Configuring the Servers, page 4-69).
Figure 4-25 shows an example of interfaces configured for multiple subnets on a Streamer.
Figure 4-25
Subnet Configuration Example on Streamer
Table 4-30 shows the possible configuration settings to use to define the subnets described in
Figure 4-25.
Table 4-30
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
Cisco VDS-VR 4.1 Software Configuration Guide
4-79
Chapter 4
Configuring the VDS
Server Level Configuration
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.
Linux Destination Route Type
Linux Destination Route is generalization of previously existing Stream Control Route and can be
created independently of an interface.When Linux Destination is selected from the Route Type
drop-down list, a corresponding Linux Source Route should also be created containing the IPs of one of
the interfaces (e.g. a stream control interface, ethX) defined in the interface setup page, as well as
containing the Linux Destination Route Gateway IP. The Linux Destination route is then written to the
file route-ethX, which is used to add routes to the routing table when the system reboots.
Note
For Linux Destination, if a corresponding Linux Source route and/or corresponding interface is not
present, a special route will not be created in the system and Default Gateway will be used. No
route-ethX file will be written for such a Linux Destination route.
Linux Source Route Type
When Linux Source is selected from the Route Type drop-down list, a gateway for a Default Control
interface whose IP address is contained in this network is defined. So, for a Default Control interface
ethX with IP <ip3>, a Linux Source route should be defined that contains <ip3>. This route then gets
written to the shared_intf_setp. A Linux Destination route is not necessary for the Default Control
interface.
Configuring the SNMP Agent
The SNMP Agent sets up SNMP on the VDS. SNMP management features on the servers include:
•
SNMPv1, SNMPv2c, and SNMPv3
•
Standard MIBs
SNMPv3 adds support for user-password-based authentication and access control. SNMPv3 also
optionally allows encryption of all SNMP communications, including objects contained in a response to
a GET or inside traps (notifications or INFORMs).
While SNMPv3 provides multiple ways of implementing authentication, access control, and encryption,
the TV VDS software has the following implementation:
•
User-Based Security Model
•
View-Based Access Control Model
For more information about SNMP on the VDS, see SNMP MIB and Trap Information, page D-1.
Cisco VDS-VR 4.1 Software Configuration Guide
4-80
Chapter 4
Configuring the VDS
Server Level Configuration
User-Based Security Model
The User-based Security Model (USM), which provides SNMP message-level security, is implemented
as follows:
•
Users are created (configured) in the SNMP agent on a VDS server through the CDSM GUI, as well
as on the Network Management Station (NMS).
•
Password-based authentication is optional, and if enabled, the user must have an associated
authentication key (password) of a minimum length of eight characters, and an authentication
protocol of either HMAC-MD5 or HMAC-SHA1.
•
Encryption is optional, if enabled, an encryption key (a minimum of eight characters) is required,
and an encryption protocol of DES or AES.
View-Based Access Control Model
The View-based Access Control Model (VACM) is used for controlling access to management
information. The TV VDS software implements VACM by allowing configuration of each management
object (OID) or group of OIDs on a VDS server through the CDSM GUI to be exposed with read-only
or read-write access to a configured user.
Note
The SNMPv2c security model that uses community strings for read-only or read-write access is still
supported. SNMPv3 USM and VACM are optional.
Trap Community Enhancements
The configuration of a per-trap-sink community string or a default community string is supported. The
supported notifications are: SNMPv1 TRAPs, SNMPv2 NOTIFICATIONS, and SNMPv2-inform
INFORM. Each trap sink, associated with a different trap station, can have optional default community
strings that are used when sending traps. Alternatively, a default trap community string can be
configured, which is used if the per-station community string is not configured.
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.
Note
If Bulk Configuration is enabled, the Configuration File Location field is displayed, along with
the Browse, Import, and Export buttons. To export the configuration of this page for all VDS
servers in the system, click Export. To import a Bulk Configuration XML file, click Browse to
locate the file, then click 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 Bulk Import/Export
Configuration, page F-4. For information about the Bulk Configuration feature and creating a
Bulk Configuration file for the SNMP settings, see Creating Bulk Configuration Files, page B-1
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 4-31.
Cisco VDS-VR 4.1 Software Configuration Guide
4-81
Chapter 4
Configuring the VDS
Server Level Configuration
Table 4-31
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.
Default Trap
Community
Default trap community string shared between this SNMP agent and a network
management system that might receive traps.
Community Authentication
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.
User-based Security Model
User Name
Name of a user defined in this SNMP agent (also known as SNMP engine). The
same name is defined and used in a network management station (NMS).
Authentication
Type
Protocol used for user authentication is either MD5 or SHA-1. Both are used in
conjunction with HMAC. The default is MD5.
Authentication
Password
Password used for user authentication; the minimum length is eight characters.
Encryption Type
Protocol used for encryption is either DES or AES.
Encryption is not enabled unless Encryption is selected in the VACM
Authentication drop-down list.
Note
Encryption
Password
Password used for encryption; the minimum length is eight characters.
View-based Access-Control Model
User Name
Name of user granted access to the specified object or OID sub-tree.
Access
Permissions granted to this user for this object or OID sub-tree is either
read-only (GET) or read-write (GET/SET).
Currently, VDS-TV objects support only GET requests.
Note
Authentication
OID
Authentication types available are the following:
•
None—Only user name is matched, no passwords.
•
Authentication—Password-based user authentication is used. Both
username and password must match to get access.
•
Encryption—Password-based user-authentication is used; additionally,
SNMP traffic is encrypted.
Specific object or OID sub-tree the user is able to access.
Note
Cisco VDS-VR 4.1 Software Configuration Guide
4-82
If OID field is left blank, it means all OIDs are accepted.
Chapter 4
Configuring the VDS
Server Level Configuration
Table 4-31
SNMP Agent Fields (continued)
Field
Description
Trap Management
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 (TRAP)
•
v2 (NOTIFCATION)
•
v2-inform (INFORM)
SNMP v2-inform sends a message received to the NMS upon receiving an NMS
message.
Note
Trap Community
Step 4
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.
(Optional) Trap community string shared between this SNMP agent and the
configured trap station. If empty, the default trap community string is used, if
available.
Click Submit to save the settings.
To clear the fields and start over, click Reset.
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, USM, VACM, and stations. To add
additional entries, click the plus sign in that section. To remove empty entries, click the minus sign. If
you want to delete an SNMP community or station, check the Delete check box associated with the entry
and click Submit.
Configuration Rules and Guidelines for USM and VACM
The following rules and guidelines apply to configuring USM and VACM entries:
Note
•
There is a one-to-one relationship between a USM entry and a VACM entry.
•
For every username in VACM, there must be a matching username in USM.
•
All usernames must be unique for both USM and VACM entries.
•
Only one OID per VACM username is allowed.
•
If the VACM entry has an Authentication setting of None, then the USM password is not verified,
which means the user is not required to enter the authentication password when accessing the OID
associated with the corresponding VACM entry.
•
If the VACM OID field is left blank, it means the user can access all OIDs.
The Cisco VDS-VR MIBs, as well as the supporting Cisco MIBs, are available for download at the
bottom of the SNMP Agent page.
Cisco VDS-VR 4.1 Software Configuration Guide
4-83
Chapter 4
Configuring the VDS
Server Level Configuration
Configuring the Server Level DNS
The Server DNS page is used to configure up to 16 domain suffixes and 16 DNS servers.
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 4-26).
Note
If Bulk Configuration is enabled, the Configuration File Location field is displayed, along with
the Browse, Import, and Export buttons. To export the configuration of this page for all VDS
servers in the system, click Export. To import a Bulk Configuration XML file, click Browse to
locate the file, then click 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 Bulk Import/Export
Configuration, page F-4. For information about the Bulk Configuration feature and creating a
Bulk Configuration file for the DNS servers, see Creating Bulk Configuration Files, page B-1
Figure 4-26
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 Server Level settings as appropriate. See Table 4-32 for descriptions of the DNS fields.
Cisco VDS-VR 4.1 Software Configuration Guide
4-84
Chapter 4
Configuring the VDS
Server Level Configuration
Table 4-32
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 Server Level NTP
The NTP Server page is used to configure up to 16 NTP servers. The clocks on all VDS servers (Vault,
Streamer, and Caching Node) and the CDSM and VVIM in a VDS 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, Import, and Export buttons. To export the configuration of this page for all VDS
servers in the system, click Export. To import a Bulk Configuration XML file, click Browse to
locate the file, then click 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 Bulk Import/Export
Configuration, page F-4. For information about the Bulk Configuration feature and creating a
Bulk Configuration file for the NTP servers, see Creating Bulk Configuration Files, page B-1
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.
Cisco VDS-VR 4.1 Software Configuration Guide
4-85
Chapter 4
Configuring the VDS
Server Level Configuration
Other NTP Configurations
In addition to configuring the IP addresses of the NTP servers, you need to set the time zone on each
VDS server, as well as configure the NTP servers for the CDSM and VVIM.
Setting the Time Zone on a VDS Server
To set the time zone on a VDS server, log in to the VDS 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
Cisco VDS-VR 4.1 Software Configuration Guide
4-86
Chapter 4
Configuring the VDS
Server Level Configuration
You will see the following:
ntpd
Step 3
0:off
1:off
2:on
3:on
4:on
5:on
6:off
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
Step 7
If the system clock is off by a significant amount, the command takes a considerable amount of
time to return.
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
Cisco VDS-VR 4.1 Software Configuration Guide
4-87
Chapter 4
Configuring the VDS
Server Level Configuration
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 VDS. Table 4-33 describes each type
of deployment.
Table 4-33
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, Import, and Export buttons. To export the configuration of this page for all VDS
servers in the system, click Export. To import a Bulk Configuration XML file, click Browse to
locate the file, then click 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 Bulk Import/Export
Configuration, page F-4. For information about the Bulk Configuration feature and creating a
Bulk Configuration file for the RTSP settings, see Creating Bulk Configuration Files, page B-1
Cisco VDS-VR 4.1 Software Configuration Guide
4-88
Chapter 4
Configuring the VDS
Server Level Configuration
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 4-27).
Figure 4-27
Step 3
RTSP Setup Page for RTSP Deployment
Enter the RTSP settings as appropriate. Table 4-34 describes each field and lists the associated RTSP
deployment.
Note
If you change any of the RTSP Setup settings, you must resubmit the Control/Setup IP page. For
more information, see Configuring the Control and Setup IPs, page 4-50.
Table 4-34
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 Configuring the Control and Setup IPs,
page 4-50.
All
Looping Session
Timeout
Activity timeout value for looping streams (carousels). RTSP
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).
Session Inactivity
Timeout
Timeout value for tearing down a session. The default is RTSP, NGOD,
IPTV, Quative,
360000 milliseconds (6 minutes). If the Session
Inactivity Timeout is set to zero (0), the session liveness EventIS, Cisco
is not checked.
Cisco VDS-VR 4.1 Software Configuration Guide
4-89
Chapter 4
Configuring the VDS
Server Level Configuration
Table 4-34
RTSP Fields for All Deployment (continued)
Field
Description
RTSP Deployment
Callback Server IP
IP address of the callback server. The VDS 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
DSM-CC, RTSP,
Timeout value for closing a connection to the
NGOD, Quative,
backoffice. If a message is not received from the
backoffice within the time specified in the Backoffice Cisco
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.
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 IP1
Authentication Manager resides on the master Streamer. EventIS, Cisco
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 Configuring the
Authentication Manager, page 4-14.
Authentication
Manager Port1
Authentication Manager port number is determined by EventIS, Cisco
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
Configuring the Authentication Manager, page 4-14.
The default is 7792.
Bandwidth Manager
IP1
Bandwidth Manager resides on the master Streamer.
Typically, the Bandwidth Manager IP address is the
same as that of the master Streamer.
Note
The Bandwidth Manager for the EventIS on
vpath FSI Setup is not the same as the
Bandwidth Manager for Thin Pipe Mapping.
Bandwidth Manager
Port1
Bandwidth Manager port number default is 7791. This EventIS on vpath
port number is determined by the configuration settings
in the Bandwidth Manager.
Backup Bandwidth
Manager IP1
IP address of the network interface card (NIC) you want EventIS on vpath
the Bandwidth Manager to bind to in case the primary
Bandwidth Manager IP and port fail.
Backup Bandwidth
Manager Port1
Port number to listen on for incoming connections from EventIS on vpath
the RTSP server. The default is 7791. The minimum port
number you can allocate is 150. The maximum port
number is 60000.
Cisco VDS-VR 4.1 Software Configuration Guide
4-90
EventIS on vpath
Chapter 4
Configuring the VDS
Server Level Configuration
Table 4-34
RTSP Fields for All Deployment (continued)
Field
Description
RTSP Deployment
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 VDS 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 VDS
RTSP server.
EventIS off vpath,
Cisco
Backup Session
Resource Manager IP
IP address of the network interface card (NIC) you want Cisco
the SRM to bind to in case the primary SRM IP and port
fail.
Backup Session
Resource Manager
Port
Port number you want the SRM to use in case the
primary SRM IP and port fail.
Stream Control IP
IP address used by the STB for communication of
EventIS off vpath
trick-mode requests to the VDS RTSP server. This does
not have to be the same IP address as the Control IP.
Stream Control Port
Port number used by the STB for communication of
trick-mode requests to the VDS 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 RTSP
number on the Streamer used to receive the requests to
reconnect.
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
NGOD
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.
Cisco
Cisco VDS-VR 4.1 Software Configuration Guide
4-91
Chapter 4
Configuring the VDS
Server Level Configuration
Table 4-34
RTSP Fields for All Deployment (continued)
Field
Description
RTSP Deployment
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
Maintenance Mode
From the Maintenance Mode drop-down list, choose
one of the following:
All
•
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.
1. The Authentication Manager and Bandwidth Manager fields are not displayed if these features are not part of your
deployment.
Step 4
Configure the clients that will communicate with the Streamer. The clients consist of the set-top boxes,
which typically require only one client definition.
The client configuration is displayed in a delimited string format:
1)rtsp | 3636 | 3636 | 65535 | quative | parameters | TCP
In this format, rtsp is the deployment, 3636 is the receive port on the Streamer and the receive port on
the client, 65535 is the receive buffer size, quative is the client model, parameters is the message payload
type, and TCP is the transport protocol.
•
To edit an existing client, click Edit next to the client definition.
•
To delete an existing client, click Delete next to the client definition.
•
To add a new client, click Add New Client.
Table 4-35 describes the fields for the client definitions.
Table 4-35
Client Configuration Fields
Field
Description
Receive Port
Port used for receiving messages from the client.
Send Port
Port used to send messages to the client.
Receive Buffer
Receive buffer size, in bytes, for the listener socket. The receive buffer can
be set to either 65535 for TCP transport or 512000 for UDP transport.
Quative and Cisco always uses TCP transport.
Cisco VDS-VR 4.1 Software Configuration Guide
4-92
Chapter 4
Configuring the VDS
Server Level Configuration
Table 4-35
Client Configuration Fields (continued)
Field
Description
Model
Client model type to use for communication with the client. The types are:
•
nCUBE
•
Digeo
•
NGOD
•
Myrio
•
Quative
•
EventIS
•
Cisco
A client model of nCUBE means the client uses RTSP with nCUBE syntax.
A Digeo client model uses Digeo syntax, and so on.
Transport
Note
Step 5
Transport protocol, either UDP or TCP, used for streaming. The transport
protocol is always TCP for Quative and Cisco.
If you change any of the RTSP Setup settings, you must resubmit the Control/Setup IP page. For
more information, see Configuring the Control and Setup IPs, page 4-50.
Click Submit.
To clear the fields and start over, click Reset.
Configuring FSI Setup
The File Service Interface (FSI) allows the backoffice to communicate file-related requests to the Vault.
These requests include ingesting content, preparation of content files (for example, trick mode creation),
and distribution of the content.
To configure the FSI settings, do the following:
Step 1
Choose Configure > Server Level > FSI Setup. The FSI Setup page is displayed.
Note
If Bulk Configuration is enabled, the Configuration File Location field is displayed, along with
the Browse, Import, and Export buttons. To export the configuration of this page for all VDS
servers in the system, click Export. To import a Bulk Configuration XML file, click Browse to
locate the file, then click 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 Bulk Import/Export
Configuration, page F-4. For information about the Bulk Configuration feature and creating a
Bulk Configuration file for the FSI settings, see Creating Bulk Configuration Files, page B-1
Cisco VDS-VR 4.1 Software Configuration Guide
4-93
Chapter 4
Configuring the VDS
Server Level Configuration
Step 2
From the Vault Select drop-down list, choose an IP address and click Display. The FSI settings for the
specified server are displayed.
Step 3
Enter the FSI settings as appropriate. See Table 4-36 for descriptions of the fields.
Table 4-36
FSI Fields
Field
Description
FSI IP Address
IP address of the Vault used in FSI communications with the backoffice. The
recommended configuration is to enter 0.0.0.0 to allow all incoming IP interfaces
on the Vault to be used for FSI communications.
FSI Server Port
Port number on the Vault used in FSI communications with the backoffice. The
default is 20004.
FTP Client Port
Port used by FSI communications when connecting to the catcher, or other FTP
server, to pull in content, and when the FTP port is not specified in the ingest
URL. The default is 21.
FTP Out Server
Port
Port used by FSI communications for egress (FTP out pulls) from the Vault. We
recommend setting the FTP Out Server Port to 5500.
FTP Out Login TTL Time, in seconds, an FTP client has to connect and log in to the Vault to perform
an FTP out pull with a temporary login. The default is 60.
FSI Content Root
Path
Root directory used to store MPEG content files on the Vault. This field is used
in both nABLE and NGOD RTSP deployments. The default is /files.
Note
Async. Callback
URL
Step 4
The FSI Content Root Path must be set to /files; otherwise, the FSI
process does not function correctly.
For IPTV deployments only. The asynchronous callback URL is where the
recording completion notification is sent when a scheduled recording completes
its capture. This URL is basically used to tell the client the recording is
completed.
Click Submit.
To clear the fields and start over, click Reset.
Configuring the Server Level Logging
All logs are located in the /arroyo/log directory. The log files are rotated at least once a day and time
stamps are added to the filenames. Some log files that grow rapidly are rotated more frequently
(determined by file size); this rotation may happen up to once an hour. Most log files have the following
suffix: log.<YYYYMMDD.> The time zone for log rotation and filename suffixes is coordinated
universal time (UTC). As part of the new log entry format, the log level and facility are included.
All log entries have the following changes:
•
Stream handle is represented in decimal format
•
IP addresses are represented in dotted-decimal format
•
Clear identification of where a stream is going rather than a MAC address
•
Time is represented in UTC
Cisco VDS-VR 4.1 Software Configuration Guide
4-94
Chapter 4
Configuring the VDS
Server Level Configuration
•
Global Object ID (GOID) is represented in hexadecimal
Stream Trace
Log messages currently in the streamevent.log file are converted to a structured message and assigned
the “stream trace” facility number. Other messages that record stream creation, routing, or playout are
converted to a structured message and assigned the “stream trace” facility number. This enhancement,
along with configuring syslog-ng to direct all “stream trace” facility messages to a single, centralized
log server, provides a coherent set of log messages that describe stream history.
Facility Information, and Associated Log File and Debug Flags
For information on each facility and associated log file and debug flags, use the loginfo tool. The loginfo
tool can run on any VDS server, including the CDSM. Start a Telnet or SSH session, log in to the VDS
server, and enter the loginfo command without any arguments. Information on each facility is listed.
Configuring Logging Levels
All logging is configured at the System Level or Server Level. The configuration of the logging levels
at the Server Level overrides the System Level settings.
To set a log level for a facility at the Server Level, do the following:
Step 1
Choose Configure > Server Level > Logging. The Log page is displayed.
Note
If Bulk Configuration is enabled, the Configuration File Location field is displayed, along with
the Browse, Import, and Export buttons. To export the configuration of this page for all VDS
servers in the system, click Export. To import a Bulk Configuration XML file, click Browse to
locate the file, then click 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 Bulk Import/Export
Configuration, page F-4. For information about the Bulk Configuration feature and creating a
Bulk Configuration file for the Logging settings, see Creating Bulk Configuration Files,
page B-1
Step 2
From the Server IP drop-down list, select an IP address.
Step 3
From the Facility Name drop-down list, select a facility and click Display. The Log Level fields are
displayed.
The facilities list is based on the configuration of the system.
Cisco VDS-VR 4.1 Software Configuration Guide
4-95
Chapter 4
Configuring the VDS
Server Level Configuration
Step 4
Enter the Log Level settings as appropriate. See Table 4-12 for descriptions of the fields.
Table 37
Log Level Fields
Field
Description
Local Log Level
The Local Log Level drop-down list has the following options:
•
Emergency (0)
•
Alert (1)
•
Critical (2)
•
Error (3)
•
Warning (4)
•
Notice (5)
•
Informational (6)
A log level setting includes all the more urgent levels. For example, if the log
level is set to Error (3), then Alert (2), Critical (1), and Emergency (0) log entries
are included as well as Error (3).
Step 5
Remote Log Level
To enable remote logging for the selected facility, select the appropriate log level
from the Remote Log Level drop-down list. The default setting is disable.
Debug Flags
Debug messages, if applicable, are configured by setting one or more debug
flags. To select or unselect debug flags, you have the following options:
•
To select one debug flag, click the flag.
•
To select multiple debug flags, hold down the Ctrl key and click each flag,
or hold down the Shift key and click the beginning flag and ending flag.
•
To unselect a debug flag when a group of debug flags are selected, hold
down the Ctrl key and click the flag.
Click Submit.
To clear the fields and start over, click Reset.
To delete the log level settings for a facility, select the facility from the drop-down list and click Delete.
Cisco VDS-VR 4.1 Software Configuration Guide
4-96
Chapter 4
Configuring the VDS
Server Level Configuration
Configuring the Server Level Syslog
The Syslog configuration page at the System Level and Server Level is used to configure the IP address
and port of the server that is to receive remote logging. The configuration of the syslog server at the
Server Level overrides the System Level settings. For remote logging information to be sent for a facility,
the Remote Log Level must be set on the Logging page. See Configuring the Server Level Logging,
page 4-94 for more information.
To configure the remote logging server, do the following:
Step 1
Choose Configure > Server Level > Syslog. The Syslog page is displayed.
Note
If Bulk Configuration is enabled, the Configuration File Location field is displayed, along with
the Browse, Import, and Export buttons. To export the configuration of this page for all VDS
servers in the system, click Export. To import a Bulk Configuration XML file, click Browse to
locate the file, then click 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 Bulk Import/Export
Configuration, page F-4. For information about the Bulk Configuration feature and creating a
Bulk Configuration file for the Syslog settings, see Creating Bulk Configuration Files, page B-1
Step 2
From the Server IP drop-down list, select an IP address.
Step 3
Check the Enable Remote Logging check box.
Step 4
In the IP Address field, enter the IP address of the remote server that is to receive syslog messages.
Step 5
In the Port filed, enter the port of the remote server that is to receive syslog messages.
Step 6
Click Submit.
To clear the fields and start over, click Reset.
To delete the remote server settings, click Delete.
Cisco VDS-VR 4.1 Software Configuration Guide
4-97
Chapter 4
Configuring the VDS
Server Level Configuration
Configuring Server Level Error Repair
The VOD Error Repair settings can be configured on the System Level, Array Level, and the Server
Level. Settings configured at the Array Level take precedence over System Level settings, and settings
at the Server Level take precedence over Array Level or System Level settings.
Note
VOD Error Repair is a licensed feature. VOD Error Repair requires the LSCP Client Protocol be set to
Cisco (RTSP) and the STB have the Cisco Visual Quality Experience Client (VQE-C) software running
on it. For more information, see VOD Error Repair, page F-7.
To configure error repair at the Server Level, do the following:
Step 1
Choose Configure > Server Level > Error Repair. The Error Repair page is displayed.
Step 2
From the Server IP drop-down list, select an IP address and click Display.
Step 3
Enter the Error Repair settings as appropriate. See Table 4-38 for descriptions of the fields.
Table 4-38
VOD Error Repair Fields
Field
Description
Repair Packets DSCP
DSCP of Repair Packets Sent
DSCP value for the transmitted RTP and RTCP packets sent for error
repair. The range is from 0 to 63. The default is 0.
RTCP Report Exporting
Step 4
Exporting
Click the Enabled radio button to enable exporting of the RTCP
reports. The RTCP reports can be exported to a third-party analysis
application.
IP Address
Enter the IP address or the domain name of the server hosting the
analysis application.
TCP Ports
Enter the TCP port number that is used to receive the reports on the
server hosting the analysis application.
Click Submit.
To clear the fields and start over, click Reset.
To return the settings to the factory default values, click Factory.
To delete the settings, click Delete.
To monitor the VOD Error Repair feature, use the Application Monitoring Tool (AMT). For more
information, see Using the VDS Streamer Application Monitoring Tool, page E-1
Cisco VDS-VR 4.1 Software Configuration Guide
4-98
Chapter 4
Configuring the VDS
Server Level Configuration
Configuring Live Database Backup
The database (AVSDB) of a Recorder can be duplicated on a backup server in real time using the Live
Database Backup service. A simple copy of the database files performed while a write operation is in
progress is likely to have errors because successive records are not written to successive file locations.
Live Database Backup offers a better backup solution by taking the write sequence into account.
Note
Live Database Backup does not work across different software versions. Before performing a software
upgrade or downgrade, shut down Live Database Backup on the backup server and all of its clients, and
only restart the service when the backup and all clients are running the same software version.
Backup Design
Live Database Backup currently supports two possible backup designs:
•
Client and server located on the same Recorder (same IP address for both)
•
Client and server located on different Recorders (different IP address for each)
The recommended approach is to have the backup server installed on each Recorder point to another
Recorder in the same cluster, thus forming a daisy-chain loop. This configuration avoids the potential
for bottlenecks from a single point of failure that could occur when using a centralized backup server for
all Recorders.
Bandwidth Management
Live Database Backup transports all data in the database and the transaction logs to the backup server
via the management network. The load on the network is especially great during the initial setup, when
both client and server go through initial sync-up and initiate a bulk transfer of all data to the backup side.
Live Database Backup tries to use all available network bandwidth so that bulk transfer occurs as quickly
as possible. Therefore, recommended practice is to start the live backup service and initial bulk sync-up
sequentially in the cluster at a time when the Recorder is not heavily loaded.
Following the initial sync-up, Live Database Backup performs incremental backups, transferring data
only when updates occur on the client side. Even under heavy load, the traffic required for incremental
backups are minimal.
The following message in the Live Backup log (livebackup.log) shows the bulk sync phase starting and
completing before entering incremental backup:
2015.08.10 17:29:46.346877 UTC
/home/isa/bss/database/live_backup_svr:livb_session_database_setup.c:livb_session_database
_setup():407: NOTICE: DB_ENV->rep_start() successful
...
[bulk sync up phase...]
...
2015.08.10 18:29:04.306399 UTC
/home/isa/bss/database/live_backup_svr:livb_server_event_handler.c:live_backup_event_handl
er():201: NOTICE: (Session 1.1-10.74.17.123:42841) synchronization completed (using socket
5)
Note
We recommend enabling and starting Live Database Backup during off-peak hours, especially if many
Recorders are involved, so as to minimize any potential impact to recording functions.
Cisco VDS-VR 4.1 Software Configuration Guide
4-99
Chapter 4
Configuring the VDS
Server Level Configuration
Using the CDSM GUI
To configure Live Database Backup at the server level, follow these steps:
Step 1
Go to Configure > Server Level > Recorder Live DB Backup.
Step 2
From the Recorder IP drop-down list, choose the IP address of the desired recorder and click Display.
Step 3
See the table below for the descriptions of the fields and configure the Recorder Live DB Backup
Settings appropriately.
Table 4-39
Recorder Live DB Backup Settings Fields
Field
Description
Live Backup Service
Click the appropriate radio button to enable or disable the service.
The service is disabled by default.
When the service is enabled, the Recorder database is duplicated on a backup
server.
Primary Backup
Server IP
Secondary Backup
Server IP
The IP address of the primary backup server.
By default, this field is set to 127.0.0.1, and the files will be backed up locally.
Note
VDS-VR (Formerly TV VDS) Release 3.8 does not support backing
up of the Recorder database on a secondary server. Although this field
is available in the CDSM GUI, its value does not affect the
configuration of the Live Database Backup service.
The IP address of the secondary backup server.
If a value is not specified for this field, this field shall have the Primary
Backup Server IP value.
Logging Interval
Determines how frequently the Recorder database will be duplicated on the
backup servers.
The default logging interval is 30 seconds.
Overall Max
Bandwidth
The maximum bandwidth that can be used by the live database backup
service.
The default value of this field is Unlimited.
Per Session
Max Bandwidth
The maximum bandwidth that can be used by each session of the live database
backup service.
The default value of this field is Unlimited.
Step 4
To save the settings, click Submit.
To clear your changes, click Reset.
Based on the settings configured through the CDSM, the statsd process writes the following files on the
Recorder:
•
/home/isa/livebackup/client.config
•
/home/isa/livebackup/server.config.<backup server ip>
Cisco VDS-VR 4.1 Software Configuration Guide
4-100
Chapter 4
Configuring the VDS
Server Level Configuration
Step 5
To configure the backup server, copy the server configuration file
/home/isa/livebackup/server.config.<backup server ip> from the Recorder to the backup server as
/home/isa/livebackup/server.config.
Using the CLI
To configure Live Database Backup from the command line, create or modify the client and backup
server configurations to match your network environment, as shown in the following examples.
Backup Server Example:
/home/isa/livebackup/server.config:
operation_address 10.74.17.25
operation_port 9993
management_address 10.74.17.25
management_port 9994
Client Server Example:
/home/isa/livebackup/client.config:
operation_address 10.74.124.238
operation_port 9991
management_address 10.74.124.238
management_port 9992
primary_server_address 10.74.17.25
primary_server_port 9993
Cisco VDS-VR 4.1 Software Configuration Guide
4-101
Chapter 4
Server Level Configuration
Cisco VDS-VR 4.1 Software Configuration Guide
4-102
Configuring the VDS
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising