Engineering Access Level Pages
This appendix describes the VVIM or CDSM pages available through the Engineering access level. The Engineering access level provides the following pages:
The Engineering access level is primarily used for initializing the CDS at the time of installation and for system diagnostics. After your system has been configured, you should not require an engineering access level user for day-to-day operations.
When you log in to the CDSM with a user account that has Engineering access level, the first page that is displayed is the CDSM Setup page. All the other CDSM pages that are available with the Master access level are still available with the Engineering access level.
In an RTSP environment, the Configure > Server Level > RTSP Setup page displays four additional fields:
- Database Connect Size
- UDP Packet Size
- Threadpool Size
- Max Sessions
These fields are only for diagnostic purposes, and their values should not be changed.
NoteWhen you configure the CDSM for Virtual Video Infrastructure (VVI), all references to CDSM are changed to Virtual Video Infrastructure Manager (VVIM) for the Vault and Caching Node manager. For example, the CDSM Audit Logs available through the When you configure the CDSM for Virtual Video Infrastructure (VVI), all references to CDSM are changed to Virtual Video Infrastructure Manager (VVIM) for the Vault and Caching Node manager. For example, the CDSM Audit Logs available through the Report > System Level left-panel menu is changed to the VVIM Audit Logs when VVI is configured on the CDSM Setup page, which changes to the VVIM Setup page.
CDSM or VVIM Setup
The CDSM or VVIM Setup page is used to initially configure the CDS. After you have set the CDSM or VVIM Setup fields for your system, click Submit . Configuration and start up messages are displayed in the left panel.
Deployed CServer Version
This field is always set to 2.X.
Stream Failover Support
Stream failover support is available for both the ISA and RTSP environments. If a Streamer fails, another Streamer in the same Stream Group takes over any active stream sessions without loss of state and backoffice independence.
Stream Steering Mode
Stream steering determines which Streamers serve streams to a QAM device. There are two types of stream steering:
- Single site (Silo site steering)
Single-site steering uses only one Stream Group to serve streams to all QAM devices. Multi-site steering can use more than one Stream Group to serve streams to the QAM devices. The QAM Gateway page reflects whether single-site or multi-site steering is enabled, by the number of preference levels available. Multi-site steering offers four preference levels (high, medium, low, and none). Single-site steering offers two preference levels (high and none).
NoteMulti-site steering is available only with ASI streaming in an ISA environment. Multi-site steering is available only with ASI streaming in an ISA environment.
Deployment Network Config
Specify whether your CDS network topology is a Layer 2 or Layer 3 network.
The only options are ISA 2.X and RTSP 2.X .
The possible settings for Stream Destination are Cable and IPTV .
The cable setting is the existing configuration with the QAM Gateway page and Headend Setup page, which allows you to map Stream Groups to QAM devices and service groups if applicable.
The IPTV setting provides the Stream Destination page in place of the QAM Gateway page and Headend Setup page. The Stream Destination page allows you to map the Stream Groups to specified subnets, which is useful in IPTV networks where each end-user has an IP address.
An option for ISA environments using the IPTV setting for the Stream Destination is the NAT option. The NAT Traversal feature allows streaming to client devices that are behind a NAT device.
NoteThe Stream Destination feature is available only for single-site steering. The Stream Destination feature is available only for single-site steering.
Parent/Child Service Groups
Parent/Child Service Groups is an optional feature and is only for ISA environments that use ASI streaming. The Parent/Child Service Groups page allows finer granularity of the service groups.
Redirect Server is an optional feature for RTSP environments. The RTSP server on the Streamer sends a redirect to the “best” Streamer to serve the content. When set to ON , the Redirect Server configuration page is displayed at the System Level, and you can specify the port number used to receive the redirect requests, as well as set the debug level.
Bulk Configuration provides a method of configuring common configuration parameters for all the servers at one time by means of an XML file. Following are the CDSM GUI configuration pages that offer bulk configuration:
- QAM Gateway
- Headend Setup
- Stream Destination
- NTP Server
- Server DNS
- SNMP Agent
- Route Tables
- RTSP Setup
- FSI Setup
When SSV Groups is enabled, Stream Groups, Vault Groups, and Cache Groups are disabled.
NoteThe SSV Group optional feature is only applicable to RTSP environments and for a CDS that uses only ISVs. The SSV Group optional feature is only applicable to RTSP environments and for a CDS that uses only ISVs.
The Thin Pipe Map page and Vault Redundancy Map page are also displayed when SSV Groups is enabled. The Vault Redundancy Map page allows mapping of ISVs for mirrored content, and the Thin Pipe Map page allows creation of low-bandwidth connections between local and remote groups.
NoteThe term SSV used in the CDSM GUI is the same as the ISV. The terms are interchangeable. The term SSV used in the CDSM GUI is the same as the ISV. The terms are interchangeable.
When SSV Groups is enabled, all pages referring to Vaults or Streamers display as SSV instead. These pages include the Stream Destination page, the QAM Gateway page, the Headend Setup page, the Control/Setup IP page, and the Vault Redundancy Map page.
Trick Mode Capture
In Release 2.2, Trick Mode Capture is an optional feature. When Trick Mode Capture is enabled, the applicable Stream Activity reports can drill down to the Stream Play History Drilldown, which displays the trick modes for a session ID. Additionally, the Graph Stream button is displayed on the Stream Monitor page. The Stream Activity reports that can drill down to the Stream Play History Drilldown are the following:
- Stream Play History
- Streams by Array
- Streams per STM-MAC
- Bandwidth per Service Group
- Stream Failures
When Trick Mode Capture is disabled, the session ID in the Stream Activity reports no longer links to the Stream Play History Drilldown and the Graph Stream button is removed from the Stream Monitor page.
When Vault Redundancy is enabled and at least two Vault Groups are configured and mapped to each other, at least one copy of each content within a group is mirrored to the configured peer group. Content is mirrored among as many as four Vault Groups (one Vault Group ingests the content and up to three Vault Groups mirror the content), which may be in different geographic regions. The Vault Redundancy adds the Vault Groups and Vault Redundancy Map configuration pages to the Array Level.
NoteIn Release 2.4, the maximum number of Vault Groups is 20. In Release 2.4, the maximum number of Vault Groups is 20.
This feature is not activated in this release.
Thin Pipe Management
Thin Pipe Management allows you to configure low-bandwidth connections between local and remote groups. A local group consists of servers in the same group (Stream Group, Cache Group, Vault Group). A remote group consists of servers in other Stream Groups, Cache Groups, and Vault Groups. Use the Thin Pipe Map page to configure this feature.
Shared Content Store
Shared Content Store is an optional feature for the ISA environment. The Shared Content Store allows one instance of a Content Store to be shared with many instances of Stream Services, each located in its own video hub office (VHO) with its own video backoffice (VBO).
Virtual Video Infrastructure
The Virtual Video Infrastructure (VVI) provides management of the Caching Nodes in a central management configuration or a split-domain management configuration.
When you enable VVI, you need to choose the Management System Role of the CDSM. The Management System Role has the following options:
- VVI and Stream Manager—Central management of all Vaults, Caching Nodes, and Streamers
- VVI (Vault/Cache) Manager—Management of only the Vaults and Caching Nodes
- Stream Manager—Management of only the Streamers
The Cache Fill Protocol options are for selecting the type of data communication that is used between Caching Nodes and Streamers. Cache Control Protocol (CCP) is used for communication among the Vaults, Caching Nodes, and Streamers. For more information about CCP Streamers and HTTP Streamers, see the “Caching Node Workflow” section.
NoteISA environments only support CCP, while RTSP environments only support HTTP for VVI. ISA environments only support CCP, while RTSP environments only support HTTP for VVI.
The split-domain management is made up of the VVI (Vault/Cache) Manager and the Stream Manager. For the Stream Manager to be able to communicate with the VVI Manager, you need to enter the IP address of the VVI Manager in the VVI (Vault/Cache) Manager VVIM IP field.
If CCP is used as the cache-fill protocol, you must provide a name for the Stream Manager in the Stream Domain Name field so that the VVIM can identify it from other Stream Managers. Communication between the VVI Manager and the Stream Manager is accomplished through database replication when using CCP.
If you choose HTTP, communication between the VVI Manager and the Stream Manager uses port 80. If port 80 is not open for communication, you can enter the data manually (used for Stream Group IDs), or upload an XML file (used for Cache Group Locator information), depending on the information required.
NoteWhen you configure the CDSM for Virtual Video Infrastructure (VVI), all references to CDSM are changed to Virtual Video Infrastructure Manager (VVIM) for the Vault and Caching Node manager. When you configure the CDSM for Virtual Video Infrastructure (VVI), all references to CDSM are changed to Virtual Video Infrastructure Manager (VVIM) for the Vault and Caching Node manager.
The VVIM and Stream Managers display different configuration, monitoring, reports, and maintenance pages based on the servers they manage. For example, when CCP is the cache-fill protocol, the VVIM displays the Configuration Generator page in the Maintenance > Software left-panel menu. The Configuration Generator page is used to generate the group IDs and server IDs for the Stream Managers to use in their domains.
Configuring Split-Domain Management
To configure a VVIM that uses split-domain management, set the VVI fields as follows:
- VVI Options—Enabled
- Management System Role —VVI (Vault/Cache) Manager
- Cache Fill Protocol —HTTP or CCP (Must be configured the same as the Stream Manager.)
To configure a Stream Manager that uses split-domain management, set the VVI fields as follows:
- VVI Options—Enabled
- Management System Role —Stream Manager
- Cache Fill Protocol —HTTP
- VVI (Vault/Cache) Manager VVIM IP— IP address of the VVIM
- Stream Domain Name —Domain name for the Stream Domain (If CCP is the Cache Fill Protocol)
The Media Scheduler is an optional feature and requires a software activation key to enable it. For more information about activating the Media Scheduler, see the “Initializing the CDS and Activating the Optional Features” section. The Media Scheduler allows live ingests from multicast IP addresses and uses the Input Channels page to map multicast IP addresses to channels. You can enable either Media Scheduler or Real-Time Capture Type, but not both.
Real-Time Capture Type
Real-Time Capture allows live ingests from multicast IP addresses and uses the CallSign Setup page to map the multicast IP addresses to call signs. You can enable either Media Scheduler or Real-Time Capture Type, but not both.
The Bandwidth Manager is an optional feature and is only for RTSP environments. The Bandwidth Manager keeps track of allocated streams and VOD network resources.
The Ingest Manager is an optional feature and requires a software activation key to enable it. For more information about activating the Ingest Manager, see “Initializing the CDS and Activating the Optional Features” section. The Ingest Manager takes care of provisioned content objects by collecting the metadata, sending messages to the appropriate subsystem to ingest the content, and sending messages to expire the content when the expiration period has passed.
RTSP Deployment Type
The RTSP Deployment type is applicable only to RTSP environments. The options are the following:
- EventIS (on vpath and off vpath)
The deployment configuration differs depending on the type of headend.
The Content Propagation setting determines whether content information is propagated to the Streamers or not. This setting is applicable only to RTSP environments.
When the RTSP Deployment Type is set to NGOD, set the Content Propagation to Not Propagated . This setting allows content information to be stored on the Caching Nodes in VVI RTSP NGOD deployments. The Streamers check their local database for a record of the content. If the content is not found, the Caching Nodes are queried for the content record.
For all other RTSP Deployment Types, set the Content Propagation to Propagated . This allows content information to be stored on the Streamers.
The Authentication Manager is an optional feature and is only for specific RTSP environments (EventIS). The Authentication Manager communicates with the backoffice to validate a request received from a set-top box before setting up a session.
The Protocol options are for selecting the RTSP deployment type for the Authentication Manager. Cisco is used for the Cisco RTSP deployment and EventIS is used for the EventIS RTSP deployment.
Service Group Steering
Service Group Steering is an optional feature and is only for RTSP environments. When the Service Group Steering option is turned on, the Configure > System Level > Headend Setup page is available to steer Stream Groups to specific service groups.
CDSM or VVIM NAV Setup
The CDSM NAV Setup changes what displays in the CDSM GUI.
CDSM or VVIM Health Monitoring
The CDSM Health Monitoring optional feature displays the Server Level monitor page, Server Vitals page and a Vitals column in the System Health Monitor page. The Server Vitals page displays the current values, as well as thresholds, for monitored system components on the server. Server components are monitored and when a threshold is exceeded, the System Health Monitor page and Server Vitals page report the event and an SNMP trap is sent.