Cisco TV CDS 2.5 ISA Software Configuration Guide November 2011 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
CONTENTS Preface xv Document Revision History Audience xv Objective xvi xv Document Organization xvi Document Conventions xvii Related Documentation xviii Obtaining Documentation and Submitting a Service Request CHAPTER 1 Product Overview xviii 1-1 Overview 1-1 TV CDS Software 1-3 Caching Nodes 1-4 Streamer Load Balancing 1-4 CServer Functionality 1-4 Streamer Content Delivery Applications 1-4 Content Delivery 1-5 Real-Time Splicing of MPEG-2 Transport Streams Dynamic Modification of Play
Contents Streamer Server Resiliency 1-16 Caching Node Disk Redundancy 1-16 Caching Node Resiliency 1-16 CDSM Redundancy 1-17 Ethernet Link Resiliency 1-17 Scalability 1-17 CHAPTER 2 Network Design 2-1 Overview 2-1 CDS with Vaults and Streamers CDS with ISVs 2-2 CDS with Caching Nodes 2-2 2-1 TV CDS and VVI Topologies 2-2 Centralized Topology 2-3 Decentralized Topology 2-4 Hybrid Topology 2-5 TV VVI Management 2-6 Centralized Management 2-7 Split-Domain Management 2-7 CDS Workflow 2-7 Popularity-Base
Contents Streaming Mode 2-18 Steering Ingests 2-18 Network Connections 2-19 Ingest Interface 2-22 Management Interface 2-23 Cache Interfaces 2-23 Cache/Stream Interfaces 2-23 Streaming Interface 2-23 CHAPTER 3 Getting Started 3-1 Initially Configuring the Devices Logging In to the TV CDSM Logging Out 3-3 3-1 3-1 Initializing the CDS and Activating the Optional Features 3-3 Navigating the CDSM 3-4 Using Online Help 3-5 Configuration Workflows 3-5 CDS Configuration Workflow 3-6 VVI Configuration Wo
Contents ASI Streaming 4-11 Configuring Stream Destinations 4-17 Configuring Parent/Child Service Groups 4-19 Configuring Distributed/ Shared ISA Settings 4-20 Configuring the Ingest Manager 4-23 Configuring Ingest Tuning 4-26 Configuring MPEG Tuning 4-29 Configuring IP Nicknames 4-31 Configuring the Ingest Driver Server 4-32 Configuring the Media Importer/Exporter 4-33 Configuring Call Signs 4-35 Configuring Input Channels 4-37 Configuring Output Channels 4-39 Configuring the System Level Logging 4-39 Con
Contents Package Metadata Editor 4-84 Fixing Conflicts in the Media Scheduler 4-86 Configuring Barker Streams 4-87 Gigabit Ethernet Streaming 4-87 ASI Streaming 4-88 Configuring SSV Groups 4-90 Configuring Manual Ingests 4-91 Configuring Barker Stream/Playlists 4-94 Gigabit Ethernet Streaming 4-94 ASI Streaming 4-96 Configuring Playout Scheduler 4-98 Changing Current Timeslots 4-105 Exporting a Playout Schedule 4-106 Exporting a Playout Schedule for an EPG 4-107 Configuring Array Level Error Repair 4-107 S
Contents Viewing Other Ingests Package Expirations 5-13 Publish Failures 5-14 Monitoring Stream Objects Stream Monitor 5-16 System Failures 5-21 5-12 5-16 Array Level Monitoring 5-31 Array Snapshot 5-31 Barker Stream Monitor 5-31 Playout Monitor 5-32 Server Level Monitoring 5-33 Disk Monitor 5-33 S.M.A.R.
Contents CDSM Audit Logs 6-38 Playout/Barker Reports 6-41 Archived Data 6-42 CDSM Audit Log Archives 6-43 Content Reports 6-43 Stream Reports 6-44 Stream Failure Reports 6-44 Stream Activity Reports 6-45 CHAPTER 7 System Maintenance 7-1 User Access 7-2 Adding Users 7-4 Add User—Force Password Change 7-4 Editing User Settings 7-5 Deleting a User 7-6 Viewing User Settings 7-6 Changing User Default Settings 7-6 Configuring System Authentication Settings 7-9 Password Complexity Rules 7-10 Configuring
Contents APPENDIX A Troubleshooting A-1 OpenStream Issues A-2 CDS Server Cannot Register with OpenStream OpenStream Reports Alert Messages A-3 A-2 General Information and Issues A-3 File System A-4 CDSM A-4 Vault, Streamer, Caching Node, and ISV A-4 Log Files A-5 Linux Log Files A-5 CServer Log Files A-5 ISA Log Files A-7 CDSM Log Files A-8 Server Configuration Files A-8 Description of the .
Contents Ingest Interface A-26 General Tips A-26 Common Ingest Problems A-26 CDS Is Not Registered to the Name Service Restarting the ISA Services A-27 Bad Content A-27 Network A-27 A-27 Content Processing Issues A-28 Listing Content A-28 Content Mirroring A-29 Verifying GOIDs A-29 Trick-Mode Issues A-30 Name and Notify Services A-30 CORBA Interface A-30 Cache-Fill Issues A-31 Tracking Cache-Fill Source A-31 Rules for ISV Interoperability with Vaults and Streamers A-31 Network A-32 Stream Stops Playing a
Contents Reliability and Availability A-39 Serviceability and Manageability A-40 Content A-42 Other A-43 CDS Content Quality Guidelines A-45 Supported Elementary Stream Types Scrambling A-45 Transport Bit Rate A-45 Stream Length A-45 Format Restrictions A-46 Preferred Formats A-46 APPENDIX Creating Bulk Configuration Files B Introduction A-45 B-1 B-1 Creating QAM Gateway and Headend Setup Bulk Configuration Files B-2 QAM Gateway and Headend Setup Bulk Configuration for Gigabit Ethernet Streaming QA
Contents Logging In to AMT E-2 AMT Statistics E-3 Viewing Error Repair Statistics E-5 Viewing Excess Bandwidth E-7 APPENDIX F Engineering Access Level Pages CDSM or VVIM Diagnostics F-2 CIDR Calculator F-2 Stream Trick-Mode Debugger Unix Timestamp Tool F-2 Server Diagrams F-2 F-1 F-2 CDSM or VVIM Setup F-3 Deployed CServer Version F-3 Stream Failover Support F-3 Stream Steering Mode F-3 Deployment Network Config F-3 Installation Type F-3 Stream Destination F-4 NAT Support F-4 Parent/Child Service G
Contents CDSM or VVIM NAV Setup F-12 CDSM or VVIM Health Monitoring F-12 System Configs F-12 Group Map 0 F-12 Servers Group Map F-12 Popularity Based Caching F-12 Add New Server F-13 APPENDIX G Software Licensing Information Notices G-1 G-1 Product Warranties G-1 Cisco TV CDS 2.
Preface This preface describes the audience, use, and organization of the Cisco TV CDS 2.5 ISA Software Configuration Guide. The preface also outlines the document conventions and support information.
Preface Objective This guide provides the information you need to configure and monitor the Cisco TV CDS. This guide provides procedures for using the commands that have been created or changed for use with the Cisco TV CDS. It does not provide detailed information about these commands. This guide does not describe system messages you might encounter or how to install your CDS.
Preface Chapter or Appendix Descriptions Appendix F, “Engineering Access Level Pages” Describes the CDSM pages visible with the Engineering access level. Appendix G, “Software Licensing Information” Provides information on open-source licenses and Cisco’s software licensing agreement. Document Conventions This guide uses the following conventions for command syntax descriptions and textual emphasis: Conventions Descriptions boldface font Commands and keywords are in boldface.
Preface Related Documentation These documents provide complete information about the CDS and are available from Cisco.com: • Release Notes for the Cisco TV CDS 2.5.2 • Cisco TV CDS 2.5 RTSP Software Configuration Guide • Cisco TV CDS 2.5 API Guide • Cisco TV CDS 2.
CH A P T E R 1 Product Overview This chapter provides a brief introduction to the Cisco TV Content Delivery System for an Interactive Services Architecture (ISA) environment.
Chapter 1 Product Overview Overview Table 1-1 CDA Mapping to Functionality and CDSM (continued) CDA Name Functionalities CDSM Device Name TV MediaX Suite Aids content ingest workflow and scheduling tasks for both asset-based and real-time content CDSM TV Content Delivery System Manager Management CDSM Figure 1-1 illustrates how a TV CDS network can be deployed.
Chapter 1 Product Overview Overview Note • One or more Stream Groups each consisting of one or more Streamers. The Stream Group is responsible for the personalization and streaming of content in response to user requests. The number of Streamers and Stream Groups is determined by the number of streams deployed and by the topology that best suits your individual network and redundancy requirements.
Chapter 1 Product Overview Overview in the local cache of the Streamer are pulled from the Vault, cached on the Streamer, and streamed to the subscriber. Wherever the content is stored relative to the point of playout, all content appears as if it is local to the Streamer and the streaming of any content is nearly instantaneous. Caching Nodes A Caching Node is an intermediary fill source for the Streamers. Caching Nodes are deployed in Virtual Video Infrastructures (VVIs).
Chapter 1 Product Overview Overview TV Streamer CDA The TV Streamer CDA is used for VOD delivery systems. TV Streamers are responsible for personalizing content and playing that content out under subscriber control. TV MediaX Suite CDA The TV MediaX Suite CDA offers a set of tools that simplify content ingest workflow and scheduling tasks for both asset-based and real-time content. The TV MediaX Suite CDA consists of the following features: • Publisher—Coordinates the ingest of pre-encrypted content.
Chapter 1 Product Overview Overview • Provides a single content delivery network for serving set-top boxes (STBs), PCs, and mobile devices • Supports content security and encryption • Supports narrowcast service such as VOD, time-shifted TV, and switched digital video (SDV) sharing the same infrastructure • Supports both traditional and next-generation STBs and headends Real-Time Splicing of MPEG-2 Transport Streams The ISA Stream Extensions feature allows real-time splicing of MPEG-2 transport s
Chapter 1 Product Overview Overview Note • Splice_Segment—Insert one or more segments at a specified NPT start value or NPT end value within an existing playlist segment • Add_Segment—Add one or more segments after a segment in the playlist Each playlist can have up to 64 content elements. The CDSM provides augmentations to the Stream Play History report. The Stream Play History report first displays the Session ID Summary.
Chapter 1 Product Overview Overview If play starts at 0 or some point before the live point, then the Catch-up to Live feature allows the end-user to fast-forward to the live point and resume normal play at the live point. The play point will be within 2.5 seconds of the live point.
Chapter 1 Product Overview Overview RTSP/1.0 200 OK CSeq: 2 Session: 12345678 Transport: RTP/AVPF/UDP; unicast; destination=54.0.1.1; client_port=8998-7123; source=101.1.2.3; server_port=50236-50237 Following is an example of the second SETUP message: SETUP rtsp://192.0.2.100/movie.mpg/rtx RTSP/1.0 Session: 12345678 CSeq: 2 Transport: RTP/AVPF/UDP; unicast; destination=54.0.1.1; client_port=8999-7124 RTSP/1.
Chapter 1 Product Overview Content Delivery System Architecture AMT Application Monitoring Tool (AMT) runs a web application on each Streamer and provides several troubleshooting tools. For more information, see Appendix E, “Using the TV CDS Streamer Application Monitoring Tool.” Content Delivery System Architecture Vaults and Streamers have different but important functions that are required for the TV CDS software to run efficiently.
Chapter 1 Product Overview Content Delivery System Architecture Table 1-2 High-Level Description of the TV CDS and TV VVI Content Delivery System Element Description CServer The CServer is the kernel software that handles bandwidth management, storage decisions, Real Time Streaming Protocol (RTSP) and Lightweight Stream Control Protocol (LSCP) and stream processing on the TV Content Delivery System.
Chapter 1 Product Overview Content Delivery System Architecture Streamer A Streamer server receives content from the Vault and delivers that content to subscribers. Streamers can be of different capacity, depending on the needs of the network, and have different applications, depending on the type of content being delivered. Currently, the highest-capacity Streamer can simultaneously stream approximately 2500 streams of MPEG-2 TS standard definition VOD.
Chapter 1 Product Overview Content Delivery System Architecture In both the CDS and VVI, all Vaults and Streamers are identified by an array ID, a group ID, and a server ID. The array ID identifies servers that are part of the same system. The group ID identifies servers that are part of the same group (Vault Group or Stream Group), and the server ID is a unique number that identifies the server. Table 1-3 lists the CDSM GUI ID names and maps them to the CServer names in the setupfile and .arroyorc files.
Chapter 1 Product Overview Content Delivery System Architecture Figure 1-3 Content Delivery System Manager User Interface Resiliency and Redundancy The TV Content Delivery System is designed to have no single point of failure. The TV Content Delivery System incorporates redundancy at several levels within the architecture.
Chapter 1 Product Overview Content Delivery System Architecture Local Mirroring Local mirroring defines the number of copies of each content object to maintain on the unique drives of a single Vault. Local mirroring allows resiliency for a small installation (for example one Vault). Local mirroring guards against a single drive failure, but does not protect against service interruption or potential data loss in the event of a complete server failure.
Chapter 1 Product Overview Content Delivery System Architecture Vault Group Redundancy In addition to the Vault server redundancy, the Cisco TV CDS offers redundancy for Vault Groups. When the CDS is configured with Vault Group redundancy and at least two Vault Groups are configured, the system handles the loss of an entire Vault Group without impacting the subscriber experience.
Chapter 1 Product Overview Content Delivery System Architecture CDSM Redundancy The Cisco TV CDS offers 1+1 redundancy for CDSMs. The primary CDSM, designated by a virtual IP address on the management interface, is used as the representative of the CDSMs to the web browser and northbound integrations, such as HTML API calls and SNMP calls. All CDS servers keep track of a controller IP address in the .arroyorc file. With CDSM redundancy, both management IP addresses are specified in the .
Chapter 1 Product Overview Content Delivery System Architecture Cisco TV CDS 2.
CH A P T E R 2 Network Design This chapter describes the different network topologies for the Cisco TV CDS, the different network connections of the CDS servers, the CDS workflow, and network configuration considerations.
Chapter 2 Network Design TV CDS and VVI Topologies to the quadrature amplitude modulation (QAM) devices over gigabit Ethernet or asynchronous serial interface (ASI), and then is modulated onto the HFC plant to the subscriber set-top box (STB) for viewing. CDS with ISVs For the smallest networks, Cisco packages the CDS in a single server, the Integrated Streamer-Vault (ISV), offering a solution for VOD services with large content libraries but small stream counts.
Chapter 2 Network Design TV CDS and VVI Topologies Note When using ISVs, with the Vault and Streamer functions contained in one server, the only topology possible is centralized. Centralized Topology In a centralized topology, all CDS servers are located in either a single video headend or a remote hub. This is the right solution for certain situations, for instance very small starting systems or where a large amount of bandwidth is available.
Chapter 2 Network Design TV CDS and VVI Topologies Figure 2-3 illustrates the centralized topology for a VVI. Figure 2-3 Centralized Topology with Caching Nodes Headend or Remote Hub Vaults GE Switch HFC Caching Nodes Streamers 252114 GE Switch GE Switch GE QAMs Decentralized Topology The decentralized topology is a hub-and-spoke topology between the headend site and multiple hub sites, where the Vaults are located at the headend and the Streamers are in the hub sites.
Chapter 2 Network Design TV CDS and VVI Topologies Figure 2-5 illustrates the decentralized topology with Caching Nodes.
Chapter 2 Network Design TV CDS and VVI Topologies Figure 2-7 illustrates the hybrid topology with Caching Nodes. Figure 2-7 Hybrid Topology with Caching Nodes Remote Hub Caching Nodes GE Switch GE QAMs GE Switch Headend Vaults Streamers GE Switch GE QAMs HFC 252116 GE Switch Streamers TV VVI Management The TV VVI offers two types of management, centralized and split-domain. In a CDS, Streamers cannot communicate with Streamers in other groups.
Chapter 2 Network Design CDS Workflow Centralized Management Centralized management uses one Virtual Video Infrastructure Manager (VVIM) to manage the Vaults, Caching Nodes, and Streamers in a VVI. Split-Domain Management Split-domain management uses one VVIM to manage the domain of Vaults and Caching Nodes, and separate managers, the Stream Managers, to manage each domain of Streamers. The Stream Managers communicate with the VVIM over port 80.
Chapter 2 Network Design CDS Workflow If a VVI is deployed, content is delivered from the Vault Group to the Cache Group in response to cache-fill calls from the Streamers. The Caching Nodes are explained in more detail in the “Caching Node Workflow” section on page 2-10. Within the Streamer array are one or more Stream Groups. The following section describes how the Stream Groups deliver streams to the subscriber STBs. Note All servers can be on different subnetworks.
Chapter 2 Network Design CDS Workflow immediately, and does not wait for the ten-second report interval. For example, if the server is given 100 Mbps and the streams that were just started uses 90 Mbps, the upper threshold limit has been reached and the server asks the bandwidth manager for more bandwidth. A separate entry is maintained for each thin pipe with a list of servers that have the same thin pipe configuration.
Chapter 2 Network Design CDS Workflow Setup Server A Streamer designated as the Setup server interfaces with the backoffice and forwards the setup messages to the appropriate Stream Group that is assigned to the destination service group. One Streamer in the Stream Group that is colocated with the backoffice server is assigned as the primary Setup server. The Setup server receives the setup request from the backoffice and maps the service group.
Chapter 2 Network Design CDS Workflow HTTP Streamers HTTP can be used for communication between the Caching Nodes and the Streamers. The HTTP Streamer communicates with a proxy for locating a fill source and pulling content. A locate service serves as a proxy for a group of Caching Nodes and Vaults. The service is accessed through a highly available virtual IP address hosted by the Caching Node. The virtual IP address is bound to a fill port (Locate Port).
Chapter 2 Network Design Vault Virtualization With FTP pull, the original content is kept on an FTP server (catcher), for a period of time and mechanisms are in place to restart ingests until they have successfully completed. With FTP push, only a window of data is buffered by a device that grooms the live (broadcast) feed and pushes the data to the Vault. With live capture over UDP, the Vault captures the live multicast feed directly.
Chapter 2 Network Design Vault Virtualization Remote Site Each remote CDS has a local Vault Group and communicates with a local BMS and local AMS located at the headend or at another headend nearby. Each remote CDS is able to ingest local content through the local Vaults and is able to access content stored in the central storage facility by way of the Caching Nodes and Vaults in the VVI.
Chapter 2 Network Design Vault Virtualization • IngestDriverHost • IngestDriverPort • IngestDriverNoOfThreads The Ingest Driver server logs events to the IngestDriver.log file located in the /arroyo/log directory. Ingest Driver Client The Ingest Driver client is used by the local Content Store to send requests to the Ingest Driver server and receive responses from the server.
Chapter 2 Network Design Vault Virtualization For RTA content, the process is same as it has always been for the CDS. The local Content Store processes the provision call (provisionForPush for RTA) and directs the local Vaults to perform the ingest of the content. Remote Streaming Local streaming is accomplished by way of the Cache Control Protocol (CCP) locate capability.
Chapter 2 Network Design Vault Virtualization The DNS server typically runs on the BMS server. The Naming Service is part of the video backoffice (VBO). All CORBA components, including the AMS, Stream Service, and Content Store, need to register with the Naming Service. The catcher receives or “catches” new content assets from an external communication device such as a satellite transmission or FTP server.
Chapter 2 Network Design BMS Considerations for ISA Environments In Release 2.5.2, Vault Virtualization replaces the SCS with the Virtual Content Store (VCS). No content is ingested at the local VHO. All ingests and deletions of content occur at the central location, and both ingests and deletions are initiated by the local BMS at each local VHO, just as they were in the SCS. However, the VHOs do not need to communicate with the super headend (SHE) as they did with the SCS feature.
Chapter 2 Network Design BMS Considerations for ISA Environments Figure 2-9 TV CDS Integration into the OpenStream BMS Streaming Mode OpenStream uses a session-based approach to handle resource requirements and allocation. In the course of setting up a session, a QAM device is specified that has available capacity and connectivity to the Streamer and the STB requesting the service. Typically, the Session and Resource Manager (SRM) is responsible for the allocation of network resources.
Chapter 2 Network Design Network Connections Figure 2-10 shows a high-level view of Ingest Steering for a single, centralized BMS and multiple VHOs. Each VHO has a local Vault Group through which all local live content is ingested. Each Stream Group streams local live content as well as national live and VOD content.
Chapter 2 Network Design Network Connections 1. The cache interfaces on an ISV are used for content mirroring among ISVs. Note Table 2-2 lists the mandatory interfaces for each CDS server. If HTTP Streamers are used in a VVI, each Caching Node must have one interface designated as the Locate interface. Stream Control is an optional interface function. For more information, see the “Configuring the Interfaces” section on page 4-109.
Chapter 2 Network Design Network Connections Figure 2-12 ISV Network Connections Cisco TV CDS 2.
Chapter 2 Network Design Network Connections Figure 2-13 shows the different logical networks of a VVI. The ingest network receives content from the content source by way of an FTP staging server or FTP catcher where it is ingested by the Vaults. The management network consists of communication between the CDSM and BMS, as well as communication with the Vaults, Streamers, Caching Nodes, QAM devices, and STBs.
Chapter 2 Network Design Network Connections Management Interface The management interface communicates with the network management system (NMS) by way of SNMP, the BMS by way of ISA commands and also RTSP, and with all Vaults, Caching Nodes, and Streamers in the same array.
Chapter 2 Network Design Network Connections Cisco TV CDS 2.
CH A P T E R 3 Getting Started This chapter provides information on configuring the TV CDS servers.
Chapter 3 Getting Started Logging In to the TV CDSM Note Consult your as-built documentation for the IP address of the CDSM. If you have redundant CDSMs, use the virtual IP address, not the IP addresses of the physical Ethernet interfaces. The CDSM GUI now supports HyperText Transport Protocol Secure (HTTPS) as a secure way to access the browser-based interface.
Chapter 3 Getting Started Initializing the CDS and Activating the Optional Features Logging Out To log out of the CDSM from any page, click Logout at the upper-right part of the page. See Figure 3-2. Figure 3-2 Logging Out Initializing the CDS and Activating the Optional Features Initial configuration of your CDS includes selecting the CServer version, the installation type, and other parameters that must be configured before you can continue the configuration process.
Chapter 3 Getting Started Navigating the CDSM Step 7 To activate the VOD Error Repair, scroll down to the VOD Error Repair section, and click the Enabled radio button next to the VOD Error Repair field. a. In the Activation Key field, enter the software access key from your Right to Use Notification for the Content Delivery Application VOD Error Repair (CDAVER) product. Step 8 Click Submit. Step 9 Log out of the CDSM.
Chapter 3 Getting Started Configuration Workflows Using Online Help Online help is available in the CDSM. You can use it by clicking on the Help button in the upper-right corner of any of the pages. Context-sensitive help is provided for the page you are viewing. The CDSM offers several levels of help: • Each page of the CDSM includes some basic help, normally displayed in the main panel. • The Help button displays context-sensitive help presented in a separate browser window.
Chapter 3 Getting Started Configuration Workflows CDS Configuration Workflow Table 3-1 lists the basic tasks, in the recommended order, for configuring the CDS for content delivery with references to the associated sections in each chapter. Table 3-1 Configuration Workflow Task Description Where to Find More Information Change administrator password Change the administrator password for the CDSM.
Chapter 3 Getting Started Configuration Workflows VVI Configuration Workflow The Virtual Video Infrastructure can be centrally managed or can use split-domain management. Central Management Configuration Workflow Table 3-2 lists the basic tasks, in the recommended order, for configuring the VVI with central management for content delivery with references to the associated sections in each chapter.
Chapter 3 Getting Started Configuration Workflows Split-Domain Management Configuration Workflow Table 3-3 lists the basic tasks, in the recommended order, for configuring the VVI with split-domain management (VVIM and Stream Manager) for content delivery with references to the associated sections in each chapter. For more information, see Chapter 2, “Network Design,”and the “CDSM or VVIM Setup” section on page F-3.
Chapter 3 Getting Started Configuration Workflows Note Before configuring the VHO ISA Settings on the Stream Manager, resubmit the Shared ISA settings on the VVIM. If the CDSM or VVIM GUI pages are not updated with respect to the ISA settings, resubmit the Shared ISA Settings page on the VVIM and the VHO ISA Setup page on the Stream Manager.
Chapter 3 Getting Started Configuration Workflows Note Trick-mode settings on the VVIM and Stream Managers must be the same. To configure trick-mode settings in the CDSM GUI, choose Configure > System Level > Ingest Tuning. Virtual Content Store Configuration Workflow In addition to the configuration workflow for split-domain management, Table 3-5 lists the basic tasks, in the recommended order, for configuring Virtual Content Store with references to the associated sections in each chapter.
Chapter 3 Getting Started Configuration Workflows TV MediaX Configuration Workflow Table 3-6 lists the basic tasks for configuring the TV MediaX Suite CDA with references to the associated sections in each chapter. Note TV MediaX is an optional feature and requires a software activation key to enable it. For more information, see the “Initializing the CDS and Activating the Optional Features” section on page 3-3.
Chapter 3 Getting Started Configuration Workflows TV Playout Configuration Workflow Table 3-7 lists the basic tasks for configuring the TV Playout CDA with references to the associated sections in each chapter. Note TV Playout is an optional feature and is only displayed if the TV Playout feature is enabled. For more information, see the “Playout Scheduler” section on page F-11. .
CH A P T E R 4 Configuring the CDS This chapter provides information on configuring the CDS servers.
Chapter 4 Configuring the CDS System Level Configuration Note • Configuring Call Signs • Configuring Input Channels • Configuring Output Channels • 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 CDS. Configuring System Level DNS Services The System DNS page is used to up to 16 domain suffixes and 16 DNS servers.
Chapter 4 Configuring the CDS 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 CDS servers (Vault, Streamer, and Caching Node) and the CDSM and VVIM in a CDS must be synchronized in order to retrieve the statistics on to the CDSM and VVIM. To view the current NTP System Level settings, choose Configure > System Level > System NTP Server.
Chapter 4 Configuring the CDS 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 the “Content Delivery System Architecture” section on page 1-10. Note Currently the CDSM allows only for the creation of one Vault array.
Chapter 4 Configuring the CDS System Level Configuration Note Caution Single-site steering assumes all Streamers in a Stream Group are located at the same geographical location. Multi-site steering is available only with ASI streaming. See the “Configuring the Streamer for BMS Connectivity” section on page 4-45 for information about configuring the ASI streaming mode. The Stream Group preference options in the QAM Gateway page differ based on the steering used in your deployment.
Chapter 4 Configuring the CDS System Level Configuration Figure 4-1 QAM Gateway Example Layer 3 Device as QAM Gateway Layer 3 Layer 2 Layer 3 GQAM Device1 172.31.253.32 Streamer 1 10.156.24.41 Layer 2 Layer 3 Device1 MAC Addr1 Layer 3 Layer 3 GQAM Device2 172.31.253.128 Layer 2 Layer 3 Device2 MAC Addr2 Streamer 3 10.156.24.43 Layer 3 Layer 3 GQAM Device3 172.31.253.192 203095 Streamer 2 10.156.24.
Chapter 4 Configuring the CDS System Level Configuration To configure a QAM gateway, do the following: Step 1 Choose Configure > System Level > QAM Gateway. The QAM Gateway 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.
Chapter 4 Configuring the CDS System Level Configuration Table 4-4 QAM Gateway Fields Field Description QAM IP IP address of the QAM gateway. QAM MAC MAC address of the next Layer 3 device connected to the Streamer in the path to the QAM device. 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.
Chapter 4 Configuring the CDS System Level Configuration 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 used to configure service groups for gigabit Ethernet streaming, Service groups and transport stream mapping for ASI streaming, and fake service groups for barker streams. Note The Headend Setup page is not available if the Stream Destination is set to IPTV.
Chapter 4 Configuring the CDS System Level Configuration To configure a fake service group for a barker stream, do the following: Step 1 Configure the broadcast QAM on the QAM Gateway page. See the “Configuring QAM Gateways” section on page 4-4. Step 2 Configure the fake service group, and input transport stream ID (TSID in) and output transport stream ID (TSID out) as appropriate for the barker stream broadcast.
Chapter 4 Configuring the CDS System Level Configuration c. Check the Reload Service Groups check box and click Submit. To clear the fields and start over, click Reset. Note Any changes (this includes additions, deletions, or modifications) to the headend setup require a reload of the service groups. See the “Restarting the Services” section on page 7-15 for more information. If the Content Storage feature is enabled, you do not need to reload service groups.
Chapter 4 Configuring the CDS System Level Configuration The headend setup settings differ depending on which QAM device type you choose. The ASI streaming QAM devices supported are: Note • NSG—Harmonic Narrowcast Services Gateway 8104, 8204, and 9000 • Path1—IP Video Networks Path 1 ASI/IP Gateway • Prisma IP—Scientific Atlanta Prisma IP GigE to ASI Gateway (The Prisma IP device has three possible UDP port numbering configuration selections: sequential, even, and odd.
Chapter 4 Configuring the CDS System Level Configuration Figure 4-5 Note You can use the Tab key to cycle through the fields. The tab order steps through the all the fields in the column on the left before moving on to the next column. Table 4-5 Step 2 Headend Setup for NSG NSG, Prisma, Path1 Headend Setup Fields Field Description TSID in Input transport stream ID (TSID in) is the identifier of a transport stream on the QAM gateway that sends streams to the QAM device.
Chapter 4 Configuring the CDS System Level Configuration Step 3 If the Content Storage feature is not enabled, you must reload the service groups. a. Choose Maintain > Services. The Services Restart page is displayed. b. From the drop-down list, choose the IP address or nickname of the server and click Display. c. Check the Reload Service Groups check box and click Submit. To clear the fields and start over, click Reset.
Chapter 4 Configuring the CDS System Level Configuration Figure 4-6 Step 2 Note Enter the settings as appropriate. See Table 4-6 for descriptions of the fields. You can use the Tab key to cycle through the fields. The tab order starts with the RF service group, and then cycles through the TSIDs for that RF.
Chapter 4 Configuring the CDS System Level Configuration Step 4 If the Content Storage feature is not enabled, you must reload the service groups. a. Choose Maintain > Services. The Services Restart page is displayed. b. From the drop-down list, choose the IP address or nickname of the server and click Display. c. Check the Reload Service Groups check box and click Submit. To clear the fields and start over, click Reset.
Chapter 4 Configuring the CDS System Level Configuration Note You can use the Tab key to cycle through the fields. Table 4-7 GQAM Shared Headend Setup Fields Field Description link Enable or disable the link to the associated service group. Service Group Service group that maps to the specified RF port on this GQAM device. Note Step 2 The GigE Gen QAM type supports up to 24 service groups and RF ports. Check the information you entered, correct any errors, and click Submit.
Chapter 4 Configuring the CDS System Level Configuration To configure the Stream Destination, do the following: Step 1 Choose Configure > System Level > Stream Destination. The Stream Destination page is displayed (Figure 4-8). 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.
Chapter 4 Configuring the CDS System Level Configuration Step 4 Choose the preference for each Stream Group. The preferences are: • High—First preference of Streamer or Stream Group to stream to this subnet. • Medium—Second preference of Streamer or Stream Group to stream to this subnet. • Low—Lowest preference of Streamer or Stream Group to stream to this subnet. • None—Do not use this Streamer or Stream Group to stream to this subnet.
Chapter 4 Configuring the CDS System Level Configuration Figure 4-9 Parent/Child Service Group Page Step 3 Enter each child service group. Step 4 Click Submit. To clear the fields and start over, click Reset. Configuring Distributed/ Shared ISA Settings The Distributed/Shared ISA Setup page is used to configure the ISA settings for the Vaults in the VVI. The ISA settings are replicated to each video hub office (VHO) in the VVI.
Chapter 4 Configuring the CDS System Level Configuration Figure 4-10 Step 2 Shared ISA Settings Page Enter the shared ISA settings as appropriate. See Table 4-8 for descriptions of the fields. Table 4-8 Shared ISA Fields Field Description ISA OpenStream Settings Vault Master IP This field defines the master IP address of the Content Service, which is the same for all Vaults in an array, and is used in the creation of the Interoperable Object References (IORs) for content objects.
Chapter 4 Configuring the CDS System Level Configuration Table 4-8 Shared ISA Fields (continued) Field Description Vault Master Port Port used by the master Content Service for controlling content. The Content Service Master Port is the same for all Vaults in the array. The default is 3200. Web Service Port Port number used by web service processes listening on this server. The default is 8080.
Chapter 4 Configuring the CDS System Level Configuration Table 4-8 Shared ISA Fields (continued) Field Description FTP Server Port Port used when the Vault receives a request from the OpenStream system to act as an FTP server and receives an FTP PUT command from the content provider acting as an FTP client. The default is port 4000. This is a control connection (data transfer process) and is known as an FTP pull process.
Chapter 4 Configuring the CDS System Level Configuration Table 4-9 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.
Chapter 4 Configuring the CDS System Level Configuration Table 4-9 Ingest Manager Fields (continued) Field Description 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.
Chapter 4 Configuring the CDS System Level Configuration Table 4-9 Step 3 Ingest Manager Fields (continued) Field Description 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.
Chapter 4 Configuring the CDS System Level Configuration Table 4-10 Ingest Tuning Fields (continued) Field Description Fail Ingest Settings PSI Errors When program specific information (PSI) errors setting is enabled and the CDS software cannot find the PAT and PMT, the ingest fails. The default for PSI Errors is Disabled.
Chapter 4 Configuring the CDS System Level Configuration Table 4-10 Ingest Tuning Fields (continued) Field Description Fail Ingest Settings PSI Errors When program specific information (PSI) errors setting is enabled and the CDS software cannot find the PAT and PMT, the ingest fails. The default for PSI Errors is Disabled.
Chapter 4 Configuring the CDS System Level Configuration Table 4-10 Ingest Tuning Fields (continued) Field Description Continuity Counter Errors Sets the Continuity Counter Errors threshold. The default is Ignore. Number of Sync Loss Errors Sets the Number of Sync Loss Errors threshold. The default is 3. Each transport-stream packet header has a 4-bit continuity counter, which increments for each transport-stream packet with the same PID.
Chapter 4 Configuring the CDS System Level Configuration Table 4-11 MPEG Tuning Fields Field 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.
Chapter 4 Configuring the CDS System Level Configuration Table 4-11 MPEG Tuning Fields (continued) Field Description 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.
Chapter 4 Configuring the CDS System Level Configuration Figure 4-11 IP Nicknames Page Step 2 Choose the IP address from the applicable drop-down list, either Cisco CDSM IP Addresses or Configured QAM Gateway IP Addresses, and click Display. Step 3 In the IP Nickname field, enter a nickname. The name can be from 5 to 20 characters in length and can consist of uppercase and lowercase letters, numbers, and the underscore (_) or hyphen (-) symbols. Step 4 Click Submit.
Chapter 4 Configuring the CDS System Level Configuration Table 4-12 Step 3 Ingest Driver Server Fields Field Description Virtual IP Virtual IP address used to receive requests from the Ingest Driver client and send responses to the Ingest Driver client. Ingest Server Port The port number used for communication with the Ingest Driver client. Default is 20000. The port number must be the same for both the Ingest Driver server and the Ingest Driver client.
Chapter 4 Configuring the CDS System Level Configuration Figure 4-12 Step 2 Media Importer/Exporter Page Enter the settings as appropriate. See Table 4-13 for descriptions of the fields. Table 4-13 Media Importer/Exporter 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 EPG file, see the “Uploading an EPG File” section on page 7-20.
Chapter 4 Configuring the CDS System Level Configuration Table 4-13 Media Importer/Exporter Fields (continued) Field Description 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. Media Exporter Settings1 Pre-Notification How much time (in seconds) prior to the start of a content program should the catalog server be notified to advertise the program to the set-top box.
Chapter 4 Configuring the CDS System Level Configuration Figure 4-13 Step 2 Enter the call sign settings as appropriate. See Table 4-14 for descriptions of the fields. Table 4-14 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.
Chapter 4 Configuring the CDS System Level Configuration Configuring Input Channels Note The Input Channels page is part of the MediaX Suite, which is an optional feature. The Input Channels page allows you to define channels mapped to a multicast group IP address and port, where scheduled content is ingested. The Input Channels page also collects a number of values for metadata generation.
Chapter 4 Configuring the CDS 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-15 for descriptions of the fields.
Chapter 4 Configuring the CDS System Level Configuration Note You cannot delete a channel that has future scheduled events. To view, edit, or delete a current channel setup, from the Select Channel drop-down list choose the channel. The Channel Setup page refreshes with the configuration for the channel selected. To delete the channel, click Delete. To edit the channel configuration, edit the fields and click Submit.
Chapter 4 Configuring the CDS System Level Configuration 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.
Chapter 4 Configuring the CDS System Level Configuration Step 3 Enter the Log Level settings as appropriate. See Table 4-16 for descriptions of the fields. Table 4-16 Log Level Fields Field Description Local Log Level The Local Log Level drop-down list has the following options: • Emergency (0) • Critical (1) • Alert (2) • Error (3) • Warning (4) • Notice (5) • Informational (6) A log level setting includes all the more urgent levels.
Chapter 4 Configuring the CDS System Level Configuration 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 filed, 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.
Chapter 4 Configuring the CDS Array Level Configuration Step 3 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 Appendix E, “Using the TV CDS Streamer Application Monitoring Tool.
Chapter 4 Configuring the CDS Array Level Configuration Note • Exporting a Playout Schedule for an EPG • 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.
Chapter 4 Configuring the CDS Array Level Configuration Step 2 From the Array Name drop-down list, choose an array and click Display. Step 3 In the New NTP Server field, enter the IP address of the NTP server. Step 4 Click Submit. To clear the fields and start over, click Reset. To delete the NTP settings, check the Delete check box and click Submit. For information on setting the time zone on a CDS server or configuring NTP on a CDSM or VVIM, see “Other NTP Configurations” section on page 4-127.
Chapter 4 Configuring the CDS Array Level Configuration Figure 4-15 Streamer ISA Page Cisco TV CDS 2.
Chapter 4 Configuring the CDS Array Level Configuration Step 2 Table 4-19 Field Enter the Streamer ISA settings as appropriate. See Table 4-19 for descriptions of the fields. Streamer ISA Fields Description Streamer ISA OpenStream Settings Stream Master IP Master IP address of the Stream Service, which is the same for all Streamers in an array, and is used in the creation of the Interoperable Object References (IORs) for stream objects.
Chapter 4 Configuring the CDS Array Level Configuration Table 4-19 Streamer ISA Fields (continued) Field Description TME/SCE From the TME/SCE drop-down list, select Enable for MystroMDN for Stream Control Events (SCE) or Enable for OpenStream for Trick-Mode Events (TME). Enabling TME requires that the stream service and LSCP or RTSP service deliver more CORBA events to the Stream Event Channel.
Chapter 4 Configuring the CDS Array Level Configuration Table 4-19 Streamer ISA Fields (continued) Field Factories ID Description 1 Simple name that identifies the root directory of the Factories where all factories need to register. The default is Factories. Factories Kind1 Factories ID extension. The default is Context. Event Channel Factory1 Simple name that identifies the Event Channel Factory, which is used to create event channels, and resolves the Notification Service name.
Chapter 4 Configuring the CDS Array Level Configuration Table 4-19 Field Streamer ISA Fields (continued) Description Session Gateways Session Gateway ID [1-5] Session Gateway ID is used by the backoffice Session Gateway service for registering with the Name Service. The default is N2BBSession Gateway. The Session Gateway ID is required by the Resource Manager to connect to the Session Gateway for checking the status of all the sessions on a regular basis. 1.
Chapter 4 Configuring the CDS Array Level Configuration To configure the Vault ISA settings, do the following: Step 1 Choose Configure > Array Level > Vault BMS. The Vault ISA page is displayed (Figure 4-16). Figure 4-16 Step 2 Vault ISA Page Enter the Vault ISA settings as appropriate. See Table 4-20 for descriptions of the fields. Cisco TV CDS 2.
Chapter 4 Configuring the CDS Array Level Configuration Table 4-20 Vault ISA Fields Field Description Vault ISA OpenStream Settings Content Master This field defines the master IP address of the Content Service, which is the same for all Vault servers in an IP array, and is used in the creation of the Interoperable Object References (IORs) for content objects.
Chapter 4 Configuring the CDS Array Level Configuration Table 4-20 Vault ISA Fields (continued) Field Description Name Service Port1 Port of the Naming Service used by the OpenStream system. The default is 5000. Notify Service IP1 IP address of the CORBA Notification Service used by the OpenStream system. Notify Service Port1 Port of the Notification Service used by the OpenStream system. The default is 5005.
Chapter 4 Configuring the CDS Array Level Configuration Grouping Stream Groups into VHOs The VHO Setup page provides a way to group Stream Groups that have the same ISA settings. After the VHO groups are created, you set the ISA settings for each VHO on the VHO ISA Settings page. See the “Configuring VHO ISA Settings” section on page 4-55 for more information. Note The VHO Setup page is available only on a Stream Manager when VVI and Content Storage are enabled in an ISA environment.
Chapter 4 Configuring the CDS Array Level Configuration Table 4-21 Step 5 Stream Group and Local Vault Group Options Stream Group Option Description No Change Do not make any changes to the VHO assignment. VHO Name Add this group to this VHO. None Remove this group from this VHO. Applicable only to groups assigned to the selected VHO. Don’t Change Do not assign this group to this VHO. Click Submit. To clear the fields and start over, click Reset.
Chapter 4 Configuring the CDS Array Level Configuration Table 4-22 VHO ISA Fields Field Description Streamer BMS Settings Stream Master IP This field defines the master IP address of the Stream Service, which is the same for all Streamers in a VHO, and is used in the creation of the Interoperable Object References (IORs) for stream objects.
Chapter 4 Configuring the CDS Array Level Configuration Table 4-22 VHO ISA Fields (continued) Field Description TME/SCE From the TME/SCE drop-down list, select Enable for MystroMDN for Stream Control Events (SCE) or Enable for OpenStream for Trick-Mode Events (TME). Enabling TME requires that the stream service and LSCP or RTSP service deliver more CORBA events to the Stream Event Channel.
Chapter 4 Configuring the CDS Array Level Configuration Table 4-22 VHO ISA Fields (continued) Field Description LSCP Client Protocol Choose the way LSCP clients communicate with the Streamers. The options are: • TVGuide—For Scientific Atlanta clients–TV Guide • RTI—For Tandberg clients • VODLink—For SeaChange clients • CV—For SeaChange clients with Cablevision • Cisco (RTSP) • TTV (RTSP) • LSCP Pause at EOS If NAT is enabled, the LSCP Client Protocol must be Cisco (RTSP) or TTV (RTSP).
Chapter 4 Configuring the CDS Array Level Configuration When grouping Streamers you should take into account network cost to stream, bandwidth usage, and geographic locations of Streamers and QAM gateways. All Streamers in a group are considered to have the same cost to reach a destination. VVI with Split-Domain Management and CCP 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.
Chapter 4 Configuring the CDS Array Level Configuration 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-18). Figure 4-18 Step 2 Stream Groups Page From the Select Stream Group to View/Edit drop-down list, choose Add New Stream Group and click Display. To edit a Stream Group, choose the Stream Group from the drop-down list and click Display.
Chapter 4 Configuring the CDS Array Level Configuration 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. To edit a Stream Group, choose the Stream Group from the drop-down list and click Display.
Chapter 4 Configuring the CDS Array Level Configuration Figure 4-19 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.
Chapter 4 Configuring the CDS Array Level Configuration Step 6 Click Submit. To reset the field, click Reset. To view the members of a Vault Group, choose the Vault Group from the drop-down list and click Display. To delete a Vault Group, 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.
Chapter 4 Configuring the CDS Array Level Configuration Figure 4-20 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.
Chapter 4 Configuring the CDS Array Level Configuration 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.
Chapter 4 Configuring the CDS Array Level Configuration The unassigned Caching Nodes are listed along with a drop down-list for each that offers the options described in Table 4-25. Table 4-25 Step 5 Caching Node Options 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.
Chapter 4 Configuring the CDS Array Level Configuration To reset the field, click Reset. To view the Vault Group mappings of a Cache Group, choose the Cache Group from the drop-down list and click Display. To delete a Cache Group or a Vault Group, see the “Configuring Cache Groups” section on page 4-65 or the “Configuring Vault Groups” section on page 4-61.
Chapter 4 Configuring the CDS Array Level Configuration Mapping Stream Groups to Cache-Fill Sources The Stream To Cache Map page is used to map Cache Groups, Vault Groups, and other Stream Groups as cache-fill sources for each Stream Group in a VVI. Before you can map the different groups to Stream Groups, you must create them.
Chapter 4 Configuring the CDS Array Level Configuration 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.
Chapter 4 Configuring the CDS Array Level Configuration Step 1 Choose Configure > Array Level > Vault Redundancy Map. The Vault Redundancy Map page is displayed (Figure 4-23). Figure 4-23 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. Note Step 3 Vault Redundancy Map Page Only national Vault Groups are displayed on the Vault Redundancy Map page.
Chapter 4 Configuring the CDS Array Level Configuration • Step 4 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 the “Configuring Vault Groups” section on page 4-61. When a Vault Group is deleted, the mapping for the Vault Group is also deleted.
Chapter 4 Configuring the CDS 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 the “Restarting a Server” section on page 7-11 for more information. Configuring the Control and Setup IPs There can only be one IP address designated as the Setup server or Control/Setup server.
Chapter 4 Configuring the CDS Array Level Configuration Each VHO must have at least one Stream Group assigned to it and must have one Stream Group configured as the Setup IP or the Control/Setup IP. The other Stream Groups in the VHO must be configured as a Control IP. Step 3 For each Stream Group, enter the IP address and subnet mask of the Control IP, Setup IP, or Control/Setup IP. Step 4 From the IP Type drop-down list, choose an IP type. See Table 4-26 for descriptions of the types.
Chapter 4 Configuring the CDS Array Level Configuration 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-25. Table 4-27 Step 5 Group Options Group Option Description No Change Do not make any changes to the site assignment.
Chapter 4 Configuring the CDS Array Level Configuration • Note Routers must support the bandwidths that are configured for the thin pipe mapping on the CDS. 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.
Chapter 4 Configuring the CDS Array Level Configuration Table 4-28 Thin Pipe Mappings for Thin Pipe Example (continued) Thin Pipe Map Remote Site Bandwidth (Gbps) SHE1toCS1 Cache Site 1 2 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 SHE1, SHE2, Cache Site 2, Cache Site 3 2 SHE1, SHE2, Cache Site 1, Cache Site 3 2 S
Chapter 4 Configuring the CDS 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.
Chapter 4 Configuring the CDS Array Level Configuration The Ingest Driver client and Ingest Driver server are part of the ISA Regionalization feature and the Virtual Content Store feature. For more information, see the “ISA Regionalization” section on page 2-12 and the “Virtual Content Store” section on page 2-16. Note The Ingest Driver Client page is only displayed on the Stream Manager if the Content Storage is set to Distributed. For more information, see the “Content Storage” section on page F-9.
Chapter 4 Configuring the CDS Array Level Configuration Configuring the Media Scheduler Note The Media Scheduler page is part of the licensed MediaX feature. For more information see the “Media Scheduler” section on page F-10. 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.
Chapter 4 Configuring the CDS Array Level Configuration 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-26). Figure 4-26 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.
Chapter 4 Configuring the CDS Array Level Configuration 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.
Chapter 4 Configuring the CDS Array Level Configuration Figure 4-28 Media Scheduler Page—Schedule Depending on the status of the schedule, the cells of the schedule 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.
Chapter 4 Configuring the CDS Array Level Configuration Figure 4-29 Step 3 Media Scheduler Page—Program Information 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.
Chapter 4 Configuring the CDS 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-30).
Chapter 4 Configuring the CDS Array Level Configuration Step 2 For metadata created from user-generated schedules, there is an option for recurring schedules (Figure 4-31). Figure 4-31 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-30 for descriptions of the Recurring Schedule fields.
Chapter 4 Configuring the CDS 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.
Chapter 4 Configuring the CDS Array Level Configuration Configuring Barker Streams Note The Barker Stream feature is optional and is not listed on the Array Level left-panel menu if it is not included in your deployment. The Barker Stream feature is also not available if the Stream Destination is set to IPTV. For more information, see the “Stream Destination” section on page F-4. The Barker Stream settings are used to configure the service groups that receive a selected barker stream.
Chapter 4 Configuring the CDS Array Level Configuration Tip Step 3 By typing the first few characters of the content name, you can jump to that section of the list. Check the check box next to each QAM IP that will send the specified barker stream. All QAM devices currently configured on the CDS are listed. Step 4 In the QAM Port field, enter the port number for each selected QAM device. Step 5 From the Svc. Group drop-down list, choose the service group for each selected QAM device.
Chapter 4 Configuring the CDS Array Level Configuration Figure 4-34 Step 3 Barker Stream Page—ASI Streaming From the Available Content drop-down list, choose the barker stream. Tip By typing the first few characters of the content name, you can jump to that section of the list. Step 4 From each Service Group drop-down list, choose each service group entry. Step 5 In the Loops field, enter the number of times the content object will loop.
Chapter 4 Configuring the CDS 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.
Chapter 4 Configuring the CDS Array Level Configuration 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 Manual Ingests The Manual Ingest page allows you to manually ingest content. Note The Manual Ingest page is part of the TV Playout feature and is displayed only if TV Playout feature is enabled.
Chapter 4 Configuring the CDS Array Level Configuration Table 4-32 Manual Ingest Fields (continued) Field Description FTP Directory The directory path where the content files are located. This can be an absolute or virtual path, depending on how the FTP server is configured. Make sure you begin the FTP path with a forward slash (/). The search includes all subdirectories. File Extensions Note Step 3 The extensions of the types of content file you want retrieve.
Chapter 4 Configuring the CDS Array Level Configuration Figure 4-36 Step 4 Manual Ingest Page—Search Results Check the check box next to each content name that you want to ingest and click Ingest Selected. Alternatively, you can click Check All to select all listed content objects. To clear the check boxes and start over, click Uncheck All or Reset. Cisco TV CDS 2.
Chapter 4 Configuring the CDS Array Level Configuration Step 5 If Localized EPG Extensions is enabled, the Localized Name and Localized Description fields are displayed for each content object that was ingested. You can enter a name and description for each content object that is used by the EPG Exporter when exporting the content object. Note The Localized EPG Extensions feature is an option of the TV Playout feature. For more information, see the “Playout Scheduler” section on page F-11.
Chapter 4 Configuring the CDS Array Level Configuration Step 1 Click Configure > Array Level > Barker Stream/Playlists. The Barker Stream page is displayed (Figure 4-33). Note The Barker Stream page displays the delivery service mode (active-active or active-standby) for the Baker Stream application. To change the delivery service mode, see the “Configuring the TV Playout Application” section on page 7-17.
Chapter 4 Configuring the CDS Array Level Configuration Step 6 Click Submit. To clear the fields and start over, click Reset. Step 7 To play the barker stream, click Start Barker. Playlists can be schedule for play by using the Playout Scheduler. Note A content object loops the specified number of times before the barker stream continues on to the next content. The barker stream loops indefinitely. Tip To edit a barker stream, choose the barker stream and click Next.
Chapter 4 Configuring the CDS Array Level Configuration Figure 4-38 Barker Stream/Playlist for ASI Streaming Page Step 2 Choose configure new and click Next. Step 3 In the Number of Contents drop-down list, select the number of content objects for the barker stream or playlist. Step 4 Enter the Barker Stream settings as appropriate. See Table 4-34 for a description of the fields. Table 4-34 Barker Stream—ASI Fields Field Description Barker Name Enter a name for the barker stream.
Chapter 4 Configuring the CDS Array Level Configuration To edit a barker stream, choose the barker stream and click Next. Enter the new settings and click Submit. To add new content, choose the number of content objects to add from the add content drop-down list. If the barker stream is playing at the time changes are submitted, the stream will stop. You will need to click Start Barker to restart the stream.
Chapter 4 Configuring the CDS Array Level Configuration Figure 4-39 Playout Scheduler Page—User Preferences Step 2 For the Preference Editor, choose either Hide On Return or Show On Return to display the User Preferences each time you go to the Playout Scheduler page. Step 3 For the Action on Recurring Schedules, choose either Preserve Existing Schedules or Overwrite Existing Schedules.
Chapter 4 Configuring the CDS Array Level Configuration • Step 5 Step 6 If Use Select Box is selected, use the down arrow of the drop-down list to display the list and select the content object. In the Channels to Schedule section, check the check boxes for the channels you want to schedule, or check the Select All check box to chose all channels. Note You can change the user preferences at any time by clicking Edit Settings in the main Playout Scheduler page or when the calendar is displayed.
Chapter 4 Configuring the CDS Array Level Configuration The schedule for the day you selected is displayed (Figure 4-41). Note The Playout Scheduler page displays the delivery service mode for the Playout Scheduler application. To change the delivery service mode (active-active or active-standby), see the “Configuring the TV Playout Application” section on page 7-17.
Chapter 4 Configuring the CDS Array Level Configuration Figure 4-42 Playout Creator Window a. In the Content Type, select either Content or Playlist. Content displays all content ingested. Playlists displays all playlists created by using the Barker Stream/Playlists page. b. If the Content Selection option was selected in the User Preferences is Use Select Box, use the down arrow of the Content drop-down list to display the list and select the content object.
Chapter 4 Configuring the CDS Array Level Configuration Figure 4-43 c. Playout Creator—Use Suggester In the Set Play Length fields, enter the Start Date. The End Date and Time fields are adjusted automatically based on the length of the content you selected. Alternatively, you can choose the number of times the content loops up to a maximum value of 12 hours after the content start time. In this case, the End Date and Time fields are dimmed.
Chapter 4 Configuring the CDS Array Level Configuration • To unschedule a scheduled content, click the timeslot that has “Scheduled Content.” The timeslot changes from “Scheduled Content” to “Marked for Unscheduling.” Click Schedule/Unschedule. You can mark several timeslots for unscheduling and submit all the changes at one time. • To reschedule content that is “Unscheduled,” click the timeslot. The timeslot changes to “Marked for Scheduling.” Click Schedule/Unschedule. The time slot is scheduled.
Chapter 4 Configuring the CDS Array Level Configuration Step 12 Once you have completed the playout schedule for the selected day, you can fill in the remaining empty timeslots with a content you choose from the Filler Content field at the bottom of the page. See Figure 4-46. Figure 4-46 Playout Scheduler Page–Filler Content a. In the Filler Content field, type the first few characters of the content object name, a list of content objects beginning with those letters are displayed.
Chapter 4 Configuring the CDS Array Level Configuration Exporting a Playout Schedule The Playout Exporter allows you to create an XML file that contains information from the Playout Scheduler for a specific channel or all channels. The XML file then can be viewed, saved, and imported into another CDS to create program listings. Note The Playout Exporter page is part of the TV Playout feature and is displayed only if TV Playout feature is enabled.
Chapter 4 Configuring the CDS Array Level Configuration Exporting a Playout Schedule for an EPG Note The EPG Exporter feature is only displayed if the Localized EPG Extensions option is enabled for the TV Playout feature. For more information, see the “Playout Scheduler” section on page F-11. The EPG Exporter allows you to create an XML file that contains information from the playout schedule for a specified channel or all channels.
Chapter 4 Configuring the CDS Array Level Configuration 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-35 for descriptions of the fields. Table 4-35 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.
Chapter 4 Configuring the CDS Server Level Configuration Server Level Configuration After a server has been initially configured (see the “Initially Configuring the Devices” section on 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.
Chapter 4 Configuring the CDS Server Level Configuration Table 4-36 CDS 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 the “Configuring the Control and Setup IPs” section on page 4-72.
Chapter 4 Configuring the CDS Server Level Configuration Figure 4-48 Step 3 Interface Setup Page—Vault Page Enter the interface settings as appropriate. See Table 4-37 for descriptions of the fields. Cisco TV CDS 2.
Chapter 4 Configuring the CDS Server Level Configuration Table 4-37 Interface Fields Field Description Setting Choose each interface setting as appropriate. See Table 4-36 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.
Chapter 4 Configuring the CDS Server Level Configuration Table 4-38 lists the CDSM GUI ID names and maps them to the CServer names in the setupfile and .arroyorc files.
Chapter 4 Configuring the CDS Server Level Configuration Table 4-39 Server Setup Fields (continued) Field Description Server Types Starting Transport Port Beginning default UDP port number used for stream and stream/cache interfaces. If the starting transport port is left blank, the default of 48879 is used. Streamer, ISV Ending Transport Port Ending default UDP port number used for stream and stream/cache interfaces. There is no Streamer, ISV default for the ending transport port number.
Chapter 4 Configuring the CDS Server Level Configuration Table 4-39 Field Server Setup Fields (continued) Description Server Types 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 If jumbo frames are enabled, you need to make sure that your switch is configured to support jumbo frames.
Chapter 4 Configuring the CDS Server Level Configuration Table 4-39 Server Setup Fields (continued) Field Description Server Types 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.
Chapter 4 Configuring the CDS Server Level Configuration • 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.
Chapter 4 Configuring the CDS Server Level Configuration Table 4-40 AF Class Drop Probability Configured on Each CDS Server AF1x AF2x AF3x AF4x Data Types AF11 AF21 AF31 AF41 The following data types are set to low drop probability: • Lost packet recovery for committed rate traffic (Vault or Caching Node or Streamer to Vault or Caching Node or Streamer) • High-priority lost packet recovery for committed rate traffic (Vault or Caching Node or Streamer to Vault or Caching Node or Streamer) •
Chapter 4 Configuring the CDS Server Level Configuration CServer Source Route Type When CServer Source is selected from the Route Type drop-down list, a subnet is defined and written to the SubnetTable file. Subnets can only be defined for stream, cache, or stream/cache interfaces. Interfaces are defined on the Interface Setup page (“Configuring the Interfaces,” page 4-109), and IP addresses for the interfaces are set on the Server Setup page (“Configuring the Servers,” page 4-112).
Chapter 4 Configuring the CDS Server Level Configuration To configure a route, do the following: Step 1 Choose Configure > Server Level > Route Tables. The Routing Table page is displayed (Figure 4-50). 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.
Chapter 4 Configuring the CDS Server Level Configuration Step 4 Table 4-42 Route Table Fields (continued) Field Description Gateway IP address of the next hop (primary datagram transmitter and receiver) along the route to the network. Route Type From the Route Type drop-down list, choose one of the following route types: • CServer Source—Used to configure a subnet and default gateway for a group of stream, cache, or stream/cache interfaces on this server.
Chapter 4 Configuring the CDS Server Level Configuration View-Based Access Control Model The View-based Access Control Model (VACM) is used for controlling access to management information. The TV CDS software implements VACM by allowing configuration of each management object (OID) or group of OIDs on a CDS server through the CDSM GUI to be exposed with read-only or read-write access to a configured user.
Chapter 4 Configuring the CDS Server Level Configuration Table 4-43 SNMP Agent Fields (continued) Field Description 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).
Chapter 4 Configuring the CDS Server Level Configuration Table 4-43 SNMP Agent Fields (continued) Field Description 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.
Chapter 4 Configuring the CDS 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-51). Note If Bulk Configuration is enabled, the Configuration File Location field is displayed, along with the Browse and Import buttons.
Chapter 4 Configuring the CDS Server Level Configuration Table 4-44 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.
Chapter 4 Configuring the CDS 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 CDS server, as well as configure the NTP servers for the CDSM and VVIM. Setting the Time Zone on a CDS Server To set the time zone on a CDS server, log in to the CDS server as root, and use the Linux link command to link the time zone to the /etc/localtime file.
Chapter 4 Configuring the CDS 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.
Chapter 4 Configuring the CDS Server Level Configuration • 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.
Chapter 4 Configuring the CDS Server Level Configuration Table 4-45 Step 5 Log Level Fields Field Description 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.
Chapter 4 Configuring the CDS 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.
Chapter 4 Configuring the CDS Server Level Configuration Cisco TV CDS 2.
CH A P T E R 5 System Monitoring The CDSM provides tools that can be used for system monitoring and system diagnostics.
Chapter 5 System Monitoring System Level Monitoring Alarms Table Any time there is an alarmed event, an alarm is displayed in the CDSM banner. The Alarms table is displayed when you roll your mouse over the alarm icon. See Figure 5-1. Clicking the alarmed event in the Alarm table takes you to the CDSM page that has more information. For example, in Figure 5-1, clicking System health problems reported takes you to the System Health page.
Chapter 5 System Monitoring System Level Monitoring Missing or Incorrect Initial IDs If the CDSM is initially configured incorrectly as a legacy CDS or VVI with central management, then reconfigured or reinstalled for a VVIM or Stream Manager, the starting IDs for group IDs, server IDs, and setup IDs need to be changed from the old system to the new system. An alert is added to the Alarms table to inform you of the situation.
Chapter 5 System Monitoring System Level Monitoring • No Ingest—Vault is offline for ingest (still accepting cache-fill traffic) • Offline—Vault is offline for all traffic (ingest and cache-fill), Streamer or Caching Node is offline. You can view the details of a monitored area of a server by clicking the box in the appropriate column. • When you click the Network check box you are taken to the NIC Monitor page. See the “NIC Monitor” section on page 5-35 for more information.
Chapter 5 System Monitoring System Level Monitoring System Snapshot The System Snapshot page provides an overview of the current activity on the CDS. A summary of the state of all streams, content ingests, and disk usage is displayed. See Figure 5-3. Figure 5-3 System Snapshot Page In a VVI, the Stream Manager only displays the stream-related date and the VVIM only displays the bandwidth and content-related data. Table 5-1 describes the information displayed on the System Snapshot page.
Chapter 5 System Monitoring Monitoring Content Objects Table 5-1 System Snapshot Page (continued) Field Description SD Streams Total number of standard-definition stream objects the CDS is currently streaming. Active Stream Bandwidth1 Total bandwidth, in megabits, used for active streams. Active Fill Bandwidth1 Total bandwidth, in megabits, used for caching content among Vaults and Streamers.
Chapter 5 System Monitoring Monitoring Content Objects Package Expiration Lists Package Expiration information, including expiration dates and all associated metadata. Allows for package expiration adjustments. Publish Failures Lists the packages that were not able to be published to the backoffice and provides a mechanism to republish the package.
Chapter 5 System Monitoring Monitoring Content Objects Figure 5-4 Completed Ingests List Figure 5-5 shows an example of the Content Status information that displays when you choose Content Status (Damaged Only). Cisco TV CDS 2.
Chapter 5 System Monitoring Monitoring Content Objects Figure 5-5 Table 5-2 Step 3 Completed Ingests List—Content Status (Damaged Only) Content Status Fields Field Description Content Name Name of the content. Duration Duration of the content. GOID Global Object ID for the content object associated with the content. Version Trick-play speed of the content object. The value, IGate, refers to an index file, which allows for the jumps between trick speeds, and so on.
Chapter 5 System Monitoring Monitoring Content Objects Figure 5-6 Completed Ingests—Ingest Details Table 5-3 describes the content object details that are displayed for each type of ingest. Cisco TV CDS 2.
Chapter 5 System Monitoring Monitoring Content Objects Table 5-3 Content Object Details Field Description Content Name Name of the content object. Asset Name Name of the asset. An asset has three basic components: metadata, content, other assets (assets are hierarchically arranged to have a parent-child relationship). Factory ID Factory responsible for this content object. Ingest IP TIP address for the ingest interface on the Vault used to download the content.
Chapter 5 System Monitoring Monitoring Content Objects Table 5-3 Content Object Details (continued) Field Description URL Uniform Resource Locator (URL) address of the content has the following: Asset Ior • Protocol used (for example, FTP) • Username and password (for example, videolan:mpeg4ftp) • IP address of the content provider server (for example, 192.168.100.
Chapter 5 System Monitoring Monitoring Content Objects Package Expirations Note Package Expirations are part of the optional Ingest Manager feature. This option is listed only on the Monitoring System Level left-panel menu if the Ingest Manager is included in your deployment. To view the details or adjust the license expiration of a package expiration, do the following: Step 1 Choose Monitor > System Level > Package Expiration. The Package Expiration page is displayed.
Chapter 5 System Monitoring Monitoring Content Objects Table 5-4 Field Package Expiration Details (continued) Description Additional Package Additional time added to the package. Window Actual Package Expiration Step 3 Actual Package Expiration is the License Expiration plus the Additional Package Window. To adjust the license expiration, enter the number of days (positive or negative) in the Adjust License Expiration field and click Update.
Chapter 5 System Monitoring Monitoring Content Objects Figure 5-8 Publish Failures Page Table 5-5 describes the publish failures details that are displayed. Table 5-5 Publish Failures Details Field Description Package Name Name of the package. Source URL Location of the original package information. Target URL Location where to place the package information. Module Type Internal identifier for what failed. In the example in Figure 5-8, the publishing of the package failed.
Chapter 5 System Monitoring Monitoring Stream Objects Monitoring Stream Objects The monitored stream objects consist of: • Stream Monitor • System Failures Stream Monitor To view the details of stream objects, do the following: Step 1 Choose Monitor > System Level > Stream Monitor. The Stream Monitor page is displayed. Step 2 The following methods can be used to display a stream object or a list of stream objects: • Enter the first character of the session ID in the text box.
Chapter 5 System Monitoring Monitoring Stream Objects Figure 5-9 shows an example of the stream object list generated by clicking Most Recent 100 or All Streams. The Session handles and the stream start time are displayed. Figure 5-9 Step 3 Stream Monitor—Stream List To view the details of a stream object, click the session ID. The Stream Details are displayed. Figure 5-10 shows an example of the stream object details. Cisco TV CDS 2.
Chapter 5 System Monitoring Monitoring Stream Objects Figure 5-10 Stream Monitor—Stream Details Table 5-6 describes the stream details. Table 5-6 Stream Details Field Description Stream ID Internal unique identifier assigned to the stream session by the Streamer. Content ID Content identifier of the stream object. LSCP IP Source IP address of the LSCP transaction (set-top box). Session ID Session ID of the stream object. Create Time Date and time the stream object was created.
Chapter 5 System Monitoring Monitoring Stream Objects Table 5-6 Stream Details (continued) Field Description QAM IP IP address of the QAM device delivering this stream object. Note QAM Port Port the QAM device is using to receive the stream object. Note Program Number If Stream Destination is enabled, this field displays the subnet address. If Stream Destination is enabled, this field does not display. This field is applicable only when Streaming Mode is set to ASI.
Chapter 5 System Monitoring Monitoring Stream Objects Table 5-6 Stream Details (continued) Field Description Speed Direction Speed direction is as follows: Provision Multiple • Play • Not playing (Pause) • n fast-forward, where n means n times fast-forward • –n rewind, where n means n times rewind Provision Multiple is enabled if this field is “yes” and disabled if this field is “no.” The Graph Stream button displays the trick-mode activity of the stream (Figure 5-11).
Chapter 5 System Monitoring Monitoring Stream Objects System Failures To view the details of system failures, do the following: Step 1 Choose Monitor > System Level > System Failures. The System Failures page is displayed. Each system failure is listed by date and time, followed by the session ID. Note Step 2 Stream Failure monitoring displays only the system failures for the current day. To view past system failures, see the “System Failures” section on page 6-27.
Chapter 5 System Monitoring Monitoring Stream Objects Table 5-7 describes the stream failure details. Table 5-7 Stream Failure Details Field Description Session ID Session ID of the failed stream. Failure Date Date and time the failure occurred. QAM IP IP address of the QAM device associated with the failure. Service Group Service group associated with the failure. Server ID Server responsible for streaming this stream object.
Chapter 5 System Monitoring Monitoring Stream Objects Table 5-8 ID Names in the CDSM GUI and CServer Files (continued) CDSM GUI ID Name CServer Files ID Name Vault Group ID on the Server Setup page arrayid Stream Group ID on the Configuration Generator page arrayid Table 5-9 lists the Managed Services Architecture (MSA) error codes. Some MSA monitored events are monitored for the CDS as well, and are prefaced by “AVS_” instead of “MSA_.” They are denoted with a footnote in the table.
Chapter 5 System Monitoring Monitoring Stream Objects Table 5-9 MSA Error Codes (continued) Numeric Error Code Error Code Description 5025 MSA_LSC_MPEG_DELIVERY LSC response; unable to deliver MPEG stream. 5026 MSA_LSC_ERR Generic DSM-CC error event. 5027 MSA_LSC_BAD_REQUEST LSC response; invalid request. 5028 MSA_LSC_BAD_STREAM LSC response; invalid stream handle. 5029 MSA_LSC_WRONG_STATE LSC response; wrong state. 5030 MSA_LSC_UNKNOWN LSC response; unknown error.
Chapter 5 System Monitoring Monitoring Stream Objects Table 5-10 INT_ERR Error Codes (continued) Numeric Error Code Error Code Description 1012 STREAMER_DISK_BAD Disk is bad on a Streamer. 1013 CONTENT_LOCATE_FAILED Cannot locate the content on any Vault. 1014 CONTENT_FILL_FAILED Cannot push content to the Streamer from Vault. 1015 NOT_ENOUGH_FILL_BANDWIDTH Not enough fill bandwidth available. 1016 FILL_LINKS_DOWN Fill links are down. 1017 STREAMING_LINKS_DOWN Stream links are down.
Chapter 5 System Monitoring Monitoring Stream Objects Table 5-10 INT_ERR Error Codes (continued) Numeric Error Code Error Code Description 2023 VAULT_HAS_FULL_LOAD Vault is running with full load. 2024 FTP_CONNECTION_FAILED Connection to FTP server failed. 2025 FTP_SERVER_BIND_FAILED FTP server can not bind to the port. 2026 FTP_PUSH_TIMEOUT FTP push timeout (PASV is not served fast enough). 2027 FTP_QUIT_RECEIVED_DURING_INGEST FTP server received QUIT request.
Chapter 5 System Monitoring Monitoring Stream Objects Table 5-10 INT_ERR Error Codes (continued) Numeric Error Code Error Code Description 2099 NS_LOG_MONITOR_ERROR Ns_log file is not updating. Restart the ISA service. 2100 AVS_ISA_GENERIC_ERROR Some unknown error occurred during execution of the operation. 3001 CACHE2APP_INITIALIZE_ERROR Failed to initialize Cache2App library. 3002 FILLCB_FAILED FillCB failed during content ingest.
Chapter 5 System Monitoring Monitoring Stream Objects Table 5-11 MPEG Error Codes (continued) Numeric Error Code Error Code Description 8003 TRICK_INGEST_NULL_INGEST_OBJECTS Ingest fails. Check available system memory. 8004 TRICK_INGEST_INVALID_SPEED_DENOMINATOR Ingest fails. Change trick speed configuration. 8005 TRICK_INGEST_INVALID_SPEED_LT_2X Ingest fails. Change trick speed configuration. 8006 TRICK_INGEST_NULL_DERIVED_INGEST_OBJECTS Ingest fails. Check available system memory.
Chapter 5 System Monitoring Monitoring Stream Objects Table 5-11 MPEG Error Codes (continued) Numeric Error Code Error Code Description 8028 TRICK_INGEST_OVERFLOW_ON_RETRY Ingest fails even after a retry (ring buffer overflow). Check ingest feed. 8029 TRICK_INGEST_KNOBS_FAILURE Ingest fails. Check ingest feed or adjust ingest configuration parameters. 8030 TRICK_INGEST_KNOBS_FAILURE_PAT_PMT Ingest fails. No PAT or PMT found. Check ingest feed or adjust ingest configuration parameters.
Chapter 5 System Monitoring Monitoring Stream Objects Table 5-11 MPEG Error Codes (continued) Numeric Error Code Error Code Description 8048 TRICK_INGEST_SEQUENCE_HEADER_CHANGE_NO Ingest fails. Sequence Header changed with no _SEQEND preceding Sequence End. 8049 TRICK_INGEST_SEQUENCE_HEADER_CHANGE _BAD_PRIOR_STARTCODE Ingest fails. Sequence Header changed with no immediately preceding Sequence End. 8050 TRICK_INGEST_SEQUENCE_HEADER_CHANGE _NO_PRIOR_STARTCODE Ingest fails.
Chapter 5 System Monitoring Array Level Monitoring Array Level Monitoring The Array Level Monitoring pages provide an overall view of the health and activity of an specified array, monitoring and deletion of barker streams, and a display of the Playout Schedule if the Playout Scheduler is enabled.
Chapter 5 System Monitoring Array Level Monitoring Playout Monitor The Playout Monitor page displays the Playout Schedule that is currently configured for the selected day and channels. Note The Playout Monitor page is part of the TV Playout feature and is displayed only if TV Playout feature is enabled. For more information, see the “Playout Scheduler” section on page F-11. To view the Playout Schedule, do the following: Step 1 Choose Monitor > Array Level > Playout Monitor.
Chapter 5 System Monitoring Server Level Monitoring The timeslots have different colors depending on the status of the scheduled content and the type of content. The Playout Scheduler page displays a legend describing the different colors for the timeslots 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.
Chapter 5 System Monitoring Server Level Monitoring Figure 5-15 Disk Monitor Page—Streamer For Vault servers, the Disk Availability line graph shows the percentage of disk space available. The gigabytes displayed for “Total Space,” “Available Space,” and “% Used” are the sum of all the disks installed on the Vault server.
Chapter 5 System Monitoring Server Level Monitoring Table 5-13 Disk Status Fields (continued) Field Description Number of Reads Number of bytes read from the disk since it was powered on. Number of Writes Number of bytes written to the disk since it was powered on. S.M.A.R.T The CDS incorporates S.M.A.R.T. to monitor the reliability of a hard drive, predict drive failures, and to carry out different types of drive self-tests. S.M.A.R.
Chapter 5 System Monitoring Server Level Monitoring Figure 5-17 NIC Monitor Page—Streamer Table 5-14 describes the information displayed for a NIC port. Table 5-14 NIC Port Status Fields Field Description Port Speed Speed of the interface in megabits per second (Mbps). Admin State Administrative state of the port interface. The administrative state is determined at the time the server is booted. The possible administrative states are up or down.
Chapter 5 System Monitoring Server Level Monitoring Figure 5-18 NIC Monitor—Streamer Port Activity Graph Server Vitals The Server Vitals page provides current values for monitored system components. Server components are monitored and if a threshold is exceeded, the System Health Monitor page reports the event and an SNMP trap is sent to the Network Management System (NMS). Note The Server Vitals page is displayed only if the CDSM Health Monitor feature is enabled.
Chapter 5 System Monitoring Server Level Monitoring Figure 5-19 Server Vitals Page Cache/Fill Bandwidth The Cache/Fill Bandwidth page displays details on the content caching activity on a Streamer. To view the caching activity on a server, choose the IP address of the server from the drop-down list on the Cache/Fill Bandwidth page and click Display. Figure 5-20 shows an example. To change how often the information is refreshed, enter the number of seconds in the Data Refresh Rate field.
Chapter 5 System Monitoring Server Level Monitoring Figure 5-20 Cache/Fill Bandwidth Page Table 5-15 describes the services listed in the Cache/Fill Bandwidth page. Note The values in the Cache/Fill Bandwidth page are only accurate if the clocks on the CDS servers are synchronized with the CDSM. If the clocks on the CDS servers are out of sync with the CDSM by more than two minutes, no values are displayed.
Chapter 5 System Monitoring Server Level Monitoring Services Monitor The Services Monitor page displays whether specific processes are running on a server. To view the current status of the services running on a server, choose the IP address of the server from the drop-down list on the Services Monitor page and click Display. Figure 5-21 shows an example of a Streamer server. Figure 5-21 Services Monitor Page—Streamer Table 5-16 describes the services listed on the Services Monitor page.
Chapter 5 System Monitoring Recommended Monitoring Schedule Table 5-16 CDS Services (continued) Service Server Description Cisco Primary Stream Setup Service Streamer Primary Setup Service is running if you are looking at the Streamer server designated as the primary Setup server. The Setup server handles setting up stream sessions. Cisco Stream Control Service Streamer Stream Control Service accepts set-top box play stream commands, for example, LSCP.
Chapter 5 System Monitoring Recommended Monitoring Schedule • Choose Monitor > System Level > System Health and check the System Health Monitor page for red or yellow states on any of the servers. Click any red or yellow boxes to see detail information on disk, NIC, or services. See the “System Health” section on page 5-3 for more information. • Choose Monitor > System Level > Failed Ingests to check for any failed ingests. See the “Ingests” section on page 5-7 for more information.
Chapter 5 System Monitoring Recommended Monitoring Schedule Step 3 Check the CServer interfaces to verify the status of the Ethernet adapters. Choose Monitor > Server Level NIC Monitor, or log in to each server and use the following commands a. Use the grep -i Link command to verify that all adapters should have a status of “link up,” except those adapters that are not being used. grep –i Link /proc/net/PRO_LAN_Adapters/*.info b.
Chapter 5 System Monitoring Recommended Monitoring Schedule tail –f /arroyo/log/protocoltiming. | grep "Capacity Disk:" The number returned indicates the percentage of the disk space available on this server. If the number is 5 or lower, then steps need to be taken to increase storage space by adding more Vaults, replacing drives with higher capacity drives, or removing unused content. 2. Check the /home/isa/ContentStore/server/ContentStore.log for ingest errors on each Vault.
CH A P T E R 6 System Reporting The CDSM provides tools that can be used for system monitoring and system diagnostics.
Chapter 6 System Reporting Stream Activity Capacity Planning The Capacity Planning report provides information on high usage of bandwidth and streams for the selected date range and modifier. Note Step 1 If Trick Mode Capture is disabled, the data for the Capacity Planning report is not available. For information on enabling the Trick Mode Capture, see the “Trick Mode Capture” section on page F-5. From the Available Reports drop-down list, choose Capacity Planning (Figure 6-1).
Chapter 6 System Reporting Stream Activity Figure 6-2 Step 2 Capacity Planning Report Selection Fields Choose a modifier. See Table 6-1 for a description of each modifier. Table 6-1 Modifier Capacity Planning Modifiers Description None (Date Only) Filter on date only. Service Group Filters the report by the service group you choose in a later step. Streamer Filters the report by the Streamer or ISV1 you specify in a later step. 1. ISV = Integrated Streamer-Vault.
Chapter 6 System Reporting Stream Activity Table 6-2 Time Breakdown Options (continued) Modifier Description Per week Peak usage of bandwidth and streams per week within the specified date range. Incomplete weeks are not returned. The start date determines the first day of the week. For example, if you specify Tuesday, the 2nd of November 2010 as the start date, the first week is calculated as spanning from Tuesday, the 2nd of November 2010 to Monday, the 8th of November 2010.
Chapter 6 System Reporting Stream Activity Figure 6-3 Capacity Planning Report—Chart l The report displays: • Report type (for example, Capacity Planning Report displaying daily peak values) • From and to dates • Peak stream count for each time breakdown within the time period selected • Peak bandwidth in Mbps for each time breakdown within the time period selected Hover your cursor over a data point to view the time breakdown, peak stream count, and peak bandwidth associated with the data poin
Chapter 6 System Reporting Stream Activity Figure 6-4 Capacity Planning Report—Grid Click the Chart button to return to the chart view. Click New Report to return to the report selection page. Step 7 To download the report to a comma-separated value (CSV) file, do one of the following: a. If you are using Internet Explorer as your web browser, click Download and then click Save or Open. Save presents a Save As dialog box. Open opens the CSV file. b.
Chapter 6 System Reporting Stream Activity Streams by Array The Stream by Array report lists all streams currently active for a specified group of Streamers. To view the Stream by Array report, do the following: Step 1 From the Available Reports drop-down list, choose Streams By Array. Figure 6-5 shows the selection fields for the Streams by Array report. Figure 6-5 Stream by Array Report Selection Fields Step 2 From the Stream Array drop-down list, choose a stream array. Step 3 Choose a modifier.
Chapter 6 System Reporting Stream Activity Step 5 Choose a time breakdown of hourly, daily, weekly, or monthly. The maximum time interval allowed for each breakdown is the following: • Hourly—31 days • Daily—2 years • Weekly— 2 years • Monthly—2 years Step 6 If you selected a modifier that requires a value, choose or specify the filter value. Step 7 Click Display. To clear the fields and start over, click Reset.
Chapter 6 System Reporting Stream Activity Click the Grid button to view the chart information in a table. Click the Chart button to return to the chart view. Click Previous Report to return to the report selection page. Note Step 8 Previous Report returns you to the report selection page or the previous report page in a multi-page report. Next Report takes you to the next page in the report. To see more detail, click a bar in the chart.
Chapter 6 System Reporting Stream Activity Figure 6-8 Session ID—Stream Play History Drilldown The report opens in a chart view and displays: – Session ID – Set-top box MAC address – Termination reason – Date and time of each play or trick mode action – Server ID of the Play server that served the trick mode – Elapsed time of each action At the bottom of each Stream Play History report is a legend mapping the action to a color.
Chapter 6 System Reporting Stream Activity Figure 6-9 Stream Play History—Stream Data The Stream Data displays: – Details about the stream (QAM IP address, QAM port, and, if applicable, service group) – Details about the content (content name, ingest information, server ID of the server storing the content, and so on) Click Hide Stream Data to hide stream data. Click Previous Report to return to the previous page. c.
Chapter 6 System Reporting Stream Activity Step 10 If a playlist is associated with a session, do the following to view stream history information: a. Click the Session ID to see the playlist history for the session (Figure 6-10). Figure 6-10 Session Playlist History The report opens in a chart view and displays: – Session ID – Start time of each playlist – Elapsed time of each playlist in minutes Each content segment in the playlist is represented by a different color.
Chapter 6 System Reporting Stream Activity If Trick Mode Capture is disabled, clicking a bar in the chart does not link to the stream play history. For information on enabling the Trick Mode Capture, see the “Trick Mode Capture” section on page F-5. Note Click Previous Report to return to the previous page. c. To see details about the stream associated with this session, click Show Stream Data. Click Hide Stream Data to hide the stream data. Click Previous Report to return to the previous page. d.
Chapter 6 System Reporting Stream Activity Figure 6-11 Streams by Time Report Selection Fields Step 2 Using the drop-down lists provided, or the calendars, choose a From Date and To Date for the report. Step 3 Choose a time breakdown of per hour, per half hour, per 15 minute, or per minute. Step 4 Click Display. To clear the fields and start over, click Reset. Cisco TV CDS 2.
Chapter 6 System Reporting Stream Activity Figure 6-12 shows an example of the Streams by Time report in a chart view with the Per Hour time breakdown selected.
Chapter 6 System Reporting Stream Activity Note Step 5 Previous Report returns you to the report selection page or the previous report page in a multi-page report. Next Report takes you to the next page in the report. To download the report to a comma-separated value (CSV) file, do one of the following: a. If you are using Internet Explorer as your web browser, click Download and then click Save or Open. Save presents a Save As dialog box. Open opens the CSV file. b.
Chapter 6 System Reporting Stream Activity Figure 6-14 shows an example of the Streams per STB-MAC report in a chart view.
Chapter 6 System Reporting Stream Activity Step 5 If a content object is associated with a session, do the following to view stream history information: a. Click a session ID to see the stream play history of a specific session. Click Previous Report to return to the previous page. b. To see details about the stream associated with this session, click Show Stream Data. Click Hide Stream Data to hide stream data. Click Previous Report to return to the previous page. Note c.
Chapter 6 System Reporting Stream Activity Stream Play History The Stream Play History report lists the trick mode history for specified streams. To view the Stream Play History report, do the following: Step 1 From the Available Reports drop-down list, choose Stream Play History. Figure 6-15 shows the selection fields for the Stream Play History report. Figure 6-15 Step 2 Stream Play History Report Selection Fields Choose a modifier. See Table 6-4 for a description of each modifier.
Chapter 6 System Reporting Stream Activity Note Selecting Session ID displays the complete play history for the specified session. The From Date and To Date fields are bypassed. Note Selecting None (Date Only) displays the Session ID Summary. To see the play history of a specific session, click a Session ID in the Session ID Summary report. Step 4 If you selected a modifier, choose or specify the filtered value.
Chapter 6 System Reporting Stream Activity Note Figure 6-17 If Trick Mode Capture is disabled, the session ID does not link to the stream play history. For information on enabling the Trick Mode Capture, see the “Trick Mode Capture” section on page F-5.
Chapter 6 System Reporting Stream Activity b. To see details about the stream associated with this session, click Show Stream Data (Figure 6-18). Figure 6-18 Stream Play History—Stream Data The Stream Data displays: – Details about the stream (QAM IP address, QAM port, and, if applicable, service group) – Details about the content (content name, ingest information, server ID of the server storing the content, and so on) Click Hide Stream Data to hide stream data.
Chapter 6 System Reporting Stream Activity c. To download the report to a comma-separated value (CSV) file, do one of the following: a. If you are using Internet Explorer as your web browser, click Download and then click Save or Open. Save presents a Save As dialog box. Open opens the CSV file. b.
Chapter 6 System Reporting Stream Activity Click Hide Stream Data to hide the stream data. Click Previous Report to return to the previous page. d. To download the report to a comma-separated value (CSV) file, do one of the following: a. If you are using Internet Explorer as your web browser, click Download and then click Save or Open. Save presents a Save As dialog box. Open opens the CSV file. b.
Chapter 6 System Reporting Stream Activity To clear the fields and start over, click Reset. Figure 6-21 shows an example of the Cache/Fill Bandwidth report in a chart view. Figure 6-21 Cache/Fill Bandwidth Report The report displays the minimum, average, and maximum bandwidth used for each timeslot for the selected Streamer. Hover your cursor over a data point to view the same information in a summary view. Click the Grid button to view the chart information in a table.
Chapter 6 System Reporting Stream Activity Note Step 6 Previous Report returns you to the report selection page or the previous report page in a multi-page report. Next Report takes you to the next page in the report. To download the report to a comma-separated value (CSV) file, do one of the following: a. If you are using Internet Explorer as your web browser, click Download and then click Save or Open. Save presents a Save As dialog box. Open opens the CSV file. b.
Chapter 6 System Reporting Stream Activity System Failures The System Failures report lists the number of system failures. To view the System Failures report, do the following: Step 1 From the Available Reports drop-down list, choose System Failures. Figure 6-22 shows the selection fields for the System Failures report. Figure 6-22 System Failures Report Selection Fields Step 2 Choose an error code, if applicable.
Chapter 6 System Reporting Stream Activity Table 6-5 Stream Failure Modifiers Modifier Description None Filters the report by date and time and, if specified, error code. Service Group Filters the report by the service group that you choose in a later step. Server ID Filters the report by a server ID that you choose in a later step. Step 4 Using the drop-down lists provided, or the calendars, choose a From Date and To Date for the report.
Chapter 6 System Reporting Stream Activity Figure 6-23 shows an example of the System Failures report in a chart view. Figure 6-23 System Failures Report The report displays: • Report type • From and to dates • Number of HD failures, number of SD failures, and total number of failures for each time breakdown Hover your cursor over a data point to view the time breakdown, number of HD failures, number of SD failures, and total number of failures associated with the data point.
Chapter 6 System Reporting Stream Activity The Stream Failure Details report is displayed for this date (Figure 6-24). Figure 6-24 Stream Failure Details The report displays: Step 9 • Date and time of the failure • Session ID of the failed stream • QAM IP address • Server ID that was sending the stream at the time of the failure • Service Group • Error code If a content object is associated with a session, do the following to view stream history information: a.
Chapter 6 System Reporting Stream Activity Note c. Previous Report returns you to the report selection page or the previous report page in a multi-page report. Next Report takes you to the next page in the report. To download the report to a comma-separated value (CSV) file, do one of the following: a. If you are using Internet Explorer as your web browser, click Download and then click Save or Open. Save presents a Save As dialog box. Open opens the CSV file. b.
Chapter 6 System Reporting Stream Activity Content Popularity The Content Popularity report lists the content by their filenames and ranks them in order of popularity. To view the Content Popularity report, do the following: Step 1 From the Available Reports drop-down list, choose Content Popularity. Figure 6-25 shows the selection fields for the Content Popularity report.
Chapter 6 System Reporting Stream Activity Figure 6-26 shows an example of the Content Popularity report in a chart view. Figure 6-26 Content Popularity Report The report displays: • Report type • From and to dates • Content filenames • Number of times each content was streamed within the time period selected Hover your cursor over a data point to view the content object name and the number of streams associated with the data point. Click the Grid button to view the chart information in a table.
Chapter 6 System Reporting Stream Activity Step 4 To view content details, click the content object name in a chart view. The Content Detail report is displayed (Figure 6-27). Figure 6-27 Content Popularity Details Click Close to close this window. Click Previous Report to return to the previous page. Step 5 To download the report to a comma-separated value (CSV) file, do one of the following: a. If you are using Internet Explorer as your web browser, click Download and then click Save or Open.
Chapter 6 System Reporting Content Activity Content Activity The Content Activity reports lists all content stored on all Vaults in the specified group and all unpublished packages. The available reports for content activity are: • Content by Ingest Date • Unpublished Package Report Content by Ingest Date To view the Content by Ingest Date report, do the following: Step 1 Choose Report > Content Activity. The Content Activity selection page is displayed.
Chapter 6 System Reporting Content Activity Figure 6-29 shows an example of the Content Activity report. Figure 6-29 Content Activity Report The report displays: Step 7 • Report type • From and to dates • Content filenames • Creation date • Destroyed date To view the details of an in-service content object, click the content filename link (Figure 6-30). Figure 6-30 Content Detail Click Close to close this window. Click Previous Report to return to the previous page.
Chapter 6 System Reporting Content Activity b. If you are using another major web browser (for example, Netscape, Firefox, Opera), right-click Download and choose Save Link As, Save Link Target As, or Save Target As depending on the web browser you are using. A Save As dialog box is displayed. Unpublished Package Report Note The Unpublished Package report is part of the optional Ingest Manager feature.
Chapter 6 System Reporting CDSM Audit Logs Figure 6-32 shows an example of the Unpublished Package report. Figure 6-32 Unpublished Package Report The report displays: • Report type • From and to dates • Package names • Creation date • Source URL • Target URL • Number of assets associated with the package Step 5 Click New Report to return to the previous page. Step 6 To download the report to a comma-separated value (CSV) file, do one of the following: a.
Chapter 6 System Reporting CDSM Audit Logs Figure 6-33 Step 2 Using the Top Level Filter drop-down list provided, choose a top-level filter from the options presented in Table 6-6. Table 6-6 Step 3 CDSM Audit Log Selection Fields Top-level Filters Modifier Description All Sections Filter on date only. Configure Filters the log by actions taken using the Configure tab of the CDSM or VVIM. Monitor Filters the log by actions taken using the Monitor tab of the CDSM or VVIM.
Chapter 6 System Reporting CDSM Audit Logs Table 6-7 Sub-level Filters (continued) Top-level Filter Low-Level Filter Options Maintain If the log is filtered by the Maintain tab, choose to filter the log further by the actions taken using the Users, Servers, Services, or Software pages of the Maintain tab. All Sections, Auto System Cleanup, and All Other To apply a top-level filter only, choose All Sub Sections from the Sub Level Filter drop-down list.
Chapter 6 System Reporting Playout/Barker Reports a. If you are using Internet Explorer as your web browser, click Download and then click Save or Open. Save presents a Save As dialog box. Open opens the CSV file. b. If you are using another major web browser (for example, Netscape, Firefox, Opera), right-click Download and choose Save Link As, Save Link Target As, or Save Target As depending on the web browser you are using. A Save As dialog box is displayed.
Chapter 6 System Reporting Archived Data Archived Data Note The CSV files are generated every 24 hours and are deleted when they are older than 30 days. The CSV files are accessible by going to the /arroyo/asmrpt directory, or by using an FTP client with the username “asmrpt” and the password “asmrpt.” Monitoring data is archived in comma-separated value (CSV) format for use in a spreadsheet program, database, or other software. Table 6-8 describes the different archived data.
Chapter 6 System Reporting Archived Data Step 5 The CSV file is compressed using gzip (extension .gz). Decompress the file using a decompression tool that includes the gzip compression code, such as Winzip, PowerArchiver 6.1, or 7-zip. CDSM Audit Log Archives The CDSM Audit log archives contain the same information as the CDSM Audit logs. For more information, see the “CDSM Audit Logs” section on page 6-38. Content Reports Table 6-9 describes the fields in the Content Report CSV files.
Chapter 6 System Reporting Archived Data Stream Reports Table 6-10 describes the fields in the Stream Report CSV files. Table 6-10 Stream Report Archive Fields Field Description mSessionId Session ID of the stream. mGoid Global object identifier. Used by the CDS database. mTsIdOut Not applicable. mTsIdIn Not applicable. mProgramNumber Not applicable. mBandwidthUsed This field is applicable only when Streaming Mode is set to ASI.
Chapter 6 System Reporting Archived Data Table 6-11 Stream Failure Report Archive Fields (continued) Field Description mOperation Operation that was taking place when the stream failed. For example: createStream, LSCP Command(), createServant, destroy. These are the measurement points or transactional states of the system at the time of the failure. See Table 5-7 on page 5-22 for more information. mErrorCode Error code provides a description of the event that caused the error.
Chapter 6 System Reporting Archived Data Cisco TV CDS 2.
CH A P T E R 7 System Maintenance This chapter explains how to perform common administrative tasks including, updating system software, restarting services, and shutting down the Vault and Streamer servers.
Chapter 7 System Maintenance User Access User Access Login authentication is used to control user access and configuration rights to the CDSM. Login authentication is the process by which the CDSM verifies whether the person who is attempting to log in to the CDSM has a valid username and password. If the local database is used, the person logging in must have a user account created on the CDSM.
Chapter 7 System Maintenance User Access CDSM User Login Checks System checks are performed on the CDSM during the user login process and during access to the CDSM GUI. If any one of the checks does not pass, access to the CDSM is denied and an error message is displayed with information on which check failed. Table 7-1 describes the system checks that are performed during the user login process and during user access to the CDSM.
Chapter 7 System Maintenance User Access Adding Users The CDS provides one built-in user, “admin,” that has master level access and cannot be deleted. The master user can add additional users with different levels of access. To add a user, do the following: Step 1 Choose Maintain > Users > Add User. The Add User page is displayed. Step 2 Fill in the fields as described in Table 7-2. Table 7-2 Field Description New User Login ID. A user name may have up to 25 characters.
Chapter 7 System Maintenance User Access Editing User Settings The Edit User page is used to update the user settings. Note Only users with Master-level access can change the access level, delete a user, and configure the user-level account settings. To edit the user settings, do the following: Step 1 Choose Maintain > Users > Edit User. The Edit User page is displayed.
Chapter 7 System Maintenance User Access Table 7-3 Step 5 Edit User Fields (continued) Field Description Action Force Password Change Manage User To force a password change for the user. at the next login, check the Force Password Change check box. If this check Account box is checked, the user is taken to the Edit User page at the next CDSM GUI login and must initiate a password change. Concurrent User Sessions Maximum number of concurrent sessions allowed for this user.
Chapter 7 System Maintenance User Access Step 1 Choose Maintain > Users > User Default Settings. The User Default Settings page is displayed. Step 2 From the Select User drop-down list, choose a user. The User Default Settings page refreshes and displays the user settings (Figure 7-1). Figure 7-1 Step 3 User Default Settings Page Enter the settings as appropriate. See Table 7-4 for descriptions of the fields.
Chapter 7 System Maintenance User Access Table 7-4 User Default Preferences (continued) Field Description Action on Recurring Schedules Choose either Preserve Exiting Schedules or Overwrite Existing Schedules. This option is only for user-generated schedules; this option is not for imported playout schedules. Content Selection Preserving Existing Schedules keeps any content that is currently scheduled for the day and channel you selected and only fills in the empty timeslots.
Chapter 7 System Maintenance User Access Step 5 If you have master level access and you want to apply the user default settings of this page to all users, check the Apply To All Users check box. Step 6 Click Save to save the changes. To clear the fields and start over, click Reset. Configuring System Authentication Settings The System Authentication page is only visible to users with Master-level access. The System Authentication fields apply system wide to all users of the CDSM GUI.
Chapter 7 System Maintenance User Access Table 7-5 System Authentication Fields (continued) Field Description Password Expiration Reminder Interval prior to the password expiration that the user is notified about the password expiration. Idle Session Timeout Interval Maximum time a session can be idle. If the time lapse between user requests exceeds the Idle Session Timeout Interval setting, the user is redirected to the Login page.
Chapter 7 System Maintenance Server Maintenance prevent performance degradation caused by many authentication requests, install the CDSM in the same location as the RADIUS or TACACS+ server, or as close as possible to it, to ensure that authentication requests can occur as quickly as possible. Server Maintenance The Server Maintenance pages provides the ability to offload and shutdown a server for maintenance, and to restart a server without shutting it down.
Chapter 7 System Maintenance Server Maintenance Step 1 Choose Maintain > Servers > Server Shutdown. The Server Shutdown page is displayed. Step 2 From the Server IP/Name drop-down list, choose the IP address or nickname of the server and click Display. The server type and ID, as well as the array ID, are displayed. Step 3 From the Shutdown drop-down list, choose Yes and click Submit. Offloading a Server The Server Offload page lets you set a server to Online or Offline.
Chapter 7 System Maintenance Server Maintenance Step 3 In the New Server Status drop-down list, select the appropriate setting and click Submit. After setting a server to offline, current traffic activity can be monitored, and when the server offline is complete, the software can be updated. To view activity on a Vault server, see the “Monitoring Content Objects” section on page 5-6. To view activity on a Streamer, see the “Monitoring Stream Objects” section on page 5-16.
Chapter 7 System Maintenance Server Maintenance To set the system thresholds and enable or disable the system services, do the following: Step 1 Choose Maintain > Servers > System Thresholds. The System Thresholds page is displayed (Figure 7-2). Figure 7-2 System Thresholds Page Step 2 Enter the threshold settings and enable or disable the services as appropriate. Step 3 Click Submit to save the settings. To clear the fields and start over, click Reset.
Chapter 7 System Maintenance Restarting the Services Restarting the Services Each server runs services that allow the server to function with other components in the CDS. Services are not automatically restarted each time there is a configuration change. If you need to restart a service, the Services Restart page provides this option. This action does not power cycle the unit. Table 7-7 describes the different services.
Chapter 7 System Maintenance Content Manager content objects that start with that first character you entered, you are prompted to continue entering the next character of the content object name or click Display. After you click Display, the Completed Ingest page is displayed with the details of the selected content object. Step 2 To display a list of content objects, use one of the following methods: • In the Browse Content box, click one of the characters.
Chapter 7 System Maintenance Software Maintenance Software Maintenance The Software Maintenance pages provides the ability to view the CDS software, upload an electronic program guide (EPG) file, generate server IDs and group IDs for Video Virtualization Infrastructure (VVI), and perform a clean-up on the system.
Chapter 7 System Maintenance Software Maintenance In an active-standby relationship, one server acts as the authority and all streams initiate from this server. The other servers participating in streaming for the TV Playout application only take over when the active server goes offline. In an active-active relationship, all servers participating in the TV Playout application, stream the content at the same time.
Chapter 7 System Maintenance Software Maintenance Importing a TV Playout Schedule The Playout Importer page can be used to upload a Playout file, containing the Playout Scheduler data from another CDS, into the Playout Scheduler of this CDS. The Playout file is an XML file. For information about exporting a Playout file, see the “Exporting a Playout Schedule” section on page 4-106. Note The Playout Importer page is part of the TV Playout feature and is displayed only if TV Playout feature is enabled.
Chapter 7 System Maintenance Software Maintenance Uploading an EPG File The EPG File Upload page can be used to upload an electronic program guide (EPG) file into the CDS for use with the Media Scheduler. The EPG file is an XML file. Note The EPG File Upload page is part of the Media Scheduler feature. For more information, see the “Media Scheduler” section on page F-10. Before you can upload an EPG file, you need to enter the channel information.
Chapter 7 System Maintenance Software Maintenance If the Stream Manager is unable to contact the VVIM during the initial configuration, the cdsconfig script prompts the Stream Manager administrator to contact the VVIM administrator for the server ID. The VVIM administrator would then go to the Configuration Generator page to generate the IDs for the Stream Manager.
Chapter 7 System Maintenance Software Maintenance Step 3 In the Stream Manager IP field, enter the IP address of the Stream Manager that you are generating IDs for. Step 4 Click Generate New IDs. Configuration Generator Table The table on the Configuration Generator page lists the Stream Domain Name, Stream Manager IP address, and the ID ranges assigned for each Stream Manager. Stream Group ID Range and Server ID Range Sometimes the group IDs and Server IDs show as “not generated” in the table.
Chapter 7 System Maintenance Software Maintenance There is a range of server IDs, 1 to 1000, that are reserved for Vaults and Caching Nodes. It is the responsibility of the VVIM administrator to make sure the server IDs are unique among all Vaults and Caching Nodes in the VVI. The VVIM reserves a group of 250 server IDs for each Stream Domain (for example, 1001-1250, 1251-1500, and so on). To generate a server ID for a Streamer, do the following: Step 1 Step 2 Choose Maintain > Software > ID Management.
Chapter 7 System Maintenance Manuals • Duplicate Locate IP Addressees—Two or more identical entries in the control IP map table for a single Cache Group, having the same group ID, locate IP, and locate subnet IP. If this has occurred, select any one of the entries for removal, and the CDSM automatically reduces the number of entries to one.
A P P E N D I X A Troubleshooting This appendix presents troubleshooting procedures for the CDS by showing the symptoms, probable causes, and recommended actions for a variety of issues.
Appendix A Troubleshooting OpenStream Issues OpenStream Issues Following are the common connectivity problems with the OpenStream system: • CDS Server Cannot Register with OpenStream • OpenStream Reports Alert Messages CDS Server Cannot Register with OpenStream This issue could manifest in the following ways: • In the ISA Content Store Log file, which is viewable by logging in to the Linux operating system on the server, you do not see the following log entry: CorbaEventSupplier.
Appendix A Troubleshooting General Information and Issues OpenStream Reports Alert Messages OpenStream reports the following alerts: • Content creation/provisioning failed alert • Content creation/provisioning failed for ContentStore • Package partial export alert • Package provision failed alert • Provision failed alert Cause 1: CDS is unable to register with OpenStream Action 1: See the “CDS Server Cannot Register with OpenStream” section on page A-2.
Appendix A Troubleshooting General Information and Issues File System The CDSM file system differs from the file system on the CDS servers (Vault, Streamer, Caching Node, ISV). CDSM The CDSM has the following directory structures: • /arroyo/asmrpt—Contains comma-separated values (CSV) files that are created by extracting information from the database every 24 hours. These files are accessible through the Reports > Archived Data page.
Appendix A Troubleshooting General Information and Issues • /home/isa/Streaming The log files are located in the /arroyo/log directory. A log file is automatically archived and moved to the /arroyo/archive directory when it reaches close to 100 MB in size. Log Files There are three types of log files in an ISA environment: • Linux Log Files • CServer Log Files • ISA Log Files • CDSM Log Files The log files are rotated at least once a day and time stamps are added to the filenames.
Appendix A Troubleshooting General Information and Issues • /arroyo/log/protocoltiming.log.—Provides information about any network interface issues and any disk issues. • /arroyo/log/avsdb.log.—Provides information about any database issues. • /arroyo/log/avsdb-err.log. • /arroyo/log/statsd.log.—Provides system statistics information. • /arroyo/log/stresstest.log.—Provides CPU uptime information. • /root/avslauncher.log.
Appendix A Troubleshooting General Information and Issues • 8—Stream has been destroyed (cnDestroyed). Protocoltiming Warning Messages Table A-1 describes some of the warning messages that might be seen in the Protocoltiming log. Table A-1 Protocoltiming Warning Messages Warning Message Description WARNING: Fill transmit System bus is overloaded or network transmissions are not occurring fast enough and bus hold offs transmission of data is being delayed.
Appendix A Troubleshooting General Information and Issues The following log files provide information on streaming: • /arroyo/log/StreamService.log • /arroyo/log/LSCPService.log • /arroyo/log/OrphanStreams.log The following log file provides services monitoring and registration to the NameService: • /arroyo/log/ns_log CDSM Log Files The CDSM has the following logs: • httpd.log.—Apache error log • httpd_access.log.—Apache access log • cdsm.log.
Appendix A Troubleshooting General Information and Issues Table A-2 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 Description of the .
Appendix A Troubleshooting General Information and Issues controller This is the IP address of the CDSM. There is only one controller line. This line is not needed in the file for the CDSM, but is used on Vaults and Streamers to point to the CDSM. mirroring This controls local mirroring, which is to say this determines the number of copies of a given piece of content that is stored locally. partno This allows the server to identify itself properly to the CDSM.
Appendix A Troubleshooting General Information and Issues groupid # An identifier that identifies the group of servers within the CDS. See the “groupid ” section on page A-9 for more information. streamer <0 or 1> vault <0 or 1> To run the server as a Streamer, set streamer to 1, otherwise set streamer to 0. To run the server as a Vault, set vault to 1, otherwise set vault to 0. Setting both streamer and vault to 0 is not a valid option.
Appendix A Troubleshooting General Information and Issues Optional Settings The following line entries are optional in the setupfile file: management eth # Specifies the interface used for management. The default is eth0. ingest eth # Specifies the interface used for live ingests (FTP push or UDP capture). By default, the management interface is used. This parameter is applicable only to Vaults.
Appendix A Troubleshooting General Information and Issues arrayid # Specifies the array this server belongs to. The array ID is used in conjunction with the StreamDestinationMap file located in the /arroyo/test directory to determine which play servers are available for selection. This selection is based on the IP address or subnet of the destination of the packet. The default value is 0.
Appendix A Troubleshooting General Information and Issues Identifying the Software Versions or Releases The following sections describe the commands for identifying the software versions on the server. Linux OS Version To identify the software version of the Linux operating system (OS) on the CDSM, enter the following command: # cat /proc/version or "uname –a" Linux version 2.6.18-92.el5 (brewbuilder@ls20-bc2-13.build.redhat.com) (gcc version 4.1.2 20071124 (Red Hat 4.1.
Appendix A Troubleshooting General Information and Issues To view the CServer settings, status, and version, enter the following command: # cat /proc/calypso/status/server_settings AVS CServer Information ENV_ISA_SR PROD (arroyoqa@build-svr) (gcc version 4.1.2 20070626 (Red Hat 4.1.
Appendix A Troubleshooting General Information and Issues Kernel Crash The kernel debugger (KDB) provides information (in the form of a core dump file) when the server processing fails. For the server to enter KDB when the server has crashed, the /proc/sys/kernel/panic parameter must be zero. If the panic parameter is non-zero, the system reboots automatically without entering KDB. In addition to KDB, there is a kdump service. The kdump service allows you to take a kernel dump of memory.
Appendix A Troubleshooting General Information and Issues Disk Drive Issues The disk drive order is irrelevant when reinserting disk drives after transporting a chassis, or transferring disk drives from one chassis to another. To view the statistics of the internal boot drive, the disk drive that contains the software, enter the df -k command.
Appendix A Troubleshooting General Information and Issues Nov 20 19:03:36 Nov 20 19:03:42 Nov 20 19:03:42 Nov 20 19:03:43 Nov 20 19:03:45 Nov 20 19:03:46 Nov 20 19:03:46 Nov 20 19:03:46 Nov 20 19:03:47 Nov 20 19:03:47 Nov 20 19:03:48 Nov 20 19:03:48 Nov 20 19:03:48 Nov 20 19:03:48 Nov 20 19:03:48 Nov 20 19:03:50 disks = 0) Note vault219 vault219 vault219 vault219 vault219 vault219 vault219 vault219 vault219 vault219 vault219 vault219 vault219 vault219 vault219 vault219 kernel: kernel: kernel: kernel:
Appendix A Troubleshooting General Information and Issues Figure A-1 Step 6 BIOS Setup Utility—Boot Settings Press F10 to save and exit the BIOS Setup Utility. Network Following are the some common network problems: • No Output on the NSG • Vault Cannot Connect to FTP Server • Checking Network Configuration No Output on the NSG There is no output on the NSG when sending a play command. Cause 1: Cannot communicate with the QAM device or the QAM settings are incorrect.
Appendix A Troubleshooting General Information and Issues • Verify the DNS server settings by going to the Configure > System Level > DNS page. • Verify the DNS servers are reachable. Checking Network Configuration The following commands are useful for checking your network configuration and activity. To view the ARP table, enter the following command: # arp -a jetsam.v.com (111.0.110.151) at 00:00:0C:07:AC:00 [ether] on eth0 cds17-m1.v.com (111.0.210.
Appendix A Troubleshooting General Information and Issues remote server id 144 ip 111.1.9.27 ip 111.1.9.28 ip 111.1.9.29 ip 111.1.9.30 end remote server Interface Information To view basic interface information, use the ifconfig command. # ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:04:23:D8:9A:80 inet addr:111.0.110.41 Bcast:111.0.110.255 Mask:255.255.255.
Appendix A Troubleshooting Startup Issues Rx_Frame_Errors Rx_FIFO_Errors Rx_Missed_Errors Tx_Aborted_Errors Tx_Carrier_Errors Tx_FIFO_Errors Tx_Heartbeat_Errors Tx_Window_Errors Tx_Abort_Late_Coll Tx_Deferred_Ok Tx_Single_Coll_Ok Tx_Multi_Coll_Ok Rx_Long_Length_Errors Rx_Short_Length_Errors Rx_Align_Errors Rx_Flow_Control_XON Rx_Flow_Control_XOFF Tx_Flow_Control_XON Tx_Flow_Control_XOFF Rx_CSum_Offload_Good Rx_CSum_Offload_Errors 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 406625 0 PHY_Media_Type PHY_Cable_L
Appendix A Troubleshooting Startup Issues Figure A-2 Step 4 BIOS Setup Utility—Advanced Chipset Control Press F10 to save and exit. Serial Console Port Settings The CDE servers ship with the following serial console settings: 115200 baud rate, no parity, 8 data bits, and 1 stop bit (115200-N-8-1). To verify the serial console settings, check the following: • BIOS Settings—Determines the speed during the very beginning of the boot process up to and including the GRUB menu.
Appendix A Troubleshooting Management and Database Issues Required Services Not Starting or Running Correctly From the CDSM GUI, view the Services page for each server by clicking Monitor > Server Level > Services. For more information, see the “Services Monitor” section on page 5-40. If the required services are not started, or they are not running correctly, check that there is two-way database connectivity between the Streamers and Vaults, and the CDSM. $ netstat -an|grep 9999 tcp 0 0 0.0.0.
Appendix A Troubleshooting Management and Database Issues Cannot Access the CDSM GUI If you cannot access the CDSM GUI, log in as root and verify that the Apache server is running on the CDSM.
Appendix A Troubleshooting Ingest Issues Database Monitoring To monitor a stuck database thread problem, use the following command: netstat –an | grep 9999 Two connections for each Vault and Streamer should be listed with a status of “ESTABLISHED.
Appendix A Troubleshooting Ingest Issues – Check the /arroyo/log/protocoltiming.log. log file. – Verify that the correct trickmode speeds are set.
Appendix A Troubleshooting Content Processing Issues Content Processing Issues This section includes the following content processing issues: • Listing Content • Content Mirroring • Verifying GOIDs • Trick-Mode Issues • Name and Notify Services • CORBA Interface Listing Content To view the actual stored content versus what the database reports, enter the following commands: $ su - isa $ cddb $ .
Appendix A Troubleshooting Content Processing Issues Content Mirroring To enable content mirroring locally on one Vault, do the following: Step 1 Modify the /home/isa/.arroyorc file by adding the following line: cserver_opts "vault local copy count 2" Step 2 Verify that the change has propagated to the /arroyo/test/vault/setupfile file. The line “vault local copy count 2” should be added to the setupfile file. Alternatively, enable local mirroring using the tunables.
Appendix A Troubleshooting Content Processing Issues echo 2 > /proc/calypso/tunables/cm_logserverinfo To list all GOID chains, enter the following command: echo 4 > /proc/calypso/tunables/cm_logserverinfo The /arroyo/log/serverinfo.log. log file contains information about the GOIDs. Note There is no need to identify and delete damaged or orphaned GOIDs. CServer repairs any damaged GOIDs. Orphaned GOIDs are deleted when the server reboots.
Appendix A Troubleshooting Cache-Fill Issues Cache-Fill Issues This section covers the following cache-fill issues: • Tracking Cache-Fill Source • Rules for ISV Interoperability with Vaults and Streamers • Network Tracking Cache-Fill Source You can track whether or not a GOID for a stream is filling remotely or locally by enabling and tracking it in the fill.log. Streams can share the same GOID; in which case it is not possible to tell which stream is currently filling the data.
Appendix A Troubleshooting Streaming and Playout Issues • An ISV can cache-fill both a colocated Streamer and a dedicated remote Streamer. • An ISV at one location cannot cache-fill a Streamer associated with an ISV at another location. • Two ISVs can mirror content with each other, but an ISV and a Vault cannot mirror content with each other. • A Vault cannot cache-fill an ISV. Network Note For more network troubleshooting methods, see the “Network” section on page A-27.
Appendix A Troubleshooting Streaming and Playout Issues Listing of Streams To monitor streams based on various criteria, go to the Stream Monitor page in the CDSM GUI by clicking Monitor > System Level > Stream Monitor. For more information, see the “Stream Monitor” section on page 5-16. No Streaming Some common causes for streaming problems are the following: • Server is in the process of being offloaded. • QAM device has no available bandwidth.
Appendix A Troubleshooting Streaming and Playout Issues The CServer returns the same completion code, so the same error is returned in the announce message. In this case, the content does not stream at all. The play request and play response are separated by about 10 to 15 seconds, instead of the typical subsecond separation. This is because of the ARP timeout process the CServer is going through to reach the destination.
Appendix A Troubleshooting Session Messaging – Verify that the appropriate bit rates are being sent from the server using the following command on all Streamers: /home/stats/ifstats – Verify that the content plays locally, and on a test client device (for example, a VLC client). – Test playing the content on an alternate player with an AVC plug-in. • Verify that the CDS is configured correctly. – Check the run script in the /arroyo/test/run directory.
Appendix A Troubleshooting Database Issues Table A-3 LSCP Status Codes (continued) State Code (hexadecimal) Description LSC_IMP_LIMIT 18 Implementation limit exceeded LSC_TRANSIENT 19 Transient error - reissue LSC_NO_RESOURCES 1a No resources LSC_SERVER_ERROR 20 Server error LSC_SERVER_FAILURE 21 Server has failed LSC_BAD_SCALE 30 Incorrect scale value LSC_BAD_START 31 Stream start time does not exist LSC_BAD_STOP 32 Stream stop time does not exist LSC_MPEG_DELIVERY 40 Unab
Appendix A Troubleshooting Database Issues Many Log Files If one of the following conditions exists, it indicates that there were database replication errors: • There are many log files with a filename similar to log.00000XXXX in the /home/isa/Berkeley/DATADIR directory. • Database could not be started. See the “Services Monitor” section on page 5-40 for more information. • Bidirectional connections are lost between servers.
Appendix A Troubleshooting Advanced Features and Applications isa 2646 1 0 Jan09 ? 00:14:50 /home/isa/Berkeley/avsdb root 26088 26059 0 13:23 pts/1 00:00:00 grep avsdb Make sure there is no avsdb process returned. If the avsdb hangs, use the process ID (2646 in the above example) with the kill command. # kill -9 2646 Step 3 Delete all files in the /arroyo/db/DATADIR directory. Step 4 As user root, stop the Vault database. # /usr/bin/db_shutdown Step 5 Confirm that the database is shut down.
Appendix A Troubleshooting Frequently Asked Questions Ingest without Media Scheduler Using Real-Time Capture for live multicast ingest requires the following procedures: 1. Enable live ingest by configuring Ingest Manager ON and setting Real-Time Capture Type to Real-Time Capture (non-Media Scheduler) in the CDSM Setup page. Activate the Ingest Manager. Because the Ingest Manager is an optional feature, an activation key is required.
Appendix A Troubleshooting Frequently Asked Questions A. After starting the database, you should see two sockets (listening and non-listening) connecting to the database on each of the remote servers on port 9999. You can check them by using the netstat -an | grep 9999 command. For example, the following output of the netstat command shows that the server (172.22.97.194) has both the listening and non-listening sockets binding on port 9999 to echo the four remote servers (172.22.97.192, 172.22.97.
Appendix A Troubleshooting Frequently Asked Questions Q. How do I check the Streamer static ARP table? A. Log in to the server as root and enter the following command: # cat /arroyo/test/ArpTable ip 192.168.2.42 mac 000000000002 ip 192.168.2.43 mac 000000000002 Q. How do I view the ARP Table dump file? A. Log in to the server as root and enter the following command: # echo 1 > /proc/calypso/test/arp_dumpstate Q. How do I recover the system from the kernel debugger (KDB) after a reboot? A.
Appendix A Troubleshooting Frequently Asked Questions Note Make sure there are no streams running before you use this command. If there are streams, the data cache in memory is not cleared. Q. How do I destroy all streams? A. Log in to the server as root and enter the following commands: # su - isa # cd ~/IntegrationTest # ./destroy_all_streams All sessions are removed, and upon restarting the services, all streams that do not have an associated session are stopped. Q.
Appendix A Troubleshooting Frequently Asked Questions # cat /arroyo/log/serverinfo.log.01132009 Check the last set of output lines to see the current content states. Object Count=37708 LengthUnknown=0 CouldNotRepair=0 IsDamaged=0 BeingRepaired=0 BeingCopied=0 needCrcValidate=37708 isFragFlag=0 isFragd=0 Defrag=0 Smooth=0 BeingFilled=0 OutOfService=0 NeedsISACheck=0 BeingDeleted=0 HasHoles=0 CopyHoles=0 SectorHoles=0 Object Status Check Complete. Q. How do I know if a content object has “holes”? A.
Appendix A Troubleshooting Frequently Asked Questions e1000 0: streaming 1 fill 0 e1000 1: streaming 1 fill 0 e1000 3: streaming 0 fill 1 streamer 1 vault 1 serverid 64 groupid 64 maxpacketsize 1316 management eth0 ingest eth0 trickspeedsv2 10 0 0 0 0 0 0 0 ftpout if eth0 max utilization mbps 0 max sessions 0 fake cylindermap 1 test 4 Q. How do I know if a subsystem on a server is overloaded? A. View the .arroyo.log.protocoltiming.log. file.
Appendix A Troubleshooting CDS Content Quality Guidelines CDS Content Quality Guidelines This section covers the following topics: • Supported Elementary Stream Types • Scrambling • Transport Bit Rate • Stream Length • Format Restrictions • Preferred Formats Supported Elementary Stream Types Video-only, audio-only (as well as audio streams with only a few or occasional video frames) and data-only streams are supported in addition to the customary multiplex of both audio and video.
Appendix A Troubleshooting CDS Content Quality Guidelines Format Restrictions Following are the format restrictions for Advanced Video Coding (AVC), H.264, and MPEG-4: • Sequence Parameter Set (SPS) seq_parameter_set_id flag must be zero. • SPS pic_order_count_type flag must be zero. • SPS seq_scaling_matrix_present_flag must be zero. • SPS profile_idc flag must only be Baseline, Main, or High profile.
Appendix A Troubleshooting CDS Content Quality Guidelines 15. Audio and video are expected not to overflow the appropriate target buffer model specified. 16. A reasonable bit rate to use when encoding MPEG-2 standard definition (SD) video is 3.75 Mbps. 17. A reasonable bit rate to use when encoding MPEG-2 high definition (HD) video is 15 Mbps. 18.
Appendix A Troubleshooting CDS Content Quality Guidelines Cisco TV CDS 2.
A P P E N D I X B Creating Bulk Configuration Files This appendix describes the Bulk Configuration feature and consists of the following topics: • Introduction, page B-1 • Creating QAM Gateway and Headend Setup Bulk Configuration Files, page B-2 • Creating Stream Destination Bulk Configuration Files, page B-9 • Creating Route Table Bulk Configuration Files, page B-10 • Creating SNMP Agent Bulk Configuration Files, page B-11 • Creating DNS Server Bulk Configuration Files, page B-12 • Creating
Appendix B Creating Bulk Configuration Files Creating QAM Gateway and Headend Setup Bulk Configuration Files Creating QAM Gateway and Headend Setup Bulk Configuration Files The QAM Gateway Bulk Configuration files differ depending on the type of streaming mode and the type of QAM. The required elements correspond to the fields on the associated CDSM GUI page.
Appendix B Creating Bulk Configuration Files Creating QAM Gateway and Headend Setup Bulk Configuration Files For information about the values of the attributes, see the “Configuring QAM Gateways” section on page 4-4. The ServerID and GroupID attributes are assigned during the initial configuration of the server and are displayed as server ID and group ID on the Server Setup page. For more information, see the “Configuring the Servers” section on page 4-112.
Appendix B Creating Bulk Configuration Files Creating QAM Gateway and Headend Setup Bulk Configuration Files ServiceGroup="4666664" ServiceGroup="4666663" ServiceGroup="1666669" ServiceGroup="1666668" ServiceGroup="1666664" ServiceGroup="1666663" StreamGroup="NEWTEST" /> StreamGroup="s234" /> StreamGroup="NEWTEST123" /> StreamGroup=
Appendix B Creating Bulk Configuration Files Creating QAM Gateway and Headend Setup Bulk Configuration Files Table B-3 Bulk Configuration File Elements for ASI QAM Gateways (continued) Tag Elements Attributes Description QAMLink — Status ServiceGroup RFNumber Used for the following ASI QAM devices: • NSG-8108 • NSG-9000 • NSG-9116 • GQAM Shared • SA xDQA • MOTO Sem8 • MOTO Sem12 • GigE Gen (with up to 24 service groups and RF ports) The Type attribute value of the QAM element must
Appendix B Creating Bulk Configuration Files Creating QAM Gateway and Headend Setup Bulk Configuration Files Note The ServerID and GroupID attributes can have the value ALL if the configuration applies to all servers in the CDS. The ALL value is case sensitive. The TSIDInLinkStatus, TSIDOutLinkStatus, and Status attributes have either the Enable value or the Disable value. The Enable and Disable values are case sensitive.
Appendix B Creating Bulk Configuration Files Creating QAM Gateway and Headend Setup Bulk Configuration Files PAGE 374Appendix B Creating Bulk Configuration Files Creating QAM Gateway and Headend Setup Bulk Configuration Files
PAGE 375Appendix B Creating Bulk Configuration Files Creating Stream Destination Bulk Configuration Files Creating Stream Destination Bulk Configuration Files If the Stream Destination is set to IPTV, the Stream Destination page is displayed instead of the QAM Gateway and Headend Setup pages. The Stream Destination feature is available only for single-site steering and in ISA environments that use gigabit Ethernet streaming as the streaming mode.
Appendix B Creating Bulk Configuration Files Creating Route Table Bulk Configuration Files Creating Route Table Bulk Configuration Files The Route Table page allows you to define multiple subnets on a server. For more information, see the “Configuring the Route Table” section on page 4-118. Table B-5 defines the Bulk Configuration file elements for the Route Table page.
Appendix B Creating Bulk Configuration Files Creating SNMP Agent Bulk Configuration Files PAGE 378Appendix B Creating Bulk Configuration Files Creating DNS Server Bulk Configuration Files PAGE 379Appendix B Creating Bulk Configuration Files Creating NTP Server Bulk Configuration Files first.sp.com second.abc.com third.xyz.com 152.1.1.10 222.2.2.11 Creating NTP Server Bulk Configuration Files The NTP Server page is used to configure the NTP servers. Table B-8 defines the Bulk Configuration file elements for the NTP Server page.
Appendix B Creating Bulk Configuration Files Bulk Configuration XML Schema Bulk Configuration XML Schema The XML Schema file describes and dictates the content of the XML file. The BulkConfiguration.xsd file contains the XML schema. PAGE 381Appendix B Creating Bulk Configuration Files Bulk Configuration XML Schema
Appendix B Creating Bulk Configuration Files Bulk Configuration XML Schema type="xs:string"/> PAGE 383Appendix B Creating Bulk Configuration Files Bulk Configuration XML Schema minOccurs="0" maxOccurs="unbounded"/>
type="xs:string"/> type="xs:string"/>
Appendix B Creating Bulk Configuration Files Bulk Configuration XML Schema
Appendix B Creating Bulk Configuration Files Bulk Configuration XML Schema type="xs:string"/> <
Appendix B Creating Bulk Configuration Files Bulk Configuration XML Schema Cisco TV CDS 2.
A P P E N D I X C BMS Communication This appendix describes the required Business Management System (BMS) configuration settings necessary for communicating with the CDS. OpenStream/ISA This section is not meant to replace the OpenStream installation manual. Instead, it is more of a a “cheat sheet” offering a list of values that must be the same on both the OpenStream BMS and the CDS to ensure communication between them. For more information, see the OpenStream Installation Manual.
Appendix C BMS Communication OpenStream/ISA In addition to the IP addresses of the Naming and Notification Services, the parameters described in Table C-2 must have the same values on both the OpenStream BMS and the CDS.
Appendix C BMS Communication OpenStream/ISA Lastly, there are four other parameters that need to be considered when configuring the OpenStream BMS and the CDS. They are: • Headend ID • LSC Response Padding • Sessions Poll Time • Stream Timeout Time These four parameters in the CDS with their default values work properly with the OpenStream BMS.
Appendix C BMS Communication OpenStream/ISA Cisco TV CDS 2.
A P P E N D I X D SNMP MIB and Trap Information This appendix describes the Simple Network Management Protocol (SNMP) management objects and traps sent by the CDS. The topics covered in this appendix include: • Overview, page D-1 • SNMP Management Objects and Traps, page D-2 • RFC Compliance, page D-6 Overview You can manage the servers by way of SNMP from a Network Management System (NMS).
Appendix D SNMP MIB and Trap Information SNMP Management Objects and Traps # chkconfig --add snmpd The following command configures snmpd to be turned on in run levels 5 and 6: # chkconfig --level 56 snmpd on SNMP Log The SNMP log file, snmpd.log, is located in the /arroyo/log directory. All log entries use UTC for the time stamp. All TV CDS-specific SNMP traps are logged in the snmpd.log file.
Appendix D SNMP MIB and Trap Information SNMP Management Objects and Traps The CISCO-CDS-TV-MIB.my file has the following MIB nodes: • cdstvConfigObjects—Configuration of servers • cdstvMonitorObjects—Monitoring of cache-fill, streaming, disk states, and services running • cdstvNotifyObjects—Objects specific to traps (notifications), for example, Managed Services Architecture (MSA) event objects Table D-1 describes the traps in the CISCO-CDS-TV-MIB.
Appendix D SNMP MIB and Trap Information SNMP Management Objects and Traps Table D-1 Cisco TV CDS Traps (continued) Trap Description cdstvSysHealthUp Previously abnormal system health parameter is now normal, that is, it has left the not OK state. See Table D-2 on page D-5 for the descriptions of the objects sent with this trap. cdstvSysHealthDown Previously normal system health parameter is now abnormal, that is, it has left the OK state.
Appendix D SNMP MIB and Trap Information SNMP Management Objects and Traps Monitored Broken Assets SNMP Traps After the statsd process is started, it waits 5 minutes (300 seconds) before collecting statistics. If a broken asset occurs within these 5 minutes, it is detected and the cdstvBrokenAsset trap is sent. After the first cycle of collecting statistics is complete, statsd waits 60 minutes from the beginning of the previous cycle before collecting statistics again. This repeats every 60 minutes.
Appendix D SNMP MIB and Trap Information RFC Compliance Table D-2 System Health SNMP Trap Objects Descriptor Possible values Description cdstvSysHealthReading Integer Current reading (value) of the system health parameter; for example, fan speed, voltage, or temperature. Fan speed is expressed in revolutions per minute (rpm), voltage in millivolts (mV) and temperature in degree Celsius. For chassis intrusion and power-supply failure, 1 denotes an error condition, and 0 denotes normal condition.
Appendix D SNMP MIB and Trap Information RFC Compliance Table D-3 SNMP RFC Standards (continued) RFC Standard Title RFC 1904 (Draft Standard) Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2) RFC 1905 (Draft Standard) Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2) RFC 1906 (Draft Standard) Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2) RFC 1910 (Historic) User-based Security Model fo
Appendix D SNMP MIB and Trap Information RFC Compliance Table D-3 SNMP RFC Standards (continued) RFC Standard Title RFC 2573 (Draft Standard) SNMP Applications RFC 2574 (Draft Standard) User-based Security Model (USM) for Version 3 of the Simple Network Management Protocol (SNMPv3) RFC 2575 (Draft Standard) View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) RFC 2576 (Proposed Standard) Coexistence between Version 1, Version 2, and Version 3 of the Internet
A P P E N D I X E Using the TV CDS Streamer Application Monitoring Tool This appendix describes the TV CDS Streamer Application Monitoring Tool (AMT) that can be used to monitor the VOD Error Repair feature. For more information about VOD Error Repair, see the “VOD Error Repair” section on page 1-8.
Appendix E Using the TV CDS Streamer Application Monitoring Tool Overview Logging In to AMT AMT uses HyperText Transport Protocol Secure (HTTPS) to access the browser-based GUI. Any valid Linux username and password can be used to log in to AMT. The username does not have to belong to any special group. To log in to AMT, do the following: Step 1 Using your web browser, enter the IP address or hostname of your Streamer. For example, if the IP address of your Streamer is 192.168.0.
Appendix E Using the TV CDS Streamer Application Monitoring Tool AMT Statistics AMT Statistics This section provided general information about the information displayed in AMT. Click Refresh to update the displayed data. The AMT statistical data is not updated automatically. The last refresh date and time are displayed to the right of the Refresh button. Table E-1 describes the information displayed for each page of AMT.
Appendix E Using the TV CDS Streamer Application Monitoring Tool AMT Statistics Table E-1 AMT GUI Pages (continued) Navigation Tree and Tab Information Provided RTP Sessions Displays the following information on VOD Sessions that can be filtered by session ID, or session destination and subnet mask: • Status • Session ID • Content name • Source IP address and port • Destination IP address and port • Bit rate (Kbps) • Repair Enabled If a filter is entered, click Submit to see the filter
Appendix E Using the TV CDS Streamer Application Monitoring Tool AMT Statistics Table E-1 AMT GUI Pages (continued) Navigation Tree and Tab Information Provided RTCP Exporter Configuration Displays configuration settings for the VQM CDA.
Appendix E Using the TV CDS Streamer Application Monitoring Tool AMT Statistics Table E-2 lists the information in the Error Repair Statistics page. Table E-2 Error Repair Statistics Field Description Generic NACK Messages Received Total Messages Number of NACK messages received by this Streamer. Invalid Messages Number of invalid messages received by this Streamer. Invalid messages are received messages that, for example, cannot be parsed.
Appendix E Using the TV CDS Streamer Application Monitoring Tool AMT Statistics Viewing Excess Bandwidth When you click Error Repair in the navigation tree and click the Excess BW tab, AMT displays the Excess BW page (see Figure E-3). Figure E-3 Excess BW Page If Error Repair is enabled and active, you can choose to display a client e-factor histogram or table by clicking the icons in the upper-right corner of the page. Use the Select a historgram drop-down menu to select Error Repair histograms.
Appendix E Using the TV CDS Streamer Application Monitoring Tool AMT Statistics Cisco TV CDS 2.
A P P E N D I X F 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: • CDSM or VVIM Diagnostics, page F-2 • CDSM or VVIM Setup, page F-3 • System Configs, page F-12 The Engineering access level is primarily used for initializing the CDS at the time of installation and for system diagnostics.
Appendix F Engineering Access Level Pages CDSM or VVIM Diagnostics CDSM or VVIM Diagnostics To access the CDSM or VVIM Diagnostics page, choose Maintain > Software > CDSM Diagnostics or VVIM Diagnostics. The first section of this page provides configuration information that is useful in diagnosing a problem.
Appendix F Engineering Access Level Pages CDSM or VVIM Setup 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.
Appendix F Engineering Access Level Pages CDSM or VVIM Setup Stream Destination The possible settings for Stream Destination are Cable, IPTV, Mixed, and Auto. 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.
Appendix F Engineering Access Level Pages CDSM or VVIM Setup Bulk Configuration 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 (For gigabit Ethernet streaming mode.
Appendix F Engineering Access Level Pages CDSM or VVIM Setup Groups mirror the content), which may be in different geographic regions. The Vault Groups feature adds the Vault Groups, Master Vault Group, and Vault Redundancy Map configuration pages to the Array Level. Note The maximum number of Vault Groups is 20. nDVR This feature is not activated in this release.
Appendix F Engineering Access Level Pages CDSM or VVIM Setup Error Repair Client on STB VOD Error Repair feature requires that the STB have the Cisco Visual Quality Experience Client (VQE-C) software running on it.
Appendix F Engineering Access Level Pages CDSM or VVIM Setup 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.
Appendix F Engineering Access Level Pages CDSM or VVIM Setup – Cache Fill Protocols: CCP For more information on configuring ISA Regionalization, see the “ISA Regionalization Configuration Workflow” section on page 3-9.
Appendix F Engineering Access Level Pages CDSM or VVIM Setup Configure > Array Level in the CDSM. The Shared ISA Setup page has all the Content Store information configured on the Vaults that is shared with all the VBOs. The VHO ISA Setup page has the Stream Services information for similar groups of Stream Groups in the same VHO.
Appendix F Engineering Access Level Pages CDSM or VVIM Setup 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. Playout Scheduler Playout Scheduler is only available in an ISA environment on a VVI with central management or a legacy CDSM.
Appendix F Engineering Access Level Pages System Configs Ingest Steering The Ingest Steering feature works with the VVI and Vault Groups features. When Ingest Steering is enabled (along with VVI central management and Vault Groups), the Ingest Steering configuration page displays at the Array Level, and the Vault Group Setup page offers the ability to assign a Vault Group to either a local or national location.
Appendix F Engineering Access Level Pages System Configs Add New Server Should you experience problems adding a new server into the CDS, and you have tried the solutions covered in the “CDSM GUI Does Not Register the Vaults and Streamers” section on page A-25, you can use the Add New Server section. Cisco TV CDS 2.
Appendix F Engineering Access Level Pages System Configs Cisco TV CDS 2.
A P P E N D I X G Software Licensing Information This appendix provides software license information related to the TV CDS. Notices The document Open Source Used in Cisco TV Content Delivery System, Release 2.5 contains licenses and related license information for open-source software included in Cisco TV CDS, Release 2.5. The document is located at the following URL: http://www.cisco.com/en/US/products/ps7127/products_licensing_information_listing.
Appendix G Software Licensing Information Product Warranties Cisco TV CDS 2.
