Imagine CloudXtream User Manual

Download

User Guide

CloudXtream

Release2.0

07‐Dec‐2016

DVR(cDVR)

CloudXtreamTM DVR (cDVR) User Guide, Release 2.0

Printed 12/7/2016

PublicationInformation

This material is protected by the copyright laws of the United States and other countries. No part of this document may be reproduced, distributed, or altered in any form, by any means, by any entity nor may it be used to make any derivative work (such as translation, transformation, or adaptation) except in accordance with applicable agreements, contracts, or licensing, without the express written consent of Imagine Communications. All other uses are illegal.

Notice

This publication is designed to assist in the use of the product as it exists on the date of publication of this manual, and may not reflect the product at the current time or an unknown time in the future. This publication does not in any way warrant description accuracy or guarantee the use for the product to which it refers. Imagine Communications reserves the right, without notice to make such changes in equipment, design, specifications, components, or documentation as progress may warrant to improve the performance of the product.

Trademarks

SelenioTM and TelurioTM are trademarks of Imagine Communications. Microsoft® and Windows® are registered trademarks of Microsoft Corporation. All other trademarks and trade names are the property of their respective companies.

Patents

The products described herein are covered by one or more U.S. and foreign patents pending. U.S. Patents: 6,996,129; 7,046,677; 7,818,355; 8,180,920. Other US and foreign patents pending.

ContactInformation

Imagine Communications has office locations around the world. For domestic and international location and contact information see: http://www.imaginecommunications.com/contact-us/

SupportContactInformation

For domestic and international support of Selenio VMG, Selenio BNP, Selenio SEP, Selenio MMC, Selenio TAT, Telurio Packager, Telurio Recording Manager, and Telurio AIM products, contact:

Support Contacts: support@imageinecommunications.com

For domestic and international support of all other Imagine Communications' products not mentioned above, contact:

Support Contacts: http://www.imaginecommunications.com/services/technical-support/

http://app.imaginecommunications.com/customerCommunityLogin

1.866.4.Imagine // (1.866.446.2446) - Inside North America +1.44.208.339.1900 - Europe & Africa +971.4.433.8260 - Middle East

cDVR User Guide, Release 2.0 2

DocumentChangeHistory

CloudXtreamTM DVR (cDVR) User Guide document history

Part Number

n/a 2.0 12/07/2016 • Updated doc for 2.0 references

n/a 1.7 07/12/2016 • Updated doc for 1.7 references

250-0359-01 Rev A 1.5 10/02/2015 • Updated doc for 1.5 references

250-0339-01 Rev A 1.4 05/18/2015 • Updated user guide with new Imagine Communications

250-0325-01 Rev A 1.3 01/26/2015 • Updated all screenshots and instructions for new API

250-0310-01 Rev A 1.2 11/14/2014 • Minor GUI Changes

250-0293-01 Rev A 1.1 9/19/2014 • Added GPFS storage mount

DRAFT, Rev A 1.0.1 n/a Production Release on 7/20/2014 (No UG)

Software Release

Release Date Changes

• Additional key servers added

• Private copy optimization functionality changes

• Video bitrate low and high thresholds to audiomap and JITP profile added

• Restart and CatchTV playback from URL using HLS or DASHISO

• Private Copy De-duplication

• Updates for CentOS 7.2 requirements

• Additional key servers added

• Private Copy feature added (major)

• Removed ASSETS tab

• Added SHARED ASSETS and UNIQUE ASSETS tabs

• Added publishing type to audio map

branding

• New keyserver: Playready Leaf

• Minor changes to JITP/RECORDER container fields

• Minor changes to CHANNELS, SCHEDULES, EBR, and ASSETS status menus

• Added private copy description & instructions

• Added Appendix A: RESTful API

• Added storage content management functionality description

• Minor GUI changes

cDVR User Guide, Release 2.0 3

TableofContents

Publication Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Patents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Support Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Table of Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Document Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Document Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Graphics Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Acronyms Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 2: Solution Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

In This Chapter: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Adaptive Bitrate (ABR) Primer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

ABR Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Video Asset Delivery Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

cDVR Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Solution Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Imagine Communications’ cDVR Solution Components . . . . . . . . . . . . . . . . . . . . . . . . . 20

Additional cDVR Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

cDVR Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Recorder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Recording Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Recording Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Te lu r io

Content Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Just In Time Packaging (JITP) Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Catch Up and Restart TV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Functionality Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Record-level Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Recording Manager Node-level Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Recording Manager Storage Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

RM WebGUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Private and Shared Copy for Continuous Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Recording Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Storage Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Private Copy Content Storage Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

DRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

cDVR User Guide, Release 2.0 4

Table of Contents

Eventual Private Copy Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Progressive Private Copy Mode (hot record and Playback) . . . . . . . . . . . . . . . . . . . 24

Private Copy Optimization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 3: cDVR Initial Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

In This Chapter: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Storage Node Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Storage System Type Configuration (Shared Copy) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

NFS Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Storage System Type Configuration (Private Copy) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Packager Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Packager System Configuration — Required Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Packager Menus Configured by RM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Installing the Packager License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Viewing Packager Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Additional Packager Licensing Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Using Recorder for EBR vs. CR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

RM Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Installing the RM License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Viewing RM Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

What Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 4: RM Redundancy Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

In This Chapter: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Networking Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Gateway Route Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Option 1: Set Default Routes on both RMs (Recommended): . . . . . . . . . . . . . . . . . 35

Option 2: Configure a Static Route on both RMs: . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Special Notes on Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Redundancy Configuration Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Log In to Primary RM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Configure Redundancy Group Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Add Standby Host from Primary RM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Verify Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Redundancy States (More Information). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Removing RM Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Remove Standby Host from Redundant Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Remove Redundancy Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

What Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Chapter 5: Recording Manager GUI Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

In This Chapter: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Launching RM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Logging In to the RM GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Understanding RM Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

RM GUI Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

cDVR User Guide, Release 2.0 5

Table of Contents

Navigating the RM GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Icons and Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Tab Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Dashboard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

What Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Chapter 6: Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

In This Chapter: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Dashboard Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Menu Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Viewing Detailed Information for an Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Acknowledging and Unacknowledging Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Chapter 7: Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

In This Chapter: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Sub-tab Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Global Config Sub-tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Segments Container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Assets Container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Nodes Sub-tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Transcoders Container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Configuring a Transcoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

JIT Packagers Container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Configuring a JIT Packager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Playlist Load Balancer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Configuring a PLLB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Storage Mounts Container. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Configuring a Storage Mount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Recorders Container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Configuring a Recorder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Record-level Redundancy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Master/Slave Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Hardware and Networking Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

BJM Hosts Container. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Configuring a BJM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

JITP/Recorder Sub-tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Key Server Container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Configuring a Key Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Audio Map Container. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Audio Map Template Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Configuring an Audio Map Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Audio Map Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Configuring an Audio Map Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Audio Output Publishing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

cDVR User Guide, Release 2.0 6

Table of Contents

