Cisco Virtualized Video Processing Controller Integration Guide

Brand: Cisco

Model: Virtualized Video Processing Controller

Type: Integration Guide

Cisco Virtualized Video Processing Controller Ver 3.2 Integration

Guide

First Published: 2016-11-01

Americas Headquarters

Cisco Systems, Inc.

170 West Tasman Drive

San Jose, CA 95134-1706

USA

http://www.cisco.com

Tel: 408 526-4000

800 553-NETS (6387)

Fax: 408 527-0883

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,

INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,

EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH

THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,

CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS.

CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF

MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT

LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS

HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network

topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional

and coincidental.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://

www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership

relationship between Cisco and any other company. (1110R)

CHAPTER 1

Introduction

This chapter provides information on the Cisco Virtualized Video Processing Controller (V2PC) product

and this Deployment Guide.

•About This Guide, page 1

•Product Overview, page 1

About This Guide

This guide describes how to integrate V2PC with Cisco ROSA Video Service Management (VSM), Cisco

Virtual Digital Content Manager (vDCM), and Cisco Virtual Media Recorder (VMR). This guide can be used

as a reference; step-by-step configuration is available in the later sections.

For detailed information on the V2PC configuration and deployment, refer to the Cisco Virtualized Video

Processing Controller User Guide and Cisco Virtualized Video Processing Controller Deployment Guide .

Product Overview

V2PC provides an open platform, that transforms the way video infrastructure is built, deployed, provisioned

and maintained. V2PC enables a video processing application to run over a cloud or on-premise infrastructure

with flexible workflow and resource orchestration.

Customers can rapidly create and orchestrate video workflows across video headends and data center

environments, and seamlessly evolve from a hardware based infrastructure to a hybrid or pure virtualized

cloud infrastructure. The software centric workflows increase the reachability of content across a variety of

content consumption platforms. This transformation has resulted in flexible user experiences, and simplified

operations, allowing customers to better manage, modify, and scale video workflows to support services such

as Live, VOD, Time Shift, and, Cloud DVR to OTT consumers.

Cisco Virtualized Video Processing Controller Ver 3.2 Integration Guide

Introduction

Product Overview

CHAPTER 2

Integrating ROSA VSM

ROSA Video Service Management (VSM) is a part of ROSA and supplies a complete, powerful solution

for the management of digital content delivery platforms for:

•Broadcast over satellite.

•Terrestrial

•DSL

•Cable networks

•Mobile TV

ROSA VSM supports a diverse range of applications, including switched digital broadcast, primary

distribution, contribution, and, transmission.

ROSA VSM delivers a complete video network management solution. VSM's set of tools can monitor and

manage digital video, audio, and applications, and the devices through which these services flow.

•Installing the ROSA VSM Application, page 3

•Adding and Activating the ROSA VSM Instance, page 3

Installing the ROSA VSM Application

To integrate ROSA VSM, the cisco-vsm application must be deployed in the V2PC master. For more

information about how to install applications, refer to the Cisco Virtualized Video Processing Controller User

Guide.

Adding and Activating the ROSA VSM Instance

Adding the ROSA VSM instance is done by following the steps shown below:

•Step 1 - Create CentOS based workers.

•Step 2 - Instance Info

Assign the following information:

Cisco Virtualized Video Processing Controller Ver 3.2 Integration Guide

◦Name—Specify a unique name for the ROSA VSM instance.

◦Description—Optional

◦Provider—Choose VMWare.

◦Zone—Choose the desired zone.

◦Image—Choose a V2PC CentOS image.

•Step 3 - VSMServer Details

Specify the following information:

◦Start—Keep the default value (Yes)

◦Config Path—Keep the default path (/opt/cisco/vsm/config/myconf.cfg)

◦Resource SLA

◦Min Node—Keep the default value (1). Typically, only one ROSA VSM server is required

in the system.

◦Max Node—Keep the default value (10)

◦Image Flavor Info

◦Image Flavor Group—Choose default-img-flavors

