Cisco Service Router Application Configuration Guide
Tangazo
Tangazo
Cisco TV CDS 2.3 RTSP
Software Configuration Guide
December 2010
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA http://www.cisco.com
800 553-NETS (6387)
Text Part Number: OL-22792-01
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.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
CCDE, CCENT, CCSI, Cisco Eos, Cisco Explorer, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase,
Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco TrustSec, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip
Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work,
Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and
Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the
Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity,
Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the
IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY,
PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1002R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
© 2010 Cisco Systems, Inc. All rights reserved.
OL-22792-01
C O N T E N T S
Preface
xiii
xiii
xiii
xiv
xiv
xv
xvi
Obtaining Documentation and Submitting a Service Request
xvi
Product Overview
1-1
1-1
1-3
1-4
1-4
1-4
Streamer Content Delivery Applications
1-4
Content Delivery System Architecture
1-5
1-6
1-7
1-7
1-7
Content Delivery System Manager and Virtual Video Infrastructure Manager
1-7
1-9
1-9
1-10
1-10
1-10
1-11
1-11
1-11
1-11
1-11
1-12
Cisco TV CDS 2.3 RTSP Software Configuration Guide iii
Contents
Network Design
2-1
2-1
2-1
2-2
2-2
TV CDS Topologies and VVI Topologies
2-2
2-3
2-4
2-5
2-6
2-7
2-7
2-7
2-8
2-8
2-9
2-9
2-9
2-10
BMS Considerations for RTSP Environments
2-11
2-11
2-12
2-14
2-15
2-15
2-15
2-15
Getting Started
3-1
Initially Configuring the Devices
3-1
3-1
3-3
Initializing the CDS and Activating the Optional Features
3-3
3-4
3-4
3-5
3-5
3-6
Cisco TV CDS 2.3 RTSP Software Configuration Guide iv OL-22792-01
OL-22792-01
3-6
Split-Domain Management Workflow
3-7
TV MediaX Configuration Workflow
3-8
Configuring the CDS
4-1
4-1
4-2
4-3
4-3
4-4
4-4
4-5
4-7
Configuring Stream Destinations
4-8
Configuring the Bandwidth Manager
4-10
Configuring the Ingest Manager
4-11
Configuring the Authentication Manager
4-15
Configuring the Redirect Server
4-17
4-17
4-20
Configuring the Media Importer
4-21
4-22
4-24
Configuring Source Output Ports
4-26
4-27
4-27
Configuring the Array Level DNS
4-28
Configuring the Array Level NTP Server
4-29
4-29
VVI with Split-Domain Management and HTTP Streamers
4-29
4-31
4-33
4-35
4-36
Mapping Vault Groups to Cache Groups
4-38
Mapping Stream Groups to Cache-Fill Sources
4-39
Mapping Vault Groups for Redundancy
4-40
Configuring the Master Vault Group
4-42
Configuring the Control and Setup IPs
4-42
Cisco TV CDS 2.3 RTSP Software Configuration Guide
Contents v
Contents
Configuring Cache-Fill Bandwidth Using Thin Pipe Mapping
4-44
Configuring the Media Scheduler
4-47
4-47
4-49
4-52
Fixing Conflicts in the Media Scheduler
4-54
4-55
4-55
4-58
4-65
4-66
4-66
CServer Destination Route Type
4-67
4-67
4-69
Configuring the Server Level DNS
4-71
Configuring the Server Level NTP
4-72
4-73
4-75
4-75
4-81
System Monitoring
5-1
5-1
5-2
5-3
5-4
5-5
5-5
5-10
5-10
5-12
5-13
5-13
5-18
5-24
5-24
5-25
5-25
Cisco TV CDS 2.3 RTSP Software Configuration Guide vi OL-22792-01
OL-22792-01
5-27
5-28
5-29
5-31
5-32
Recommended Monitoring Schedule
5-33
5-33
5-34
Monitoring Tasks for Streamers and Vaults
5-34
5-35
Monitoring Tasks for Streamers
5-36
5-36
5-36
System Reporting
6-1
6-1
6-2
6-6
6-9
6-13
6-15
6-18
6-20
6-20
6-22
6-23
6-25
6-26
6-26
6-27
6-28
6-28
System Maintenance
7-1
7-2
7-2
7-3
7-3
Cisco TV CDS 2.3 RTSP Software Configuration Guide
Contents vii
Contents
7-3
Changing User Default Settings
7-4
7-5
7-5
7-6
7-6
7-7
7-7
7-9
7-9
Viewing the Software Version and Server Information
7-9
7-10
Identifying Server IDs and Group IDs for VVI with Split-Domain Management
7-10
Generating Server IDs and Group IDs from the VVIM
7-11
7-13
Troubleshooting
A-1
A-2
A-2
A-2
A-3
A-3
A-3
A-4
A-6
A-7
Description of the .arroyorc Settings
A-7
Description of the setupfile Settings
A-8
Identifying the Software Versions or Releases
A-12
A-12
A-12
Using ifstats to Monitor Traffic
A-14
A-14
A-15
CDSM GUI Disk Monitor Page Reports a Disk Warning
A-16
A-17
A-18
A-19
A-20
Cisco TV CDS 2.3 RTSP Software Configuration Guide viii OL-22792-01
OL-22792-01
BIOS Settings—Operating System Hangs or Goes into KDB Mode
A-20
A-21
Required Services Not Starting or Running Correctly
A-22
Management and Database Issues
A-22
A-22
A-23
CDSM GUI Does Not Register the Vaults and Streamers
A-23
A-24
A-24
A-24
FSI Starts but Cannot Ingest Content
A-24
A-25
A-25
Asset Ingest Manager Restart Causes Endless Loop
A-26
A-27
A-27
A-28
A-28
A-28
A-29
A-29
A-30
Rules for ISV Interoperability with Vaults and Streamers
A-30
A-30
Stream Stops Playing at the Same Place or Does Not Play at All
A-30
A-31
A-31
A-31
A-32
A-33
A-33
A-34
A-34
A-34
CDS Is Streaming but No Video Is Playing on the STB
A-35
A-36
A-36
A-37
A-38
Cisco TV CDS 2.3 RTSP Software Configuration Guide
Contents ix
Contents
A-39
CDSM GUI Does Not Report All the Ingested Content
A-39
A-39
A-39
A-40
Advanced Features and Applications
A-41
A-41
A-41
Ingest without Media Scheduler
A-42
A-42
A-42
A-42
Serviceability and Manageability
A-43
A-45
A-46
CDS Content Quality Guidelines
A-47
Supported Elementary Stream Types
A-47
A-47
A-48
A-48
A-48
A-48
Creating Bulk Configuration Files
B-1
B-1
Creating QAM Gateway Bulk Configuration Files
B-2
Creating Headend Setup Bulk Configuration Files
B-3
Creating Stream Destination Bulk Configuration Files
B-4
Creating Route Table Bulk Configuration Files
B-5
Creating SNMP Agent Bulk Configuration Files
B-6
Creating DNS Server Bulk Configuration Files
B-7
Creating NTP Server Bulk Configuration Files
B-8
Creating FSI Setup Bulk Configuration Files
B-9
Creating RTSP Setup Bulk Configuration Files
B-10
B-13
SNMP MIB and Trap Information
C-1
C-1
Cisco TV CDS 2.3 RTSP Software Configuration Guide x OL-22792-01
OL-22792-01
C-1
SNMP Management Objects and Traps
C-2
C-5
Engineering Access Level Pages
D-1
D-2
D-2
D-2
D-2
D-2
D-3
D-3
D-3
D-3
D-3
D-3
D-4
D-4
D-4
D-4
D-5
D-5
D-5
D-6
D-6
D-6
D-6
Configuring Split-Domain Management
D-7
D-7
D-7
D-7
D-8
D-8
D-8
D-8
D-9
D-9
CDSM or VVIM Health Monitoring
D-9
D-9
Cisco TV CDS 2.3 RTSP Software Configuration Guide
Contents xi
Contents
D-9
D-9
D-9
D-9
D-10
Software Licensing Information
E-1
E-1
E-1 xii
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Preface
This preface describes the audience, use, and organization of the Cisco TV CDS 2.3 RTSP Software
Configuration Guide. The preface also outlines the document conventions and support information.
This preface contains the following sections:
•
•
•
•
•
Document Revision History, page xiii
Document Organization, page xiv
•
•
Related Documentation, page xvi
Obtaining Documentation and Submitting a Service Request, page xvi
Document Revision History
The Document Revision History table below records technical changes to this document.
Document Revision Date
OL-22792-01 December, 2010
Change Summary
Initial release
Audience
This guide is for the networking professional managing the Cisco TV Content Delivery System, hereafter referred to as CDS. Before using this guide, you should have experience working with the Cisco
IOS software and be familiar with the concepts and terminology of Ethernet, local area networking, and
TV streaming.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide xiii
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. For information on installing the hardware, see the Cisco Content Delivery Engine 100/200/300/400
Hardware Installation Guide, the Cisco Content Delivery Engine 110 Hardware Installation Guide, or the Cisco Content Delivery Engine 205/220/250/420 Hardware Installation Guide. See the
Documentation” section on page xvi
for links to documentation online.
For documentation updates, see the release notes for this release.
Document Organization
This document contains the following chapters and appendices:
Chapters or Appendices
Chapter 4, “Configuring the CDS”
Chapter 5, “System Monitoring”
Chapter 7, “System Maintenance”
Descriptions
Provides an overview of the Content Delivery System.
Describes the possible network topologies for the
Content Delivery System.
Describes accessing and navigating the Content Delivery
System Manager (CDSM).
Describes how to configure the CDS using the CDSM web-based user interface.
Explains how to monitor the CDS components using the
CDSM.
Explains the different reports available through the
CDSM.
Explains how to install software updates, restart services, add administrator users, and shut down and reboot the servers.
Presents troubleshooting procedures for the CDS, including the symptoms, probable causes, and recommended actions for a variety of problems.
Appendix B, “Creating Bulk Configuration
Provides information on creating Bulk Configuration
XML files.
Appendix C, “SNMP MIB and Trap
Appendix D, “Engineering Access Level
Appendix E, “Software Licensing
Provides information on SNMP and the Cisco TV CDS proprietary SNMP informational events and traps.
Describes the CDSM pages visible with the Engineering access level.
Provides information on open-source licenses and
Cisco’s software licensing agreement.
xiv
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Preface
Document Conventions
This guide uses the following conventions for command syntax descriptions and textual emphasis:
Conventions
boldface font
italic font
[ ]
{x | y | z}
[x | y | z]
Descriptions
Commands and keywords are in boldface.
Arguments for which you supply values are in italics.
Elements in square brackets are optional.
Alternative, mutually exclusive, keywords are grouped in braces and separated by vertical bars.
Optional alternative keywords are grouped in brackets and separated by vertical bars.
string
italic screen
font
^
A nonquoted set of characters. Do not use quotation marks around the string or the string will include the quotation marks.
Terminal sessions and information the system displays are in screen
font.
screen
font
boldface screen
font Information you must enter is in
boldface screen
font.
Arguments for which you supply values are in
italic screen
font.
< >
The symbol ^ represents the key labeled Control—for example, the key combination ^D in a screen display means hold down the Control key while you press the D key.
Nonprinting characters, such as passwords, are in angle brackets in contexts where italics are not available.
!, # An exclamation point ( ! ) or a pound sign ( # ) at the beginning of a line of code indicates a comment line.
Caution
Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.
Note
Means reader take note. Notes contain helpful suggestions or references to materials not contained in this publication.
Tip
Means the following information might help you solve a problem.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide xv
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.3.1
•
•
•
•
•
•
Cisco TV CDS 2.3 ISA Software Configuration Guide
Cisco TV CDS 2.1–2.3 API Guide
Cisco Content Delivery Engine 205/220/250/420 Hardware Installation Guide
Cisco Content Delivery Engine 110 Hardware Installation Guide
Cisco Content Delivery Engine 100/200/300/400 Hardware Installation Guide
Cisco Content Delivery System 2.x Documentation Roadmap
•
Regulatory Compliance and Safety Information for Cisco Content Delivery Engines
You can access the software documents at the following URL: http://www.cisco.com/en/US/products/ps7127/tsd_products_support_series_home.html
You can access the hardware documents at the following URL: http://www.cisco.com/en/US/products/ps7126/tsd_products_support_series_home.html
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
xvi
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
C H A P T E R
1
Product Overview
This chapter provides a brief introduction to the Cisco TV Content Delivery System for a Real Time
Streaming Protocol (RTSP) environment. This chapter covers the following major topics:
•
•
Content Delivery System Architecture, page 1-5
Overview
The Cisco TV Content Delivery System (CDS) is a distributed network of Content Delivery Engines
(CDEs) running Content Delivery Applications (CDAs) that collaborate with each other to deliver personalized entertainment and interactive media to subscribers.
The Cisco TV CDS has a variety of mechanisms to accelerate the distribution and delivery of content.
The CDS interoperates with electronic program guides (EPGs), set-top boxes (STBs), and backoffice applications, offering an end-to-end solution for video delivery systems.
The Cisco TV CDS functionality can be separated into five areas:
•
Ingest
•
•
•
•
Storage
Caching
Streaming
Management
Each CDE in the CDS contributes to one or more of these functions as determined by the CDAs running on it.
describes the relationship between the CDA names and the names the TV Content
Delivery System Manager (CDSM) uses.
Table 1-1 CDA Mapping to Functionality and CDSM
CDA Name
Vault
Content Cache
TV Streamer
Functionalities
Ingest and storage
CDSM Device Name
Vault
Content distribution between Vaults and Streamers Caching Node
Content caching, personalization, and streaming to STBs Streamer
Cisco TV CDS 2.3 RTSP Software Configuration Guide
1-1 OL-22792-01
Overview
Figure 1-1
Chapter 1 Product Overview
Table 1-1 CDA Mapping to Functionality and CDSM (continued)
CDA Name
TV MediaX Suite
Functionalities
Aids content ingest workflow and scheduling tasks for both asset-based and real-time content
Management
CDSM Device Name
CDSM
CDSM TV Content
Delivery System
Manager
illustrates how a TV CDS network can be deployed. A business management system (BMS), commonly called a backoffice, enables service providers to deploy on-demand services using video on demand (VOD) servers, networks, billing systems and other system components. The asset management system (AMS) manages the content on headend and node servers, while the BMS handles functions related to pitching and catching. Sometimes there is some overlap of functionality between the BMS and the AMS.
There are two types of systems available with the TV CDS: a CDS with an array of Vaults and Streamers, and a Virtual Video Infrastructure (VVI) with an array of Vaults, Caching Nodes, and Streamers. The
CDSM manages the Vaults and Streamers in a CDS. The VVIM manages the Vaults, Caching Nodes, and
Streamers in a VVI with centralized management. For more information about network design and VVI management, see the
“TV CDS Topologies and VVI Topologies” section on page 2-2
a high-level view of both a CDS and a VVI.
High-Level System View of Content Delivery System and Virtual Video Infrastructure
Asset
Management
System
Business
Management
System
Metadata
Raw
Data
Content
Provider
CDSM
(VVIM)
4-6 GigE
1-12GigE
Vault Array
Management
Management
Switched
Network
Switched
Network
1-12 GigE
1-12GigE
GigE
Switched
Network
Streamer Array
RF Devices
Management
Caching Nodes
RF
Set-top Box
HFC
The Cisco TV CDS solution has three major elements:
•
A Vault array consisting of one or more Vault servers. The Vault array is responsible for ingest and reliable storage of video on demand (VOD) content. The number of Vault servers in the Vault array is driven by the amount of content that the system offers and the degree of redundancy.
1-2
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 1 Product Overview
Overview
•
•
One or more Streamer arrays each consisting of one or more Streamer servers. The Streamer array is responsible for the personalization and streaming of content in response to user requests. The number of Streamer servers and Streamer arrays is determined by the number of streams deployed and by the topology that best suits your individual network and redundancy requirements.
A CDSM server. The Content Delivery System Manager is used to manage the Vault and Streamer servers, collect event logs, and provide reporting tools.
Note
In smaller systems, the Integrated Streamer-Vault (ISV) server can be used, where the Vault and
Streamer functionalities exist in one ISV server.
The Cisco TV VVI solution has four major elements:
•
One or more Vault Groups consisting of one or more Vaults. The Vaults are responsible for ingest and reliable storage of VOD content. The number of Vaults in the Vault Group, and the number of
Vault Groups is driven by the amount of content that the system offers and the degree of redundancy.
•
•
•
One or more Cache Groups, consisting of one or more Caching Nodes. The Caching Nodes provide more flexibility in designing a multi-tiered Virtual Video Infrastructure (VVI) by acting as a tier between the Vaults and the Streamers. The Caching Nodes facilitate content distribution and remove distribution traffic from the network backbone.
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.
The CDSM is used to manage the Vaults, Streamers, and Caching Nodes in the same array, collect event logs, and provide reporting tools. In a split-domain management system configuration, there is a Stream Manager that manages all the Streamers, and a Virtual Video Infrastructure Manager
(VVIM) that manages all the Vaults and Caching Nodes.
TV CDS Software
The Cisco TV CDS kernel software, known as the CServer, creates a logical network that pools, load balances, and coordinates the physical resources of the CDEs, so that the whole network operates and is managed as if it is a single resource.
The CServer facilitates the rapid movement of content between Vaults and Streamers while keeping required bandwidth to a minimum. To accomplish this, the Cisco TV CDS software uses a proprietary protocol, the Cache Control Protocol (CCP), across the gigabit Ethernet networks. All content is held reliably on the Vault servers and a large amount, but not all, of the content is also contained on the
Streamer servers. Cisco CCP, a multilayered caching architecture, along with associated software algorithms ensures that content segments are delivered only to the Streamers where there is demand for that content. The TV CDS software monitors the frequency of subscriber demand and places content appropriately in either the dynamic random access memory (DRAM) or disk cache on the serving
Streamer.
Content is delivered across the network in response to cache-fill calls from the Streamers in an opportunistic manner, depending on the availability of bandwidth; delivery can be faster than real-time delivery where bandwidth allows. The TV CDS software that ensures content on the Streamer servers is always the most popular content; that is, the content requested by the largest number of subscribers. User requests are generally served from the cache on the Streamer. Requests for content that are not already
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
1-3
Chapter 1 Product Overview
Overview
in the local cache on 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). The VVI is a deployment type of the TV CDS. In a CDS, servers cannot communicate with servers in other groups. In a VVI, servers in other groups can communicate with each other on an as needed basis. Streamers and Caching Nodes dynamically discover fill sources within other groups. Streamers send cache-fill calls to remote servers (Streamers in other Stream Groups and Caching
Nodes) for content that is not found locally (DRAM, disk cache, or peer Streamers). In a VVI, the
Caching Nodes can communicate with the Streamers by using CCP or HTTP. For more information on how a Caching Node interfaces with a CCP Streamer and an HTTP Streamer, see the
Workflow” section on page 2-9 .
Streamer Load Balancing
To ensure that new streams are distributed to the best Streamer in the group, each Stream Group runs a load distribution protocol among its members. The best Streamer is the Streamer that has the requested content in the highest-performing cache resource (DRAM or disk) or that has the most unused capacity.
In this way, new Streamers are brought into operation hitlessly—because after a new server is in service, fresh streams are automatically allocated to it. Furthermore, the cache capacity of the group is the sum of the caches of all Streamers in the group, which provides the most optimal system operation and the highest cache-hit rate.
CServer Functionality
The CServer is responsible for the following:
•
•
•
•
Storing content
Streaming content
Managing bandwidth usage for ingests
Managing bandwidth usage for streaming
•
•
Mirroring content among Vault servers
Making decisions on content retention on Streamer servers
Streamer Content Delivery Applications
On top of the CServer, and taking advantage of the services it offers, a variety of applications deliver individual personalized entertainment services. Cisco currently offers the following applications:
•
•
TV Streamer delivering VOD and network personal video recorder (nPVR) services
TV MediaX Suite for simplifying ingest and workflow scheduling tasks for asset-based and real-time content
In a full TV CDS network, the Vault, TV Streamer, and CDSM are required. The TV MediaX Suite is an optional CDA. In a smaller TV CDS network, the ISV can be used in place of the Vault and TV Streamer.
1-4
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 1 Product Overview
Content Delivery System Architecture
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.
•
Scheduler—Schedules real-time content or imports the schedule from an electronic program guide
(EPG).
Content Delivery System Architecture
Vaults and Streamers have different but important functions that are required for the TV CDS software to run efficiently. The Integrated Streamer-Vault (ISV) server combines the functionality of both the
Vault and Streamer for smaller networks. The Content Delivery System Manager provides a browser-based user interface for configuration, monitoring, maintenance, and reports of the TV Content
Delivery System solution. In a VVI, the Caching Nodes provide a pure caching layer for a multi-tiered
VVI.
Figure 1-2 shows the different elements of the TV Content Delivery System and the TV Virtual
Video Infrastructure with the addition of the Caching Nodes.
Figure 1-2 High-Level View of the Content Delivery System and Virtual Video Infrastructure
Mgmt
Mgmt
Database
SystemManager
Reports
Event Collection
Mgmt
Ingests
M g m t
Video
Accelerator
(CServer)
Database
Vault
Server
Cache Fills
Storage
M g m t
Video
Accelerator
(CServer)
Database
Caching
Node
Cache Fills
M g m t
Video
Accelerator
(CServer)
Database
Streamer
Server
Streams
Storage
Storage
describes the system elements shown in
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
1-5
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
CServer
Database
Management
Storage
Event Collection
Reports
Description
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.
The database stores information about the system, including current states of all ingests and streams, configuration settings, and system statistics.
Some database elements are global among all servers and some are local.
For example, statistics are stored on the local server and the Content
Delivery System Manager only. States about stream objects are replicated on all Streamer servers. The Content Delivery System Manager stores a superset of all database elements.
There are two types of management:
•
•
Content Delivery System Manager—Browser-based user interface
SNMP agent—Network Management System (NMS) interface
There are four levels of storage (or cache):
•
•
All content is stored on the Vault server, as well as mirrored to other
Vaults.
Requested content is stored on the Caching Nodes.
•
•
Recently requested content, or popular content is stored on the hard drive on the Streamer.
Currently requested content, or popular content, is stored in the random access memory (RAM) on the Streamer.
The Content Delivery System Manager collects logged events for reporting purposes as well as for third-party applications
The Content Delivery System Manager provides a reporting tool to aid performance trending and analysis of streams, popular content, bandwidth usage, and more.
Vault
The Vault ingests content delivered over a standard interface (for example, using FTP to receive content from a catcher), performs whatever processing is required (for example, generating trick-play files), and stores the processed content reliably on disk. A Vault Group consists of a scalable number of Vaults that divide the responsibility for ingest and storage among the members of the group. Vault servers can be colocated or distributed to multiple locations across an IP or Ethernet network. Each Vault can simultaneously ingest up to 160 channels of MPEG-2 transport stream (TS) content and store up to 6000 hours of MPEG-2 TS standard definition content with two mirrored copies of the content and one or two trick files.
1-6
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
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. Streamers can be colocated with Vaults or distributed to remote locations. The Stream Group is responsible for the personalization and streaming of content in response to user requests.
Caching Node
The Caching Node provides a 10-Gbps throughput to facilitate the distribution of content from the Vaults to the Streamers. The Caching Nodes allow for the ability to create a tier-based hierarchy in the CDS.
Caching Nodes are deployed in VVIs. Vaults can be strategically located for storing content on a national network, while the Streamers are located in a regional network. The Caching Node can be colocated with the Vaults or distributed closer to regional locations across an IP or Ethernet network. A Cache Group consists of several Caching Nodes that divide the responsibility for distribution among the members of the group.
The Caching Nodes use CCP to communicate with the Vaults and Streamers. Alternatively, the Caching
Nodes can use HTTP instead of CCP to communicate with Streamers.
Integrated Streamer-Vault
The Integrated Streamer-Vault (ISV) server offers the functionality of both a Vault and Streamer in one server.
The ISV server ingests content delivered over a standard interface, performs whatever processing is required, and stores the processed content reliably on disk. An ISV array consists of a scalable number of ISV servers that divide the responsibility for ingest, storage, and streaming among the members of the array.
Content Delivery System Manager and Virtual Video Infrastructure Manager
The Content Delivery System Manager (CDSM) and the Virtual Video Infrastructure Manager (VVIM) are each a browser-based user interface accessible by a web browser program and designed to manage a
TV CDS or a TV VVI network.
The CDSM provides centralized management functions for the TV CDS, including configuration, monitoring, troubleshooting, reporting, and maintenance.
The VVIM provides centralized management function for the TV VVI, including configuration, monitoring, troubleshooting, reporting, and maintenance. The VVIM in a centralized domain management configuration manages the Vaults, Caching Nodes, and Streamers, The VVIM in a split-domain management configuration manages the Vaults and Caching Nodes, while the Streamers are managed by the Stream Manager. For more information about split-domain management, see the
VVI Management” section on page 2-6 .
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
1-7
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. In the CDSM GUI, 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.
Table 1-3 ID Names in the CDSM GUI and CServer Files
CDSM GUI ID Name
Array ID on the Array Name page
Group ID on the Server-Level pages
Stream Group ID on the Server Setup page
CServer Files ID Name
groupid groupid arrayid
Cache Group ID on the Server Setup page
Vault Group ID on the Server Setup page arrayid arrayid
Stream Group ID on the Configuration Generator page arrayid
In a VVI with CCP Streamers, similar to a CDS, all Vaults, Streamers, and Caching Nodes are identified by an array ID, a group ID and a server ID. The group ID and server ID in a VVI with CCP Streamers must be unique among other groups and servers in the same system.
In a VVI with HTTP Streamers, the Vaults, Streamers, and Caching Nodes still use an array ID, a group
ID and a server ID for identification, but there is additional functionality that allows the Vaults and
Caching Nodes to communicate using CCP, while the Caching Nodes communicate with the Streamers using HTTP. It is not required that the group ID and server ID be unique, but it is recommended.
The CDSM and VVIM (as well as the Stream Manager) have three configuration and monitoring levels: system, array, and server. System-wide configuration affects all servers managed by that manager. The array-level configuration affects all the servers of the specified array or group, and the server-level configuration applies changes to a specific server.
The CDSM and VVIM offer a drill-down approach to show the status of any stream or ingest point, or the physical status of any piece of hardware.
The CDSM reporting helps operators manage all aspects of the TV CDS. Information on stream traffic, content statistics, and server data are gathered from all servers in the network and correlated automatically, showing at a glance the status of the network and reporting on statistics such as content popularity, stream usage, and bandwidth usage for each service group.
The VVIM monitoring and reporting helps operators manage all aspects of the TV VVI in either a centralized management capacity or a split-domain management capacity. In a split-domain capacity, the
VVIM monitors the ingests and the Stream Manager monitors the streams of the Streamers in its domain.
shows the system monitoring page of the CDSM.
1-8
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 1 Product Overview
Figure 1-3 Content Delivery System Manager User Interface
Content Delivery System Architecture
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. These levels of redundancy eliminate any customer impact from potential failures of Vault disks, Vault servers, Streamer disks,
Streamer servers, ISV servers, Ethernet connections, processors, and power supplies.
Each server constantly monitors the state of its peers. The TV CDS unique resource pooling and auto-failover techniques allow all servers in the network to actively contribute to satisfying storage and streaming demand at all times. If a server fails, the load is instantaneously redistributed among the surviving servers, ensuring continuity of service.
Vault Disk Redundancy
The Vault server protects content through full 1:N redundancy. If a disk fails, the data is available from a redundant server, spreading the load and optimizing the bandwidth. Additionally, the regeneration of the redundant content utilizes the bandwidth of the whole Vault array rather than just the disk bandwidth available inside a particular server, significantly reducing the rebuild time. The need to replace the failed drive is not time critical in the least, making quarterly replacement of any failed Vault drives feasible.
Mirroring
The primary method to protect the content against loss because of hardware failure is mirroring. Content is stored on a Vault and, based on the policy, it is mirrored to other locations in the Vault array. The number of mirrored copies is configurable. There are two types of mirroring:
•
Remote mirroring
•
Local mirroring
When remote mirroring is used, copies of the content are mirrored to drives on other Vaults, based on the number of Vault mirror copies configured.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01 1-9
Chapter 1 Product Overview
Content Delivery System Architecture
When local mirroring is used, copies of the content are mirrored across all the available drives on the same Vault, so that the content can be recovered from another drive if one of the drives fails.
Local mirroring is not turned on by default, and is generally only used when there is a single Vault in a system.
Vault Server Resiliency
The Cisco TV CDS can handle the loss of an entire Vault server without impacting the subscriber. The communication with the backoffice suite is performed by a Vault server that is designated as the Vault master. If the Vault master fails, one of the remaining slave Vault servers in the Vault array transparently takes over as the master. The remaining Vaults detect the loss of a Vault server, run a check of all stored content, and regenerate redundant content that was affected by the lost Vault server. This regeneration runs in the background, utilizing spare system bandwidth that is not consumed by subscriber load, resulting in the shortest possible regeneration window possible without compromising performance to the subscriber.
Vault Master
The Vault master, designated by a virtual IP address on its management interface, is used as the representative of the Vault array to the backoffice and handles the ingest of new content.
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.
Content is mirrored among as many as four Vault Groups (one Vault Group ingests the content and up to three Vault Groups mirror the content), which may be in different geographic regions. If the primary
Vault Group becomes unavailable, because of network, power, or other catastrophic problems, any
Streamer or Caching Node that was requesting content from that Vault Group would fail over to the other
Vault Group until the primary Vault Group came back online and could again respond to cache-fill requests for content.
With Vault redundancy, at least one copy of each content within a group is mirrored to a configured peer group. Vault Group mirroring runs as a low-priority process, so as not to impact the performance of the guaranteed streaming delivery.
Note
The maximum number of Vault Groups for this release is 20.
Streamer Disk Redundancy
The disks in the Streamer are not used for full content storage as in most VOD implementations. Rather, the Streamer disks are part of the TV CDS multilevel caching architecture. If a disk is lost on a Streamer, the only impact is a marginal loss of caching capability for the system. Any content that was cached on that Streamer disk is retrieved again from the Vault. The RAM on the Streamer has enough content cached for streaming to the subscriber, so that this refetch of content from the Vault occurs without impacting the subscribers. For example, for a Streamer array of five Streamers with sixteen hard drives each, a lost drive only reduces the total caching capability by less than 1.25 percent. The need to replace the failed drive is not time critical in the least, making quarterly replacement of any failed Streamer drives feasible.
1-10
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 1 Product Overview
Content Delivery System Architecture
Streamer Server Resiliency
The Cisco TV CDS architecture allows for failed Streamer servers as well. If any Streamer server fails, the communication to the backoffice is transparently handed off to another Streamer. With the TV CDS software, if a Streamer server fails the other Streamers recognize that failure and continue streaming to that subscriber.
Caching Node Disk Redundancy
The disks in the Caching Node are not used for full content storage like most VOD implementations.
Rather, the Caching Node disks are part of the TV CDS multilevel caching architecture. If a disk is lost on a Caching Node, the only impact is a marginal loss of caching capability for the system. Any content that was cached on that Caching Node disk is retrieved again from the Vault.
Caching Node Resiliency
The Cisco TV CDS architecture allows for failed Caching Nodes as well. If a Caching Node fails, any cache-fill transmissions that were in process at the time of the failure are re-requested by the Streamer, and any new requests are responded to by the remaining Cache Nodes in the Cache Group.
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 .arroyorc file on each CDS server, except the CDSM, which only has the other CDSM IP address.
The statsd process is configured with a virtual IP address that can move from one CDSM to the other. If the primary CDSM becomes unavailable, because of network, power, or other catastrophic problems, the secondary CDSM takes over the virtual IP address and the administrator can connect to the secondary
CDSM within 15 seconds.
Login information is not shared between CDSMs. If the administrator is logged in and a failover occurs, the administrator has to log in again to the other CDSM.
The CDS servers (Vault, Caching Node, Streamer, and ISV) participate in replication with both the primary and secondary CDSM in the same manner as occurred without redundancy, including synchronization of tables. However, the CDS servers can only retain up to one hour of reporting data, so if a CDSM is down for over an hour, when the CDSM recovers, it is only able to get the last hour of reporting data from each CDS server, which means the reporting data is not synchronized between the primary and secondary CDSMs. Reporting data is archived in comma-separated value (CSV) files every
24 hours and these CSV files are deleted when they are older than 30 days.
Ethernet Link Resiliency
All Ethernet links used within the Cisco TV CDS architecture incorporate link failure detection with automatic failover. This includes the interconnections between the Vault array and the Streamer array for cache-fill, and the Ethernet links that carry the subscriber streams to the transport networks.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
1-11
Chapter 1 Product Overview
Content Delivery System Architecture
Scalability
The Cisco TV CDS has separated streaming and storage, which enables a cable operator to add storage without affecting streaming counts to add streaming without affecting storage, and in VVIs, to add distribution nodes without directly affecting storage or streaming. This flexibility allows cable operators to grow according to the needs of customers and to scale the system on an as-needed basis. For example, if more storage is required, the cable operator adds a Vault server without taking the system offline, and in Layer 2 networks the new device is automatically discovered within the architecture and the new resources are automatically utilized by the system. If additional streaming is required, the content provider either purchases more streaming licenses within the current servers, or a Streamer server is added to the system without the need to take the system offline.
1-12
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
C H 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. The topics covered in this chapter include:
•
•
•
•
•
TV CDS Topologies and VVI Topologies, page 2-2
BMS Considerations for RTSP Environments, page 2-11
Network Connections, page 2-12
Overview
The TV CDS enables cable operators and multiple service operators (MSOs) to offer VOD and MediaX services to consumer customers over their existing hybrid fiber coaxial (HFC) network, with existing next-generation digital STBs. The TV CDS solution uses a gigabit Ethernet (GE) transport network from the headend to the distribution hub, where the HFC network terminates.
TV CDS grows seamlessly from a single server implementation to multiple servers. As growth continues, TV CDS allows operators to install distributed servers to address concentrations of subscribers while leaving content ingest and management centralized.
Stream Groups can be distributed close to the subscriber and linked back to the central Vault locations by way of the Cisco Cache Control Protocol (CCP). Cisco CCP automatically ensures that any new content that is required by a customer edge device is transferred within a maximum of a 250-millisecond delay to the appropriate edge location; as a result, all content appears local to each edge site, even though most content is stored at the central Vault location.
The TV CDS offers different configurations with regards to network topology, business management systems (BMSs), and streaming modes.
CDS with Vaults and Streamers
In a TV CDS with Vaults and Streamers, MPEG-2 transport stream (TS) video is stored on the Vaults with the associated trick-mode files. Content is transported from the Vaults to the Streamers as needed, by using CCP over gigabit Ethernet networks. Content is sent unicast from the Streamers and delivered to the quadrature amplitude modulation (QAM) devices over gigabit Ethernet or asynchronous serial interface (ASI), and then modulated onto the HFC plant to the subscriber set-top box (STB) for viewing.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01 2-1
Chapter 2 Network Design
TV CDS Topologies and VVI Topologies
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.
In a TV CDS with ISVs, MPEG-2 TS video is stored on the ISV servers with the associated trick-mode files. Content is sent unicast from the ISVs and delivered to the QAM devices over a gigabit Ethernet network, and then is modulated onto the HFC plant to the subscriber STB for viewing.
CDS with Caching Nodes
For larger networks, Cisco offers the CDS with Caching Nodes in the Virtual Video Infrastructure (VVI).
In a VVI, Caching Nodes are the intermediary fill source for Streamers, which removes a large portion of the distribution traffic from the Vaults.
In a TV VVI, MPEG-2 TS video is stored on the Vaults with the associated trick-mode files. Content is transported from the Vaults to the Caching Nodes as needed, by using CCP over gigabit Ethernet networks. Content is distributed from the Caching Nodes to the Streamers as needed, by using CCP over gigabit Ethernet networks, or by using HTTP over gigabit Ethernet networks. Content is sent unicast from the Streamers and delivered to the QAM devices over a gigabit Ethernet network, and then is modulated onto the HFC plant to the subscriber STB for viewing.
TV CDS Topologies and VVI Topologies
The TV CDS (using Vaults and Streamers, or ISVs) and the TV VVI (using Vaults, Caching Nodes, and
Streamers), supports centralized, decentralized, and hybrid gigabit Ethernet network designs. Because the use of Vaults and Streamers separates storage from streaming, streaming requirements can be satisfied on an as-needed basis and the streaming can be centralized or distributed among multiple locations. Caching Nodes separate the ingest and storage of content from the distribution of content, offering greater flexibility and network efficiency.
The TV CDS topology and TV VVI topology can change with the evolving needs of the system operator.
If the need to decentralize becomes evident, you can move the Streamers or Vaults to remote hubs without disrupting service. The VVI offers additional flexibility in designing your network. Vaults can be centrally located at a national network, and content may be classified by market (city, state, or a broader region) depending on the AMS or BMS used. Caching Nodes can be located centrally, or distributed closer to the regional networks where the Streamers are located. Using Caching Nodes in the network design takes the distribution traffic off the network backbone.
Caution
All Cisco servers are connected through a switch. Because all Vaults, CCP Streamers, and Caching
Nodes in the same array exchange heartbeat messages through the cache interfaces, it is important to ensure there is enough bandwidth among switches involved in delivering cache traffic, as well as to support the same aggregated amount of traffic on all cache interfaces.
Note
When using ISVs, with the Vault and Streamer functions contained in one server, the only topology possible is centralized.
2-2
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 2 Network Design
TV CDS Topologies and VVI Topologies
Centralized Topology
In a centralized topology, both Vault and Streamer 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. A centralized topology has advantages in reducing operational cost by placing equipment in one physical location.
Figure 2-1 illustrates the centralized
topology for Vaults and Streamers.
Figure 2-1 Centralized Topology with Vaults and Streamers
Headend or Remote Hub
Switch
Network
Switch
Network
GE QAMs
Streamers
Vaults
HFC
Figure 2-2 illustrates the centralized topology for ISVs.
Figure 2-2 Centralized Topology with ISVs
Headend or Remote Hub
Switch
Network
HFC
ISVs
GE QAMs
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
2-3
Chapter 2 Network Design
TV CDS Topologies and VVI Topologies
illustrates the centralized topology for a VVI.
Figure 2-3
Vaults
Centralized Topology with Caching Nodes
Headend or Remote Hub
GE Switch
HFC
Caching Nodes
GE Switch
Streamers
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 Vault servers are located at the headend and the Streamer servers are in the hub sites.
For a VVI, a decentralized topology provides a three-tiered approach by having the Vaults located in the headend, the Caching Nodes in intermediary sites, and the Streamers in the hub sites. The decentralized topology works well for distributing Streamer Groups close to subscribers. A decentralized topology has advantages in reducing the amount of long-haul fiber transport bandwidth needed—typically by a factor of ten or better.
Figure 2-4 illustrates the decentralized topology.
Figure 2-4 Decentralized Topology
Streamers
Remote Hub 1
Switch
Network
GE QAMs
HFC
Vaults
Storage Content
Headend
Switch
Network
Streamers
Remote Hub 2
Switch
Network
GE QAMs
HFC
2-4
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 2 Network Design
Figure 2-5 illustrates the decentralized topology with Caching Nodes.
TV CDS Topologies and VVI Topologies
Figure 2-5 Decentralized Topology with Caching Nodes
Tier Two
Caching Nodes
Remote Hub 1
Streamers
GE QAMs
GE Switch
GE Switch
Headend - Tier One
Vaults
GE Switch
HFC
Tier Two
Caching Nodes
Remote Hub 2
Streamers
GE QAMs
GE Switch
Storage Content
GE Switch
HFC
Hybrid Topology
In a hybrid topology, the Vault servers and backup Streamer servers are located at the headend, with the active Streamers at a remote hub site. If the remote hub site goes down, the Streamers at the headend take over. A hybrid topology blends the advantages of centralized and decentralized topologies that is based on needs of the system implemented.
illustrates the hybrid topology.
Figure 2-6 Hybrid Topology
Vaults
Headend
Switch
Network
Storage
Content
Streamers
Remote Hub
Switch
Network
GE QAMs
Switch
Network
HFC
Streamers
GE QAMs
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
2-5
Chapter 2 Network Design
TV CDS Topologies and VVI Topologies
illustrates the hybrid topology with Caching Nodes.
Figure 2-7 Hybrid Topology with Caching Nodes
Remote Hub
Caching Nodes
GE Switch
GE Switch
GE QAMs
Headend
Vaults
GE Switch
GE Switch
Streamers
GE QAMs
HFC
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. In a VVI, Streamers in other groups can communicate with each other on an as-needed basis.
All Vaults, Streamers, and Caching Nodes are identified by an array ID, a group ID, and a server ID. In the CDSM GUI, 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, Cache Group, and Stream Group), and the server
ID is a unique number that identifies the server.
lists the CDSM GUI ID names and maps them to the CServer names in the setupfile and .arroyorc files.
Table 2-1 ID Names in the CDSM GUI and CServer Files
CDSM GUI ID Name
Array ID on the Array Name page
Group ID on the Server-Level pages
Stream Group ID on the Server Setup page
CServer Files ID Name
groupid groupid arrayid
Cache Group ID on the Server Setup page
Vault Group ID on the Server Setup page arrayid arrayid
Stream Group ID on the Configuration Generator page arrayid
2-6
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 2 Network Design
CDS Workflow
Note
VVI is available in an RTSP environment, and in an ISA environment that uses the Shared Content Store feature and CCP Streamers.
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. If port 80 is not open for communication, the managers cannot communicate with each other and configuration settings need to be uploaded to the Stream
Managers from information downloaded from the VVIM.
In a split-domain VVI that uses HTTP for communication between the Caching Nodes and Streamers, and in a split-domain VVI that uses CCP in an RTSP environment, the databases for each domain are separate. The information stored in each database is not shared with the servers in the other domains.
In an ISA environment with a split-domain VVI that uses CCP for communication between the Caching
Nodes and Streamers, the database is replicated among all servers in the Vault/Cache domain and the
Stream domains. Because the VVI allows intercommunication among different Cache Groups and
Stream Groups when CCP Streamers are used, the server ID and group ID must be unique across the system.
Note
Split-domain management is supported in an RTSP environment and an ISA environment with the
Shared Content Store feature and CCP Streamers.
CDS Workflow
Content is ingested and stored in the Vault array. The Vault array consists of two or more Vault Groups, which in turn consists of two or more Vaults that are either colocated or distributed to multiple locations across an Ethernet network. Content ingest is initiated by the backoffice based on a subscriber request, and based on schedule or barker channel content. Manual ingest, which is operator initiated, is also offered as an optional feature.
Note
Release 2.2.1 and later releases support the ability to differentiate between a DVD asset and a video asset to support ingest, trick-play creation, and streaming of content files as large as 30 GB. The content files could span multiple days.
As the content is ingested into the Vault, any necessary trick-mode files are created. The content and trick-mode files are then mirrored within the same Vault or across the Vault array. The replication of content allows for data recovery should a Vault undergo a failure.
Content is delivered from the Vault array to the Streamer array in response to cache-fill calls from the
Streamers to fulfill subscriber requests for VOD content. Content is also distributed across the network in response to scheduled or barker stream content fulfillment.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01 2-7
CDS Workflow
Chapter 2 Network Design
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
Node Workflow” section on page 2-9
.
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. However, because of backoffice restrictions, the externalized IP address is constrained to migrate among servers on the same subnetwork. This means the content store server in an Interactive Services Architecture (ISA) environment can migrate only among
Vaults that are on the same subnet, and the Setup and Control servers can migrate only among Streamers on the same subnet.
Streamer Workflow
A Stream Group is a configurable group of Streamers that are designated to serve specified QAM devices, and subsequently, specific service groups. From a session setup and control perspective, there are three logical types of servers in a Stream Group:
•
•
•
Setup server
Control server
Play server
The Setup and Control servers have both a primary and a backup server. The primary server services all messages, while the backup server simply maintains states. If a primary server is unreachable, the backup server takes over control and creates another backup server. Thus, there is always a primary and backup pair of servers for setup and control. The Play server does not have a backup server. However, the Control server selects a new Play server in the event of a failure of the existing Play server.
Note
The ability to have both a primary and backup server depends on the number of Streamers in the Stream
Group.
The Setup and Control server IP addresses are configurable. For an ISA environment, the Setup IP address is the same as the Stream Master IP address. For RTSP, the Setup server and Control server must be the same server. For both ISA and RTSP environments, the Stream Service selects a Streamer in the
Stream Group to be the Setup server, and another Streamer (sometimes the same Streamer) to be the
Control server.
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.
The Setup server returns the IP address of the Control server, and the STB issues subsequent control messages to this IP address.
2-8
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 2 Network Design
CDS Workflow
Control Server
The Control server assigns requests to specific Streamers and dynamically migrates streams between
Streamers based upon changes in stream states (for example, content splice boundaries, maintenance trickle down, or server failures). One server in the Stream Group is assigned as the primary Control server. The Control server runs the Lightweight Stream Control Protocol (LSCP) proxy in an ISA environment and the Real-Time Streaming Protocol (RTSP) proxy in an RTSP environment.
For each and every setup message received from the backoffice, a CCP message is generated and sent to the Control server. In the initial setup request, the Control server receives the setup parameters but does not choose a Play server. After a control message is received from the STB, the Control server gets performance information (for example, server load) from the potential Play servers within the Stream
Group and sends a CCP message to the best candidate. Subsequent control messages, whether from the
STB or from the Setup server, are forwarded to the chosen Play server.
Play Server
The Play server is the Streamer that is assigned to play the stream. This Streamer acquires the content, whether in RAM, a local disk, or a Vault, and ensures guaranteed service delivery of the stream. Every
Streamer in a Stream Group is a possible candidate to be the Play server.
Caching Node Workflow
A Cache Group is a configurable group of Caching Nodes that serve content to specified Stream Groups.
When a content request is received by a Streamer, the Streamer first checks to see if the content is stored locally, which includes DRAM, disk cache, and Streamers in the same Stream Group. Content on the
Streamers is always the most popular content, so user requests are generally served from local storage.
Streamers send cache-fill calls to remote servers for content that is not found locally. The remote servers can be Streamers in other Stream Groups, Caching Nodes in Cache Groups, or Vaults in Vault Groups
(Vault Redundancy must be enabled). The cache-fill source selected, whether another Streamer, Caching
Node, or Vault, is based on the network capacity and fill-source capacity (disk and memory), as well as on the preference configured for that group of servers. Caching Nodes could respond to the request with a message stating the content is not currently cached, but there are other fill sources the Caching Nodes can contact (Caching Nodes in other Cache groups, and Vaults).
The Caching Nodes use CCP to communicate with the Vaults, and use either CCP or HTTP to communicate with Streamers.
Note
ISA environments only support CCP, while RTSP environments only support HTTP for VVI.
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).
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
2-9
Chapter 2 Network Design
CDS Workflow
HTTP Streamers request content by HTTP GET requests to the proxy service (the server with the locate service). The proxy server checks its own storage and peer fill sources (servers in the same group) for the content using extended-CCP. If the content is found, the best source is chosen based on capacity and a redirect response is sent to the chosen server. If the content is not found, a cache-fill request is sent to the remote servers.
After the best server is chosen to send the content to the HTTP Streamer, a single cache-fill port on that server is chosen for the HTTP transfer of the content. This is different from CCP transfers, which could potentially use all cache-fill ports to deliver the content.
HTTP Locate Port
With respect to resiliency, the Locate Port service is similar to the Setup and Control servers,. The primary server of the Locate Port service has the locate port IP address bound to an interface. The backup server becomes the primary if the primary fails.
Peer Caching Nodes advertise among themselves about the ability to host the HTTP Locate Port Service, this includes primary, backup, available, and not usable states. Available means the Caching Node can be either a primary or backup if needed. Not usable means that the server cannot host the service; for the
HTTP Locate Port this typically means that there are no usable network ports for the service.
A dedicated network port on the Caching Node is used solely for the HTTP Locate Port service. The primary server determines service availability based on the link status of the dedicated network port.
Failover of the service occurs if the network port loses link status. A reestablished link results in the server becoming available.
CCP Streamers
The CCP Streamers use CCP to communicate with the Caching Nodes. They do not use the proxy address that was assigned to the Locate Port for HTTP Streamers. CCP Streamers load-balance locate requests across fill sources.
The Streamer or Caching Node sends a locate-and-request message from the proxy server. The Proxy server sends a message to the best source to fill the request.
Streamers or Caching Nodes needing content first query peer sources (servers within the same group).
Streamers also query local Streamers, if the content is not found, then a request to the remote sources is sent. Remote sources are queried based on a preference list. Sources are grouped and preferences are assigned for each group.
Vault Workflow
The Vaults ingest content using three different methods:
•
FTP pull
•
•
FTP push
Live capture of MPEG-2 transport streams over UDP
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.
2-10
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 2 Network Design
BMS Considerations for RTSP Environments
BMS Considerations for RTSP Environments
The TV CDS integrates with Interactive Services Architecture (ISA) used in business management systems (BMSs) such as the Tandberg OpenStream and the RTSP used in BMSs such as ARRIS nABLE, as well as in environments that are a combination of both ISA and RTSP. The BMS determines the roles and responsibilities of the TV CDS.
nABLE Integration
The nABLE BMS uses a combination of eXtensible Markup Language (XML) over Hypertext Transfer
Protocol (HTTP) and RTSP for communication between nABLE Headquarters (HQ) and Real-time (RT) components and the CDS. The HQ communicates file-related requests by using XML/HTTP to the Vault server, as well as server status information requests to both the Streamer and Vault servers. The RT communicates with the Streamer server by way of RTSP to establish session setups for multiple, interchangeable VOD flows (RTSP or DSM-CC).
Figure 2-8
Note
Currently, configuring the CDS for integration with the nABLE BMS is performed by Cisco field engineers. For more information on integration of the CDS with the nABLE BMS, contact the Cisco technical support department.
Figure 2-8 illustrates how the CDS integrates with the nABLE BMS.
TV CDS Integration into the nABLE BMS
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
2-11
Chapter 2 Network Design
Network Connections
Network Connections
The network connections for a TV CDS with Vaults and Streamers, a TV CDS with ISVs, and a TV VVI
with Caching Nodes all have different network connections. Table 2-2 lists the different required
interfaces for each CDS server. The interfaces are described in the following sections.
Figure 2-9 illustrates a TV CDS with Vaults and Streamers. Figure 2-10
illustrates a TV CDS with ISVs.
illustrates a TV VVI with Caching Nodes.
Table 2-2 CDS Interfaces
Interface
Management
Ingest
Cache
Stream
Vault
1
1
1 to 8
—
Streamer
1
—
1 to 13
1 to 13
ISV
1
1
1 to 4
1
1 to 4
1.
The cache interfaces on an ISV are used for content mirroring among ISVs.
Caching Node
1
—
1 to 12
—
Note
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-55
.
shows the different logical networks of a CDS consisting of Vaults and Streamers. The ingest network receives content from the content source by way of an FTP staging server or FTP catcher and the content is ingested by the Vaults. The management network consists of communication between the
CDSM and the BMS, as well as communication with the Vaults, Streamers QAM devices, and STBs.
The cache network consists of Vaults and Streamers.
2-12
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 2 Network Design
Figure 2-9 Vault and Streamer Network Connections
Network Connections
Figure 2-10 shows the different logical networks of a CDS consisting of ISVs. The ingest network
receives content from the content source by way of an FTP staging server or FTP catcher and the content is ingested by the ISVs. The management network consists of communication between the CDSM and
BMS, as well as communication with the ISVs, QAM devices, and STBs.
Figure 2-10 ISV Network Connections
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
2-13
Chapter 2 Network Design
Network Connections
Figure 2-11
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.
VVI Network Connections
Cable STB
Content Commands to and from Vaults
Session Command to and from Streamer
BMS
Content
Source
Catcher
FTP
FTP
Staging
Server
Mgmt
Network
Ingest
Network mgmt mgmt
Ingest mgmt
Vault
Vault
Caching
Node
Caching
Node mgmt
Cache
Network
BMS information
BMS information
Stream
Group
S w i t c h
C
F
E
QAM
Device
Cable STB
HFC
Network mgmt
BMS information mgmt
Vault mgmt ingest
Vault
Caching
Node
Caching
Node
Cache
Network
Stream
Group
S w t c i h
C
F
E
QAM
Device
HFC
Network
Layer 2/3:
QAM:
QPSK:
Ingest Interface
The ingest interface takes in FTP traffic from the content provider at a maximum rate of one gigabit per second. After the Vault server receives URL information about the content from the BMS by using the management interface, the ingest interface either (1) receives FTP traffic by acting as an FTP client, or
(2) receives live data upon receiving a request to act as the FTP server.
When using Layer 2 packet forwarding, to segregate all ingest traffic through the switching fabric, we recommend the use of a port-based VLAN.
2-14
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
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. Information shared among servers in the same array includes the following:
•
Host service information
•
•
Domain Name System (DNS) service information
QAM gateway information
•
All ISA information
Management traffic is low volume; however, when using Layer 2 packet forwarding, we recommend using a port-based VLAN to ensure delivery of critical management communications.
Cache Interfaces
The CCP uses the cache interfaces on the Vaults, Caching Nodes, and Streamers to send the following data to the servers in the same array:
•
Content sent to the Streamers
•
•
Content mirrored among the Vaults
Messages containing information used for performance optimization exchanged among all the CDS servers
Note
All Cisco CDS servers are connected through a switch fabric. Because all Vaults, Caching Nodes, and
Streamers in the same array exchange heartbeat messages through the cache interfaces, it is important to ensure there is enough bandwidth among switches involved in delivering cache traffic and to support the same aggregated amount of traffic on all cache interfaces.
When using Layer 2 packet forwarding for cache traffic, we recommend the use of a port-based VLAN.
Cache/Stream Interfaces
The cache/stream interfaces on the Streamer server can be used for both cache and streaming traffic. The number of interfaces designated for each traffic type is configurable. If an interface is configured for both cache and streaming traffic, priority is given to the higher-bandwidth stream traffic provided cache traffic is able to transmit on other interfaces.
When using Layer 2 packet forwarding for cache and stream traffic, we recommend the use of a port-based VLAN.
Streaming Interface
The streaming interface delivers streaming traffic consisting of MPEG-2 transport streams to STBs by way of QAM devices.
If an interface is configured for both stream and cache traffic, and the jumbo frames feature is not enabled for stream traffic while jumbo frames is enabled for cache traffic, stream traffic uses 1500-byte packets while cache traffic uses jumbo frames.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
2-15
Network Connections
Chapter 2 Network Design
2-16
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
C H A P T E R
3
Getting Started
This chapter provides information on configuring the TV CDS servers. The topics covered in this chapter include:
•
Initially Configuring the Devices, page 3-1
•
•
•
•
Logging In to the TV CDSM, page 3-1
Initializing the CDS and Activating the Optional Features, page 3-3
Configuration Workflows, page 3-5
This chapter assumes the CDS servers are already installed and takes you through the next steps toward configuring and monitoring the CDS.
Initially Configuring the Devices
You must initially configure the Content Delivery Engines (CDEs) before they can participate in the CDS network. The CDE that runs the TV Content Delivery System Manager (CDSM) must be initialized first so that the CDEs running the Streamers and Vaults, and optionally Caching Nodes, or the ISVs can communicate with it. For more information about initially configuring the CDEs, see the Cisco Content
Delivery Engine 205/220/250/420 Hardware Installation Guide, the Cisco Content Delivery Engine 110
Hardware Installation Guide, or the Cisco TV CDS 2.3 Installation, Upgrade, and Maintenance Guide.
Initial configuration of your CDEs includes basic network configuration settings to provide connectivity to the CDSM. After the CDEs are configured with these settings you can use the CDSM to configure and manage all the servers in the CDS.
After you have initially configured your CDEs, you must initially set up your CDS and activate any
for more information.
Logging In to the TV CDSM
To log in to the TV CDSM, do the following:
Step 1
Using your web browser, enter the IP address or hostname of your CDSM.
For example, if the IP address of your CDSM is 192.168.0.236, you can access it by entering http://192.168.0.236 in the address or location text box of your browser program.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01 3-1
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 System Login page is displayed, as shown in
.
Figure 3-1 System Login Page
Note
The CDSM supports Microsoft Internet Explorer version 6 or higher.
Step 2
Enter your user name and password and click Log In.
The built-in user name is admin and the initial password is admin.
Note
We strongly recommend that you change the built-in user password as soon as possible. See the
“Editing User Settings” section on page 7-3 for more information.
Tip
To navigate within the CDSM, click one of the navigation bar options (for example, Maintain), then one of the tab options (for example, Users), and then one of the left-panel menu options (for example, Add
Users). Navigational directions in procedures are written as in the following example:
Choose Maintain > Users > Add Users.
3-2
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
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 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.
If the Media Scheduler or Ingest Manager are part of your deployment, you need to activate these features.
To initialize your CDS or activate the Media Scheduler and Ingest Manager, do the following:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Log in to the CDSM as admin, or use another user account that has master access.
Add a user with engineering access.
a.
b.
Choose Maintain > User > Add Users. The Add Users page is displayed.
In the New User and Password fields, enter the user name and password for this account.
c.
d.
From the Access drop-down list, choose Engineering.
Click Add User.
Log out of the CDSM, and log in as the user with the engineering access level that you specified in
Step 2 . The CDSM Setup page is displayed.
Choose the options for your deployment and click Submit. For more information about the fields on this page, see the
“CDSM or VVIM Setup” section on page D-3 .
Scroll down to the Media Scheduler section, and click the ON radio button next to the Media Scheduler field.
In the Activation Key field, enter the software access key from your Right to Use Notification for the
Content Delivery Application Media Scheduler (CDAMS) product.
In the Importer/Transformer Type field, choose either OCN or SA Tribune. The
Importer/Transformer Type specifies the expected EPG format, the fields for the Input Channels page, and the expected ADI metadata.
Scroll down to the Ingest Manager section, and click the ON radio button next to the Ingest Manager field.
In the Activation Key field, enter the software access key from your Right to Use Notification for the
Content Delivery Application Ingest Manager (CDAIM) product.
Click Submit.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
3-3
Navigating the CDSM
Step 11
Log out of the CDSM.
Navigating the CDSM
The CDSM pages consist of the elements illustrated in
Figure 3-3
1
CDSM User Interface
2
3 4
5
Chapter 3 Getting Started
6
1
Left panel menu
2
Tabs
3
Tab options
4
Page title
5
Main panel
6
Tools (Home, Help, and, Logout)
The tabs are accessible from any page in the CDSM.
The tab options are used to select the applicable level. In the Configure and Monitor pages, the tab option selected determines whether the configuration or monitoring applies to the system as a whole, to the array level, or to a specific server.
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.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
3-4 OL-22792-01
Chapter 3 Getting Started
Configuration Workflows
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. The content of this page is different depending on the page of the CDSM you are viewing when you click
Help. After inside the help system you can move around to view different topics by using a variety of navigation tools:
–
–
Back/forward page buttons
Links within the page contents
•
–
–
Table of Contents, accessed through the navigation panel at the left of the page.
Contents icon shows and hides the Table of Contents.
–
Print icon prints the page you are viewing.
From the Help window, you can display the full Cisco TV CDS 2.3 RTSP Software Configuration
Guide by clicking the View PDF button.
Configuration Workflows
After you have completed the initial installation and configuration of the CDEs for the CDS and you have verified connectivity to the CDSM, you are ready to configure the CDS for content delivery. The configuration workflow consists of one ore more of the following:
•
•
•
TV MediaX Configuration Workflow
CDS Workflow
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
Task
Change admin password
Interface setup
Server setup
Route table
CDS Configuration Workflow
Description
Change the administrator password for the
CDSM.
Configure the different interfaces on the CDS servers.
Configure the IP addresses and ports for the interfaces, as well as other settings such as quality of service (QoS).
Where to Find More Information
“Editing User Settings,” page 7-3
“Configuring the Interfaces,” page 4-55
“Configuring the Servers,” page 4-58
Route Table identifies destination subnetworks for cache, stream, and stream control interfaces. Route Table is optional.
“Configuring the Route Table,” page 4-66
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
3-5
Chapter 3 Getting Started
Configuration Workflows
Table 3-1 CDS Configuration Workflow (continued)
Task
Stream Groups setup
Control and setup
IPs
QAM gateways
Headend setup
Ingest tuning
1
Description
A Stream Group consists of one or more
Streamers. Stream Groups relate to QAM gateways or destination subnetwork by the
Stream Group preference.
Where to Find More Information
“Configuring Stream Groups,” page 4-29
Configure the Control server and Setup server
IP address for the Stream Groups.
Configure the QAM Gateways for the CDS.
“Configuring QAM Gateways,” page 4-4
Associate service groups with Stream Groups.
Configure the trick-mode speeds for ingested content.
“Configuring Ingest Tuning” section on page 4-17
1.
If the Stream Destination feature is enabled, the QAM Gateway page and Headend Setup page are replaced with the Stream
Destination page. For more information, see the
“Configuring Stream Destinations” section on page 4-8 .
The other configuration settings, DNS settings, and so on, can be configured in any order.
VVI Workflow
The Virtual Video Infrastructure can be centrally managed or can use split-domain management.
Central Management 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.
Table 3-2 VVI Configuration Workflow
Task
Change administrator password
Interface setup
Description
Change the administrator password for the
CDSM.
Where to Find More Information
“Editing User Settings,” page 7-3
Server setup
Route table
Stream Groups setup
Configure the different interfaces on the CDS servers.
Configure the IP addresses and ports for the interfaces, as well as other settings such as quality of service (QoS).
“Configuring the Interfaces,” page 4-55
“Configuring the Servers,” page 4-58
Route Table identifies destination subnetworks for cache, stream, and stream control interfaces. Route Table is optional.
“Configuring the Route Table,” page 4-66
A Stream Group consists of one or more
Streamers. Stream Groups relate to QAM gateways or destination subnetwork by the
Stream Group preference.
“Configuring Stream Groups,” page 4-29
Cisco TV CDS 2.3 RTSP Software Configuration Guide
3-6 OL-22792-01
Chapter 3 Getting Started
Configuration Workflows
Table 3-2 VVI Configuration Workflow (continued)
Task
Control and Setup
IP addresses
Cache Groups setup
Stream to cache map
QAM gateways
Headend setup
Ingest tuning
1
Description
Configure the Control server and Setup server
IP address for the Stream Groups.
A Cache Group consists of one or more
Caching Nodes.
Cache Groups are mapped to Stream Groups and given a preference.
Where to Find More Information
“Configuring Cache Groups,” page 4-36
Cache-Fill Sources,” page 4-39
Configure the QAM Gateways for the CDS.
“Configuring QAM Gateways,” page 4-4
Associate service groups with Stream Groups.
Configure the trick-mode speeds for ingested content.
“Configuring Ingest Tuning” section on page 4-17
1.
If the Stream Destination feature is enabled, the QAM Gateway page and Headend Setup page are replaced with the Stream
Destination page. For more information, see the
“Configuring Stream Destinations” section on page 4-8
.
The other configuration settings, DNS settings, and so on, can be configured in any order.
Split-Domain Management Workflow
lists the basic tasks, in the recommended order, for configuring the VVI with split-domain management (VVIM and Stream Manger) for content delivery with references to the associated sections in each chapter. For more information, see the
and the
Table 3-3 VVI Split-Domain Configuration Workflow
Task
Change administrator password
Interface setup
Manager
VVIM and Stream
Manager
Description
Change the administrator password for the
CDSM.
Where to Find More Information
“Editing User Settings,” page 7-3
Server setup
Route table
Stream Groups setup
Control and setup
IPs
VVIM and Stream
Manager
VVIM and Stream
Manager
VVIM and Stream
Manager
Stream Manager
Stream Manager
Configure the different interfaces on the CDS servers.
Configure the IP addresses and ports for the interfaces, as well as other settings such as quality of service (QoS).
“Configuring the Interfaces,” page 4-55
“Configuring the Servers,” page 4-58
Route Table identifies destination subnetworks for cache, stream, and stream control interfaces. Route Table is optional.
“Configuring the Route Table,” page 4-66
“Configuring Stream Groups,” page 4-29
A Stream Group consists of one or more
Streamers. Stream Groups relate to QAM gateways or destination subnetwork by the
Stream Group preference.
Configure the Control server and Setup server
IP address for the Stream Groups.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
3-7
Chapter 3 Getting Started
Configuration Workflows
Table 3-3 VVI Split-Domain Configuration Workflow (continued)
Task
Cache Groups setup
Cache Group locator
Stream to cache map
QAM gateways
1
Headend setup
Ingest tuning
Manager
VVIM
Stream Manager
Stream Manager
Stream Manager
Stream Manager
VVIM
Description
A Cache Group consists of one or more
Caching Nodes.
Locate Cache Groups in VVIM domain.
Where to Find More Information
“Configuring Cache Groups,” page 4-36
Cache Groups are mapped to Stream Groups and given a preference.
“Locating Cache Groups,” page 4-31
Cache-Fill Sources,” page 4-39
Configure the QAM Gateways for the CDS.
“Configuring QAM Gateways,” page 4-4
Associate service groups with Stream Groups.
Configure the trick-mode speeds for ingested content.
“Configuring Ingest Tuning” section on page 4-17
1.
If the Stream Destination feature is enabled, the QAM Gateway page and Headend Setup page are replaced with the Stream Destination page. For more information, see the
“Configuring Stream Destinations” section on page 4-8
.
The other configuration settings, DNS settings, and so on, can be configured in any order.
TV MediaX Configuration Workflow
Table 3-4 lists the basic tasks for configuring the TV MediaX Suite CDA with references to the
associated sections in each chapter.
Table 3-4 TV MediaX Configuration Workflow
Task
Specify the data feed import type used to populate the Media
Scheduler, and the transformer type used to process the ADI metadata.
Map each channel to a multicast group IP address and port, and specify the settings for every program in the channel.
Upload an EPG file. During the upload process, the EPG file is parsed into database records that in turn populates the Media
Scheduler.
Schedule the ingest of content.
The Media Scheduler does the following:
Where to Find More Information
“Configuring Input Channels” section on page 4-24
“Configuring Input Channels” section on page 4-24
“Uploading an EPG File” section on page 7-10
Scheduler” section on page 4-47
1.
2.
3.
Values from the EPG file are combined with the values from the Input Channels page, and the ADI metadata XML file is created.
The database records are marked according to the Media
Scheduler settings (scheduled, unscheduled, marked for scheduling, and so on).
The ADI metadata is published to the backoffice.
3-8
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
C H A P T E R
4
Configuring the CDS
This chapter provides information on configuring the CDS servers. The topics covered in this chapter include:
•
System Level Configuration, page 4-1
•
•
Array Level Configuration, page 4-27
Server Level Configuration, page 4-55
Note
If Virtual Video Infrastructure (VVI) with split-domain management is enabled, the CDSM pages associated with the Vaults and Caching Nodes display only on the VVI Manager (VVIM), and the CDSM pages associated with the Streamers display only on the Stream Manager. For more information, see the
“Virtual Video Infrastructure” section on page D-6 .
System Level Configuration
The System Level tab has the following configuration options:
•
•
•
•
•
•
•
•
•
•
•
•
•
Configuring Stream Destinations
Configuring the Bandwidth Manager
Configuring the Ingest Manager
Configuring the Authentication Manager
Configuring the Redirect Server
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-1 OL-22792-01
Chapter 4 Configuring the CDS
System Level Configuration
•
•
•
•
Configuring the Media Importer
Configuring Source Output Ports
Note
The System Level configuration settings are distributed to all arrays and servers in the CDS.
Configuring DNS Services
The System DNS page is used to configure up to 16 domain suffixes and 16 DNS servers.
To view the current DNS System Level settings choose, Configure > System Level > System DNS.
Note
If you are upgrading the TV CDS software to Release 2.3 from Release 2.0 or an earlier release, the system prompts you to Submit any settings that have previous domain suffixes to populate the new DNS database structure.
To configure the DNS service settings, do the following:
Step 1
Step 2
Choose Configure > System Level > System DNS. The System DNS page is displayed.
Enter the DNS system level settings as appropriate. See
for descriptions of the fields.
Table 4-1 DNS Service Fields
Field Description
New Domain Suffix Specify, if applicable, the internal domain that is used to fully qualify an unqualified hostname. For example, if you are using OpenStream as the BMS, specify a subdomain consistent with what OpenStream is using, for example, bms.n2bb.com. Accordingly, unqualified hostnames used in CORBA transactions, such as contentstore, resolve correctly to contentstore.bms.n2bb.com.
New DNS Server IP address of the DNS server.
Step 3
Click Submit.
To clear the fields and start over, click Reset.
To delete the DNS settings, check the Delete check box and click Delete Entry.
4-2
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
System Level Configuration
Configuring NTP Services
The System NTP Server page is used to configure up to 16 NTP servers. The clocks on all CDS servers
(Vault, Streamer, and Caching Node) and the CDSM and VVIM in a CDS must be synchronized in order to retrieve the statistics on to the CDSM and VVIM.
To view the current NTP System Level settings, choose Configure > System Level > System NTP
Server.
To configure the NTP service settings, do the following:
Step 1
Step 2
Step 3
Choose Configure > System Level > System NTP Server. The System NTP Server page is displayed.
In the New NTP Server field, enter the IP address of the NTP server.
Click Submit.
To clear the fields and start over, click Reset.
To delete the NTP settings, check the Delete check box and click Delete Entry.
For information on setting the time zone on a CDS server or configuring NTP on a CDSM or VVIM, see
“Other NTP Configurations” section on page 4-73
.
Configuring the Hosts Service
The Host Service page offers the option to enter a hostname and associated IP address as an alternative or backup to the DNS service. The system searches the host service table before searching the DNS services. The host service settings are considered an alternative or backup to the DNS service.
To view the current host service settings, Choose Configure > Host Service. The hostnames currently configured are listed at the bottom of the page.
To configure the host service settings, do the following:
Step 1
Step 2
Choose Configure > Host Service. The Host Service page is displayed.
Enter the host service settings as appropriate. See
for descriptions of the fields.
Table 4-2 Host Service Fields
Field
Hostname
Host IP Address
Description
Hostname of no more than 64 characters. Assigning hostnames is optional. The hostname does not have to be a fully-qualified domain name.
IP address associated with the hostname.
Step 3
Step 4
Click Submit. The new entry is added to the host table located at the bottom of the page.
To clear the fields and start over, click Reset.
To add more hostnames to the host table, repeat
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-3
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-5
.
Note
Currently the CDSM allows only for the creation of one Vault array.
To view the current Array Name listings, Choose Configure > Array Name. The array names currently configured are listed.
To configure an array name setting, do the following:
Step 1
Step 2
Step 3
Choose Configure > Array Name. The Array Name page is displayed.
Enter the array name used to identify the group of servers.
To reset the field, click Reset.
Click Submit.
Configuring QAM Gateways
The QAM Gateway page is used to identify the QAM gateway devices and the association between the
Streamers and QAM device. A QAM gateway is typically a Layer 3 device.
Note
The QAM Gateway page is not available if the Stream Destination is set to IPTV. For more information, see the
“Stream Destination” section on page D-4 .
A QAM gateway is a device that sits between a Streamer and a QAM modulator. Depending on the design of your network, a QAM gateway is a Layer 3 routing device, gigabit quadrature amplitude modulation (GQAM), Narrowband Services Gateway (NSG), Path1, or a similar device.
Single-site steering is supported for an RTSP environment. Single-site steering uses only one Stream
Group to serve streams to a QAM device.
Note
Single-site steering assumes all Streamers in a Stream Group are located at the same geographical location.
With single-site steering, you are given the option to set a Stream Group to High or None. Only one
Stream Group can be set to High, all others are set to None. In a CDS network with single-site steering, if one Streamer in the Stream Group that is serving streams to a QAM device fails, another Streamer in the same group takes over.
4-4
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
ARP
System Level Configuration
The Address Resolution Protocol (ARP) is the method for finding a host MAC address when only its IP address is known. The QAM Gateway page allows you to specify the MAC address of an IP gateway.
There are three reasons you may want to do this:
1.
To statically configure the MAC address of an IP gateway.
2.
3.
ARP is disabled on the QAM gateway.
To statically configure all devices on the network to have all packets go to a specific IP gateway.
For single-site steering, the QAM Gateway page allows you to specify the MAC address of the IP gateway when you enter the IP address of the QAM gateway. All streams from the Stream Group with a high preference are routed to the IP gateway specified.
Note
We recommend you leave all QAM MAC settings blank and allow ARP to determine the MAC address of the next Layer 3 device connected to the Streamer. To specify the next Layer 3 device, see the
“Configuring the Route Table” section on page 4-66 .
To view the current configuration for a QAM gateway, Choose Configure > QAM Gateway, choose the
QAM IP address from the drop-down list, and click Next.
To configure a QAM gateway, do the following:
Step 1
Choose Configure > QAM Gateway. The QAM Gateway page is displayed (
Note
If Bulk Configuration is enabled, the Configuration File Location field is displayed, along with the Browse and Import buttons. To import a Bulk Configuration XML file, click Browse to locate the file, then Import to import the file. The status of the import is displayed in the left panel.
For information on enabling the Bulk Configuration feature, see the
“Bulk Configuration” section on page D-4
. For information about creating a Bulk Configuration file for QAM
Gateways, see the
“Creating QAM Gateway Bulk Configuration Files” section on page B-2 .
Step 2
From the drop-down list, choose enter new and click Next.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-5
System Level Configuration
Figure 4-1 QAM Gateway Page
Chapter 4 Configuring the CDS
Step 3
Enter the QAM gateway settings as appropriate. See
for descriptions of the fields.
Table 4-3 QAM Gateway Fields
Field
QAM IP
QAM MAC
Description
IP address of the QAM gateway.
MAC address of the next Layer 3 device connected to the Streamer in the path to the
QAM modulator. The MAC address can be entered with or without the colon separators.
Stream Group
Preferences
We recommend you leave the QAM MAC setting blank and allow ARP to determine the MAC address of the next Layer 3 device. To specify the next Layer 3 device, see the
“Configuring the Route Table” section on page 4-66 .
Choose the preference for each Stream Group. The preferences are:
•
High—First preference of Streamer or Stream Group to stream to this QAM.
•
None—Do not use this Streamer or Stream Group to stream to this QAM.
For more information on creating Stream Groups, see the
.
Step 4
Click Submit.
To reset the fields, click Reset.
4-6
To edit a QAM gateway, choose the QAM IP address and click Next. Enter the new settings and click
Submit.
To delete a QAM gateway, choose the QAM IP address, click Next, and then click Delete QAM.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
System Level Configuration
Configuring the Headend Setup
The Headend Setup page is associated with the Service Group Steering optional feature.
Note
The Headend Setup page is not available if the Stream Destination is set to IPTV. For more information,
see the “Stream Destination” section on page D-4
.
Service Group Steering is used to associate service groups with Stream Groups. The Headend Setup page offers more granularity than the QAM Gateway page. The QAM Gateway page allows you to assign preference to which Stream Groups serve which QAM Gateways. The Headend Setup page allows you to assign preference to which Stream Groups serve which service group.
Note
The Headend Setup page is displayed only if the Service Group Steering feature is enabled. For more information, see the
“Service Group Steering” section on page D-9
Note
You must first configure the Stream Groups before you can configure the headend setup for a specific service group. See the
“Configuring Stream Groups” section on page 4-29
.
To configure the headend setup, do the following:
Step 1
Choose Configure > Headend Setup. The Headend Setup page is displayed (
Note
If Bulk Configuration is enabled, the Configuration File Location field is displayed, along with the Browse and Import buttons. To import a Bulk Configuration XML file, click Browse to locate the file, then Import to import the file. The status of the import is displayed in the left panel.
For information on enabling the Bulk Configuration feature, see the
“Bulk Configuration” section on page D-4
. For information about creating a Bulk Configuration file for QAM
Gateways, see the
“Creating Headend Setup Bulk Configuration Files” section on page B-3 .
Figure 4-2 Headend Setup Page
OL-22792-01
Step 2
From the Select Service Group drop-down list, choose Add New.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-7
Chapter 4 Configuring the CDS
System Level Configuration
Step 3
Step 4
Step 5
In the New Service Group field, enter the service group name.
Choose the preference for each Stream Group. The preferences are:
•
High—First preference of Streamer or Stream Group to stream to this service group.
•
•
Medium—Second preference of Streamer or Stream Group to stream to this service group.
Low—Lowest preference of Streamer or Stream Group to stream to this service group.
•
None—Do not use this Streamer or Stream Group to stream to this service group.
For more information on creating Stream Groups, see the
“Configuring Stream Groups” section on page 4-29 .
Click Submit.
To delete a service group, choose it from the Select Service Group drop-down list and click Delete.
Configuring Stream Destinations
The Stream Destination page provides a way to associate subnetworks with Stream Groups. The Stream
Destination page is an alternative to the QAM Gateway page and Headend Setup page where you associate a Stream Group with a specific QAM device and any applicable service groups. Mapping
Stream Groups to specified subnets is appropriate for IPTV networks, where each end-user device has its own IP address.
Note
The Stream Destination page is not available if the Stream Destination is set to Cable. For more information, see the
“Stream Destination” section on page D-4 .
To configure the Stream Destination, do the following:
Step 1
Choose Configure > Stream Destination. The Stream Destination page is displayed (
Note
If Bulk Configuration is enabled, the Configuration File Location field is displayed, along with the Action on Import option, and the Browse and Import buttons.
To import a Bulk Configuration XML file, click Browse to locate the file, select Add for the
Action on Import, then Import to import the file. The status of the import is displayed in the left panel.
To delete the configurations defined in the Bulk Configuration XML file, click Browse to locate the file, select Delete for the Action on Import, then Import. All the subnets defined in the Bulk
Configuration XML file are deleted and the status is displayed in the left panel.
For information on enabling the Bulk Configuration feature, see the
Gateways, see the “Creating Stream Destination Bulk Configuration Files” section on page B-4
.
Step 2
From the Subnet drop-down list, choose enter new.
To edit a subnet, choose the subnet from the Subnet drop-down list.
4-8
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
Figure 4-3 Stream Destination Page
System Level Configuration
OL-22792-01
Step 3
Enter the subnet address and subnet mask and click Submit.
Note
If network address translation (NAT) is used for the STBs, be sure the IP subnet reflects the public, routeable IP address for the NAT device, not the internal private IP address of the STB.
Step 4
Choose the preference for each Stream Group. The preferences are:
•
High—First preference of Streamer or Stream Group to stream to this subnet.
•
•
•
Medium—Second preference of Streamer or Stream Group to stream to this subnet.
Low—Lowest preference of Streamer or Stream Group to stream to this subnet.
None—Do not use this Streamer or Stream Group to stream to this subnet.
Note
If your CDS network is deployed with a single-site steering configuration, you only see High and None as Stream Group Preference options, and only one Stream Group can have a preference of high.
Step 5
For more information on creating Stream Groups, see the
“Configuring Stream Groups” section on page 4-29
.
Click Submit.
To reset the fields, click Reset.
To delete a subnet, choose the subnet from the Subnet drop-down list, and click Delete Subnet.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-9
Chapter 4 Configuring the CDS
System Level Configuration
Configuring the Bandwidth Manager
The Bandwidth Manager runs on the master Streamer and keeps track of allocated streams and VOD network resources.
Note
The Bandwidth Manager is an optional feature is not listed if it is not included in your deployment. For information on enabling the Bandwidth Manager feature, see the
“Bandwidth Manager” section on page D-7
.
To configure the Bandwidth Manager, do the following:
Step 1
Choose Configure > Bandwidth Manager. The Bandwidth Manager page is displayed ( Figure 4-4
).
Figure 4-4 Bandwidth Manager Page
Step 2
Enter the Bandwidth Manager settings as appropriate. See
Table 4-4 for descriptions of the fields.
Table 4-4 Bandwidth Manager Fields
Field
Bandwidth Manager IP
1
Bandwidth Manager
Port
Database Thread Pool
Server Thread Pool
Description
IP address of the network interface card (NIC) you want the Bandwidth
Manager to bind to. Valid entry includes an asterisk (*) and 0.0.0.0, which signifies the Bandwidth Manager IP is set individually for each Streamer on the RTSP Setup page. See the
“Configuring RTSP Setup” section on page 4-75
for more information.
Port number to listen on for incoming connections from the RTSP server.
The default is 7791. The lowest port number you can allocate is 150. The highest port number is 60000.
Number of threads in the database connection pool. The default is 10. The minimum number of database threads is 1; the maximum is 100.
Number of threads in the Bandwidth Manager server pool that are used to process RTSP requests for the duration of the connection. The default is 5.
The minimum number of server thread pools is 1; the maximum is 100.
4-10
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
System Level Configuration
Table 4-4 Bandwidth Manager Fields (continued) (continued)
Field
Sync Thread Pool
Sync Alarm
Description
Number of threads available to synchronize sessions with the RTSP during a synchronization operation. The default is 2. The minimum number of synchronization thread pools is 2; the maximum is 50.
How often the synchronization alarm is triggered. The default is 864,000 seconds (10 days). The minimum amount of time the synchronization alarm trigger can be set to is 2400 seconds (40 minutes). The maximum amount of time is 4,294,967,296 (over 136 years).
1.
Changes to this field affect the same field on the RTSP Setup page.
Step 3
Step 4
Click Submit.
To clear the settings, click Reset.
Reload the Bandwidth Manager service.
a.
Choose Maintain > Services. The Services Restart page is displayed.
b.
c.
From the drop-down list, choose the IP address or nickname of the server and click Display.
Check the Reload Bandwidth Manager check box and click Submit.
To clear the fields and start over, click Reset.
Configuring the Ingest Manager
The Ingest Manager takes care of provisioned content objects by collecting the metadata, sending messages to the appropriate subsystem to ingest the content, and sending messages to expire the content when the expiration period is past.
Note
The Ingest Manager is an optional feature. The Ingest Manager is not listed on the System Level left-panel menu if it is not included in your deployment. For information on enabling the Ingest Manager feature, see the
“Ingest Manager” section on page D-8
.
To configure the Ingest Manager, do the following:
Step 1
Choose Configure > Ingest Manager. The Ingest Manager page is displayed ( Figure 4-5
).
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-11
System Level Configuration
Figure 4-5 Ingest Manager Page
Chapter 4 Configuring the CDS
Step 2
Enter the Ingest Manager settings as appropriate. See
Table 4-5 for descriptions of the fields.
4-12
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
System Level Configuration
Table 4-5 Ingest Manager Fields
Field Description
General Settings
Ingest Manager Host Ingest Manager listener binds to this IP address. Enter an asterisk (*) if you want to listen to all IP addresses on the system.
Ingest Manager Port Port number to use for listening for inbound connections.
Callback Port
Additional Package
Window
FTP Timeout
Use Asset ID
Manage CORBA
Services
Require Notify
Service
Port number to use for File Services Interface (FSI) callbacks.
Additional time to wait after the package expiration window has been reached before destroying the content.
Maximum period (in seconds) the Ingest Manager waits before timing out an
FTP session and terminating the process.
Choose Yes to use the Asset ID for the content name, otherwise choose No.
The recommended setting is No. If set to No, the Ingest Manager uses the
*.mpg as the content name when used in combination with the Media
Scheduler.
Choose Yes to have the CDS manage the CORBA services, otherwise choose
No.
Choose Yes to have the CDS require the use of the Notify Service, otherwise choose No.
Ingest Manager Debug Choose Off to have the debug logging turned off. Choose Low to have minimal information and error logging. Choose Full for full debug logging information.
Meta Data Publish Choose Enable from the drop-down list to publish the content metadata, otherwise choose Disable.
Meta Publish URL #1 URL where the metadata is published, typically the backoffice.
Meta Publish URL #2 URL of the backup server where the metadata is published.
Ingest Settings
Ingest Interface
Name Service IP and
Port
Notify Service IP and
Port
Choose all the ingest interfaces that apply: ISA, Cisco SOAP, Prodis SOAP; otherwise choose Disable to disable the Ingest Manager.
IP address and port of the CORBA Naming Service used by the backoffice.
ISA-only field.
IP address and port of the CORBA Notification Service used by the backoffice.
ISA-only field.
Notify Service Factory Name used to locate the Notify Service through corbaloc protocol. The default name used is NotifyEventChannelFactory. ISA only-field.
Event Channel ID Simple name that identifies the root directory of the Event Channel where all event channels need to register. The default is EventChannels. ISA-only field.
Event Channel Kind Directory extension of the Event Channel ID. The default is Context. ISA-only field.
Factories ID Simple name that identifies the root directory of the factories where all factories need to register. The default is Factories. ISA-only field.
Factories Kind Factories ID extension. The default is Context. ISA-only field.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-13
Chapter 4 Configuring the CDS
System Level Configuration
Table 4-5 Ingest Manager Fields (continued)
Field Description
Package Channel ID Simple name that identifies the Package Event Channel where all events concerning package objects are published. The default is PackageChannel.
ISA-only field.
Package Channel Kind Event Channel Package ID extension. The default is Factory. ISA-only field.
Package Factory ID Simple name that identifies the root directory of the factories where all factories need to register. The default is PackageFactory. ISA-only field.
Package Factory Kind Factories ID extension. The default is Factory. ISA-only field.
Package Factory Name Name of the Package Factory that will be registered with the backoffice. The default is AVS_PackageFactory. ISA-only field.
Package Factory
Server ID
Cisco SOAP URL
Prodis SOAP URL
Numeric value that identifies the Package Factory Server for all ingests. The default is 90. ISA-only field.
IP address, port, and directory on the Vault used to receive content using the
Cisco SOAP (Simple Object Access Protocol). You can specify the IP address and port number, but the directory must be “CiscoAIM.” An example of the
Cisco SOAP URL is http://10.22.216.251:8793/CiscoAIM.
IP address, port, and directory on the Vault used to receive content using the
Prodis SOAP. You can specify the IP address and port number, but the directory must be “ProdisAIM.” An example of the Prodis SOAP URL is http://10.22.216.251:8793/ProdisAIM.
Backoffice Settings
Max Retries
Retry Interval
Maximum number of times to retry a failed communication with the backoffice. The range is 0–1000. The default is 10.
Amount of time (in minutes) to wait before retrying a failed communication.
The range is 0–10080. The default is 10.
Backoffice Timeout
Backoffice
If the Retry Interval is set to zero, the Ingest Manager retries once every 6000 seconds (100 minutes).
Tip
By default, the Ingest Manager does not retry an expired package. Set the Retry Interval, as well as the Publish Time Adjustment field on the Input Channel page, so that if publishing a package fails, a retry can happen at least once before the start time of the recording. See the
“Configuring Input Channels” section on page 4-24
for more information.
Amount of time (in seconds) to wait for the backoffice to respond to a communication attempt. The range is 0–3600. The default is 300.
Choose TotalManage to use the TotalManage backoffice support, otherwise choose Disable to disable backoffice support.
Location of the TotalManage backoffice.
Backoffice URL
Content Store Settings
Content Store
Content Store URL
Choose the type of content store: ISA, FSI, or NGOD. To disable the content store, choose Disable.
URL where the content store is located.
4-14
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
System Level Configuration
Table 4-5 Ingest Manager Fields (continued)
Field Description
Encryption Settings
Encryption
Encryption URL
Choose Verimatrix, or Widevine to use encryption. Choose Disable to disable encryption.
Location on the encryption server used to send MPEG files for encryption. An example of the Encryption URL is http://192.168.128.54:7898/files/encrypted, where the IP address, port ,and directory is specified.
Encryption FTP URL Location on the encryption server used to retrieve encrypted MPEG files. An example of the Encryption FTP URL is ftp://192.168.128.54:7899/files/encrypted, where the IP address, port, and directory is specified.
Step 3
Click Submit.
To clear the settings, click Reset.
Configuring the Authentication Manager
Note
The Authentication Manager is an optional feature. The Authentication Manager is not listed on the
System Level left-panel menu if it is not included in your deployment. For information on enabling the
Authentication Manager feature, see the
“Authentication Manager” section on page D-8 .
The Authentication Manager communicates with the backoffice to validate a request received from a set-top box (STB) before setting up a session. Before requesting a session setup from the CDS, the STB requests an entitlement key from the backoffice. The STB then passes the entitlement key as one of the parameters in the request to the CDS. The CDS in turn passes the entitlement key to the backoffice to validate the request. If the backoffice responds that the entitlement key is not valid, the session is not set up and the CDS returns an error status to the STB.
To configure the Authentication Manager, do the following:
Step 1
Choose Configure > Authentication Manager. The Authentication Manager page is displayed
(
).
Note
Depending on the Authentication Manager protocol selected (either Cisco or EventIS), the
Authentication Manager displays different fields.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-15
System Level Configuration
Figure 4-6 Authentication Manager Page—Cisco
Chapter 4 Configuring the CDS
Step 2
Enter the Authentication Manager settings as appropriate. See
for descriptions of the fields.
Table 4-6 Authentication Manager Fields
Field
Authentication
Manager IP
1
Description
Authentication Manager resides on the master Streamer. Typically, the Authentication Manager IP address is the same as that of the master Streamer.
Protocol
EventIS
Cisco
Authentication
Manager Port
Notification Retry
Interval
Debug Level
Authentication Manager port number default is 7794. This port number is determined by the properties specifications of the
Authentication Manager. If you need to change the port number, contact Cisco technical support.
EventIS Hostname Hostname or IP address of the EventIS server.
EventIS Port
Authentication
Server SOAP
Interface
Port number on the EventIS server used to receive authentication requests.
IP address, port, and logical partition on the Streamer used to receive messages about session teardowns in the following format: http://<ip_address>:<port><path>
EventIS
EventIS
Cisco
Authentication
Timeout
Time to wait, in seconds, for the authentication server to respond.
The range is from 1 to 10.
Time to wait, in seconds, before attempting to connect to the authentication server again. The range is from 1 to 60.
EventIS
Cisco
EventIS
Cisco
Cisco
From the Debug Level drop-down list, choose ERROR to have the debug logging only reporting errors. Choose INFO to report minimal information and error logging. Choose HIGH for a high level of debug logging information. Choose HEX_DUMP for the highest debug level.
EventIS
Cisco
1.
Changes to this field affect the same field on the RTSP Setup page.
Step 3
Click Submit.
4-16
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
System Level Configuration
Configuring the Redirect Server
The Redirect Server page allows you to configure the port used for RTSP redirects and allows you to enable or disable the debug level for logging.
Note
The Redirect Server page is not available if the Redirect Server feature is not enabled. For more information, see the
“Redirect Server” section on page D-4
.
To configure the Redirect Server settings, do the following:
Step 1
Step 2
Step 3
Step 4
Choose Configure > Redirect Server. The Redirect Server page is displayed.
In the Redirect Server Port field, enter the port number to use for RTSP redirects.
From the Debug Level drop-down list, choose OFF to disable the debug logging or choose ON to enable the debug logging.
Click Submit.
To reset the field, click Reset.
Configuring Ingest Tuning
The Ingest Tuning page allows you to set the speeds of the trick-mode files created for each ingested content.
To view the current ingest tuning settings Choose Configure > Ingest Tuning.
To configure the ingest tuning, do the following:
Step 1
Choose Configure > Ingest Tuning. The Ingest Tuning page is displayed (
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-17
System Level Configuration
Figure 4-7 Ingest Tuning Page
Chapter 4 Configuring the CDS
Step 2
Enter the ingest tuning settings as appropriate. See
Table 4-7 for descriptions of the fields.
4-18
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
System Level Configuration
Table 4-7 Ingest Tuning Fields
Field Description
Trick-Mode Settings
Speed 1
Speed 2
You can set eight different trick-mode speeds for each ingested content. A trick-mode file, either fast-forward or rewind (–X), is created for each selected speed.
Speed 3
Choose the trick-mode speed from the drop-down list and click Submit. Available trick-mode speeds are 2, 4, 5, 6, 8, 10, 15, 30, 32, 60, and 127.
Speed 4
To reset the values and start over, click Reset.
Speed 5
Speed 6
Speed 7
Speed 8
Ingest MPEG Settings
Program ID
Standardization
If Program Identifier (PID) Standardization is enabled, MPEG-2 video assets have their PIDs standardized at ingest so that most assets use the same PIDs.
PSI
Sequence End
Remove
Rate
Standardize
It may be important that all assets use the same PIDs, for example, if multiple assets are going to be part of a playlist and you cannot guarantee that all assets were created with a consistent set of PIDs. The standard PID assignment follows the CableLabs recommendations (see MD-SP-VOD-CEP2.0-I02-070105). Any changes made to the asset is reversed if an FTP OUT is performed. Only standard audio/video assets that may be used in playlists have their PIDs standardized; data downloads, audio only, carousel files, and such other files are left unmodified. Changing the PIDs does not affect normal VOD playback of the asset.
When Program ID Standardization is enabled, you have an option to enable or disable PSI. Enabling Program ID Standardization only standardizes the PIDs, not the Program Specific Information (PSI). If you choose Enabled for PSI, the Program
Association Table (PAT) and the Program Map Table (PMT) are standardized so that they do not vary at all between one piece of content and another. Use these settings progressively to try and resolve issues with playlists (black scree or no video after transitions, temporary glitches, and so on). Use Program ID Standardization only first, reingest the content, and play the content. If there are still problems, try both enabling Program ID Standardization and PSI. If there are problems playing the content back that was ingested with both of these options enabled, disable them and reingest the content to see if the issue resolves.
If Sequence End Remove is enabled, a SEQ END header that is present at the end of the asset (and only at the end) is removed on ingest. Doing this allows fades between assets in a playlist , which can make the playlist appear more seamless. Any changes made to the asset is reversed if an FTP OUT is performed. Removing the SEQ END, if present, makes no difference to the VOD playback of the asset.
If Rate Standardize is enabled, MPEG-2 video assets have their rates standardized at ingest so that most assets use one of two standard rates, 3.75 Mbps for SD assets and
15 Mbps for HD assets. These settings follow CableLabs recommendations.
Standardizing the rates can be helpful in certain configurations if playlists are going to be created containing multiple assets and you cannot guarantee that all assets were created with consistent rates. For example, some QAM devices do not handle rate changes during playout. Consult your QAM vendor for guidance on whether to enable
Rate Standardize. Any changes to the asset are reversed if an FTP OUT is performed.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-19
Chapter 4 Configuring the CDS
System Level Configuration
Step 3
Click Submit.
To clear the fields and start over, click Reset.
Configuring IP Nicknames
The IP nicknames are used as an alternative for the IP address in the CDSM drop-down lists.
To configure an IP nickname for a CDS server or QAM gateway, do the following:
Step 1
Choose Configure > IP Nickname. The IP Nicknames page is displayed (
).
Figure 4-8 IP Nicknames Page
Step 2
Step 3
Step 4
Choose the IP address from the applicable drop-down list, either Cisco CDSM IP Addresses or
Configured QAM Gateway IP Addresses, and click Display.
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.
Click Submit.
To reset the field, click Reset.
To edit or view a current IP nickname association, choose an IP address or nickname from the drop-down list and click Display.
4-20
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
System Level Configuration
Configuring the Media Importer
Note
The Media Importer is part of the MediaX Suite, which is an optional feature.
The Media Importer settings allows you to specify the data feed import type used in populating the
Media Scheduler with data from an EPG file, as well as to configure the automatic import function.
To configure the Media Importer, do the following:
Step 1
Choose Configure > System Level > Media Importer. The Media Importer page is displayed
(
).
Figure 4-9 Media Importer Page
OL-22792-01
Step 2
Enter the settings as appropriate. See
for descriptions of the fields.
Table 4-8 Media Importer Fields
Field Description
Media Importer Settings
Importer Type To upload the EPG using the CDSM, set the Importer Type to host. For information on uploading an EGP file, see the
“Uploading an EPG File” section on page 7-10
.
Transformer Type Transformer Type is configured at the time of initial installation and specifies the EPG format of either OCN or SA Tribune. This is a read-only field.
Enable Auto Import To automatically import the EPG information, check the Enable Auto Import check box. The Auto Import fields are displayed.
FTP Server IP IP address of the FTP server that is used to send the EPG file.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-21
Chapter 4 Configuring the CDS
System Level Configuration
Table 4-8 Media Importer Fields (continued)
Field
FTP Path
Username
Password
Retry Count
Retry Interval
Auto Import Schedule
Daily
Weekly
Description
Directory path of the location of the EPG files on the FTP server.
Username, if required, to access the FTP server.
Password, if required, to access the FTP server.
Number of times to retry connecting to the FTP server, if the connection fails.
Number of seconds to wait before retrying the connection to the FTP server.
If daily is chosen (the default setting), enter the time of day the EPG file should be imported using the 24-hour clock format.
If weekly is chosen, choose the days of the week and the time of day (24-hour clock format) when the EPG file should be imported.
Step 3
Click Submit.
To reset the field, click Reset.
Configuring Call Signs
The CallSign Setup page is used to configure the call signs of the program channels.
Note
The CallSign Setup is an optional feature. The CallSign Setup is not listed on the System Level left-panel menu if it is not included in your deployment.
A call sign is a unique identifier for a program channel. The channels, identified by their call signs, are mapped to a multicast IP address and port that a content provider or satellite uses to send content by using the Single-Program Transport Stream (SPTS) IP interface.
To configure a CallSign, do the following:
Step 1
Choose Configure > System Level > Callsign Setup. The CallSign Setup page is displayed
(
).
4-22
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
Figure 4-10 CallSign Setup Page
System Level Configuration
OL-22792-01
Step 2
Enter the call sign settings as appropriate. See
for descriptions of the fields.
Table 4-9
Field
CallSign
Multicast IP
Port
CallSign Setup Fields
Description
CallSign is a unique identifier for a program channel (content source).
Multicast IP address of the device sending a Single Program Transport Stream
(SPTS).
Port associated with the CallSign.
Step 3
Click Submit.
To edit a CallSign setting, enter the CallSign, the new settings, and click Submit. The new settings overwrite the previous settings and are displayed in the Configured CallSigns section.
To delete a CallSign setting, check the Delete check box associated with the entry and click Delete.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-23
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 several values for metadata generation.
If you upload an EPG file, and you want to modify the metadata for all programs for a channel, then add the channel in the Input Channels page and enter the modifications in the fields provided. All scheduling information from the EPG file is listed on the Media Scheduler page. For more information, see the
“Uploading an EPG File” section on page 7-10 .
Caution
All channel default values specified on the Input Channels page overwrites any metadata information for future ingested assets of the specified channel. The metadata for the assets already ingested are not affected.
To define a channel and set the metadata information, do the following:
Step 1
Choose Configure > System Level > Input Channels. The Input Channels page is displayed
(
).
Figure 4-11 Input Channels Page
Step 2
From the Select Channel drop-down list, choose Add New Channel.
Note
The Channel Name is automatically generated by combining the Provider and Channel ID fields with a hyphen (-) between the values.
4-24
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
System Level Configuration
Step 3
Step 4
In the Multicast Group IP field, enter the multicast IP address that the Vault must join (by using IGMP) to ingest content.
In the Port field, enter the port number the Vault should listen to for ingesting content.
Step 5
Note
The combination of the IP address and port must be unique for each channel.
Enter the channel settings as appropriate. See
Table 4-10 for descriptions of the fields.
Table 4-10 Input Channels Fields
Field
Channel Code
Channel ID
Category ID
Catalog ID
Product
Provider
Provider ID
Preview Period
Licensing Window
Start
Licensing Window
End
Encryption
Rating
Publish Time
Adjustment
Suggested Price
Billing ID
Audio Type
Description
Used to create the asset name and the category in the Asset Distribution
Interface (ADI) metadata file. Maximum length is three characters.
Identifies the channel in the EPG file.
Identifies the category corresponding to the channel (numeric only).
Channel ID used in the catalog.
Choose movie on demand (MOD), subscriber video on demand (SVOD), or
Real-Time Innovations (RTI) as the product type for this channel.
Name of the provider.
Unique identifier for the provider of all assets in this channel. The Provider ID must be set to a registered Internet domain name that is restricted to at most 20 lowercase characters and belongs to the provider. For example, a valid Provider
ID for CableLabs is “cablelabs-films.com.”
Amount of time (in seconds) the subscribers are allowed to preview assets on this channel before they are charged for viewing the asset.
From the drop-down list, choose the number of days to add to the start date of the license window for all assets in this channel.
From the drop-down list, choose the number of days to add to the end date of the license window for all assets in this channel.
If the assets on this channel are encrypted, choose Yes. Otherwise, choose No.
Motion Picture Association of America (MPAA) rating for all assets on this channel (G, PG, PG13, R, or NC-17).
Amount of time to add to the start time for publishing each program on this channel to the backoffice. The Publish Time Adjustment must be longer than the value set for the Media Importer/Exporter Pre-Notification field.
Suggested price for each asset on this channel. The format is xx.xx.
Billing ID for every asset on this channel. This field applies only to the SA
Tribune transformer type.
Audio types available for all assets on this channel (Dolby ProLogic, Dolby
Digital, Stereo, Mono, Dolby 5.1).
Step 6
Click Submit.
To reset the field, click Reset.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-25
System Level Configuration
Note
You cannot delete a channel that has future scheduled events.
Chapter 4 Configuring the CDS
To view, edit, or delete a current channel setup, from the Select Channel drop-down list choose the channel. The Channel Setup page refreshes with the configuration for the channel selected. To delete the channel, click Delete. To edit the channel configuration, edit the fields and click Submit.
Configuring Source Output Ports
Note
The Source Output Port page is displayed when NGOD is selected as the RTSP Deployment Type on the
CDSM Setup page. For more information, see the
“RTSP Deployment Type” section on page D-8 .
The Multiple SOPs feature introduces the ability to create SOP domains and associate a virtual IP address with each domain. The stream interfaces on the Streamer are grouped by using the Route Tables page and are associated with an SOP domain and virtual IP address. This allows for the grouping of the stream interfaces on a Streamer into two groups, each group associated with an SOP domain and virtual
IP address, to direct traffic from the stream interfaces to two different routers.
The logical SOP appears to the other NGOD components as a single interface, but internally to the CDS, the logical SOP could represent multiple physical interfaces on multiple Streamers. All the physical interfaces of a logical SOP are directed to one router, while the interfaces of another logical SOP are directed to a different router. Each Streamer, defined by a logical SOP, connects to a different router.
In Release 2.1.1 and Previous Releases
In Release 2.1.1 and previous releases that were configured for an RTSP environment with an NGOD deployment, the CDSM provided a Server Level configuration page, the RTSP Setup page, which included configuration fields for the physical SOP IP and port and the logical SOP. The physical SOP
IP and port were the IP address and port number of the gigabit Ethernet interface that was used as the
SOP on the Streamer. The logical SOP was the domain name used for identification purposes to the On
Demand Resource Manager (ODRM). The logical SOP (domain name of the SOP) was tied to the entire
Streamer. The Streamer is part of a Stream Group, and a system can have multiple Stream Groups in a system, each supporting a different SOP.
The logical SOP domain name, maximum number of streams, and maximum bandwidth for each SOP are provided to the ODRM vendor. The ODRM vendor uses this information along with the service group information, QAM device information, and so on, to configure the system.
In Release 2.1.2 and Later Releases
In Release 2.1.2 and later releases that were configured for an RTSP environment with an NGOD deployment, the SOP domain name and a virtual IP address are added through the Source Output Port page. Each group of stream interfaces on a Streamer are represented by a virtual IP address and SOP domain.
The stream interfaces (or stream/cache interfaces) on each Streamer connect to two routers, with half the interfaces directed to one router and the other half of the interfaces directed to the other router. This is accomplished by way of the Route Tables page. For more information, see the
.
4-26
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
Array Level Configuration
If there are three Streamers, for example, with stream interfaces 1 to 6 going to router 1 and stream interfaces 7 to 12 going to router 2, the following SOPs need to be created:
•
•
SOP A is defined as interfaces 1 to 6 on Streamer 1, 2, and 3.
SOP B is defined as interfaces 7 to 12 on Streamers 1, 2, and 3.
The Multiple SOP feature allows for stream routing control, provides balance across the routers, and provides redundancy in case of a transport network failure. If a stream interface fails, another stream interface in the same SOP takes over.
Configuring Multiple SOPs
The following rules apply for the Multiple SOP feature:
•
•
There is a one-to-one relationship between the SOP virtual IP address and domain name, and the stream interface subnet configured in the Route Tables page.
SOP virtual IP address and domain name should not span more than one Stream Group.
Note
A logical SOP, which is an SOP virtual IP address and domain name, can span multiple source subnets.
To configure the Multiple SOP feature, do the following:
Step 1
Step 2
Step 3
Step 4
Step 5
Choose Configure > System Level > Source Output Port. The Source Output Port page is displayed.
In the SOP Name field, enter the domain name of this Streamer for identification purposes to the On
Demand Resource Manager (ODRM). In Release 2.1.1 and previous releases, this was the Logical SOP field on the RTSP Setup page.
In the Virtual IP field, enter the virtual IP address for this SOP.
Click Submit.
to
for each SOP.
The configured SOPs are displayed in the bottom half of the page. To delete an SOP, check the Delete check box associated with the SOP and click Submit.
To complete the configuration of multiple SOPs, you must define each route in the Route Table page and choose CServer Source as the Route Type. For more information, see the
“Configuring the Route Table” section on page 4-66 .
Array Level Configuration
•
•
•
The Array Level tab has the following configuration options:
•
Configuring the Array Level DNS
Configuring the Array Level NTP Server
•
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-27
Chapter 4 Configuring the CDS
Array Level Configuration
•
•
•
•
•
•
•
•
•
Mapping Vault Groups to Cache Groups
Mapping Stream Groups to Cache-Fill Sources
Mapping Vault Groups for Redundancy
Configuring the Master Vault Group
Configuring the Control and Setup IPs
Configuring Cache-Fill Bandwidth Using Thin Pipe Mapping
Configuring the Media Scheduler
Note
The Array Level configuration settings are distributed to all servers in the specified array.
Configuring the Array Level DNS
The Array DNS page is used to configure up to 16 domain suffixes and 16 DNS servers.
To view the current Array DNS settings for an Array Level, Choose Configure > Array Level > Array
DNS, choose an array name from the drop-down list, and click Display.
Note
If you are upgrading the TV CDS software to Release 2.3 from Release 2.0 or an earlier release, the system prompts you to Submit any settings that have previous domain suffixes to populate the new DNS database structure.
To configure the DNS settings for an Array Level, do the following:
Step 1
Step 2
Step 3
Choose Configure > Array Level > Array DNS. The Array DNS page is displayed.
From the Array Name drop-down list, choose an array and click Display.
Enter the DNS binding Array Level settings as appropriate. See
for descriptions of the fields.
Table 4-11 Array DNS Fields
Field
New Domain
Suffix
Description
Specify, if applicable, the internal domain that is used to fully qualify an unqualified hostname. For example, if you are using OpenStream as the BMS, specify a subdomain consistent with what OpenStream is using, for example, bms.n2bb.com. Accordingly, unqualified hostnames used in CORBA transactions, such as contentstore, resolve correctly to contentstore.bms.n2bb.com.
New DNS Server IP address of the DNS server.
Step 4
Click Submit.
To clear the fields and start over, click Reset.
4-28
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
To delete the DNS settings, check the Delete check box and click Delete Entry.
Array Level Configuration
Configuring the Array Level NTP Server
The Array NTP Server page is used to configure up to 16 NTP servers.
To view the current NTP settings for an Array Level, choose Configure > Array Level > Array NTP
Server, choose an array name from the drop-down list, and click Display.
To configure the NTP settings for an Array Level, do the following:
Step 1
Step 2
Step 3
Step 4
Choose Configure > Array Level > Array NTP Server. The Array NTP Server page is displayed.
From the Array Name drop-down list, choose an array and click Display.
In the New NTP Server field, enter the IP address of the NTP server.
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-73
.
Configuring Stream Groups
A Stream Group consists of one or more Streamers. Streamers within a Stream Group work as a team with regard to content caching, load distribution, and bandwidth usage. Stream Groups interact with other Stream Groups by passing streams among each other based on performance qualification and cost considerations. If a Stream Group must give up a stream to another group, Stream Group preferences set on the QAM Gateway page are followed. Stream Groups relate to QAM gateways or destination subnetwork by the Stream Group preference. For more information about Stream Group and QAM
gateway associations, see the “Configuring QAM Gateways” section on page 4-4 . For more information
about destination subnetworks and Stream Groups, see the
“Configuring Stream Destinations” section on page 4-8
.
A Streamer can never be a member of more than one Stream Group.
When grouping Streamers you should take into account network cost to stream, bandwidth usage, and geographic locations of Streamers and QAM gateways. All Streamers in a group are considered to have the same cost to reach a destination.
VVI with Split-Domain Management and HTTP Streamers
A VVI with split-domain management has one manager (VVIM) that manages the Vaults and Caching
Nodes, and one manager (Stream Manager) that manages the Streamers.
When you use CCP Streamers in a VVI, all group IDs and server IDs need to be unique among all servers in the VVI. The VVIM manages all the group IDs and server IDs for the VVI with CCP Streamers. The
Stream Manager gets an allotment of group IDs from the VVIM in one of two ways:
•
During the initial installation, by way of the CDSM Setup page
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-29
Chapter 4 Configuring the CDS
Array Level Configuration
•
In the first-time configuration of Stream Groups
Communication between the VVI Manager and the Stream Manager is accomplished through database replication when CCP is used as the protocol.
The CDSM Setup page for the Stream Manager has a field for the VVIM IP address. The VVIM IP address is used to send an HTTP GET request to the VVIM for a range of group IDs. If the Stream
Manager is unable to reach the VVIM, either because port 80 is not open for communication or some other connectivity reason, the Stream Group page displays a field for entering the beginning group ID.
The administrator of the Stream Manager gets the beginning group ID from the administrator of the
VVIM. The VVIM gets the beginning group ID on the Configuration Generator page. For more information, see the
“Identifying Server IDs and Group IDs for VVI with Split-Domain Management” section on page 7-10 .
For more information about the VVI settings on the CDSM Setup page, see the “Virtual Video
Infrastructure” section on page D-6
.
Caution
The beginning group ID must be generated by the VVIM, and if manually entered, it must be entered correctly. Entering the wrong ID can cause cache-fill failures and other issues.
To configure a Stream Group, do the following:
Step 1
Choose Configure > Array Level > Stream Groups Setup. The Stream Groups page is displayed
(
).
To edit a Stream Group, choose the Stream Group from the drop-down list and click Display.
Figure 4-12 Stream Groups Page
Step 2
Step 3
Step 4
From the Select Stream Group to View/Edit drop-down list, choose Add New Stream Group and click
Display.
In the New Stream Group Name field, enter the name of the Stream Group and click Submit.
You can use only alphanumeric characters (0–9, a–z, A–Z), the dash (-), and the underscore (_) to create a Stream Group name.
Add the Streamers to the Stream Group.
4-30
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
Array Level Configuration
The unassigned Streamers are listed along with a drop down-list for each that offers the options
Table 4-12 Unassigned Streamer Options
Unassigned Streamer Option
No Change
Stream Group Name
None
Description
Do not make any changes to the Stream Group assignment.
Add this Streamer to this Stream Group.
Remove this Streamer from this Stream Group. Applicable only to Streamers assigned to the selected Stream Group.
Step 5
Click Submit.
To reset the field, click Reset.
To view the members of a Stream Group, choose the Stream Group from the drop-down list and click
Display.
To delete a Stream Group, first remove all Streamers from the group, then click Delete Group.
Caution
If you delete a Stream Group or edit the members of a Stream Group, and the Stream Destination feature is enabled, you must re-submit each Stream Destination subnet that is associated with the Stream Group that you changed or deleted.
Locating Cache Groups
The Cache Group Locator page is used by the Stream Manager in a VVI with split-domain management to identify and locate the Cache Groups that are managed by the VVIM. Split-domain management uses port 80 to communicate group IDs and server IDs. The databases for each domain are separate.
Note
The Cache Group Locator page is available only on the Stream Manager when VVI is enabled. For more information, see the
“Virtual Video Infrastructure” section on page D-6
.
There are two methods on the Cache Group Locator page for getting the Cache Group information:
•
Import
•
Upload
The Import option uses an HTTP GET request to communicate with the VVIM in retrieving the Cache
Groups. The Upload option uploads an XML file that was created by the VVIM. To use the Import option, the Stream Manager must know the IP address of the VVIM and must be able to communicate
with the VVIM over port 80. The VVIM IP address is set on the CDSM Setup page. See the “Virtual
must be downloaded from the VVIM and delivered to the administrator of the Stream Manager. For more information on downloading the XML file from the VVIM, see the
“Identifying Server IDs and Group
IDs for VVI with Split-Domain Management” section on page 7-10 .
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-31
Chapter 4 Configuring the CDS
Array Level Configuration
To identify and locate the Cache Groups, do the following:
Step 1
Choose Configure > Array Level > Cache Group Locator. The Cache Group Locator page is displayed
(
).
Figure 4-13 Cache Group Locator Page
Step 2
Step 3
Step 4
From the Configured Cache Locations drop-down list, choose Add Cache Group Locations.
Choose either Import or Upload.
If you choose Import, do the following:
a.
In the VVIM IP, enter the IP address of the VVIM.
b.
a.
b.
If the VVIM IP address was provided in the CDSM Setup page, or previously on the Cache Group
Locator page, it is displayed in the VVIM IP field.
Click Import Cache Groups.
The Stream Manager sends an HTTP GET request over port 80 to the VVIM for the Cache Group information. If the VVIM does not respond with the CacheGroupsConfig.xml file before the timeout period, the Cache Group Locator page displays the Upload option.
If you choose Upload, do the following:
Get the CacheGroupsConfig.xml file from the administrator of the VVIM and save it to a location you can access from the CDSM (for example, to your local machine).
Click Browse to locate the CacheGroupsConfig.xml file. The Choose File dialog box is displayed.
c.
Navigate to the file and click Open. The path and filename are displayed in the Cache Groups File
Location field.
Click Upload.
d.
After the CacheGroupsConfig.xml file is either imported or uploaded, the Cache Groups are listed in the
Configured Cache Locations drop-down list.
To view, edit, or delete a Cache Group Location, do the following:
Step 1
Choose Configure > Array Level >Cache Group Locator. The Cache Group Locator page is displayed.
4-32
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
Array Level Configuration
Step 2
Step 3
Step 4
From the Configured Cache Locations drop-down list, choose a Cache Group location. The page refreshes and the Cache Group information is displayed. The Location Virtual IP and Location Subnet fields are informational only.
To rename the Cache Group Location, enter a new name in the Cache Location Name and click Submit.
To reset the field, click Reset
To delete a Cache Group location, click Delete.
Configuring Vault Groups
A Vault Group consists of one or more Vaults. Vaults within a Vault Group work as a team with regard to content ingest, cache-fill responses, load distribution, and bandwidth usage. Vault Groups interact with other Vault Groups by passing cache-fill requests among each other based on performance qualification and cost considerations. For more information on Vault Group redundancy, see the
“Mapping Vault Groups for Redundancy” section on page 4-40
.
Note
The Vault Groups Setup page is part of the Vault Redundancy feature and is displayed only if Vault
Redundancy is enabled. For more information, see the
“Vault Redundancy” section on page D-5 . If VVI
is enabled, The Vault Groups Setup page is displayed only on the VVIM. For more information, see the
“Virtual Video Infrastructure” section on page D-6 .
A Vault can never be a member of more than one Vault Group.
When grouping Vaults you should consider network costs, bandwidth usage, and geographic locations of Vaults, Caching Nodes, and Streamers. All Vaults in a group are considered to have the same cost to reach a destination.
Note
The maximum number of Vault Groups is 20.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-33
Chapter 4 Configuring the CDS
Array Level Configuration
To configure a Vault Group, do the following:
Step 1
Choose Configure > Array Level > Vault Groups Setup. The Vault Groups Setup page is displayed
(
).
Figure 4-14 Vault Groups Setup Page
Step 2
Step 3
Step 4
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.
In the New Vault Group Name field, enter the name of the Vault Group and click Submit.
You can use only alphanumeric characters (0–9, a–z, A–Z), the dash (-), and the underscore (_) to create a Vault Group name.
Add the Vaults to the Vault Group.
The unassigned Vaults are listed along with a drop down-list for each that offers the options described in
Table 4-13 Unassigned Vault Options
Unassigned Vault Option
No Change
Vault Group Name
None
Description
Do not make any changes to the Vault Group assignment.
Add this Vault to this Vault Group.
Remove this Vault from this Vault Group. Applicable only to
Vaults assigned to the selected Vault Group.
Step 5
Click Submit.
To reset the field, click Reset.
4-34
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
Array Level Configuration
To view the members of a Vault Group, choose the Vault Group from the drop-down list and click
Display.
To delete a Vault Group, first remove all Vaults from the group, then click Delete Group.
Configuring SSV Groups
An SSV Group consists of one or more ISVs. ISVs within an SSV Group work as a team with regard to content ingest, cache-fill responses, load distribution, and bandwidth usage. SSV Groups interact with other SSV Groups by passing cache-fill requests among each other based on performance qualification and cost considerations.
Note
The SSV Groups Setup page is part of the SSV Group feature and is displayed only if SSV Group is enabled. For more information, see the
“SSV Groups” section on page D-5 . The Vault Redundancy Map
page and the Thin Pipe Map page are also displayed when SSV Groups is enabled. The Vault
Redundancy Map page can be used to map SSV Groups for mirroring. For more information, see the
“Mapping Vault Groups for Redundancy” section on page 4-40
. The Thin Pipe Map page can be used to configure low-bandwidth connections among SSV Groups. For more information, see the
Cache-Fill Bandwidth Using Thin Pipe Mapping” section on page 4-44
.
An ISV can never be a member of more than one SSV Group.
Note
The term SSV used in the CDSM GUI is the same as the ISV. The terms are interchangeable.
When grouping ISVs you should consider network costs, bandwidth usage, and the geographic locations of the ISVs. All ISVs in a group are considered to have the same cost to reach a destination.
Note
The maximum number of SSV Groups is 20.
To configure an SSV Group, do the following:
Step 1
Step 2
Step 3
Step 4
Choose Configure > Array Level > SSV Groups Setup. The SSV Groups Setup page is displayed.
From the Select SSV Group to View/Edit drop-down list, choose Add New SSV Group and click
Display.
To edit an SSV Group, choose the SSV Group from the drop-down list and click Display.
In the New SSV Group Name field, enter the name of the SSV Group and click Submit.
You can use only alphanumeric characters (0–9, a–z, A–Z), the dash (-), and the underscore (_) to create an SSV Group name.
Add the SSVs (ISVs) to the SSV Group.
The unassigned SSVs are listed along with a drop down-list for each that offers the options described in
.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-35
Chapter 4 Configuring the CDS
Array Level Configuration
Table 4-14 SSV Options
SSV Option
No Change
Vault Group Name
None
Don’t Change
Step 5
Click Submit.
To reset the field, click Reset.
Description
Do not make any changes to the SSV Group assignment.
Add this Vault to this SSV Group.
Remove this SSV from this SSV Group. Applicable only to
SSVs assigned to the selected SSV Group.
Do not assign this SSV to this SSV Group.
To view the members of an SSV Group, choose the SSV Group from the drop-down list and click
Display.
To delete an SSV Group, first remove all SSVs from the group, then click Delete Group.
Configuring Cache Groups
A Cache Group consists of one or more Caching Nodes. Caching Nodes within a Cache Group work as a team with regard to content caching, load distribution, and bandwidth usage. Cache Groups interact with other Cache Groups by passing cache-fill requests among each other based on performance qualification and cost considerations. If a Cache Group must give up a cache-fill task to another group,
Cache Group preferences set on the Stream to Cache Map page are followed.
Note
The Cache Groups Setup page is part of the VVI feature and is displayed only on VVIMs.
A Caching Node can never be a member of more than one Cache Group.
When grouping Caching Nodes you should take into account network costs, bandwidth usage, and geographic locations of Vaults, Caching Nodes, and Streamers. All Caching Nodes in a group are considered to have the same cost to reach a destination.
To configure a Cache Group, do the following:
Step 1
Choose Configure > Array Level > Cache Groups Setup. The Cache Groups Setup page is displayed
(
).
4-36
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
Figure 4-15 Cache Groups Setup Page—HTTP Streamers
Array Level Configuration
OL-22792-01
Step 2
Step 3
Step 4
Step 5
From the Select Cache Group to View/Edit drop-down list, choose Add New Cache Group and click
Display.
To edit a Cache Group, choose the Cache Group from the drop-down list and click Display.
In the New Cache Group Name field, enter the name of the Cache Group and click Submit.
You can use only alphanumeric characters (0–9, a–z, A–Z), the dash (-), and the underscore (_) to create a Cache Group name.
For a VVI that uses HTTP for communication between the Caching Nodes and Streamers, do the following:
a.
b.
In the Location Virtual IP field, enter the IP address this Cache Group uses as the virtual IP address for the Locate Port service. The virtual IP address is bound to the Locate IP and Port. For more information about the Locate Port service, see the
“HTTP Streamers” section on page 2-9
.
In the Location Subnet Mask field, enter the subnet mask for the Location IP address.
Add the Caching Nodes to the Cache Group.
The unassigned Caching Nodes are listed along with a drop down-list for each that offers the options
Table 4-15 Unassigned Caching Node Options
Unassigned Caching Node Option
No Change
Cache Group Name
None
Description
Do not make any changes to the Cache Group assignment.
Add this Caching Node to this Cache Group.
Remove this Caching Node from this Cache Group. Applicable only to Caching Nodes assigned to the selected Cache Group.
Step 6
Click Submit.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-37
Chapter 4 Configuring the CDS
Array Level Configuration
To reset the field, click Reset.
To view the members of a Cache Group, choose the Cache Group from the drop-down list and click
Display.
To delete a Cache Group, first remove all Caching Nodes from the group, then click Delete Group.
Mapping Vault Groups to Cache Groups
The Cache To Vault Map page is used to map Vault Groups to Cache Groups in a VVI. Before you can
map Vault Groups to Cache Groups, you must create them. For more information, see the “Configuring
Cache Groups” section on page 4-36 and the
“Configuring Vault Groups” section on page 4-33 .
Note
The Cache To Vault Map page only displays on the VVIM and is available only when Vault Redundancy and VVI are both enabled. For more information, see the
“Vault Redundancy” section on page D-5
and the
“Virtual Video Infrastructure” section on page D-6
.
To map Vault Groups to Cache Groups, do the following:
Step 1
Step 2
Step 3
Step 4
Choose Configure > Array Level > Cache To Vault Map. The Cache To Vault Map page is displayed.
From the Cache Group drop-down list, choose a Cache Group and click Select. All available Vault
Groups are displayed. By default, all preferences are set to None.
Choose the preference setting for each Vault Group. Following are the possible preferences:
•
•
High—First preference as a source for cache-fill requests.
Medium—Second preference as a source for cache-fill requests.
•
•
Low—Lowest preference as a source for cache-fill requests.
None—Do not use this Vault Group as a cache-fill source.
Groups with the same preference level are considered equally as a cache-fill source. At least one Vault
Group must have a preference higher than None.
Click Submit.
To reset the field, click Reset.
To view the Vault Group mappings of a Cache Group, choose the Cache Group from the drop-down list and click Display.
To delete a Cache Group or a Vault Group, see the
“Configuring Cache Groups” section on page 4-36 or
the “Configuring Vault Groups” section on page 4-33
. When a Cache Group is deleted, the mapping for the Cache Group is also deleted, and any mapping to the Cache Group in the Stream To Cache Map page is also deleted. When a Vault Group is deleted, the Vault Group is removed from each Cache Group mapping; any mapping for the Vault Group in the Vault Redundancy Map page is also deleted.
4-38
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
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 to Stream Groups in a VVI. Before you
“Configuring Cache Groups” section on page 4-36
for more information.
In a VVI with split-domain management, the Stream Manager must know about the Cache Groups to map the Stream Groups to the Cache Groups. See the
“Locating Cache Groups” section on page 4-31
for more information.
Note
The Stream To Cache Map page is available only on the Stream Manager when VVI is enabled. For more information, see the
“Virtual Video Infrastructure” section on page D-6
.
Streamers can be used as cache-fill sources when Streamer is Cache is enabled on the Server Setup page
(
“Configuring the Servers,” page 4-58 ). A Stream Group is available on the Stream To Cache Map page
when at least one Streamer in a Stream Group has Streamer is Cache enabled.
To map Cache Groups to Stream Groups, do the following:
Step 1
Choose Configure > Array Level > Stream To Cache Map. The Stream To Cache Map page is
).
Figure 4-16 Stream To Cache Map Page
OL-22792-01
Step 2
Step 3
From the Stream Group drop-down list, choose a Stream Group and click Select. All available Cache
Groups and Stream Groups are displayed. By default, all preferences are set to None.
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.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-39
Chapter 4 Configuring the CDS
Array Level Configuration
Step 4
•
None—Do not use this Cache Group or Stream Group as a cache-fill source.
Groups with the same preference level are considered equally as a cache-fill source. At least one Cache
Group must have a preference higher than None.
Click Submit.
To reset the field, click Reset.
To view the Cache Group mappings of a Stream Group, choose the Stream Group from the drop-down list and click Display.
To delete a Stream Group or Cache Group, see the
“Configuring Stream Groups” section on page 4-29
or “Configuring Cache Groups” section on page 4-36 . When a Stream Group is deleted, the mapping for
the Stream Group is also deleted. When a Cache Group is deleted, the Cache Group is removed from each Stream Group mapping, and any mapping for that Cache Group in the Vault To Cache Map page is also deleted. When a Vault Group is deleted, the Vault Group is removed from each Stream Group mapping, and any mapping for the Vault Group in the Vault Redundancy Map page is also deleted.
Mapping Vault Groups for Redundancy
The Vault Redundancy Map page is used to map Vault Groups to each other. Before you can map Vault
Groups for redundancy, you must create them. See the
“Configuring Vault Groups” section on page 4-33
for more information.
Note
The Vault Redundancy Map page is part of the Vault Redundancy feature and is displayed only if Vault
Redundancy is enabled. If VVI is enabled, The Vault Redundancy Map page is displayed only on the
VVIM. For more information, see the
“Virtual Video Infrastructure” section on page D-6 and the
Redundancy” section on page D-5
.
Note
In Release 2.3, the maximum number of Vault Groups is 20.
Vault Groups interact with other Vault Groups by passing cache-fill requests among each other based on performance qualification and cost considerations. If a Vault Group must give up a cache-fill task to another group, Vault Group preferences set on the Vault Redundancy Map page are followed. For more
information on Vault Group redundancy, see the “Vault Group Redundancy” section on page 1-10 .
To map a Vault Group to another Vault Group, do the following:
Step 1
Choose Configure > Array Level > Vault Redundancy Map. The Vault Redundancy Map page is displayed (
4-40
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
Figure 4-17 Vault Redundancy Map Page
Array Level Configuration
OL-22792-01
Step 2
Step 3
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.
Choose the preference setting for the Vault Group. The possible preferences are:
•
Mirror—Content is mirrored to this Vault Group, and this Vault Group becomes the source for content requests from Streamers or Caching Nodes if the primary Vault Group becomes unavailable.
You can select up to three Vault Groups to which to mirror content.
Note
The Vault Mirror Copies field in the Server Setup page determines the number of mirrored
for more information. The Vault Redundancy Map page specifies which Vault Groups participate in the content mirroring.
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-33 . When a Vault Group
is deleted, the mapping for the Vault Group is also deleted.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-41
Chapter 4 Configuring the CDS
Array Level Configuration
Configuring the Master Vault Group
The Master Vault Group page allows you to select the Vault Group that has the master Vault and the master IP address. One of the Vaults in the Master Vault Group is designated the master Vault. If the master Vault fails, another Vault in the Master Vault Group takes over as the master Vault.
The master IP address is set as part of the initial configuration (cdsconfig script) and the information is added to the statsd line in the rc.local file.
To locate the master Vault in the Master Vault Group, log in to each Vault as root and enter the ifconfig
-a | more command. The master Vault has the virtual IP address (eth0:1) output as follows: eth0:1 Link encap:Ethernet HWaddr 00:11:00:00:00:00 inet addr:172.22.98.54 Bcast:172.22.99.255 Mask:255.255.254.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Memory:b8820000-b8840000
The slave Vaults do not have the virtual IP address as up.
Note
The Master Vault Group page is part of the Vault Redundancy feature and is displayed only if Vault
Redundancy is enabled. If VVI is enabled, The Master Vault Group page is displayed only on the VVIM.
For more information, see the
“Virtual Video Infrastructure” section on page D-6
and the
Redundancy” section on page D-5
.
To configure the Master Vault Group, do the following:
Step 1
Step 2
Step 3
Choose Configure > Array Level > Master Vault Group. The Master Vault Group is displayed.
Click the Master Vault Group radio button associated with the Vault Group.
Click Submit.
Note
After you have submitted the settings the first time, if you change the Master Vault Group, you must restart all the Vaults in the old Master Vault Group and the new Master Vault Group for the changes to take effect. See the
“Restarting a Server” section on page 7-5
for more information.
Configuring the Control and Setup IPs
A Streamer designated as the Setup server interfaces with the backoffice and forwards the setup messages to the appropriate Stream Group. There can only be one IP address designated as the Setup server for each Stream Group. In an RTSP environment, the Setup server and Control server must be the same server.
Note
In an RTSP environment that uses VVI with split-domain management, each Stream Manager is allotted two Setup IDs for the Setup servers. If the Stream Manager uses both Setup IDs, it contacts the VVIM for additional Setup IDs. If the VVIM is unreachable, the Control/Setup IP page displays the Setup ID
Group IDs for VVI with Split-Domain Management” section on page 7-10 .
4-42
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
Array Level Configuration
The Control server is used to communicate with Lightweight Stream Control Protocol (LSCP) clients or
Real Time Streaming Protocol (RTSP) clients. Each Control server handles up to 18,000 sessions. You must configure a Control server for each group of up to 18,000 sessions. For instance, if you have 19,000 sessions, you need to configure two Control servers. The Control servers are associated with each Stream
Group. For this release there can only be one Control server for each Stream Group.
For more information about the Control and Setup servers, see the
“Streamer Workflow” section on page 2-8
.
To configure a Control/Setup IP, do the following:
Step 1
Choose Configure > Array Level > Control/Setup IP. The Control/Setup IP page is displayed
(
Figure 4-18 Control/Setup IP Page
Step 2
Step 3
For each Stream Group, enter the IP address and subnet mask of the Control IP, Setup IP, or
Control/Setup IP.
From the IP Type drop-down list, choose an IP type. See
for descriptions of the types.
Table 4-16 Control/Setup Types
Type
Control IP
Setup IP
Control/Setup IP
Description
IP address used only for LSCP or RTSP client control.
IP address of the Setup server.
Control/Setup IP address used for LSCP or RTSP client control.
Step 4
Click Submit.
To reset the field, click Reset.
OL-22792-01
Note
All currently configured Control/Setup IPs are listed in the Configured Control/Setup IPs section of the
Control/Setup IP page.
To edit a Control/Setup IP, make any changes to the Control/Setup IP as necessary, and click Submit.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-43
Array Level Configuration
To delete a Control/Setup IP, check the Delete check box and click Submit.
Chapter 4 Configuring the CDS
Configuring Cache-Fill Bandwidth Using Thin Pipe Mapping
The Thin Pipe Map page allows you to configure low-bandwidth connections between local and remote groups. A local group consists of servers in the same group, for example, all the Streamers in a Stream
Group are considered part of the same group, or local group. A local group consists of CDS servers in the same local area network (LAN). A remote group consists of all the servers in the other Stream
Groups, Cache Groups, and Vault Groups. A remote group consists of all the CDS servers that are reachable by way of a wide area network (WAN).
There can be multiple thin pipes configured for each local group. As an example, a site with Caching
Nodes organized into a Cache Group could have one 500-Mbps thin pipe going to a site with a Vault
Group, and a second 500-Mbps thin pipe going to a location with a Stream Group. The thin pipes are completely independent of each other.
The Thin Pipe Map page also allows for the configuration of thin pipes in a hierarchy, where a remote group must be reached through several pipes. For example, a Cache Group could have a 500 Mbps thin pipe over which it streams to multiple Stream Groups. Each Stream Group could have separate 100 Mbps thin pipes. In this case, the Cache Group traffic on egress to all Stream Groups is limited to 500 Mbps, while ingress traffic to each Stream Group from this Cache Group is limited to 100 Mbps. In this example, the Cache Group would have four thin pipes configured: one 500 Mbps pipe to all three Stream
Groups, and a total of three 100 Mbps pipes, one to each individual Stream Group.
Note
The Thin Pipe Map page is displayed only if Thin Pipe Management is enabled. See the
Management” section on page D-6 for more information.
For CCP traffic to work properly in the CDS, the following configuration must exist:
•
•
•
Thin pipe mapping must be configured in the CDS.
DiffServ AF settings must be configured on the CDS servers.
Routers must support the bandwidths that are configured for the thin pipe mapping on the CDS.
Note
The configured bandwidth for CCP on the Thin Pipe Map page must be the minimum bandwidth reserved for the AF class. The sum of the bandwidths of all physical links configured for CCP among all sites must be less than the bandwidth configured for the AF class reserved for CCP.
CCP is used as the protocol among Vaults and Caching Nodes in a VVI that uses HTTP, and among all servers in a VVI that uses CCP and in all non-VVIs. The AF class is configured on each CDS server. See the
“Configuring the Servers” section on page 4-58 for more information.
As an example,
Figure 4-19 shows the maximum bandwidth available for the various groups in a Virtual
Video Infrastructure (VVI) system with two super headends (SHEs), three caching sites, and one streaming site.
4-44
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
Figure 4-19 Thin Pipe Example
Array Level Configuration
OL-22792-01
Note
The maximum bandwidth available is dictated by the physical link, as well as by any network design constraints placed on bandwidth availability. If a switched network has further restrictions, for example,
Vault Group 1 (VG1) to Vault Group 2 (VG2) and Cache Group 3 (CG3) share a 3 Gbps link on the route between VG1 and the other two sites, then another thin pipe must be configured to specify this 3-Gbps restriction.
lists the thin pipe mappings that would be configured for the different Vault Groups illustrated in
.
Table 4-17 Thin Pipe Mappings for Thin Pipe Example
Thin Pipe Map Remote Group
Vault Group 1 (VG1)
VG1toAll Vault Group 2, Cache Group 1, Cache Group 2, Cache Group 3 5
Bandwidth
(Gbps)
VG1toVG2
VG1toCG1
VG1toCG2
Vault Group 2
Cache Group 1
Cache Group 2
VG1toCG3
Vault Group 2 (VG2)
Cache Group 3
VG2toAll Vault Group 1, Cache Group 1, Cache Group 2, Cache Group 3 4
2
2
4
2
VG2toCG1
VG2toCG2
VG2toCG3
Cache Group 1
Cache Group 2
Cache Group 3
Cache Group 1 (CG1)
CG1toAll Vault Group 1, Vault Group 2, Cache Group 2, Cache Group 3
2
2
2
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-45
Chapter 4 Configuring the CDS
Array Level Configuration
Table 4-17 Thin Pipe Mappings for Thin Pipe Example (continued)
Thin Pipe Map Remote Group
CG2toSG1 Stream Group 1
Cache Group 2 (CG2)
CG2toAll Vault Group 1, Vault Group 2, Cache Group 1, Cache Group 3 2
Cache Group 3 (CG3)
CG3toAll Vault Group 1, Vault Group 2, Cache Group 1, Cache Group 3 2
Bandwidth
(Gbps)
3
The thin pipes configured in
ensure that the bandwidth for Vault Group 1 never exceeds the maximum bandwidth available for Vault Group 1, which is 5 Gbps. This means that even if all remote groups were requesting cache fills from Vault Group 1, which would be a maximum throughput of 9
Gbps, the actual maximum bandwidth of cache-fill traffic coming from Vault Group 1 would never exceed 5 Gbps.
To configure a Thin Pipe Map, do the following:
Choose Configure > Array Level > Thin Pipe Map. The Thin Pipe Map page is displayed
(
).
Figure 4-20 Thin Pipe Map Page
Step 5
Step 6
Step 7
Step 8
From the Configured Pipes drop-down list, choose Create New Pipe and click Select.
To edit a Pipe Map, choose the Pipe Map from the drop-down list and click Select.
From the Local Group drop-down list, choose the group you want to use as the local group for this thin pipe map.
In the Pipe Name field, enter the name for the pipe map.
In the Max Bandwidth field, enter the maximum megabits per second (Mbps) for this pipe.
The maximum bandwidth entered applies to each server in the group. For example, if the maximum bandwidth between two groups is designed as 5 Gbps (5000 Mbps) and there are two servers in each group, then the entered amount should be 2500 Mbps (5000 Mbps divided by the number of servers in the group).
4-46
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
Array Level Configuration
Note
The maximum bandwidth threshold is 75 percent of the Max Bandwidth field.
Step 9
Step 10
Step 11
In the Available Remote Groups area, check the check box next to each remote group that you want to use this maximum bandwidth restriction.
Check the Limit HTTP check box if this thin pipe is to limit the bandwidth between Caching Nodes and
Streamers in a VVI that uses HTTP as the caching protocol.
Click Submit
To reset the field, click Reset.
To delete a thin pipe mapping, choose the pipe name from the Configured Pipes drop-down list, click
Select, and click Delete.
Configuring the Media Scheduler
Note
The Media Scheduler page is part of the optional MediaX feature.
The Media Scheduler page allows you to schedule content for ingest and generate content metadata. The channels available in the Media Scheduler page are determined by the channels included in the uploaded
EPG file and those configured on the Input Channels page. See the
“Uploading an EPG File” section on page 7-10
and the
“Configuring Input Channels” section on page 4-24
for more information.
The ingest time is calculated by adding the value of the ingest schedule start timeslot to the Publish Time
Adjustment field from the Input Channels page.
Note
To be able to schedule content, you must add the channels through the Input Channel page, and then either upload an EPG file to populate the cells in the Media Scheduler, or manually enter the metadata using the Media Scheduler Package Metadata window.
From the Media Scheduler page, you can perform the following tasks:
•
•
Choose the channels to schedule content ingest.
View the content metadata for each selected timeslot.
•
Schedule content to be ingested for a particular channel, provided all required ADI metadata values are available.
Add metadata values if they are not available, or modify the metadata values.
•
•
Resolve any conflicts in the EPG data.
The following procedure walks you through all these tasks.
User Preferences
To schedule content ingest and edit metadata information, do the following:
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-47
Chapter 4 Configuring the CDS
Array Level Configuration
Step 1
Choose Configure > Array Level > Media Scheduler. The User Preferences for the Media Scheduler page is displayed (
Figure 4-21 Media Scheduler Page—User Preferences
Step 2
Choose either Hide On Return or Show On Return to display the user preferences each time you go to the Media Scheduler page.
Note
You can change the user preferences at any time by clicking Edit Settings in the main Media
Scheduler page or when the calendar is displayed. To have your settings recalled each time you log in to the CDSM, see the
“Changing User Default Settings” section on page 7-4
.
Step 3
Step 4
Step 5
For Action on Recurring Schedules, choose either Preserve Existing Schedules or Overwrite
Existing Schedules. This option is only for user-generated schedules; this option is not for uploaded
EPG data. For more information, see the
“Package Metadata Editor” section on page 4-52 .
Preserving Existing Schedules keeps any content that is currently scheduled for the day and channel you selected, and fills only the empty timeslots. Overwrite Existing Schedules overwrites any content that is currently scheduled for the day and channel you selected.
When you schedule an event that originated from an uploaded EPG file, the Media Scheduler creates a package name combining the channel name, title brief, and the word “package.” For Package Name
Auto-Generation, if the package name already exists and you want a new package name auto-generated, choose Enable and the start time is added to the package name. If the package name already exists and you want to create the package name using the Metadata Editor, choose Disable.
Check the check boxes for the channels you want to schedule.
4-48
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
Array Level Configuration
Step 6
Note
To create new channels, see the
“Configuring Input Channels” section on page 4-24 .
Click Save to save the settings. The calendar is displayed (
).
Figure 4-22 Media Scheduler Page—Calendar
To clear the fields and start over, click Reset.
Scheduling Content for Ingest
To schedule content ingest and edit metadata information, do the following:
Step 1
Step 2
Choose Configure > Array Level > Media Scheduler. If Hide On Return was selected in the User
Preferences, the Media Scheduler calendar is displayed (
). If Show On Return was selected in the User Preferences, the User Preferences are displayed (
From the calendar, click the day you want to schedule. If the month you are scheduling is not shown, use the left and right arrows on either side of the calendar to change the month.
Note
Today’s date is displayed with a box around it.
The schedule for the day you selected is displayed (
).
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-49
Array Level Configuration
Figure 4-23 Media Scheduler Page—Schedule
Chapter 4 Configuring the CDS
Depending on the status of the schedule, the schedule cells that contain data (programs) are displayed in different colors. When you first view the Media Scheduler page with uploaded EPG data, all the programs are in the “Not Scheduled” state. The Media Scheduler page displays a legend describing the different colors for the cells in the schedule.
Small timeslots are marked blue. To view the program information on small timeslots, click the timeslot.
The page refreshes and the schedule for the small timeslot is displayed at the bottom of the page.
Tip
To view information about a program, move the mouse pointer over a cell. A pop-up displays the program information (
4-50
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
Figure 4-24 Media Scheduler Page—Program Information
Array Level Configuration
OL-22792-01
Step 3
Click each cell for each program you want to schedule.
If all the required information for metadata creation is available for the channel and the timeslot, the color of the cell changes to green, indicating that the timeslot is “Marked for Scheduling.”
If all the required information for metadata creation is not available, a new window opens and the
Package Metadata Editor is displayed. See the
“Package Metadata Editor” section on page 4-52
.
Tip
Alternatively, you can click the channel column heading to schedule all unscheduled events for that channel. If all required metadata information is available, this method automatically submits the changes and refreshes the page with all the timeslots marked “Scheduled.
Tip
The Bulk Schedule option allows you to schedule the events for multiple channels at the same time. To schedule all channels or a group of channels for a whole day, click Bulk Schedule. The
Bulk Schedule dialog box is displayed. Check the check box next to each channel and click
Submit. If all required metadata information is available, this method schedules all the timeslots for the day. To check all the channels, check Select All. To uncheck all the channels, check
Unselect All. The field alternates from Select All to Unselect All fields.
Note
You can only schedule current and future timeslots. However, you can view past timeslots.
Step 4
Click Submit. The Media Scheduler page refreshes and all the “Marked for Scheduling” cells are changed to “Scheduled.”
Note
Only current and future schedule entries can be edited.
To remove a scheduled ingest, click the scheduled timeslot. The timeslot changes from “Scheduled” to
“Marked for Unscheduling.” Click Submit.
Tip
You can mark timeslots for unscheduling and mark different timeslots for scheduling, and submit all the changes at one time.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-51
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-25 Package Metadata Editor—User-Generated Timeslot
Metadata that originates from an EPG file is created using a combination of channel values (set in the
Input Channels page) and data uploaded from the EPG file. If all the data is available, the metadata is generated, the content is scheduled for ingest, and the start time is set for publishing the content.
4-52
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
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-26 Recurring Schedule Options for User-Generated Schedules
OL-22792-01
Check the Recurring Schedules check box to copy the metadata information to the timeslots specified in the Recurring Schedule fields. See
for descriptions of the Recurring Schedule fields.
Table 4-18 Recurring Schedule Fields
Field Option
Recurrence Pattern Daily
Recurrence End
Time
Weekly
Monthly
One year from start time
End After
End By
Description
If Daily is selected, the metadata is copied to the same timeslot each day until the Recurrence End Time is reached.
If Weekly is selected, the metadata is copied to the same timeslot on each day of the week selected (Sun, Mon, Tue,
Wed, Thu, Fri, Sat) until the Recurrence End Time is reached.
If Monthly is selected, the metadata is copied to the same timeslot on the week selected (1st, 2nd, 3rd, 4th, last) and day of the week selected (Sun, Mon, Tue, Wed, Thu, Fri,
Sat) until the Recurrence End Time is reached.
Recurrence Pattern is repeated for one year from the metadata Start Time.
Recurrence Pattern is repeated the number of times you specify in the occurrences field.
Recurrence Pattern is repeated until the date you specified in the End By field is reached.
Step 3
Depending on the setting in the User Preferences settings, any existing metadata is preserved or overwritten. See the
“User Preferences” section on page 4-47
for more information.
Fill in any missing information, or edit existing information, using the Package Metadata and click
Submit.
For information on the fields displayed in the Package Metadata, see the CableLabs Video-On-Demand
Content Specification Version 1.1 (MP-SP-VOD-CONTENT1.1-I03-040107) document at http://www.cablelabs.com
.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-53
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.
To view these conflicts and schedule the latest information, do the following:
Step 1
Choose Configure > Array Level > Media Scheduler. The Media Scheduler page displays all the conflicts, including those events that have passed (
To go to the main Media Scheduler page, click Go To Scheduler.
Figure 4-27 Media Scheduler Page—Conflicts
Step 2
Step 3
Step 4
To fix a scheduling conflict, click the link for the record number. The Media Scheduler page refreshes and displays the channel of the selected conflict.
The timeslots that have conflicts are displayed with a brown color.
To clear a conflict, click the timeslot. The timeslot gets the latest information and is displayed with the color green, indicating “Marked for Scheduling” if all the metadata information is available.
If all the required information for metadata creation is not available, a new window opens and the
Package Metadata Editor is displayed (
Figure 4-25 ). Fill in the metadata as required and click Submit.
The Package Metadata Editor window closes.
After all the conflicts have been cleared on the Media Scheduler page, click Submit to schedule all
“Marked for Scheduling” timeslots.
4-54
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
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.
The Server Level tab has the following configuration options:
•
•
•
•
•
•
•
•
Configuring the Server Level DNS
Configuring the Server Level NTP
Configuring the Interfaces
The Interface Setup page is used to configure the different interfaces on the CDS servers. The functionality of the Ethernet interfaces on the CDS servers is configurable. However, there is an optimal configuration for each server. The interface functions are described in
Table 4-19 CDS Interfaces
Type
General
Description
Reserves an Ethernet interface to allow optimal configuration.
Management Communicates with other network devices with regards to condition of the server, stream control, and ISA communications.
Ingest Establishes connectivity with a content provider system and to ingest content on to a Vault or an ISV.
Cache Transports content between Vaults and Streamers, or in the case of VVI, between
Vaults, Caching Nodes, and Streamers.
Stream/Cache Used on the Streamer for both cache and streaming traffic. If an interface is configured for both cache and streaming traffic on a Streamer, priority with be given to the higher-bandwidth stream traffic provided cache traffic is able to transmit on other interfaces.
Stream Transports streams to the QAM devices, or to subnets in the case of IPTV.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-55
Chapter 4 Configuring the CDS
Server Level Configuration
Table 4-19 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-42 . To configure a
separate route subnet for stream control traffic, see the
.
Locate Used on the Caching Nodes to communicate with HTTP Streamers. One interface on the Caching Node must be set to Locate for HTTP Streamers. HTTP Streamers are supported only in a Virtual Video Infrastructure (VVI). For more information, see the
“Caching Node Workflow” section on page 2-9 .
For all CDE servers, the optimal configuration is:
•
•
eth0 as management eth1 as ingest on Vaults and ISVs
•
All other interfaces are available for cache, stream, stream/cache, stream control, or locate, as appropriate for the server
To configure the interface settings, do the following:
Step 1
Step 2
Choose Configure > Server Level > Interface Setup. The Interface Setup page is displayed
(
).
From the Server IP drop-down list, choose the IP address or nickname of the server and click Display.
4-56
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
Figure 4-28 Interface Setup Page—Vault Page
Server Level Configuration
OL-22792-01
Step 3
Step 4
Choose each interface setting as appropriate.
Click Submit to save the settings.
To clear the fields and start over, click Reset.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-57
Chapter 4 Configuring the CDS
Server Level Configuration
Configuring the Servers
After a server has been initially configured, the CDSM detects it and the IP address or nickname of the server is available for selection in the server drop-down lists.
To configure the server settings, do the following:
Step 1
Step 2
Step 3
Choose Configure > Server Level > Server Setup. The Server Setup page is displayed.
From the Server IP drop-down list, choose the IP address or nickname of the server and click Display.
The fields differ for a Vault, Streamer, and ISV server.
Figure 4-29 shows the Server Setup for a Vault.
shows the Server Setup for a Streamer. The ISV server setup page has a combination of the
Vault and Streamer fields. See
for descriptions of the fields and to which server they apply.
The fields for the Caching Node setup page are described in
Table 4-20 lists the CDSM GUI ID names and maps them to the CServer names in the setupfile and
.arroyorc files.
Table 4-20 ID Names in the CDSM GUI and CServer Files
CDSM GUI ID Name
Array ID on the Array Name page
Group ID on the Server-Level pages
Stream Group ID on the Server Setup page
CServer Files ID Name
groupid groupid arrayid
Cache Group ID on the Server Setup page
Vault Group ID on the Server Setup page arrayid arrayid
Stream Group ID on the Configuration Generator page arrayid
4-58
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
Figure 4-29 Server Setup–Vault Server Page
Server Level Configuration
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-59
Server Level Configuration
Figure 4-30 Server Setup—Streamer Server Page
Chapter 4 Configuring the CDS
4-60
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
Server Level Configuration
Table 4-21 Server Setup Fields
Field
Hostname
Description
Fully qualified hostname for this server. The name can be up to 64 characters long.
Assigning a hostname is optional.
The hostname must be fully qualified, for example: vault.cisco.com.
Server Type
All servers:
Vault, Caching
Node,
Streamer, ISV
The DNS must be able to resolve the hostname to the IP address you select, with both forward and reverse lookups. If you enter a hostname that cannot be resolved, you may not be able to access the server.
TTL IP time to live (TTL) for data packets. The IP TTL default is 16 hops. Valid entries range from 0 to 255.
Null Streaming From the Null Streaming drop-down list, choose Enabled to allow the streaming of null
MPEG files, or Disabled to prevent the streaming of null MPEG files.
Default Stream/Cache Settings
Source IP Default source IP address for all stream and cache interfaces. If the source IP address is left blank, the default of 192.168.207.65 is used.
Starting
Transport Port
Ending
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.
Ending default UDP port number used for stream and stream/cache interfaces. There is no default for the ending transport port number.
Rate
Standardize
This field is informational only. If this field is set to enable, then MPEG-2 video assets have their rates standardized at ingest so that most assets use one of two standard rates,
3.75 Mbps for SD assets or 15 Mbps for HD assets. To change the settings of the Ingest
MPEG fields, see the
“Configuring Ingest Tuning” section on page 4-17
.
Stream Group Information
Stream Group
Stream Group
ID
These fields display the Stream Group and Stream Group ID the ISV or Streamer is a member of. The Stream Group and Stream Group ID are informational only. To configure
Stream Groups, see the
“Configuring Stream Groups” section on page 4-29
.
All servers
All servers
All servers
Streamer, ISV
Streamer, ISV
Cache Port Default UDP port number used for cache traffic between servers. If the cache port is left blank, the default of 48879 is used.
Ingest MPEG Settings
PID
Standardization
Sequence End
Remove
This field is informational only. If this field is set to enable, then MPEG-2 video assets have their program identifiers (PIDs) standardized at ingest so that most assets use the same PIDs. To change the settings of the Ingest MPEG fields, see the
.
This field is informational only. If this field is set to enable, a SEQ END header that is present at the end of the asset (and only at the end) is removed on ingest. To change the settings of the Ingest MPEG fields, see the
“Configuring Ingest Tuning” section on page 4-17 .
All servers
Vault
Vault
Vault
Streamer, ISV
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-61
Chapter 4 Configuring the CDS
Server Level Configuration
Table 4-21 Server Setup Fields (continued)
Field
Streamer Is
Cache
Description
If Streamer Is Cache is enabled, the Streamer can be used as a possible cache-fill source by a Streamer in a different Stream Group. All Stream Groups that have at least one
Streamer with Streamer is Cache enabled are displayed on the Stream to Cache Map page, where the Stream Group can be selected as a possible cache-fill source and given a preference. Only the Streamers with Streamer Is Cache enabled are used as possible cache-fill sources. The protocol used for cache-fill responses from Streamers is always
CCP. For more information, see the
“Mapping Stream Groups to Cache-Fill Sources” section on page 4-39
.
Server Type
Streamer
Cache Group Information
Cache Group
Cache Group ID
These fields display the Cache Group Name and Cache Group ID the Caching Node is a member of. The Cache Group Name is informational only. To configure Cache Groups, see the
“Configuring Cache Groups” section on page 4-36 .
Vault Group Information
Vault Group
Vault Group ID
These fields display the Vault Group Name and Vault Group ID the Vault is a member of.
The Vault Group Name is informational only. To configure Vault Groups, see the
“Configuring Vault Groups” section on page 4-33 .
Caching Node
Vault
Jumbo Frames Support
Stream Jumbo
Frames
By default, jumbo frames are disabled on stream interfaces. In this case, stream traffic adheres to standard frames, which have a maximum frame size of 1500 bytes.
Streamer, ISV
Cache Jumbo
Frames
If jumbo frames are enabled, you need to make sure that your switch is configured to support jumbo frames. The jumbo frame size must be set, at a minimum, to 8192 bytes.
By default, jumbo frames are disabled on cache interfaces. In this case, cache traffic adheres to standard frames, which have a maximum frame size of 1500 bytes.
All servers
Vault Mirror
Copies
Vault Local
Copies
If jumbo frames are enabled, you need to make sure that your switch is configured to support jumbo frames to be able to communicate across the cache interfaces. The jumbo frame size must be set, at a minimum, to 8192 bytes.
Server Status
Server Offload Server Offload shows the current offload status of the server. When Server Offload is enabled, the server is configured to reject new provisioning. Server offload is typically enabled when system maintenance needs to be performed, or when a server needs to be removed from service. For more information, see the
“Offloading a Server” section on page 7-6
.
Choose the number of copies from the drop-down list that ensures there is at least one copy of the content at each site. For example, if there are two different sites, each with two
Vaults, set the Vault Mirror Copies to 3.
From the drop-down list, choose the number of copies of content that are stored on this server.
All servers
Vault, ISV
Vault, ISV
4-62
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
Server Level Configuration
Table 4-21 Server Setup Fields (continued)
Field Description
Transport, Cache, and HTTP IP Packets
Server Type
Transport
Differentiated
Services Code
Point
–and–
Differentiated Services Code Point (DSCP) uses six bits of the DiffServ field, which was originally the ToS octet, to mark all outgoing packets with a specific DSCP value. Cache or transport traffic may require certain forwarding behavior, known as the per-hop behavior (PHB), which is specified in the DSCP. The network gives priority to marked traffic. Generally, the lower number has lower priority and the higher number has higher priority. The valid entries are 0 to 63.
Cache
Differentiated
Services Code
Point
DSCP is set separately for cache and transport interfaces.
Note
DSCP can also be set for HTTP Streamers when HTTP is selected as the cache-fill protocol for VVI on the CDSM Setup page.
Cache Priority From the Cache Priority drop-down list, choose an AF class. For more information, see the
“Configuring QoS Settings” section on page 4-65 .
All servers
All servers
FTP Out Settings
FTP Out
Interface
FTP Out
Bandwidth
FTP out interface determines whether the management interface or the ingest interface is used for FTP pulls and FTP pushes. It is also used for the ISA 1.5 FTP Out feature.
Enter the maximum bandwidth (in Mbps) allowed for FTP functionality. Valid entries are
0 to 1000.
FTP Out
Sessions
Enter the maximum number of FTP out sessions allowed. The range is from 1 to 10.
Management Interface
Vault, ISV
Vault, ISV
Vault, ISV
Management IP IP address of the management interface on this server.
Gateway
Subnet Mask
FTP Listener
IP address of the gateway to the network.
Subnet mask that defines the subnetwork for this server.
Choose either the Management interface or the Ingest interface as the FTP listener. The
FTP listener selected determines which interface is used for FTP pulls or FTP pushes.
Ingest Interface
Ingest IP IP address of the ingest interface on this server. The ingest IP address is used to establish connectivity to the content provider system.
Subnet mask that defines the subnetwork for this interface.
Ingest Subnet
Mask
Locate Interface
Locate Interface
IP
IP address for this interface. The Locate Interface is used by the Locate Port service for communications with third-party streamers that use HTTP to communicate.
Locate Port Port number used for communication with HTTP Streamers. CCP Streamers do not use the Locate Port; instead, they load-balance locate requests across fill sources. For more information on HTTP Streamers and CCP Streamers, see the
“HTTP Streamers” section on page 2-9
.
General Interface
IP
Subnet Mask
IP address for this interface.
Subnet mask that defines the subnetwork for this interface.
All servers
All servers
All servers
Vault, ISV
Vault, ISV
Vault, ISV
Caching Node
Caching Node
All servers
All servers
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-63
Chapter 4 Configuring the CDS
Server Level Configuration
Table 4-21 Server Setup Fields (continued)
Field Description
Stream/Cache Interface
Source IP IP address for this interface. The IP address set for this interface overrides the default
Source IP setting.
If you are using Layer 3 communication among Vaults, Caching Nodes, and Streamers, each cache or stream/cache interface must have an IP address.
If you are using Layer 2 communication among Vaults , Caching Nodes, and Streamers,
IP addresses for cache and stream/cache interfaces are optional.
Transport Port This setting applies only to stream or stream/cache interfaces. This is the UDP port number for stream traffic. The port number set for this interface overrides the default transport port setting.
Cache Port UDP port number for cache traffic. The port number set for this interface overrides the default cache port setting.
Stream Control Interface
IP address for this interface. Stream Control
IP
Stream Control
Subnet
Subnet mask that defines the subnetwork for this interface.
Server Type
All servers
Streamer, ISV
All servers
Streamer, ISV
Streamer, ISV
Note
The Auto Populate Source IPs button is available when the first applicable interface (for example, the first stream interface) is configured with an IP address. Clicking Auto Populate
Source IPs automatically enters the next consecutive IP address as the Source IP for the next interface, and continues to populate all Source IPs until they are all filled. Any preexisting IP addresses in the Source IP fields are overwritten.
Note
To configure an unconfigured interface, click the click here link. The Interface Setup page is displayed. Choose the setting for the interface you want to configure and then click Submit. The
Server Setup page is displayed. Complete the interface configuration by filling in the fields as appropriate. See
for field descriptions.
Note
The Streamer can have a maximum of 12 interfaces configured for stream traffic simultaneously, with a maximum of 12 interfaces configured for cache traffic, or any variation of the two (for example, 8 stream interfaces and 6 cache interfaces). If an interface is configured for both cache and streaming traffic on a Streamer, priority is given to the higher-bandwidth stream traffic provided that cache traffic is able to transmit on other interfaces.
Step 4
Click Submit to save the settings.
To clear the fields and start over, click Reset.
4-64
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
Server Level Configuration
Configuring QoS Settings
There needs to be a dedicated Differentiated Services (DiffServ) Assured Forwarding (AF) class for the
CCP traffic. The Assured Forwarding PHB guarantees a certain amount of bandwidth to an AF class and allows access to extra bandwidth, if available. There are four AF classes, AF1x through AF4x. Within each class, there are three drop probabilities (low, medium, and high).
Note
The sum of all bandwidths configured for CCP traffic cannot exceed the bandwidth configured for the
AF classes reserved for CCP. CCP is used as the protocol among Vaults and Caching Nodes in a VVI that uses HTTP, and among all servers in a VVI that uses CCP and in all non-VVIs.
lists the four AF classes and the data types for each drop probability. To set the AF class on each server, use the Cache Priority drop-down list in the Server Setup page.
Table 4-22 AF Class Drop Probability Configured on Each CDS Server
AF1x
Class
AF2x
Class
AF3x
Class
AF4x
Class Data Types
AF11 AF21 AF31 AF41 The following data types are set to low drop probability:
•
•
•
Lost packet recovery for committed rate traffic (Vault or Caching
Node or Streamer to Vault or Caching Node or Streamer)
High-priority lost packet recovery for committed rate traffic
(Vault or Caching Node or Streamer to Vault or Caching Node or
Streamer) iGate and index file transmission (Vault or Caching Node to
Streamer)
•
First part of mirror data going to a new Vault (Vault to Vault)
•
Control traffic
AF12 AF22 AF32 AF42 Committed rate traffic (Vault or Caching Node or Streamer to Vault or
Caching Node or Streamer) is set for medium drop.
AF13 AF23 AF33 AF43 The following data types are set to high drop probability:
•
Remote smoothing traffic (Vault to Vault) and prefetched traffic
(Vault to Caching Node to Streamer)
•
•
•
•
Mirroring traffic for creating additional mirrored copies (Vault to
Vault)
Repair traffic that is recovering striped data lost because of a drive failure (Vault to Vault)
Mirroring of live ingest traffic (Vault to Vault)
Lost packet recovery of mirroring traffic (Vault to Vault)
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-65
Chapter 4 Configuring the CDS
Server Level Configuration
Configuring the Route Table
In earlier releases, the Route Table included a section called “Network Information,” which had the default gateway and local network for cache traffic, and the default gateway and local network for stream traffic. The same default gateway and local network could be used for both stream and cache traffic.
Interfaces were grouped into transport groups that could separate stream traffic to multiple transport networks. The transport mechanism did not work on cache-fill interfaces. The streaming network and cache-fill network were treated as distinct entities, which disallowed an interface to function as both a streaming interface and a cache-fill interface.
Release 2.1 introduced the ability to define multiple subnets on a server. Multiple subnets replace the transport group mechanism and applies equally to stream and cache-fill interfaces. With multiple subnets you have the ability to group interfaces into separate subnets. One of the uses for multiple subnets is to configure half of the interfaces on the server to connect to one switch or router, and the other half of the interfaces to connect to a different switch or router for redundancy. The Route Table page allows for multiple subnets for cache, stream, and stream/cache interfaces.
The Route Table page has three different route types:
•
CServer Source (written to the SubnetTable file)
•
•
CServer Destination (written to the RoutingTable file)
Stream Control (written to the Linux OS route table)
Each route type has a different function, and each route type is written to a different file on the CDS server.
Note
You cannot have intersecting subnets for any defined routes for CServer Source or CServer Destination.
CServer Source Route Type
When CServer Source is selected from the Route Type drop-down list, a subnet is defined and written to the SubnetTable file. Subnets can only be defined for stream, cache, or stream/cache interfaces.
Interfaces are defined on the Interface Setup page (
“Configuring the Interfaces,” page 4-55 ), and IP
addresses for the interfaces are set on the Server Setup page (
“Configuring the Servers,” page 4-58
).
shows an example of interfaces configured for multiple subnets on a Streamer.
Figure 4-31 Subnet Configuration Example on Streamer
4-66
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
Server Level Configuration
shows the possible configuration settings to use to define the subnets described in
Table 4-23 Route Table Settings for CServer Source
Subnet
Subnet 1
Subnet 2
Network
192.168.1.0
192.168.2.0
Subnet Mask
255.255.255.0
255.255.255.0
Gateway
192.168.1.1
192.168.2.1
Route Type
CServer Source
CServer Source
The Route Table entry for the subnet is defined by a network and subnet mask, and also includes a default gateway. ARP is applied for any data packets that have a destination IP address within the defined subnet, and the MAC address is returned. Any data packets outside the subnet are sent to the default gateway.
CServer Destination Route Type
When CServer Destination is selected from the Route Type drop-down list, an alternate gateway for a destination subnet (based on the Network and Subnet Mask fields) is defined and written to the
RoutingTable file. The alternate gateway is used whenever the destination IP address of the data packet falls within the destination subnet defined with the Route Type of CServer Destination.
Stream Control Route Type
When Stream Control is selected from the Route Type drop-down list, a subnet and default gateway is defined for all stream control traffic, and the information is written to the Linux OS routing table file.
The Stream Control route type is available only when one of the interfaces is set to Stream Control in
the Interface Setup page. See the “Configuring the Interfaces” section on page 4-55
for more information. The Linux OS routing table file is also used to store route information for the ingest and management interfaces.
Note
After being upgraded to Release 2.1 or later, any servers with incompatible routes are listed in red in the drop-down list. You can review the Route Table configuration for each of these servers, modify or delete the routes, and click Submit to apply the changes. The routes are converted to the Release 2.1 format and the server is listed in black. When all servers with incompatible routes are fixed, the warning message is removed and the entry in the system alarm drop-down list in the GUI banner is removed.
To configure a route, do the following:
Step 1
Choose Configure > Server Level > Route Tables. The Routing Table page is displayed (
).
Note
If Bulk Configuration is enabled, the Configuration File Location field is displayed, along with the Browse and Import buttons. To import a Bulk Configuration XML file, click Browse to locate the file, then Import to import the file. The status of the import is displayed in the left panel.
For information on enabling the Bulk Configuration feature, see the
“Bulk Configuration” section on page D-4
. For information about creating a Bulk Configuration file for QAM
Gateways, see the
“Creating Route Table Bulk Configuration Files” section on page B-5 .
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-67
Server Level Configuration
Figure 4-32 Route Table Page—Layer 3 Network
Chapter 4 Configuring the CDS
Step 2
Step 3
From the drop-down list, choose a server and click Display. Any configured routes are displayed.
Enter the route settings as appropriate. See
Table 4-24 for descriptions of the fields.
Table 4-24 Route Table Fields
Field Description
Network IP address of the network.
Subnet Mask The subnet mask of the network.
Gateway
Route Type
IP address of the next hop (primary datagram transmitter and receiver) along the route to the network.
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.
SOP
•
•
CServer Destination—Used to configure a default gateway for a specified destination subnetwork. Typically this is used to configure the default gateway to reach the QAM devices.
Stream Control— Used when configuring a subnet route for the stream control traffic. This option is available only on Streamers, and is available only when one of the interfaces on the Streamer is configured as a Stream Control interface. See the
“Configuring the Interfaces” section on page 4-55
for more information.
Note
Note
For multiple SOPs used for NGOD RTSP deployments, you must choose
CServer Source as the Route Type.
From the SOP drop-down list, choose an SOP. To create an SOP and for more information on SOPs, see the
“Configuring Source Output Ports” section on page 4-26 .
The SOP field is not shown in Figure 4-32
.
4-68
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
Step 4
Click Submit.
To reset the field, click Reset.
To delete a route, check the Delete check box and click Submit.
Server Level Configuration
Configuring the SNMP Agent
The SNMP Agent sets up SNMP on the CDS. For more information about SNMP on the CDS, see
Appendix C, “SNMP MIB and Trap Information.”
To configure the SNMP Agent settings for a new server, do the following:
Step 1
Choose Configure > Server Level > SNMP Agent. The SNMP Agent page is displayed (
).
Note
If Bulk Configuration is enabled, the Configuration File Location field is displayed, along with the Browse and Import buttons. To import a Bulk Configuration XML file, click Browse to locate the file, then Import to import the file. The status of the import is displayed in the left panel.
For information on enabling the Bulk Configuration feature, see the
“Bulk Configuration” section on page D-4
. For information about creating a Bulk Configuration file for QAM
Gateways, see the
“Creating SNMP Agent Bulk Configuration Files” section on page B-6 .
Figure 4-33 SNMP Agent Page
OL-22792-01
Step 2
Step 3
Choose the IP address of the server from the drop-down list and click Display.
Enter the settings as appropriate. The fields are described in
.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-69
Chapter 4 Configuring the CDS
Server Level Configuration
Table 4-25 SNMP Agent Fields
Field
SNMP Contact
Description
Specify a name used to identify the point of contact for this server. You may specify a name with up to 64 characters.
SNMP Location Specify the location of the server. You may enter a name with up to 64 characters.
Community Name Enter a community string that will have access to this server through SNMP.
Permissions The permissions for the community are:
•
•
read-only read/write
Trap Station
Version
The default is read/write.
If you do not choose a permission setting for a community you are adding, read/write privileges are applied.
The IP address or Fully Qualified Domain Name (FQDN) of a network management station.
The SNMP versions supported in the CDSM are:
•
v1
•
•
v2 v2-inform
SNMP v2-inform sends a message received to the NMS upon receiving an NMS message.
Note
There is no default for the SNMP version. If you do not choose an SNMP version for a trap station you are adding, SNMP communication is not successful to that station.
Step 4
Step 5
Click Submit to save the settings.
To clear the fields and start over, click Reset.
To add another SNMP community or SNMP station, fill in the appropriate fields and click Submit.
To edit the SNMP information, choose the IP address of the server from the drop-down list, edit the fields, and click Submit.
The SNMP page allows for multiple entries of SNMP communities and stations. If you want to delete an SNMP community or station, check the Delete check box associated with the entry and click Submit.
Note
The Cisco TV CDS MIBs are available for download at the bottom of the SNMP Agent page.
4-70
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
Configuring the Server Level DNS
The Server DNS page is used to up to 16 domain suffixes and 16 DNS servers.
Server Level Configuration
Note
If you are upgrading the TV CDS software to Release 2.3 from Release 2.0 or an earlier release, the system prompts you to Submit any settings that have previous domain suffixes to populate the new DNS database structure.
To configure the DNS settings for a server, do the following:
Step 1
Choose Configure > Server Level > Server DNS. The Server DNS page is displayed ( Figure 4-34
).
Note
If Bulk Configuration is enabled, the Configuration File Location field is displayed, along with the Browse and Import buttons. To import a Bulk Configuration XML file, click Browse to locate the file, then Import to import the file. The status of the import is displayed in the left panel.
For information on enabling the Bulk Configuration feature, see the
“Bulk Configuration” section on page D-4
. For information about creating a Bulk Configuration file for QAM
Gateways, see the
“Creating DNS Server Bulk Configuration Files” section on page B-7
.
Figure 4-34 Server DNS Page
OL-22792-01
Step 2
Choose the IP address of the server from the drop-down list and click Display.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-71
Chapter 4 Configuring the CDS
Server Level Configuration
Step 3
Enter the DNS binding Server Level settings as appropriate. See
Table 4-26 for descriptions of the DNS
binding fields.
Table 4-26 DNS Binding Fields
Field
New Domain
Suffix
Description
Specify, if applicable, the internal domain that is used to fully qualify an unqualified hostname. For example, if you are using OpenStream as the BMS, specify a subdomain consistent with what OpenStream is using, for example, bms.n2bb.com. Accordingly, unqualified hostnames used in CORBA transactions, such as contentstore, resolve correctly to contentstore.bms.n2bb.com.
New DNS Server IP address of the DNS server.
Step 4
Click Submit.
To clear the fields and start over, click Reset.
To delete the DNS settings, check the Delete check box and click Delete Entry.
Configuring the Server Level NTP
The NTP Server page is used to configure up to 16 NTP servers. The clocks on all CDS servers (Vault,
Streamer, and Caching Node) and the CDSM and VVIM in a CDS must be synchronized in order to retrieve the statistics on to the CDSM and VVIM.
To configure the NTP settings for a server, do the following:
Step 1
Choose Configure > Server Level > NTP Server. The NTP Server page is displayed.
Note
If Bulk Configuration is enabled, the Configuration File Location field is displayed, along with the Browse and Import buttons. To import a Bulk Configuration XML file, click Browse to locate the file, then Import to import the file. The status of the import is displayed in the left panel.
For information on enabling the Bulk Configuration feature, see the
Gateways, see the
“Creating NTP Server Bulk Configuration Files” section on page B-8
.
Step 2
Step 3
Step 4
Choose the IP address of the server from the drop-down list and click Display.
In the New NTP Server field, enter the IP address of the NTP server.
Click Submit.
To clear the fields and start over, click Reset.
To delete the NTP settings, check the Delete check box and click Delete Entry.
4-72
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
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.
The following are examples of the command used to set UTC and several different US time zones:
•
UTC option:
ln -sf /usr/share/zoneinfo/UTC /etc/localtime
•
EST option:
ln -sf /usr/share/zoneinfo/US/Eastern /etc/localtime
•
Central option:
ln -sf /usr/share/zoneinfo/US/Central /etc/localtime
•
Mountain option:
ln -sf /usr/share/zoneinfo/US/Mountain /etc/localtime
•
Pacific option:
ln -sf /usr/share/zoneinfo/US/Pacific /etc/localtime
Find the time zone for your specific location in the /usr/share/zoneinfo directory.
Configuring the NTP Server on the CDSM and VVIM
Configuring the NTP server on the CDSM or VVIM involves the following:
1.
Adding the NTP servers to the /etc/ntp.conf file
2.
3.
4.
5.
Setting the run levels for the Network Time Protocol daemon (ntpd)
Setting the time zone
Setting the server date and time
Starting the NTP service
6.
7.
Synchronizing the server clock with the NTP server
Synchronizing the hardware clock on the server
Specific NTP configuration details should be obtained from your system administrator to add the NTP servers to the /etc/ntp.conf file.
To setup the NTP server on the CDSM or VVIM, do the following:
Step 1
Step 2
Log in to the CDSM or VVIM as root.
Set the run levels for the NTP service.
# chkconfig --level 2345 ntpd on
To check the run level settings, enter the following command:
# chkconfig --list ntpd
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01 4-73
Chapter 4 Configuring the CDS
Server Level Configuration
Step 3
Step 4
Step 5
Step 6
You will see the following: ntpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
Stop the ntpd service.
# service ntpd stop
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.
Set the system date and time to a date and time close to the NTP server date and time by entering the
date -s command, for example:
# date -s "16:55:30 Nov 7, 2010"
Synchronize the server clock to the NTP server.
# ntpd -q
Note
If the system clock is off by a significant amount, the command takes a considerable amount of time to return.
Step 7
Step 8
Start the ntpd service.
# service ntpd start
Synchronize the hardware clock.
# /sbin/hwclock --systohc
Step 9
Check the NTP synchronization.
# ntpq -p
Step 10
Reboot the CDSM or VVIM.
# init 6
4-74
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
Server Level Configuration
Configuring RTSP Setup
Real Time Streaming Protocol (RTSP) setup involves different parameters based on the RTSP deployment that was specified during the initial installation of the CDS.
describes each type of deployment.
Table 4-27 RTSP Deployment
Environment
Motorola
IPTV
Scientific Atlanta
RTSP
Deployment
Configuration Description
RTSP
IPTV
DSM-CC
NGOD (Motorola) NGOD
Quative
EventIS
Quative
EventIS
Streamer acts as the RTSP client and the backoffice acts as the RTSP server.
IPTV uses multicasting with Internet Group Management Protocol (IGMP) version 2 for live television broadcasts and RTSP for on-demand programs.
Streamer acts as the RTSP server and the backoffice acts as the RTSP client.
The Next Generation On Demand (NGOD) approach uses DSM-CC messaging in a
Motorola environment.
The STB communicates with the backoffice to create a VOD session. Upon completion, the STB creates an RTSP session with the Streamers. The Streamer acts as an RTSP server and is responsible for accepting the request from the STB.
The STB communicates with the backoffice to initiate a purchase transaction and generate an entitlement ID. The STB then initiates an RTSP session with the Streamer.
The Streamer authenticates the entitlement ID with the backoffice and allocates stream resources.
Cable and IPTV Cisco
The Eventis deployment with “on vpath” is selected when both session and stream control messages go directly to the RTSP server from the STB. The EventIS deployment with “off vpath” is selected when control messages go through the backoffice before reaching the RTSP server, while the stream control messages go directly to the RTSP server.
Cisco RTSP defined protocol that supports both IPTV and cable STBs. Uses “on vpath” communication.
RTSP Deployment
To configure the RTSP settings, do the following:
Step 1
Choose Configure > Server Level > RTSP Setup. The RTSP Setup page is displayed.
Note
If Bulk Configuration is enabled, the Configuration File Location field is displayed, along with the Browse and Import buttons. To import a Bulk Configuration XML file, click Browse to locate the file, then Import to import the file. The status of the import is displayed in the left panel.
For information on enabling the Bulk Configuration feature, see the
“Bulk Configuration” section on page D-4
. For information about creating a Bulk Configuration file for QAM
Gateways, see the
“Creating RTSP Setup Bulk Configuration Files” section on page B-10
.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-75
Chapter 4 Configuring the CDS
Server Level Configuration
Step 2
From the Streamer Select drop-down list, choose a Streamer IP address and click Display. The RTSP settings for the specified server are displayed (
Figure 4-35 RTSP Setup Page for RTSP Deployment
Step 3
Enter the RTSP settings as appropriate.
describes each field and lists the associated RTSP deployment.
Note
If you change any of the RTSP Setup settings, you must resubmit the Control/Setup IP page. For more information, see the
“Configuring the Control and Setup IPs” section on page 4-42 .
Table 4-28
Looping Session
Timeout
Session Inactivity
Timeout
RTSP Fields for All Deployment
Field
Master Streaming IP
Description
Informational only. The IP address of the master
Streamer. To configure the Master Streaming IP address, see the
“Configuring the Control and Setup
.
RTSP Deployment
All
Activity timeout value for looping streams (carousels).
If a GET_PARAMETER request (heartbeat) is received from the backoffice within the specified timeout period, the looping session remains active. If not, the looping session is torn down.
RTSP
The default is 240000 milliseconds (4 minutes).
Timeout value for tearing down a session. The default is
360000 milliseconds (6 minutes). If the Session
Inactivity Timeout is set to zero (0), the session liveness is not checked.
RTSP, NGOD,
IPTV, Quative,
EventIS, Cisco
4-76
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
Server Level Configuration
Table 4-28 RTSP Fields for All Deployment (continued)
Field
Callback Server IP
Callback Server Port UDP port number of the callback server.
Backoffice Timeout Timeout value for closing a connection to the backoffice. If a message is not received from the backoffice within the time specified in the Backoffice
Timeout, the TCP connection is closed. Setting the
Backoffice Timeout to zero (0) is the same as disabling it and the connection is not closed.
RTSP Server IP
RTSP Server Port
Authentication
Manager IP
1
IP address of the server that communicates with this
Streamer using RTSP.
TCP port number the RTSP server is listening on for communication with this Streamer.
Quative
DSM-CC, RTSP,
NGOD, Quative,
Cisco
DSM-CC, RTSP,
NGOD, Quative
DSM-CC, RTSP,
NGOD, Quative
Authentication Manager resides on the master Streamer.
Typically, the Authentication Manager IP address is the same as that of the master Streamer. This field is only informational. To modify this field, see the
“Configuring the Authentication Manager” section on page 4-15 .
EventIS, Cisco
Authentication
Manager Port
Description
IP address of the callback server. The CDS sends announce messages to the callback server whenever an
RTSP session is torn down and released by the RTSP server. Announce messages are sent for both normal
(STB initiated) and abnormal (timeout) terminations.
RTSP Deployment
Quative
Bandwidth Manager
IP
Authentication Manager port number is determined by the properties specifications of the Authentication
Manager. If you need to change the port number, contact
Cisco technical support. This field is only informational. If you must modify this field, see the
“Configuring the Authentication Manager” section on page 4-15 . The default is 7792.
EventIS, Cisco
Bandwidth Manager resides on the master Streamer.
Typically, the Bandwidth Manager IP address is the same as that of the master Streamer. If the Bandwidth
Manager IP address is set on the Bandwidth Manager page, then this field is only informational and if you must modify this field, see the
Bandwidth Manager” section on page 4-10 . If the
Bandwidth Manager IP address on the Bandwidth
Manager page is set to an asterisk (*) or 0.0.0.0, then you must enter the IP address for the Bandwidth
Manager in this field for each Streamer.
EventIS on vpath
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-77
Chapter 4 Configuring the CDS
Server Level Configuration
Table 4-28 RTSP Fields for All Deployment (continued)
Field
Bandwidth Manager
Port
Backup Bandwidth
Manager IP
Backup Bandwidth
Manager Port
Session Resource
Manager IP (or Server
IP)
Session Resource
Manager Port (or
Server Port)
Backup Session
Resource Manager IP
Backup Session
Resource Manager
Port
Stream Control IP
Description RTSP Deployment
Bandwidth Manager port number default is 7791. This port number is determined by the configuration settings in the Bandwidth Manager. If the Bandwidth Manager
IP address is set on the Bandwidth Manager page, then this field is only informational and if you must modify this field, see the
Manager” section on page 4-10 . If the Bandwidth
Manager IP address on the Bandwidth Manager page is set to an asterisk (*) or 0.0.0.0, then you must enter the port number for the Bandwidth Manager in this field for each Streamer.
EventIS on vpath
IP address of the network interface card (NIC) you want the Bandwidth Manager to bind to in case the primary
Bandwidth Manager IP and port fail.
EventIS on vpath
Port number to listen on for incoming connections from the RTSP server. The default is 7791. The minimum port number you can allocate is 150. The maximum port number is 60000.
EventIS on vpath
EventIS off vpath,
Cisco
IP address used by the backoffice or Session Resource
Manager (SRM) for communication of session control requests to the CDS RTSP server.
Port number used by the backoffice or SRM for communication of session control requests to the CDS
RTSP server.
EventIS off vpath,
Cisco
IP address of the network interface card (NIC) you want the SRM to bind to in case the primary SRM IP and port fail.
Cisco
Port number you want the SRM to use in case the primary SRM IP and port fail.
Cisco
Stream Control Port
Reconnect IP
Reconnect Port
IP address used by the STB for communication of trick-mode requests to the CDS RTSP server. This does not have to be the same IP address as the Control IP.
Port number used by the STB for communication of trick-mode requests to the CDS RTSP server.
EventIS off vpath
EventIS off vpath
Only for nABLE Motorola environments. The IP address on the Streamer used to receive the requests to reconnect to the backoffice server. After a connection has been established with the backoffice for RTSP communication, sometimes the backoffice sends a request to reconnect.
RTSP
Only for nABLE Motorola environments. The TCP port number on the Streamer used to receive the requests to reconnect.
RTSP
4-78
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
Server Level Configuration
Table 4-28 RTSP Fields for All Deployment (continued)
Field
LSCP Listener IP
LSCP Listener Port
LSCP Response Pad
Component Name
Max History
Log Level
Maintenance Mode
Description
IP address on the Streamer used to receive LSCP requests.
TCP port number on the Streamer that is listening for
LSCP commands from the set-top box. The default is
9000.
When LSCP Response Padding is enabled, three blank bytes are added to the end of the LSCP response. The default is disabled.
RTSP Deployment
DSM-CC, NGOD
DSM-CC, NGOD
DSM-CC, NGOD
Component name is the name of the master Streamer that is registered with the DNS server. This is a critical communication component and must match the table entry in the DNS server.
Number of transactions (trick mode, play, pause) to maintain before sending the RTSP log message to the backoffice. If set to zero (0), the log message is not generated and the history is not returned upon session teardown.
From the Log Level drop-down list, choose one of the following:
NGOD
RTSP
All
•
•
Off—Logging is turned off.
Low—Logging messages are minimal in length (for example, RTSP message received).
•
High—Logging messages include all information concerning the event (for example, RTSP message with all syntax of the message).
From the Maintenance Mode drop-down list, choose one of the following:
All
•
•
On—All current sessions continue until they are finished and all new SETUP requests receive a
“Service Unavailable” response.
Off—The Streamer is available for new sessions and continues streaming current sessions.
1.
The Authentication Manager and Bandwidth Manager fields are not displayed if these features are not part of your deployment.
Step 4
Configure the clients that will communicate with the Streamer. The clients consist of the set-top boxes, which typically require only one client definition.
The client configuration is displayed in a delimited string format:
1)rtsp | 3636 | 3636 | 65535 | quative | parameters | TCP
In this format, rtsp is the deployment, 3636 is the receive port on the Streamer and the receive port on the client, 65535 is the receive buffer size, quative is the client model, parameters is the message payload type, and TCP is the transport protocol.
•
To edit an existing client, click Edit next to the client definition.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01 4-79
Server Level Configuration
•
•
To delete an existing client, click Delete next to the client definition.
To add a new client, click Add New Client.
Table 4-29 describes the fields for the client definitions.
Chapter 4 Configuring the CDS
Table 4-29
Field
Receive Port
Send Port
Receive Buffer
Model
Transport
Client Configuration Fields
Description
Port used for receiving messages from the client.
Port used to send messages to the client.
Receive buffer size, in bytes, for the listener socket. The receive buffer can be set to either 65535 for TCP transport or 512000 for UDP transport.
Quative and Cisco always uses TCP transport.
Client model type to use for communication with the client. The types are:
•
•
•
nCUBE
Digeo
NGOD
Myrio
•
•
•
Quative
EventIS
•
Cisco
A client model of nCUBE means the client uses RTSP with nCUBE syntax.
A Digeo client model uses Digeo syntax, and so on.
Transport protocol, either UDP or TCP, used for streaming. The transport protocol is always TCP for Quative and Cisco.
Note
If you change any of the RTSP Setup settings, you must resubmit the Control/Setup IP page. For more information, see the
“Configuring the Control and Setup IPs” section on page 4-42 .
Step 5
Click Submit.
To clear the fields and start over, click Reset.
4-80
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 4 Configuring the CDS
Server Level Configuration
Configuring FSI Setup
The File Service Interface (FSI) allows the backoffice to communicate file-related requests to the Vault.
These requests include ingesting content, preparation of content files (for example, trick mode creation), and distribution of the content.
To configure the FSI settings, do the following:
Step 1
Choose Configure > Server Level > FSI Setup. The FSI Setup page is displayed.
Note
If Bulk Configuration is enabled, the Configuration File Location field is displayed, along with the Browse and Import buttons. To import a Bulk Configuration XML file, click Browse to locate the file, then Import to import the file. The status of the import is displayed in the left panel.
For information on enabling the Bulk Configuration feature, see the
“Bulk Configuration” section on page D-4
. For information about creating a Bulk Configuration file for QAM
Gateways, see the
“Creating FSI Setup Bulk Configuration Files” section on page B-9
.
Step 2
From the Vault Select drop-down list, choose an IP address and click Display. The FSI settings for the specified server are displayed (
).
Figure 4-36 FSI Setup Page
OL-22792-01
Step 3
Enter the FSI settings as appropriate. See
Table 4-30 for descriptions of the fields.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
4-81
Chapter 4 Configuring the CDS
Server Level Configuration
Table 4-30 FSI Fields
Field
FSI IP Address
FSI Server Port
Description
IP address of the Vault used in FSI communications with the backoffice. The recommended configuration is to enter 0.0.0.0 to allow all incoming IP interfaces on the Vault to be used for FSI communications.
Port number on the Vault used in FSI communications with the backoffice. The default is 20004.
FTP Client Port Port used by FSI communications when connecting to the catcher, or other FTP server, to pull in content, and when the FTP port is not specified in the ingest
URL. The default is 21.
FTP Out Server
Port port used by FSI communications for egress (FTP out pulls) from the Vault. The default is 21.
FTP Out Login TTL Time, in seconds, an FTP client has to connect and log in to the Vault to perform an FTP out pull with a temporary login. The default is 60.
Log Level From the Log Level drop-down list, choose one of the following:
FSI Content Root
Path
Async. Callback
URL
Off—Logging is turned off.
Low—Logging messages are minimal in length (for example, RTSP message received).
High—Logging messages include all information concerning the event (for example, RTSP message with all syntax of the message).
Root directory used to store MPEG content files on the Vault. This field is used in both nABLE and NGOD RTSP deployments. The default is /files.
For IPTV deployments only. The asynchronous callback URL is where the recording completion notification is sent when a scheduled recording completes its capture. This URL is basically used to tell the client the recording is completed.
Step 4
Click Submit.
To clear the fields and start over, click Reset.
4-82
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
C H A P T E R
5
System Monitoring
The CDSM provides tools that can be used for system monitoring and system diagnostics. The topics covered in this chapter include:
•
System Level Monitoring, page 5-1
•
•
•
•
•
Monitoring Content Objects, page 5-4
Monitoring Stream Objects, page 5-13
Array Level Monitoring, page 5-24
Server Level Monitoring, page 5-25
Recommended Monitoring Schedule, page 5-33
Note
If Virtual Video Infrastructure (VVI) with split-domain management is enabled, the CDSM pages associated with the Vaults and Caching Nodes display only on the VVI Manager (VVIM), and the CDSM pages associated with the Streamers display only on the Stream Manager. For more information, see the
“Virtual Video Infrastructure” section on page D-6 .
System Level Monitoring
The System Level Monitoring pages provide an overall view of the health and activity of the CDS. The
System Level links are:
•
•
To view the System Level Monitoring pages, click Monitor from any page in the CDSM, and then click
System Health or System Snapshot, as appropriate.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
5-1 OL-22792-01
Chapter 5 System Monitoring
System Level Monitoring
System Health
The System Health page provides a top-level view of the overall health of each group in the CDS and each server in each group. Any time there is an alarmed event, an alarm is displayed in the CDSM banner.
The Alarms menu is displayed when you roll your mouse over the alarm icon. See
the alarmed event in the Alarm menu takes you to the CDSM page that has more information. For
, clicking System health problems reported takes you to the System Health page.
Figure 5-1 CDSM Banner—System Health Alarm
To view the System Health page, choose Monitor > System Health. See Figure 5-2
.
Figure 5-2 System Health Page
The colored boxes on the System Health Monitor page have the following meaning:
•
•
Green—All components are operating.
Yellow—Some components are not operational.
•
Red—All components have failed.
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
for more information.
5-2
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 5 System Monitoring
System Level Monitoring
•
•
•
When you click the Disk check box you are taken to the Disk Monitor page. See the
“Disk Monitor” section on page 5-25 for more information.
When you click the Services check box you are taken to the Services Monitor page. See the
“Services Monitor” section on page 5-32 for more information.
When you click the Vitals check box you are taken to the Server Vitals Monitor page. See the
“Server Vitals” section on page 5-29 for more information.
Note
The Vitals column is displayed only if the CDSM Health Monitor feature is enabled. For more information, see the
“CDSM or VVIM Health Monitoring” section on page D-9
.
The time shown at the bottom of the left-panel menu is not the current time, but rather the CDSM time that is used for the health status and monitoring the system.
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 System Snapshot Page
OL-22792-01
In a VVI, the Stream Manager only displays the stream-related date and the VVIM only displays the bandwidth and content-related data.
describes the information displayed on the System Snapshot page.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
5-3
Chapter 5 System Monitoring
Monitoring Content Objects
Table 5-1 System Snapshot Page
Field Description
Data Refresh Rate How often the information is refreshed. The default is 10 seconds. The range is
10 to 300. All field values that are updated, based on the refresh rate, are initially shown in a green colored font.
Total Streams
HD Streams
SD Streams
Total number of stream objects the CDS is currently streaming.
Total number of high-definition stream objects the CDS is currently streaming.
Total number of standard-definition stream objects the CDS is currently streaming.
Total bandwidth, in megabits, used for active streams.
Active Stream
Bandwidth
1
Active Fill
Bandwidth
Total Content
Total bandwidth, in megabits, used for caching content among Vaults and
Streamers.
Total number of content objects currently stored, ingested, provisioned for ingest, and failed ingest on the CDS.
Active Ingests Total number of content objects currently being ingested on the CDS.
Completed Ingests Total number of content objects currently stored on the CDS.
Prov. (push) Ingests Total number of content objects that have been requested for ingestion, but have not yet begun active ingestion.
Failed Ingests Total number of content objects that failed to complete the ingest process.
Temp Out of
Service
Total Disk
Disk Used
Disk Available
Total number of content objects that are in a Temp Out of Service state. The backoffice may put a content object into this state for a certain amount of time.
Total disk space, in bytes, on the CDS.
Total used disk space, in bytes, on the CDS.
Total available disk space, in bytes, on the CDS.
1.
Active Stream Bandwidth and Active Fill Bandwidth values are only accurate if the clocks on the CDS servers are synchronized with the CDSM.
Monitoring Content Objects
The content objects links on the Monitor System Level page provides information on the status of content ingests.
Table 5-2 describes the different ingest states that are monitored.
Table 5-2 Monitored Ingest States
Completed Ingests
Active Ingests
Package Expiration
Publish Failures
Lists content objects that have been fully ingested.
Lists content objects that are in the process of being ingested.
Lists Package Expiration information, including expiration dates and all associated metadata. Allows for package expiration adjustments.
Lists the packages that were not able to be published to the backoffice and provides a mechanism to republish the package.
5-4
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 5 System Monitoring
Monitoring Content Objects
In a VVI with split-domain management, the Stream Manager displays the following completed ingest details: Content Name, File Size, Rate, Create Time, and Last Modified. For the other completed ingests fields, see the same content asset on the VVIM.
Ingests
Viewing Completed Ingests is a different procedure than viewing the other types of monitored ingests.
This section contains the following topics:
•
•
Viewing Completed Ingests
To view the details of completed ingests, do the following:
Step 1
Step 2
Choose Monitor > System Level > Completed Ingests.
The following methods can be used to display a list of content objects:
•
Enter the first character of the content object name in the text box. A drop-down list of content objects is displayed. If there are more than 25 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. You can continue to enter characters to reduce the list (you can also delete characters to increase the list) and at any point click Display. After you click Display, a list of content objects is displayed that has the same beginning characters that you entered in the text box.
•
•
In the Browse Content box, click one of the characters. A list of content objects that begin with that character is displayed.
In the Quick Lists box, the following options are offered:
–
–
Most Recent Ingests (max 100)—Lists the 100 most recent completed ingests sorted by ingest date.
List All Contents—Lists all completed ingests sorted by content name. This option is available only if the number of completed ingests is less than 100.
–
–
Content Status—Lists status information for each completed ingest.
Content Status (Damaged Only)—Lists status information only for damaged completed ingests.
After you perform one of these methods, a list is displayed. The list of content objects can span several pages. To view the next page, click the page number.
Figure 5-4 shows an example of the Completed Ingests list generated with any of the methods, except
the Content Status options. The content names and the date they were ingested are displayed.
Note
In a VVI, the Stream Manager displays the Streamed Content page, which has a subset of the information displayed on the Completed Ingest page.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
5-5
Monitoring Content Objects
Figure 5-4 Completed Ingests List
Chapter 5 System Monitoring
shows an example of the Content Status information that displays when you choose Content
Status or Content Status (Damaged Only).
5-6
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 5 System Monitoring
Figure 5-5 Completed Ingests List—Content Status
Monitoring Content Objects
OL-22792-01
Table 5-3
Field
Content Name
Duration
GOID
Version
Server ID
Status
Content Status Fields
Description
Name of the content.
Duration of the content.
Global Object ID for the content object associated with the content.
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. The value, redo, is an undo file. When the content is ingested, if there are any changes made during the ingest, the changes are recorded in the redo file. If the content is sent by using FTP
Out, the changes are undone and the original file is sent.
Server ID of the Vault that is storing the content object.
Status of the storing process of the content object, either complete or partial.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
5-7
Chapter 5 System Monitoring
Monitoring Content Objects
Step 3
To view the details of a content object, click the content name. The Ingest Details are displayed
(
Figure 5-6 Completed Ingests—Ingest Details
Table 5-4 describes the content object details that are displayed for each type of ingest.
5-8
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 5 System Monitoring
Monitoring Content Objects
Table 5-4 Content Object Details
Field
Content Name
Factory ID
Ingest IP
File Size
Rate
Create Time
Last Modified
Op State
Admin State
Push Provision
Description
Name of the content object.
Factory responsible for this content object.
IP address of the ingest interface on the Vault used to download the content.
File size, in bytes, of this content object.
Rate of ingest in bits per second (3750000 = 3.75 Mbps).
Time and date this content object was created.
Time and date this content object was last modified.
Operational state of this content object. The possible operational states are:
•
•
•
•
Created—Content is loading.
In Service—Content is available for streaming.
•
Out of Service—Content is not available for streaming.
Administrative state of this content object. The possible administrative states are:
Unprovisioned—Content is loading.
In Service—Content is available for streaming.
•
Out of Service—Content is not available for streaming.
Type of FTP provisioned. The provision types are:
•
FTP pull
Content Copies
Asset Ior
•
FTP push
These fields display the following information about the copies of the content:
Speed/Direction—The trick-mode speed and direction (fast forward or rewind).
Server ID—The server ID where the copy is stored.
Status—The status of the stored content.
Trick Speeds [1-8] Trick speeds 1 through 8 show the trick-mode speeds for this content object.
Full Content ID
Ior
1
URL
Full identification of this content object.
Interoperable Object Reference (IOR) for this content object.
Uniform Resource Locator (URL) address of the content has the following:
•
Protocol used (for example, FTP)
•
•
Username and password (for example, videolan:mpeg4ftp)
IP address of the content provider server (for example, 192.168.100.184)
•
Directory where the content is stored on the provider server (for example, videolan)
•
Name of the file (for example, long_encore_3.75.mpg)
Asset IOR associated with this content object.
1.
Not displayed in
.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
5-9
Chapter 5 System Monitoring
Monitoring Content Objects
Viewing Active Ingests
To view the details of active ingests, do the following:
Step 1
Step 2
Choose Monitor > System Level > Active.
Choose a content object from the drop-down list and click Display. The details of the content object are
displayed. Figure 5-6 on page 5-8
shows an example of the ingest details.
By typing the first character of the content object name, you can jump to that section of the list.
In addition, you can perform a text string search by typing the text string you want to search for in the
Search Ingests field and clicking Search. A list of content objects that contain the text string are listed.
To see the content object details, click the content object name listed. To return to the previous page without selecting a content object, click Back.
Table 5-4 on page 5-9 describes the content object details that are displayed for active ingests.
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
Step 2
Choose Monitor > Package Expiration. The Package Expiration page is displayed.
From the Available Packages drop-down list, choose a package and click Display. The Package
Expiration details are displayed.
By typing the first character of the package name, you can jump to that section of the list.
shows an example of the Package Expiration details.
5-10
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 5 System Monitoring
Figure 5-7 Package Expiration Page
Monitoring Content Objects
OL-22792-01
describes the package expiration details that are displayed.
Table 5-5 Package Expiration Details
Field Description
Package Name Name of the package.
License Expiration Date the package expires.
Additional Package
Window
Additional time added to the package.
Actual Package
Expiration
Actual Package Expiration is the License Expiration plus the Additional
Package Window.
Step 3
Step 4
To adjust the license expiration, enter the number of days (positive or negative) in the Adjust License
Expiration field and click Update.
The license expiration is adjusted by the number of days you entered. The Additional Package Window is not affected and is still applied to create the Actual Package Expiration.
In the Asset Details section, to view the metadata associated with the package expiration, click the plus sign (+) next to the metadata you want to view.
To delete a package, choose the package from the Available Packages drop-down list, click Display, and then click Delete in the Package Expiration Details section.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
5-11
Chapter 5 System Monitoring
Monitoring Content Objects
Publish Failures
Note
Publish Failures 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.
The Publish Failures page lists the packages that were not able to be published to the backoffice and provides a mechanism to republish the package.
To publish an unpublished package, or delete an unpublished package, do the following:
Step 1
Step 2
Choose Monitor > Publish Failures. The Publish Failures page is displayed.
From the Unpublished Packages drop-down list, choose a package and click Display. The Unpublished
Package details are displayed.
By typing the first character of the package name, you can jump to that section of the list.
shows an example of the Publish Failures details.
Figure 5-8 Publish Failures Page
Table 5-6 describes the publish failures details that are displayed.
Table 5-6 Publish Failures Details
Field
Package Name
Source URL
Target URL
Description
Name of the package.
Location of the original package information.
Location where to place the package information.
5-12
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 5 System Monitoring
Monitoring Stream Objects
Table 5-6
Field
Module Type
Creation Date
Publish Failures Details (continued)
Description
Internal identifier for what failed. In the example in
, the publishing of the package failed.
Date the database record was created for this failure.
Step 3
Step 4
In the Assets section, to view the metadata associated with the unpublished package, click the plus sign
(+) next to the metadata you want to view.
To restart the publishing process and set the creation date to today, click Publish.
To delete an unpublished package, click Delete.
Monitoring Stream Objects
The monitored stream objects consist of:
•
•
Stream Monitor
Step 1
Step 2
Choose Monitor > Stream Monitor. The Stream Monitor page is displayed.
The following methods can be used to display a a stream object or a list of stream objects:
•
Enter the first character of the session handle in the text box. A drop-down list of stream objects is displayed. If there are more than 25 objects that start with that first character you entered, you are prompted to continue entering the next character of the object name or choose one that is listed. You can continue to enter characters to reduce the list (you can also delete characters to increase the list) and at any point choose one. After you choose one, the stream details are displayed (
•
In the Quick Lists box, the following options are offered:
–
Most Recent 100—Lists the 100 most recent stream objects.
–
–
All Streams—Lists all streams. This option is available only if the number of streams is less than 100.
Destination IP, Destination Port, Client IP, Client Port—If you do not know the session handle, you can perform a text string search by selecting the field you want to search on, entering the text string in the Search String field, and clicking Search. A list of stream objects that contain the text string in the field you selected are listed. Click the linked field (session handle as seen in
) to see the stream monitor details for the selected object, or click
Back to return to the previous page.
After you perform one of these methods, a list is displayed. The list of stream objects can span several pages. To view the next page, click the page number.
Figure 5-9 shows an example of the stream object list generated by clicking Most Recent 100 or All
Streams. The Session IDs and the stream start time are displayed.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
5-13
Chapter 5 System Monitoring
Monitoring Stream Objects
The stream object list generated by entering the destination IP, destination port, client IP, or client port in the Quick List box, displays the session ID, stream start time, destination IP, destination port, client
IP, and client port.
Figure 5-9 Stream Monitor—Stream List
Step 3
To view the details of a stream object, click the session handle. The Stream Details are displayed.
shows an example of the stream object details.
5-14
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 5 System Monitoring
Figure 5-10 Stream Monitor—Stream Details
Monitoring Stream Objects
OL-22792-01
describes the stream details.
Table 5-7 Stream Details
Field
Session Handle
RTSP Session ID
Description
Internal unique identifier assigned to the stream session by the Streamer.
RTSP identifier of the stream session that is used in communications with the backoffice and set-top box.
External Session ID Session identifier generated by the backoffice.
Destination IP IP address used to receive the stream (for example, the QAM or set-top box).
Cisco TV CDS 2.3 RTSP Software Configuration Guide
5-15
Chapter 5 System Monitoring
Monitoring Stream Objects
Table 5-7 Stream Details (continued)
Field
Destination Port
Client IP
Client Port
Session Group ID
Client ID
Service Group
Service Area
Description
Port number used to receive the stream (for example, the QAM or set-top box).
IP address of the set-top box that requested the stream.
Set-top box port number used to send the stream request.
Identifier defined by the backoffice for a logical grouping of sessions.
Identifier of the client that is receiving the stream.
Service group used for this session.
Logical name that describes the service group, which is a logical grouping of subscribers.
Entitlement This is an identifier that specifies if this a valid SETUP request. This is used to pass back to the authentication server during the setup process. This is only used in a EventIS environment.
Allocated Bandwidth Bandwidth allocated for this stream session.
Current Operation Current set-top box operation. The possible operations are:
Operation Start
Stream State
LSCP Mode
Stream Looping
•
•
•
•
Fast Forward
Rewind
Start time of the currently active operation.
Stream state has the following possible values: playing, paused, stopped.
Valid LSCP modes are:
•
Normal Play
Paused
•
•
•
Open—The server is not transporting a media stream.
Pause—The server is not transporting a media stream.
Search transport—The server is searching for start NPT (normal play time). When at start NPT, it enters the Transport mode.
Transport—The server is transporting the media stream and pauses at the end of the stream. If scale is positive, indicating a forward direction, end of stream is the end of media. If scale is negative, indicating a reverse direction, end of stream is the beginning of media.
•
•
•
Transport pause—The server is transporting the media stream and pauses at stop NPT.
Search transport pause—The server is transporting the media stream and pauses at stop NPT.
Pause search transport—The server is transporting the media stream. It does so until stop NPT, and then transitions to search transport mode.
End of stream—The server is not transporting a media stream.
•
LSCP is not used in a Motorola environment. In an nABLE Motorola environment, the value is always 0.
This field indicates whether stream looping is turned on or off for this stream.
5-16
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 5 System Monitoring
Monitoring Stream Objects
Table 5-7
Field
From STB
Stream Node
Position
History
Stream Details (continued)
Description
If From STB has the value yes, then the set-top box created this session.
If From STB has the value no, then the backoffice created this session.
Logical node on the transport network used to stream the session to the STB.
The value is a three-digit number, with 000 being the default. In an nABLE
Motorola environment, the value is typically -1.
Current stream position. The position is the number of milliseconds from the beginning of the video in NPT format.
Current transaction (trick mode, play, pause) history of this stream session.
The Graph Stream button displays the trick-mode activity of the stream (
).
Note
If Trick Mode Capture is disabled, the Graph Stream is not displayed. For information on enabling the
Trick Mode Capture, see the
“Trick Mode Capture” section on page D-5 .
Figure 5-11 Stream Activity Report
OL-22792-01
To delete a stream object, display the object and click Delete.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
5-17
Chapter 5 System Monitoring
Monitoring Stream Objects
Stream Failures
To view the details of Failed Streams, do the following:
Step 1
Choose Monitor > Failed Streams. The Stream Failures page is displayed.
Each failed stream is listed by the date and time the stream failed, followed by the session ID of the failed stream.
Note
Stream Failure monitoring displays only the failed streams for the current day. To view past stream failures, see the
“Stream Failures” section on page 6-15
.
Step 2
From the Stream Failures drop-down list, choose the timestamp and session ID of the stream object and click Display. The stream failure details are displayed. See
To delete a failed stream, display the object and click Delete.
Figure 5-12 Stream Failures Page
5-18
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 5 System Monitoring
Monitoring Stream Objects
describes the stream failure details.
Table 5-8 Stream Failure Details
Field
Session ID
Failure Date
QAM IP
Service Group
Server ID
Description
Session ID of the failed stream.
Date and time the failure occurred.
IP address of the QAM device associated with the failure.
Service group associated with the failure.
Server responsible for streaming this stream object. To view the IP address associated with the Server ID, see the
“Configuring the Servers” section on page 4-58
.
Group ID
Failed Operation Operation that was taking place when the stream failed, for example, createStream,
LSCP Command(), or createServant, destroy. These are the measurement points or transactional states of the system at the time of the failure.
Failed Task
All servers that are part of the same CDS system (managed by one CDSM) have the same Group ID. This Group ID corresponds to the CDSM GUI array ID and should be unique across an enterprise.
describes the ID mapping between the
CDSM GUI and the CServer.
Failed task is the event category that provides the type of execution sequence that the call stack was currently in at the time of the failure. The list of the high-level categories are:
•
Tune In
•
Play Movie
Error Code
•
•
•
Load Application
Load Catalog
Eligibility Check
Select Subscription
•
•
•
Movie Setup
Movie Control
Movie Confirm
Purchase Confirm
•
•
•
Purchase Subscription
Select Movie
•
•
•
Purchase Log
Stop Movie
•
Purchase Check
•
Movie Release
Error code provides a description of the event that caused an error. See
for descriptions of the error codes.
lists the CDSM GUI ID names and maps them to the CServer names in the setupfile and
.arroyorc files.
Table 5-9 ID Names in the CDSM GUI and CServer Files
CDSM GUI ID Name
Array ID on the Array Name page
Group ID on the Server-Level pages
Stream Group ID on the Server Setup page
Cache Group ID on the Server Setup page
CServer Files ID Name
groupid groupid arrayid arrayid
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
5-19
Chapter 5 System Monitoring
Monitoring Stream Objects
Table 5-9 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
also lists errors in the network or network components.
Error Codes Table 5-10
Numeric Error Code Error Code
2024
2025
2026
2027
2036
2041
3006
6001
6002
6003
6004
6005
6006
6007
6008
6009
6010
6011
FTP_CONNECTION_FAILED
FTP_SERVER_BIND_FAILED
FTP_PUSH_TIMEOUT
FTP_QUIT_RECEIVED_DURING_INGEST
NOT_ENOUGH_QAM_BANDWIDTH
CONTENT_CAN_NOT_BE_LOCATED
SET_DESTINATION_FAILED
RTSP_REQUEST_INVALID
Description
Connection to FTP server failed.
FTP server can not bind to the port.
FTP push timeout (PASV is not served fast enough).
FTP server received QUIT request.
Not enough QAM bandwidth.
Content is not found in the related content stores.
Failed while setting destination of the stream.
RTSP request was not understood by the RTSP server. Either the syntax is incorrect of the method is unknown.
SESSION_NOT_FOUND
RTSP_METHOD_NOT_VALID_IN_STATE
RTSP_RANGE_NOT_VALID
TRANSPORT_UNSUPPORTED
NO_DESTINATION_DEFINED
RTSP session ID could not be found in the RTSP server.
RTSP request is not valid for the current RTSP session state.
RTSP range header does not have valid values.
Transport header could not be parsed.
INTERNAL_SERVER_ERROR
Transport header does not have a stream destination value.
There was an internal server error during an RTSP request.
RTSP_SERVICE_UNAVAILABLE
UNSUPPORTED_RTSP_VERSION
RTSP service is unavailable.
RTSP version is not supported.
UNSUPPORTED_OPTION RTSP require header is not supported.
STREAMING_ERROR_READING_CONTENT There was an error reading the content in a stream.
Table 5-11 lists the error codes for errors that could occur during ingest or during trick-mode file
creation, which cause stream failures.
5-20
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 5 System Monitoring
Monitoring Stream Objects
Table 5-11 MPEG Error Codes
Numeric
Error
Code Error Code
8001
8002
8003
8004
TRICK_INGEST_NO_INGEST_OBJECTS
TRICK_INGEST_TOO_MANY_SPEEDS
TRICK_INGEST_NULL_INGEST_OBJECTS
Description
Ingest fails. Check available system memory.
Too many trick speeds. Change trick speed configuration.
Ingest fails. Check available system memory.
TRICK_INGEST_INVALID_SPEED_DENOMINATOR Ingest fails. Change trick speed configuration.
8005
8006
8007
8008
8009
TRICK_INGEST_INVALID_SPEED_LT_2X Ingest fails. Change trick speed configuration.
TRICK_INGEST_NULL_DERIVED_INGEST_OBJECTS Ingest fails. Check available system memory.
TRICK_RSDVR_DYNAMIC_TRICK_CREATION
_FAILS
RS-DVR trick-mode file creation fails. Change trick speed configuration.
TRICK_INGEST_CDN_AVC_UNSUPPORTED
TRICK_RSDVR_BAD_STREAM_TYPE
Do not attempt to ingest an Advanced Video Coding
(AVC) stream on a VVI system.
RS-DVR trick-mode file creation fails. Stream should already have failed ingest.
8010
8011
8012
8013
8014
8015
8016
8017
8018
8019
8020
8021
8022
8023
8024
8025
TRICK_INGEST_ABORTED
TRICK_INGEST_INSUFFICIENT_DATA
TRICK_INGEST_STREAM_TOO_BIG
TRICK_RSDVR_WRITE_OVERFLOW
General ingest failure. Check ingest feed.
Ingest fails. Check ingest feed.
Ingest fails. The limit is 162 GB or about 12 hours at a known bitrate.
RS-DVR trick-mode file creation fails. Check ingest feed.
Ingest fails. Check ingest feed.
Streaming rate may be incorrect. Check ingest feed.
TRICK_INGEST_VBR_UNSUPPORTED
TRICK_INGEST_RATE_FORCED
TRICK_INGEST_PAT_NOT_FOUND
TRICK_INGEST_DEFAULTING_PMT_PID
Program association table (PAT) not found. Check ingest feed.
Program map table (PMT) process ID (PID) not determined. Check ingest feed.
TRICK_INGEST_DEFAULTING_PROGRAM_NUMBER Program number not determined. Check ingest feed.
TRICK_INGEST_DEFAULTING_VIDEO_PID_AND_
TYPE
Video PID or type not determined. Check ingest feed.
TRICK_INGEST_BITRATE_INDETERMINATE
TRICK_INGEST_FIRST_PTS_NOT_FOUND
Bitrate cannot be determined. Check ingest feed or adjust ingest configuration parameters.
First presentation time stamp (PTS) not determined.
Check ingest feed.
TRICK_INGEST_CANNOT
DETERMINE_FRAMERATE
TRICK_INGEST_PMT_NOT_FOUND
Frame rate not determined. Check ingest feed.
TRICK_INGEST_MULTIPLE_VIDEO_PIDS
PMT not found. Check ingest feed.
Multiple video PIDs found. Check ingest feed.
TRICK_INGEST_PID_REPLACEMENT_CANCELLED PIDs could not be standardized. Check ingest feed.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
5-21
Chapter 5 System Monitoring
Monitoring Stream Objects
Table 5-11 MPEG Error Codes (continued)
Numeric
Error
Code Error Code
8026
8027
8028
8029
8030
8031
8032
8033
8034
8035
8036
8037
8038
8039
8040
8041
8042
8043
8044
8045
TRICK_INGEST_OVERFLOW
TRICK_INGEST_WRITE_ERROR
TRICK_INGEST_OVERFLOW_ON_RETRY
TRICK_INGEST_KNOBS_FAILURE
TRICK_INGEST_KNOBS_FAILURE_PAT_PMT
TRICK_INGEST_KNOBS_FAILURE_BITRATE
TRICK_INGEST_KNOBS_FAILURE
_DISCONTINUITIES
_COUNTERS
TRICK_INGEST_KNOBS_FAILURE_CONTINUITY
TRICK_INGEST_KNOBS_FAILURE_SYNC
Description
Ingest fails because of ring buffer overflow. Check ingest feed.
Ingest fails because of a 1x write problem. Check ingest feed.
Ingest fails even after a retry (ring buffer overflow).
Check ingest feed.
Ingest fails. Check ingest feed or adjust ingest configuration parameters.
Ingest fails. No PAT or PMT found. Check ingest feed or adjust ingest configuration parameters.
Ingest fails. Bitrate cannot be computed. Check ingest feed or adjust ingest configuration parameters.
Ingest fails. Too many discontinuities. Check ingest feed or adjust ingest configuration parameters.
Ingest fails. Too many continuity counter errors.
Check ingest feed or adjust ingest configuration parameters.
Ingest fails. Too many sync errors. Check ingest feed or adjust ingest configuration parameters.
TRICK_INGEST_KNOBS_FAILURE_SYNC_TIME
TRICK_INGEST_KNOBS_FAILURE_PIC_GAPS
TRICK_INGEST_HORIZONTAL_PIC_SIZE_EXCEEDS
_MAX
Ingest fails. Sync loss too long. Check ingest feed or adjust ingest configuration parameters.
Ingest fails. Too many picture gaps. Check ingest feed or adjust ingest configuration parameters.
TRICK_INGEST_KNOBS_FAILURE_PIC_GAP_TIME Ingest fails. Picture gap too long. Check ingest feed or adjust ingest configuration parameters.
TRICK_INGEST_SEQUENCE_HEADER_NOT_FOUND Ingest fails. Could not find a Sequence Header. Check ingest feed.
TRICK_INGEST_SPS_NOT_FOUND
TRICK_INGEST_CDN_SEQ_WRITE_FAILED
Ingest fails. Could not find an SPS. Check ingest feed.
Ingest fails because of a Sequence Header write error.
Check ingest feed.
TRICK_INGEST_CDN_NONCONFORMAL
_FRAME_START
TRICK_INGEST_SPLIT_SEQEND_SEQ_PAIR
VVI: Ingest fails. Invalid frame start. Check ingest feed.
Ingest fails. SequenceEnd/SequenceHeader pair not consecutive. Check ingest feed.
TRICK_INGEST_PIC_SIZE_CHANGED
TRICK_INGEST_PIC_SIZE_H_OR_V_ZERO
Ingest fails. Picture size changed. Check ingest feed.
Ingest fails. Picture size H or V zero. Check ingest feed.
Ingest fails. Horizontal size exceeds max (1920).
Check ingest feed.
5-22
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 5 System Monitoring
Monitoring Stream Objects
Table 5-11 MPEG Error Codes (continued)
Numeric
Error
Code
8046
8047
8048
8049
8050
8051
8052
8053
8054
8055
8056
Error Code
TRICK_INGEST_VERTICAL_PIC_SIZE_EXCEEDS
_MAX
TRICK_INGEST_SEQUENCE_HEADER_CHANGED
TRICK_INGEST_SEQUENCE_HEADER_CHANGE_NO
_SEQEND
TRICK_INGEST_SEQUENCE_HEADER_CHANGE
_BAD_PRIOR_STARTCODE
TRICK_INGEST_SEQUENCE_HEADER_CHANGE
_NO_PRIOR_STARTCODE
TRICK_INGEST_ILLEGAL_FRAMERATE
TRICK_INGEST_CDN_ILLEGAL
PES_PACKETISATION
TRICK_INGEST_CDN_STREAM_STARTS_WITH
_P_FRAME
TRICK_INGEST_CDN_STREAM_STARTS_WITH
_B_FRAME
TRICK_INGEST_ZERO_BITRATE
TRICK_INGEST_CDN_STREAM_STARTS_WITH
_BAD_I_FRAME
Description
Ingest fails. Vertical size exceeds max (1088). Check ingest feed.
VVI: Ingest fails. Sequence Header changed. Check ingest feed.
Ingest fails. Sequence Header changed with no preceding Sequence End.
Ingest fails. Sequence Header changed with no immediately preceding Sequence End.
Ingest fails. Sequence Header changed with no preceding start code
Illegal frame rate code. Check ingest feed.
VVI: Ingest fails. Illegal PES packetization. Check ingest feed.
VVI: Ingest fails: Stream begins with a P-frame.
Check ingest feed.
VVI: Ingest fails: Stream begins with a B-frame.
Check ingest feed.
Check ingest feed. Bitrate indeterminate.
VVI: Ingest fails: Stream begins with a malformed
I-frame. Check ingest feed.
lists the Managed Services Architecture (MSA) error codes for the optional Ingest Manager feature.
MSA Error Codes for the Optional Ingest Manager Feature Table 5-12
Numeric
Error
Code Error Code
7000
7001
7002
7003
MSA_BAD_XML
MSA_BAD_REQUEST
MSA_UNKNOWN_HOST
Description
There was an XML parsing error. Check the ADI XML for errors.
The request for content was bad. Check the target backoffice URL.
The host is unknown. Check the target backoffice URL.
MSA_CONNECTION_DROP The connection was dropped. Check the URL. The Ingest Manager possibly misformatted the ADI XML.
MSA_BACKOFFICE_TIMEOUT The backoffice did not respond within the allowed time interval. 7004
7005
7006
7007
7008
MSA_UNKNOWN
MSA_FAILED_POST
MSA_PKG_EXPIRED
MSA_ENCRYPT_FAILED
An unknown error occurred. Check the /home/isa/bss/log/aim.log.
The Ingest Manager failed to post the ADI to the backoffice.
The package has expired and the retry record is removed.
Ingest failed because Ingest Manager was unable to encrypt the content.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
5-23
Chapter 5 System Monitoring
Array Level Monitoring
Table 5-12 MSA Error Codes for the Optional Ingest Manager Feature
Numeric
Error
Code Error Code
7009
7010
7011
MSA_STORE_FAILED
MSA_BACKOFFICE_FAILED
MSA_INVALID_URL
Description
Ingest failed because Ingest Manage had a problem with the storage server.
Ingest failed because Ingest Manage was unable to contact the backoffice.
URL provided for the ingest is invalid.
Table 5-13 lists the MSA error codes for the File Service Interface (FSI).
MSA Error Codes for FSI Table 5-13
9002
9003
9004
9005
9006
9007
Numeric Error
Code
9001
Error Code
MSA_INGEST_INIT
MSA_CONTENT_ALREADY
MSA_DEL_RECORD_FAILED
MSA_INGEST_CANCELED
MSA_UNKNOWN_ERROR
MSA_ALLOC_ERROR
MSA_FILLCB_FAILED
9008
9009
MSA_ICONTENT_FAILED
MSA_INGEST_FAILED
Description
Unable to initialize the ingest from the FTP location.
Content is already ingesting.
Database record deletion failed.
Ingest has been canceled.
Unknown ingesting error has occurred.
Unable to continue because of a memory allocation error.
CServer FillCB call failed.
CServer call to iContentPlay failed.
Unable to ingest the specified content.
Array Level Monitoring
The Array Level Monitoring pages provide an overall view of the health and activity of a specified array.
Array Snapshot
The Array Snapshot page provides an overview of the current activity for the specified array of servers on the CDS. A summary of the state of all streams, content ingests, and disk usage is displayed.
The fields displayed on the Array Snapshot page are the same fields that are displayed on the System
Snapshot page, with the active stream bandwidth and active fill bandwidth shown for each Stream Group.
For descriptions of the fields, see Table 5-1 on page 5-4 .
5-24
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 5 System Monitoring
Server Level Monitoring
Server Level Monitoring
The Server Level Monitoring pages provide detail information on the health and activity of a Vault or
Streamer server.
To view the Server Level Monitoring pages, do the following:
Step 1
Step 2
Choose Monitor > Server Level, and then click one of the following as applicable:
•
•
•
•
•
Choose the IP address of the server from the drop-down list and click Display.
Disk Monitor
The Disk Monitor page provides real-time information on the status of a disk.
To view the current status of a disk, choose the IP address of the server from the drop-down list on the
Disk page, click Display, and roll your mouse over one of the disks displayed in the graphic. If the server is a Lindenhurst CDE, click one of the disks displayed in the graphic.
shows an example of a Streamer server.
To change how often the information is refreshed, enter the number of seconds in the Data Refresh Rate field. The default is 10 seconds. The range is 10 to 300. All field values that are updated, based on the refresh rate, are initially shown in a green font.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
5-25
Server Level Monitoring
Figure 5-13 Disk Monitor—Streamer Page
Chapter 5 System Monitoring
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.
The Linux File System Stats table shows the combined total storage space for the partitions of the disk drives, the combined available storage space for the partitions of the disk drives, and the percentage of used storage for each combined partition. In
Figure 5-13 , the hda2 partition has an alarm indicator
because the usage has exceeded the user-defined threshold of 40 percent. For information on setting
thresholds, see the “Setting System Thresholds” section on page 7-7
.
Table 5-14 describes the information displayed when a disk is selected.
5-26
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 5 System Monitoring
Server Level Monitoring
Table 5-14 Disk Status Fields
Field
Current Temp
Description
The current temperature of the hard disk.
Smart Status
Number of Reads
The Self-Monitoring, Analysis and Reporting Technology (S.M.A.R.T.) status of a disk as determined by the manufacturer in accordance with the relevant ATA/SCSI standards. S.M.A.R.T. is logic embedded in the firmware that determines when a disk is going bad.
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.T is firmware, native to most disk drives, that monitors disk attributes over time, making it possible to perform predictive failure analysis. Advanced warning of predictive failures allows the operator to perform preventative maintenance.
To view the current read/write activity that has occurred in the last five seconds on the selected disk,
click Graph Disks. Figure 5-14 shows an example of the Disk Activity graph.
Figure 5-14 Disk Monitor—Vault Disk Activity Graph
OL-22792-01
The Disk Activity graph displays an average calculation of the amount of data read (in megabytes per second) and data writes over a five-second period.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
5-27
Chapter 5 System Monitoring
Server Level Monitoring
NIC Monitor
The NIC Monitor page displays the status of each network interface card (NIC) on the server.
To view the current status of a NIC on a server, choose the IP address of the server from the drop-down list on the NIC Monitor page, click Display, and click one of the NIC ports displayed in the graphic.
shows an example of the eth4 interface on a Vault server.
To change how often the information is refreshed, enter the number of seconds in the Data Refresh Rate field. The default is 10 seconds. The range is 10 to 300. All field values that are updated, based on the refresh rate, are initially shown in a green font.
Figure 5-15 NIC Monitor—Vault Page
Table 5-15 describes the information displayed for a NIC port.
Table 5-15 NIC Port Status Fields
Field
Port Speed
Admin State
Op State
Description
Speed of the interface in megabits per second (Mbps).
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.
Operational state of the port interface. The operational state is either up or down. If the port is not connected to the network or is malfunctioning, the operational state displayed is down.
5-28
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 5 System Monitoring
Server Level Monitoring
Table 5-15
Field
Media Type
Poll Interval
Transmit
Received
NIC Port Status Fields (continued)
Description
Physical conduit of the interface. The physical type is either copper or fiber optic.
Number of seconds between each disk polling.
Total number of bytes transmitted since this port has been operational and configured as administratively up.
Total number of bytes received since this port has been operational and configured as administratively up.
To view the average transmit and receive activity that has occurred in the last two seconds for each port
on this server, click Graph Ports. Figure 5-16
shows an example of the Port Activity graph.
Figure 5-16 NIC Monitor—Vault 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. For more information, see the
“CDSM or VVIM Health Monitoring” section on page D-9 .
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
5-29
Chapter 5 System Monitoring
Server Level Monitoring
To view the current values of the monitored components, as well as the threshold settings, choose the IP address of the server from the drop-down list on the Server Vitals page and click Display.
To change how often the information is refreshed, enter the number of seconds in the Data Refresh Rate field. The default is 10 seconds. The range is 10 to 300. All field values that are updated, based on the refresh rate, are initially shown in a green colored font.
To change the temperature format to Fahrenheit, choose ºF for the Temperature Format. The default is
Celsius (ºC).
The monitored components are different for each Content Delivery Engine (CDE) model.
shows an example of the Server Vitals page for a Vault (CDE420).
Figure 5-17 Server Vitals Page
5-30
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 5 System Monitoring
Server Level Monitoring
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.
To change how often the information is refreshed, enter the number of seconds in the Data Refresh Rate field. The default is 10 seconds. The range is 10 to 300. All field values that are updated, based on the refresh rate, are initially shown in a green font.
Figure 5-18 Cache/Fill Bandwidth Page
OL-22792-01
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.
Table 5-16 Cache/Fill Bandwidth Fields
Service
Active Stream Count
Description
The number of active streams on this Streamer.
Active Stream Bandwidth The bandwidth (in Mbps) used for streaming on this Streamer.
Unique Stream Count The number of unique streams on this Streamer.
Unique Stream Bandwidth The bandwidth (in Mbps) used for serving unique streams on this
Streamer.
Fill Receive Stream Count The number of streams on this Streamer that are retrieving content from the Vault to fulfill requests for content.
Actual Fill Stream
Bandwidth
The bandwidth (in Mbps) used on this Streamer for retrieving content from the Vault.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
5-31
Chapter 5 System Monitoring
Server Level Monitoring
Table 5-16 Cache/Fill Bandwidth Fields (continued)
Service Description
Disk Read Stream Count The number of streams on this Streamer sending content that was retrieved from the disks on the Streamer.
Disk Read Bandwidth The bandwidth (in Mbps) used on this Streamer for retrieving locally stored content (content on the disks on the Streamer).
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.
shows an example of a
Streamer server.
Figure 5-19 Services Monitor Page—Streamer
Table 5-17 describes the services listed on the Services Monitor page.
Table 5-17 CDS Services
Service
Cisco Cache Server
Cisco FSI Master
Cisco FSI Server
Server
Both
Vault
Vault
Description
The Cache server runs on all servers. The Cache server is responsible for the core functions of the CDS.
The File Service Interface (FSI) Master process is running if you are looking at a master Vault server.
The FSI Master serves as the master Vault process for content file-related requests from the backoffice.
The FSI Server runs on every Vault and processes file-related requests from the FSI Master.
5-32
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 5 System Monitoring
Recommended Monitoring Schedule
Table 5-17 CDS Services (continued)
Service
Cisco RTSP Server
Server
Streamer
Cisco Resource Manager Streamer
Cisco DB Server
DB Synchronization
Status
Cisco SNMP Server
Cisco System Manager
Cisco BWMgr Server
Cisco Ingest Manager
Both
Both
Both
Both
Streamer
Vault
Description
The RTSP server runs on the Streamer as either a client or server depending on the headend environment. The
RTSP server handles messaging between the CDS and the backoffice.
The Resource Manager runs on a Streamer server. The
Resource Manager handles orphaned streams.
The DB (database) server runs on all servers and is responsible for keeping track of all data objects in the
CDS.
Displays the status of the database synchronization among all servers. The states are “OK” and “not OK.”
The SNMP server shows as running when the SNMP agent is running.
The System Manager runs on each server and facilitates communication with the CDSM.
The Bandwidth Manager process runs on the Streamer provided the optional Bandwidth Manager feature is part of your deployment. It keeps track of allocated streams and VOD network resources.
The Ingest Manager process is running if you are looking at a master Vault server and the optional
Ingest Manager feature is part of your deployment.
Recommended Monitoring Schedule
This monitoring schedule is recommended to ensure that the CDS is functioning as expected and identify potential issues that may cause down time.
Caution
Do not attempt to access the Linux command line unless you are familiar with the CDS, the Linux operating system, and have a basic understanding of the Linux command line.
Note
Some error warnings in the logs are only informational and no action is necessary.
Daily Tasks
The following tasks should be performed daily:
•
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-2
for more information.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
5-33
Chapter 5 System Monitoring
Recommended Monitoring Schedule
•
Choose Monitor > System Level > Failed Ingests to check for any failed ingests. See the
for more information.
Weekly Tasks
The following tasks should be performed weekly:
•
Monitoring Tasks for Streamers and Vaults
•
•
Monitoring Tasks for Streamers
Note
All commands require that you log into the Linux operating system as root. Some tasks have a CDSM option.
Monitoring Tasks for Streamers and Vaults
To monitor the Streamer and Vaults weekly, do the following:
Step 1
Step 2
Step 3
Recover used disk space. Log in to each server using the root logon and run the following command:
dh -h
Filesystem Size Used Avail Use% Mounted on
/dev/hda1 13G 5.2G 7.0G 43% /
/dev/hda6 20G 16G 4.3G 78% /arroyo/log
If the disk usage is greater than 75 percent, recover the disk space using the following methods:
a.
Search and remove any core files.
find /arroyo –name core* find /home/isa –name core* b.
c.
Copy any archived logs to an external device and delete them from the /arroyo/archive directory.
Check for the presence of old install or upgrade ISO files in the /root directory and delete them.
find /root –name *.iso
find /arroyo –name *.iso
Verify the services are running. Choose Monitor > Server Level > Services Monitor to check the services for each server, or log in to each server and run the following commands:
su - isa show_calypso_services
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.
Use the grep -i Speed command to verify that each adapter that has a “link up” status should have a speed of 1000.
5-34
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 5 System Monitoring
Recommended Monitoring Schedule
Step 4
Step 5
Step 6
Step 7 grep –i Speed /proc/net/PRO_LAN_Adapters/*.info
c.
Use the grep -i State command to verify that all adapters should have an “up” state, except those adapters that are not being used.
grep –i State /proc/net/PRO_LAN_Adapters/*.info
Check the CServer streaming and cache-fill interfaces using the following command:
/home/stats/ifstats
Check the database thread count using the following command:
netstat –an | grep 9999
Two connections for each Vault and Streamer should be listed with a status of “ESTABLISHED.”
Check the protocol timing logs for errors or problems. Also, look at the protocol timing logs for packet retransmissions.
tail –f /arroyo/log/protocoltiming.log.{date} | grep retransmissions
Look for warning messages.
grep –i warning /arroyo/log/protocoltiming.log.<
date> | more
Step 8
Note
The “WARNING” messages can sometimes be misleading; for example, “datawait” and “slow disk” messages occur normally and do not indicate a problem.
The number of GOIDs for a particular content object must be the same on all servers (Vaults and
Streamers) that are supposed to have the content. The number of Vaults that must have the same number of GOIDs for a particular content object is determined by the mirrored copy configuration (see the
“Configuring the Servers” section on page 4-58 ). The number of GOIDs is also dependent on the trick
speeds configured you configured (see the
“Configuring Ingest Tuning” section on page 4-17 ). If the
GOID is different between a Vault and a Streamer, session setup is not created properly because of an issue of “no content available.” This is because there is no content on the Vault that matches the GOID of the Streamer has.
Monitoring Tasks for Vaults
In addition to the weekly monitoring tasks for both the Vaults and Streamers, the Vaults can also be monitored in the following ways:
1.
Check the available space on the Vault hard drives. Choose Monitor > Server Level > Disk
Monitor. The disk availability is shown as a percentage and as a number of gigabytes. Alternatively, view the protocol timing logs by running the following command:
tail –f /arroyo/log/protocoltiming.{date} | grep “Capacity Disk:”
2.
3.
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.
Check the /home/isa/fsi logs for ingest errors on each Vault. The master Vault has an additional log.
Look for errors in the following log files in the /home/isa/bss/logs/ directory:
–
fsi.log
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01 5-35
Recommended Monitoring Schedule
–
fsi.err
The fsi.log and fsi.err files are related to the ingest activity on a Vault.
Chapter 5 System Monitoring
Monitoring Tasks for Streamers
In addition to the weekly monitoring tasks for both the Vaults and Streamers, the Streamers can also be monitored in the following ways:
1.
Look at the streaming log.
tail -f /arroyo/log/streamevent.log.<date>
2.
Look for errors in the following log files in the /home/isa/bss/logs/ directory:
–
–
rtsp.log rtsp.err
The rtsp.log and rtsp.err files are used to check the stream setup and control on a Streamer.
Monthly Tasks
The monthly monitoring tasks consist of the following:
1.
2.
Choose Monitor > System Level > System Snapshot and check that the “Disk Available” amount meets the requirements for the expected movie storage in the next three to six months.
Run the reports for the last month that are suitable for your requirements and save them as comma-separated value (CSV) files.
3.
4.
Using the bandwidth and streaming reports, check that the CDS is not exceeding required usage per service area.
Run a quick security check.
a.
Ensure that the CDSM changes can be attributed to individual users and not to a generic admin account.
b.
Reset CDSM passwords if necessary.
c.
Reset Linux passwords if necessary.
d.
Check that access policies and firewalls are still enforced.
Other Tasks
If you have access to an anything on demand (XOD) application, do the following:
1.
Check the inspect-live log for excessive errors.
2.
Check the inspect-live log for excessive communication times with the BMS or CDS.
5-36
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
C H A P T E R
6
System Reporting
The CDSM provides tools that can be used for system monitoring and system diagnostics. The topics covered in this chapter include:
•
•
•
•
Note
If Virtual Video Infrastructure (VVI) with split-domain management is enabled, the CDSM pages associated with the Vaults and Caching Nodes display only on the VVI Manager (VVIM), and the CDSM pages associated with the Streamers display only on the Stream Manager. For more information, see the
“Virtual Video Infrastructure” section on page D-6 .
Stream Activity
The Stream Activity reports displays information about streams. The available reports are:
•
•
•
•
•
•
To access the available Stream Activity reports, choose Report > Stream Activity, and follow the procedure for the specific report described in the following subsections.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
6-1 OL-22792-01
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-1 Available Reports for Stream Activity
shows the selection fields for the Streams by Array report.
Figure 6-2 Stream By Array Report Selection Fields
Step 2
Step 3
From the Stream Array drop-down list, choose a stream array.
Choose a modifier. See
for a description of each modifier.
6-2
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 6 System Reporting
Stream Activity
Table 6-1 Streams by Array Modifiers
Modifier
None (Date
Only)
Description
Filter on date only.
Destination IP Filters the report by the IP address of the destination device you choose in a later step.
Step 4
Step 5
Step 6
Step 7
Using the drop-down lists provided, or the calendars, choose a From Date and To Date for the report.
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
If you selected a modifier that requires a value, choose or specify the filter value.
Click Display.
To clear the fields and start over, click Reset.
with no optional modifiers selected.
Figure 6-3 Streams by Array Report
OL-22792-01
The report displays:
•
Report type (for example, Daily Stream Activity Report for streams by array)
Cisco TV CDS 2.3 RTSP Software Configuration Guide
6-3
Stream Activity
Chapter 6 System Reporting
•
From and to dates
•
Date and time of each stream count
•
Total number of standard definition (SD) streams, total number of high-definition (HD) streams, and total streams overall for the time period selected
Click Previous Report to return to the report selection page.
Note
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.
Step 8
To see more detail, click the total number of streams link. For example, in Figure 6-3
, click 5 total. The
Session ID Summary is displayed ( Figure 6-4
).
Figure 6-4 Session ID Summary
Note
The Session ID Summary can be sorted by clicking on each column heading.
Step 9
The report displays:
•
•
Session ID
Content name
•
Start and end date and time
The Session ID Summary can be sorted by clicking on each column heading.
To see the stream play history of a specific session, click a session ID (
Note
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 D-5
.
6-4
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 6 System Reporting
Figure 6-5 Session ID—Stream Play History Drilldown
Stream Activity
The report displays:
•
Session ID
•
•
Set-top box MAC address
Termination reason
•
•
Date and time of each play or trick mode action
Elapsed time of each action
At the bottom of each Stream Play History report is a legend mapping the action to a color.
Click Previous Report to return to the previous page.
Note
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.
Step 10
To see details about the stream associated with this session, click Show Stream Data (
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
6-5
Stream Activity
Figure 6-6 Stream Play History–Stream Data
Chapter 6 System Reporting
Step 11
The Stream Data displays:
•
•
Details about the stream (QAM IP address and port, and service group)
Details about the content (content name, ingest information, server ID storing the content, and so on)
Click Hide Stream Data to hide stream data.
Click Previous Report to return to the previous page.
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.
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.
Streams by Time
The Streams by Time report summarizes the number of standard-definition and high-definition streams by the selected time breakdown in the specified time period. This report can be used to analyze slow times of day and to plan outages.
To view the Streams by Time report, do the following:
Step 1
From the Available Reports drop-down list, choose Streams By Time.
Figure 6-7 shows the selection
fields for the Streams By Time report.
6-6
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 6 System Reporting
Figure 6-7 Streams by Time Report Selection Fields
Stream Activity
Step 2
Step 3
Step 4
Using the drop-down lists provided, or the calendars, choose a From Date and To Date for the report.
Choose the time breakdown.
Click Display.
To clear the fields and start over, click Reset.
Figure 6-8 shows an example of the Streams by Time report with the Per Hour time breakdown selected.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
6-7
Stream Activity
Figure 6-8 Streams by Time Report
Chapter 6 System Reporting
The report displays:
•
Report type (for example: Stream Activity Report for streams by time)
•
•
From and to dates
Time of each stream activity survey
•
Total number of streams for each time within the specified from and to dates
Click Previous Report to return to the previous page.
Note
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.
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. 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.
6-8
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
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.
selection fields for the Stream Play History report.
Figure 6-9 Stream Play History Report Selection Fields
OL-22792-01
Step 2
Choose a modifier. See Table 6-2 for a description of each modifier.
Table 6-2 Stream Play History Modifiers
Modifier Description
None (Date Only) Displays a list of all streams (Session ID Summary) filtered by the from and to dates.
Session Handle
Destination IP
Filters the report by a session handle you specify in a later step.
Filters the report by the IP address of the destination device you choose in a later step.
Step 3
Using the drop-down lists provided, or the calendars, choose a From Date and To Date for the report.
Note
Selecting Session ID displays the complete play history for the specified session. The From
Date and To Date fields are bypassed.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
6-9
Chapter 6 System Reporting
Stream Activity
Step 4
Step 5
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.
If you selected a modifier, choose or specify the filtered value. For example, if you choose Service Group as the modifier, you specify which Service Group.
Click Display.
To clear the fields and start over, click Reset.
shows an example of the Stream Play History report.
Figure 6-10 Stream Play History Report
Note
The Session ID Summary can be sorted by clicking on each column heading.
Step 6
The report displays:
•
Session ID
•
•
Content name
Start and end date and time
To see the stream play history of a specific session, click a session ID (
Note
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 D-5
.
6-10
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 6 System Reporting
Figure 6-11 Session ID Stream Play History Drilldown
Stream Activity
Step 7
The report displays:
•
Session ID
•
•
Set-top box MAC address
Termination reason
•
•
Server ID of the Play server that served the trick mode
Date and time of each play or trick mode action
•
Elapsed time of each action
Click Previous Report to return to the previous page.
To see details about the stream associated with this session, click Show Stream Data (
).
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
6-11
Stream Activity
Figure 6-12 Stream Play History—Stream Data
Chapter 6 System Reporting
The Stream Data displays:
•
•
Details about the stream (QAM IP address and port, and service group)
Details about the content (content name, ingest information, server ID storing the content, and so on)
Click Hide Stream Data to hide stream data.
Click Previous Report to return to the previous page.
At the bottom of each Stream Play History report is a legend mapping the action to a color.
Note
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.
Step 8
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.
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.
6-12
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 6 System Reporting
Stream Activity
Cache/Fill Bandwidth
The Cache/Fill Bandwidth report displays details on the content caching activity on a Streamer.
To view the Cache/Fill Bandwidth report, do the following:
Step 1
From the Available Reports drop-down list, choose Cache/Fill Bandwidth.
shows the selection fields for the Cache/Fill Bandwidth report.
Figure 6-13 Cache/Fill Bandwidth Report Selection Fields
OL-22792-01
Step 2
Step 3
Step 4
Step 5
From the Server Array drop-down list, choose a server array.
Using the drop-down lists provided, or the calendars, choose a From Date and To Date for the report.
From the Server ID drop-down list, choose a Streamer.
Click Display.
To clear the fields and start over, click Reset.
Figure 6-14 shows an example of the Cache/Fill Bandwidth report.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
6-13
Stream Activity
Figure 6-14 Cache/Fill Bandwidth Report
Chapter 6 System Reporting
The report displays the minimum, average, and maximum bandwidth used for the selected Streamer.
Click Previous Report to return to the previous page.
Note
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.
Step 6
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.
6-14
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 6 System Reporting
Stream 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.
Stream Failures
The Stream Failures report lists the number of stream failures.
To view the Stream Failures report, do the following:
Step 1
From the Available Reports drop-down list, choose Stream Failures.
Figure 6-15 shows the selection
fields for the Stream Failures report.
Figure 6-15 Stream Failures Report Selection Fields
OL-22792-01
Step 2
Step 3
Choose an error code, if applicable. See
in the
“Stream Failures” section on page 5-18
for descriptions of possible error codes.
Choose a modifier. See Table 6-3 for a description of each modifier.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
6-15
Chapter 6 System Reporting
Stream Activity
Table 6-3
Modifier
Service Group
Server ID
Stream Failure Modifiers
Description
Filters the report by the service group that you choose in a later step.
Filters the report by a server ID that you choose in a later step.
Step 4
Step 5
Step 6
Step 7
Using the drop-down lists provided, or the calendars, choose a From Date and To Date for the report.
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
If you selected a modifier, choose the filter value.
Click Display.
To clear the fields and start over, click Reset.
shows an example of the Stream Failures report.
Figure 6-16 Stream Failures Report
Step 8
The report displays:
•
Report type
•
•
From and to dates
Date (and time if applicable) of each time breakdown
•
Total number of failures for each time breakdown selected
To see more detail, click the total number of failures link. The Stream Failure Details report is displayed
(
).
6-16
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 6 System Reporting
Figure 6-17 Stream Failure Details
Stream Activity
OL-22792-01
Step 9
The report displays:
•
•
•
•
•
•
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
The report can be sorted by clicking on each column heading.
To see the stream play history of a specific session, click a session ID.
Note
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 D-5
.
Step 10
Click Previous Report to return to the previous page.
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
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.
Step 11
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.
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.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
6-17
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.
shows the selection fields for the Content Popularity report.
Figure 6-18 Content Popularity Report Selection Fields
Step 2
Step 3
Using the drop-down lists provided, or the calendars, choose a Start Time and End Time for the report.
Click Display.
To clear the fields and start over, click Reset.
shows an example of the Content Popularity report.
Figure 6-19 Content Popularity Report
6-18
The report displays:
•
•
Report type
Optional modifiers if applicable
•
•
•
From and to dates
Content object name
Total number of streams for each content streamed in the specified time period
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 6 System Reporting
Stream Activity
Step 4
To view content details, click the content object name. The Content Detail report is displayed
(
Figure 6-20 Content Popularity Details
Click Close to close this window.
Click Previous Report to return to the previous page.
Note
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.
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. 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.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
6-19
Chapter 6 System Reporting
Content Activity
Content Activity
The Content Activity report lists all content stored on all Vaults in the specified group and all unpublished packages. The available reports are:
•
•
Content by Ingest Date
To view the Content by Ingest Date report, do the following:
Step 1
Step 2
Click Report > Content Activity. The Content Activity selection page is displayed.
From the Available Reports drop-down list, choose Content By Ingest Date (
).
Figure 6-21 Content Activity Selection Fields
Step 3
Step 4
Step 5
Step 6
From the Array drop-down list, choose an array.
Using the drop-down lists provided, or the calendars, choose a From Date and To Date for the report.
Choose Include Deleted to include content that has been deleted from the array; otherwise, choose
Exclude Deleted.
Click Display.
To clear the fields and start over, click Reset.
shows an example of the Content Activity report.
6-20
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 6 System Reporting
Figure 6-22 Content Activity Report
Content Activity
Step 7
The report displays:
•
Report type
•
•
From and to dates
Content filenames
•
•
Creation date
Destroyed date
Figure 6-23 Content Detail
OL-22792-01
Click Close to close this window.
Click Previous Report to return to the previous page.
Note
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.
Step 8
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.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
6-21
Content Activity
Chapter 6 System Reporting 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
To view the Unpublished Package report, do the following:
Step 1
Step 2
Choose Report > Content Activity. The Content Activity selection page is displayed.
From the Available Reports drop-down list, choose Unpublished Package Report ( Figure 6-24
).
Figure 6-24 Unpublished Package Selection Fields
Step 3
Step 4
Using the drop-down lists provided, or the calendars, choose a From Date and To Date for the report.
Click Display.
To clear the fields and start over, click Reset.
shows an example of the Unpublished Package report.
6-22
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 6 System Reporting
Figure 6-25 Unpublished Package Report
CDSM Audit Logs
Step 5
Step 6
•
•
•
The report displays:
Report type
From and to dates
•
•
•
Package names
Creation date
Source URL
Target URL
•
Number of assets associated with the package
Click New Report to return to the previous page.
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.
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.
CDSM Audit Logs
The CDSM Audit log keeps track of every configuration change, deletion of monitored items, and maintenance actions.
To view the CDSM Audit logs, do the following:
Step 1
Choose Report > CDSM Audit logs.
shows the selection fields for the CDSM Audit logs.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
6-23
CDSM Audit Logs
Figure 6-26 CDSM Audit Log Selection Fields
Chapter 6 System Reporting
Step 2
Step 3
Using the drop-down lists provided, or the calendars, choose a From Date and To Date for the log.
Click Display.
To clear the fields and start over, click Reset.
shows an example of the CDSM Audit log.
Figure 6-27 CDSM Audit Log
Step 4
Step 5
The log displays:
•
•
•
•
From and to dates
Action taken (Section Descriptor)
User who took the action
System used
•
Date the action occurred
To get more information about the action taken, click a section descriptor. The CDSM Audit Log Detail is displayed in a new window. Click Close to close the window.
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.
6-24
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 6 System Reporting
Archived Data 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.
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-4 describes the different archived data.
Table 6-4 Archived Data Types
Archive Description
Log of configuration changes that were made to the system and when the changes were made.
Archive of content ingested.
Archive of all streams.
Archive of trick mode and play actions that occurred on all streams.
To download an archived data report, do the following:
Step 1
Step 2
Step 3
Choose Report > Archived Data. The Archived Data page is displayed.
From the Archives drop-down list, choose an archive and click Next.
Right-click the HTTP link of the report you want to download and choose Save Target As, 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 (
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
6-25
Archived Data
Figure 6-28 Save As Dialog Box
Chapter 6 System Reporting
Step 4
Step 5
Choose a location and name for the file and click Save.
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-23
.
Content Reports
Table 6-5 describes the fields in the Content Report CSV files.
Table 6-5 Content Report Archive Fields
Field
mGoid mName mProvider mCategory
Description
Global object identifier. Used by the CDS database.
The name of the content file.
Not applicable.
Not applicable.
mFactoryId mOpState
Not applicable.
Operational state is not used and is always 2 (In Service). mAdminState Administrative state is not used and is always 2 (In Service).
mProvisionForPush Type of FTP provisioned. Values are:
•
•
•
0—FTP pull
1—FTP push
3—Live recording
6-26
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 6 System Reporting
Archived Data
Table 6-5 Content Report Archive Fields (continued)
Field
mURL mIngestIpAddress
Description
URL of the content file. This field is applicable only for FTP pull.
IP address of the ingest interface on the Vault used to download the content file.
mIngestFileSize Content file size, in bytes.
mCreateTime Time and date this content file was created. The time and date is represented in seconds since the start of Unix epoch time.
1 mLastModifiedTime Time and date this content file was last modified. The time and date is represented in seconds since the start of Unix epoch time.
mDeleteTime Time and date this content file was deleted. The time and date is represented in seconds since the start of Unix epoch time
.
Server ID of the Vault server that is the primary source for this content file.
mServerId mAssetName mEncrypted mRate
Asset name of the content, if populated.
Not applicable.
Transmit rate requirement of the file, in bytes per second.
1.
Unix epoch time is 1970-01-01T00:00:00Z
Stream Reports
describes the fields in the Stream Report CSV files.
Table 6-6 Stream Report Archive Fields
Field
mSessionId mGoid mTsIdOut
Description
Session ID of the stream.
Global object identifier. Used by the CDS database.
Not applicable.
mTsIdIn Not applicable.
mProgramNumber Not applicable.
mBandwidthUsed This field is applicable only when Streaming Mode is set to ASI. mQAMIp
The transport stream bandwidth, in bytes, required for this stream object.
IP address of the QAM device that participated in transmitting the stream.
mQAMPort mSetTopMac mServiceGroup mStartTime mLastTime
The IP address is represented as an integer. For example, 3232235818 decimal converts to C0A8012A hexadecimal, which translates to 192.168.1.42
Port the QAM device is using to receive the stream object.
Not applicable.
Not applicable.
Timestamp when the stream was created. The timestamp is represented in seconds since the start of Unix epoch time.
1
Not applicable.
1.
Unix epoch time is 1970-01-01T00:00:00Z
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
6-27
Chapter 6 System Reporting
Archived Data
Stream Failure Reports
Table 6-7 describes the fields in the Stream Failure Report CSV files.
Table 6-7 Stream Failure Report Archive Fields
Field
mSessionId mKey mServerId mGroupId Array ID the Streamer is associated with.
mServiceGroup Service group that participated in transmitting the stream.
mQAMIp mEventTime
IP address of the QAM device that participated in transmitting the stream.
The IP address is represented as an integer. For example, 3232235818 decimal converts to C0A8012A hexadecimal, which translates to 192.168.1.42
Timestamp of when the event occurred. The timestamp is represented in seconds since the start of Unix epoch time.
1 mOperation
Description
Session ID of the failed stream.
CDS database key for this record.
Server ID of the Streamer that participated in transmitting the stream.
mErrorCode mOperand mTask
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
for more information.
Error code provides a description of the event that caused the error. See
for more information.
Operand that was being operated on at the time of the failure, for example, the
StreamID is the operand if a stream was being created or controlled at the time of failure.
Failed task is the event category indicating the type of execution sequence that the call stack was currently within at the time of the failure. See
for more information.
1.
Unix epoch time is 1970-01-01T00:00:00Z
Stream Activity Reports
The Stream Activity Reports archive contains all trick mode and play actions of all streams within the
given 24-hour period. Table 6-8 describes the fields that are exported to the CSV file.
Table 6-8
Field
mSessionId mActionTime mServerId mOpState
Stream Activity Report Fields
Description
Session ID of the stream.
Timestamp when the stream activity occurred. The timestamp is represented in seconds since the start of Unix epoch time.
1
Server ID of the Streamer that is providing the stream.
Operational state is not used and is always zero (0).
6-28
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 6 System Reporting
Archived Data
Table 6-8 Stream Activity Report Fields (continued)
Field
mStreamState mSpeed
Description
Stream state is not used and is always zero (0).
Speed direction is as follows:
•
•
1 means play
0 means not paused/stopped mNptOffset
•
•
n means n times fast-forward
–n means n times rewind
Current point in time (milliseconds) where the stream is on the set-top box, based on from NPT and to NPT. mDestroyedReason This field is only populated if the stream is destroyed by the CDS orphan stream handler. The CDS orphan stream handler only destroys a stream for one of the following two reasons:
•
Orphan session is detected
•
LSCP timeout maximum has been reached
1.
Unix epoch time is 1970-01-01T00:00:00Z
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
6-29
Archived Data
Chapter 6 System Reporting
6-30
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
OL-22792-01
C H 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. This chapter covers the following topics:
•
•
•
•
•
Restarting the Services, page 7-9
Software Maintenance, page 7-9
Note
If Virtual Video Infrastructure (VVI) with split-domain management is enabled, the CDSM pages associated with the Vaults and Caching Nodes display only on the VVI Manager (VVIM), and the CDSM pages associated with the Streamers display only on the Stream Manager. For more information, see the
“Virtual Video Infrastructure” section on page D-6 .
Note
You must have read/write privileges to perform the functions described in this chapter.
Caution
Many of the functions discussed in this chapter involve rebooting a CDS server. Rebooting a Vault server does not interrupt stream services, but causes current ingests to fail. If your CDS does not have stream failover, rebooting a Streamer without offloading it interrupts all stream services. If possible, you should perform functions that require a system restart during times when the least number of users are actively connected to your system.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
7-1
Chapter 7 System Maintenance
User Access
User Access
The CDS consists of one of the following network configurations:
•
One or more Vault servers, one or more Streamer servers, and one CDSM
•
One or more ISV servers and one CDSM
All the components of your CDS are configured, monitored, and managed centrally through the CDSM.
The CDSM is a browser-based interface that runs on its own server. However, there are some ISV systems that include the CDSM functions.
The CDS provides three levels of user access:
•
Read only access provides viewing access to the configuration settings and monitoring capabilities.
•
•
Read/write access provides the ability to change the configuration settings and monitor all aspects of the system. In addition, a user with read/write access can perform software upgrades, restart servers, and restart services in a CDS.
Master access has all the privileges of the read/write level and can add, delete, and change the level of access of the other users.
•
Engineering access is primarily used for initializing the CDS at the time of installation and for CDS diagnostics. After your CDS has been configured, you should not require a user with engineering access level for day-to-day operations.
There is one built-in user, “admin,” that has master user capabilities. This is the only user that exists on a new system.
Setting Up 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
Step 2
Choose Maintain > Users > Add User. The Add User page is displayed.
Fill in the fields as described in
Table 7-1 Add User Fields
Field
New User
Password
Access
Description
User login ID. A user name may have up to 25 characters. Any 7-bit characters from the
American National Standards Institute (ANSI) character set are allowed.
Password associated with the user login name. The password must be at least 5 characters. The maximum is 20.
Choose the appropriate access level from the drop-down list. See the beginning of this
section, the “User Access” section on page 7-2 for descriptions of the access levels.
Step 3
Click Add User to add this user.
To clear the fields and start over, click Reset.
7-2
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 7 System Maintenance
User Access
Editing User Settings
To change a user password and access level, do the following:
Step 1
Step 2
Step 3
Step 4
Choose Maintain > Users > Edit User. The Edit User page is displayed.
From the Action drop-down list, choose Change Password or Change Access.
From the User Name drop-down list, choose a user name.
Fill in the new password or choose the access as appropriate. See
Table 7-2 for descriptions of these
fields.
Table 7-2
Field
New Password
Access
Edit User Fields
Description
Password associated with the user login name. The range is 5 to 20 characters.
Choose the appropriate access level from the drop-down list. See the beginning of this section, the
“User Access” section on page 7-2
, for descriptions of the access levels.
Step 5
Click Submit to save the changes.
To clear the fields and start over, click Reset.
Deleting a User
To delete a user from the list of users, do the following:
Step 1
Step 2
Step 3
Step 4
Choose Maintain > Users > Edit User. The Edit User page is displayed ( Figure 7-1 on page 7-4
).
From the Action drop-down list, choose Delete User.
From the User Name drop-down list, choose a user.
Click Submit to delete the user.
To clear the fields and start over, click Reset.
Viewing User Settings
To view all user settings you must log in with master access level. Choose Maintain > Users > View
Users. The View Users page is displayed.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
7-3
Chapter 7 System Maintenance
User Access
Changing User Default Settings
The User Default Settings page allows you to specify your settings for the Media Scheduler page so that each time you log in to the CDSM your settings are recalled. If you have master level access, you can specify the settings for all users. For more information about the Media Scheduler, see the
“Configuring the Media Scheduler” section on page 4-47 .
To change the default settings for a user, do the following:
Step 1
Step 2
Choose Maintain > Users > User Default Settings. The User Default Settings page is displayed.
From the Select User drop-down list, choose a user. The User Default Settings page refreshes and displays the user settings (
Figure 7-1 User Default Settings Page
Step 3
In the Media Scheduler Preferences section of the page, make your selections as appropriate. See
Table 7-3 for descriptions of the fields.
7-4
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 7 System Maintenance
Server Maintenance
Table 7-3 Media Scheduler Preferences
Field
Action on
Recurring
Schedules
Description
Choose either Preserve Exiting Schedules or Overwrite Existing Schedules. This option is only for user-generated schedules and is not for uploaded electronic program guide (EPG) data.
Package Name
Generation
Preserving Existing Schedules keeps any content that is currently scheduled for the day and channel you selected and fills in only the empty timeslots. Overwrite Existing
Schedules overwrites any content that is currently scheduled for the day and channel you selected.
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.” If the package name already exists and you want a new package name auto-generated, choose Enable and the start time is added to the package name. If the package name already exists and you want to create the package name using the
Metadata Editor, choose Disable.
Step 4
Step 5
Step 6
In the Input Channels Displayed on Media Scheduler section of the page, check the check boxes for the channels you want to schedule, or check the Select All check box to choose all channels.
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.
Click Save to save the changes.
To clear the fields and start over, click Reset.
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. The Server Maintenance pages include the following:
•
•
•
•
Restarting a Server
Caution
Restarting a Vault or Streamer server while there are still active ingests and streams causes the current ingests and streams to fail.
Restarting a server briefly shuts down the unit, then restarts it using the installed version software image.
This action does not power off the unit.
To restart a server, do the following:
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
7-5
Chapter 7 System Maintenance
Server Maintenance
Step 1
Step 2
Step 3
Choose Maintain > Servers > Server Restart. The Server Restart page is displayed.
From the Server IP 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.
From the Restart drop-down list, choose Yes and click Submit.
Shutting Down a Server
Caution
Shutting down a Vault or Streamer server while there are still active ingests and streams causes the current ingests and streams to fail.
Shutting down by simply powering off the unit using the chassis power button is not recommended, as this may result in corruption of the configuration information, including system status when the shutdown occurred.
Shutting down and restarting using the CDSM is the recommended procedure. the Server Shutdown shuts down and powers off the selected unit.
To shut down and power off a server, do the following:
Step 1
Step 2
Step 3
Choose Maintain > Servers > Server Shutdown. The Server Shutdown page is displayed.
From the Server IP 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.
From the Shutdown drop-down list, choose Yes and click Submit.
Offloading a Server
The Server Offload page lets you enable or disable the server offload. When Server Offload is enabled on a server, the server is configured to reject new provisioning; that is, do not allow new ingests on a
Vault and do not allow new streams on a Streamer and move existing streams to another Streamer gracefully.
To enable Server Offload, do the following:
Step 1
Step 2
Step 3
Choose Maintain > Servers > Server Offload. The Server Offload page is displayed.
From the Server IP 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.
Choose Enable and click Submit.
7-6
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 7 System Maintenance
Server Maintenance
After enabling Server Offload, current traffic activity can be monitored, and when the server offload is
Objects” section on page 5-4 . To view activity on a Streamer, see the
and stream objects before updating the software.
Note
The Server Offload setting is persistent through a system reboot.
Server Offload—Disable
After the software upgrade or maintenance is complete, you need to disable the server offload so that the server can again participate in the system.
To disable Server Offload, do the following:
Step 1
Step 2
Step 3
Choose Maintain > Servers > Server Offload.
From the Server IP 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.
Choose Disable and click Submit.
Setting System Thresholds
The System Thresholds page allows you to set thresholds for loss and usage of the CDS resources, as well as enable or disable monitoring of the CDS services. The Performance Parameters section of the page has threshold values; the System Services section of the page enables or disables monitoring of the specific services. To view the system services monitored, see the
“Services Monitor” section on page 5-32
.
Table 7-4 lists each threshold in the Performance Parameters section, and where each
threshold is monitored.
Table 7-4 Performance Thresholds
Threshold
Port Loss
Monitoring Page
The Network indicator box on the “System Health” section on page 5-2 .
Disk Loss The Disk indicator box on the
“System Health” section on page 5-2 .
Disk Capacity Notify The
“Disk Monitor” section on page 5-25 .
Disk Capacity Warning The
“Disk Monitor” section on page 5-25 .
Linux File System Usage The
“Disk Monitor” section on page 5-25 .
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
(
).
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
7-7
Server Maintenance
Figure 7-2 System Thresholds Page
Chapter 7 System Maintenance
Step 2
Step 3
Enter the threshold settings and enable or disable the services as appropriate.
Click Submit to save the settings.
To clear the fields and start over, click Reset.
To restore the default settings, click Restore. The default values are shown in a separate column on the page.
7-8
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
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-5
describes the different services.
Table 7-5 Restart Services Options
Service
Reload Bandwidth
Manager
RTSP
SNMP
Description
Optional feature. Any time there are changes to the Bandwidth Manager configuration, it is necessary to reload the bandwidth manager.
Any time there are changes to the RTSP Setup page, it is necessary to restart the RTSP nABLE service.
Any time there are changes to the SNMP configuration, it is necessary to restart the SNMP service.
To restart a service, do the following:
Step 1
Step 2
Step 3
Choose Maintain > Services. The Services Restart page is displayed.
From the Server IP 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.
Select the check box next to each service you want to restart and click Submit.
To clear the fields and start over, click Reset.
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 upload a topology file. This section covers the following topics:
•
Viewing the Software Version and Server Information
•
•
Identifying Server IDs and Group IDs for VVI with Split-Domain Management
Viewing the Software Version and Server Information
To view the TV CDS software version and server information, choose Maintain > Software > Software
Version. The Software Version page is displayed. From the Server IP drop-down list, choose the IP address or nickname of the server and click Display. The following information is displayed:
•
Server type (Vault, Streamer SSV (ISV))
•
•
Software version
Server ID
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01 7-9
Chapter 7 System Maintenance
Software Maintenance
•
•
•
•
•
Array ID
Product ID (PID)—CDE model (for example, CDE220)
Version ID (VID)—Hardware version (for example, V01)
Serial number—Serial number of the CDE
Additional string—Model variation (for example, 4A-C)
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
Before you can upload an EPG file, you need to enter the channel information. See the
Input Channels” section on page 4-24
for more information.
To upload an EPG file, do the following:
Step 1
Step 2
Step 3
Choose Maintain > Software > EPG Upload. The EPG File Upload page is displayed.
Enter the full path and filename in the EPG File Location field, or click Browse to locate the file using the Browse window.
After the full path and filename of the EPG File is entered, click Upload.
To clear the fields and start over, click Reset.
Identifying Server IDs and Group IDs for VVI with Split-Domain Management
The VVIM manages all the identifiers, and the Stream Managers get a range of group IDs and server IDs from the VVIM and uses them for the Streamers it manages.
Table 7-6 lists the CDSM GUI ID names and maps them to the CServer names in the setupfile and
.arroyorc files.
Table 7-6 ID Names in the CDSM GUI and CServer Files
CDSM GUI ID Name
Array ID on the Array Name page
Group ID on the Server-Level pages
Stream Group ID on the Server Setup page
CServer Files ID Name
groupid groupid arrayid
Cache Group ID on the Server Setup page
Vault Group ID on the Server Setup page arrayid arrayid
Stream Group ID on the Configuration Generator page arrayid
7-10
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 7 System Maintenance
Software Maintenance
Generating Server IDs and Group IDs from the VVIM
The Configuration Generator page is used to generate group IDs and server IDs for the Stream Managers.
When the Stream Manager contacts the VVIM during the initial configuration using the cdsconfig script, the VVIM generates the IDs, sends them to the Stream Manager, and populates the table on the
Configuration Generator page. This is done by an HTTP GET request over port 80.
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.
For HTTP streamers, if the Stream Manager is unable to reach the VVIM, either because port 80 is not open for communication or because of some other connectivity reason, the Stream Manager administrator can contact the VVIM administrator for the needed information. This information consists of the following:
•
Stream Group IDs
•
Cache Group information
Using the Configuration Generator page, the VVIM administrator can look up the group ID and server
ID ranges, and if necessary generate them. The VVIM administrator can provide the beginning group ID for the Stream Groups, which the Stream Manager administrator enters on the Stream Groups Setup page, if prompted to do so.
The Cache Group information is contained in an XML file, called CacheGroupsConfig.xml. The VVIM administrator can click the Download link to view the CacheGroupsConfig.xml file, and right-click the
Download link to save the XML file locally. This XML file can be sent to the Stream Manager administrator and the Stream Manager can upload it through the Cache Group Locator page.
To generate new IDs or view the existing IDs, do the following:
Step 1
Choose Maintain > Software > Configuration Generator. The Configuration Generator page is
).
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
7-11
Software Maintenance
Figure 7-3 Configuration Generator Page
Chapter 7 System Maintenance
Step 2
Step 3
Step 4
In the Stream Domain Name field, enter the name of the Stream Manager that you are generating IDs for.
In the Stream Manager IP field, enter the IP address of the Stream Manager that you are generating IDs for.
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.To generate the IDs, click the Not Generated text in the Stream Group ID Range column. A dialog box is displayed asking if you want to generate the IDs now. Click OK.
Stream Manager IP Address
The IP address of the Stream Manager is not included in the table on the Configuration Generator page until the Stream Manager is configured using the CDSM Setup page. It is possible that the Stream
Manager IP address failed to be captured, in which case the entry is displayed as “Not Captured.” Click the Not Captured link to enter the IP address manually. A text box is displayed with an Update icon
(plus sign) and a Cancel icon (X).
7-12
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Chapter 7 System Maintenance
Manuals
Setup ID Range
Setup IDs are only used in RTSP environments that have split-domain management and are using CCP
Streamers. The VVIM only generates two setup IDs for each Stream Domain. A setup ID is used to identify the Setup server in a Stream Group. The Setup and Control servers are configured for each
Stream Group on the Control/Setup IP page. See the
“Configuring the Control and Setup IPs” section on page 4-42
for more information. If the Stream Manager uses the two allotted setup IDs, it contacts the
VVIM for a new set of setup IDs. If the connection between the Stream Manager and VVIM fails, the
Stream Manager administrator contacts the VVIM administrator for the IDs. The new setup IDs can be generated by clicking the Generate new Setup ID range icon in the Setup ID Range column.
Note
CCP Streamers are not supported in a VVI split-domain management for RTSP environments.
Manuals
To view the manual, choose Maintain > Manuals. The Manual page is displayed. Click the link to the manual. The manual is displayed by means of the Acrobat Reader plug-in for your browser.
Tip
To download the manual to your computer, right-click the link of the manual and save the manual to a location on your hard drive for later viewing.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
7-13
Manuals
Chapter 7 System Maintenance
7-14
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
OL-22792-01
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. The topics covered in this appendix include:
•
•
•
•
•
•
Management and Database Issues, page A-22
Content Processing Issues, page A-28
•
•
•
•
•
Streaming and Playout Issues, page A-31
Advanced Features and Applications, page A-41
Frequently Asked Questions, page A-42
•
CDS Content Quality Guidelines, page A-47
There are a variety of possible combinations of CDS topologies, backoffice environments, middleware, and so on. The engineers using this troubleshooting appendix are expected to know their system well enough that they can extrapolate the relevant troubleshooting guidelines. With all connectivity issues, physical integrity of cables and ports should be verified, as well as VLAN configuration if applicable.
All Linux commands described in this appendix require console access to the server, or Secure Shell
(SSH) access to the server.
Caution
Do not attempt to access the Linux command line unless you are familiar with the CDS, the Linux operating system, and have an understanding of the Linux command line.
Note
It is important to verify at each step that the correct user account is being used. The root and isa user accounts are the only ones required to manipulate the files. The root user account uses the # symbol as a prompt. The isa user account uses the $ symbol as a prompt. We strongly recommend that you change these passwords as soon as possible by using the passwd command.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
A-1
Appendix A Troubleshooting
General Issues
General Issues
This section describes the CDS file system, log files, configuration files, and general troubleshooting methods. This section includes the following:
•
•
•
•
•
•
Identifying the Software Versions or Releases
Using ifstats to Monitor Traffic
•
•
•
File System
The CDSM file system differs from the file system on the other servers (Vault, Streamer, 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. The asm_archiver job must be installed and added to the crontab for these files to be generated. For more information, see the
“Archived Data” section on page 6-25
.
/arroyo/db—Contains the database binaries, this roughly maps to the /home/isa/Berkeley directory on Streamers and Vaults.
•
•
•
•
•
•
/arroyo/db/DATADIR—Contains the database files and indexes.
/arroyo/image—The staging area for CDS software image files. This directory also includes backup directories when a software upgrade is performed on the server.
/arroyo/msa—Contains the Managed Services Architecture (MSA) logs that are created by extracting information from the database. The logs are processed by the iVAST MSA agent.
/arroyo/www—Contains the HTTP files for the CDSM GUI. The subdirectory arroyo/www/htdocs, contains the PHP files for the CDSM GUI.
/arroyo/www/modules—The link library for htdocs files.
/home/isa/—Contains configuration and log files.
Report Archiving
The CSV files are generated every 24 hours and are deleted when they are older than 30 days. The CSV files are stored in the /arroyo/asmrpt directory. For the CSV files to be generated, the report archiver needs to be installed and configured. 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.”
A-2
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix A Troubleshooting
General Issues
Vault, Streamer, and ISV
The Vault, Streamer, and ISV have the following directory structures:
•
/arroyo/db
•
•
/arroyo/log
/arroyo/test/
•
•
•
•
•
In addition to the above directories, the Vault, Streamer, and ISV have the following directories specific to the RTSP environment:
•
/home/isa/bss
•
/arroyo/archive
/home/isa
•
/home/isa/bss/bin—Contains the VOD server binaries
/home/isa/bss/database—Contains the database files
/home/isa/bss/etc—Contains the configuration files for the binaries
/home/isa/bss/lib—Contains the shared application libraries
•
•
•
/home/isa/bss/log—Contains the application log files
/home/isa/bss/log/archive—Contains the archived log files
/home/isa/bss/run—Contains process ID (PID) files for running the application
/home/isa/bss/scripts—Contains general scripts
Log Files
There are three types of log files in an RTSP environment:
•
•
•
The CServer log files are automatically archived and moved to the /arroyo/archive directory when the disk storage reaches a certain level. The RTSP log files are automatically archived and moved to the
/home/isa/bss/log archive directory whenever the FSI or RTSP process is restarted, or the log file reaches close to 50 MB. A total of nine revisions are kept of each log file, with the eight oldest being compressed and moved to the archive directory.
Linux Log Files
The Linux operating system has the following useful log files:
•
/var/log/debugmessages—Syslog messages
•
/var/log/messages—Includes useful bootup status messages
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
A-3
Appendix A Troubleshooting
General Issues
CServer Log Files
The CDS has the following useful log files:
•
/arroyo/log/c2k.log.<date>—This log has information about content read issues. The date extension for the log filename has the format of yyyymmdd (for example, 20090115 is January 15, 2009). To increase the verbosity of this log file, use the following command:
# echo "6" > /proc/calypso/tunables/c2k_verbosedump
•
•
•
•
•
•
•
•
/root/avslauncher.log.<date>—Provides information about the startup of the avslauncher module.
Other CServer log files that may be useful are the following:
•
•
•
•
/arroyo/log/protocoltiming.log.<date>—Provides information about any network interface issues and any disk issues.
/arroyo/log/avsdb.log.<date>—Provides information about any database issues.
/arroyo/log/statsd.log.<date>—Provides system statistics information.
/arroyo/log/stresstest.log.<date>—Provides CPU uptime information.
/arroyo.log/controlblocktiming.log.<date>
/arroyo.log/debug.log.<date>
/arroyo.log/decommissioned.log.<date>
/arroyo.log/deleted.log.<date>
•
•
/arroyo.log/executiontiming.log.<date>
/arroyo.log/objectRepair.log.<date>
/arroyo.log/serverinfo.log.<date>
/arroyo.log/streamevent.log.<date>
/arroyo.log/systemstats.log.<date>
Note
The files with the extension <date> use the format yyyymmdd. The date is the Coordinated Universal
Time (UTC) date.
CServer Error Codes
CServer error codes that appear in the c2k.log.<date> file do not necessarily mean an error has occurred.
An actual error has “err” listed in the entry, as opposed to “out” or “ntc.” Following is a list of important
CServer error and status codes:
Error Codes
•
5—Completion of a task.
•
25—Insufficient resources.
Status Codes
•
0—Content is okay (cnOK).
•
•
•
1—Stream has ended (cnEnd).
2—Stream has been paused (cnPaused).
3—Error has occurred (cnError).
A-4
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix A Troubleshooting
General Issues
•
•
•
•
•
•
4—Next element is being processed (cnNextElement).
5—Live content has resumed (cnResumeLive).
6—Next content object is being processed (cnNextContent).
7—Next iteration is being processed (cnNextIteration).
9—There has been a failover (cnFailover) .
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 bus hold offs
System bus is overloaded or network transmissions are not occurring fast enough and transmission of data is being delayed. The counts following these numbers may be low, this is not a concern because the delay is only 2 microseconds (ms). However, if the counts are high, this can cause stream data delivery problems.
WARNING: Fill Data
Wait
Vault or Caching Node is unable to deliver data to a waiting Caching Node or Streamer because the data is not yet available. If the numbers are low, this is not a concern because the delay is only
2 ms. If the counts are high, this can cause stream data delivery problems.
WARNING Data Low
WARNING: Disk
Refetches
WARNING: No capacity
5 percent
Data being streamed has less than 100 ms buffered ahead of the current stream point. Normally there should be a 2-second elasticity buffer for data being transmitted, except for a short interval when the stream first starts and the data is still “bursting” to fill the elasticity buffer. There are no problems as a result of this warning, but it is a precursor to the Fill Data Wait warning.
Warning does not indicate any problems with streaming content, just that the disk bandwidth was not being used as efficiently as possible.
Server was not accepting any new requests, which were sent to it during five percent of the preceding ten-second sample period, because it was out of capacity. Other statistics in the protocoltiming log need to be examined to determine why the server determined it was out of capacity. If Caching Nodes or Streamers are unable to find an alternate server to provide the data they need, a stream failure may occur.
WARNING: Cannot stripe disk writes
Indicates one of the following two conditions:
•
Some disk drives are completely full and data can no longer be written to them.
WARNING: Mirror
Recovery degraded - some remote vaults (0:1) are inaccessible
•
The disk system is under a full-bandwidth load such that some drives are fully committed to reading stream data and are never getting any time to write data to the drive.
The data storage pattern is not efficient when this happens because the data can no longer be spread equally across all the drives. Check other load statistics to determine why the disk system cannot stripe to some drives is useful in determining why these warnings are occurring.
The configured mirroring has not occurred because 1 or more required Vaults are down, or a partner Vault is up but configured to be in a different Vault Group.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
A-5
Appendix A Troubleshooting
General Issues
RTSP Log Files
The Linux user isa is the owner of the application files in an RTSP environment. To change from the root use the su – isa command.
All application log files are located in /home/isa/bss/log directory. When a log file reaches around
50 MB in size, it is archived and moved to the archive directory. When the RTSP or FSI is restarted, all current log files are archived and moved to the archive directory. The latest archived log files remain uncompressed, while the rest are gzipped. The archive directory always maintains the ten latest archives of each log file. The older log files are deleted.
If the RTSP application or the FSI application does not start, check the following files for possible reasons:
•
rtsp.err
•
•
rtsp.out
fsi.err
•
fsi.out
These files are located in the /home/isa/bss/log/ directory.
The CDS RTSP environment has the following useful log files:
•
/home/isa/bss/log/fsi.log
•
•
/home/isa/bss/log/rtsp.log
/home/isa/bss/log/aim.log
•
/home/isa/bss/log/library.log—Logs the cache2app library information
To change the log levels while the RTSP application is not running, edit the arroyo-env.sh file.
$ cd /home/isa/bss/scripts/
$ vi arroyo-env.sh
Change the value for the ARROYO_LOG_LEVEL variable to OFF, LOW, or HIGH. The default setting is LOW.
To change the log level whether the RTSP application is running or not, use the RTSP Setup page. For more information, see the
“Configuring RTSP Setup” section on page 4-75 .
Log File—rtsp.out
The rtsp.out log file stores the processing state and associated session ID of each thread.
The thread state logging is controlled by the THREAD_MON_FREQ in the arroyo-env.sh script in the
/home/isa/bss.scripts directory. The THREAD_MON_FREQ parameter is used as a time interval to print the thread state and the corresponding value, which could range from 0 to 65535. The default value for the THREAD_MON_FREQ parameter is 30. The logging can be turned off by setting
THREAD_MON_FREQ to 0.
Following is an example of the rtsp.out log file:
13 Apr 2010 23:06:36,407002|Thread named ThreadPoolThread0 is PROCESSING request with sessionid : 172452576
13 Apr 2010 23:06:36,407113|Thread named ThreadPoolThread1 is PROCESSING request with sessionid : 242353532
13 Apr 2010 23:06:36,407149|Thread named ThreadPoolThread2 is NOT PROCESSING any requests
13 Apr 2010 23:06:36,407184|Thread named ThreadPoolThread3 is NOT PROCESSING any requests
13 Apr 2010 23:06:36,407220|Thread named ThreadPoolThread4 is NOT PROCESSING any requests
13 Apr 2010 23:06:36,407255|Thread named ThreadPoolThread5 is NOT PROCESSING any requests
A-6
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix A Troubleshooting
General Issues
Server Configuration Files
The server configuration settings are stored in the .arroyorc file and the setupfile file. This section describes the different parameters for each file.
Note
This section is informational only. All changes to the configuration files should be accomplished through the initial configuration and CDSM GUI.
Table A-2 lists the CDSM GUI ID names and maps them to the CServer names in the setupfile and
.arroyorc files.
Table A-2 ID Names in the CDSM GUI and CServer Files
CDSM GUI ID Name
Array ID on the Array Name page
Group ID on the Server-Level pages
CServer Files ID Name
groupid groupid
Stream Group ID on the Server Setup page
Cache Group ID on the Server Setup page arrayid arrayid
Vault Group ID on the Server Setup page arrayid
Stream Group ID on the Configuration Generator page arrayid
Description of the .arroyorc Settings
This section describes the different line entries of the .arroyorc file. The .arroyorc file is located in the
/home/isa directory and is created during the initial configuration procedure outlined in the Cisco
Content Delivery Engine 205/220/420 Hardware Installation Guide.
self
This number represents what type of server the CDE is:
•
•
•
•
0 = ISV (also known as SSV)
1 = Vault
2 = Streamer
3 = CDSM
groupid
All servers that are part of the same CDS system (managed by one CDSM) have the same group ID. This group ID should be unique across an enterprise. The purpose of the group ID is to allow servers in a group to recognize each other as belonging to the same group. If two server groups were on the same
VLAN and they had the same group number they would conflict and cause issues. This is much more likely to be an issue in a lab environment with shared resources than an actual production deployment but this should still be managed.
serverid
Every server in the group has to have a unique ID ranging from 1 to 255. It is a good idea to use a standardized numbering solution; for example, all 1xx serverids are Streamers and all 2xx server IDs are
Vaults.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
A-7
Appendix A Troubleshooting
General Issues vault
This parameter has the IP address of a Vault in the system. Each “vault” line represents an individual
Vault. There may be multiple vault lines.
streamer
This is the IP address of a Streamer in the system. Each “streamer” line represents an individual
Streamer. There may be multiple streamer lines.
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. The CDSM can then display the appropriate server graphic in the GUI and manage the appropriate number of disks, Ethernet ports, and so on.
mgmtif
The index of the management interface starting at eth0. Typically this remains 0.
ingestif
This parameter is only for Vaults. The index of the ingest interface starting at eth0. Typically this remains 0 but may have the value of 1 as well.
dbdomsock
This is the “file handle” where the applications address messages intended for the database.
dbnetport
This is the port number where the applications address messages intended for the database.
controlif
The index of the stream control interface starting at eth0. This is an optional configuration that is used when you want to separate the Setup and Control interface.
Description of the setupfile Settings
This section describes the different parameters of the setupfile file. The setupfile file is located in the
/arroyo/test directory. Some values for the parameters in the setupfile file are set during the initial configuration (serverid, groupid, streamer vault), others are set by using the CDSM.
Note
The localip # line entry has been deprecated. Ignore this line entry.
A-8
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix A Troubleshooting
General Issues
Required Settings
The following line entries are required in every setupfile file:
serverid #
An identifier that uniquely identifies the server within a group of servers identified by the group ID. See the
“serverid” section on page A-7 for more information.
groupid #
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.
service address <ip in dot notation> setup <setup portno> control <control portno>
The service address is used to specify whether this server can assume the role of the Setup server, the
Control server, or both the Setup and Control servers for the specified IP address. This parameter applies only to Streamers.
•
•
setup portno—A value of 0 means the server is not available to assume the role of the Setup server for the specified IP address. A value of 1 means to use the default port number 3300.
control portno—A value of 0 means the server is not available to assume the role of the Control server for the specified IP address. A value of 1 means to use the default port number 9000.
e1000 <index>: streaming <0 or 1> fill <0 or 1> ip <ip in dot notation> tport <transport portno> cport <cache portno> tgid <transport groupid>
The e1000 is used to configure the network interfaces for cache-fill and transport/streaming. Each
“e1000” line represents an individual Ethernet port. Include one line per interface.
•
index—Refers to the interface index as known to the e1000 driver. In the case of servers with the
Lindenhurst chipset, this matches one for one with the number for the eth# interface.
•
streaming—For transport/streaming. A value of 1 means this interface is used for streaming, otherwise set streaming to 0.
•
fill—For cache fill. A value of 1 means this interface is used for cache fill. Otherwise, set fill to 0.
•
•
ip—Each interface requires a source IP address. This assumes Layer 3 networks only.
tport—The transport port number used as the source in transporting (streaming) packets. A value of 0 means to use the default port number 1026 (unless affected by the optional default source IP entry).
•
•
cport—The cache port number used as the source in caching (fill) packets. A value of 0 means to use the default port number 48879 (unless affected by the optional default source IP entry).
tgid—The transport group ID for this interface. The transport group ID is used in conjunction with the TransportGroupIdTable file located in the /arroyo/test directory to determine which interface to use to transport the packet. This is based on destination IP address or subnet of the packets. The default value is 0, which means this interface is available to any transport group. Any other value means the interface is dedicated to a particular transport group.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
A-9
General Issues
Appendix A Troubleshooting vault mirror copies <number of copies>
The Vault mirror copies is a numeric value representing the number of copies of each content to store on the Vaults.
Note
The transport group ID (tgid) has been deprecated. Use the SubnetTable instead. See the
“Network” section on page A-18
.
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.
e1000 adapters: maxrate <rate in Mbps>
Controls the maximum transmit bandwidth on this interface, either for streaming, for caching, or for both. The default is 975 Mbps.
ibg adapters
The maximum transmit bandwidth of the ibg adapters. The default is 975 Mbps.
disks #
Specifies the number of hard drives (disks) installed on a server. The default is 12 disks for a Streamer, and 24 disks for a Vault. If you have a server with 12 disks, you must add this entry and specify 12 disks; otherwise, warning messages stating disks are non-operational are logged to the protocoltiming log file.
test #
Specifies the test mode of the server. The default is 4, which means to run the server in production mode.
cache_dscp #
Used to set the DSCP bits on cache-fill packets. The default value is 0.
cache_ecn #
Used to set the ECN bits on cache-fill packets. The default value is 0. This parameter should not be used.
transport_dscp #
Used to set the DSCP bits on transport/streaming packets. The default value is 0.
transport_ecn #
Used to set the ECN bits on transport/streaming packets. The default value is 0. This parameter should not be used.
A-10
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix A Troubleshooting
General Issues trickspeedsv2 # # # # # # # #
Used to specify up to 8 speeds for generating trick objects during ingest. This parameter is applicable only to Vaults. The defaults are 5, –5, 10, –10, 32, and –32. The highest speeds are –127. An entry larger than 127 defaults to 127. A value of 0 is ignored.
ftpout if eth # max utilization mbps # max sessions #
Used to specify which interface on the Vault is used for FTP Out, the maximum bandwidth utilization for all active sessions (in Mbps), and the maximum number of simultaneous sessions allowed. By default the maximum sessions is 0, meaning that FTP Out is not allowed. The default for bandwidth utilization is 0, which means unlimited usage. The default interface selected is the management interface. For FTP
Out to function properly, the entire content must exist on the Vault.
bypass_isacheck <0 or 1>
Used in the RTSP environments to bypass global object ID (GOID) checks at startup.
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. The selection is based on the destination IP address or subnet of the packets. The default value is 0.
remote site manager <ip address> for arrayid #
Specifies the IP address of a remote site manager for a specified array. The remote site manager has a list of all the servers that it can connect to that are located at the same site (the servers are listed in the
RemoteServers list on the remote site manager). When this server comes up, it contacts the remote site manager and asks for a referral for a server that is in the specified array. The remote site manager returns the IP address of a server from that array. This server sets up connections with all the referred remote servers, and once every minute, checks to see if there are connections with all remote array servers. If for some reason one is not available, this server contacts the remote site manager for another referral.
Note
You must add the allow new L3 remote servers 1 directive to the setupfile for both this server and the server that gets referred. If you do not add this directive, this server cannot establish a connection with the referred remote server.
default source ip <ip in dot notation> tport <minportno> - <maxportno> cport <portno>
Used to affect source packets if no specific information is provided in the individual mandatory e1000 interface entries.
•
•
ip—The default source IP address for an interface. This value is overridden by the mandatory e1000 interface entry. This IP address is not meaningful in a Layer 3 network. However, today it must have a non-zero value for the other values to be looked at.
tport—After a stream is started, a random port within the range specified is used as the source port for transport/streaming packets of the stream (assuming no specific port was selected for tport in the mandatory e1000 interface entries).
•
cport—The source port to use for cache-fill packets (assuming no specific port was selected for cport in the mandatory e1000 interface entries).
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
A-11
Appendix A Troubleshooting
General Issues
Note
The default source IP is useful in a Layer 2 network. For Layer 3 networks, an IP address is required for each interface, so the value in the default source IP is superseded by the individual entries for the interfaces. However, the default source IP setting specifies other defaults
(transport port and cache port). If you would like to specify a range of transport ports, then the default source IP could have a value of zero.
Note
The default source IP can be used in conjunction with the mandatory e1000 interface entries. For example, the default source IP can be used to specify a range for the source transport port.
However, the generation of a random port does not currently work on every stream start.
Therefore, it is best not use this option.
bms address <ip> <port>
The IP address and port of the backoffice.
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 ([email protected]) (gcc version
4.1.2 20071124 (Red Hat 4.1.2-41)) #1 SMP Tue Apr 29 13:16:15 EDT 2008
To identify the software version of the Linux OS on the Vault, Streamer, or ISV, enter the following commands:
# cat /proc/version
Linux version 2.6.18-53.el5.kernel.2_6_18.2008.10.07.01 (arroyoqa@build-svr) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Mon Nov 17 18:21:51 PST 2008
# uname -a
Linux stm74 2.6.18-53.el5.kernel.2_6_18.2008.10.07.01 #1 SMP Mon Nov 17 18:21:51 PST
2008 i686 i686 i386 GNU/Linux
CDS-Related Releases
The RTSP CDS software is a combination of an RTSP overlay, statsd software, and the CServer code.
The following sections describe how to identify the software version of each.
RTSP Environment
To identify the software version of the CDS RTSP overlay image, enter the following command:
# cat /arroyo/image/tags linux/linux kernel-2_6_18-2009-01-15-01 snmp/statsd statsd-2009-01-14-03 snmp/agent.531 snmpd-2009-01-16-01
A-12
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix A Troubleshooting
cserver cserver-e013-2009-01-16-06 export export-e013-2008-10-06-01 avsdb avsdb-2009-01-06-01 cache2app r_2_0v1-isa-e008-2009-01-15-01 isa r_2_0v1-isa-e008-2009-01-15-01 bss bss-r20-2009-01-15-01 avslauncher avslauncher-2009-01-13-01 framework frmwk-r20-2008-10-28-02 tavsdb tavsdb-2009-01-14-01 ui/http/httpd-2.2.9 asm-2008-09-21-01 ui/http/php-5.2.6 asm-2009-01-13-01 ui/http/www/R25 CDSM-1-15-2009 upscripts upgrade-2009-1-8-01 packager 1 flav_inst 1
statsd Program
General Issues
To identify the software version of the statsd program, enter the following command:
# strings /home/stats/statsd |grep Rel
STATSD Release TOP_OF_TREE (arroyoqa@build-svr) (gcc version 4.1.2 20070626 (Red Hat
4.1.2-14)) #1-Nstatsd-2008-11-07-02 Mon Nov 17 18:34:15 PST 2008
CSserver Code
To identify the software version of the CServer on the Streamer, Vault, or ISV, enter the following command:
# strings avs_cserver.ko |grep CServer
Average setup time spent in CServer =
AVS CServer Release #1-Ncserver-e013-2008-11-17-05 Mon Nov 17 18:54:01 PST 2008
ENV_ISA_SR DEBUG
AVS CServer Information ENV_ISA_SR DEBUG (arroyoqa@build-svr) (gcc version 4.1.2
20070626 (Red Hat 4.1.2-14)) #1-Ncserver-e013-2008-11-17-05 Mon Nov 17 18:54:01 PST
2008
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.2-14))
#1-Ncserver-e013-2009-01-20-03 Tue Jan 20 17:54:28 PST 2009
Server Settings:
Server is operational
Cache2App is operational
TSCs Per Second is 2333447000
Network Settings:
Running in L3 Network Mode
Allow Jumbo Frames
Transport/Stream Data Payload: 1316
Cache/Fill Data Payload: 7680
Cache/Fill Control Maximum Packet Size: 8048
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
A-13
Appendix A Troubleshooting
General Issues
Using ifstats to Monitor Traffic
The ifstats command shows real-time traffic on each Ethernet interface on the server.
# /home/stats/ifstats ifstats - 11:12:22
============================================================
Int# R-Mbps X-Mbps R-Bytes X-Bytes
eth0 0 0 56760511 166307653
eth1 0 0 0 0
eth2 4 457 3439241508 3497139080
eth3 4 457 3439172148 3099124288
eth4 4 457 3441836680 2945489644
eth5 4 472 3443060380 2736115618
eth6 4 471 3438423816 2613199736
eth7 5 464 3440066492 2419935662
eth8 4 449 3439982812 2266582156
eth9 4 465 3443251384 2164010982 eth10 5 465 3439982136 1915437726 eth11 4 464 3438935192 397577442 eth12 5 464 3440343164 300903930 eth13 4 465 3439540716 4454799830
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. The kdump service runs automatically if the server is configured to reboot automatically after a crash (which means the panic parameter is non-zero). The kdump service stores the kernel memory dump in the /var/arroyo/crash directory. After the kernel memory is dumped, the system reboots into the normal operating system.
If the server is configured to enter KDB (which means the panic parameter is zero), the server enters
KDB mode. The kdump command allows you to take a kernel memory dump while the server is in KDB mode. The kdump command reboots the server into kdump mode, takes a kernel memory dump, and reboots the server into the normal operating system.
If a server has crashed after being started automatically from the /etc/rc.local directory, you need to boot in single-user mode. To boot in single-user mode, perform the following steps:
Step 4
Step 5
Step 6
Step 7
Step 8
Step 1
Step 2
Step 3
Reboot the server.
When a blue screen displays a list of Linux versions, press the E key to edit the kernel entry.
Multiple lines are displayed. Use the Up Arrow and Down Arrow keys to highlight the second line. You may need to press the E key again to edit the line. A square cursor appears at the end of the line.
Remove the 115200 from the console parameter (for example, console=ttySO,115200n8).
Add the word “Single” or the letter “S” to the end of the line.
Press Enter.
Press the B key to boot the Linux kernel into single-user mode.
Wait for the server to finish booting up.
A-14
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix A Troubleshooting
Step 9
Step 10
Edit the /etc/rc.local file and comment out the line /arroyo/test/vault/run.
Reboot the server.
General Issues
To view the contents of the core dump file from the Linux prompt, do the following:
Step 1
Step 2
Run the GNU debugger (gdb), and specify the core file and binary file.
gdb --core=<
core-file> <binary-file>
The core-file parameter is the core filename and the binary-file is the binary file that produced the core file.
After the GNU debugger has started, enter the backtrace command, bt, at the gdb prompt and press
Enter. gdb> bt
The callback stack is displayed, which shows the history of the current function calls that were made at the time of the crash.
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.
# df -k
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/hda1 10317828 3764936 6028776 39% /
/dev/hda2 20641788 1711372 17881776 9% /arroyo
/dev/hda3 8254272 32828 7802148 1% /arroyo/db
/dev/hda6 35641880 1185880 32645480 4% /arroyo/log none 1681200 0 1681200 0% /dev/shm
To view the statistics of a removable SATA or SCSI disk drive, use the following commands:
# cat /proc/calypso/status/streamer/diskinfo
Disk Info:
Disks(12) Op(12)
Storage: T(804G) A(21%) U(0)
BW: (99%) w(1.35M/s) r(0/s)
I/O Util: w(1:0%) e(0) a(0%)
Disk[ 1][67.0G] A[20%] B[11x]
Disk[ 2][67.0G] A[20%] B[0x]
Disk[ 3][67.0G] A[21%] B[0x]
Disk[ 4][66.5G] A[22%] B[0x]
Disk[ 5][67.0G] A[20%] B[0x]
Disk[ 6][67.0G] A[21%] B[0x]
Disk[ 7][67.0G] A[20%] B[0x]
Disk[ 8][67.0G] A[20%] B[0x]
Disk[ 9][67.0G] A[21%] B[0x]
Disk[10][67.0G] A[20%] B[0x]
Disk[11][67.0G] A[20%] B[0x]
Disk[12][67.0G] A[20%] B[0x]
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
A-15
Appendix A Troubleshooting
General Issues
CDSM GUI Disk Monitor Page Reports a Disk Warning
If the CDSM GUI Disk Monitor page reports a disk warning, check the disk drive status in the
/arroyo/log/protocoltiming.log.<date> log file and the /var/log/debugmessages log file.
# grep drives /arroyo/log/protocoltiming.log.11132007
WARNING: 5 disk drives are non-operational
WARNING: 5 disk drives are non-operational
...
WARNING: 5 disk drives are non-operational
WARNING: 5 disk drives are non-operational
# grep disks /var/log/debugmessages
Nov 20 19:02:44 vault219 kernel: RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
Nov 20 19:03:34 vault219 kernel: Waiting for 2 disks to finish initializing
Nov 20 19:03:34 vault219 kernel: Waiting for 4 disks to finish initializing
Nov 20 19:03:35 vault219 kernel: Waiting for 3 disks to finish initializing
Nov 20 19:03:36 vault219 kernel: Waiting for 2 disks to finish initializing
Nov 20 19:03:36 vault219 kernel: Waiting for 1 disks to finish initializing
Nov 20 19:03:36 vault219 kernel: Waiting for 5 disks to finish initializing
Nov 20 19:03:42 vault219 kernel: Waiting for 6 disks to finish initializing
Nov 20 19:03:42 vault219 kernel: Waiting for 5 disks to finish initializing
Nov 20 19:03:43 vault219 kernel: Waiting for 4 disks to finish initializing
Nov 20 19:03:45 vault219 kernel: Waiting for 11 disks to finish initializing
Nov 20 19:03:46 vault219 kernel: Waiting for 10 disks to finish initializing
Nov 20 19:03:46 vault219 kernel: Waiting for 9 disks to finish initializing
Nov 20 19:03:46 vault219 kernel: Waiting for 8 disks to finish initializing
Nov 20 19:03:47 vault219 kernel: Waiting for 7 disks to finish initializing
Nov 20 19:03:47 vault219 kernel: Waiting for 6 disks to finish initializing
Nov 20 19:03:48 vault219 kernel: Waiting for 5 disks to finish initializing
Nov 20 19:03:48 vault219 kernel: Waiting for 4 disks to finish initializing
Nov 20 19:03:48 vault219 kernel: Waiting for 3 disks to finish initializing
Nov 20 19:03:48 vault219 kernel: Waiting for 2 disks to finish initializing
Nov 20 19:03:48 vault219 kernel: Waiting for 1 disks to finish initializing
Nov 20 19:03:50 vault219 kernel: Total disk space = 24.0TB on 24 disk drives (Lost disks = 0)
Note
Sometimes on the CDE400, the bus and host resets are used to reset the SATA driver because the Linux
SATA driver, sats_mv.ko, does not provide a device reset vector. If the device is reset when there are no outstanding requests, warning messages are displayed on the console. These warning messages are informational and do not indicate a failure.
A-16
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix A Troubleshooting
General Issues
Memory Issues
To slow down the CDSM bootup to see the memory counter, do the following:
Step 1
Step 2
Reboot the server.
To enter the BIOS Setup Utility, press the Delete key on your keyboard when you see the following text prompt:
Press DEL to runSetup
Note
In most cases, the Delete key is used to invoke the setup screen. There are a few cases where other keys are used, such as F1, F2, and so on.
Step 3
Step 4
Step 5
Use the Right Arrow key to navigate to the Boot menu.
Choose the Boot Settings configuration option (
Choose Quick Boot and set it to Disabled.
Figure A-1 BIOS Setup Utility—Boot Settings
OL-22792-01
Step 6
Press F10 to save and exit the BIOS Setup Utility.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
A-17
Appendix A Troubleshooting
General Issues
Network
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.170) at 00:30:48:58:5B:A1 [ether] on eth0 cds17-v1.v.com (111.0.210.171) at 00:30:48:31:53:B2 [ether] on eth0
? (111.0.210.175) at 00:30:48:32:0A:5A [ether] on eth0 cds17-s1.v.com (111.0.210.172) at 00:04:23:D8:89:44 [ether] on eth0 cds17-s1.v.com (111.0.210.172) at 00:04:23:D8:89:44 [ether] on eth0
To view the IP routing table, enter the following command:
# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
111.0.210.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
111.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 111.0.210.1 0.0.0.0 UG 0 0 0 eth0
To view the CDS subnet table, enter the following command:
# cat /arroyo/test/SubnetTable network 111.1.13.1 netmask 255.255.255.240 gateway 111.1.13.1 transport_source_ip 0
A-18
Note
In Release 2.1, the local networks and their gateways are specified in the SubnetTable file. For backward compatibility, the local subnet and gateway in the RoutingTable are still supported and are used if the
SubnetTable file does not exist. The Routing Table can still be used to specify static routes.
To view the CDS routing table, enter the following command:
# cat /arroyo/test/RoutingTable default gateway 111.1.13.1
network 111.1.13.1 netmask 255.255.255.240 gateway 0.0.0.0
To view the CDS remote server table, enter the following command:
# cat /arroyo/test/RemoteServers remote server id 141 ip 111.1.9.20
ip 111.1.9.21
ip 111.1.9.22
ip 111.1.9.23
ip 111.1.9.24
end remote server remote server id 143 ip 111.1.9.25
ip 111.1.9.26
end remote server remote server id 144 ip 111.1.9.27
ip 111.1.9.28
ip 111.1.9.29
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix A Troubleshooting
General Issues
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.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13946269 errors:0 dropped:0 overruns:0 frame:0
TX packets:11594110 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3085199261 (2942.2 Mb) TX bytes:1317620721 (1256.5 Mb)
Interrupt:24 Base address:0x3000 Memory:dd240000-0
For detailed interface information, view the interface information file in the /proc/net/ directory.
# cat /proc/net/PRO_LAN_Adapters/eth0.info
Description Intel® Gigabit Ethernet Network Connections
Part_Number ffffff-0ff
Driver_Name igb
Driver_Version 1.2.22-CDS
PCI_Vendor 0x8086
PCI_Device_ID 0x10a7
PCI_Subsystem_Vendor 0x15d9
PCI_Subsystem_ID 0x10a7
PCI_Revision_ID 0x02
PCI_Bus 14
PCI_Slot 0
PCI_Bus_Type UNKNOWN
PCI_Bus_Speed UNKNOWN
PCI_Bus_Width UNKNOWN
IRQ 194
System_Device_Name eth0
Current_HWaddr 00:30:48:C3:26:9E
Permanent_HWaddr 00:30:48:C3:26:9E
Link up
Speed 1000
Duplex Full
State up
Rx_Packets 406625
Tx_Packets 135553
Rx_Bytes 41539919
Tx_Bytes 30390314
Rx_Errors 0
Tx_Errors 0
Rx_Dropped 0
Tx_Dropped 0
Multicast 236747
Collisions 0
Rx_Length_Errors 0
Rx_Over_Errors 0
Rx_CRC_Errors 0
Rx_Frame_Errors 0
Rx_FIFO_Errors 0
Rx_Missed_Errors 0
Tx_Aborted_Errors 0
Tx_Carrier_Errors 0
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
A-19
Startup Issues
Tx_FIFO_Errors 0
Tx_Heartbeat_Errors 0
Tx_Window_Errors 0
Tx_Abort_Late_Coll 0
Tx_Deferred_Ok 0
Tx_Single_Coll_Ok 0
Tx_Multi_Coll_Ok 0
Rx_Long_Length_Errors 0
Rx_Short_Length_Errors 0
Rx_Align_Errors 0
Rx_Flow_Control_XON 0
Rx_Flow_Control_XOFF 0
Tx_Flow_Control_XON 0
Tx_Flow_Control_XOFF 0
Rx_CSum_Offload_Good 406625
Rx_CSum_Offload_Errors 0
PHY_Media_Type Copper
PHY_Cable_Length Unknown Meters (+/- 20 Meters)
PHY_Extended_10Base_T_Distance Unknown
PHY_Cable_Polarity Normal
PHY_Disable_Polarity_Correction Enabled
PHY_Idle_Errors 0
PHY_Receive_Errors 0
PHY_MDI_X_Enabled MDI
PHY_Local_Receiver_Status OK
PHY_Remote_Receiver_Status OK
Appendix A Troubleshooting
Startup Issues
This section includes the following topics:
•
•
•
BIOS Settings—Operating System Hangs or Goes into KDB Mode
Required Services Not Starting or Running Correctly
BIOS Settings—Operating System Hangs or Goes into KDB Mode
When a single bit error occurs in the memory of a server, it causes the Linux OS to lock up, which puts the server into kernel debugger (KDB) mode. This is because of the BIOS Error Correcting Code (ECC)
Type being set incorrectly.
To correct the ECC Error Type setting in the BIOS Setup Utility, do the following.
Step 1
Step 2
Step 3
During the server bootup, press the Delete key to enter the BIOS Setup Utility.
Navigate to the Advanced menu and choose Advanced Chipset Control.
Choose ECC Error Type and change the setting to NMI (
).
A-20
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix A Troubleshooting
Figure A-2 BIOS Setup Utility—Advanced Chipset Control
Startup Issues
Step 4
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. In the BIOS Setup Utility, check that the Console Redirection in the
Advanced menu is set to VT100.
•
•
/etc/boot/menu.lst—Determines the speed after the kernel is loaded.
/etc/inittab—Determines the speed after the OS is loaded. Enter the following:
$ cat /etc/inittab | grep S0
S0:2345:respawn:/sbin/agetty ttyS0 115200 vt100
Note
The CDE100 may have the following serial console settings: 9600 baud rate, no parity, 8 data bits, and
1 stop bit (9600-N-8-1).
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
A-21
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-32
. 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.0:9999 0.0.0.0:* LISTEN tcp 0 0 172.22.97.193:9999 172.22.97.197:56998 ESTABLISHED tcp 0 0 172.22.97.193:34743 172.22.97.197:9999 ESTABLISHED tcp 0 0 172.22.97.193:9999 172.22.97.192:50343 ESTABLISHED tcp 0 0 172.22.97.193:39158 172.22.97.196:9999 ESTABLISHED tcp 0 0 172.22.97.193:46030 172.22.97.192:9999 ESTABLISHED tcp 0 0 172.22.97.193:9999 172.22.97.196:55780 ESTABLISHED tcp 0 0 172.22.97.193:9999 172.22.97.191:50950 ESTABLISHED tcp 0 0 172.22.97.193:60598 172.22.97.191:9999 ESTABLISHED tcp 0 0 172.22.97.193:9999 172.22.97.194:37543 ESTABLISHED tcp 0 0 172.22.97.193:56376 172.22.97.194:9999 ESTABLISHED
Two connections for each Vault and Streamer should be listed with a status of “ESTABLISHED.”
If the connection states do not say “ESTABLISHED,” check the configuration of /home/isa/.arroyorc file to make sure the settings are correct, then restart the database.
Log in to the server as isa and start the database.
$ arroyo start avsdb
Log into the server as root and start the statsd.
$ /home/stats/statsd
Check that the RTSP listener is running on the correct port.
$ arroyo status
$ netstat -an | grep 554
Management and Database Issues
This section includes the following topics:
•
•
•
•
CDSM GUI Does Not Register the Vaults and Streamers
System Health
The colored boxes on the System Health Monitor page have the following meaning:
•
•
•
Green—All components are operating; occasionally click each check box to verify.
Yellow—Some components are not operational.
Red—All components have failed.
A-22
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
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.
# ps -aef | grep http root 4023 1 0 Aug09 ? 00:01:44 /arroyo/www/bin/httpd nobody 4033 4023 0 Aug09 ? 00:00:53 /arroyo/www/bin/httpd nobody 4034 4023 0 Aug09 ? 00:00:53 /arroyo/www/bin/httpd nobody 4035 4023 0 Aug09 ? 00:00:53 /arroyo/www/bin/httpd nobody 4036 4023 0 Aug09 ? 00:00:53 /arroyo/www/bin/httpd nobody 4037 4023 0 Aug09 ? 00:00:53 /arroyo/www/bin/httpd nobody 4085 4023 0 Aug09 ? 00:00:52 /arroyo/www/bin/httpd nobody 4086 4023 0 Aug09 ? 00:00:53 /arroyo/www/bin/httpd nobody 4572 4023 0 Aug10 ? 00:00:52 /arroyo/www/bin/httpd root 11598 30692 0 16:12 pts/0 00:00:00 grep http
If the Apache server is not running, restart the server.
# /arroyo/www/bin/apachectl start
CDSM GUI Does Not Register the Vaults and Streamers
If the CDSM GUI is not able to register that the Vaults and Streamers are part of the array or CDS, do the following:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Log in to the Vault or Streamer as root.
Verify two-way database connectivity with the CDSM.
# netstat -an | grep 9999
Verify statsd is running.
# ps -aef | grep statsd
Verify the correct version and permissions for /home/stats/svrinit or svrinit_15 are being used.
# ls –l /home/stats/
On the Vault and the Streamer, initialize the CDS host in the database by using svrinit_15. Use the following options:
•
•
•
•
Option -i for the server physical IP address (eth0)
Option -s for the subnet mask of the network
Option -h for the host name
Option -d to deregister
For example, first deregister the CDS host using the -d option, then initialize the CDS host.
# svrinit_15 -i <ip_address> -s <subnet_mask> -h <host_name> -d
# svrinit_15 -i <ip_address> -s <subnet_mask> -h <host_name>
If you still have trouble getting the tables initialized, then log in to the CDSM GUI with an engineering access user account and add the Streamer or Vault by clicking the Maintain > Software > System
Configs page and using the Add New Server option.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
A-23
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.” If two-way connection does not exist, run db_shutdown on all servers including the CDSM, then start the database using the following commands:
# su – isa
$ arroyo start avsdb
If the database is stuck and db_shutdown does not take effect, use ps –ef |grep avsdb to query the process ID (PID), then use the kill -9 {pid} command to kill the avsdb process, and lastly restart the database.
Ingest Issues
This section includes the following ingest issues:
•
•
•
Ingest Interface
This section includes the following topics on troubleshooting the ingest interface:
•
FSI Starts but Cannot Ingest Content
•
•
•
Asset Ingest Manager Restart Causes Endless Loop
FSI Starts but Cannot Ingest Content
Cause 1: FSI mode selected is incorrect.
Action 1: Check the FSI mode on the server by viewing the /home/isa/bss/log/fsi.log when FSI is started.
The FSI running mode should be what you set in /home/isa/bss/scripts/arroyo-site-env.sh; for example, set “FSI_DEPLOYMENT=1.”
11/05/2008|19:04:50.035191|fsid.cc|444|366702208| Initializing fsi daemon...
11/05/2008|19:04:50.035470|fsid.cc|445|366702208| main(): Thread ID: 366702208
11/05/2008|19:04:50.035520|fsid.cc|447|366702208| Initializing FSI configuration...
11/05/2008|19:04:50.035654|DatabaseConnection.cc|62|366702208| Successfully connected database socket.
11/05/2008|19:04:50.048468|fsid.cc|459|366702208| Setting FSI running mode to "1" as specified by commandline.
A-24
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix A Troubleshooting
Ingest Issues
FSI Does Not Start
Cause 1: Invalid port address.
cat fsi.err | grep FSID
[fsid.cc:588] ERROR: FSID Port of 0 is an invalid port address
Action 1: Change the FSI port to a nonzero value (default=20004).
Using the CDSM GUI, choose Configure > Server Level > FSI Setup and enter a new port number in the FSI Server Port field. See the
“Configuring FSI Setup” section on page 4-81 for
more information.
Action 2: Log in to the server as isa and start the FSI service.
$ arroyo start fsi
Cause 2: Cannot open cache2app reported in fsi.log and fsi.err.
Action 1: Verify that the CSserver process is running
•
•
Log in to the server as root and enter the lsmod command to check if the avs_cserver is running.
If the avs_cserver is not running, enter the rpm –qa | grep cserver command to see if it is installed.
If avs_cserver is installed, enter the /arroyo/test/run command to start avs_cserver.
If avs_cserver is not installed, call Cisco Technical Support.
Content Not Ingesting
Cause 1: Cannot connect to the FTP server (for example, Lysis Content Ingest Server).
Action 1: Check the network connectivity and user access.
Check the network connectivity, access control lists (ACLs), user access privileges, and so on for the FTP server.
Action 2: Verify the manual FTP request.
Verify that a manual FTP request to the FTP server from the user isa is working and list the content to be ingested.
Cause 2: Content is not correctly named in the ADI XML file.
Action 1: View the aim.log file.
cat aim.log | grep FTPP
11/23/2007|12:00:59.383279|AIMListenThread |0144|06151|CALLBACK
RECVD[FSICALLBACK 2251799813686769 400 FTPProcess.cc:328: Caught exception:
FTPProcess::run_ftp(): FTP Failed: ftp://username:password@ftpserver:21//6663_3800p.mpg. Failed while waiting for a response to the retrieve command from ftp server.]
2.
In this example, 6663_3800p.mpg does not exist on the FTP server. Make sure the FTP server content matches the content listed in the ADI XML file.
Cause 3: The Asset Ingest Manager (AIM) is not getting a message from the FTP server.
Action 1: Do the following:
1.
Identify the master Vault by looking at the /sbin/ifconfig file and locating the eth0:1 interface.
On the master Vault, enter the tail –f aim.log command.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
A-25
Appendix A Troubleshooting
Ingest Issues
3.
4.
5.
6.
Retry the transfer from the FTP server.
If there is a connectivity issue, the aim.log is not updated.
Restart the AIM process by entering the arroyo stop aim command followed by the arroyo
start aim command.
If necessary, restart the FTP server.
Asset Ingest Manager Restart Causes Endless Loop
Cause 1: AIM has orphaned threads.
Action 1: Check the aim.log for endless looping message.
12/12/2007|11:47:16.677035|AVSIngestMgrISA |0178|01024|******************* AIMd starting*******************
12/12/2007|11:47:16.678530|pTCP |0065|01024|Host info 10.212.17.12:5555
12/12/2007|11:47:16.684145|pRunMaster |0035|01024|Current process is the master
12/12/2007|11:47:16.684267|pDomain |0093|01024|UNIX Domain sock path [/tmp/isadb]
12/12/2007|11:47:16.684326|pSock |0115|01024|Connected to /tmp/isadb
12/12/2007|11:47:16.684500|pDbConfigObject |0257|01024|Db errcode[55]
12/12/2007|11:47:16.684597|AIMCache |0164|01024|Trying to load dynamic libs.......
12/12/2007|11:47:16.686275|AIMCache |0179|01024|Loaded [libAVSFSI_AIM.so]
12/12/2007|11:47:16.743879|AIMCache |0179|01024|Loaded [libAVSVerimatrix_AIM.so]
12/12/2007|11:47:16.745238|AIMCache |0179|01024|Loaded [libAVSTotalManage_AIM.so]
12/12/2007|11:47:16.745753|AIMCache |0182|01024|Shared lib error[libAVSNGOD_AIM.so: cannot open shared object file: No such file or directory]
12/12/2007|11:47:16.745911|AIMCache |0182|01024|Shared lib error[libAVSISA_AIM.so: cannot open shared object file: No such file or directory]
12/12/2007|11:47:16.746031|AIMCache |0182|01024|Shared lib error[libAVSWideVine_AIM.so: cannot open shared object file: No such file or directory]
……..
12/12/2007|15:55:20.321800|AIMDbManager |0021|02051|AIM config change detected.....
12/12/2007|15:55:20.322220|AIMCache |0316|02051|DB Tag[.0.0.0:20004/][]
12/12/2007|15:55:20.322670|AIMDbManager |0054|02051|Config change from [http://0.0.0.0:20004/][]
12/12/2007|15:55:20.323040|AIMDbManager |0055|02051|Config change to [.0.0.0:20004/][]
12/12/2007|15:55:20.323430|AIMCache |0316|02051|DB Tag[omeplace.here.there:8082/totalmanage/vod][]
12/12/2007|15:55:20.323960|AIMDbManager |0054|02051|Config change from
[http://someplace.here.there:8082/totalmanage/vod][]
12/12/2007|15:55:20.324330|AIMDbManager |0055|02051|Config change to
[omeplace.here.there:8082/totalmanage/vod][]
12/12/2007|15:55:20.324700|AIMCache |0316|02051|DB Tag[nage/vod][]
12/12/2007|15:55:20.325100|AIMDbManager |0054|02051|Config change from [/totalmanage/vod][5001]
12/12/2007|15:55:20.325500|AIMDbManager |0055|02051|Config change to [nage/vod][]
12/12/2007|15:56:20.443830|pDbConfigObject |0257|02051|Db errcode[55]
12/12/2007|15:56:20.444500|AIMDbManager |0021|02051|AIM config change detected.....
12/12/2007|15:56:20.445230|AIMCache |0316|02051|DB Tag[0004/][]
12/12/2007|15:56:20.445690|AIMDbManager |0054|02051|Config change from [.0.0.0:20004/][]
12/12/2007|15:56:20.446060|AIMDbManager |0055|02051|Config change to [0004/][]
12/12/2007|15:56:20.446460|AIMCache |0316|02051|DB Tag[.here.there:8082/totalmanage/vod][]
12/12/2007|15:56:20.446900|AIMDbManager |0054|02051|Config change from
[omeplace.here.there:8082/totalmanage/vod][]
12/12/2007|15:56:20.447270|AIMDbManager |0055|02051|Config change to
[.here.there:8082/totalmanage/vod][]
12/12/2007|15:56:20.448310|AIMDbManager |0054|02051|Config change from [nage/vod][]
12/12/2007|15:56:20.448700|AIMDbManager |0055|02051|Config change to [][]
12/12/2007|15:57:20.564550|pDbConfigObject |0257|02051|Db errcode[55]
Action 1: Check for orphaned AIM threads during the AIM service being stopped.
Log in as isa and stop the AIM service, verify there are no orphaned AIM threads, and restart the AIM service.
A-26
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix A Troubleshooting
Ingest Issues
$ arroyo stop aim
$ ps -aef | grep AVSIngestMgr isa 7291 7243 0 20:59 pts/0 00:00:00 grep AVSIngestMgr
$ arroyo start aim
Cause 2: The master Vault AIM is in a degraded state.
Check the aim.log on the slave Vault to verify it is in a waiting state.
12/12/2007|14:57:08.954182|AVSIngestMgrISA |0178|01024|******* AIMd starting****
12/12/2007|14:57:08.955726|pTCP|0065|01024|Host info 10.212.17.12:5555
12/12/2007|14:57:08.961349|pTCP|0065|01024|Host info *:5555
12/12/2007|14:57:08.961442|pRunMaster|0029|01024|process is not the master, waiting on notification
Action 1: Cause a failover between the master and slave Vaults.
On the master Vault, stop the statsd and Ingest Manager (AIM) services, thereby causing Vault failover. The AIM service on the new master Vault should immediately start processing ingest requests.
On the old master Vault, log in as root and restart the statsd service, log in as isa and restart the
AIM service. This Vault becomes the new standby and the AIM process is in waiting mode.
Bad Content
Variable bit rate (VBR) encoded content is not currently supported. See the “CDS Content Quality
Guidelines” section on page A-47
for constant bit rate (CBR) guidelines.
Network
Ensure that the network maximum transmission unit (MTU) is appropriately set. If jumbo frames are enabled on the CDS, then the network must support jumbo frames. We recommend that the network support jumbo frames even when the jumbo frame option is disabled.
If a Layer 2 network is used for CDS, then appropriate MAC addresses (ARP entries) have to be configured on the switches and routers. Ensure that the CDS Vault and Streamer interfaces are in the same VLAN. If a Layer 3 network is used for the CDS, then ensure that the corresponding default gateways are correctly configured on CDS Vaults and Streamers for the various interfaces and Stream
Groups.
Ensure that the content source (catcher, FTP server, and so on) is reachable from the Vaults or ISVs, and that manual content transfer using FTP works correctly.
For more information about the status of the network interfaces, network routing tables, ARP and so on
see the “Network” section on page A-18 .
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
A-27
Appendix A Troubleshooting
Content Processing Issues
Content Processing Issues
This section includes the following content processing issues:
•
•
•
•
Listing Content
To view the actual stored content versus what the database reports, enter the following commands:
$ su - isa
$ cd /arroyo/db
$ ./AVSDBUtil <<- EOF > db_content_list
> 1
> 2
> 0
> EOF
$ cat db_content_list
Content Mirroring
To enable content mirroring locally on one Vault, do the following:
Step 1
Step 2
Modify the /home/isa/.arroyorc file by adding the following line: cserver_opts "vault local copy count 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. You can also use the tunables to verify the settings.
echo 2 > /proc/calypso/tunables/vaultlocalcopycount
Note
Using the echo 2 command to enable local mirroring in the tunable file only changes the local copy count temporarily. The local copy count resets to its original value on reboot. To configure the local copy count permanently for any value other than 1, edit the /arroyo/test/vault/setupfile or use the CDSM GUI.
A-28
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix A Troubleshooting
Content Processing Issues
To enable content mirroring between two Vaults, do the following:
Step 1
Step 2
Step 3
Step 4
Step 5
In the CDSM GUI, choose Configure > Server Level > Server Setup. The Server Setup page is displayed.
For more information, see the
“Configuring the Servers” section on page 4-58
.
From the Server IP drop-down list, choose the IP address of the server.
From the Vault Mirror Copies drop-down list, choose 2.
Click Submit.
Verify the change has propagated by looking at /arroyo/test/vault/setupfile and
/arroyo/log/protocoltiming.log.<date> files.
# grep mirror /arroyo/test/setupfile vault mirror copies 2
# grep LocalMirror /arroyo/log/protocoltiming.log.11202007
-LocalMirror Active=0:0 comp=0% obj=0.0/s read=0b/s write=0b/s copies=1
-LocalMirror Active=0:0 comp=0% obj=0.0/s read=0b/s write=0b/s copies=1
Verifying GOIDs
You cannot verify that the global object identifiers (GOIDs) among Vaults and Streamers are correct by comparing the total number of GOIDs on each server. There are actually multiple chains of GOIDs. If you list the GOID chains you can verify that the GOIDs are correct, because listing the GOIDs provides a summary at the end of the listing that reports any issues.
To list the GOIDs, enter the following command: 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.<date> 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.
Trick-Mode Issues
Verify the trick-mode settings in the CDSM GUI and the Vault setupfile file.
•
•
From the CDSM GUI, choose Configure > System Level > Ingest Tuning to view the trick-mode settings.
To check the trick-mode setting in the setupfile on the Vault, enter the following command:
$ grep trick /arroyo/test/setupfile trickspeedsv2 4 10 32 -32 -10 -4
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
A-29
Cache-Fill Issues
Appendix A Troubleshooting
Check the /arroyo/log/c2k.log.<date> log file and the session message logs during playout to verify that the trick-mode files are being streamed.
Cache-Fill Issues
This section covers the following cache-fill issues:
•
•
Rules for ISV Interoperability with Vaults and Streamers
Rules for ISV Interoperability with Vaults and Streamers
The following rules apply for ISVs to interoperate with Vaults and Streamers:
•
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 .
Stream Stops Playing at the Same Place or Does Not Play at All
Cause 1: Jumbo frames are not supported or configured on the cache-fill network switch.
Check 1: Search the c2k.log file and the rtsp.log file for content read errors.
==> /arroyo/log//c2k.log.01152008 <==
15-Jan-2008 20:42:33 UTC :out:c2k_p_setcontentbundle: stream 3 localStreamHandlePtr 00000000 remoteServer 00000000
15-Jan-2008 20:42:33 UTC :out:c2k_p_setcontentbundlecontinue: stream 3 localStreamHandle 0
15-Jan-2008 20:42:33 UTC :out:c2k_p_setdestination: stream 3 localStreamHandle 0 ip 0xe0016401 port 10000
15-Jan-2008 20:42:41 UTC :out:igate goid d346434b982851 finished read 0 length e3 lastbytes b4 retries 0 reqlen 0/e3
15-Jan-2008 20:42:41 UTC :err:IGate::ReadClose(goid 0): ERROR: Never saw header
15-Jan-2008 20:42:41 UTC :err:IGate::ReadClose(goid 0): ERROR: Never saw EOF record
15-Jan-2008 20:42:44 UTC :out:igate goid d346434b982851 finished read 0 length e3 lastbytes b4 retries 1 reqlen 0/e3
15-Jan-2008 20:42:44 UTC :err:IGate::ReadClose(goid 0): ERROR: Never saw header
15-Jan-2008 20:42:44 UTC :err:IGate::ReadClose(goid 0): ERROR: Never saw EOF record
15-Jan-2008 20:42:47 UTC :out:igate goid d346434b982851 finished read 0 length e3 lastbytes b4 retries 2 reqlen 0/e3
15-Jan-2008 20:42:47 UTC :err:IGate::ReadClose(goid 0): ERROR: Never saw header
15-Jan-2008 20:42:47 UTC :err:IGate::ReadClose(goid 0): ERROR: Never saw EOF record
==> rtsp.log <==
01/15/2008|21:43:03.585614|MyrioSession.cc|385|Successfully sent message to IPTV STB
01/15/2008|21:43:03.585785|StreamImpl.cc|1980|***** Stream State (after Callback receipt) ****
01/15/2008|21:43:03.585846|StreamImpl.cc|1981|Stream Position : = 1152089708
01/15/2008|21:43:03.585899|StreamImpl.cc|1982|Current Operation : = 0
01/15/2008|21:43:03.585957|StreamImpl.cc|1983|Operation Time (ms) : = 1200429783585
01/15/2008|21:43:03.586011|StreamImpl.cc|1984|Stream State : = stopped
Cisco TV CDS 2.3 RTSP Software Configuration Guide
A-30 OL-22792-01
Appendix A Troubleshooting
Streaming and Playout Issues
01/15/2008|21:43:03.586062|StreamImpl.cc|1985|************************************************
01/15/2008|21:43:03.586191|MyrioSession.cc|375|IPTV STB Message:
ANNOUNCE * RTSP/1.0
CSeq: 30539779
Session: 13762563 x-notice: 4400 "Error Reading Content Data" event-date=20080115T204303.586Z
01/15/2008|21:43:03.586259|MyrioSession.cc|385|Successfully sent message to IPTV STB
Check 2: Ping between the two devices.
Ping between the two devices on the cache-fill VLAN using a packet size greater than 1500 bytes.
Action 1: If the ping fails, verify that jumbo frames and cache-fill interfaces are configured correctly.
Verify that jumbo frames are enabled on the switch ports for the cache-fill VLAN, and verify that the cache-fill interfaces are configured correctly on the Streamers and Vaults. See the
“Configuring the Servers” section on page 4-58 for information on configuring the cache-fill
interfaces.
Streaming and Playout Issues
This section includes the following 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 Objects” section on page 5-13 .
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.
Tuning failure because of one of the following:
•
–
–
Error in the ARP table
QAM device is down
–
Network problem
Backoffice is out of synchronization with the CDS ContentStore, resulting in content not being found.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
A-31
Appendix A Troubleshooting
Streaming and Playout Issues
Stream Not Playing
The rtsp.log file has the entry, “error reading content data.” This means that a callback was received from the CServer with a completion code of 3.
Cause 1: A piece of the content is missing.
In this case, a user can typically stream part of the content, but at some point the stream stops and the error message is returned in the ANNOUNCE message. The content needs to be validated at the CServer level.
Action 1: Set up a stream to play to a multicast address.
If this is successful, then there is a network issue, which is either a default gateway or unreachable remote client. You can verify whether it is successful by looking at the
/home/stats/ifstats file.
Action 2: If ifstats information does not detect a problem, try streaming to another multicast IP address.
Repeat streaming to a multicast address with different content and, if possible, ingest known good content. Check the protocoltiming.log.<date> for damaged GOIDs by using the following command:
tail -f protocoltiming.log.<latest date> | grep Goids
Cause 2: There is a problem reaching the destination QAM device.
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. After stream response fails, the CServer calls back with the completion code of 3, which causes the
“error reading content data” message.
Action 1: Check that the interfaces involved in the streaming are up and operating at the correct speed.
Using the CDSM GUI, choose Monitor > Server Level > NIC Monitor, choose the IP address of the server, and verify the participating interfaces are up and operating at gigabit Ethernet
speeds For more information, see the “NIC Monitor” section on page 5-28 .
Action 2: Set up a stream to play to a multicast address.
If this is successful, then there is a network problem, which is either a default gateway or unreachable remote client. You can verify whether it is successful by looking at the
/home/stats/ifstats information.
Action 3: If streaming to a multicast address is not successful, check that the Vaults can be reached.
Check the /arroyo/log/protocoltiming.log.<date> log file for the number of reachable remote servers. Additionally, if there is a cache-fill issue, you will see a large megabit value for the re-xmit buffer.
You can also check the /arroyo/log/c2k.log.<date> log file for any unreachable Vaults.
Cause 3: The c2k.log file reports “no streamer available, out of capacity.”
The protocoltiming.log file reports “remote vaults 0 caches 0.” This means the Streamer and
Vault have lost connection with each other.
Action 1: Check the route configured on the servers.
Use the cat /arroyo/test/RoutingTable command to verify correct route table entries.
Check the routing table using the CDSM GUI by clicking Configure > Server Level > Route
Tables. For more information, see the
“Configuring the Route Table” section on page 4-66 .
Cisco TV CDS 2.3 RTSP Software Configuration Guide
A-32 OL-22792-01
Appendix A Troubleshooting
Streaming and Playout Issues
Action 2: Use the cat /arroyo/test/RemoteServers to check if the remote server is configured correctly.
Action 3: Check the routing table on the switch or router.
Poor Video or Audio Quality
This section includes the following issues that result in poor video or audio quality:
•
•
•
•
•
CDS Is Streaming but No Video Is Playing on the STB
No Video Displayed
When content is streamed to a client device, if there is no video picture displayed on the client device and the audio is working fine, use the following troubleshooting methods:
•
Verify that the source is working properly and that the original content is of good quality.
–
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. There is a tunable set for Telenet to stream null packets when the end of the stream is reached. This should be commented out or removed in a non-Telenet environment.
–
The interface that you are using for real-time ingests needs to be configured for the CServer.
There are a couple of settings that define the interrupt for the real-time ingest interface and ensure that a single central processing unit (CPU) is responsible for receiving the packets for the ingest. Without these settings, packets can be out of order, which can cause problems with the video picture.
To fix this, use the cat /proc/interrupts command to display the interrupts and find the interrupt value associated with the interface you are using for ingest. After you know this value, add the following lines to the /arroyo/test/run script: echo 1 > /proc/irq/<interrupt value>/smp_affinity echo <interrupt value> > /proc/calypso/test/bypass_disable_irq
You can enter these lines at the Linux command line as well by doing so you do not have to reboot your system for them to take effect. Any content that you have previously ingested should be considered invalid.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
A-33
Appendix A Troubleshooting
Streaming and Playout Issues
RTSP Cannot Start
The owner and group permission of the RTSP binary file are incorrect. To correct this, enter the following commands:
# cd /home/isa/bss/bin
# chown root:root AVSRTSPServer
# chmod u+s AVSRTSPServer
# su - isa arroyo start rtsp
Video Stops Playing
If the video stops playing after a fixed interval (for example, five minutes), check to see that the interval the video played for matches the session inactivity timeout setting in the CDSM GUI Configure >
Server Level > RTSP Setup page.
If the interval matches the setting, check the /home/isa/bss/log/rtsp.log file for the STB responses within the inactivity timeout interval.
This scenario could be caused by the STB possibly not responding, or the STB response may be getting lost in the network.
No Video Playing on the STB
Check the /home/isa/bss/log/rtsp.log file on the relevant Streamer. If you see a successful setup request and response, and do not see a play request for the same session, there is some issue with the STB communication to the RTSP server. The RTSP server should also be receiving a get_parameter request as a heartbeat to keep the session alive. If this does not happen, the session is torn down after the session inactivity timeout is exceeded, and a “session timed-out” message is sent.
Following is an example of the rtsp.log file showing the setup, response, teardown, and timeout messages.
SETUP rtsp://10.212.16.18:554/?AssetId=CAN36099.mpg RTSP/1.0^M CSeq: 10^M User-Agent: OpenTV VOD 1^M Transport:
MP2T/DVBC/QAM;unicast;client=168892769.6501124101;destination=172.23.68.2;client_port=1^M
06/13/2007|20:23:33.548631|RTSPTCPListener.cc|298|Valid RTSP request received, port = 554
06/13/2007|20:23:33.548788|RTSPMsgHandler.cc|671|Current session count = 0
06/13/2007|20:23:33.548868|RTSPMsgHandler.cc|283|Created session id of: = 1179649
06/13/2007|20:23:33.548942|StreamImpl.cc|111|Stream handle set to: = 1
06/13/2007|20:23:33.549200|StreamImpl.cc|1745|Stream setup - URL = CAN36099.mpg, downstream address = -1!0.0.0.0!172.23.68.2!1
06/13/2007|20:23:33.549814|StreamImpl.cc|545|DSADDR - IP: 172.23.68.2, port: 1, node: -1
06/13/2007|20:23:33.550150|QuativeSession.cc|782|SETUP Response: RTSP/1.0 200 OK^M CSeq: 10^M Session:1179649; timeout=300^M Transport: MP2T/DVBC/QAM;unicast;client=168892769.6501124101; destination=172.23.68.2;client_port=1^M
Location:rtsp://10.212.16.18:554^M
06/13/2007|20:23:33.550227|QuativeSession.cc|794|Successfully sent SETUP response.
06/13/2007|20:23:33.550377|PersistenceConnection.cc|137|Repository operation successfully completed
06/13/2007|20:23:37.313753|RTSPMsgHandler.cc|1161|In production mode, accepting incoming SETUP requests
06/13/2007|20:24:37.325864|RTSPMsgHandler.cc|1161|In production mode, accepting incoming SETUP requests
06/13/2007|20:25:37.338193|RTSPMsgHandler.cc|1161|In production mode, accepting incoming SETUP requests
06/13/2007|20:26:37.350250|RTSPMsgHandler.cc|1161|In production mode, accepting incoming SETUP requests
06/13/2007|20:27:37.362401|RTSPMsgHandler.cc|1161|In production mode, accepting incoming SETUP requests
06/13/2007|20:28:37.374832|RTSPMsgHandler.cc|1161|In production mode, accepting incoming SETUP requests
06/13/2007|20:29:13.075941|LivenessManager.cc|213|Session has timed-out, initiating teardown process.Session: 1179649
06/13/2007|20:29:13.076127|RTSPMsgHandler.cc|671|Current session count = 1
06/13/2007|20:29:13.076319|QuativeSession.cc|665|Message: ANNOUNCE * RTSP/1.0^M CSeq: 17956865^M Session: 1179649^M
Notice:5402 Event-Date=20070613T182913.076Z "Client Session Terminated"^M
A-34
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix A Troubleshooting
Streaming and Playout Issues
CDS Is Streaming but No Video Is Playing on the STB
Check the /home/isa/bss/log/rtsp.log file on the relevant Streamer for any of the following message flows:
•
Setup request is sent from Quative, followed by setup okay response returned from CDS.
•
•
Describe request is sent from the STB, followed by describe ok response and details returned from
CDS.
Play request is sent from STB, followed by play ok response sent from CDS.
•
•
Teardown request is sent from STB, followed by teardown performed by CDS.
The possible causes for the above message flows are the following:
•
STB is not tuning to the correct frequency or program ID, or the session resource manager (SRM) is returning incorrect information.
SRM is providing the wrong edge QAM device to the CDS. In the rtsp.log file, check the IP address in the setup RTSP header.
•
•
Edge QAM device port mapping may be wrong. Check the edge QAM device configuration.
Radio frequency (RF) is not reaching the STB.
Following is an example of the rtsp.log file showing the request and response messages.
SETUP rtsp://87.231.193.114:554/?AssetId=CAN0000095932.mpg RTSP/1.0^M CSeq: 2^M User-Agent: OpenTV VOD 1^M Transport:
MP2T/DVBC/QAM;unicast;client=170027388.4312020202;destination=172.23.77.2;client_port=16^M
11/29/2007|16:10:56.952766|RTSPTCPListener.cc|298|Valid RTSP request received, port = 554
11/29/2007|16:10:56.952938|RTSPMsgHandler.cc|644|Current session count = 0
11/29/2007|16:10:56.953163|RTSPMsgHandler.cc|311|Created session id of: = 30801921
11/29/2007|16:10:56.953250|StreamImpl.cc|111|Stream handle set to: = 30801921
11/29/2007|16:10:56.953562|StreamImpl.cc|1733|Stream setup - URL = CAN0000095932.mpg, downstream address =
-1!0.0.0.0!172.23.77.2!16 11/29/2007|16:10:56.953736|StreamImpl.cc|563|DSADDR - IP: 172.23.77.2, port: 16, node: -1
11/29/2007|16:10:56.954630|QuativeSession.cc|786|SETUP Response: RTSP/1.0 200 OK^M CSeq: 2^M Session: 30801921;timeout=300^M
Transport: MP2T/DVBC/QAM;unicast;client=170027388.4312020202;destination=172.23.77.2;client_port=16^M Location: rtsp://87.231.193.114:554^M
11/29/2007|16:10:56.954730|QuativeSession.cc|798|Successfully sent SETUP response.
11/29/2007|16:10:56.954832|PersistenceConnection.cc|137|Repository operation successfully completed
11/29/2007|16:10:57.195223|RTSPTCPListener.cc|155|Messages: DESCRIBE * RTSP/1.0^M CSeq: 90^M Session: 30801921^M
Accept:application/sdp^M
11/29/2007|16:10:57.195306|RTSPTCPListener.cc|298|Valid RTSP request received, port = 554
11/29/2007|16:10:57.195443|RTSPMsgHandler.cc|644|Current session count = 1
11/29/2007|16:10:57.195711|ContentManager.cc|277|Calculated content duration: = 3814142
11/29/2007|16:10:57.195834|RTSPQuativeProtocolHandler.cc|444|Describe response
11/29/2007|16:10:57.195911|QuativeSession.cc|684|Message: RTSP/1.0 200 OK^M CSeq: 90^M Session: 30801921^M
Content-Type:application/sdp^M Content-Length: 170^M ^M v=0^M o=- 3405337857 3405337857 IN IP4 10.236.141.67^M s=RTSP
Session^M t=0 0^M m=video 0 udp M2T^M c=IN IP4 0.0.0.0^M i=CAN0000095932.mpg^M a=type:vod^M a=range:npt=0.0-3814.142
11/29/2007|16:10:57.195975|QuativeSession.cc|694|Successfully sent message to STB
11/29/2007|16:10:57.377758|RTSPTCPListener.cc|155|Messages: PLAY * RTSP/1.0^M CSeq: 91^M Session: 30801921^M Scale: 1^M Range:npt=0-^M
11/29/2007|16:10:57.377850|RTSPTCPListener.cc|298|Valid RTSP request received, port = 554
11/29/2007|16:10:57.377986|RTSPMsgHandler.cc|644|Current session count = 1
11/29/2007|16:10:57.378120|StreamImpl.cc|1121|play(*, from: 0 to: 2147483647)
11/29/2007|16:10:57.378179|StreamImpl.cc|588|handleContent(), url: *, play content now: 1, no flush: 0
11/29/2007|16:10:57.378235|StreamImpl.cc|697|handlePlay(), loop content: 0, play content now: 1, no flush: 0
11/29/2007|16:10:57.385722|RTSPQuativeProtocolHandler.cc|403|Play response
11/29/2007|16:10:57.385838|QuativeSession.cc|684|Message: RTSP/1.0 200 OK^M CSeq: 91^M Session: 30801921^M Scale: 1^M
Range: npt=0.000-^M
11/29/2007|16:10:57.385895|PersistenceConnection.cc|137|Repository operation successfully completed
11/29/2007|16:10:57.385971|QuativeSession.cc|694|Successfully sent message to STB
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01 A-35
Appendix A Troubleshooting
Session Messaging
11/29/2007|16:10:57.386033|PersistenceConnection.cc|137|Repository operation successfully completed
11/29/2007|16:10:58.456207|RTSPTCPListener.cc|155|Messages:PLAY * RTSP/1.0^M CSeq: 92^M Session:30801921^M Scale: 1.0^M
11/29/2007|16:10:58.456286|RTSPTCPListener.cc|298|Valid RTSP request received, port = 554
11/29/2007|16:10:58.456450|RTSPMsgHandler.cc|644|Current session count = 1
11/29/2007|16:10:58.456595|StreamImpl.cc|1121|play(*, from: -2147483648 to: 2147483647)
11/29/2007|16:10:58.456654|StreamImpl.cc|588|handleContent(), url: *, play content now: 1, no flush: 0
11/29/2007|16:10:58.456711|StreamImpl.cc|697|handlePlay(), loop content: 0, play content now: 1, no flush: 0
11/29/2007|16:10:58.456997|StreamListener.cc|103|Call Handle: 4 Session Id: 30801921 Completion Code: 0 Error
Code: 31 Position: 1523 Content Index: 0 Speed: 1 Play Server: 114
11/29/2007|16:10:58.457074|ModelMsg.cc|164|Starting the processing of a model msg.
11/29/2007|16:10:58.457142|RTSPMsgHandler.cc|923|Successful transition for call handle: = 4
11/29/2007|16:10:58.457474|PersistenceConnection.cc|137|Repository operation successfully completed
11/29/2007|16:10:58.457535|PersistenceConnection.cc|137|Repository operation successfully completed
11/29/2007|16:10:58.457602|RTSPQuativeProtocolHandler.cc|403|Play response
11/29/2007|16:10:58.457704|QuativeSession.cc|684|Message: RTSP/1.0 200 OK^M CSeq: 92^M Session: 30801921^M Scale: 1^M
Range: npt=1.523-^M ^M
11/29/2007|16:10:58.457760|QuativeSession.cc|694|Successfully sent message to STB
11/29/2007|16:11:02.546768|RTSPTCPListener.cc|155|Messages: TEARDOWN * RTSP/1.0^M CSeq: 93^M Session: 30801921^M ^M
11/29/2007|16:11:02.546866|RTSPTCPListener.cc|298|Valid RTSP request received, port = 554
11/29/2007|16:11:02.547022|RTSPMsgHandler.cc|644|Current session count = 1
11/29/2007|16:11:02.547222|QuativeSession.cc|665|Message:ANNOUNCE * RTSP/1.0^M CSeq:2^M Session:30801921^M Notice: 2405
Event-Date=20071129T151102.547Z "Session torn down: Requested by STB"^M
Session Messaging
This section includes the following topics on session messaging:
•
•
Log File Search Tips
To search for general RTSP errors, use the following commands:
grep "RTSP/1.0 4" rtsp.log
grep "RTSP/1.0 5" rtsp.log
To search for content read errors, use the following command:
grep "Error Reading Content Data" rtsp.log
To search for stopped sessions, use the following command:
grep "stream_session: stopped" rtsp.log
To search for SETUP requests, use the following command:
grep "SETUP rtsp" rtsp.log
Use the CSeq header value in the rtsp.log file to match RTSP requests to responses.
Use the Session header value in the rtsp.log file to trace a single RTSP session from setup to teardown.
A-36
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix A Troubleshooting
Session Messaging
Codes
OL-22792-01
The ANNOUNCE method is a mechanism for RTSP servers to signal RTSP clients about start of stream or end of RTSP session events. An ANNOUNCE request must include a “CSeq” header and “Notice.”
Following are the Notice codes:
•
1103 Playout Stalled (from VOD server only)
•
•
•
•
1104 Playout Resumed (from VOD server only)
1500 New Scale (from VOD server only)
2101 EOS (end of stream) (from VOD server only)
2104 BOS (beginning of stream); can happen in case of rewind or reverse play (from VOD server only)
•
•
•
•
2401 Ticket Expired; the playout has stopped (from the MS server only).
4400 Error Reading Content Data; the playout has stopped (from VOD server only); from the
Streamer to the client referring to a hole in the content or a delay in getting the content
5200 Server Resources Unavailable; the playout has stopped (from MS server only)
5402 Client Session Terminated; teardown has been initiated by the server, the session is closed
(from MS server only)
•
•
5403 Server Shutting Down; the playout has stopped. If from MS server, the session is closed. If from VOD server, the client must issue a teardown of the session (first configuration only).
5502 Internal Server error; the playout has stopped. The client must issue a teardown of the session.
After receiving and interpreting a request message, the recipient responds with an RTSP response message. The status code returned in the RTSP response message must be in the range 100 to 599 (per
RFC 2326). If the server returns another value, the client must treat the error according to the range value:
•
1xx: Informational—Request received, continuing process.
•
•
•
•
2xx: Success —Action was successfully received, understood, and accepted.
3xx: Redirection—Further action must be taken to complete the request.
4xx: Client Error—Request contains bad syntax or cannot be fulfilled.
5xx: Server Error—Server failed to fulfill an apparently valid request.
Table A-3 describes the RTSP status codes.
Table A-3 RTSP Status Codes
State
OK
BAD_REQUEST
FORBIDDEN
NOT_FOUND
METHOD_NOT_ALLOWED
NOT_ACCEPTABLE
REQUEST_TIMEOUT
Code Description
200 return "OK"
400
403
404
405 return "Bad Request" return "Forbidden” return "Not Found" return "Method Not Allowed"
406
408 return "Not Acceptable" return "Request Time-out"
Cisco TV CDS 2.3 RTSP Software Configuration Guide
A-37
Database Issues
Appendix A Troubleshooting
Table A-3 RTSP Status Codes (continued)
State Code Description
UNSUPPORTED_MEDIA_TYPE 415
INVALID_PARAMETER 451 return "Unsupported Media Type" return "Parameter Not Understood"
NO_BANDWIDTH
SESSION_NOT_FOUND
INVALID_METHOD
453
454
455 return "Not Enough Bandwidth" return "Session Not Found" return "Method Not Valid in This State"
INVALID_HEADER
INVALID_RANGE
456
457
UNSUPPORTED_TRANSPORT 461
DESTINATION_UNREACHABLE 462
DESTINATION_REQUIRED 463
INTERNAL_SERVER_ERROR 500
NOT_IMPLEMENTED
SERVICE_UNAVAILABLE
501
503
UNSUPPORTED_VERSION 505 return “Header Filed Not Valid for Resource” return "Invalid Range" return "Unsupported transport" return "Destination unreachable" return "Destination required" (nCUBE extension) return "Internal Server Error" return "Not Implemented" return "Service Unavailable" return "RTSP Version not supported"
UNSUPPORTED_OPTION 551
NGOD Extensions for Session Setup Failure (SSF)
return "Option not supported"
SSF_ASSET_NOT_FOUND 771 return "Server Setup Failed - Asset Not Found"
SSF_SOP_NOT_AVAILABLE 772
SSF_UNKNOWN_SOP_GROUP 773
SSF_UNKNOWN_SOP_NAMES 774
SSF_INSUFF_VOLUME_BW 775
SSF_INSUFF_NETWORK_BW 776
SSF_INVALID_REQUEST 777
SSF_INTERNAL_ERROR 778 return "Server Setup Failed - SOP Not Available" return "Server Setup Failed - Unknown SOP Group" return "Server Setup Failed - Unknown SOP Names" return "Server Setup Failed - Insufficient Volume Bandwidth" return "Server Setup Failed - Insufficient Network Bandwidth" return "Server Setup Failed - Invalid Request" return "Server Setup Failed - Internal Error"
Database Issues
This section covers the following database issues and troubleshooting methods:
•
•
A-38
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix A Troubleshooting
Database Issues
Database Replication
This section covers the following database issues:
•
CDSM GUI Does Not Report All the Ingested Content
•
•
CDSM GUI Does Not Report All the Ingested Content
First, verify that the package has not already expired.
Second, check for index errors in the CDSM database logs, using the following command:
$ grep index /arroyo/log/avsdb.log.20071106
11-06-2007 07:54:22PM:db_error DB_SECONDARY_BAD:Secondary index inconsistent with primary -30976
11-06-2007 07:54:22PM:db_error DB_SECONDARY_BAD:Secondary index inconsistent with primary -30976
11-06-2007 07:54:22PM:db_error DB_SECONDARY_BAD:Secondary index inconsistent with primary -30976
11-06-2007 07:54:22PM:db_error DB_SECONDARY_BAD:Secondary index inconsistent with primary -30976
11-06-2007 07:54:22PM:db_error DB_SECONDARY_BAD:Secondary index inconsistent with primary -30976
11-06-2007 07:54:22PM:db_error DB_SECONDARY_BAD:Secondary index inconsistent with primary -30976
The example output indicates that the Vault and CDSM databases are not synchronized, possibly because of the server times not being synchronized, a network connectivity issue, a server failure, or some other similar issue.
For resolution, see the
“Corruption Recovery” section on page A-40
.
Errors in Log File
If the error “FSI_ENV:XX:YY was not found in the database” occurs repeatedly in the logs (see the following example), there could be two causes for this issue.
03/22/2007|02:23:37.041319|../database/DbAlgorithms.h|142|2051| DEBUG_V: DbAlgorithms::get(__dataset="FSI_ENV:99:102")
03/22/2007|02:23:37.041508|../database/DbAlgorithms.h|152|2051| DEBUG_V: DbAlgorithms::get(__dataset=FSI_ENV:99:102): Received 1484 bytes from database socket.
03/22/2007|02:23:37.041606|../database/DbAlgorithms.h|175|2051| DbAlgorithms::get(__dataset=FSI_ENV:99:102): 'FSI_ENV:99:102' was not found in the database.
Cause 1: The databases are not synchronized.
If you are sure you entered an FSI configuration into the CDSM and the FSI is still giving this message, the configuration did not get replicated to the server where the FSI process is running.
Cause 2: The FSI configuration not existing in the database.
The FSI process can run without an existing database configuration by using its internal defaults.
Many Log Files
If one of the following conditions exist, 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.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
A-39
Database Issues
Appendix A Troubleshooting
•
•
•
Database could not be started. See the
“Services Monitor” section on page 5-32 for more
information.
Bidirectional connections are lost between servers. See the
“Required Services Not Starting or
Running Correctly” section on page A-22 .
The following error message is listed in the /arroyo/log/avsdb-err.log.yyyyMMdd file: tavsdb: unable to allocate memory for mutex; resize mutex region
# tail -f avsdb-err.log.20081111 tavsdb: unable to allocate memory for mutex; resize mutex region tavsdb: unable to allocate memory for mutex; resize mutex region tavsdb: unable to allocate memory for mutex; resize mutex region tavsdb: unable to allocate memory for mutex; resize mutex region tavsdb: unable to allocate memory for mutex; resize mutex region tavsdb: unable to allocate memory for mutex; resize mutex region tavsdb: unable to allocate memory for mutex; resize mutex region tavsdb: unable to allocate memory for mutex; resize mutex region tavsdb: unable to allocate memory for mutex; resize mutex region tavsdb: unable to allocate memory for mutex; resize mutex region
•
The /home/isa/Berkeley/DATADIR/REPLAY.db file increases to several GB.
$ ls -ltr
-rw-r----- 1 isa isa 10485760 Nov 11 17:46 log.0000002824
-rw-r----- 1 isa isa 10485760 Nov 11 17:46 log.0000002825
-rw-r----- 1 isa isa 10485760 Nov 11 17:46 log.0000002826
-rw-r----- 1 isa isa 10485760 Nov 11 17:46 log.0000002837
-rw-r----- 1 isa isa 10485760 Nov 11 17:46 log.0000002838
-rw-r----- 1 isa isa 10485760 Nov 11 17:46 log.0000002839
-rw-r----- 1 isa isa 10485760 Nov 11 17:46 log.0000002841
-rw-r----- 1 isa isa 10485760 Nov 11 17:46 log.0000002840
-rw-r----- 1 isa isa 10485760 Nov 11 17:46 log.0000002843
-rw-r----- 1 isa isa 10485760 Nov 11 17:46 log.0000002842
-rw-r--r-- 1 isa isa 5726769152 Nov 12 15:23 REPLAY.db
For resolution, see the “Corruption Recovery” section on page A-40 .
Corruption Recovery
Caution
Escalate to tier-three support before making any intrusive database changes.
If the CDSM database is corrupted and the Vault database is not corrupted, do the following:
Step 1
Step 2
As user root, stop the CDSM database.
# /usr/bin/db_shutdown
Confirm that the database is shut down.
# ps -ef | grep avsdb isa 2646 1 0 Jan09 ? 00:14:50 /arroyo/db/avsdb root 26088 26059 0 13:23 pts/1 00:00:00 grep avsdb
Maker 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
A-40
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix A Troubleshooting
Advanced Features and Applications
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Delete all files in the /arroyo/db/DATADIR directory.
As user root, stop the Vault database.
# /usr/bin/db_shutdown
Confirm that the database is shut down.
# ps -ef | grep avsdb
Copy all files in /arroyo/db/DATADIR directory from the Vault to the CDSM.
As user root, restart the Vault database.
# su - isa
# ps -ef | grep avsdb
As user root, restart the CDSM database.
# su - isa
# ps -ef | grep avsdb
Check the configuration on the CDSM and make sure no configuration parameters were lost.
Advanced Features and Applications
This section covers the Media Scheduler feature (live multicast ingest).
Live Multicast Ingest
Live multicast ingest is available as part of the Media Scheduler feature or the Real-Time Capture feature.
Ingest with Media Scheduler
Using Media Scheduler for live multicast ingest requires the following procedures:
1.
2.
3.
Enable live ingest by setting both the Media Scheduler and the Ingest Manager to ON in the CDSM
Setup. See the
“Initializing the CDS and Activating the Optional Features” section on page 3-3 for
more information.
Use the CDSM Input Channels page to configure the input channels. See the
Channels” section on page 4-24 for more information.
Upload channel schedules by importing the electronic program guide (EPG). See the
EPG File” section on page 7-10
for more information.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
A-41
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. See the
“Initializing the CDS and Activating the Optional Features” section on page 3-3
for more information.
2.
Use the CDSM CallSign Setup page to configure call signs with multicast IP addresses.
Ingest Troubleshooting
If the message “ERROR: Unable to login to the ftp location,” is present in the /home/isa/bss/log/aim.log file, check the FTP server configured in the Ingest Manager by using the ps -ef | grep ftp command. If the FTP service is not running, enter the service vsftpd start command to start it.
Frequently Asked Questions
Many of the frequently asked questions (FAQs) responses were based on an ISV system, but guidelines can be easily extrapolated for a Vault and Streamer. This section covers the following topics:
•
•
•
•
Serviceability and Manageability
Reliability and Availability
Q.
How do I enable stream resiliency?
A.
Log in to the CDSM with engineering access. The CDSM Setup page is displayed. For Stream
Failover Support, choose “ON” and click Submit. For more information, see the
.
Q.
How do I check and make sure the database is running properly?
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.193, 172.22.97.195 and 172.22.97.191).
# netstat -an|grep 9999 tcp 0 0 172.22.97.194:9999 172.22.97.195:48652 ESTABLISHED tcp 0 0 172.22.97.194:9999 172.22.97.191:42732 ESTABLISHED tcp 0 0 172.22.97.194:54563 172.22.97.195:9999 ESTABLISHED tcp 0 0 172.22.97.194:39342 172.22.97.191:9999 ESTABLISHED tcp 0 0 172.22.97.194:9999 172.22.97.192:40207 ESTABLISHED tcp 0 0 172.22.97.194:41815 172.22.97.192:9999 ESTABLISHED tcp 0 0 172.22.97.194:9999 172.22.97.193:33196 ESTABLISHED tcp 0 0 172.22.97.194:43269 172.22.97.193:9999 ESTABLISHED
Cisco TV CDS 2.3 RTSP Software Configuration Guide
A-42 OL-22792-01
Appendix A Troubleshooting
Frequently Asked Questions
tcp 0 0
If you can not see both listening and non-listening sockets binding on port 9999 for each of the remote servers, the database is not running properly. Check that you have the correct replication group members in your /home/isa/.arroyorc file.
Serviceability and Manageability
Q.
How do I check the calypso server status?
A.
Log in to the server as root and enter the cat /proc/calypso/status/server_settings command.
Q.
How do I check central processing unit (CPU)?
A.
Log in to the server as root and enter the cat /proc/cpuinfo command.
Q.
How do I check the kernel network driver version?
A.
Log in to the server as root and list the e1000.ko file to check the date and time it was created using the following command:
ls -l /lib/modules/<
current running kernel name>/kernel/drivers/net/e1000/e1000.ko
The following example shows that the e1000.ko file is based on the kernel
2.5.18-53.el5.kernel.2_6_18.2009.01.08.01.
# ls -l /lib/modules/2.6.18-53.el5.kernel.2_6_18.2009.01.08.01/kernel/drivers/net/e1000/e1000.ko
-rw-r--r-- 1 root root 2617502 Jan 8 18:13
/lib/modules/2.6.18-53.el5.kernel.2_6_18.2009.01.08.01/kernel/drivers/net/e1000/e1000.ko
Q.
How do I stop, start, and, restart the Apache server on the CDSM?
A.
Log in to the server as root and enter the following command:
# /arroyo/www/bin/apachectl stop
# /arroyo/www/bin/apachectl start
# /arroyo/www/bin/apachectl restart
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?
# echo 1 > /proc/calypso/test/arp_dumpstate
Q.
How do I recover the system from the kernel debugger (KDB) after a reboot?
A.
If the server starts the KDB tool instead of rebooting, modify the /etc/grub.conf file as follows: kdb=off panic=1 kernel /boot/vmlinuz-2.4.32avs ro root=/dev/hda1 console=tty0 console=ttyS0,115200 kdb=off panic=1
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
A-43
Appendix A Troubleshooting
Frequently Asked Questions
Q.
What do I do if the KDB prompt is displayed when the server restarts after a failure?
A.
Boot into single user-mode (see the “Kernel Crash” section on page A-14
).
Q.
How do I identify any holes in the content?
A.
Log in to the server as root and enter the following commands:
# echo 2 > /proc/calypso/tunables/cm_logserverinfo
# cat /arroyo/log/serverinfo.log.01132009
Look at the last two lines of output. If there are no holes, the last two lines should be the following:
BeingDeleted=0 HasHoles=0 CopyHoles=0 SectorHoles=0
Object Status Check Complete.
Q.
How do I clear cached video blocks (data cache) on the Streamer?
A.
Log in to the server as root and enter the echo 1 > /proc/calypso/test/clearcache command.
Q.
How do I clear the data cache in memory?
A.
Log in to the server as root and enter the echo 1 > /proc/calypso/test/clearmem command.
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, stop the services, change to the database table directory, remove the session table, and restart the services.
# arroyo stop
# cd /home/isa/bss/database/DATADIR
# rm RTSP_SESSION.db, RTSP_ANNEX.db
# arroyo start
All sessions are removed, and upon restarting the services, all streams that do not have an associated session are stopped.
Q.
How do I delete an individual stream from the database?
A.
Log in to the server as root and enter the following commands:
# su – isa
$ cd bss/database
$ ./AVSDBUtil
5
-> RTSP SESSIONS
2
-> GET ALL SESSIONS
1
-> DELETE SESSIONS
Enter the Session Handle:
Q.
How do I destroy all streams when none of the above methods work?
A.
Log in to the server as root and enter the following commands:
[root@ssv3 root]# /usr/bin/db_shutdown
[root@ssv3 root]# ps –ef |grep avs
Wait for all avs processes to stop, then reboot the server.
[root@ssv3 root]# reboot
A-44
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix A Troubleshooting
Q.
How do I check the routing table and gateway?
A.
Log in to the server as root and check the file /arroyo/test/RoutingTable.
# cat /arroyo/test/RoutingTable default gateway 192.169.131.250 network 192.169.131.0 netmask 255.255.255.0 gateway 0.0.0.0 default cache gateway 192.169.131.250 local cache network 192.169.131.0 netmask 255.255.255.0
Frequently Asked Questions
Content
Q.
How do I get information on a content stream that seems corrupted; for example, there is macroblocking, the stream stops and restarts, and so on?
A.
Log in to the server as root and enter the following commands:
# echo 2 > /proc/calypso/tunables/cm_logserverinfo
# 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.
Log in to the server as root and view the /var/log/debugmessages. There is a message in the debug messages file about the GOID and the content holes.
Q.
What do I do if content ingest is not working?
A.
Log in to the server as root, enter the less /home/isa/ContentStore/server/GenericLog.log command, and review the log for anomalies.
Q.
How do I delete ingests that are “stuck” in the active ingest state?
A.
Log in to the server as root and enter the following commands:
# su - isa
$ ./arroyo/db/AVSDBUtil log4cxx: No appender could be found for logger (cdscommon.db).
log4cxx: Please initialize the log4cxx system properly.
***************************************
1: CONTENT
2: FSI LOG
3: FSI LPI
4: RTSP Config
5: RTSP SESSIONS
0: EXIT
Enter [1/2/3/4/5] or 0? :
***************************************
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
A-45
Appendix A Troubleshooting
Frequently Asked Questions
Choose the option 1 (CONTENT). In the next menu, choose option 1 (DELETE CONTENT). Enter the content ID of the “stuck” ingest, then choose the exit option for each menu until you are back at the Linux prompt.
Q.
How do I manually ingest content from the command line?
A.
Log in to the server as root and enter the following commands:
# su - isa
# cd ~/SDClient
Update the SDClient.cfg file with the local IP address.
# ./sdClient
Follow the SDClient menus.
Other
Q.
How do I view the CServer code configuration file?
A.
Log in to the server as root and enter the cat /arroyo/test/<server type>/setupfile command. The server type is one of the following: vault, streamer, or ssv.
# cat /arroyo/test/<server type>/setupfile
# CServer core configuration. Changes to this file require
# a server reboot.
local 0 0 2 remote 0 0 2 fill 3 1 maxrate 900000 localip 0c0a80040 localip 0c0a80040 e1000 adapters: maxrate 965 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.<date> file. When you see the “COST REQUEST NO
CAPACITY:” message, it means that the server is running out of capacity and it cannot accept new streaming requests.
Also, when you see a line in the /arroyo/log/c2k.log.<date> file that says the following:
01-May-2007 17:40:44 UTC :err:ServeStream::reserveStream: refused streamhandle 4 for goid a445c9780e7f8f due to its load 3750, current load 0
This entry typically means there are no stream ports linked. In the ten-second snapshot of the
/arroyo/log/protocoltiming.log.<date> file, there is a line that shows load values for each of the major subsystems (LAN, memory, CPU, and so on). More than likely one of the subsystems is at
100, which is the subsystem that is having the problem.
A-46
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix A Troubleshooting
Q.
How do I enable debugging?
A.
Log in to the server as root and enter the following commands:
# su - isa
# cd ~/StreamsDriver
# touch DEBUGGING_ON
# ~/IntegrationTest/debugging_on_off
#./stop_driver
#./run_driver
Q.
How do I update the remote servers from /arroyo/test/RemoteServers?
A.
Log in to the server as root and enter the following commands:
# echo 1 > /proc/calypso/test/readremoteservers
CDS Content Quality Guidelines
CDS Content Quality Guidelines
This section covers the following topics:
•
•
•
•
•
•
Supported Elementary Stream Types
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.
Scrambling
The transport layer cannot be scrambled, meaning the transport header and any adaptation field must be in the clear. Streams whose Elementary Streams (ESs) are fully scrambled, including all start codes, are capable of being ingested and streamed, but are incapable of trick play.
For trick-play capability, the following cannot be scrambled:
•
Packetized Elementary Stream (PES) headers
•
•
Program Association Table (PAT) and Program Map Table (PMT)
Closed-caption data (if scrambled, the data is incorrectly included in tricks)
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
A-47
Appendix A Troubleshooting
CDS Content Quality Guidelines
Transport Bit Rate
All transport streams are constant bit rate (CBR). Variable bit rate (VBR) is not supported. The maximum bit rate is 35 Mbps. There is no minimum bit rate. The ES video bit rate, as specified in the
MPEG-2 sequence header, is ignored. The bit rates of individual ESs do not matter. The CBR for an individual ES (in particular the video) is not required. All that is required is that the aggregate transport stream be CBR.
Streams containing MPEG-2 or AVC video are expected to conform to the appropriate buffer models spelled out in ISO/IEC 13818-1 and 14496-10 .
Stream Length
All content must be at least one second in length. A content item must be under 12 hours in length or
15 GB, whichever comes first.
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.
Preferred Formats
Using the following guidelines improves the performance of the system, the quality of the tricks, and the trick transitions.
1.
All content should be encoded as a Single Program Transport Stream (SPTS) . If multiple programs must be included (for example, a Picture-in-Picture (PIP) stream), ensure that the “real” program is encoded with the lowest program number.
2.
3.
All content should follow the process ID (PID) numbering specified in the Content Encoding
Profiles 2.0 Specification (MD-SP-VOD-CEP2.0-I02-070105), section 6.7.5. Regardless, the audio and video PIDs should be above 0x20.
All content should be preceded with a Program Association Table (PAT) and then a Program Map
Table (PMT), and then a Program Clock Reference (PCR) before the first audio or video frame.
Optionally, the discontinuity bit can be set.
4.
5.
6.
All content should use the same PID for both PCR and video.
All content should begin with a closed Group Of Pictures (GOP) for MPEG-2 or with an
Instantaneous Decoder Refresh (IDR) frame for AVC. This first frame is always accompanied by a sequence header for MPEG-2 or by an SPS for AVC.
To guarantee relatively smooth looking trick modes, the minimum I/IDR-frame frequency should be eight per second. If the minimum trick speed is 4x or less, the I/IDR-frame frequency should be at least two per second. In no case should two I/IDR frames be more than two seconds apart.
A-48
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix A Troubleshooting
CDS Content Quality Guidelines
7.
8.
9.
Each I-frame should be preceded by a sequence header and GOP header if any exist for an MPEG-2 video. Each I/IDR frame should be preceded by an SPS and Picture Parameter Set (PPS) for H.264 video.
Avoid mixing frame data from multiple video frames in the same transport packet. Specifically, no data belonging to the prior frame exists following the Packetized Elementary Stream (PES) packet header for the next frame. Breaking this rule may improve encoding efficiency slightly, but degrades the quality of the tricks on certain set-top boxes (STBs).
All content must be encoded as a single sequence, with no changes in horizontal or video resolutions, or changes in encoding parameters in the middle of the content.
10.
11.
12.
13.
14.
The GOP size may be variable, but GOPs should generally not exceed two seconds. Using longer
GOPs may improve encoding efficiency, but the quality of lower-speed tricks (3x, 4x) may suffer.
No more than four B-frames should be used between each pair of I-frames or P-frames.
There should be no continuity counter errors in the content.
There should be no discontinuities in the content, other than an optional one on the first PCR.
15.
16.
17.
18.
The accuracy requirements for PCRs, +/–five parts per million (5 ppm), as stated in ISO/IEC
13818-1, must be adhered to throughout the stream.
Audio and video are expected not to overflow the appropriate target buffer model specified.
A reasonable bit rate to use when encoding MPEG-2 standard definition (SD) video is 3.75 Mbps.
A reasonable bit rate to use when encoding MPEG-2 high definition (HD) video is 15 Mbps.
19.
Appropriate bit rates for carriage of AVC are still being established, and while they are expected to be at least half the bit rates of MPEG-2, no specific recommendations can be offered.
There may be PIDs in the content that are not specified in the PMT. Such use is beyond the scope of this document.
20.
21.
22.
23.
All PATs and PMTs should be identical, with the same version number throughout.
The CDS support up to 30 Mbps MPEG-2 video encoding.
Content is filtered out if three occurrences of one-second synchronization lost are identified.
Content is filtered out if five seconds of null frames are identified.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
A-49
CDS Content Quality Guidelines
Appendix A Troubleshooting
A-50
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
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:
•
•
•
•
•
•
•
•
•
•
Creating QAM Gateway Bulk Configuration Files, page B-2
Creating Stream Destination Bulk Configuration Files, page B-4
Creating Route Table Bulk Configuration Files, page B-5
Creating SNMP Agent Bulk Configuration Files, page B-6
Creating DNS Server Bulk Configuration Files, page B-7
Creating NTP Server Bulk Configuration Files, page B-8
Creating FSI Setup Bulk Configuration Files, page B-9
Creating RTSP Setup Bulk Configuration Files, page B-10
Bulk Configuration XML Schema, page B-13
Introduction
Bulk Configuration provides a method of configuring common parameters for all the servers at one time by using an XML file. Following are the CDSM GUI configuration pages that offer Bulk Configuration:
•
QAM Gateway
•
•
•
•
•
Headend Setup
Stream Destination
NTP Server
Server DNS
•
•
•
SNMP Agent
Route Tables
RTSP Setup
FSI Setup
Note
To enable the optional Bulk Configuration feature, see the
“Bulk Configuration” section on page D-4
.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
B-1 OL-22792-01
Appendix B Creating Bulk Configuration Files
Creating QAM Gateway Bulk Configuration Files
Creating QAM Gateway Bulk Configuration Files
The QAM Gateway page is used to identify the QAM device (IP address), and to configure the preference settings for the Stream Groups. For Layer 2 networks, there is an option to specify the MAC address of the next hop for each Stream Group and Streamer.
Note
Before you can use the Bulk Configuration feature to configure QAM gateways and the headend setup, all Streamers must be associated with a Stream Group. For more information on Stream Groups, see the
“Configuring Stream Groups” section on page 4-29
.
describes the Bulk Configuration file elements for QAM gateways for gigabit Ethernet streaming.
Bulk Configuration File Elements for Gigabit Ethernet QAM Gateways Table B-1
Tag
QAMList
Elements
QAM
Attributes
—
Description
Marks beginning and end of QAM devices.
QAM QAMStreamGroupPreference IP
QAMStreamGroupPreference Server StreamGroupName
QAMMAC
Preference
Server — ServerID
GroupID
QAMMAC
Defines a QAM device.
Maps Stream Groups to the QAM device. The QAMMAC attribute is optional and is only used for Layer 2 networks.
Optional. Maps the MAC address of the QAM device to a Streamer. Only used in Layer 2 networks.
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-58
.
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 Preference attribute can have a value of High or None. These values are case sensitive.
Following is an example of the Bulk Configuration file used to populate the QAM Gateway page. The example is for a Layer 2 network and uses the optional QAMMAC attribute for the
QAMStreamGroupPreference and the optional Server element to specify the next hop MAC address.
<QAMList xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >
<QAM IP="1.1.1.1">
<QAMStreamGroupPreference StreamGroupName="SG1" QAMMAC="00:00:00:00:00:01" Preference="High">
<Server ServerID="50" GroupID="1" QAMMAC="00:00:00:00:00:11" />
</QAMStreamGroupPreference>
<QAMStreamGroupPreference StreamGroupName="SG2" QAMMAC="00:00:00:00:00:02" Preference="None">
<Server ServerID="55" GroupID="1" QAMMAC="00:00:00:00:00:11" />
</QAMStreamGroupPreference >
<QAMStreamGroupPreference StreamGroupName="SG3" QAMMAC="00:00:00:00:00:03" Preference="None"/>
</QAM>
Cisco TV CDS 2.3 RTSP Software Configuration Guide
B-2 OL-22792-01
Appendix B Creating Bulk Configuration Files
Creating Headend Setup Bulk Configuration Files
<QAM IP="1.1.1.2">
<QAMStreamGroupPreference StreamGroupName="SG1" QAMMAC="00:00:00:00:00:01" Preference="None"/>
<QAMStreamGroupPreference StreamGroupName="SG2" QAMMAC="00:00:00:00:00:02" Preference="High"/>
</QAM>
</QAMList>
Creating Headend Setup Bulk Configuration Files
The Bulk Configuration file for the Headend Setup page consist of service groups to Stream Groups mappings.
Table B-2 defines the Bulk Configuration file elements for headend setup.
Table B-2
Tag
Headend
Bulk Configuration File Elements for Headend Setup
Elements Attributes
ServiceGroupToStreamGroup —
ServiceGroupToStreamGroup — ServiceGroup
StreamGroup
Description
Marks beginning and end of mapping of service groups to Stream Groups.
Maps service groups to Stream Groups.
. Following is an example of the Bulk Configuration file used to populate the Headend Setup page:
<?xml version="1.0" encoding="UTF-8"?>
<Headend
xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >
<ServiceGroupToStreamGroup ServiceGroup="4666669" StreamGroup="NEWTEST" />
<ServiceGroupToStreamGroup ServiceGroup="4666668" StreamGroup="s234" />
<ServiceGroupToStreamGroup ServiceGroup="4666664" StreamGroup="NEWTEST" />
<ServiceGroupToStreamGroup ServiceGroup="4666663" StreamGroup="s234" />
<ServiceGroupToStreamGroup ServiceGroup="1666669" StreamGroup="NEWTEST123" />
<ServiceGroupToStreamGroup ServiceGroup="1666668" StreamGroup="s234" />
<ServiceGroupToStreamGroup ServiceGroup="1666664" StreamGroup="NEWTEST" />
<ServiceGroupToStreamGroup ServiceGroup="1666663" StreamGroup="s234" />
</Headend>
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
B-3
Appendix 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. For more information, see the
“Stream Destination” section on page D-4
. The Stream Destination page provides a way to associate subnetworks with Stream Groups.
defines the Bulk Configuration file elements for Stream Destination.
Table B-3 Bulk Configuration File Elements for Stream Destination
Tag
StreamDestinationList
Elements
StreamDestination
Attributes
—
Description
Marks beginning and end of subnets defined for IPTV.
Defines a subnet.
StreamDestination StreamGroupPreference SubnetAddress
SubnetMask
StreamGroupPreference — StreamGroupName
Preference
Maps Stream Groups to the subnet address.
For information about the values of the attributes, see the
“Configuring Stream Destinations” section on page 4-8 .
Note
The Preference attribute can have a value of High or None. These values are case sensitive.
Following is an example of the Bulk Configuration file used to populate the Stream Destination page.
<?xml version="1.0" encoding="UTF-8"?>
<StreamDestinationList
xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs">
<StreamDestination SubnetAddress="132.2.2.0" SubnetMask="255.255.255.0" >
<StreamGroupPreference StreamGroupName="NEWTEST" Preference="High" />
<StreamGroupPreference StreamGroupName="s234" Preference="None" />
</StreamDestination>
<StreamDestination SubnetAddress="130.10.10.0" SubnetMask="255.255.255.0" >
<StreamGroupPreference StreamGroupName="s234" Preference="High" />
<StreamGroupPreference StreamGroupName="NEWTEST" Preference="None" />
</StreamDestination>
</StreamDestinationList>
B-4
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
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-66 .
Table B-4 defines the Bulk Configuration file elements for the Route Table page.
Table B-4
Route
Bulk Configuration File Elements for Route Tables
Tag Elements
RouteTableList RouteTable
RouteTable Server
Route
Server —
—
Attributes
—
—
ServerID
GroupID
Network
SubnetMask
Gateway
RouteType
Description
Marks beginning and end of defined routes.
Defines a route table.
Identifies the CDS server.
Defines a route.
For information about the values of the attributes, see the
“Configuring the Route Table” section on page 4-66
. 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-58
.
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 RouteType attributes possible values are: cServer Source, cServer Destination, or Stream
Control. These values are case sensitive.
Following is an example of the Bulk Configuration file used to populate the Route Table page:
<?xml version="1.0" encoding="UTF-8"?>
<RouteTableList xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >
<RouteTable>
<Server ServerID="ALL" GroupID="ALL"/>
<Route Network="3.2.3.0" SubnetMask="255.255.255.0" Gateway="1.1.1.10" RouteType="cServer Source" />
<Route Network="3.2.5.0" SubnetMask="255.255.255.0" Gateway="1.1.1.1" RouteType="cServer Source" />
<Route Network="3.2.6.0" SubnetMask="255.255.255.0" Gateway="1.1.1.10" RouteType="cServer Source"/>
<Route Network="4.2.7.0" SubnetMask="255.255.255.0" Gateway="1.1.1.10" RouteType="cServer Source" />
<Route Network="5.2.8.0" SubnetMask="255.255.255.0" Gateway="1.1.1.10" RouteType="cServer Source" />
<Route Network="2.2.9.0" SubnetMask="255.255.255.0" Gateway="1.1.1.10" RouteType="cServer Source" />
<Route Network="6.2.10.0" SubnetMask="255.255.255.0" Gateway="1.1.1.10" RouteType="cServer Source" />
<Route Network="7.2.21.0" SubnetMask="255.255.d255.0" Gateway="1.1.1.10" RouteType="cServer Source" />
</RouteTable>
<RouteTable>
<Server ServerID="50" GroupID="1111"/>
<Server ServerID="51" GroupID="1111"/>
<Server ServerID="52" GroupID="1111"/>
<Server ServerID="53" GroupID="1111"/>
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01 B-5
Appendix B Creating Bulk Configuration Files
Creating SNMP Agent Bulk Configuration Files
<Route Network="120.2.3.0" SubnetMask="255.255.255.0" Gateway="1.1.1.10" RouteType="cServer Source" />
<Route Network="120.2.4.0" SubnetMask="255.255.255.0" Gateway="1.1.1.11" RouteType="cServer Source" />
<Route Network="120.2.5.0" SubnetMask="255.255.255.0" Gateway="1.1.1.1" RouteType="cServer Source" />
<Route Network="120.120.2.6" SubnetMask="255.255.255.0" Gateway="1.1.1.10" RouteType="cServer Source" />
<Route Network="120.2.7.0" SubnetMask="255.255.255.0" Gateway="1.1.1.10" RouteType="cServer Source" />
<Route Network="120.2.8.0" SubnetMask="255.255.255.0" Gateway="1.1.1.10" RouteType="cServer Source" />
<Route Network="120.2.9.0" SubnetMask="255.255.255.0" Gateway="1.1.1.10" RouteType="cServer Source" />
<Route Network="120.2.10.0" SubnetMask="255.255.255.0" Gateway="1.1.1.10" RouteType="cServer Source" />
<Route Network="120.2.21.0" SubnetMask="255.255.d255.0" Gateway="1.1.1.10" RouteType="cServer Source" />
</RouteTable>
</RouteTableList>
Creating SNMP Agent Bulk Configuration Files
The SNMP Agent page is used to configure SNMP communication. Table B-5
defines the Bulk
Configuration file elements for the SNMP Agent page.
Table B-5 Bulk Configuration File Elements for SNMP Agent
Tag
SNMPAgentList
Elements
SNMPAgent
Attributes
—
SNMPAgent
Server
SNMPCommunity
SNMPTrapStation
Server
SNMPCommunity
SNMPTrapStation
—
—
—
Contact
Location
ServerID
GroupID
Name
Permissions
TrapStation
Version
Description
Marks beginning and end of defined SNMP agents.
Defines an SNMP agent.
Identifies the CDS server.
Defines the community for the SNMP agent.
Defines the trap station for the SNMP agent.
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-58 .
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.
Following is an example of the Bulk Configuration file used to populate the SNMP Agent page:
<?xml version="1.0" encoding="UTF-8"?>
<SNMPAgentList
xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >
<SNMPAgent Contact="TestContact" Location="TestLocation">
<Server ServerID="ALL" GroupID="ALL"/>
<SNMPCommunity Name="public" Permissions="Read-Only" />
<SNMPCommunity Name="public2" Permissions="Read-Only" />
Cisco TV CDS 2.3 RTSP Software Configuration Guide
B-6 OL-22792-01
Appendix B Creating Bulk Configuration Files
Creating DNS Server Bulk Configuration Files
<SNMPTrapStation TrapStation="77.77.77.77" Version="v1"/>
<SNMPTrapStation TrapStation="177.77.77.77" Version="v2"/>
</SNMPAgent>
<SNMPAgent Contact="XXXX" Location="YYYY">
<Server ServerID="71" GroupID="1111"/>
<Server ServerID="72" GroupID="1111"/>
<Server ServerID="73" GroupID="1111"/>
<Server ServerID="74" GroupID="1111"/>
<Server ServerID="75" GroupID="1111"/>
<SNMPCommunity Name="XXXX" Permissions="Read-Only" />
<SNMPCommunity Name="YYYY" Permissions="Read-Only" />
<SNMPTrapStation TrapStation="5.99.99.9" Version="v1"/>
<SNMPTrapStation TrapStation="55.77.77.77" Version="v2"/>
</SNMPAgent>
</SNMPAgentList>
.
Creating DNS Server Bulk Configuration Files
The Server DNS page is used to configure the DNS servers.
Table B-6 defines the Bulk Configuration
file elements for the Server DNS page.
Table B-6 Bulk Configuration File Elements for DNS Server
Tag
DNSList
DNS
Server
DomainSuffix
DNSServer
Elements
DNS
Server
DomainSuffix
DNSServer
—
—
—
Attributes
—
—
ServerID
GroupID
—
—
Description
Marks the beginning and ending of the DNS settings
Defines the DNS server settings.
Identifies the CDS server.
Defines the domain suffix.
Defines the DNS server.
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-58
.
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 Permission attribute can have the value of Read-Only or Read-Write.
Following is an example of the Bulk Configuration file used to populate the Server DNS page:
<<?xml version="1.0" encoding="UTF-8"?>
<DNSList
xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >
<DNS>
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
B-7
Creating NTP Server Bulk Configuration Files
<Server ServerID="ALL" GroupID="ALL"/>
<DomainSuffix>first.sp.com</DomainSuffix>
<DomainSuffix>second.abc.com</DomainSuffix>
<DomainSuffix>third.xyz.com</DomainSuffix>
<DNSServer>152.1.1.10</DNSServer>
<DNSServer>222.2.2.11</DNSServer>
</DNS>
</DNSList>
Appendix B Creating Bulk Configuration Files
Creating NTP Server Bulk Configuration Files
The NTP Server page is used to configure the NTP servers.
Table B-7 defines the Bulk Configuration
file elements for the NTP Server page.
Table B-7
NTPServerIP
Bulk Configuration File Elements for NTP Server
Tag Elements
NTPServerList NTPServer
NTPServer Server
NTPServerIP
Server —
—
Attributes
—
—
ServerID
GroupID
—
Description
Marks the beginning and ending of the NTP settings.
Defines the NTP settings.
Identifies the CDS server.
Defines the NTP server.
. 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-58 .
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.
Following is an example of the Bulk Configuration file used to populate the NTP Server page:
<<?xml version="1.0" encoding="UTF-8"?>
<NTPServerList
xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >
<NTPServer>
<Server ServerID="ALL" GroupID="ALL"/>
<NTPServerIP>198.168.1.10</NTPServerIP>
<NTPServerIP>172.31.2.11</NTPServerIP>
</NTPServer>
</NTPServerList>
B-8
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix B Creating Bulk Configuration Files
Creating FSI Setup Bulk Configuration Files
Creating FSI Setup Bulk Configuration Files
The FSI Setup page is used to configure the FSI.
defines the Bulk Configuration file elements for the FSI Setup page.
Table B-8 Bulk Configuration File Elements for FSI Setup
Tag Elements Attributes
FSISetupList FSISetup —
FSISetup
Server
Server
—
IPAddress
ServerPort
FTPClientPort
FTPOutServerPort
FTPOutLoginTTL
LogLevel
ContentRootPath
AsyncCallbackURL
ServerID
GroupID
Description
Marks the beginning and ending of the FSI settings.
Defines the FSI settings.
Identifies the CDS server.
For information about the values of the attributes, see the
“Configuring FSI Setup” section on page 4-81 .
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-58 .
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 LogLevel attribute can have the value of High, Low, or Off.
Following is an example of the Bulk Configuration file used to populate the FSI Setup page:
<?xml version="1.0" encoding="UTF-8"?>
<FSISetupList
xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >
<FSISetup IPAddress="171.1.1.1"
ServerPort="333"
FTPClientPort="555"
FTPOutServerPort="5001"
FTPOutLoginTTL="64"
LogLevel="Off"
ContentRootPath="/videcontent/"
AsyncCallbackURL="http://1.1.1.1/test.php" >
<Server ServerID="61" GroupID="1111"/>
</FSISetup>
</FSISetupList>
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
B-9
Appendix B Creating Bulk Configuration Files
Creating RTSP Setup Bulk Configuration Files
Creating RTSP Setup Bulk Configuration Files
The RTSP Setup page is used to configure the RTSP. Table B-9
defines the Bulk Configuration file elements for the RTSP Setup page.
Table B-9 Bulk Configuration File Elements for RTSP Setup
Tag
RTSPSetupList
RTSPSetup
Server
Elements
RTSPSetup
RTSPClientList RTSPClient
RTSPClient
Server
RTSPClientList
—
—
Attributes
—
ReceivePort
SendPOrt
ReceiveBuffer
Model
Transport
Description
Marks the beginning and ending of the RTSP settings.
Defines the RTSP settings.
See the RTSP Setup Fields table for a description of the values and the applicable fields for your RTSP deployment.
ServerID
GroupID
—
Identifies the CDS server.
Marks the beginning and ending of the RTSP clients.
Defines the RTSP client.
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-58 .
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.
Following are examples of the Bulk Configuration file used to populate the RTSP Setup page for the different RTSP deployment types:
DSM-CC RTSP Deployment
<?xml version="1.0" encoding="UTF-8"?>
<RTSPSetupList
xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >
<RTSPSetup MasterStreamingIP="1.1.1.1"
BackofficeTimeout="3000"
RTSPServerIP="121.1.1.2"
LSCPAddress="1.1.1.1"
LSCPPort="1111"
LSCPResponsePadding="on"
RTSPServerPort="5000"
LogLevel="Off"
MaintenanceMode="on">
<Server ServerID="5" GroupID="111"/>
<RTSPClient ReceivePort="111" SendPort="222" ReceiveBuffer="65535" Model="nCube" Transport="TCP" />
B-10
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix B Creating Bulk Configuration Files
Creating RTSP Setup Bulk Configuration Files
<RTSPClient ReceivePort="999" SendPort="888" ReceiveBuffer="65535" Model="Diego" Transport="TCP" />
</RTSPSetup>
</RTSPSetupList>
RTSP RTSP Deployment
<?xml version="1.0" encoding="UTF-8"?>
<RTSPSetupList
xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >
<RTSPSetup MasterStreamingIP="121.1.1.1"
LoopingSessionTimeout="11000"
SessionInactivityTimeout="22000"
BackofficeTimeout="33000"
RTSPServerIP="171.1.1.2"
RTSPServerPort="15000"
ReconnectIP="12.1.1.3"
ReconnectPort="9000"
MaxHistory="5"
LogLevel="high"
MaintenanceMode="off">
<Server ServerID="2" GroupID="1111"/>
<RTSPClient ReceivePort="3111" SendPort="9222" ReceiveBuffer="65535" Model="nCube" Transport="TCP" />
<RTSPClient ReceivePort="3999" SendPort="9888" ReceiveBuffer="65535" Model="Diego" Transport="TCP" />
</RTSPSetup>
</RTSPSetupList>
NGOD RTSP Deployment
<?xml version="1.0" encoding="UTF-8"?>
<RTSPSetupList
xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >
<RTSPSetup MasterStreamingIP="1.1.1.1"
BackofficeTimeout="3000"
SessionInactivityTimeout="22000"
RTSPServerIP="121.1.1.2"
RTSPServerPort="5000"
LSCPAddress="1.1.1.1"
LSCPPort="1111"
LSCPResponsePadding="on"
ComponentName="xyz"
LogLevel="low"
MaintenanceMode="on">
<Server ServerID="2" GroupID="1111"/>
<RTSPClient ReceivePort="111" SendPort="222" ReceiveBuffer="65535" Model="nCube" Transport="TCP" />
<RTSPClient ReceivePort="999" SendPort="888" ReceiveBuffer="65535" Model="Diego" Transport="TCP" />
</RTSPSetup>
</RTSPSetupList>
IPTV RTSP Deployment
<?xml version="1.0" encoding="UTF-8"?>
<RTSPSetupList
xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >
<RTSPSetup MasterStreamingIP="1.1.1.1"
SessionInactivityTimeout="22000"
LogLevel="high"
MaintenanceMode="on">
<Server ServerID="2" GroupID="1111"/>
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
B-11
Appendix B Creating Bulk Configuration Files
Creating RTSP Setup Bulk Configuration Files
<RTSPClient ReceivePort="111" SendPort="222" ReceiveBuffer="65535" Model="nCube" Transport="TCP" />
<RTSPClient ReceivePort="999" SendPort="888" ReceiveBuffer="65535" Model="Diego" Transport="TCP" />
</RTSPSetup>
</RTSPSetupList>
EventIS on-vpath RTSP Deployment
<?xml version="1.0" encoding="UTF-8"?>
<RTSPSetupList
xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >
<RTSPSetup MasterStreamingIP="172.1.1.1"
BackofficeTimeout="3000"
SessionInactivityTimeout="22000"
AuthenticationManagerIP="121.1.1.2"
AuthenticationManagerPort="5000"
BandwidthManagerIP="121.1.1.2"
BandwidthManagerPort="5000"
BackupBandwidthManagerIP="1.1.1.1"
BackupBandwidthManagerPort="1111"
LogLevel="high"
MaintenanceMode="off">
<Server ServerID="2" GroupID="1111"/>
<RTSPClient ReceivePort="111" SendPort="222" ReceiveBuffer="65535" Model="nCube" Transport="TCP" />
<RTSPClient ReceivePort="999" SendPort="888" ReceiveBuffer="65535" Model="Diego" Transport="TCP" />
</RTSPSetup>
</RTSPSetupList>
EventIS off-vpath RTSP Deployment
<?xml version="1.0" encoding="UTF-8"?>
<RTSPSetupList
xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >
<RTSPSetup MasterStreamingIP="172.1.1.1"
SessionInactivityTimeout="22000"
AuthenticationManagerIP="121.1.1.2"
AuthenticationManagerPort="5000"
ServerIP="10.1.1.1"
ServerPort="5555"
StreamControlIP="191.1.1.2"
StreamControlPort="9000"
LogLevel="high"
MaintenanceMode="off">
<Server ServerID="2" GroupID="1111"/>
<RTSPClient ReceivePort="111" SendPort="222" ReceiveBuffer="65535" Model="nCube" Transport="TCP" />
<RTSPClient ReceivePort="999" SendPort="888" ReceiveBuffer="65535" Model="Diego" Transport="TCP" />
</RTSPSetup>
</RTSPSetupList>
Quative RTSP Deployment
<?xml version="1.0" encoding="UTF-8"?>
<RTSPSetupList
xmlns="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >
<RTSPSetup MasterStreamingIP="172.1.1.1"
SessionInactivityTimeout="2000"
CallbackServerIP="129.1.1.2"
CallbackServerPort="4000"
LogLevel="low"
MaintenanceMode="on">
B-12
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix B Creating Bulk Configuration Files
Bulk Configuration XML Schema
<Server ServerID="2" GroupID="1111"/>
<RTSPClient ReceivePort="111" SendPort="222" ReceiveBuffer="65535" Model="nCube" Transport="TCP" />
<RTSPClient ReceivePort="999" SendPort="888" ReceiveBuffer="65535" Model="Diego" Transport="TCP" />
</RTSPSetup>
</RTSPSetupList>
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.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:ws="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs"
targetNamespace="http://www.cisco.com/schemas/VCPBU/CDS-TV/R0/ciscowebsvcs" >
<!-- Configure/Server/ elements -->
<xs:element name="Server">
<xs:complexType>
<xs:attribute name="ServerID" type="xs:string" use="required"/>
<xs:attribute name="GroupID" type="xs:string" use="required"/>
<xs:attribute name="QAMMAC" type="xs:string"/>
</xs:complexType>
</xs:element>
<!-- Configure/System/QAMGateway/ elements -->
<xs:element name="QAMStreamGroupPreference">
<xs:complexType>
<xs:sequence>
<xs:element ref="ws:Server"
minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="StreamGroupName" type="xs:string"/>
<xs:attribute name="QAMMAC" type="xs:string"/>
<xs:attribute name="Preference" type="xs:string"/>
</xs:complexType>
</xs:element>
<xs:element name="TSIDOutLink">
<xs:complexType>
<xs:attribute name="Index" type="xs:nonNegativeInteger"/>
<xs:attribute name="TSIDOut" type="xs:string"/>
<xs:attribute name="TSIDOutLinkStatus" type="xs:string"/>
<xs:attribute name="ServiceGroup" type="xs:string"/>
<xs:attribute name="RFNumber" type="xs:string"/>
</xs:complexType>
</xs:element>
<xs:element name="QAMASILink">
<xs:complexType>
<xs:sequence>
<xs:element ref="ws:TSIDOutLink"
minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="Number" type="xs:string"/>
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
B-13
Appendix B Creating Bulk Configuration Files
Bulk Configuration XML Schema
<xs:attribute name="TSIDIn" type="xs:string"/>
<xs:attribute name="TSIDInLinkStatus" type="xs:string"/>
</xs:complexType>
</xs:element>
<xs:element name="QAMLink">
<xs:complexType>
<xs:attribute name="Status" type="xs:string"/>
<xs:attribute name="ServiceGroup" type="xs:string"/>
<xs:attribute name="RFNumber" type="xs:string"/>
</xs:complexType>
</xs:element>
<xs:element name="GQAMLink">
<xs:complexType>
<xs:sequence>
<xs:element ref="ws:TSIDOutLink"
minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="ServiceGroup" type="xs:string"/>
<xs:attribute name="RFNumber" type="xs:string"/>
</xs:complexType>
</xs:element>
<xs:element name="QAM">
<xs:complexType>
<xs:sequence>
<xs:element ref="ws:QAMStreamGroupPreference"
minOccurs="0"
maxOccurs="unbounded"/>
<xs:element ref="ws:QAMLink"
minOccurs="0"
maxOccurs="unbounded"/>
<xs:element ref="ws:QAMASILink"
minOccurs="0"
maxOccurs="unbounded"/>
<xs:element ref="ws:GQAMLink"
minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="IP" type="xs:string"/>
<xs:attribute name="Type" type="xs:string"/>
<xs:attribute name="GQAMPort" type="xs:positiveInteger"/>
</xs:complexType>
</xs:element>
<xs:element name="QAMList">
<xs:complexType>
<xs:sequence>
<xs:element ref="ws:QAM"
minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- Configure/System/StreamDestination/ elements -->
<xs:element name="StreamGroupPreference">
<xs:complexType>
<xs:attribute name="StreamGroupName" type="xs:string"/>
<xs:attribute name="Preference" type="xs:string"/>
</xs:complexType>
Cisco TV CDS 2.3 RTSP Software Configuration Guide
B-14 OL-22792-01
Appendix B Creating Bulk Configuration Files
Bulk Configuration XML Schema
</xs:element>
<xs:element name="StreamDestination">
<xs:complexType>
<xs:sequence>
<xs:element ref="ws:StreamGroupPreference"
minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="SubnetAddress" type="xs:string"/>
<xs:attribute name="SubnetMask" type="xs:string"/>
</xs:complexType>
</xs:element>
<xs:element name="StreamDestinationList">
<xs:complexType>
<xs:sequence>
<xs:element ref="ws:StreamDestination"
minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- Configure/System/Headend/ elements -->
<xs:element name="ServiceGroupToStreamGroup">
<xs:complexType>
<xs:attribute name="ServiceGroup" type="xs:string"/>
<xs:attribute name="StreamGroup" type="xs:string"/>
</xs:complexType>
</xs:element>
<xs:element name="Headend">
<xs:complexType>
<xs:sequence>
<xs:element ref="ws:QAM"
minOccurs="0"
maxOccurs="unbounded"/>
<xs:element ref="ws:ServiceGroupToStreamGroup"
minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- Configure/Server/RouteTables/ elements -->
<xs:element name="Route">
<xs:complexType>
<xs:attribute name="Network" type="xs:string"/>
<xs:attribute name="SubnetMask" type="xs:string"/>
<xs:attribute name="Gateway" type="xs:string"/>
<xs:attribute name="RouteType" type="xs:string"/>
</xs:complexType>
</xs:element>
<xs:element name="RouteTable">
<xs:complexType>
<xs:sequence>
<xs:element ref="ws:Server"
minOccurs="0"
maxOccurs="unbounded"/>
<xs:element ref="ws:Route"
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01 B-15
Appendix B Creating Bulk Configuration Files
Bulk Configuration XML Schema
minOccurs="0"
maxOccurs="unbounded" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="RouteTableList">
<xs:complexType>
<xs:sequence>
<xs:element ref="ws:RouteTable"
minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- Configure/Server/SNMP/ elements -->
<xs:element name="SNMPCommunity">
<xs:complexType>
<xs:attribute name="Name" type="xs:string"/>
<xs:attribute name="Permissions" type="xs:string"/>
</xs:complexType>
</xs:element>
<xs:element name="SNMPTrapStation">
<xs:complexType>
<xs:attribute name="TrapStation" type="xs:string"/>
<xs:attribute name="Version" type="xs:string"/>
</xs:complexType>
</xs:element>
<xs:element name="SNMPAgent">
<xs:complexType>
<xs:sequence>
<xs:element ref="ws:Server"
minOccurs="0"
maxOccurs="unbounded"/>
<xs:element ref="ws:SNMPCommunity"
minOccurs="0"
maxOccurs="unbounded"/>
<xs:element ref="ws:SNMPTrapStation"
minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="Contact" type="xs:string"/>
<xs:attribute name="Location" type="xs:string"/>
</xs:complexType>
</xs:element>
<xs:element name="SNMPAgentList">
<xs:complexType>
<xs:sequence>
<xs:element ref="ws:SNMPAgent"
minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- Configure/Server/RTSP/ elements -->
<xs:element name="RTSPClient">
<xs:complexType>
Cisco TV CDS 2.3 RTSP Software Configuration Guide
B-16 OL-22792-01
Appendix B Creating Bulk Configuration Files
Bulk Configuration XML Schema
<xs:attribute name="ReceivePort" type="xs:positiveInteger"/>
<xs:attribute name="SendPort" type="xs:positiveInteger"/>
<xs:attribute name="ReceiveBuffer" type="xs:positiveInteger"/>
<xs:attribute name="Model" type="xs:string"/>
<xs:attribute name="Transport" type="xs:string"/>
</xs:complexType>
</xs:element>
<xs:element name="RTSPSetup">
<xs:complexType>
<xs:sequence>
<xs:element ref="ws:Server"
minOccurs="0"
maxOccurs="unbounded"/>
<xs:element ref="ws:RTSPClient"
minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="MasterStreamingIP" type="xs:string"/>
<xs:attribute name="LoopingSessionTimeout" type="xs:positiveInteger"/>
<xs:attribute name="SessionInactivityTimeout" type="xs:positiveInteger"/>
<xs:attribute name="BackofficeTimeout" type="xs:positiveInteger"/>
<xs:attribute name="RTSPServerIP" type="xs:string"/>
<xs:attribute name="RTSPServerPort" type="xs:positiveInteger"/>
<xs:attribute name="ReconnectIP" type="xs:string"/>
<xs:attribute name="ReconnectPort" type="xs:positiveInteger"/>
<xs:attribute name="MaxHistory" type="xs:nonNegativeInteger"/>
<xs:attribute name="LogLevel" type="xs:string"/>
<xs:attribute name="MaintenanceMode" type="xs:string"/>
<xs:attribute name="LSCPAddress" type="xs:string"/>
<xs:attribute name="LSCPPort" type="xs:positiveInteger"/>
<xs:attribute name="LSCPResponsePadding" type="xs:string"/>
<xs:attribute name="ComponentName" type="xs:string"/>
<xs:attribute name="BandwidthManagerIP" type="xs:string"/>
<xs:attribute name="BandwidthManagerPort" type="xs:positiveInteger"/>
<xs:attribute name="AuthenticationManagerIP" type="xs:string"/>
<xs:attribute name="AuthenticationManagerPort" type="xs:positiveInteger"/>
<xs:attribute name="BackupBandwidthManagerIP" type="xs:string"/>
<xs:attribute name="BackupBandwidthManagerPort" type="xs:positiveInteger"/>
<xs:attribute name="CallbackServerIP" type="xs:string"/>
<xs:attribute name="CallbackServerPort" type="xs:positiveInteger"/>
<xs:attribute name="ServerIP" type="xs:string"/>
<xs:attribute name="ServerPort" type="xs:positiveInteger"/>
<xs:attribute name="StreamControlIP" type="xs:string"/>
<xs:attribute name="StreamControlPort" type="xs:positiveInteger"/>
</xs:complexType>
</xs:element>
<xs:element name="RTSPSetupList">
<xs:complexType>
<xs:sequence>
<xs:element ref="ws:RTSPSetup"
minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- Configure/Server/FSI/ elements -->
<xs:element name="FSISetup">
<xs:complexType>
<xs:sequence>
<xs:element ref="ws:Server"
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01 B-17
Appendix B Creating Bulk Configuration Files
Bulk Configuration XML Schema
minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="IPAddress" type="xs:string"/>
<xs:attribute name="ServerPort" type="xs:positiveInteger"/>
<xs:attribute name="FTPClientPort" type="xs:positiveInteger"/>
<xs:attribute name="FTPOutServerPort" type="xs:positiveInteger"/>
<xs:attribute name="FTPOutLoginTTL" type="xs:positiveInteger"/>
<xs:attribute name="LogLevel" type="xs:string"/>
<xs:attribute name="ContentRootPath" type="xs:string"/>
<xs:attribute name="AsyncCallbackURL" type="xs:string"/>
</xs:complexType>
</xs:element>
<xs:element name="FSISetupList">
<xs:complexType>
<xs:sequence>
<xs:element ref="ws:FSISetup"
minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- Configure/Server/DNS elements -->
<xs:element name="DomainSuffix" type="xs:string"/>
<xs:element name="DNSServer" type="xs:string"/>
<xs:element name="DNS">
<xs:complexType>
<xs:sequence>
<xs:element ref="ws:Server"
minOccurs="0"
maxOccurs="unbounded"/>
<xs:element ref="ws:DomainSuffix"
minOccurs="0"
maxOccurs="unbounded"/>
<xs:element ref="ws:DNSServer"
minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="DNSList">
<xs:complexType>
<xs:sequence>
<xs:element ref="ws:DNS"
minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- Configure/Server/NTPServer elements -->
<xs:element name="NTPServerIP" type="xs:string"/>
<xs:element name="NTPServer">
<xs:complexType>
<xs:sequence>
<xs:element ref="ws:Server"
Cisco TV CDS 2.3 RTSP Software Configuration Guide
B-18 OL-22792-01
Appendix B Creating Bulk Configuration Files
minOccurs="0"
maxOccurs="unbounded"/>
<xs:element ref="ws:NTPServerIP"
minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="NTPServerList">
<xs:complexType>
<xs:sequence>
<xs:element ref="ws:NTPServer"
minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
Bulk Configuration XML Schema
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
B-19
Bulk Configuration XML Schema
Appendix B Creating Bulk Configuration Files
B-20
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
A P P E N D I X
C
SNMP MIB and Trap Information
This appendix describes the Simple Network Management Protocol (SNMP) traps sent by the CDS. The topics covered in this appendix include:
•
•
•
SNMP Management Objects and Traps, page C-2
Overview
You can manage the servers by way of SNMP from a Network Management System (NMS). To implement SNMP management, the servers must be configured with a management IP address, SNMP community strings, and contact information. For more information about configuring the server for
SNMP communication, see the
“Configuring the SNMP Agent” section on page 4-69 .
Note
We recommend configuring a VLAN for management traffic.
SNMP management features on the servers include:
•
•
SNMP version 1 or version 2c
Standard MIBs
SNMP Agent
The SNMP agent on the server uses certain variables that are included in a Cisco Management
Information Base (MIB) file. By default, the SNMP agent is not started automatically. To start the SNMP agent, login to the server as root and enter the following command:
# nice -n 19 /usr/local/sbin/snmpd
To have the SNMP agent start automatically after a reboot, use the Linux vi editor to add the following to the /etc/rc.local file: nice -n 19 /usr/local/sbin/snmpd
To verify the SNMP agent has started, enter the ps -ef | grep snmpd command.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
C-1 OL-22792-01
Appendix C SNMP MIB and Trap Information
SNMP Management Objects and Traps
SNMP Management Objects and Traps
The CDS SNMP agent and Management Information Base (MIB) file are compliant with the Internet
Engineering Task Force (IETF) standards for SNMP v1 and SNMP v2c. For a list of SNMP-associated
Request For Comment (RFC) specifications, see the “RFC Compliance” section on page C-5
.
The CISCO-CDS-TV-MIB.txt MIB file is available through the CDSM, and is dependent on the following MIBs distributed on Cisco.com:
•
•
ftp://ftp.cisco.com/pub/mibs/v2/CISCO-SMI.my
ftp://ftp.cisco.com/pub/mibs/v2/CISCO-TC.my
•
ftp://ftp.cisco.com/pub/mibs/v2/CISCO-PRODUCTS-MIB.my
You can download the MIBs by doing the following:
Step 1
Step 2
Choose Configure > Server Level > SNMP Agent. The SNMP Agent page is displayed with a list of the MIB files at the bottom of the page.
To save the file locally, right-click the MIB filename, and choose Save As, Save Target As, or a similar save command.
To view the file, click the MIB filename.
The CISCO-CDS-TV-MIB.txt 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
describes the traps in the CISCO-CDS-TV-MIB.
Table C-1
cdstvDiskHealthDown cdstvMSAEvent cdstvServiceUp
Cisco TV CDS Traps
Trap
cdstvDiskHealthUp cdstvServiceDown
Description
Previously inactive disk is now active and ready, that is, the disk has returned to the OK (0) state.
Active disk is now inactive, that is, it has left the OK (0) state.
MSA event (error) has occurred.
Previously stopped service is now running, that is, it has left the not running state. The cdstvServiceName object, which contains the name of the service, is sent with the trap.
Previously running service is now stopped, that is, it has left the running state. The cdstvServiceName object, which contains the name of the service, is sent with the trap.
C-2
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix C SNMP MIB and Trap Information
SNMP Management Objects and Traps
Table C-1 Cisco TV CDS Traps (continued)
Trap
cdstvDiskUsageHigh
Description
Disk usage on the system has crossed the maximum usage threshold.
The cdstvDiskUsagePercent object, which contains the percentage of the disk that is used, is sent with the trap.
cdstvDiskUsageNormal cdstvLinuxFSUsageHigh
This trap corresponds to the Disk Capacity Notify field on the System
Threshold page. For more information, see the
Thresholds” section on page 7-7 . When the disk usage exceeds the
threshold set for the Disk Capacity Notify field, the cdstvDiskUsageHigh trap is sent.
Disk usage on the system has returned to a value within the usage threshold. The cdstvDiskUsagePercent object, which contains the percentage of the disk that is used, is sent with the trap.
Linux file system (FS) usage on the server has crossed the maximum usage threshold. The cdstvLinuxFSMountPoint and cdstvLinuxFSUsagePercent objects, which contain the mount point and the percentage used, are sent with the trap.
cdstvLinuxFSUsageNormal Linux file system (FS) usage on the server has returned to a value within the usage threshold. The cdstvLinuxFSMountPoint and cdstvLinuxFSUsagePercent objects, which contain the mount point and the percentage used, are sent with the trap.
cdstvPortLossHigh Port loss on the system has crossed the maximum threshold. The cdstvPortLossPercent object, which contains port loss percentage, is sent with the trap.
cdstvPortLossNormal cdstvSysHealthUp cdstvSysHealthDown
Port loss on the system has returned to a value within the threshold. The cdstvPortLossPercent object, which contains port loss percentage, is sent with the trap.
Previously abnormal system health parameter is now normal; that is, it has left the not OK state. See
Table C-2 on page C-4 for the descriptions
of the objects sent with this trap.
Previously normal system health parameter is now abnormal; that is, it has left the OK state. See
Table C-2 on page C-4 for the descriptions of
the objects sent with this trap.
Monitored Services SNMP Traps
The services reported as up or down in SNMP correspond to the services on the Service Monitor page.
For more information on the monitored services, see the
“Services Monitor” section on page 5-32
.
For the cdstvServiceUp and cdstvServiceDown traps, if the database shuts down, a cdstvServiceDown trap is sent for the Cisco DB server, but no other services can be monitored without the database running.
No SNMP traps are sent for services until the database is functional again.
If the SNMP agent itself is down, the CDSM shows the Cisco SNMP Server as “Not Running” but no
SNMP trap can be sent for this service because the SNMP agent itself is down.
If the CDS server is shut down cleanly, there may be a cdstvServiceDown trap sent for the Cisco SNMP
Server before the entire server shuts down. No traps can be sent until the SNMP agent is running.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
C-3
Appendix C SNMP MIB and Trap Information
SNMP Management Objects and Traps
System Health Threshold Crossing Alerts
The temperature, fans, and power are monitored on the CDS servers and the states and thresholds are
displayed on the Server Vitals page. See the “Server Vitals” section on page 5-29
. If a threshold is exceeded, an alarmed event is registered on the CDSM and the cdstvSysHealthDown trap is sent with information about the threshold crossing alert (TCA).
Note
The Server Vitals page is displayed only if the CDSM Health Monitor feature is enabled. For more information, see the
“CDSM or VVIM Health Monitoring” section on page D-9
.
describes the objects that are sent with the cdstvSysHealthUp and cdstvSysHealthDown traps.
Table C-2 System Health SNMP Trap Objects
Descriptor
cdstvSysHealthName
Possible values
String
Description
Name of the system health monitoring parameter, for example, VBAT Voltage.
Type of the system health monitoring parameter.
cdstvSysHealthType 1—Fan-speed
2—Voltage
3—Temperature
4—Chassis intrusion
5—Power supply failure cdstvSysHealthReading Integer cdstvSysHealthHighLimit Integer
Current reading (value) of the system health parameter; for example, fan speed, voltage, or temperature. Fan speed is expressed in rpm, voltage in mV and temperature in degree
Celsius. For chassis intrusion and power-supply failure, 1 denotes an error condition, and 0 denotes normal condition.
Higher limit (threshold) of the system health parameter. Voltage is expressed in mV and temperature in degree Celsius. Not applicable for other parameters such as fan speed.
cdstvSysHealthLowLimit Integer cdstvSysHealthStatus 1—Normal
2—Low
3—High
4—Not-OK
Lower limit (threshold) of the system health parameter. Fan speed is expressed in rpm and voltage in mV. Not applicable for other parameters such as temperature.
Current status of the system health parameter.
The not-ok value applies to power supply failure and chassis intrusion, because high and low limits do not apply to these parameters.
C-4
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix C SNMP MIB and Trap Information
RFC Compliance
RFC Compliance
Table C-3 is a list of SNMP RFC standards.
Table C-3 SNMP RFC Standards
RFC Standard Title
RFC 1155 (STD0016) Structure and Identification of Management Information for
TCP/IP-based Internets
RFC 1157 (STD0015) Simple Network Management Protocol (SNMP)
RFC 1212 (STD0016) Concise MIB Definitions
RFC 1213 (STD0017) Management Information Base for Network Management of
TCP/IP-based internets:MIB-II
RFC 2790 (Draft
Standard)
Host Resources MIB
RFC 1901(Historic)
RFC 1902 (Draft
Standard)
Introduction to Community-based SNMPv2
Structure of Management Information for Version 2 of the Simple
Network Management Protocol (SNMPv2)
RFC 1903 (Draft
Standard)
RFC 1904 (Draft
Standard)
RFC 1905 (Draft
Standard)
RFC 1906 (Draft
Standard)
RFC 1910 (Historic)
Textual Conventions for Version 2 of the Simple Network Management
Protocol (SNMPv2)
Conformance Statements for Version 2 of the Simple Network
Management Protocol (SNMPv2)
Protocol Operations for Version 2 of the Simple Network Management
Protocol (SNMPv2)
Transport Mappings for Version 2 of the Simple Network Management
Protocol (SNMPv2)
User-based Security Model for SNMPv2
RFC 2011(Proposed
Standard - Updates RFC
1213)
SNMPv2 Management Information Base for the Internet Protocol using
SMIv2
RFC 2012 (Proposed
Standard)
RFC 2013 (Proposed
Standard)
SNMPv2 Management Information Base for the Transmission Control
Protocol using SMIv2
SNMPv2 Management Information Base for the User Datagram
Protocol using SMIv2
IP Forwarding Table MIB RFC 2096 (Proposed
Standard)
RFC 2863 (Draft
Standard)
The Interfaces Group MIB
RFC 3410
(Informational)
Introduction and Applicability Statements for Internet-Standard
Management Framework
RFC 3411 (STD0062) An Architecture for Describing Simple Network Management Protocol
(SNMP) Management Frameworks
RFC 3412 (STD0062) Message Processing and Dispatching for the Simple Network
Management Protocol (SNMP)
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
C-5
RFC Compliance
Appendix C SNMP MIB and Trap Information
Table C-3 SNMP RFC Standards (continued)
RFC Standard Title
RFC 3413 (STD0062) Simple Network Management Protocol (SNMP) Applications
RFC 3414 (STD0062) User-based Security Model (USM) for version 3 of the Simple Network
Management Protocol (SNMPv3)
RFC 3415 (STD0062) View-based Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)
RFC 3416 (STD0062) Version 2 of the Protocol Operations for the Simple Network
Management Protocol (SNMP)
RFC 3417 (STD0062) Transport Mappings for the Simple Network Management Protocol
(SNMP)
RFC 3418 (STD0062) Management Information Base (MIB) for the Simple Network
Management Protocol (SNMP)
RFC 2570
(Informational)
Introduction to Version 3 of the Internet-standard Network Management
Framework
RFC 2571 (Draft
Standard)
RFC 2572 (Draft
Standard)
An Architecture for Describing SNMP Management Frameworks
Message Processing and Dispatching for the Simple Network
Management Protocol (SNMP)
SNMP Applications RFC 2573 (Draft
Standard)
RFC 2574 (Draft
Standard)
RFC 2575 (Draft
Standard)
RFC 2576 (Proposed
Standard)
User-based Security Model (USM) for Version 3 of the Simple Network
Management Protocol (SNMPv3)
View-based Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)
Coexistence between Version 1, Version 2, and Version 3 of the
Internet-standard Network Management Framework
RFC 2578 (STD0058) Structure of Management Information Version 2 (SMIv2)
RFC 2579 (STD0058) Textual Conventions for SMIv2
RFC 2580 (STD0058) Conformance Statements for SMIv2
C-6
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
OL-22792-01
A P P E N D I X
D
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 D-2
•
•
The Engineering access level is primarily used for initializing the CDS at the time of installation and for system diagnostics. After your system has been configured, you should not require an engineering access level user for day-to-day operations.
When you log in to the CDSM with a user account that has Engineering access level, the first page that is displayed is the CDSM Setup page. All the other CDSM pages that are available with the Master access level are still available with the Engineering access level.
In an RTSP environment, the Configure > Server Level > RTSP Setup page displays four additional fields:
•
Database Connect Size
•
•
UDP Packet Size
Threadpool Size
•
Max Sessions
These fields are only for diagnostic purposes, and their values should not be changed.
Note
When you configure the CDSM for Virtual Video Infrastructure (VVI), all references to CDSM are changed to Virtual Video Infrastructure Manager (VVIM) for the Vault and Caching Node manager. For example, the CDSM Audit Logs available through the Report > System Level left-panel menu is changed to the VVIM Audit Logs when VVI is configured on the CDSM Setup page, which changes to the VVIM Setup page.
Cisco TV CDS 2.3 RTSP Software Configuration Guide
D-1
Appendix D 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. The following remaining sections of the CDSM or VVIM Diagnostic page are:
•
CIDR Calculator
•
•
•
Stream Trickmode Debugger
Unix Timestamp Tool
Server Diagrams
CIDR Calculator
By entering an IP address and network mask, and clicking Submit, the Classless Inter-Domain Routing
(CIDR) Calculator provides the following TCP/IP network information:
•
•
•
•
Network address
Broadcast address
Number of hosts
Range of IP addresses for the hosts
Stream Trick-Mode Debugger
To view the trick-mode data for a Session ID enter the Session ID and click Submit. The CDSM or
VVIM Diagnostic page refreshes and a View Data button is displayed next to the Submit button. Click
View Data to see the raw trick-mode data. A new window displays the data. Right-click in that window and choose View Source in the pop-up menu. A formatted version of the raw data is displayed.
Unix Timestamp Tool
Clicking on a day in the calendar displays the Unix start time and end time. The time is represented in seconds since the start of Unix epoch time, which is 1970-01-01T00:00:00.
Server Diagrams
Choose a server from the Server Diagrams drop-down list and a graphic of the server is displayed.
D-2
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix D 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. If a Streamer fails, another
Streamer in the same Stream Group takes over any active stream sessions without loss of state and backoffice independence.
Stream Steering Mode
Stream steering determines which Streamers serve streams to a QAM device. There are two types of stream steering:
•
•
Single site (Silo site steering)
Multi-site
Single-site steering uses only one Stream Group to serve streams to all QAM devices. Multi-site steering can use more than one Stream Group to serve streams to the QAM devices. The QAM Gateway page reflects whether single-site or multi-site steering is enabled, by the number of preference levels available. Multi-site steering offers four preference levels (high, medium, low, and none). Single-site steering offers two preference levels (high and none).
Note
Multi-site steering is available only with ASI streaming in an ISA environment.
Deployment Network Config
Specify whether your CDS network topology is a Layer 2 or Layer 3 network.
Installation Type
The only options are ISA 2.X and RTSP 2.X.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
D-3
Appendix D Engineering Access Level Pages
CDSM or VVIM Setup
Stream Destination
The possible settings for Stream Destination are Cable and IPTV.
The cable setting is the existing configuration with the QAM Gateway page and Headend Setup page, which allows you to map Stream Groups to QAM devices and service groups if applicable.
The IPTV setting provides the Stream Destination page in place of the QAM Gateway page and Headend
Setup page. The Stream Destination page allows you to map the Stream Groups to specified subnets, which is useful in IPTV networks where each end-user has an IP address.
An option for ISA environments using the IPTV setting for the Stream Destination is the NAT option.
The NAT Traversal feature allows streaming to client devices that are behind a NAT device.
Note
The Stream Destination feature is available only for single-site steering.
Parent/Child Service Groups
Parent/Child Service Groups is an optional feature and is only for ISA environments that use ASI streaming. The Parent/Child Service Groups page allows finer granularity of the service groups.
Redirect Server
Redirect Server is an optional feature for RTSP environments. The RTSP server on the Streamer sends a redirect to the “best” Streamer to serve the content. When set to ON, the Redirect Server configuration page is displayed at the System Level, and you can specify the port number used to receive the redirect requests, as well as set the debug level.
Bulk Configuration
Bulk Configuration provides a method of configuring common configuration parameters for all the servers at one time by means of an XML file. Following are the CDSM GUI configuration pages that offer bulk configuration:
•
•
•
•
•
•
•
•
•
QAM Gateway
Headend Setup
Stream Destination
NTP Server
Server DNS
SNMP Agent
Route Tables
RTSP Setup
FSI Setup
D-4
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix D Engineering Access Level Pages
CDSM or VVIM Setup
SSV Groups
When SSV Groups is enabled, Stream Groups, Vault Groups, and Cache Groups are disabled.
Note
The SSV Group optional feature is only applicable to RTSP environments and for a CDS that uses only
ISVs.
The Thin Pipe Map page and Vault Redundancy Map page are also displayed when SSV Groups is enabled. The Vault Redundancy Map page allows mapping of ISVs for mirrored content, and the Thin
Pipe Map page allows creation of low-bandwidth connections between local and remote groups.
Note
The term SSV used in the CDSM GUI is the same as the ISV. The terms are interchangeable.
When SSV Groups is enabled, all pages referring to Vaults or Streamers display as SSV instead. These pages include the Stream Destination page, the QAM Gateway page, the Headend Setup page, the
Control/Setup IP page, and the Vault Redundancy Map page.
Trick Mode Capture
In Release 2.2 and later releases, Trick Mode Capture is an optional feature. When Trick Mode Capture is enabled, the applicable Stream Activity reports can drill down to the Stream Play History Drilldown, which displays the trick modes for a session ID. Additionally, the Graph Stream button is displayed on the Stream Monitor page. The Stream Activity reports that can drill down to the Stream Play History
Drilldown are the following:
•
Stream Play History
•
•
•
•
Streams by Array
Streams per STM-MAC
Bandwidth per Service Group
Stream Failures
When Trick Mode Capture is disabled, the session ID in the Stream Activity reports no longer links to the Stream Play History Drilldown and the Graph Stream button is removed from the Stream Monitor page.
Vault Redundancy
When Vault Redundancy is enabled and at least two Vault Groups are configured and mapped to each other, at least one copy of each content within a group is mirrored to the configured peer group. Content is mirrored among as many as four Vault Groups (one Vault Group ingests the content and up to three
Vault Groups mirror the content), which may be in different geographic regions. The Vault Redundancy adds the Vault Groups and Vault Redundancy Map configuration pages to the Array Level.
Note
In Release 2.3, the maximum number of Vault Groups is 20.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
D-5
Appendix D Engineering Access Level Pages
CDSM or VVIM Setup
RS DVR
This feature is not activated in this release.
Thin Pipe Management
Thin Pipe Management allows you to configure low-bandwidth connections between local and remote groups. A local group consists of servers in the same group (Stream Group, Cache Group, Vault Group).
A remote group consists of servers in other Stream Groups, Cache Groups, and Vault Groups. Use the
Thin Pipe Map page to configure this feature.
Shared Content Store
Shared Content Store is an optional feature for the ISA environment. The Shared Content Store allows one instance of a Content Store to be shared with many instances of Stream Services, each located in its own video hub office (VHO) with its own video backoffice (VBO).
Virtual Video Infrastructure
The Virtual Video Infrastructure (VVI) provides management of the Caching Nodes in a central management configuration or a split-domain management configuration.
When you enable VVI, you need to choose the Management System Role of the CDSM. The
Management System Role has the following options:
•
VVI and Stream Manager—Central management of all Vaults, Caching Nodes, and Streamers
•
•
VVI (Vault/Cache) Manager—Management of only the Vaults and Caching Nodes
Stream Manager—Management of only the Streamers
The Cache Fill Protocol options are for selecting the type of data communication that is used between
Caching Nodes and Streamers. Cache Control Protocol (CCP) is used for communication among the
Vaults, Caching Nodes, and Streamers. For more information about CCP Streamers and HTTP
Streamers, see the “Caching Node Workflow” section on page 2-9
.
Note
ISA environments only support CCP, while RTSP environments only support HTTP for VVI.
The split-domain management is made up of the VVI (Vault/Cache) Manager and the Stream Manager.
For the Stream Manager to be able to communicate with the VVI Manager, you need to enter the IP address of the VVI Manager in the VVI (Vault/Cache) Manager VVIM IP field.
If CCP is used as the cache-fill protocol, you must provide a name for the Stream Manager in the Stream
Domain Name field so that the VVIM can identify it from other Stream Managers. Communication between the VVI Manager and the Stream Manager is accomplished through database replication when using CCP.
If you choose HTTP, communication between the VVI Manager and the Stream Manager uses port 80.
If port 80 is not open for communication, you can enter the data manually (used for Stream Group IDs), or upload an XML file (used for Cache Group Locator information), depending on the information required.
D-6
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix D Engineering Access Level Pages
CDSM or VVIM Setup
Note
When you configure the CDSM for Virtual Video Infrastructure (VVI), all references to CDSM are changed to Virtual Video Infrastructure Manager (VVIM) for the Vault and Caching Node manager.
The VVIM and Stream Managers display different configuration, monitoring, reports, and maintenance pages based on the servers they manage. For example, when CCP is the cache-fill protocol, the VVIM displays the Configuration Generator page in the Maintenance > Software left-panel menu. The
Configuration Generator page is used to generate the group IDs and server IDs for the Stream Managers to use in their domains.
Configuring Split-Domain Management
To configure a VVIM that uses split-domain management, set the VVI fields as follows:
•
•
VVI Options—Enabled
Management System Role—VVI (Vault/Cache) Manager
•
Cache Fill Protocol—HTTP or CCP (Must be configured the same as the Stream Manager.)
To configure a Stream Manager that uses split-domain management, set the VVI fields as follows:
•
•
•
•
•
VVI Options—Enabled
Management System Role—Stream Manager
Cache Fill Protocol—HTTP
VVI (Vault/Cache) Manager VVIM IP—IP address of the VVIM
Stream Domain Name—Domain name for the Stream Domain (If CCP is the Cache Fill Protocol)
Media Scheduler
The Media Scheduler is an optional feature and requires a software activation key to enable it. For more information about activating the Media Scheduler, see the
“Initializing the CDS and Activating the
Optional Features” section on page 3-3 . The Media Scheduler allows live ingests from multicast IP
addresses and uses the Input Channels page to map multicast IP addresses to channels. You can enable either Media Scheduler or Real-Time Capture Type, but not both.
Real-Time Capture Type
Real-Time Capture allows live ingests from multicast IP addresses and uses the CallSign Setup page to map the multicast IP addresses to call signs. You can enable either Media Scheduler or Real-Time
Capture Type, but not both.
Bandwidth Manager
The Bandwidth Manager is an optional feature and is only for RTSP environments. The Bandwidth
Manager keeps track of allocated streams and VOD network resources.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
D-7
Appendix D Engineering Access Level Pages
CDSM or VVIM Setup
Ingest Manager
The Ingest Manager is an optional feature and requires a software activation key to enable it. For more information about activating the Ingest Manager, see
“Initializing the CDS and Activating the Optional
. The Ingest Manager takes care of provisioned content objects by collecting the metadata, sending messages to the appropriate subsystem to ingest the content, and sending messages to expire the content when the expiration period has passed.
RTSP Deployment Type
The RTSP Deployment type is applicable only to RTSP environments. The options are the following:
•
•
•
•
•
•
DSM-CC
RTSP
NGOD
IPTV
Quative
EventIS (on vpath and off vpath)
•
Cisco
The deployment configuration differs depending on the type of headend.
Content Propagation
The Content Propagation setting determines whether content information is propagated to the Streamers or not. This setting is applicable only to RTSP environments.
When the RTSP Deployment Type is set to NGOD, set the Content Propagation to Not Propagated. This setting allows content information to be stored on the Caching Nodes in VVI RTSP NGOD deployments.
The Streamers check their local database for a record of the content. If the content is not found, the
Caching Nodes are queried for the content record.
For all other RTSP Deployment Types, set the Content Propagation to Propagated. This allows content information to be stored on the Streamers.
Authentication Manager
The Authentication Manager is an optional feature and is only for specific RTSP environments
(EventIS). The Authentication Manager communicates with the backoffice to validate a request received from a set-top box before setting up a session.
The Protocol options are for selecting the RTSP deployment type for the Authentication Manager. Cisco is used for the Cisco RTSP deployment and EventIS is used for the EventIS RTSP deployment.
D-8
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Appendix D Engineering Access Level Pages
System Configs
Service Group Steering
Service Group Steering is an optional feature and is only for RTSP environments. When the Service
Group Steering option is turned on, the Configure > System Level > Headend Setup page is available to steer Stream Groups to specific service groups.
CDSM or VVIM NAV Setup
The CDSM NAV Setup changes what displays in the CDSM GUI.
CDSM or VVIM Health Monitoring
The CDSM Health Monitoring optional feature displays the Server Level monitor page, Server Vitals page and a Vitals column in the System Health Monitor page. The Server Vitals page displays the current values, as well as thresholds, for monitored system components on the server. Server components are monitored and when a threshold is exceeded, the System Health Monitor page and Server Vitals page report the event and an SNMP trap is sent.
System Configs
The System Configs page contains critical CDS parameters that are set at the time of the initial installation of the CDS. Generally, the default settings are appropriate for all environments.
Caution
If these parameters are changed after the CDS is in service, your CDS may not function properly.
Group Map 0
Specifies whether the Group Map 0 parameter is for an ISA or RTSP environment.
Servers Group Map
Specifies whether the Servers Map 0 parameter is for an ISA or RTSP environment.
License Map
This is the CDS license, and is set at the time of installation.
Control IP Map
The Control IP Map is always set to one.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
D-9
Appendix D 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-23
, you can use the Add New Server section.
D-10
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
A P P E N D I X
E
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.3 contains licenses and related license information for open-source software included in Cisco TV CDS, Release 2.3. The document is located at the following url: http://www.cisco.com/en/US/products/ps7127/products_licensing_information_listing.html
If you have any questions or problems accessing the link, please contact: [email protected]
Product Warranties
For product warranty information, refer to the warranty information in the Accessory Kit accompanying the product.
OL-22792-01
Cisco TV CDS 2.3 RTSP Software Configuration Guide
E-1
Product Warranties
Appendix E Software Licensing Information
E-2
Cisco TV CDS 2.3 RTSP Software Configuration Guide
OL-22792-01
Pakua
Kiungo cha umma kime sasishwa
Kiungo cha umma kwa mazungumzo yako kimesasishwa. You may view and manage your chat links after registration here.
Kiungo cha umma cha hati
Tangazo