Profile Container — JITP Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Configuring a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Source Server Container — JITP Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Configuring a Source Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Channels Sub-tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Channels Sub-tab Tour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Default View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Configured View - Collapsed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Configured View - With Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Configuring Channels and Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Creating Channels and Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Schedules Sub-tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Schedules Sub-tab Tour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Default View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Configured View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Configuring Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Creating a Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Scheduling Calendar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Modifying a Recording Schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Deleting a Recording Schedule(s). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Event Based Recordings Sub-tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Event Based Recordings Sub-tab Tour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Using the EBR URL to View a Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Deleting a Recording(s) from RM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Shared Assets Sub-tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Shared Assets Sub-tab Tour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Default View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Configured View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Configuring Shared Assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Creating a Shared Asset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Scheduling Calendar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Modifying a Shared Asset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Deleting a Shared Asset(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Using the Shared Assets URL to View a Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Unique Assets Sub-tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Unique Assets Sub-tab Tour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Default View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Configured View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Configuring Unique Assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Creating a Unique Asset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Scheduling Calendar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Modifying a Unique Asset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Deleting a Unique Asset(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Using the Unique Assets URL to View a Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Content Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

How EBR Content is Stored . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

EBR Storage Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

How CR Content is Deleted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

CR Storage Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Deletion Mechanism Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

What is Deleted. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

cDVR User Guide, Release 2.0 7

Table of Contents

Chapter 8: System Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

In This Chapter: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Prerequisite System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

System Tab Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Menu Tree Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

System Tab Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Contextual Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

App Config (Reset/Backup/Restore) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Menu Access and Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

View HTTP Backup File Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Restoring a Database for Redundant RMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

App State (Restart) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Menu Access and Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

System State (Reboot/Shutdown) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Menu Access and Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Network Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

IP Branch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

IP Address Configuration — Menu Access and Usage. . . . . . . . . . . . . . . . . . . . . . 121

Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

IP Restart — Menu Access and Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Ethernet Ports Branch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Network Interfaces Branch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Menu Access and Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Routes Branch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Menu Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Menu Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

DNS Branch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Menu Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Menu Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

NTP Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Server Config Branch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Menu Access and Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Server State Branch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Server Restart Branch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

SNMP Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Settings Branch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Trap Sink Branch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Add a Trap Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Delete a Trap Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Modify a Trap Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Syslog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Menu Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Add a Syslog Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Delete a Syslog Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

cDVR User Guide, Release 2.0 8

Table of Contents

Modify a Syslog Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Hostname. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Menu Access and Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Timezone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Menu Access and Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

License Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Details Branch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Menu Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Server Branch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Lockcode Branch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Menu Access and Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Refresh Branch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Redundancy Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Group Branch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Hosts Branch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Add a Redundancy Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Delete a Redundancy Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Failover Branch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Recover Branch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Redundancy Switchover and Recovery Behavior. . . . . . . . . . . . . . . . . . . . . . . . . . 155

Registered Apps Branch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Debug Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Menu Access and Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Software Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Menu Access and Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Chapter 9: Reports & Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

In This Chapter: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

CPU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

DMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

IPMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Graphs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Information Required for Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

In This Appendix: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

cDVR User Guide, Release 2.0 9

Table of Contents

Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Access and Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

cDVR User Guide, Release 2.0 10

CHAPTER 1

Imagine Communications’ CloudXtream™ Digital Video Recorder (cDVR) solution is a multicomponent, cloud enabled system that provides end-to-end video recording and delivery using the service provider’s own data center or a hosted private cloud. Imagine Communications supports both shared and strict private copy configurations in order to enable users to comply with the

“Cablevision” scheduled recording—Event-based and Continuous Record—and seamlessly supports fast-forward, resume, and sliding window playback in both shared and private copy modes.

This release of cDVR is offered as a multi-component, software-only solution, each of which runs on a Linux-based

environment (refer to the subsequent sections on Storage and Capacity for details).

This user guide describes functionality, configuration and usage of the Recording Manager (RM), the cDVR management component. Refer to the CloudXtream

Upgrade Guide for instructions on software installation.

Introduction

ruling. Additionally, cDVR provides two different methods of operator or user-based

operating system. cDVR can be deployed on server-based hardware or in a virtualized

DVR Software Installation, Setup, and

InThisChapter

This chapter contains the following sections:

• “Document Organization,” next.

• “Document Audience” on page 12.

• “Related Documentation” on page 12.

• “Document Conventions” on page 13.

• “Graphics Used” on page 13.

• “Acronyms Used” on page 13.

1. The Cablevision ruling provides standards for ensuring content programming remains unique to the viewer so as to comply with U.S. copyright law.

2. Refer to the Release Notes or the CloudXtream of CentOS.

cDVR User Guide, Release 2.0 11

DVR Software Setup & Upgrade Guide for compatible versions

Introduction - Document Organization

DocumentOrganization

This guide is organized as follows:

• Chapter 1, “Introduction,” (this chapter) describes the contents and conventions used in the

CloudXtream

• Chapter 2, “Solution Overview,” provides a detailed description of cDVR and its features.

• Chapter 3, “cDVR Initial Setup,” lists the procedure for initial configuration of the cDVR

components.

• Chapter 4, “RM Redundancy Setup,” provides instructions for setting up redundant Recording

Managers.

• Chapter 5, “Recording Manager GUI Overview,” provides an introduction and overview to the RM

graphical user interface (GUI)

• Chapter 6, “Dashboard,” describes the RM Dashboard view.

• Chapter 7, “Configuration,” describes how to use the Configuration tab to set up recording

parameters.

• Chapter 8, “System Configuration,” covers all maintenance and system-related tasks such as

software upgrades, database backups, diagnostics, and configuring SNMP and syslog servers.

• Chapter 9, “Reports & Troubleshooting,” describes alarms and events related to cDVR in addition to

general troubleshooting tips.

• Appendix A, “RESTful API,” provides information on how to access the Telurio Recording Manager’s

online API help pages.

DVR (cDVR) User Guide.

DocumentAudience

This guide is for system administrators and operators who are responsible for installation and maintenance of the Imagine Communications cDVR solution. You should be familiar with general video and networking practices and terminology, and should be familiar with basic installation of hardware.

RelatedDocumentation

• CloudXtream

• Te lu ri o

DVR Software Setup & Upgrade Guide, Release 2.0

DVR Release Notes, Release 2.0

Recording Manager: List of Events, Release 2.0

cDVR User Guide, Release 2.0 12

Introduction - Document Conventions

DocumentConventions

Table 1 provides an easy way to recognize important information in this user guide.

Table 1. Document Conventions

When you see: It means:

Notes are indicated by the icon shown on the left, and point out information that may not be part

of the text but provide tips and other helpful advice.

Cautions are indicated by the icon on the left, and let you know that an action may have

undesirable consequences if the instructions are not followed correctly. Cautions also indicate that failure to follow guidelines could cause damage to equipment or loss of data.

Warnings are indicated by the icon on the left, and indicate that failure to take the necessary

precautions or to follow guidelines could cause harm to equipment and personnel.

Navigation tip: follow the path next to the pointer to navigate a specific GUI menu.

Clicking any

blue link takes you to the referenced item.

GraphicsUsed

In some cases, the screens shown in this manual may have been slightly modified after the manual was released, or may appear slightly different on different browsers.

All efforts have been made to ensure that the latest images are used. In all cases, the functionality described is current at the time of writing.

AcronymsUsed

Table 2 provides is a list of acronyms commonly used in video processing and cDVR. Note that some of

these acronyms may not be used in this user guide.

Table 2. Video Processing and Adaptive Bitrate Streaming Acronyms

Acronym Meaning

AAC Advanced Audio Coding

ABR Adaptive Bitrate

AC3 Audio Coding Version 3 (Dolby Digital 5.1, or DD)

ADM Ad Management Service (function of AWE)

ADS Ad Decision Service

AIM Ad Insertion in Multi Screen (Imagine Communications term)

API Application Programming Interface

AU Access Unit

cDVR User Guide, Release 2.0 13

Introduction - Acronyms Used

Table 2. Video Processing and Adaptive Bitrate Streaming Acronyms

Acronym Meaning

Avail Available opportunity for ad placement

AWE Ad Workflow Engine (Imagine Communications term)

B-Frame Bidirectional compression picture frame

BJM Background Job Manager

CDN Content Delivery Network

cDVR CloudXtream digital video recorder

CIFS Common Internet Files System (Microsoft based)

CNS Content Name Server

CR Continuous Recording

DAI Digital Ad Insertion

DD Dolby Digital (same as AC3)

DD+ Dolby Digital Plus (same as E-AC-3)

DASH Dynamic Adaptive Streaming over HTTP

DMA Designated Market Area

DMM Dynamic Manifest Manipulation

DRM Digital Rights Management

DTS Decoding Time Stamp

DTS Digital Theater Systems

DVR Digital Video Recorder

E-AC-3 Enhanced Audio Coding 3 (Dolby Digital Plus 7.1, or DD+)

EBP Encoder Boundary Point

EIDR Entertainment Identifier Registry (CableLabs sponsored registry for TV & movie programming)

ENC Encoder

ES Elementary Stream

ESAM Event Signaling and Messaging

GOP Group of Pictures

GPFS General Parallel File System

GUI Graphical User Interface

HDS HTTP Dynamic Streaming (Adobe)

HD High Definition

HLS HTTP Live Streaming (Apple)

HRD Hypothetical Reference Decoder

HTTP Hypertext Transfer Protocol

IAB Interactive Advertising Bureau

IDR Instantaneous Decoder Refresh

I-Frame Intracoded compression picture frame

IIS Internet Information Services (Microsoft based)

JIT Just-in-time (Imagine Communications term)

cDVR User Guide, Release 2.0 14

Introduction - Acronyms Used

Table 2. Video Processing and Adaptive Bitrate Streaming Acronyms

Acronym Meaning

JITP Just-in-time Packaging (Imagine Communications term)

JITT Just-in-time Transcoding

KMS Key Management Server

MBR Multi-Bit Rate

MP4 MPEG-4 Part 14 format

MSS Microsoft Smooth Streaming (HTTP based)

NAS Network Attached Storage

NFS Network File System (Linux based)

NTP Network Time Protocol

PAT Program Association Table

PCE Private Copy Engine

PCM Pulse Code Modulation

PCR Program Clock Reference

PES Packetized Elementary Stream

P-Frame Predicted compression picture frame

PID Packet ID

PLLB Playlist Load Balancer (now Telurio Load Balancer)

PMT Program Map Table

PO Placement Opportunity (aka. ad-break, avail)

POIS Placement Opportunity Information Service

PRRS Playlist Rebuilder, Redirection Server (Now referred to as PS)

PS Playlist Server (formerly referred to as PRRS)

PTS Presentation Time Stamp

RTMP Real Time Messaging Protocol

SAP Stream Access Point

SD Standard Definition

SIS Subscriber Information Service

SSM Source Specific Multicast

TAP

TelurioTM Packager (Imagine Communications)

TLB Telurio Load Balancer (formerly PLLB)

TS Transport Stream

UDP User Datagram Protocol

URI Universal Resource Identifier (contains URL & URN)

URL Universal Resource Locator (always a URI)

URN Universal Resource Name (not necessarily a URI)

UPID Unique Program ID

UUID Universally Unique Identifier (See RFC 4122)

VAST Video Ad Serving Template

cDVR User Guide, Release 2.0 15

Introduction - Acronyms Used

Table 2. Video Processing and Adaptive Bitrate Streaming Acronyms

Acronym Meaning

VES Video Elementary Stream

VMG Video Multiprocessing Gateway (Imagine Communications)

VOD Video on Demand

XML Extensible Markup Language

XML-RPC Extensible Markup Language - Remote Procedure Call

cDVR User Guide, Release 2.0 16

CHAPTER 2

A Cloud Digital Video Recording (cDVR) solution provides the ability for a subscriber to make recordings of many linear multiscreen channels and programs. Recordings can be initiated by an operator for Catch-up/Time-shift TV or initiated by a subscriber, where the end user selects when and what to record.

Imagine Communications’ cDVR solution is a network based DVR solution that continuously records channels. Recorded content is managed in the service provider’s network, thus helping operators optimize storage and CDN costs. Subscribers can then create recording assets by abstracting the continuously recorded content for delivery to their multi-screen devices.

This chapter provides an overview of Imagine Communications’ cDVR features and functionality, as well as a brief description of other non-Imagine Communications components in an cDVR environment.

Note: Several acronyms are used throughout this chapter. You may wish to refer to Table 2, “Video

SolutionOverview

Processing and Adaptive Bitrate Streaming Acronyms,” on page 13

for their meanings.

InThisChapter:

• “Adaptive Bitrate (ABR) Primer,” next;

• “cDVR Terminology” on page 18;

• “Solution Overview” on page 19;

• “cDVR Features” o n page 20.

AdaptiveBitrate(ABR)Primer

To understand how cDVR works in a multi bit rate environment, a general description of ABR streaming is provided here.

ABRTechnology

Adaptive streaming works via a video client’s playback of a sequence of HTTP-requested short video file fragments, or “chunks.” Adaptive HTTP streaming allows the client to request fragments of the same content—a video asset—encoded at different bit rates and resolutions (referred to as “profiles”). In this manner, as network bandwidth changes, the client can download the best possible quality fragment at any point in time.

Several player protocols have been developed for delivering and viewing adaptive streaming including: Apple HTTP Live Streaming (HLS), Microsoft Smooth Streaming (MSS), Adobe HTTP Dynamic Streaming (HDS), and MPEG’s Dynamic Adaptive Streaming over HTTP (DASH).

cDVR User Guide, Release 2.0 17

Solution Overview - cDVR Terminology

HTTP-based streaming utilizes two types of files in order to accomplish dynamic streaming:

• Manifest files—contain metadata that describes the identity and location of all alternate multi-

bitrate streams. Client players use manifest files (also referred to as “playlists”) to determine information about the content including (but not limited to) available bitrates, codecs, video resolutions, markers, captions, and the location of segments. See manifest formats.

• Content files—contain the actual video and audio that has been specially encoded in order for the

client player to retrieve discrete file segments during playback. See content formats.

Table 3. HTTP-based supported manifest & content

Player Manifest Format Content Format

HDS F4M FMP4

HLS M3U8 TS

MSS ISM ISMC / ISMV

DASH-TS MPD TS

DASH-ISO MPD FMP4

Table 3 for a list of supported

VideoAssetDeliveryMethods

Media content can be delivered to customers in two ways: Live or On-demand.

• Live Delivery — This method ingests content in either a (stored) file or (live) stream format and

delivers that content in real-time to the consumer. An example of live delivery could be either a sporting event (stream) or a network prime time TV show (file). In both cases, the ingest manner is different, but the client has no control of the program; it cannot be paused, stopped, or restarted at will (unless a digital recorder is used).

• On Demand Delivery — This method also ingests content in either a file or stream format,

however, rather than delivering the content immediately in real-time, it is stored on a server (in file format) and made available for the consumer to watch at some point in the future (otherwise known as Video On Demand, or VOD). The client can start the program playback from the beginning at will, as well as stopping, pausing, or randomly seeking inside the program. An example of VOD content would be services like Netflix or Hulu.

cDVRTerminology

Below are some of the most commonly used cDVR-related expressions that industry professionals use.

• Cloud DVR—the ability for a subscriber to create personal recordings that are saved in the

network cloud rather than on the equipment at the subscriber’s premises.

• StartOver—a subscriber can view a current program from the beginning that has already begun

broadcasting, normally initiated from the Electronic Programming Guide (EPG).

• TimeShift—a subscriber can scroll back in time within the EPG to view a program that occurred

some hours previous (usually limited to 6-8 hours back from the current time).

• CatchUp—a subscriber can watch content that has already aired, marked by the operator as “hot”

content (usually limited to several programs per day, allowing the user to go back several weeks).

• Hot Record Playback—a subscriber can view content as it’s being recorded

cDVR User Guide, Release 2.0 18

Solution Overview - Solution Overview

• Event Based Recording—start and end times are fixed; a single file asset is stored per event,

which cannot be changed following the end of the recording.

• Continuous Recording (CR)—recording is abstracted (extracted from the original), which allows

start and end times to be edited before, during, and after the recording. Abstracted recording allows for granularity, post-capture modification, and efficient use of storage.

• Stitching—when recording programs in CR mode, recordings are abstracted as a collection of

video fragments and grouped together (“stitched”) to create a single manifest file for requested content.

• Private Copy—multiple recordings are stored and managed on a per subscriber basis, thus

allowing each subscriber a private copy of a program.

• Shared Copy—a recording is stored and managed one time in order for the same copy to be

available for any subscriber requesting it.

SolutionOverview

This section provides an overview of all components that are used in a service provider’s network when implementing cDVR functionality. The first part of this section describes Imagine Communications’ cDVR components; the second part of this section describes additional components required for an end-to-end cDVR network.

Figure 1. cDVR network architecture

cDVR User Guide, Release 2.0 19

Solution Overview - cDVR Features

ImagineCommunications’cDVRSolutionComponents

The Imagine Communications cDVR solution consists of several components:

• Telurio

order for middleware to schedule and playback recordings.

• Telurio

HLSv4 mezzanine format for delivery to a JITP-ready Packager.

• Telurio

manifest stitching. The JITP server creates ABR-ready chunks for either event-based or continuous recording. For CR, the Stitcher function then creates virtual assets by producing a variant manifest from the correct set of fragmented CR files.

• Private Copy Engine (PCE) — Manages replication and delete processes. Uses the Background

Job Manager (BJM) process to manage bulk copy requests.

• Telurio Load Balancer (TLB) — (Formerly known as PLLB)

instances, modifying playlists so that the URLs point to the JITP from which the content will be played back. This function guarantees high availability if a server running JITP goes down.

• Storage Node Support — Currently, the Hewlett Packard Enterprise (HPE) 4520

has been tested and is supported for this release of cDVR.

Recording Manager — a GUI-based application that provides a RESTful set of APIs in

Recorder — a Packager licensed for recording MBR IDR aligned streams, which creates

Packager JITP — a Packager licensed for JITP and, in the case of continuous recording,

Load balance requests across JITP

storage server

AdditionalcDVRComponents

The components in this section are not part of Imagine Communications’ cDVR solution package, but are nonetheless recommended and/or required for an end-to-end cDVR system to function.

• Middleware Scheduler—third party application that sits between the EPG and RM. Uses RM API to

manage user initiated schedules.

• Digital Rights Management (DRM) server—encrypts streams for secure delivery (not required for

cDVR, but still recommended).

• Video Transcoder—ingests content, prepares audio and video assets for segmentation; this can be

Imagine Communications’ Selenio NEXT or Selenio FLEX, or a third party transcoder.

• Mezzanine Storage—Storage server for the HLS v4 mezzanine files generated by Recorder ; this can

be either NFS or GPFS format.

• Content Delivery Network (CDN)—an aggregation of storage and cache servers that contains

content for video providers.

• Clients—end user devices that subscribe to and receive video content via set-top box, computer, or

mobile devices.

cDVRFeatures

The following key component features are included as part of this solution:

1. In the 1.7 release, the load balancing component was referred to as the Playlist Load Balancer (PLLB); as of release 2.0, the load balancer has been renamed to Telurio Load Balancer (TLB).

2. The HP 4520 storage server is currently required for Private Copy.

cDVR User Guide, Release 2.0 20

Solution Overview - cDVR Features

Recorder

The Recorder provides live-to-file video capture of multi-bit rate (MBR) video. By recording the MBR video and audio of every channel to a mezzanine storage, subscribers have the ability to create personal recording of events in the future or even events that have already occurred in the past.

Since this content is saved as ABR in the network, the play out is available for any multi-screen device.

RecordingModes

Two recording modes are offered:

• Continuous Recording (CR) — any or all channels are recorded to mezzanine format. Subscribers’

events can be abstracted from these recordings and stitched together based on the subscriber start and end times.

• Event Based Recording (EBR) — designed for systems in which storage space is constrained, EBR

allows subscribers to define what is recorded based on subscriber start and end time.

RecordingFunction

The Recorder operates as an independent component, which provides the following benefits:

• The JITP output component can scale in a more practical manner;

• End client packaging can utilize more diverse use cases.

Telu rioTMRecordingManager

The Telurio Recording Manager (RM) acts as the central management point for the cDVR solution; managing assets, storage, recordings and events.

As users select events to record from their EPG, these selections are routed through the operator’s middleware device to the RM. With the RM’s easy-to-integrate RESTful APIs, operators are not locked into a single middleware vendor.

ContentStorage

By storing the recorded content once in a common format, an overall smaller footprint of storage space is realized. All video, audio and data are captured to ensure the richness of the entire stream is available for packaging to the end client. This single stored format is then packaged on-the-fly based on the client’s device as requested.

Since the recorded content is in a common, non-proprietary format (HLSv4), use of the recorded content is not restricted. For those operators concerned with security of the recorded content, the mezzanine content can be encrypted.

StorageTypes

Imagine Communications’ cDVR solution offers several storage options to meet the various operator preferences:

• GPFS — General Parallel File System

cDVR User Guide, Release 2.0 21

Solution Overview - Functionality Description

• NFS — Network File System

• NFS4 — Network File System, version 4

• Webdav Light — HTTP-based storage for Private Copy

PrivateCopyContentStorageGuidelines

The guidelines below are recommended for storage when making use of the cDVR Private Copy feature.

• HP Storage using Apollo 45xx servers is required;

• Imagine Communications provides a customized ISO of applicable versions of CentOS;

• Minimum of 10Gbps interfaces for storage nodes.

JustInTimePackaging(JITP)Server

By converting recorded content on-the-fly, the JITP server provides multi-screen playback of the recorded content to whatever client format requested, including: HLS, MSS, HDS and DASH. This playback can be from assets recorded in the past or from live content that has been time-shifted (with an end in the future). Clients can invoke playback modes including pause, fast-forward, and rewind.

Scaling

The architecture of JITP allows the operator to scale to many thousands of simultaneous client requests.

DRM

The JITP server has been integrated with many types of DRM and can extend to other DRM vendors as needed. This capability allows operators to utilize their choice of encryption vendors and technologies.

CatchUpandRestartTV

Catch-up and Restart playback allows for non-linear Restart and Catch-Up TV by using a URL with an appended start and stop time. Rather than using asset-based segments from the linear side, updates or additions to packaging formats and DRMs are done on the JITP side. Thus, playback is done from the continuous record buffer via the JITP.

FunctionalityDescription

This section provides a functionality description of the key cDVR solution features; it is not an allinclusive list.

Record‐levelRedundancy

cDVR User Guide, Release 2.0 22

Solution Overview - Functionality Description

Recorder fails to write content to the storage server, then the redundant Recorder will pick up in its place and continue to write the content to the storage server.

Note: A Recorder is a Packager that is licensed for recording. When you configure the Recorders tab in

the RM, you are in effect configuring a specific type of package on a Packager.

RecordingManagerNode‐levelRedundancy

To allow for the highest level of redundancy which minimizes downtime, Imagine Communications’ cDVR solution provides node-level, 1+1 active/standby redundancy for the RM in which an RM redundancy group contains a Primary (or Active) provides a failover capability from the active RM to the standby RM. Each time the configuration database for the active the active RM’s configuration database.

RM is updated, the standby RM synchronizes its configuration database with

RM and a Standby RM. The redundancy group

RecordingManagerStorageManagement

One of the capabilities of the RM is the ability to manage storage. Operators define storage management parameters based on available disk space and the RM will control the recording and deletion of content accordingly. These parameters include:

• Days to continuously record live channels

• Time to keep unreferenced segments

• Time to keep assets

The Recorder functionality is integrated with key storage technologies as described in the section titled,

“Storage Types” on page 21.

RMWebGUI

The RM WebGUI provides the user interface to the RM, Recorder, and JITP server by allowing configuration and monitoring of channels, monitoring managed nodes, and scheduling recording. The RM WebGUI is an integrated interface application that is automatically installed with the RM software image and accessed through the RM IP address. RM also performs cDVR management and configuration of the Recorder and JITP/Stitcher.

PrivateandSharedCopyforContinuousRecord

In a shared copy cDVR environment, a single copy of a recorded program is stored in the network and can be accessed by multiple subscribers. In a private copy cDVR environment, one private copy of a program is available only to the subscriber requesting it. If two subscribers wish to view the same program, a separate copy (i.e., two copies) must be available for each requesting subscriber. Private copy allows service providers to deliver cloud-based DVR content to locations in which usage rights require private copies of programming per subscriber.

The RM has the ability to create either shared or private copy recordings from recordings made continuously.

cDVR User Guide, Release 2.0 23

Solution Overview - Functionality Description

Figure 2 shows the data flow differences between private and shared copy:

Figure 2. Private and Shared Copy Differences

EventualPrivateCopyMode

The system presents a link for each private copy but an actual replicated copy is not available until after the recording has completed.

Note: There is a global configuration setting to allow use of eventual private copy vs. progressive

private copy mode.

ProgressivePrivateCopyMode(hotrecordandPlayback)

In Progressive Private Copy mode, a unique, replicated copy is created for each subscriber when a recording starts. The replicated copies continue to be recorded even as the asset is being created. Furthermore, the user can playback from their private copy at any time.

In this mode, the continuous record buffer is deleted once the private copies are made.

Note: The previous continuous record deletion method is still available. A configuration parameter

must be set at the RM in order to use this new real time deletion method.

Both Eventual and Progressive Private Copy support up to 10,000 simultaneous private copy recordings.

cDVR User Guide, Release 2.0 24

Solution Overview - Functionality Description

PrivateCopyOptimization

Private Copy Optimization is a process that allows for maximum storage efficiency while maintaining private copy regulations using a process called De-duplication.

De-Duplication

For de-duplication3, a master asset is created and all other assets for an event are simply soft-linked to the master asset. No additional dynamic processing is required as the requested asset simply returns files across the soft-link from the fully complete master asset.

3. De-duplication is also referred to as intelligent data compression.

cDVR User Guide, Release 2.0 25

CHAPTER 3

cDVRInitialSetup

This chapter covers the basic steps required for initializing cDVR, which entails licensing and configuring the Telurio Packagers for their appropriate application (JITP and Recorder), and licensing the Telurio Recording Manager (RM).

InThisChapter:

• “Prerequisites,” next;

• “Overview” on page 26;

• “Storage Node Configuration” on page 27;

• “Packager Configuration” on page 28;

• “RM Licensing” on page 31;

• “What Next?” on page 33.

Prerequisites

Prior to performing initial setup of cDVR, you must have installed the appropriate Packager1 and RM software applications on your desired target servers. Refer to the Te l u r i o

Installation and Upgrade Guide and the CloudXtream Guide for instructions.

Additionally, you must have the appropriate network communication to and from all Imagine Communications cDVR Solution components (RMs, JITPs, Recorders, PCEs, TLBs), as well as communication to and from all other related cDVR nodes, whether Imagine Communications or third party (Transcoders, Storage Mounts, or Object Store).

Overview

After you have installed the appropriate software onto your servers, you must configure each application with a valid license, and perform basic system configuration for the JITP server and Recorder.

Caution: Each node in Imagine Communications’ cDVR solution requires static IP (not DHCP) address

configuration for correct operation. Refer to the Telurio Upgrade Guide for instructions on configuring static IP addresses for Packager. Refer to the

CloudXtream IP address for an RM.

Packager Software

DVR Software Installation, Setup, and Upgrade

Packager Software Installation &

DVR Software Setup & Upgrade Guide for instructions on configuring a static

1. For JITP and Recorder server applications

cDVR User Guide, Release 2.0 26

cDVR Initial Setup - Storage Node Configuration

StorageNodeConfiguration

If you are using cDVR for Private Copy, setting up one or more storage node(s) requires the following software / hardware components:

ecommended Hardware:

• HP Apollo 4520 recommended

oftware:

• PCE (Private Copy Engine) application — one or more instances (bjmh-2.0-

xxxxxx.rgb.x86_64.rampx)

• PLLB (Playlist Load Balancer) application — one or more instances (plb-1.0.0-xx.elx.x86_64.rampx)

StorageSystemTypeConfiguration(SharedCopy)

When using the system in Shared Copy Mode, depending on which type of storage server you are using, additional configuration may be necessary for the routing devices in your network. Follow the guidelines listed below for the applicable storage server.

NFSPortConfiguration

When using NFS or NFS4 as a storage server, the cDVR solution requires that certain ports be available for communication. communication ports.

Table 4. Communication port usage for cDVR

Application

XMLRPC API Unidirectional Recording Manager XMLRPC 80 & 443

Recording Manager Bidirectional Recording Manager UDP

Recording Manager Unidirectional Recorder XMLRPC 80 & 443

Recording Manager Unidirectional JITP Server

Recording Manager Unidirectional NAS-NFS NFS NFS

Recorder Bidirectional Recorder UDP

Recorder Unidirectional Recording Manager XMLRPC 80 & 443

Recorder Unidirectional NAS-NFS NFS NFS

Origin Unidirectional JITP Server

Table 4 below provides a list of protocols/components and their corresponding

Communication Direction

Communication Target Protocol Port Number

9036

(Packager)

Multicast

Safenet UDP

XMLRPC 80 & 443

UDP

Multicast

HTTP Content served from JITP

12344-12346

5093

9047

9036

12344-12346

cDVR User Guide, Release 2.0 27

cDVR Initial Setup - Packager Configuration

Table 4. Communication port usage for cDVR

Application

JITP Server (Packager)

Communication Direction

Unidirectional Recording Manager XMLRPC Events 80 & 443

Unidirectional NAS-NFS NFS NFS

Communication Target Protocol Port Number

StorageSystemTypeConfiguration(PrivateCopy)

When using the system in Private Copy Mode, Webdav-light is used for storage for all components. Webdav-light is bundled in the Imagine Communications’-provided operating system (CentOS 7.2)

PackagerConfiguration

Each instance of a JITP server and Recorder is, in actuality, a Packager application. Prior to performing any cDVR-related configuration from the RM, you must perform initial configuration and licensing on each Packager. on each Packager, regardless of whether the Packager is used as a Recorder or JITP server.

Table 5 below provides a list of required system configuration that must be performed

PackagerSystemConfiguration—RequiredMenus

Table 5 provides a list of system parameters that will need to be configured or verified according to

your network-specific parameters via the Packager’s interface (GUI or API). Instructions for configuring

each of these menus can be found in the System Configuration chapter of the Tel u ri o Guide (Chapter 4).

Table 5. Required system configuration before configuring packaging

Parameter GUI Menu / API Call Requirement

Hostname

License key sysconfig >> license Required

DNS sysconfig >> network >> dns Required

Network interface

assignment

Packager IP address sysconfig >> network >> ip Required

Network routes sysconfig >> network >> route Required

NTP server(s) sysconfig >> ntp Optional, but recommended

POIS sysconfig >> pois Required if using ad insertion

Syslog server sysconfig >> syslog Optional, but recommended

Timezone sysconfig >> timezone Required if not using NTP server

sysconfig >> hostname Optional, but recommended

sysconfig >> network >> interface >> assignment

Required

Packager User

a. When configuring a hostname for Packager, the hostname must not contain any uppercase letters. b. Two parameters must be configured here: 1) The Management interface (set to eth0 or equivalent) and 2) The Ex-