◦Image Flavor Name—Choose the image flavor that matches the node that you want to

allocate for this ROSA VSM application. The minimum image flavor for the ROSA VSM

application is large.

The procedure to add and to enable instances is described in the Cisco Virtualized Video Processing

Controller User Guide.

Cisco Virtualized Video Processing Controller Ver 3.2 Integration Guide

Integrating ROSA VSM

Adding and Activating the ROSA VSM Instance

CHAPTER 3

Integrating vDCM

The Cisco Virtual Digital Content Manager (vDCM) is a virtualized and software-based video processing

platform, providing advanced video, audio, and metadata processing for live multiformat video delivery.

vDCM is implemented as a set of virtualized video functions on a cloud-based network functions virtualization

infrastructure. vDCM provides two applications, the vDCM Video Processing (VP) App and the vDCM

OTT App.

The vDCM VP App supports premium picture quality, statistical multiplexing (statmux), multiplexing,

transcode, and so on. The vDCM OTT App supports multiscreen transcoding.

In an application with vDCM VP Apps and vDCM OTT Apps, ROSA VSM monitors the apps and handles

the appropriate device pools. For ABR channel creation using the vDCM OTT App, the xCode Media Flow

Controller interacts with ROSA VSM and VSM handles the node allocation, provisioning, and backup

control. Therefore, integrate ROSA VSM before attempting the integration procedure for the vDCM VP

App or vDCM OTT App, See Integrating ROSA VSM, on page 3.

•Setting up a Network with vDCM VPA and vDCM OTT, page 5

•Integrating vDCM Video Processing App, page 6

•Integrating vDCM OTT App, page 9

•Troubleshooting, page 15

Setting up a Network with vDCM VPA and vDCM OTT

For a vDCM VPA and vDCM OTT application, the following network setups are possible:

•2-network setup

In this typical setup, two networks are used: a management network and a video network. The V2PC

data-in and data-out network are the same and correspond to the video network.

•3-network setup

In this setup, three networks are defined: one management network, a video input network, and a video

output network. The V2PC data-in network corresponds to video input network. The V2PC data-out

network corresponds to video output network.

Cisco Virtualized Video Processing Controller Ver 3.2 Integration Guide

The networks are set up in the infrastructure provider and zones of the infrastructure provider. In addition, in

the creation of the worker nodes, the IP addresses of the two or three interfaces must be specified. See the

general sections on creating a VMware infrastructure provider, creating a network, and creating a worker

node.

Integrating vDCM Video Processing App

Installing the vDCM Video Processing App

For integrating vDCM VP App instances in V2P Controller, deploy the cicso-vdcm-vp application. Before

you can deploy a vDCM VP application to a set of worker nodes, you must upload the CentOS 7.2 image file

to your VMware environment. This image file is distributed together with the cisco-vdcm packages.

In addition, the vDCM xCoding requires a specific number of CPUs and RAM. Create a custom image flavor

group and the following flavor for vDCM applications:

•56 vCPU –64 GB RAM –50 GB disk, if the underlying hardware is a BM200 M4 with E2697 v3

processors.

•64 vCPU –64 GB RAM –50 GB disk, if the underlying hardware is a BM200 M4 with E2697 v4

processors.

The procedure to upload an image file on a VMware infrastructure, to create custom image flavors, and to

install applications, refer to the Cisco Virtualized Video Processing Controller User Guide.

Adding and Activating the vDCM VPA Instances

The vDCM VPA can take on different roles in your application such as MUX, PROCESSING, and SMX.

The role MUX corresponds to a vDCM VPA with multiplexing and local xCode processing capabilities. The

role PROCESSING corresponds to a vDCM VPA which is configured to do xCode processing only. In this

case, this worker would be associated with another vDCM VPA instance worker node. This association or

binding can be done using the vDCM VPA GUI. The role SMX corresponds to a vDCM VPA which would

be used as a URC statmux controller.

Each of these roles are meant to be exclusive. You enable a role by specifying the Start value to Yes