ternal interface (where the video or origin traffic is passed).

cDVR User Guide, Release 2.0 28

cDVR Initial Setup - Packager Configuration

PackagerMenusConfiguredbyRM

The following GUI menus (or API calls) are configured by the RM and should not be configured directly from the Packager GUI or via an API call directly to the Packager server. Attempting to change the parameters in these menus without the RM can cause the cDVR network to malfunction.

Table 6. Packager menus that should not be changed in the Packager GUI

Packager Menu Tree / API Call NOT to be modified

configuration >> audiomap (all) show add / modify / remove

configuration >> input (all) show add / modify / remove

configuration >> jitp (all) show add / modify / remove

configuration >> output >> directory (all) show add / modify / remove

configuration >> output >> format (all) — Recorder only

configuration >> output >> stream (all) show add / modify / remove

configuration >> package (all) show add / modify / remove

configuration >> session (all) show abort

configuration >> stitcher (all) show add / modify / remove

sysconfig >> config (all) backup /

sysconfig >> database (all) show set

sysconfig >> defaults (all) show add / modify / remove

sysconfig >> ingestproxy none not used as part of

sysconfig >> keyserver (all) show add / modify / remove

sysconfig >> policy show set

sysconfig >> system show lock, restart, unlock

Menu Action OK to use

show modify

backupfile

Menu Action - NOT OK to use

reset, restore

cDVR; do not configure.

a. Modifying output formats is not allowed for Recorder; however, it is allowed for the JITP server

InstallingthePackagerLicense

Each instance of a JITP server and Recorder requires a separate, application-specific license. Beginning with release 6.0, Packager prefers an external license server in order to perform packaging services. Imagine Communications’ offers standalone and redundant instances of SafeNet licensing. For detailed

installation instructions, refer to the latest Te l ur io

For a Packager appliance that leverages a License Server, you must upload a new license key file to update licensing.

To install a Packager license, proceed as follows:

1. Log into the GUI by navigating to the Packager’s IP address.

2. Enter the username and password for access (default is admin/ripcode!)

3. From the System tab, click through to sysconfig >> license >> lockcode >> show.

cDVR User Guide, Release 2.0 29

Packager Software Installation and Upgrade Guide.

cDVR Initial Setup - Packager Configuration

4. Copy the Lockcode field entry and contact Imagine Communications Customer Support for

further instructions on receiving a license key.

5. After obtaining the license key from Imagine Communications, return to the Packager GUI.

6. From the System tab, click through to sysconfig >> license >> server >> set.

7. In the Server Address field, enter the remote license server IP address.

8. Click Submit to save changes.

9. From the System tab, click through to sysconfig >> license >> update.

10. In the License File URL field, enter one of the following:

• The full HTTP or TFTP URL to the remote license key file. For example:

http://remotehost/path/to/licenseFile.key tftp://remotehost/path/to/licenseFile.key

-or-

• The actual license key strings as received from Imagine Communications (copying and pasting

is recommended).

11. Click Submit to save changes and apply the new license.

12. Perform the steps in this section for every Packager within your cDVR system.

Note: Each Packager requires its own license, regardless of redundancy or load balancing. For example,

if you have two Recorders operating in 1+1 redundancy, two JITP-only servers, and 2 JITP-withStitcher servers, you will need a total of six (6) Packager licenses: 2 for Recorder, 2 for JITP only, and 2 for JITP+Stitcher.

ViewingPackagerLicensing

You can see which type of licensing the Packager has based on whether it has been licensed for Recorder, JITP, or JITP with Stitcher.

From the System tab, navigate to sysconfig >> license >> show, and click Submit.

Results will appear similar to the following:

cDVR User Guide, Release 2.0 30

cDVR Initial Setup - RM Licensing

JITP only

Recorder only

Note: In a typical network deployment, License Key Features will generally be for either JITP only or for

Recorder only. The graphic below shows both JITP and Recorder licenses together for simplicity.

AdditionalPackagerLicensingInformation

For additional details on installing, viewing, and testing Packager licensing, please refer to the Telur io Packager Software Installation and Upgrade Guide.

UsingRecorderforEBRvs.CR

If you are planning to use the same Recorder for both event-based recording (EBR) and continuous recording (CR), please note that the RM will set the output format to HLS version 4 so as to accommodate CR. If you wish to change the output format to something else for EBR, the following two rules should be followed when configuring a Recorder:

• Use separate Packagers for EBR and CR, -and-

• Do not change anything in the configuration >> output >> format >> hls menu of the

Packagers.

Note: For HLS output, a Packager, whether it is operating as a Recorder or a JITP server, can output

either only HLSv2 or only HLSv4, but not both versions at the same time.

RMLicensing

The RM has a built-in License Server that manages licenses for management. If desired, the RM can use an external License Server; in this case, you must configure the RM to point to the IP address or host name (DNS name) for the external server where the Licensing Application is installed.

For an RM application that leverages the localhost License Server, you must upload a new license key file to update licensing for the RM.

Note: Using the RM as its own license server (localhost) is the most typical method of licensing.

cDVR User Guide, Release 2.0 31

cDVR Initial Setup - RM Licensing

InstallingtheRMLicense

To install a RM license, proceed as follows:

1. Log into the GUI by navigating to the RM’s IP address.

2. Enter the username and password for access (default is admin/ripcode!)

3. From the System tab, click the triangle symbol next to the Licensing container to expand the

menu.

4. Click on Lock Code.

5. From the license Lockcode menu, copy the contents of the Lock Code field entry and contact

Imagine Communications Customer Support for further instructions on receiving a license key.

6. After obtaining the license key from Imagine Communications, return to the expanded Licensing

container in the RM GUI.

7. Click on Server.

8. Click the icon to bring up the Modify window..

9. In the Active Server field, enter either the remote license server IP address or, if using the RM as its

own license server, enter the RM’s own IP address

10. Click Submit to save the new license server.

11. From the Licensing container, click on Update.

12. Click the icon to bring up the Modify window.

13. In the URL field, enter one of the following, depending on what kind of license server you are

using:

• The full HTTP or TFTP URL to the remote license key file. For example:

http://remotehost/path/to/licenseFile.key

2. Alternatively, you may enter “localhost” instead of the RM’s IP address; however, we recommend using the IP address instead.

cDVR User Guide, Release 2.0 32

cDVR Initial Setup - What Next?

tftp://remotehost/path/to/licenseFile.key

-or-

• A path to a file located on the localhost. For example:

/root/path/licenseFile.key

-or-

• The actual license key strings as received from Imagine Communications (copying and pasting

is recommended).

14. Click Submit to save changes and apply the new license.

15. If you are using RM 1+1 node-level redundancy, perform the steps in this section for both RMs that

will be in the redundancy group.

ViewingRMLicensing

You can view RM licensing details as follows:

From the System tab, click the triangle symbol next to the Licensing container to expand the menu, then click Details to view the Licensed Feature Details contents.

Results will appear similar to the following:

WhatNext?

Now that you’ve performed initial configuration and licensing for your cDVR components, proceed to

Chapter 5, “Recording Manager GUI Overview” to get familiar with the RM GUI.

cDVR User Guide, Release 2.0 33

CHAPTER 4

RMRedundancySetup

This section describes how to set up two RMs to operate in node-level 1+1 active/standby redundancy. If you are not using RM redundancy in your deployment, you may skip this chapter and proceed to

Chapter 5, Recording Manager GUI Overview on Page 41.

This release of cDVR supports 1+1 active/standby redundancy for the RM component only.

InThisChapter:

• “Prerequisites,” next;

• “Networking Requirements” on page 34;

• “Redundancy Configuration Instructions” on page 36;

• “Removing RM Redundancy” on page 38;

• “What Next?” on page 40.

Prerequisites

In order to set up RM redundancy, you must have installed the RM software application on both devices meant to be redundant. (Refer to the CloudXtream

instructions.)

NetworkingRequirements

In order to configure RM node redundancy you must ensure the two target RMs can communicate multicast management traffic to each other.

Caution! RM redundancy uses the multicast address of 225.0.0.38 for all redundancy communication.

This multicast IP address should not be changed routers are not configured to pass multicast traffic (the default) then you must manually configure all relevant interfaces on the router(s) to pass the 225.0.0.38 multicast address.



Unicast over port 9036 is used for initial setup exchanges between RMs, however, ongoing redundancy communication is performed through multicast over ports 12344-12346. For more information on communication protocols and their respective ports, refer to

Configuration” on page 27

DVR Software Setup & Upgrade Guide for

on RM. As such if your WAN-based network



“Storage Node

1. If your network configuration requires the use of a different multicast IP address, please contact Imagine Communications Customer Support for further instructions. See

cDVR User Guide, Release 2.0 34

“Contacting Customer Support” on page 164.

RM Redundancy Setup - Networking Requirements

GatewayRouteRules

In order for multicast messages to pass between the redundant RMs, the correct route tables must be configured. If you configured the redundant RMs with a static IP address (rather than the default DHCP configuration), you most likely configured a gateway IP address during the OS installation process. However, this did not automatically configure a default gateway. Rather, it was used to configure

various internal network tables. In instances where multiple Ethernet interfaces given RM, Imagine Communications recommends that you manually configure a default gateway in order to pass multicast traffic between redundant RMs.

Configuring a default route can be done in one of two ways: set a default route for both Recording Managers (recommended), or add a static route for both. Both methods are described below:

Option1:SetDefaultRoutesonbothRMs(Recommended):

1. In both RMs’ GUI, click the System tab and click through to Network > IP > IP Address Configuration.

2. Click the wrench ( ) icon next to the entry for the appropriate Ethernet interface.