•Step 1 - Instance Info

Specify the following settings:

◦Name—A unique name for the instance.

◦Description—Optional

◦Provider—VMWare

◦Zone—The desired zone

◦Image—A vdcm image. The image must correspond to the CentOS 7.2 image that is uploaded in

the infrastructure provider.

•Step 2 - MUX Details

Cisco Virtualized Video Processing Controller Ver 3.2 Integration Guide

Integrating vDCM

Integrating vDCM Video Processing App

Specify the following information for multiplexing if needed:

◦Start—Specify Yes

◦Config Path—Keep the default path (/opt/cisco/vdcmvp/mux/config/myconf.cfg)

◦Resource SLA

◦Min Node—The number of instances required for your application. For instance in a 1-1

backup application, specify two.

◦Max Node—Keep the default value (10)

◦Image Flavor Info

◦Image Flavor Group—Choose the name of the group to which the image flavor belongs.

◦Image Flavor Name—Choose the image flavor that matches the nodes to be allocated

by these instances.

vDCM xCoding requires a specific custom image flavor group, See Installing the vDCM

Video Processing App, on page 6.

◦Configuration

◦VSM Control—Enable this parameter if ROSA VSM controls the instances.

◦VSM Instance Name—The name of the ROSA VSM that controls the instances.

◦VSM Region Name—The name of the region to which the ROSA VSM belongs to.

◦VLAN For Data In—If the port for data-in belongs to a VLAN, enable this parameter and

specify the VLAN ID.

◦VLAN For Data Out—If the port for data-out belongs to a VLAN, enable this parameter

and specify the VLAN ID.

◦Video Source SubNet—For routed SSM traffic, specify the IP address range. For multiple

ranges, separate the ranges by a comma.

The video source subnet settings are used to configure static routes on the video network

interface during the post install of the vDCM applications.

◦Step 3 - PROCESSING Details

Specify the following information for the vDCM VPA if needed:

◦Start—Specify Yes

◦Config Path—Keep the default path (/opt/cisco/vdcmvp/processing/config/myconf.cfg)

◦Resource SLA

◦Min Node—The number of instances required for your application.

◦Max Node—Keep the default value (10)

◦Image Flavor Info

Cisco Virtualized Video Processing Controller Ver 3.2 Integration Guide

Integrating vDCM

Adding and Activating the vDCM VPA Instances

◦Image Flavor Group—Choose the name of the group to which the image flavor

belongs.

◦Image Flavor Name—Choose the image flavor that matches the nodes to be

allocated by these vMFP App instances.

vDCM XCoding requires a specific custom image flavor group, See Installing the vDCM

Video Processing App, on page 6.

◦Configuration

◦VLAN For Data In—If the port for data-in belongs to a VLAN, enable this parameter

and specify the VLAN ID.

◦VLAN For Data Out—If the port for data-out belongs to a VLAN, enable this parameter

and specify the VLAN ID.

◦Video Source SubNet—For routed SSM traffic, specify the IP address range. For

multiple ranges, separate the ranges by a comma.

•Step 4 - SMX Details

Specify the following settings for the statmux controller functionality of the vDCM Video Processing

App instances if needed:

◦Start—Specify Yes

◦Config Path—Keep the default path (/opt/cisco/vdcmvp/smx/config/myconf.cfg)

◦Resource SLA

◦Min Node—The number of instances required for your application. For instance in a 1-1

backup application, specify two.

◦Max Node—Keep the default value (10)

◦Image Flavor Info

◦Image Flavor Group—Choose the name of the group to which the image flavor belongs.

◦Image Flavor Name—Choose the image flavor that matches the nodes that you want

to allocate for these vDCM Video Processing App instances.

◦Configuration

◦VSM Control—Enable this parameter if ROSA VSM controls the instances.

◦VSM Instance Name—The name of the ROSA VSM that controls the instances.

◦VSM Region Name—The name of the region to which the ROSA VSM belongs.

Cisco Virtualized Video Processing Controller Ver 3.2 Integration Guide