3. In the Mode field, select Default Gateway.

4. A new field called Gateway Address will appear; enter the IP address of each respective device’s

default gateway IP address.

are available for a

Example: If RM-A’s IP address is 10.10.10.15 with a 16-bit mask, its default gateway will most likely be 10.10.0.1. If RM-B’s IP address is 192.168.30.150 with a 24-bit mask, it’s gateway IP address will most likely be: 192.168.30.1.

5. Click Submit.

6. Restart the IP services for both RM’s via the System tab > Network > IP > IP Restart menu.

Option2:ConfigureaStaticRouteonbothRMs:

Note: This option should only be used to configure static routes, not the default gateway.

1. In both RMs’ GUI, click the System tab and click through to Network > Routes and click the plus ( ) icon to add a route.

2. Enter the destination multicast subnet address in the Destination field. (For example, this address could be 225.0.0.38)

3. Enter the subnet mask for the destination subnet in the Mask field. (For example, this address could be 255.255.255.255)

4. Enter the gateway IP address to use for the subnet in the Gat eway field. Leave this field blank to use the default gateway.

Note: For multicast addresses, the Gateway field must always be left blank.

5. From the Interface drop-down box, select the appropriate target interface

6. Click Submit.

2. If you have only one Ethernet interface on the system hosting the RM application, explicitly setting a default gateway is not required. With multiple interfaces, however, the OS setup process will automatically setup a default gateway on the first Ethernet interface it finds. As such, if the interface you wish to use is not the first one the OS finds, not having an explicit default gateway set up for the desired interface may prevent communication between RMs.

cDVR User Guide, Release 2.0 35

RM Redundancy Setup - Redundancy Configuration Instructions

SpecialNotesonRoutes

• Imagine Communications’ multicast management traffic (used for redundancy management) is

sent to the multicast group on 225.0.0.38.

• If the default gateway that you configured in Option 1 was for an interface other than what is

assigned as the management interface, then Option 2 must also be used to configure an entry for

225.0.0.38 on the management interface.

Caution! If more than one interface is configured and the management interface does not have a

default gateway configured, without adding the 225.0.0.38 address to the management interface the redundancy multicast management traffic will use the interface containing the default gateway instead of the management interface, which will cause redundancy to fail.



For more information on communication protocols and their respective ports, refer to “Storage

Node Configuration” on page 27

RedundancyConfigurationInstructions



Perform the steps in this section from only the Primary RM. You do not need to perform any steps from the Standby RM, except to verify settings.

LogIntoPrimaryRM

1. Open a Firefox or Chrome web browser from a management computer that has access to the Recording Manager.

2. Navigate to the physical IP address of the RM that will start as the primary. This will be the group master as long as it’s active.

3. Log in with the credentials: admin/ripcode!

ConfigureRedundancyGroupDetails

4. Click the System tab.

5. Click the triangle [ ] symbol next to the Redundancy container to expand the menu, then click

on Group.

3. For multicast management traffic, RM expects to communicate over the currently configured management

interface. Usually this defaults to eth0, however, the name of this interface depends upon the particular hardware in use.

cDVR User Guide, Release 2.0 36

RM Redundancy Setup - Redundancy Configuration Instructions

6. Click the wrench [ ] icon to bring up the Modify window.

The Group Type and Product Type menus are preselected for 1+1 and RAPS respectively as shown below. :

7. In the Virtual IP field, enter the virtual IP address that will be assigned to both the Primary and Standby RMs.

8. Click Submit to save and add the redundancy group.

9. Confirm the Connection Status icon in the top right corner of the GUI changes from red to green

(response time should be less than a minute).

Note: Once you have configured a redundancy group from the physical IP address of the master RM, all

further configuration, including the section below, should be performed via the GUI of the VIP which you set in

Step 7 above.

AddStandbyHostfromPrimaryRM

10. Log in to the VIP address of the redundancy group.

11. From the System tab of the VIP RM, click the triangle [ ] symbol next to the Redundancy

container to expand the menu, then click on Hosts.

12. From the Redundancy Host menu, click the plus ( ) icon to add a host entry (the Primary host entry will already be present).

The ADD menu will open.

cDVR User Guide, Release 2.0 37

RM Redundancy Setup - Removing RM Redundancy

13. In the Host IP field, enter the IP address of the Standby RM.

14. The Host Type drop-down menu should already be preselected to Standby.

15. Click Submit to save and add the Standby RM to the redundancy group.

VerifyRedundancy

16. From the System tab, click the triangle [ ] symbol next to the Redundancy container to expand the menu, then click on Group.

17. Ver ify the host_type and host_state for the Primary RM show Active/Active as their entries.

18. Ver ify the host_type and host_state for the Standby RM show Standby/Idle as their entries.

RedundancyStates(MoreInformation)

For more information on the redundancy states and their meanings, refer to the section titled,

“Redundancy Tree” on page 150.

RemovingRMRedundancy

There are two levels of redundancy removal, depending on whether you wish to remove only the standby host, or redundancy altogether.

cDVR User Guide, Release 2.0 38

RM Redundancy Setup - Removing RM Redundancy

Note: When performing any redundancy removal actions, whether removing a host from the group or

the group itself, all actions are performed from the Active RM. No actions are required from the Standby RM.

RemoveStandbyHostfromRedundantGroup

In certain upgrade, downgrade, or configuration situations, you may be required to remove the standby RM while keeping the redundancy group intact. For example, you may wish to make a standby RM a standalone RM or you wish to make a standby RM part of a different redundancy group.

To remove only the standby RM, proceed as follows:

1. Log in to the Active or VIP RM.

2. From the System tab, click the triangle [ ] symbol next to the Redundancy container to expand

the menu, then click on Hosts.

3. Locate the row entry in which the Host Type indicates Standby and click the trash

() icon.

4. From the confirmation pop-up box, click Delete to confirm.

The resulting Redundancy Host menu should now show only the Active RM as a host.

Note: Once the Standby RM has been removed from the redundancy group, the Standby (now a

standalone) will not be accessible until its services restart—about 30 seconds.

RemoveRedundancyGroup

In certain upgrade, downgrade, or configuration situations, you may be required to completely tear down redundancy between two RMs. Tearing down redundancy means removing both the standby host and the redundancy group itself, thus leaving no trace of redundancy on either system.

To remove the redundancy group from the RM, proceed as follows:

1. Log in to the Active RM (not the VIP).

2. Remove the Standby host first as described in the previous section,

Redundant Group” on page 39

“Remove Standby Host from

cDVR User Guide, Release 2.0 39

RM Redundancy Setup - What Next?

Caution: You cannot remove an active redundancy host without first removing the standby host.

3. From the System tab, click the triangle [ ] symbol next to the Redundancy container to expand the menu, then click on Hosts.

4. Select the row entry in which the Host Type indicates Active (which should be the only entry in the list) and click the trash

5. From the confirmation pop-up box, click Delete to confirm.

Navigating to the SYSTEM > Redundancy > Group menu should show empty fields from the Redundancy Group status menu.

() icon.

WhatNext?

Now that you’ve performed redundancy configuration for your cDVR components, proceed to Chapter

5, “Recording Manager GUI Overview”

cDVR User Guide, Release 2.0 40

to familiarize yourself with the RM GUI.

CHAPTER 5

RecordingManagerGUIOverview

The Recording Manager (RM) GUI is the user interface for configuring and monitoring all RM components, including: node configuration, system configuration, channel management, event-based and continuous record, and alarm and event monitoring.

This chapter provides an overview for navigating the RM GUI interface.

InThisChapter:

• “Prerequisites,” next.

• “Launching RM” on page 42.

• “Understanding RM Tools” on page 43.

• “Icons and Buttons” on page 46.

• “Tab Overview” on page 47.

Prerequisites

Before you can use the RM GUI you must have performed the procedures described in Chapter 3,

“cDVR Initial Setup”

and Chapter 4, “RM Redundancy Setup”.

cDVR User Guide, Release 2.0 41

Recording Manager GUI Overview - Launching RM

LaunchingRM

The RM GUI is installed with the RM server software and can be accessed by navigating to the RM’s IP address from a standard Firefox or Chrome web browser.

LoggingIntotheRMGUI

To log in to the GUI, you will need the IP address of the RM.

1. From a Firefox or Chrome browser, navigate to the RM’s IP address.

Note: If you configured 1+1 RM redundancy, log in using the VIP.

2. Enter the default Username and Password as follows:

Username: admin Password: ripcode!

cDVR User Guide, Release 2.0 42

Recording Manager GUI Overview - Understanding RM Tools

Upon successful login, the RM GUI opens at the Dashboard tab:

UnderstandingRMToo ls

Numerous tools are built into the RM interface to simplify configuration, management, and monitoring of the RM and Recorder components. This section describes the overall GUI, screen components, colorization, and icons. The following topics are covered:

• RM GUI Hierarchy

• Navigating the RM GUI

RMGUIHierarchy

The RM GUI is organized in a tab-to-container and tree-branch fashion, where the major configuration and monitoring functions are separated in tab-based menus that further drill down to nested or tree/ branch containers.

Figure 3 below provides a quick snapshot of the overall RM menu hierarchy.

cDVR User Guide, Release 2.0 43

Recording Manager GUI Overview - Understanding RM Tools

Tab s

Sub-tabs

Figure 3. RM Hierarchy

NavigatingtheRMGUI

The RM GUI has several screen components to enable quick navigation and immediate system status.

Figure 4 below provides an overview of the GUI’s basic navigation tools.

cDVR User Guide, Release 2.0 44

Recording Manager GUI Overview - Understanding RM Tools

Tabs

Sub-tabs

Collapsed containers

Selects all items

Selects individual items

Action buttons

Expanded container (with nested options)

Sorts in descending order Sorts in ascending order

Figure 4. GUI Navigation Tools

cDVR User Guide, Release 2.0 45

Recording Manager GUI Overview - Icons and Buttons

IconsandButtons

The RM GUI makes use of several graphic and text based icons and buttons to easily convey status and actionable items. In general, an icon will display a status of some sort while a button or check-box provides the ability to make a change to the system.

Table 7 provides a description and general legend of each status icon and action button.

Table 7. Icon and Button Meanings

Symbol Applies to: Meaning

General system

NODES tab

SCHEDULES tab

SHARED / UNIQUE ASSETS tabs

General system

NODES tab

SCHEDULES tab

SHARED / UNIQUE ASSETS tabs

General system

NODES tab

SCHEDULES tab

SHARED / UNIQUE ASSETS tabs

General system, all tabs General system & all tabs—indicates more information is available

General system, all tabs General system & all tabs—mousing over the question mark will

SCHEDULES tab

SHARED / UNIQUE ASSETS tabs

SCHEDULES tab

SHARED / UNIQUE ASSETS tabs

SCHEDULES tab SCHEDULES—schedule is marked for imminent deletion.

General system—connectivity status to RM and hardware is good.

NODES—status of node is good. Good connectivity, responsive to

status checks.

SCHEDULES—schedule is currently running.

SHARED / UNIQUE ASSETS—several states are conveyed with

this icon: a) asset is currently in the process of being created; b) asset initialization success; c) a request for an immediate copy has successfully started; d) a scheduled copy has started successfully.

General system—there are unacknowledged system errors of at least a Warning level, or there is a hardware-related warning.

NODES—some sort of connectivity to a node may have failed or a redundancy failure has occurred.

SCHEDULES—schedule has been set, but there is an error, or the schedule is attempting to run again.

SHARED / UNIQUE ASSETS—partial success in asset creation or another type of warning.

General system—several states are conveyed with this icon: a) connectivity to RM has failed, b) hardware failure, or c) a critical alarm has occurred and has not been acknowledged.

NODES—connectivity to node has failed.

SCHEDULES—the schedule failed to run.

SHARED / UNIQUE ASSETS—asset failed to launch or failed to

complete successfully.

for the status or configuration parameter of a particular item. Clicking on the icon will open a dialog box with more information.

open a tool tip for additional configuration help.

SCHEDULES—schedule has been completed.

SHARED / UNIQUE ASSETS—asset creation has been completed.

ASSETS—when using PRIVATE copy, this icon indicates the private copy asset is complete, but there is a problem (either the copy failed or otherwise had issues).

SCHEDULES—schedule start is pending.

SHARED / UNIQUE ASSETS—asset creation is pending.

cDVR User Guide, Release 2.0 46

Recording Manager GUI Overview - Tab Overview

Table 7. Icon and Button Meanings

Symbol Applies to: Meaning

SCHEDULES tab SCHEDULES—schedule is starting.

SCHEDULES tab SCHEDULES—schedule is stopping.

DASHBOARD tab

CONFIGURATION tab (sub tabs: GLOBAL, NODES, JITP/ RECORDER, & CHANNELS)

SYSTEM tab

REPORTS tab

All menus Clicking this button opens a pop-up window to modify existing

All menus Clicking this button causes a command to be executed, such as a

All menus Clicking this button adds a new row entry to the tree or branch

All menus Clicking this button deletes an existing row entry from the tree or

TabOverview

There are four main tabs available in the RM GUI which allow you to configure and monitor the cDVR components: Dashboard, Configuration, System, and Reports. These tabs are briefly referenced here and are discussed in detail in the subsequent chapters of this user guide.

Clicking on the triangle or the container name will expand the menu out one level for additional configuration or information.

Clicking directly on the triangle next to the menu tree will expand the menu out one level.

configuration.

backup, a restart, or polling for information.

category.

branch category.

Dashboard

The DASHBOARD tab provides a snapshot view of the hardware status for the RM and cDVR-related events.

cDVR User Guide, Release 2.0 47

Recording Manager GUI Overview - Tab Overview

Configuration

The CONFIGURATION tab is where you will do most of your cDVR provisioning, including global recording parameters, node setup, channel configuration, and recording scheduling. The tab includes the following sub-tabs: Main, Nodes, JITP/Recorder, Channels, Scheduler, Event Based Recordings, Shared Assets, and Unique Assets.

System

The SYSTEM tab provides functions related to maintaining and configuring RM system parameters. From here you can perform actions such as setting up network parameters, timezones, redundancy, and licensing; you can manage the RM database and services, and you can view and update software, in addition to other system-related setup.

cDVR User Guide, Release 2.0 48

Recording Manager GUI Overview - What Next?

Reports

The REPORTS tab displays capacity and statistical information about the RM, such as CPU, memory, and disk capacity, processes status, and additional information provided in graph format.

WhatNext?

The remaining chapters of this user guide provide detailed information about each RM tab and subtab, including explanations of each field or set up parameter.

For steps on how to set up an Imagine Communications cDVR system from beginning to end, refer to the cDVR Quick Start Guide for this release.

cDVR User Guide, Release 2.0 49

CHAPTER 6

Dashboard

This chapter describes the Dashboard tab of the RM GUI, which can be accessed by logging in to the RM as described in the section titled,

InThisChapter:

• “Dashboard Overview,” next.

• “Hardware” on page 51.

• “Events” on page 52.

DashboardOverview

“Launching RM” on page 42.

The RM GUI Dashboard tab presents information for Hardware and Events. Each container can be expanded or collapsed by clicking on the triangle next to the title of each section.

Icons

The icons displayed in the Dashboard indicate current system or line item status. Each item will display the highest error condition state for that category.

• — Indicates the current status is good; no errors are present on the RM or the specified task.

• — Indicates there is a major or warning condition present; some errors have occurred during

recording operations.

• — Indicates the presence of a critical error condition.

• — Indicates more information is available for a particular event.

cDVR User Guide, Release 2.0 50

Dashboard - Hardware

Hardware

This section displays information about the status of the RM hardware including Memory Usage, CPU Usage, and Disk Usage.

cDVR User Guide, Release 2.0 51

Dashboard - Events

Events

This section displays current and historical events on the system for critical, major, warning, and informational severity levels. Many filtering options are available from the Events summary, including the ability to sort events based on category or acknowledged state.