Integrating vDCM

Adding and Activating the vDCM VPA Instances

In the current V2PC software version, the configuration of the vDCM VP App instance

must be done using its user interface.

Note

Enabling the vDCM VPA AIC

Enabling the AIC must be done on the Application Deployment Manager > Deployed Applications page

by changing its Admin State to Enable and clicking Update.

Enabling the AIC results in the following steps being performed:

•The vDCM VPA applications are installed to all nodes part of the AIC instance.

•A vDCM VPA device pool is created in the ROSA VSM server with the name that corresponds to the

AIC instance name.

•The vDCM VPA worker instances are added as devices in the vDCM VPA device pool in ROSA VSM.

•ROSA VSM establishes communication with the vDCM VPA instances and polls them.

Disabling the vDCM VPA AIC

Disabling the AIC must also be done on the Application Deployment Manager > Deployed Applications

page. Change its Admin State to Disable and click Update.

Disabling an AIC is only possible if there are no media workflows using the AIC instance.Note

Disabling the AIC results in the following steps being performed:

•The devices corresponding to the vDCM VPA worker instances are removed from the device pool in

ROSA VSM.

•The devices are removed in ROSA VSM.

Integrating vDCM OTT App

Installing the vDCM OTT App / Media Flow Controller

For integrating vDCM OTT App instances in V2PC, deploy the cisco-vdcm-ott application on the V2PC

master and install the cisco-vdcm-ott-transcode-mediaflow controller. The vDCM OTT App application

requires the CentOS 7.2 image. Before you can deploy a vDCM OTT application to a set of worker nodes,

upload the CentOS 7.2 image file to your VMware environment. This image file is distributed together with

the cisco-vdcm packages.

Cisco Virtualized Video Processing Controller Ver 3.2 Integration Guide

Integrating vDCM

Enabling the vDCM VPA AIC

In addition, the multiscreen transcoding using the vDCM OTT App requires a specific number of CPUs and

RAM. Create a custom image flavor group and the following flavor for vDCM applications:

•56 vCPU –64 GB RAM –50 GB disk, if the underlying hardware is a BM200 M4 with E2697 v3

processors.

•64 vCPU –64 GB RAM –50 GB disk, if the underlying hardware is a BM200 M4 with E2697 v4

processors.

For the procedures to upload an image file on a VMware infrastructure, create custom image flavors, and

install applications and media workflow controllers, See Cisco Virtualized Video Processing Controller User

Guide.

After installing the vDCM OTT App, the V2P Controller GUI has several extra menu entries under the Media

Resources section such as TS Channel and TS Channel lineup and under the Templates section such as vDCM

OTT Transcode and vDCM OTT Packaging.

Enabling the vDCM OTT App AIC

Enabling the AIC must be done on the Application Deployment Manager > Deployed Applications page

by changing its Admin State to Enable and clicking Update.

Enabling the AIC results in the following steps being performed:

•The vDCM OTT applications are installed to all nodes part of the AIC instance.

•A vDCM OTT pool is created in the VSM server with corresponding name.

•The vDCM OTT worker instances are added to the device pool.

•The vDCM OTT instances are polled.

To disable the AIC, change Admin State to Disable and click Update

Setting up an xCode Media Workflow

The steps to set up a media workflow for ABR services using the vDCM OTT App are:

•Configuring TS channels

•Creating vDCM OTT transcode templates

•Creating vDCM OTT packaging templates

•Completing the media workflow

For detailed information about the vDCM OTT App, the vDCM OTT App parameters and settings as shown

in the templates, the TS channel, and the media workflow wizard ,see Cisco Virtual Digital Content Manager

(vDCM) User Guide

Configuring TS Channels

The TS channels are accommodated on the Cisco vDCM OTT > TS channels page. To access this page,

click Media Workflow Manager > Resources > Media Sources > vDCM OTT TS Channels.

Cisco Virtualized Video Processing Controller Ver 3.2 Integration Guide

Integrating vDCM