cDVR User Guide, Release 2.0 52

Dashboard - Events

MenuDescription

Table 8 describes the fields and columns available in the Events container:

Table 8. Events fields

Name Typ e Description

Acknowledgement Action Button Use the drop-down menu to select which type of

Severity Menu Navigation Use the drop-down menu to choose the minimum level of severity

Filter Menu Navigation Use the drop-down menu to filter displayed results. Choices are:

Page Size Menu Navigation Use the drop-down menu to choose the number of results

Auto-Refresh Menu Navigation Use the drop-down menu to choose whether to enable or disable

ID Column Heading Displays the line entry number of the event. Clicking on this

Severity Column Heading Displays the severity level of the event. Clicking on this column

Created Column Heading Displays the date and time the event occurred. Clicking on this

Source Column Heading Displays the IP address or hostname of the node from which the

Ack Date-Time Column Heading Displays the date and time that the event was acknowledged (if

Detail Column Heading Provides a detailed description of the event

acknowledgement to choose for one or more events. Choices are:

Acknowledge Selected — acks highlighted events

Unacknowledge Selected — unacks highlighted events

Acknowledge All — acks all events

that will be displayed in the events list. Choices are:

Info — displays all events, including Info events

Warning — displays all events from Warning level and up,

excluding Info events

Major — displays all events from Major level and up, excluding Warning events

Critical — displays all Critical level events, excluding all others.

All, Acknowledged, or Unacknowledged

displayed per page. Choices are:

20, 50, or 100

events from being automatically refreshed. Choices are:

Enable or Disable

column header will sort events by ascending or descending ID number

header will sort events by ascending or descending severity level.

column header will sort events by ascending or descending date and time.

event originated. The nodes whose events are reported are:

RM, JITP, or Recorder.

Clicking on this column header will sort events by ascending or descending IP address or hostname.

Note: For JITP and Recorder, the event description will reference the JITP or Recorder as a Packager

ack’d at all). Clicking on this column header will sort events by ascending or descending Ack date and time.

cDVR User Guide, Release 2.0 53

Dashboard - Events

ViewingDetailedInformationforanEvent

You can view detailed information for a given event by clicking the icon next to a row entry. An Event Details window for a specific event will open similar to the one shown below.

AcknowledgingandUnacknowledgingEvents

An active event condition may be cleared by acknowledging its status. When you unacknowledge an event, its active severity status is reinstated on the system.

To acknowledge or unacknowledge one or more events:

1. Select the desired events from the summary list.

- To select a group of consecutive events, click on the first event in the group, hold down the

SHIFT key on your keyboard, and click on the last event in the group.

- To select a group of non-consecutive events, hold down the CTRL key on your keyboard while

clicking on the desired events.

2. From the Severity field, choose the minimum severity level by which to filter the events.

Note: The severity filter will return events that match the minimum severity criteria. Choosing Critical

will return events that are only critical severity. Choosing Major will return Major severity events and higher. Choosing Warning will return all Warning and higher events.

3. From the Filter field, choose whether to sort events based on acknowledged state, or select All to

display both acknowledged and unacknowledged events.

4. From the Acknowledge field, select whether to Acknowledge Selected, or Unacknowledge Selected,

or Acknowledge All events.

cDVR User Guide, Release 2.0 54

Dashboard - Events

Unacknowledged Events Shown

Acknowledged Events Shown

5. Click on Ack/Unack next to the drop down box.

The selected event(s) are immediately acked or unacked.

Note: For a complete list of event messages, refer to the Recording Manager List of System Events &

Trap s.

cDVR User Guide, Release 2.0 55

CHAPTER 7

Configuration

This chapter describes the Configuration tab of the RM GUI, which can be accessed by logging in to the RM as described in the section titled, scheduling is performed in this tab. System related configurations for the RM are performed from the

System Configuration tab (next chapter).

InThisChapter:

• “Overview,” next.

• “Global Config Sub-tab” on page 57.

• “Nodes Sub-tab” on page 60.

• “JITP/Recorder Sub-tab” on page 71.

• “Channels Sub-tab” on page 83.

• “Schedules Sub-tab” on page 86.

• “Event Based Recordings Sub-tab” on page 93.

• “Shared Assets Sub-tab” on page 95.

• “Unique Assets Sub-tab” on page 101

• “Content Management” on page 108.

“Launching RM” on page 42. All recording configuration and

Overview

The CONFIGURATION tab consists of several sub-tabs in which all recording-based parameters are provisioned for various cDVR components, such as transcoders (Imagine Communications-based or third party), Recorders, JITP servers, and storage devices. All scheduling and recording is performed from the CONFIGURATION tab. The sub-tabs are described in detail in subsequent sections, but are shown and briefly described below as an overview.

• GLOBAL CONFIG — contains global recording and content delivery parameters for system

components

• NODES — allows you to add all node-related parameters, such as IP addresses and storage

locations

• JITP/RECORDER — provides configuration for all packaging-related parameters, such as key

servers, audio maps, JITP profiles, and source servers

• CHANNELS — allows you to add the transcoded programs that will be recorded

cDVR User Guide, Release 2.0 56

Configuration - Global Config Sub-tab

• SCHEDULER — provides detailed scheduling for both event-based and continuous recording.

• EVENT BASED RECORDINGS — displays a list of all event-based programs that have been or are

currently being recorded

• SHARED ASSETS — provides the ability to create and display shared content assets from CR

segments that have been or are currently being recorded.

• UNIQUE ASSETS — provides the ability to create and display private copy content assets from CR

segments that have been or are currently being recorded.

Sub‐tabOrganization

The sub-tabs are organized in a procedural left-to-right, top-to-bottom fashion. That is, the system should be configured starting with the left-most tab and ending with the right-most tab. Containers within each tab should be configured starting at the top and moving to the bottom.

Note that depending on your specific network deployment, not all tabs will require configuration or viewing. Specifically, the default settings in the GLOBAL CONFIG sub-tab may not need to be changed, and depending on whether you are using Event Based Recordings or Continuous Recordings, you may or may not need to view the EVENT BASED RECORDINGS or SHARED/UNIQUE ASSETS sub-tabs.

GlobalConfigSub‐tab

The GLOBAL CONFIG sub-tab is accessed by clicking through the CONFIGURATION > GLOBAL CONFIG menu path. In this menu, you can configure global parameters for segment directory and

asset sizes and when to delete assets and segments.

The two containers in the Main sub-tab are:

• Segments Container

• Assets Container

SegmentsContainer

The Segments container allows you to customize duration and storage deletion parameters for segment directories.

A segment directory contains individual segment files (usually in .TS format). A segment file consists of multiple content fragments (pieces of video and audio). The Segments container pertains to settings for segment directories only, not individual segments and not fragments.

To open the segment parameters, navigate to:

cDVR User Guide, Release 2.0 57

Configuration - Global Config Sub-tab

Segments container - Default

CONFIGURATION  GLOBAL CONFIG  Segments  [expand]

If you wish to modify the parameters in this menu, click the wrench icon ( ) to open the Modify menu.

Table 9 describes the fields in the Segments nested container.

Table 9. GLOBAL CONFIG > Segments

Name Description Default

Segment Directory Size (minutes) Specifies the maximum size (duration) in minutes of

content in an asset’s segment directory. A new segment directory is created when the duration is reached.

Value range: 1 to 30

Segment Unreferenced Age (days)

Specifies the absolute number of days before a segment not associated with an asset is deleted. Once deleted, unreferenced segments are no longer available for asset creation.

Value range: 1 - 40000

AssetsContainer

The ASSETS container allows you to set when CR assets are deleted from the storage server.

To open the assets parameter, navigate to:

cDVR User Guide, Release 2.0 58

Configuration - Global Config Sub-tab

Assets container - Default

CONFIGURATION  GLOBAL CONFIG  Assets  [expand]

If you wish to modify the parameters in this menu, click the wrench icon ( ) to open the Modify menu.

Table 10 describes the f ield in the Assets nested container.

Table 10. Main > Content Delivery fields

Name Description Default

Asset Max Age (days) Specifies the absolute number of days before an asset

(associated with segment directories) is deleted.

Value range: 1 - 40000

cDVR User Guide, Release 2.0 59

Configuration - Nodes Sub-tab

NodesSub‐tab

The NODES sub-tab is accessed by clicking through to CONFIGURATION > NODES. The NODES menu is where you will configure the bulk of your initial setup parameters including transcoders, JITP servers, storage mounts, and Recorders.

The following server components are described in this section:

• Transcoders Container

• JIT Packagers Container

• Playlist Load Balancer

• Storage Mounts Container

• Recorders Container

• BJM Hosts Container

Each of these components is discussed in detail in “Solution Overview” on page 19. This section describes GUI configuration parameters for each container listed above.

TranscodersContainer

The TRANSCODERS container allows you to set up one or more transcoding devices that will be used

for cDVR input. You can use an Imagine Communications transcoder, such as the Selenio Selenio

To view the Trans coder s container, navigate to:

TAT, or you can use a third party transcoder.

VMG or

cDVR User Guide, Release 2.0 60

Configuration - Nodes Sub-tab

Default

Populated

CONFIGURATION  NODES  Transcoders  [expand]

ConfiguringaTranscoder

You can add( ), modify ( ), or delete ( ) a transcoder from this menu, using Table 11 below for guidelines.

Table 11. Transcoders Node fields

Name Description Default

Status Indicates current RM connectivity status to the transcoder. One of two

icons will be displayed here:

Green checkmark — RM has good connectivity with the transcoder

Red “X” — transcoder

connectivity.

Name Specifies the name the RM will use when referencing the transcoder.

When setting this parameter, use a unique name.

IP Address Specifies the IP address of the transcoder. Empty

Type Specifies what type of transcoder is being used. Choices are:

VMG — Imagine Communications’ hardware-based transcoder

TransAct — Imagine Communications’ software-based transcoder

Other — third party transcoder

Click this button to add a new entry. n/a

Click this button next to an entry you wish to delete. n/a

is in the RM’s database, but there is no current

n/a

Empty

None selected

Click this button to modify parameters for an existing entry. n/a

cDVR User Guide, Release 2.0 61

Configuration - Nodes Sub-tab

Default

Populated

JITPackagersContainer

The JIT Packagers container allows you to set up one or more JITP servers that will be used to create ABR-ready chunks from the MBR IDR aligned streams generated by the Recorder. This device must be

a Packager licensed for JITP (and optionally for Stitcher

Caution: If you are using RM node-level redundancy for your system, you must first configure

redundancy for the RM’s before adding any JITP servers to this container. Refer to

“RM Redundancy Setup”

To view the JIT Packagers container, navigate to:

Configuration  Nodes  JIT Packagers  [expand]

for instructions.

Chapter 4,

ConfiguringaJITPackager

You can add( ), modify ( ), or delete ( ) a JIT Packager from this menu, using Table 1 2 below for guidelines.

1. Stitcher is required for CR.

cDVR User Guide, Release 2.0 62

Configuration - Nodes Sub-tab

Table 12 describes the fields in the JIT Packagers nested container.

Table 12. JIT Packagers Node fields

Name Description Default

Status Indicates current RM connectivity status to the JIT Packager. One of

Name Specifies the name the RM will use when referencing the JITP. When

IP Address Specifies the IP address of the JITP. Empty

n/a

icons will be displayed here:

two

Green checkmark — RM has good connectivity with the JITP

Red “X” — JITP

connectivity.

setting this parameter, use a unique name.

Click this button to add a new entry. n/a

Click this button next to an entry you wish to delete. n/a

Click this button to modify parameters for an existing entry. n/a

is in the RM’s database, but there is no current

Empty

Note: When adding a new JITP to RM’s database, the JITP’s database will be reset so that RM can

configure JITP from an empty database with default values. This process may take a few minutes.

PlaylistLoadBalancer

The Playlist Load Balancer (PLLB, also referred to as TLB) container allows you to add a Telurio Load Balancer that will load balance requests across JITP instances.

To view the Playlist Load Balancer container, navigate to:

cDVR User Guide, Release 2.0 63

Configuration - Nodes Sub-tab

Default

Populated

Configuration  Nodes  Playlist Load Balancer  [expand]

ConfiguringaPLLB

You can add( ), modify ( ), or delete ( ) a PLLB from this menu, using Table 12 below for guidelines.

Table 12 describes the fields in the Playlist Load Balancer nested container.

Table 13. PLLB Node fields

Name Description Default

Status Indicates current RM connectivity status to the PLLB. One of two

will be displayed here:

Green checkmark — RM has good connectivity with the PLLB

Red “X” — PLLB

connectivity.

Name Specifies the name the RM will use when referencing the PLLB. When

setting this parameter, use a unique name.

Primary Status Indicates connectivity status between RM and the Primary PLLB. Empty

Primary IP Address Specifies the IP address of the Primary PLLB. Empty

Click this button to add a new entry. n/a

Click this button next to an entry you wish to delete. n/a

is in the RM’s database, but there is no current

icons

n/a

Empty

Click this button to modify parameters for an existing entry. n/a

cDVR User Guide, Release 2.0 64

Configuration - Nodes Sub-tab

Default

Populated (Direct)

Note: When adding a new PLLB to RM’s database, the PLLB’s database will be reset so that RM can

configure from an empty database with default values. This process may take a few minutes.

StorageMountsContainer

The Storage Mounts container provides the ability to specify a file server that will store the HLSv4 mezzanine content generated by Recorder for either EBR or CR. In the case of CR (and optionally EBR), the JITP server will pull content from the storage server in order to prepare and deliver ABR-ready chunks.

For EBR, the JITP server can ingest DASH-TS and HLS V4, or, when not using JITP for EBR, the content can be played back by any media player supported by a Packager.

To view the Storage Mounts container, navigate to:

Configuration  Nodes  Storage Mounts  [expand]

cDVR User Guide, Release 2.0 65

Configuration - Nodes Sub-tab

ConfiguringaStorageMount

You can add( ), modify ( ), or delete ( ) a storage mount from this menu, using Table 14 below for guidelines.

Table 14. Storage Mounts Node fields

Name Description Default

Status Indicates current RM connectivity status to the storage mount. One of two

Name Specifies the name the RM will use when referencing the storage server.

Mount Type Specifies the type of storage server used. Choices are:

URL For NFS access only. Specifies the hostname or IP address and mount

icons will be displayed here:

Green checkmark — RM has good connectivity with the storage mount

Red “X” — storage mount is in the RM’s database, but there is no current

connectivity.

Red checkmark — RM has connectivity to the device, but the device is disabled or otherwise degraded.

When setting this parameter, use a unique name.

NFS — Network File System (common client/server file storage system)

NFS4 — Network File System (common client/server file storage system)

GPFS — no longer supported.

Webdav-Light — HTTP-based.With this setting, Recorders write output to the storage node using HTTP, and JITP nodes will read segment files using HTTP. This eliminates the need to configure and use NFS.

point path of the storage server where content will be stored. Proper format should be as follows:

Two methods of configuration are available for NFS:

Direct NFS access directly via mount. Proper format should be as follows:

[ip addr or hostname]:/[root directory]/[sub-directory]/[directory ..n]

nfs://myhost.domain.com:/ndvr/nfs-1/content

HTTP NFS access the content. Proper format should be as follows:

http://[ip addr or hostname]/[directory]/

http://10.32.128.200/ndvr/content

Note: for GPFS, this field is autopopulated with the mount path once a GPFS node is added.

: In this case, the JITP server accesses the content

or Webdav-Light access: In this case, the JITP uses HTTP to

Blue dots

Empty

cDVR User Guide, Release 2.0 66

Configuration - Nodes Sub-tab

Table 14. Storage Mounts Node fields

Name Description Default

Origin Base URL For NFS access only. Specifies the base URL that will be used for

Used Indicates the amount of space (in Gigabytes) in use on the NFS server.

Capacity Indicates the amount of space (in Gigabytes) available for use on the

Empty

access to the storage mount.

Two types of URLs available for NFS:

Direct NFS access: This field is autopopulated for direct NFS access. Do not enter any data in this field. Proper format will be displayed as follows:

nfs://[ip addr or hostname]:/[root directory]/[sub-directory]/[directory ..n]

myhost.domain.com:/ndvr/nfs-1/content

HTTP NFS or Webdav-light access: If HTTP access to the storage mount is different from the entry in the URL field, a different URL may be added here. If the URL and Origin Base URL use the same URL, entry in this field is optional. Proper format to use for HTTP access is as follows:

http://[ip addr or hostname]/[directory]/

http://10.32.128.200/ndvr/content

Blank

This number is auto-populated once the RM has established connectivity to the NFS.

NFS server. This number is auto-populated once the RM has established connectivity to the NFS and is automatically refreshed at regular polling intervals.

Click this button to add a new entry. n/a

(autopopulated)

Blank (autopopulated)



Click this button next to an entry you wish to delete. n/a

Click this button to modify parameters for an existing entry. n/a

RecordersContainer

The Recorders container allows you to set up one or more Recorder devices that will be used to record MBR IDR streams (from the transcoder) and create the HLSv4 mezzanine format for storage and delivery to a JITP server.

Caution: If you are using RM node-redundancy for your system, you must first configure redundancy

for the RM’s before adding any Recorders to this container. Refer to

Redundancy Setup”

for instructions.

To view the Recorders container, navigate to:

Chapter 4, “RM

cDVR User Guide, Release 2.0 67

Configuration - Nodes Sub-tab

Default

Populated (redundant shown)

CONFIGURATION  NODES  Recorders  [expand]  [expand on Recorder row entry]

ConfiguringaRecorder

You can add( ), modify ( ), or delete ( ) a storage mount from this menu, using Table 15 below for guidelines.

Table 15. Recorders Node fields

Name Description Default

Status

(For Recorder container group)

Name Specifies the name the RM will use when referencing the Recorder(s).

Storage Specifies which storage server to use for the Recorder group.

HLS Version Specifies the HLS version that the Recorder will use for creating the

Indicates current RM connectivity status to the Recorder. One of two

icons will be displayed here:

Green checkmark — RM has good connectivity with the Recorder

Red “X” — Recorder is in the RM’s database, but there is no current

connectivity.

Red checkmark — RM has connectivity to the device, but the device is disabled or otherwise degraded.

When setting this parameter, use a unique name.

Whatever was configured from the Configuration > Nodes > Storage Mounts container will be displayed here in a drop-down box.

storage mezzanine format. Choose from either HLSv2 or HLSv4.

Note: HLSv4 should be used for this version of software.

n/a

Empty

None Selected

cDVR User Guide, Release 2.0 68

Configuration - Nodes Sub-tab

Table 15. Recorders Node fields

Name Description Default

Primary Status Indicates the operational status of the Primary Recorder. One of three

Primary IP Address Specifies the IP address of the Recorder. Empty

Redundant Status Indicates the operational status of the redundant Recorder (if it has

Redundant IP Address

n/a

status indications will be displayed:

OK - Good connectivity, Recorder is operational

SET FAILURE - No connectivity, Recorder is disabled

DISABLED - There is connectivity, but Recorder is disabled for another reason.

n/a

been configured). One of three status indications will be displayed:

OK - Good connectivity, Recorder is operational

SET FAILURE - No connectivity, Recorder is disabled

DISABLED - Recorder is disabled due to either no redundant node being configured or another type of redundancy failure.

Specifies the IP address of the redundant Recorder. Recorder redundancy is enabled as soon as the redundant IP address is configured and connectivity is established.

Note: To add another non-redundant Recorder, click the “+” icon in the table and add a new node.

Click this button to add a new entry. n/a

Empty

Click this button next to an entry you wish to delete. n/a

Click this button to modify parameters for an existing entry. n/a

Note: When adding a new Recorder to RM’s database, the Recorder’s database will be reset so that RM

can configure it from an empty database with default values. This process may take a few minutes.

Record‐levelRedundancy

In record-level redundancy, a Primary and Redundant Recorder are configured to provide active-muted redundant recording from the RM. Both Recorders are concurrently recording content received from the transcoder, but only one recording at a time is written to the storage server for JITP delivery. If a Recorder fails to write content to the storage server, then the redundant Recorder will pick up in its place and continue to write the content to the storage server.

Note: A Recorder is a Packager that is licensed for recording. When you configure the Recorders tab in

the RM, you are in effect configuring a specific type of package on a Packager.

In essence, record-level redundancy from the RM works in the same manner that package-level redundancy works on a Packager, with one exception: in record-level redundancy, the Recorders are not writing content to the storage server at the same time; rather, they are recording content at the same time, but only one Recorder writes the content to disk at a time.

Master/SlaveBehavior

In record-level redundancy, reference timing control is based on a first-come first-serve basis. The redundant recording that starts first effectively becomes the ‘master’ record, on which the ‘slave’

cDVR User Guide, Release 2.0 69

Configuration - Nodes Sub-tab

Default

Populated (redundant shown)

recording will base its PTS timing, segment number, encryption key, and various other points of reference. If the master fails, the slave begins writing its recording to disk in addition to becoming the new master on which the old master will base its reference timing if and when it recovers. The same behavior ensues for a slave recording that is manually stopped (rather than having stopped due to network error or outage).

HardwareandNetworkingRequirements

Since Recorder is an extension of a Packager, the hardware and networking requirements for recordlevel redundancy are the same as for package-level redundancy. Please refer to the section titled,

“Package-level Redundancy” in Chapter 6 of the Te lur io information on hardware and networking requirements.

BJMHostsContainer

The BJM Hosts container allows you to set up one or more Private Copy Engine (PCE) nodes that will manage replication and delete processes of private copy.

Caution: If you are using RM node-redundancy for your system, you must first configure redundancy

for the RM’s before adding any BJMs to this container. Refer to

Setup”

for instructions.

Packager User Guide, Release 5.9 for

Chapter 4, “RM Redundancy

To view the BJM Hosts container, navigate to:

CONFIGURATION  NODES  BJM Hosts  [expand]  [expand on BJM row entry]

cDVR User Guide, Release 2.0 70

Configuration - JITP/Recorder Sub-tab

ConfiguringaBJM

You can add( ), modify ( ), or delete () a BJM from this menu, using Table 1 5 below for guidelines.

Table 16. Recorders Node fields

Name Description Default

Status

(For Recorder container group)

Name Specifies the name the RM will use when referencing the BJM host.

IP Address Specifies the IP address of the BJM.

Storage Specifies which storage server to use for the BJM group. Whatever was

Max Load Specifies number of simultaneous asset copy sessions.

Current Load Indicates the current number of sessions for the BJM. n/a

Current Copy Ops Shows the number of private copy asset copy jobs currently in progress

Current Delete / Optimize Ops

Indicates current RM connectivity status to the BJM. One of two will be displayed here:

Green checkmark — RM has good connectivity with the node

Red “X” — Node is in the RM’s database, but there is no current

connectivity.

Red checkmark — RM has connectivity to the device, but the device is disabled or otherwise degraded.

When setting this parameter, use a unique name.

configured from the Configuration > Nodes > Storage Mounts container will be displayed here in a drop-down box.

Default is set to -1, which is an unlimited number of sessions.

on the BJM.

Shows the number of private copy asset delete or optimization jobs currently in progress on the BJM.

Click this button to add a new entry. n/a

icons

n/a

Empty

None Selected

-1

n/a

Click this button next to an entry you wish to delete. n/a

Click this button to modify parameters for an existing entry. n/a

JITP/RecorderSub‐tab

The JITP/RECORDER sub-tab is accessed by clicking through to CONFIGURATION > JITP/RECORDER. From this menu you can configure global packaging / recording parameters for the JITP servers and Recorders in the RM’s cluster.

This section provides an overview of each container in the JITP/RECORDER sub-tab and describes its GUI parameters.

• Key Server Container — Applies to both JITP and Recorder

• Audio Map Container — Applies to both JITP and Recorder

• Profile Container — JITP Only

• Source Server Container — JITP Only

cDVR User Guide, Release 2.0 71

Configuration - JITP/Recorder Sub-tab

Default

Populated

KeyServerContainer

The Key Server container allows you to set up one or more key servers to manage encryption keys between the JITP or Recorder and the client player. When a key server is configured in this menu, it will be applied to all JITP servers and Recorders within the RM cluster. Whether or not the key server is used for a particular package or recording depends on how an individual channel is configured (see

“Channels sub-tab fields” on page 85 for more information on configuring key servers for channels).

To view the Key Server container, navigate to:

CONFIGURATION  JITP/RECORDER  Key Server  [expand]

ConfiguringaKeyServer

You can add( ), modify ( ), or delete ( ) a key server from this menu, using Ta b le 17 below for guidelines.

Table 17. Key Server Node fields

Name Description Default

Key Server Vendor Specifies which key server vendor to add. Choices from the drop-down

menu are:

None, Verimatrix HLS, Nagra Irdeto, Internal PlayReady, KPN, PlayReady Leaf, Irdeto Flash Access, Irdeto Fairplay, Irdeto Widevice, Conax GoLive, and Irdeto PlayReady

Key Server URL Specifies the URL where the key server is running. Proper format is:

http://[domain]/[subdirectory]/...

Applies to: Verimatrix HLS, Nagra, Internal HLS, Verimatrix PlayReady, Irdeto, KPN, PlayReady Leaf, Irdeto Flash Access, Irdeto Fairplay, Irdeto Widevine, Conax GoLive, and Irdeto PlayReady.

cDVR User Guide, Release 2.0 72

, Internal HLS, Verimatrix PlayReady,

Verimatrix HLS

Empty

Configuration - JITP/Recorder Sub-tab

Table 17. Key Server Node fields

Name Description Default

Port Specifies the port number under which the Key Server is running for the

Key Server URL.

Valid range is 0 - 65535.

Only applies to: Verimatrix HLS, Nagra, Verimatrix PlayReady, and KPN

Note: If leaving this value at 0, the default port of 80 will be used for HTTP and 443 will be used for HTTPS.

Client Key Request URL

Specifies the URL for the client to use when authenticating with the key server. Maximum of 1024 characters.

Only applies to: Internal PlayReady Internal Flash Access, Irdeto Fairplay, Irdeto Widevine, and Irdeto PlayReady.

Client Certificate Specifies the HTTP or TFTP URL to download for the client certificate

file. Maximum of 1024 characters.

Only applies to: PlayReady Leaf

Client Key Specifies the HTTP or TFTP URL to download for the client certificate

file. This field only applies if the certificate is a PFX file (PKCS 12) or a .PEM file (certificate file). If a .PFX file is entered, leave the Client Key field blank as the key will be automatically extracted from the file. Maximum of 1024 characters.

Only applies to: PlayReady Leaf

Client Key Password

Specifies the PlayReady Leaf client password. This field only applies if the Client Certificate field is a .PEM file (certificate file), in which case the Client Key must be manually entered here. Maximum of 1024 characters.

Only applies to: PlayReady Leaf

PlayReady Key Seed

Specifies the PlayReady key seed to use when using an Internal PlayReady key server.

Valid range is 30 - 512 characters.

Only applies to: Internal PlayReady

User Name Specifies the username for logging into the key server.

Only applies to: KPN, Internal Flash Access, Irdeto Fairplay, Irdeto Widevine, Conax GoLive, and Irdeto PlayReady.

Password Specifies the password for logging into the key server.

Only applies to: KPN, Internal Flash Access, Irdeto Fairplay, Irdeto Widevine, Conax GoLive, and Irdeto PlayReady. Irdeto Widevine,

Account ID Specifies the Account ID to use for the key server.

Only applies to Internal Flash Access, Irdeto Fairplay, and Irdeto PlayReady.

Registration User Name

Enter the user name for content registration.

Only applies to Internal Flash Access, Irdeto Fairplay, and Irdeto PlayReady.

Registration Password

Enter the password for content registration.

Only applies to Internal Flash Access, Irdeto Fairplay, and Irdeto PlayReady.

Flash Access

For IrdetoFlashAccess only. Empty Server Transport Certificate

Empty

cDVR User Guide, Release 2.0 73

Configuration - JITP/Recorder Sub-tab

Table 17. Key Server Node fields

Name Description Default

Flash Access Server Certificate

Flash Access Policy File

Packager Credential

Packager Credential Password

a. This option is only available for use with HLSv2, which is a beta-only feature for this release.

For IrdetoFlashAccess only. Empty

Click this button to add a new entry. n/a

Click this button next to an entry you wish to delete. n/a

Click this button to modify parameters for an existing entry. n/a

AudioMapContainer

The Audio Map container implements Packager’s late-binding audio feature, which allows for the inclusion of one or more alternative audio tracks to be published within a single recording. Audio map rules determine how (or if) content audio tracks are published by evaluating each input audio track against a set of user-defined rules. Having audio map rules allows for delivery protocols to adjust for variations in audio language and quality based on the client device’s parameters and bandwidth capacity.

The Audio Map container is configured in two steps:

1. Create an audio map template

2. Add rules to the audio map template

AudioMapTemplateNames

Before you can add an audio map rule, you must first create an audio map template name.

To view the Audio Map container for template names, navigate to:

cDVR User Guide, Release 2.0 74

Configuration - JITP/Recorder Sub-tab

Default (template name)

Populated (template name)

CONFIGURATION  JITP/RECORDER  Audio Map  [expand]

ConfiguringanAudioMapTemplate

You can add( ), modify ( ), or delete ( ) an audio map template from this menu, using

Table 18 below for guidelines.

Table 18. Audio Map container fields - template name

Name Description Default

Name Specifies the name of the audio map template. This field can be up to

23 alphanumeric characters long.

Note: Once the Name has been saved to the RM database, it cannot

be modified. If you wish to change the name, you must delete the entry

and add a new one.

Click this button to add a new entry. n/a

Click this button next to an entry you wish to delete. n/a

Click this button to modify parameters for an existing entry.

Note: If the specified audiomap is in use by an active recording, this

field cannot be modified until the recording is complete or stopped.

Empty

n/a

AudioMapRules

After creating an audio map template, up to 8 rules may be defined for each template. A rule consists of several configurable input audio conditions that, when met, will produce a specified output audio publishing option as described in

cDVR User Guide, Release 2.0 75

Table 20 on page 78.

Configuration - JITP/Recorder Sub-tab

Add New Rule

Populated

Audio map rules are applied on an exclusive basis, which means that once the rule conditions are met for the highest priority rule, no further rules are processed for the matching input audio track.

Note: Since audio map rules are applied exclusively based on highest priority rule match, the rule

priority should be set with the most specific audio characteristics as the highest, and each less specific characteristic (more generic) as subsequently lower priorities.

Caution: The Recorder and JITP servers do not support segmentation for multiple audio tracks where

the language code, codec, and bitrate are identical. That is, each audio input track being fed to nodes of the same content must be unique, either in language, code, or bitrate. If such identical audio input tracks are fed to the Recorder and JITP, cDVR will not work correctly, which can result in “Out-of-Sync” messages and incorrect audio track publishing.

To view the Audio Map container for rules, navigate to:

Configuration  JITP/Recorder  Audio Map  [expand]  [expand Audio Map name]

cDVR User Guide, Release 2.0 76

Configuration - JITP/Recorder Sub-tab

ConfiguringanAudioMapRule

You can add( ), modify ( ), or delete ( ) an audio map rule from this menu, using

Table 19 below for guidelines.

Table 19. Audio Map container fields - rule

Name Description Default

Priority Sets the order in which rules are evaluated against the audio input

tracks, 1 being the first (or highest priority) and 8 being the last (or

lowest). Once a rule matches an audio track, no subsequent rules will

be evaluated.

Note: Priority should be configured from most specific audio

characteristics (highest priority) to least specific audio characteristics

(lower priority).

Note: Once the Rule has been saved to the RM database, it cannot be

modified. If you wish to change the parameters or priority level, you

must delete the entry and add a new one.

Audio Codec Specifies the input codec to which this rule will apply. Options from the

drop-down menu are:

• Any (rule will apply for any audio codec provided it matches all other

• AAC-LC — Advanced Audio Coding Low-Complexity

• AAC-HE — Advanced Audio Coding Low-Complexity + SBR

• Dolby Digital (AC-3)

• AAC-HEv2 — Advanced Audio Coding Low-Complexity + SBR + PS

• Dolby Digital Plus (E-AC-3)

Audio Channel Select the number of input channels to which this rule will apply.

Options are:

• Any (rule will apply for any number of audio channels provided it

•Mono

•Stereo

• 5.1 Surround

Bitrate Low Enter the lowest input audio bit rate for which the rule will apply.

Acceptable value is any number between 0 and 640000 bps.

Note: If you want the rule to apply to an input track of any bit rate range,

enter 0 here and 640000 in the Bitrate High field.

Bitrate High Enter the highest input audio bit rate for which the rule will apply.

Acceptable value is any number between 8000 and 640000 bps.

Note: If you want the rule to apply to an input track of any bit rate range,

enter 640000 here and 0 in the Bitrate Low field.

Language Enter the language of the audio track for which this rule will apply.

• This field may contain only 3 characters and must comply to the

• The code “any” is a valid entry option and will apply the rule to an

Video Bitrate Low Enter the minimum video bitrate that the track can be played at.

Acceptable range is 0 to 25000000 bps.

For HLS tracks, add a margin for fluctuations.

conditions)

matches all other conditions)

ISO639-2

audio track of any language.

language code standard.

Any

Empty

any

cDVR User Guide, Release 2.0 77

Configuration - JITP/Recorder Sub-tab

Table 19. Audio Map container fields - rule

Name Description Default

Video Bitrate High Specifies the maximum video bitrate that the track can be played at.

Acceptable range is 0 to 25000000 bps.

For HLS tracks, add a margin for fluctuations.

Publishing Type Select the type of audio output that will be published when all input

conditions have been met. Choices are: Primary,

Primary+AudioOnly, AudioOnly, Audio Only - Custom, Do Not

Publish.

See

types and how they may vary based on player.

Click this button to add a new entry. n/a

Click this button next to an entry you wish to delete. n/a

Click this button to modify parameters for an existing entry. n/a

100,000,000

Primary

Table 20 on page 78 for a detailed description of these publishing

AudioOutputPublishingOptions

Four types of output publishing options are available when a rule condition is matched. Based on the delivery protocol, each publishing option has a specific behavior.

Note: In order to support multiple audio outputs for Private Copy, you must set the Output Publishing

Type to either Audio Only or Audio Only-Custom.

Table 20. Audio map behavior based on delivery protocol

Output Publishing Type HLS Behavior HDS Behavior MSS Behavior

Primary Matching audio will be

published as the default audio with the video.

Primary + Audio Only Matching audio will be

published as the default audio with video -and- offered as an audio-only feed.

Audio Only Matching audio will be

published by itself as an audio-only feed (no video)

Audio Only - Custom Matching audio will be

published by itself as an audio-only feed (no video) and can only be played by a custom player.

Matching audio will be published as the default audio with the video.

Same as Primary: matching audio will be published as the default audio with the video.

Ignores this rule, and proceeds to next rule for a match. If no match is found, audio is considered alternate.

Table 20 describes each condition:

Matching audio will be published.

Same as primary: matching audio will be

published.

Ignores this rule and pro-

ceeds to next rule for a match.If no match is found, audio is pub-

lished.

Ignores this rule and pro-

ceeds to next rule for a match.If no match is found, audio is pub- lished.

cDVR User Guide, Release 2.0 78

Configuration - JITP/Recorder Sub-tab

Table 20. Audio map behavior based on delivery protocol

Output Publishing Type HLS Behavior HDS Behavior MSS Behavior

Do Not Publish Matching audio will be

dropped at the input and will not appear in any generated output.

No Rule Match Input audio that does not

match any rule will be published as a non- default feed.

ProfileContainer—JITPOnly

The Profile container applies only for JITP servers in the RM cluster, not to Recorders. The Profile container provides the ability to set variables for JITP profile tables that determine whether an output format is allowed for packaging and how that format is handled in terms of segment duration, audio map rules, and key servers.

Matching audio will be dropped at the input and will not appear in any generated output.

Input audio that does not match any rule will be published as an alter- nate feed.

Matching audio will be dropped at the input and will not appear in any generated output.

Input audio that does not match any rule will be published.

Caution: When modifying system values for JITP, the asset cache for all the JITP servers in the RM

clusters will be will be flushed and ongoing playback may fail and need to be restarted. It is advisable to perform these actions only during a scheduled maintenance window.

To view the Profile container, navigate to:

cDVR User Guide, Release 2.0 79

Configuration - JITP/Recorder Sub-tab

Default

Populated

CONFIGURATION  JITP/RECORDER  Profile  [expand]  [expand again]

ConfiguringaProfile

You can add( ), modify ( ), or delete ( ) a player profile from this menu, using Ta b l e 2 1 below for guidelines.

Table 21. Profile container fields - template name

Name Description Default

Name Specifies the name of the profile. This field can be up to 23

alphanumeric characters long.

Note: Once the Name has been saved to the RM database, it cannot

be modified. If you wish to change the name, you must delete the entry

and add a new one.

Type Specifies the output package format for which the JITP settings will

apply. Available types are:

HLS, DASH ISO, and MSS

Segment Duration

Specifies the recording length (in seconds) of each segment for the

specified player.

For HLS, if this field is set to 0, no additional segmentation will be

performed for this package type and the HLS stream will be passed

through as is.

Empty

n/a

Empty

cDVR User Guide, Release 2.0 80

Configuration - JITP/Recorder Sub-tab

Table 21. Profile container fields - template name

Name Description Default

Key Server Specifies which, if any, encryption key server to use. Drop-down box

populates with key servers configured in the Key Server container.

Key Rotation

(minutes)

Audio Map Specifies which audio map template and associated rules to use for the

Video Bitrate Low Enter the minimum video bitrate to publish. For HLS tracks, add a

Video Bitrate High Enter the maximum video bitrate to publish. For HLS tracks, add a

Allowed Specifies whether the package format will be allowed for JIT packaging.

Policy ID Enter Policy ID number Empty

Subcontent Type Enter Subcontent Type Empty

Specifies the duration of time (in minutes) that a particular encryption

key will be used. After the time period expires, a new encryption key will

be required.

Enter 0 or leave blank for no rotation.

player. Drop-down box populates with audio maps configured in the

Audio Map container.

margin for fluctuations.

Valid range is from 0 - n.

margin for fluctuations.

Valid range is from 0 - n.

Choices are yes or no.

Click this button to add a new entry. n/a

Unselected

100000000

false

Click this button next to an entry you wish to delete. n/a

Click this button to modify parameters for an existing entry. n/a

a. The first frame for each fragment is an IDR frame or RAI flag.Therefore, the fragment duration specified with periodic

modes is not an absolute, but a minimum target. The final duration will be based on how far the IDR or RAI frames are from the fragment duration. For example: an IDR periodic fragment duration of 3 seconds with IDRs inbound at a 2 second interval will produce 4-second fragments.

SourceServerContainer—JITPOnly

The Source Server container applies only for JITP servers in the RM cluster, not to Recorders. The Source Server defines where inbound content is stored for JITP.

Caution: When modifying system values for JITP, the asset cache for all the JITP servers in the RM

clusters will be flushed and ongoing playback may fail and need to be restarted. It is advisable to perform these actions only during a scheduled maintenance window.

To view the Source Server container, navigate to:

cDVR User Guide, Release 2.0 81

Configuration - JITP/Recorder Sub-tab

Default

Populated

CONFIGURATION  JITP/RECORDER  Source Server  [expand]

ConfiguringaSourceServer

You can add( ), modify ( ), or delete ( ) a source server from this menu, using Ta b l e 22 below for guidelines..

Table 22. Source Server container fields - template name

Name Description Default

Recording Type Specifies which type of recording for which the Source Server settings

will apply. Choices from the drop-down menu are:

Continuous Recording, Event Based Recording, or Unique Asset

Recording

Pattern Specifies the identifier for the source server that contains the inbound

content for Just-in-Time packaging. It is used to map to a valid

hostname, or a directory ID for a file system mount.

• Can be up to 255 characters (

• Pattern cannot begin or end with a dash

Note: This entry cannot be the management IP address or host name.

Profile Specifies the output package profile for which the JITP settings will

apply. The drop-down list is populated from the Profile container.

a-z, 0-9, - [dash] and . [dot])

Continuous Recording

Empty

Unselected

cDVR User Guide, Release 2.0 82

Configuration - Channels Sub-tab

Channels tab - no channels configured

Table 22. Source Server container fields - template name

Name Description Default

Storage Specifies the storage server for which the Source Server settings will

apply. The drop-down list is populated with the storage devices

configured in the CONFIGURATION > NODES > Storage Mounts

container.

Note: This option is only displayed when Event Based Recording or

Unique Asset Recording is set as the Recording Type.

Click this button to add a new entry. n/a

Click this button next to an entry you wish to delete. n/a

Click this button to modify parameters for an existing entry. n/a

ChannelsSub‐tab

Preselected with first Storage Mount entry

The CHANNELS sub-tab allows you to create or delete channels from transcoded output that the RM will use to schedule recordings; it also provides a snapshot view of all configured channels.

ChannelsSub‐tabTou r

To view the CHANNELS sub-tab, navigate as follows:

CONFIGURATION > CHANNELS.

DefaultView

When you first view this menu, no channels will be configured and the window will appear as follows:

cDVR User Guide, Release 2.0 83

Configuration - Channels Sub-tab

ConfiguredView‐Collapsed

A configured Channels sub-tab will appear similar to the following:

ConfiguredView‐WithStreams

Clicking on the Streams button will open a pop-up window that allows entry of individual streams for a particular channel, similar to what is shown below.

cDVR User Guide, Release 2.0 84

Configuration - Channels Sub-tab

ConfiguringChannelsandStreams

You can add( ), modify ( ), or delete ( ) a channel and its streams from this menu, using

Table 23 below for guidelines.

Table 23. Channels sub-tab fields

Name / Type Description Default

Channel container fields

Name Specifies the name of the channel. This field can be up to 23

Transcoder Specifies which transcoder the channel will use for its input. When

MBR / Group Optional.

Stream container fields (Note: Click the “Streams” button to open the pop-up configuration window)

IP Address Specifies the multicast IP address(es) to which the transcoder is

Port Specifies the UDP (User Datagram Protocol) port of the multicast

Published Video Bitrate

Enabled Specifies whether the selected stream is enabled or disabled for

Empty

alphanumeric characters long.

Note: Once the Name has been saved to the RM database, it cannot be modified. If you wish to change the name, you must

delete the entry and add a new one.

Unselected

in edit mode, the drop-down box is populated with the list of transcoders configured from the CONFIGURATION > NODES > Transcoders container.

Empty

Specifies the name of the VMG’s MBR or another transcoder’s Group ID output transport stream group that will be associated with the channel. This field is for reference only.

Empty

sending its output.

Valid entries are: 224.0.0.1 – 239.255.255.254. Refer to iana.org for details.

Note: If using Source Specific Multicasting (SSM), you must use only this range: 232.0.0.1 – 232.255.255.254.

Empty

source on which the transcoder is sending its output. If the MBR / Group field is used, the IP Address and Port entries will be auto-

populated.

Valid range is 1 – 65535

Specifies the video bit rate at which the transcoded stream is being published. Enter 0 (zero) or leave blank to have RM use the bit rate it detects from the input stream.

channel recording.

Click this button to add a new entry. n/a

True

Click this button next to an entry you wish to delete. n/a

Click this button to modify parameters for an existing entry. n/a

CreatingChannelsandStreams

Creating a channel entails adding a row entry to the Channels sub-tab and configuring the streams within the channel.

cDVR User Guide, Release 2.0 85

Configuration - Schedules Sub-tab

To create a channel, proceed as follows:

1. From the CONFIGURATION > CHANNELS menu, click “+” to open the ADD menu.

2. Fill out the fields according to the descriptions for channels in

3. Click Submit to save and add the channel to the RM database.

4. Click the Streams button for the desired channel row entry.

A pop-up Streams menu will open.

5. Click “+” to open the stream’s ADD menu.

6. Fill out the fields according to the descriptions for streams in

7. Click Submit to save the stream to the RM database.

8. Click “+” in the same Streams pop-up to add additional streams to the channel.

9. Click “+” in the Channels container to add additional channels.

SchedulesSub‐tab

The SCHEDULES sub-tab is where all event based recording (EBR) and continuous recording (CR) is scheduled. From here you can create new recording schedules, check the status of currently scheduled recordings, import and export recording schedules, and perform detailed search queries of all recordings.

Table 23 on page 85.

SchedulesSub‐tabTour

To view the SCHEDULES sub-tab, navigate as follows:

CONFIGURATION > SCHEDULES.

DefaultView

When you first view this menu, no recordings will be scheduled and the window will appear as follows:

cDVR User Guide, Release 2.0 86

Configuration - Schedules Sub-tab

ConfiguredView

A configured SCHEDULES sub-tab will appear similar to the following:

ConfiguringSchedules

You can add( ), modify ( ), or delete ( ) a scheduled recording from this menu, using

Table 24 below for guidelines.

Table 24. Schedules sub-tab fields

Name / Type Description Default

Fields

Status Indicates the current status of the scheduled recording. Refer to

Table 7 on page 46 for definitions.

Input Type Indicates whether the program input originates via Channel or URL.

If the Recorder is ingesting a UDP stream, select Channel.

If the Recorder is ingesting HLSv2, select URL.

Note: URL for JITT will be supported in a future release.

Channel Specifies the name of the channel on which the recording is

scheduled.

When creating a new schedule, a drop-down box of options that were defined in the CONFIGURATION > CHANNELS sub-tab will be displayed.

Input URL Specifies the input URL location.

Only used if Input Type is URL (i.e., the Recorder is ingesting HLSv2)

Recorder Specifies the name of the Recorder on which the recording is

scheduled.

When creating a new schedule, a drop-down box of options that were defined in the CONFIGURATION > NODES > Recorders container will be displayed.

Name (path) Specifies the unique directory path where the recording is placed.

When creating a new schedule, this path must be defined. Valid entries ranges are 1 - 200 alphanumeric characters.

Read-only

Empty

Preselected with first channel configured

Empty

Preselected with first Recorder configured

Empty

cDVR User Guide, Release 2.0 87

Configuration - Schedules Sub-tab

Table 24. Schedules sub-tab fields

Name / Type Description Default

Package Type Specifies the type of package that is recorded.

Audio Map Specifies the name of the Audio Map rules that the recording is

Start Time Specifies the start time of the scheduled recording.

End Time Specifies the end time of the scheduled recording.

Segment Dir. Size (minutes)

When creating a new schedule, choose one of the following from the drop-down box:

• Continuous Record — For all package types where the recording will be CR

EBR Recordings:

• Apple HTTP Live Streaming

• MPEG Dash TS

• RGB Packager Asset

• Adobe HTTP Dynamic Streaming

• Microsoft Smooth Streaming

• Adobe HTTP Dynamic Streaming - HTTP File Format

using.

When creating a new schedule, a drop-down box of options that were defined in the CONFIGURATION > JITP/RECORDER > Audio Map container will be displayed.

When creating a new schedule, an interactive scheduling calendar will pop-up. Refer to

“Scheduling Calendar” on page 90 for usage

guidelines.

Leaving this field empty will start the recording immediately upon clicking the Save icon.

When creating a new schedule, an interactive scheduling calendar will pop-up. Refer to

“Scheduling Calendar” on page 90 for usage

guidelines.

Leaving this field empty will record content with no stop time, i.e., forever, upon clicking the Save icon.

Note: The max length of an EBR is 18 hours. The max length of a CR is only limited to the amount of disk space available on the storage server.

For CR only.

Specifies the duration (in minutes) of each recorded segment directory. For example, if you specify a Segment Duration of 30 minutes, then each segment directory will contain 30 minutes worth of chunked TS files.

When creating a new schedule, this field is optional; if left blank, the numbers specified in the Configuration > Main > Global container are used. Any value entered here will override the defaults from the

Global container.

Unselected

Preselected with first Audio Map configured

Empty

cDVR User Guide, Release 2.0 88

Configuration - Schedules Sub-tab

Table 24. Schedules sub-tab fields

Name / Type Description Default

Max. Unref. Storage (days)

Content ID Specifies a description of encrypted content. This field is used by

Key Server Vendor Specifies which key server vendor will be used for the channel.

Key Rotation

(minutes)

Message Read-only n/a

Buttons

Query Filter

button

Delete Selected

button

Export (CSV)

button

Import (CSV)

button

For CR only.

Empty

Specifies the maximum number of days that an unreferenced CR segment directory (i.e., a segment of a recording that has not been used for asset creation) will be stored before it is automatically deleted.

When creating a new schedule, this field is optional; if left blank, the number specified in the Configuration > Main > Global container is used. Any value entered here will override the defaults from the

Global container.

Empty

some key management servers to identify the content. Example: demo:RC001.

Leave this field empty if no key server is used or if no Content ID for the key server is used.

None

Choices from the drop-down box are:

None, Verimatrix HLS, Nagra

PlayReady, Mezzanine

Specifies the duration of time (in minutes) that a particular

, Verimatrix PlayReady, Internal

, KPN, and PlayReady Leaf.

0 encryption key will be used. After the time period expires, a new encryption key will be required.

Enter 0 or leave blank for no rotation.

Clicking this button will open the Query Filters window in which you

n/a can search and filter an entry based on various parameters

When one or more scheduled recording entries are selected,

n/a clicking this button will delete the selected schedules.

Note: You can select all rows at once to delete all, as shown in

Figure 4 on page 45.

Clicking this button will export the current list of all scheduled recordings to a Comma Separate Value (CSV) list that can be viewed in a program such as Microsoft Excel.

Clicking this button will import a desired list of scheduled recordings to a Comma Separate Value (CSV) list that can be viewed in a program such as Microsoft Excel. Any new schedules from this file will be appended to existing schedules.

Click this button to add a new entry. n/a

Click this button next to an entry you wish to delete. n/a

Click this button to modify parameters for an existing entry. n/a

a. This option is only available for use with HLSv2, which is a beta-only feature for this release.

b. For CR only: A choice of Mezzanine encryption will configure the Recorder to encrypt CR segments stored to disk.

cDVR User Guide, Release 2.0 89

Configuration - Schedules Sub-tab

CreatingaSchedule

To create a new recording schedule, proceed as follows:

1. From the CONFIGURATION > SCHEDULES menu, click “+” to open the ADD menu.

2. Fill out the fields according to the descriptions for channels in

3. Click Submit to save and add the schedule to the RM database.

A new row entry container and its recording status will be added to the SCHEDULES menu.

Table 24 on page 87.

SchedulingCalendar

When creating a new recording schedule or asset, you can specify the start and end time of the EBR or CR. For CR, leaving the start and end times blank will start recording immediately and record indefinitely once the values have been saved. you can leave this field blank to either automatically start the recording once the values have been saved When the Create Schedule or Create Asset window is

cDVR User Guide, Release 2.0 90

Configuration - Schedules Sub-tab

displayed, clicking on the Start Time or End Time field produces an interactive calendar for ease of scheduling:

You can enter start and end times in one of two ways:

• Typing the date and time manually in the relevant fields;

• Clicking the highlighted current date, which will automatically enter the current date and time.

• Clicking on the desired date and using the time slider to the right of the date to adjust start/end

time.

For Continuous Record only:

• In addition to the above three options, if you are scheduling a CR from the SCHEDULES tab,

leaving the start time empty will automatically start the recording as soon as the schedule is saved, and leaving the end time empty will record content indefinitely with no stop time.

Or, you can use a combination of all of the above as suits your needs.

Note: When clicking the current date in order to start the recording immediately, we recommend that

you adjust the time up by one minute in order to ensure the current time does not pass before you save the schedule. For example: if you have scheduled the recording to start at 12:10 PM and the current time is 12:10 PM, if the time changes to 12:11 PM before you save the schedule, you will receive an error that the start time has passed when trying to save the schedule.

ModifyingaRecordingSchedule

You can modify various aspects of a recording schedule depending on whether the recording has begun. To modify a recording schedule, proceed as follows

1. From CONFIGURATION > SCHEDULES, locate the recording you wish to modify and click the

“wrench” icon to modify.

2. If the recording has not yet begun you can modify any field as described in

If the recording has already begun, but not yet ended, the only parameter you can modify is the End Time (refer to the

3. Click Submit to save changes to the RM database.

“Scheduling Calendar” on page 90).

Table 24 on page 87.

cDVR User Guide, Release 2.0 91

Configuration - Schedules Sub-tab

Delete single schedules

Delete all schedules

Delete one or more schedules

DeletingaRecordingSchedule(s)

You can delete one or more recording schedules at any time, regardless of whether the recording has begun.

Note: Deleting a recording schedule does not delete the actual recording. When you delete a schedule

after recording has begun, the recording is effectively stopped.

To delete one or more schedules, you can do one of three things from CONFIGURATION > SCHEDULES tab:

• To delete a single schedule, locate the schedule(s) you wish to delete and click the “trash” icon next

to the row entry.

-or-

• To delete multiple schedules at once, click to check the deletion box next to the row entries you wish

to delete, then click the Delete Selected button. 

-or-

• To delete all schedules, click the selection box at the top of the SCHEDULES window to select all

schedule, then click the Delete Selected button.

cDVR User Guide, Release 2.0 92

Configuration - Event Based Recordings Sub-tab

EventBasedRecordingsSub‐tab

The Event Based Recordings sub-tab provides information about completed EBR programs. From here you can view storage links for recordings. No configuration is performed from this sub-tab; it is for viewing or deleting only.

EventBasedRecordingsSub‐tabTour

To view the Event Based Recordings sub-tab, navigate as follows:

CONFIGURATION > EVENT BASED RECORDINGS.

EBR items whose recordings have been completed or are in process will appear in this window. Below is an example:

Table 25 describes the fields and buttons in the Event Based Recordings sub-tab.

Table 25. Scheduler sub-tab fields

Name / Type Description

Channel Name Displays the name of the recorded channel.

Start Time Displays when the recording started.

End Time Displays when the recording ended.

URL Displays the path, on the storage server, where the recording stream can be found.

Package Type

Delete Selected

button

Query Filter

button

Displays the type of EBR package that has been recorded. One of the following options will be displayed in this column:

• Apple HTTP Live Streaming

• MPEG Dash TS

• RGB Packager Asset

• Adobe HTTP Dynamic Streaming

• Microsoft Smooth Streaming

• Adobe HTTP Dynamic Streaming - HTTP File Format

When one or more recorded entries are selected, clicking this button will delete the recording from the storage server.

Note: You can select all rows at once to delete all as shown in

Clicking this button will open the Query Filters window in which you can search and filter an entry based on various parameters.

Figure 4 on page 45.

a. In order to record a particular Package Type, the Recorder(s) must have the proper Package Type licensing.

cDVR User Guide, Release 2.0 93

Configuration - Event Based Recordings Sub-tab

UsingtheEBRURLtoViewaRecording

You can use the URL provided in the Event Based Recording sub-tab to view a recording on a media player that supports the package type. To view the event based recording using the URL, do one of the following:

• For links with HTTP in the URL (and no Mezzanine encryption), the URL provided in the tab can be

used as is.

• For links with NFS in the URL (or with Mezzanine encryption), the URL can be viewed from the JITP

server, and the link must be modified as follows:



http://[JITP Source Server Pattern]/[schedule name]/index.[manifest type]

 For example:

http://ndvr-jitp3.lab.ripcode.com/dec22/testeb1/index.m3u8

Note: When using MSS as an output format, a “/Manifest” must be added to the “index.isml” portion as

follows: index.ism/Manifest

DeletingaRecording(s)fromRM

You can delete recordings from the RM’s database.

Note: Deleting a recording from the RM’s database does not delete the recording from the storage

server; it only deletes the reference from the database. To delete a recording form the storage server, you must delete the relevant files directly from the storage server.

To delete one or more recordings from the RM’s database, proceed as follows:

cDVR User Guide, Release 2.0 94

Configuration - Shared Assets Sub-tab

Delete single recordings

Delete all recordings

1. From Configuration > Event Based Recording, locate the recording(s) you wish to delete and

click the selection box next to the row entry.

Or, if you want to delete all schedules, click the selection box at the top of the Scheduler window.

2. Click the Delete button.

3. Confirm the deletion message by clicking OK.

SharedAssetsSub‐tab

The Shared Assets sub-tab is where you can create viewable shared assets from segments that have been or are in the process of being continuously recorded.

Prerequisite

Prior to creating a CR asset, you must have first created a recording schedule for the intended asset as described in

SharedAssetsSub‐tabTou r

To view the Shared Assets sub-tab, navigate as follows:

Configuration > Shared Assets.

“Schedules Sub-tab” on page 86.

cDVR User Guide, Release 2.0 95

Configuration - Shared Assets Sub-tab

DefaultView

When you first view this menu, no assets will be listed and the window will appear as follows:

ConfiguredView

A configured SHARED ASSETS sub-tab can look like this:

ConfiguringSharedAssets

You can add( ), modify ( ), or delete ( ) an asset from this menu, using Table 26 below for guidelines.

Table 26. Shared Assets sub-tab fields

Name / Type Description Default

Fields

Status Indicates the current status of the scheduled CR assets. One of four

status icons will be displayed. Refer to definitions.

Asset Key Specifies the unique directory path under which the asset is placed.

When creating a new asset, this path must be defined. Valid entries ranges are 1 - 200 alphanumeric characters.

Asset Type Specifies whether the asset will be shared (one recording available

for all subscribers) or unique (one unique recording for each requesting subscriber). Choices are:

SHARED

Table 7 on page 46 for

Read-only

Empty

Shared

cDVR User Guide, Release 2.0 96

Configuration - Shared Assets Sub-tab

Table 26. Shared Assets sub-tab fields

Name / Type Description Default

Schedule Specifies the name of the schedule from which the asset is being

Content ID If the CONFIGURATION > JITP/RECORDER > Profile container

Start Time Specifies the start time of the created asset.

End Time Specifies the end time of the created asset.

URL Displays the path, on the JITP server, where the asset stream can

Asset Max Age Specifies the absolute number of days before an asset (associated

Buttons

Query Filter

button

Export (CSV)

button

Import (CSV)

button

created.

When creating a new asset, a drop-down box of options that were defined in the CONFIGURATION > SCHEDULE sub-tab will be

displayed

was configured to use a key encryption server, the value here specifies the Content ID that the asset will use for encryption by the JITP server.

This field is alphanumeric.

When creating a new asset, an interactive scheduling calendar will pop-up. Refer to

“Scheduling Calendar” on page 90 for usage

guidelines.

Note: In order for an asset to be created, the CR segments must either be present or scheduled to be present for the asset’s start / end time range. For example, assume you have created a CR schedule on the channel named Disney from the present day at 1:00 PM to the following day at 1:00 PM. If you attempt to create an asset from this recording that starts or ends outside of this range (starting or ending, for example, at 12:00 PM on the present day), the asset will fail to be created.

When creating a new schedule, an interactive scheduling calendar will pop-up. Refer to

“Scheduling Calendar” on page 90 for usage

guidelines.

Note: The max length of a CR is only limited to the amount of disk space available on the storage server.

be found.

with segment directories) is deleted.

Value range: 1 - 40000

The value set here will override the value set in Configuration > Global (see

“Assets Container” on page 58) for this particular

shared asset.

Clicking this button will open the Query Filters window in which you can search and filter an entry based on various parameters.

Clicking this button will export the current list of all assets to a Comma Separate Value (CSV) list that can be viewed in a program such as Microsoft Excel.

Clicking this button will import a desired list of assets to a Comma Separate Value (CSV) list that can be viewed in a program such as Microsoft Excel. Any new assets from this file will be appended to existing assets.

NOTE: If the start time of the asset occurs in the past, the asset will not be imported.

First

schedule in

table

Unselected

Empty

Read-only

n/a

cDVR User Guide, Release 2.0 97

Configuration - Shared Assets Sub-tab

Table 26. Shared Assets sub-tab fields

Name / Type Description Default

Delete Selected

button

a. When creating a new asset from a newly created schedule, you must refresh the browser in order to populate the

Schedule drop-down box with the new schedule.

CreatingaSharedAsset

To create a new shared asset, proceed as follows:

When one or more asset entries are selected, clicking this button will delete the selected asset(s).

Note: You can select all rows at once to delete all as shown in

Figure 4 on page 45.

Click this button to add a new entry. n/a

Click this button next to an entry you wish to delete. n/a

Click this button to modify parameters for an existing entry. n/a

From the CONFIGURATION > SHARED ASSETS menu, click “+” to open the ADD menu:

1. Fill out the fields according to the descriptions for channels in

Table 26 on page 96.

cDVR User Guide, Release 2.0 98

Configuration - Shared Assets Sub-tab

2. Click Submit to save and add the asset to the RM database.

A new row entry container and its recording status will be added to the SHARED ASSETS menu.

SchedulingCalendar

Refer to “Scheduling Calendar” on page 90 for instructions on using the SHARED ASSETS Scheduling Calendar.

ModifyingaSharedAsset

In this release, only the end time can be modified once a shared asset has been created. In order to change other parameters, you must delete the shared asset.

DeletingaSharedAsset(s)

You can delete one or more shared assets at any time.

Note: Deleting a shared asset does not delete the asset from the storage server; it only deletes the

reference to the recorded segments. Continuous Record assets can only be automatically deleted by the RM according to the parameters set up from either the GLOBAL CONFIG tab or for the individual asset.

To delete one or more assets from the RM, you can do one of three things from the CONFIGURATION > SHARED ASSETS tab:

• To delete a single shared asset, locate the schedule(s) you wish to delete and click the “trash” icon

next to the row entry.

-or-

• To delete multiple shared assets at once, click to check the deletion box next to the row entries you

wish to delete, then click the Delete Selected button. 

-or-

• To delete all shared assets, click the selection box at the top of the SHARED ASSETS window to

select all assets, then click the Delete Selected button.

cDVR User Guide, Release 2.0 99

Configuration - Shared Assets Sub-tab

Delete single asset

Delete all assets

Delete one or more assets

UsingtheSharedAssetsURLtoViewaRecording

You can use the URL provided in the Shared Assets sub-tab to view a completed or in-progress shared asset on a media player that supports the package type. To view the asset on a media player using the URL, you will need to modify the provided URL as follows (depending on whether encryption is being used):

For links where no Mezzanine encryption is used and HLS is the desired output format, one of two options is available:

• Copy the relevant link as shown in the SHARED ASSETS tab and paste it into a media player

• Use the following format:

-Or-

2. When content is recorded using direct NFS access instead of HTTP access, you must formulate the link using the JITP source server pattern.

cDVR User Guide, Release 2.0 100

Imagine CloudXtream User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Notice

Trademarks

Patents

Introduction

Recorder

Prerequisites

Overview

Prerequisites

Prerequisites

• RM GUI Hierarchy

Dashboard

Configuration

System

Reports

Dashboard

Icons

Hardware

Events

Configuration

Overview

• Segments Container

• Transcoders Container

To view the Playlist Load Balancer container, navigate to:

Prerequisite