Enabling the vDCM OTT App AIC

To add a new TS channel, click and enter the following information in the Create TS Channel dialog box:

•Specify the channel name, target and source IP address, the port, the service name, and service identifier

(SID) of the incoming source stream.

•Click Video and specify the attributes of the incoming video stream in the area.

•Click Audio and specify the attributes of the incoming audio stream in the area. Repeat this step

for each incoming audio stream to be specified.

•Click Meta and specify the attributes of incoming metadata stream in the area.

To delete a stream definition, check its check box and click .

Tip

Extra functions on the Cisco vDCM OTT > TS Channels page are:

•To duplicate a TS channel, check the check box of the channel and click .

•To delete a TS channel, check the check box of the channel and click .

•To edit a TS channel, check the check box of the channel and click .

Creating a vDCM OTT Transcode Template

The TS transcode templates are located on the Cisco vDCM OTT > Transcode page. To access this page,

click Media Workflow Manager > Resources > Templates > vDCM OTT Transcode.

To add a new template, click and enter the following information in the Create TS Transcode Template

dialog box:

Cisco Virtualized Video Processing Controller Ver 3.2 Integration Guide

Integrating vDCM

Setting up an xCode Media Workflow

•In the Expected Channel Characteristics area, specify the format and frame rate of the incoming video

stream.

•In the Boundary Placement area, specify the ABR settings of the profile sets.

•In the Video area, click to add a profile and configure the video settings. Repeat this step for each

profile to be added.

To duplicate a profile, check the check box of the profile to be duplicated and click .

To remove a profile, check the check box of the profile to be removed and click .

•In the Audio area, click to add an audio output stream or rule. Repeat this step for each audio stream

or rule to be added.

To duplicate an audio stream or rule, check the check box of the entry to be duplicated and click .

To remove an audio stream or rule, check the check box of the entry to be removed and click .

Extra functions on the Cisco vDCM OTT > Transcode page are:

•To duplicate a template, check the check box of the template and click .

•To delete a template, check the check box of the template and click .

•To edit a template, check the check box of the template and click .

Cisco Virtualized Video Processing Controller Ver 3.2 Integration Guide

Integrating vDCM

Setting up an xCode Media Workflow

Creating a vDCM OTT TS Packaging Template

The TS packaging templates are located on the Cisco vDCM OTT > Packaging page. To access this page,

click Media Workflow Manager > Resources > Templates > vDCM OTT Packaging.

To add a new template, click and enter the following information in the Create TS Packaging Template

dialog box:

•In the UDP Streaming area, click and specify the destination network setting for the outgoing TS.

Two destinations can be specified

•In the Archive Output area, enable the check box to save the TS to the disk of the vDCM OTT server

and specify the archive settings. (Optionally)

•In the Transport Stream Settings area, specify the TS settings such as program number, PIDs, and so

on.

•In the Metadata Output area, specify the metadata for the outgoing TS.

Additional functions on the Cisco vDCM OTT > Packaging page are:

•To duplicate a template, check the check box of the template and click .

Cisco Virtualized Video Processing Controller Ver 3.2 Integration Guide

Integrating vDCM

Setting up an xCode Media Workflow

•To delete a template, check the check box of the template and click .

•To edit a packaging template, check the check box of the template and click .

Completing the Media Workflow

Procedure

Step 1 Click Media Workflow Manager > Media Workflows.

The Media Workflow Manager > Media Workflows page appears.

Step 2 From the --Select a Media Workflow Type-- drop down list, choose Transcode and click .

The Create Transcode Media Workflow dialog box appears with the General step selected.

Step 3 In the Service Flow Name field, enter a name for the media workflow.

Step 4 From the Application Instance drop-down list, choose the instance to be occupied by this workflow.

Step 5 Click Next to display the Channel step.

Step 6 From the Channel drop-down list, choose the input TS channel to be processed.

Step 7 On the ESAM tab, configure the ESAM settings as required.

Step 8 Click Next to display the Transcode step.

Step 9 From the Transcode Template drop down list, choose the vDCM OTT transcode template for this workflow.

Cisco Virtualized Video Processing Controller Ver 3.2 Integration Guide

Integrating vDCM

Setting up an xCode Media Workflow

The configured profiles appears in the Video area and the audio streams appears in the Audio area.

Step 10 Click Next to display the Packaging step.

Step 11 From the Packaging Template drop-down list, choose the vDCM OTT package template for this workflow.

Step 12 Click Next to display the Summary.

Step 13 If an ATS channel must be created for this profile set, specify the ATS Channel Name and Channel ID.

Hint: ATS channels can be used as input definition or starting point of a live-capture media workflow over

an MCE/MPE application.

Step 14 Click Finish.

Step 15 Click to enable the workflow.

On enabling the media workflow, the V2PC master sends the necessary commands to the ROSA VSM server

to create a lineup configuration in ROSA VSM. The lineup configuration is specified against the device pool

corresponding with the AIC instance. The ROSA VSM server software selects a suitable vDCM OTT instance

within the device pool and sends the necessary provisioning commands to the vDCM OTT Application.

Additional functions on the Cisco vDCM OTT > Media Workflows page are:

•To disable a media workflow, check the check box of the media workflow and click .

•To delete a media workflow, check the check box of the media workflow and click .

•To edit a media workflow, check the check box of the media workflow and click .

Troubleshooting

Problem: vDCM vPA AIC instance goes into error state or vDCM OTT AIC instance goes into error state

Troubleshooting steps

1Verify that there are worker nodes available with the required image flavor and image

2Verify that a 2-network or a 3-network setup is configured in the infrastructure provider, the zone, and

the worker node. See Setting up a Network with vDCM VPA and vDCM OTT, on page 5.

3Verify if the installation of the application was successful by accessing the vDCM OTT GUI on the worker

node or the vDCM VPA GUI. If the GUI cannot be accessed, it points to failures in the application

installation.

4Detailed logs can be consulted on the V2PC master node in the directory

/var/log/opt/cisco/v2pc/errorlog

In this directory, a log file is present corresponding with the AIC name. For example, for a cisco-vdcm-ott

AIC instance, the file would cisco-vdcm-ott-<aic-name>.current.

Problem: the xCode media workflow is enabled but there is no video on the output.

Troubleshooting steps:

1Open the ROSA VSM user interface on the VSM worker node and verify the activation state of the lineup

configuration.

Cisco Virtualized Video Processing Controller Ver 3.2 Integration Guide

Integrating vDCM

Troubleshooting

A common case of failure is that the video source is not reachable for the vDCM OTT App instance on

the worker node. In this case, the lineup configuration fails (red state). Open the vDCM OTT user interface

on the worker node and verify that the video stream can be detected at the input.

Another cause is an allocation failure. By default, the ROSA VSM allocates up to six ABR services on a

single vDCM OTT instance. If the number of ABR channels exceeds the total number of ABR channels

that can be done, then the activation fails. The number of service flows can be increased per instance in

the VSM GUI (provided the CPU load on the vDCM OTT App instance allows it).

2If the lineup configuration is in green state in the ROSA VSM, open the vDCM OTT App GUI and verify

the state of the service flow.

3Detailed logs can be consulted on the V2PC master node in the directory /var/log/opt/cisco/v2pc/errorlog

In this directory, a log file is present corresponding with the AIC name. For example, for a

cisco-vdcm-xcode- MFC instance, the file would cisco-xcode-<mfc-name>.current.

Cisco Virtualized Video Processing Controller Ver 3.2 Integration Guide

Integrating vDCM

Troubleshooting

CHAPTER 4

Integrating VMR

Cisco Virtual Media Recorder (VMR) provides the core recording capability for Cloud DVR or Timeshift

TV systems. Its architecture allows for scaling service to include millions of subscribers. Recording, storage,

and playback can scale independently, allowing service providers to optimize their investment based on

channels served and usage data on recording and playback requests.

VMR is a segment-based digital media recorder that records live packaged feed from linear packagers

compiled in Common Intermediate Format (CIF) media segments. For recording, VMR consumes media

data as segments from an upstream linear packager, parses manifest files and, when a segment corresponding

to a recording request arrives, captures the segment and pushes it to storage.

VMR also supports media playout to a compatible just-in-time packager (JITP) by converting recordings to

a supported format such as HTTP Live Streaming (HLS) for consumption by end clients. For playback, a

request for playing back a recorded segment is triggered by a just-in-time (JITP) packager. VMR retrieves

the segment from storage and serves it back to the JITP packager.

•Installing the VMR AIC in V2PC, page 17

Installing the VMR AIC in V2PC

After installing the V2P Controller and VMR, integrating the two applications requires installing the cisco-vmr

application instance controller (AIC) to allow the V2PC to act as the control interface for VMR. After installing

the VMR AIC, you can create a media flow controller (MFC) instance of VMR as described in the Cisco

Virtual Media Recorder User Guide.

1Install VMR as described in the Cisco Virtual Media Recorder Deployment Guide.

2Log in to V2PC at the master IP address, port 8443.

3In the V2PC navigation panel, select Application Deployment Manager > Create New Application to

open the Create New Application dialog.

4In the Package Name field, type cisco-vmr, and then click Save. A new application named cisco-vmr

should now appear in the Applications list.

5Confirm that Region is defined as Region 0. If not, define the Region as follows:

•Select Application Deployment Resources > Providers and configure it.

•Drag Region 0 to the Application Deployment Manager page at left.

Cisco Virtualized Video Processing Controller Ver 3.2 Integration Guide

•Drag cisco-vmr to Region 0

6Click Add New. The New Application Instance wizard launches at Step 1 - Instance Info.

7Enter a new cisco-vmr instance name (for example, vmr-02).

8Select Platform Instance and confirm that Provider auto-populates.

9Click Next to navigate to Step 2 - EXTERNAL SERVICES Details.

10 Configure the VMR AIC as follows:

•Docker Registry IP—Docker registry IP address

•Database IP—Database IP address; can be one or multiple IP addresses. If multiple, the user name

and password for all database IP addressses should be the same.

•Database User Name—Database user name

•Database Password—Database password; leave blank

•Objectstore IP—Objectstore IP address or FQDN; can be one or multiple IP addresses. If multiple,

the user name and password for all objectstore IP addresses should be the same.

•Objectstore User Name—Objectstore user name

•Objectstore Password—Objectstore password

•VSRM IP—VSRM IP address or URL

•Locality—VSRM locality information

•Site Id—Site ID for the cisco-vmr installation

•Active Storage Path—Storage path for active contents; for COS, the path must start with rio/

•Archive Storage Path—Storage path for archive contents; for COS, the path must start with rio/

•Recon Storage Path—Storage path for reconstituted contents; for COS, the path must start with

rio/

11 Click Next to navigate to Step 3 - VMR SERVICES Details.

12 Continue configuring the instance as follows:

•VMR hostname—VMR UI hostname

•Playback hostname—FQDN of the packager service host; can be the same as rioFqdn

•VMR Service IP—FQDN of the VMR API host; can be the same as rioRqdn

•VMR GUI Port—FQDN of the VMR API host; can be the same as rioRqdn

•Playback Service Port—Port designation for the VMR API; enter 9998

•Max Supported Channels—Maximum number of channels this VMR installation supports. This

setting uses the number of worker nodes available to determine the number of pods brought up by

VMR.

13 Click Next to navigate to Step 4 - LOG SERVICE Details.

14 Continue configuring the service instance as follows:

Cisco Virtualized Video Processing Controller Ver 3.2 Integration Guide

Integrating VMR

Installing the VMR AIC in V2PC

Page is loading ...

Cisco Virtualized Video Processing Controller Integration Guide

Cisco Virtualized Video Processing Controller Integration Guide

Cisco Virtualized Video Processing Controller Integration Guide

Related papers

Other documents