DCM Integration Into ROSA NMS

4043022 Rev B
DCM Integration into ROSA NMS

Implementation Design Guide
For Your Safety
For Your Safety

Explanation of Warning and Caution Icons
Avoid personal injury and product damage! Do not proceed beyond any symbol
until you fully understand the indicated conditions.
The following warning and caution icons alert you to important information about
the safe operation of this product:
You may find this symbol in the document that accompanies this product.
This symbol indicates important operating or maintenance instructions.
You may find this symbol affixed to the product. This symbol indicates a
live terminal where a dangerous voltage may be present; the tip of the flash
points to the terminal device.
protective ground terminal.
chassis terminal (normally used for equipotential bonding).
You may find this symbol affixed to the product. This symbol warns of a
potentially hot surface.
You may find this symbol affixed to the product and in this document. This
symbol indicates an infrared laser that transmits intensity-modulated light
and emits invisible laser radiation or an LED that transmits intensity-
modulated light.
Important
Please read this entire guide. If this guide provides installation or operation
instructions, give particular attention to all safety statements included in this guide.
4043022 Rev B iii

Notices
Notices
Trademark Acknowledgments
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its
affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found
at www.cisco.com/go/trademarks.
Other 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. (1009R)
Publication Disclaimer
Cisco Systems, Inc., assumes no responsibility for errors or omissions that may
appear in this publication. We reserve the right to change this publication at any
time without notice. This document is not to be construed as conferring by
implication, estoppel, or otherwise any license or right under any copyright or
patent, whether or not the use of any information in this document employs an
invention claimed in any existing or later issued patent.
Copyright
© 2012 Cisco and/or its affiliates. All rights reserved.
Information in this publication is subject to change without notice. No part of this
publication may be reproduced or transmitted in any form, by photocopy,
microfilm, xerography, or any other means, or incorporated into any information
retrieval system, electronic or mechanical, for any purpose, without the express
permission of Cisco Systems, Inc.
4043022 Rev B v
Contents
Contents
For Your Safety iii
Notices v
Safe Operations ix
Preface xi
Chapter 1 Setting Up ROSA NMS 1

Introducing ROSA NMS ......................................................................................................... 2
Installing the ROSA NMS Drivers ......................................................................................... 3
Introduction ................................................................................................................. 3
To Install the ROSA Drivers ...................................................................................... 4
Making Task Instances ............................................................................................................ 8
Introduction ................................................................................................................. 8
To Make a Task Instance ............................................................................................ 8
Creating Authentication Profiles ......................................................................................... 10
Introduction ............................................................................................................... 10
Adding an Authentication Profile .......................................................................... 10
Mapping a DCM into ROSA NMS ...................................................................................... 12
Introduction ............................................................................................................... 12
To Map a DCM into ROSA NMS ............................................................................ 12
Operational Limitations and Errors .................................................................................... 16
Chapter 2 Working with the Graphical User Interfaces 17

Opening the User Interface of a DCM ................................................................................ 18
Opening the User Interface of a Task or Component ....................................................... 20
Chapter 3 Using DCM Macros 23

About the DCM Macros ........................................................................................................ 24
Installing the DCM Macros .................................................................................................. 25
Creating Config Files ............................................................................................................. 26
Using DCM Macros ............................................................................................................... 28
Handling Service Components Tracking Rules.................................................... 28
GbE Port Settings ...................................................................................................... 32
4043022 Rev B vii

Contents
Importing and Removing PSI/SI Data .................................................................. 34

Starting or Stopping Streaming of Outgoing Transport Streams ...................... 36
Handling the Services Population of an Outgoing Transport Stream .............. 38
Starting and Stopping a Splicing Event ................................................................. 39
Logo Insertion ........................................................................................................... 42
Using Macros for Service Backup ........................................................................... 51
Transport Stream Backup ........................................................................................ 58
Joining GbE Port Pairs to a Multicast Group ........................................................ 62
Configuring the D9036 Statmux Controller .......................................................... 68
Generating Test Messages ....................................................................................... 72
Importing the Device Configuration ...................................................................... 72
Activating Alternate Services .................................................................................. 73
Appendix A Customer Information 75

Product Support ..................................................................................................................... 76
Obtaining Support .................................................................................................... 76
Support Telephone Numbers .................................................................................. 76
Appendix B Available Macros 79

DCM Macros........................................................................................................................... 80
Appendix C Macro Backup Configuration Consideration 85

Modifying Registries for Device Backup Purposes ........................................................... 86
Glossary 89
viii 4043022 Rev B

Safe Operations
Safe Operations
The software described in this guide is used to monitor and / or manage Cisco
equipment. Certain safety precautions should be observed when operating
equipment of this nature.
For product specific safety requirements refer to the appropriate section of the
documentation accompanying your product.
4043022 Rev B ix
Preface
Preface
About this Guide
Introduction
This Implementation Design Guide provides the necessary information to integrate a
Digital Content Manager (further called DCM) into the ROSA® Network
Management System (further called ROSA NMS).
Audience
The audience of this Implementation Design Guide includes authorized and trained
service personnel who are responsible for the installation, configuration, and usage
of the Digital Content Manager and the ROSA NMS software.
Required Knowledge
To use this User's Guide, service personnel should have a basic knowledge about the
technology used in relation to this product.
Related Publications
Refer to the following publications for more information about the DCM and the
ROSA NMS system.
 ROSA Network Management System - User's Guide, part number 4014778
 IIOP Protocol Driver - User's Guide, part number: 6985041
 SI Editor - User's Guide, part number: 6985061
 Statmux Pool Manager - User's Guide, part number 4022297
 Digital Headend Backup - User's Guide, part number 6985066
 Macro Component - User's Guide, part number: 6984990
 Digital Content Manager (DCM) - Configuration Guide
 Digital Content Manager (DCM) - Online Help
Both DCM publications can be accessed via the embedded graphical user interface of
the DCM.
4043022 Rev B xi
1 Chapter 1
Setting Up ROSA NMS
Introduction
This chapter describes how to setup the ROSA Network Management
System for the integrating of DCM devices into this system.
In This Chapter
 Introducing ROSA NMS ........................................................................ 2
 Installing the ROSA NMS Drivers........................................................ 3
 Making Task Instances ........................................................................... 8
 Creating Authentication Profiles ........................................................ 10
 Mapping a DCM into ROSA NMS ..................................................... 12
 Operational Limitations and Errors ................................................... 16
4043022 Rev B 1
Chapter 1 Setting Up ROSA NMS
Introducing ROSA NMS

ROSA NMS is a complete solution to manage Cisco equipment in the most efficient,
cost-effective manner possible. The ROSA platform supports a wide range of
broadcast and broadband networks with a complete set of protocol and device
drivers, automation tasks, and service description models. This network
management system also contains a complete toolbox to integrate third-party
equipment.
The ROSA NMS allows creating customized views like geographical views, rack
layout views, equipment interconnection views… to make the diagnostic process
easier.
The ROSA NMS automation tasks help the user to build self-healing systems by
using a wide palette of tasks for backup equipment, transmission links or services.
The ROSA NMS Notification task can send pager, SMS and E-mail messages to
service technicians when certain alarm conditions occur. This task is highly
configurable, different rules and schedules can be defined for each scenario and
service technician.
Important:
 To integrate a DCM into an application with ROSA NMS, an OS account must be
created for which the IIOP option is enabled and the IIOP External IP service of
the DCM must be switched on. For information, please refer to configuration
guide or online help of the DCM.
 To ensure backward compatibility with the older ROSA NMS systems, it is
advised to create a guest OS account with IIOP privileges and password guest.
This account is automatically created when upgrading the DCM for the first time
to software package version 8.5. From ROSA NMS systems version 4.3 onwards,
security profiles can be defined to work with other accounts than the guest OS
account. For information, please refer to configuration guide or online help of the
DCM.
2 4043022 Rev B
Installing the ROSA NMS Drivers

Introduction
Before a DCM can be integrated into ROSA NMS, a number of ROSA NMS drivers
should be installed. The following list shows these drivers:
 IIOP Protocol Driver
The IIOP Protocol driver is a protocol driver that is used to establish
communication with IIOP devices. The driver scans for IIOP devices and allows
mapping of IIOP devices to ROSA resources.
 DCM Device Driver
The DCM Device Driver allows integrating the embedded GUI of the DCM into
ROSA NMS.
 AC Manager Component
The AC Management Component can be used to create, edit, and delete access
criteria and services.
 SI Distributor
A part of the SI Distributor functionality is used by the AC Manager component.
 Scrambling Control Task Driver
The Scrambling Control Task Driver acts as a scrambling/descrambling switch.
 Statmux Pool Manager (SPM)
The Statmux Pool Manager tool allows easy and quick configuration of multiple
encoders participating into a statmux application controlled by DCM's IP
statmux controller.
 Macro Component
The Macro Component can be used to execute the DCM macros. More
information can be found in chapter Using DCM Macros on page 23.
Notes:
 When the ROSA system is used for management or configuration purposes, both
the IIOP Protocol Driver and DCM Device driver are required.
 When the ROSA NMS system and DCM device(s) participate into CA systems,
with the exception of the Macro Component and Statmux Pool Manager driver,
all drivers mentioned above must be installed. The AC Manager Component
driver and the Scrambling Control Task Driver should not be installed when the
Event Information Scheduler (EIS) functionality is performed by a third party
device.
4043022 Rev B 3
Pay attention to the following remarks before installing the drivers into the ROSA
software:
 You cannot install drivers with a lower product version.
 To upgrade a driver, simply install the newer driver. The old driver will be
replaced automatically. Do NOT uninstall the old driver first!
 Downgrading drivers within the same product version is not possible unless you
uninstall the drivers first. Uninstalling a driver results in the loss of all
configurations because all resources using the driver are removed from the
Server Explorer tree.
 If you install drivers that require a server software version higher than the
current installed version, the server software will be upgraded automatically.
For detailed information concerning the installation of drivers, please refer to the
User’s Guide of the ROSA software.
To Install the ROSA Drivers

The following procedure explains how to install the drivers into the ROSA NMS
software.
1 In the Server Explorer tree of the ROSA system, select the server in which the
DCM must be integrated.
2 In the Config menu, point to Drivers…
Result: The Installed Drivers dialog is displayed.
3 Press the Install… button.

Result: The Open dialog is displayed.
4 Browse to the folder containing the driver files. These driver files can be found
on the ROSA Installation DVD or on the following location:
4 4043022 Rev B
 ROSA Device Configuration Shell: in the folder \ Program Files \ Cisco \

ROSADevConfShell \ Copernicus \ Drivers\ on the hard disk of the PC
running the ROSA software.
Note: If your ROSA DCS system is upgraded from 3.0 to 4.0 or higher, the
driver files are located in the following folder: .. \ Program Files \ Scientific-
Atlanta \ ROSADevConfShell\ Copernicus \ Drivers \.
 ROSA Single User: in the folder .. \ Program Files \ Cisco \ ROSASingleUser
\ Copernicus \ Drivers \ on the hard disk of the PC running the ROSA NMS
software.
Note: If your ROSA Single User system is upgraded from 3.0 to 4.0 or higher,
the driver files are located in the following folder: .. \ Program Files \
Scientific-Atlanta \ ROSASingleUser \ Copernicus \ Drivers \.
 ROSA Client: on the server’s hard disk in the shared folder \ Copernicus \
Drivers
Notes:
 If the \ Drivers folder on the server’s hard disk is no longer shared, you can
download all driver files to the hard disk of your client computer. On the
Installed Drivers dialog, click on the Get Drivers from Server button.
The files are then copied into the folder .. \ Copernicus \ drivers on your local
hard disk.
 When the drivers are downloaded from our FTP server, browse to the
location where you stored these files.
5 Select the driver files required for your application. The following table lists the
driver files.
ROSA NMS Driver File Name

IIOP Protocol Driver IIOP Protocol.rsx
DCM Device Driver DCM.rsx
AC Manager Component AC Manager Component.rsx
Scrambling Control Task Driver Scrambling Control Task.rsx
DVB SI Distributor SI Distributor.rsx
Statmux Pool Manager SPM.rsx
To select multiple drivers, press and hold down the [CTRL] key, and point to
each file.
6 Press the Open button.
4043022 Rev B 5
Result: After successful installation, the names of the drivers are added to the
Installed Drivers dialog.
7 Press the Close button to close the dialog.

Note: After selecting the driver files and pressing the Open button, it may be
possible that the server must be rebooted, in this case the following message box is
displayed.
The following procedure describes how to reboot the server.

 Close the Please, reboot server (via ROSA)! message box by pointing to the OK
button.
 On the Installed Drivers dialog, click on the Close button to close the dialog.
 In the Server menu, select Manage and point to Reboot Server...
6 4043022 Rev B
Result: The following confirmation box is displayed.
 Click on the Yes button to reboot the server.

Result: The server starts rebooting.
4043022 Rev B 7
Making Task Instances

Introduction
After the installation of the Scrambling Control Task driver and SI Distributor Task
driver, task instances for these tasks must be created.
Note: As long as no task instance is created for a task, the task will not appear in the
Explorer Tree.
To Make a Task Instance

The following procedure explains how to create a task instance for the Scrambling
Control Task. The procedure to make a task instance for the SI Distributor Task is
similar.
1 In the Server Explorer tree of ROSA, select the server that participates into the
CAS system.
2 In the Config menu, point to Drivers….
Result: The Installed Drivers dialog is displayed.
3 Select Scrambling Control Task and click on the Make Task button.
8 4043022 Rev B
Making Task Instances
Result: The Make Task dialog is displayed.
4 Press the OK button to confirm.

Result: The Scrambling Control Task is added to the Explorer Tree.
5 Click on the Close button to close the Installed Drivers dialog.
4043022 Rev B 9
Creating Authentication Profiles

Introduction
For security reasons, a DCM requires authentication before external management via
IIOP is allowed. Before a DCM can be mapped into ROSA NMS, the DCM must be
provided with an OS account with IIOP privileges and an authentication profile
should be created for the IIOP driver with matching user name and password.
Adding an Authentication Profile

Follow these steps to create an authentication profile.
1 Right-click on IIOP Protocol in the Server Explorer and click on Properties in
the shortcut menu.
Result: The IIOP Protocol user interface appears.
2 Click on the Authentication Profile tab
Result: The Authentication Profiles list displays.
3 Click on Add....
10 4043022 Rev B
Creating Authentication Profiles
Result: The Add Authentication Profile dialog appears.
4 In the Profile Name box, type a unique name for the authentication profile.
5 In the User Name box, type the user name.
Note: The user name must correspond with the OS account with IIOP privileges
defined on the DCM.
6 In the Password box, type the password.
Note: The password must correspond with the OS account with IIOP privileges
defined on the DCM.
7 Press OK to confirm or Cancel to abort the operation.
4043022 Rev B 11
Mapping a DCM into ROSA NMS

Introduction
Before a DCM can be mapped into the ROSA software, a scan operation must be
executed to detect the device. If the scan operation is successfully performed and the
device is mapped, the unit will be displayed into the Server Explorer tree of the
ROSA system. The procedure to scan and to map a DCM using the IIOP Protocol
Driver can be found in following subtopic.
To Map a DCM into ROSA NMS

The following procedure is designed to be used as step-by-step instructions for
mapping a DCM using the IIOP Protocol driver.
Note: More detailed information concerning the IIOP Protocol drive can be found in
the IIOP Protocol Driver User’s Guide.
1 In the Server Explorer tree of the ROSA system, right-click on the IIOP Protocol
node and point to Properties in the shortcut menu.
Result: The user interface of the IIOP Protocol driver is displayed.
12 4043022 Rev B
2 Click on the Add... button.

Result: The Add devices to scan dialog is displayed.
3 In Identify device by drop down box, select how to identify the device.
4 If IP address is selected, then type the IP address in the From box. If IP address
range is selected, then type the IP address range values in the From and To box.
5 Select the Enable Authentication check box to enable authentication.
6 In the Authentication Profile list box, select the authentication profile to be used
for the DCM.
7 In the Time Out box, type a timeout value between 10 and 60000 ms.
8 In the Retry Count box, type a retry value between 1 and 5.
9 Click on OK to confirm and to close the dialog.
10 Point to Apply.
11 Select the Map Resources tab on the user interface of the IIOP Protocol driver.
4043022 Rev B 13
Result: The Map Resources tab is displayed.
12 Select the DCM that must be mapped and click on the New Resource... button.
Result: The New Resource dialog is displayed.
13 Enter a resource name in the Name box and press the OK button to confirm.
14 4043022 Rev B
Result: The new DCM will be added to the Server Explorer tree.
Note: If the authentication fails, an error message will be logged in IIOP Protocol
driver. Verify the authentication profiles.
4043022 Rev B 15
Operational Limitations and Errors

When the port mode of the Ethernet ports is set to Fixed Individual Ports, the
following steps should be done to load the full device configuration of the DCM into
ROSA NMS.
1 Execute the DCM.LoadFullDeviceConfiguration macro as described in topic
Importing the Device Configuration on page 72.
2 Press the Reload button on the user interface of the SI Distributor task driver if
this driver is installed.
16 4043022 Rev B
2 Chapter 2
Working with the Graphical
User Interfaces
Introduction
This chapter describes how to open the web browser user interface of
the DCM using ROSA NMS and how to open the user interface of a
task or component.
In This Chapter
 Opening the User Interface of a DCM ............................................... 18
 Opening the User Interface of a Task or Component ...................... 20
4043022 Rev B 17
Chapter 2 Working with the Graphical User Interfaces
Opening the User Interface of a DCM

Perform the following steps to open the user interface of the DCM via ROSA NMS.
1 In the Server Explorer or Group Explorer tree of the ROSA system, right-click on
the DCM resources for which the user interface must be opened and point to
Properties in the shortcut menu.
Result: The user interface of the selected DCM resource will be opened.
Notes:
 The user interface can also be opened by double-clicking on the unit in a map.
The following picture depicts a DCM.
 The user interface of the DCM can be opened via ROSA NMS without logging on
by using the DCM bypass login feature. For a DCM with software package lower
than version 8.5, ROSA NMS uses a default account for this. But from DCM
software version 8.5 onwards, ROSA NMS (version 4.3 or higher) needs the
knowledge of the user name and password of a GUI account by creating a
registry key on the computer running the ROSA NMS Server software. The
following steps describe how to add such registry key.
a Open Regedit on the computer running the ROSA NMS Server software.
b In the tree, browse to
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Barco.Copernicus.Container.
18 4043022 Rev B
Opening the User Interface of a DCM
c Right-click on this string, point to New and select Key in the shortcut menu.
Result: A new key is added under

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Barco.Copernicus.Container
for which the name is editable.
d Enter DCM and press enter.
e Right-click on this DCM string, point to New and select Key in the shortcut
menu.
f Enter the IP address of management port of the DCM that is connected to the
ROSA NMS server and press enter.
Hint: The octets of the IP address should be separated by dots.
g In the tree, right-click on this key, point to New, and select String Value.
Result: A new value is added for this key.
h Rename this value to Username.
i Right-click on this value and point to Modify in the shortcut menu.
Result: The Edit String dialog appears.
j In the Value data box, enter the username of the GUI account and press OK.
k Repeat step g up to j for a string value for the password. Use Password for
value name and the password of the GUI account for value data.
l Close Regedit.
4043022 Rev B 19
Opening the User Interface of a Task or Component

The following steps explain how to open the AC Manager Component. The
procedures to open the Scrambling Control Task and Statmux Pool Manager are
similar.
Note: Since only a part of the SI Distributor Task functionality is used for DVB
Scrambling, an empty GUI will be displayed with the message SI Distributor Control
Panel not available due to missing License after opening the task.
1 In the Explorer Tree of the server that participates in the Conditional Access
System, right-click on AC Manager Component and point to Properties in the
shortcut menu.
Result: The AC Manager Component with the Access Criteria dialog is
displayed.
 To Resize the Graphical User Interface

The size of the user interface of a task or component can be increased or
decreased by dragging the lower right corner of the dialog.
Note: The user interface of a task or component cannot be made smaller than the
size it was opened.
20 4043022 Rev B
Opening the User Interface of a Task or Component
 To Maximize the Graphical User Interface

The user interface of a task or component can be maximized by clicking on the
maximize button in the upper right corner of the window.
 To Close the Graphical User Interface
The user interface of a task or component can be closed in one of the following
ways:
- On the File menu, click on Exit.
- Press [Alt] + [F4]
- Click on the close button in the upper right corner of the window.
 The Apply button
When changes are made to settings on the user interface, the new settings must
be sent to the device by clicking on the Apply button. When settings are made on
different tabs of the user interface, these settings can be activated all at once by
clicking on the Apply button.
 The Reload button
When settings are accidentally changed, the previous settings can be restored by
clicking on the Reload button.
Note: This reload function works only before the Apply button has been pressed.
 Checking the Driver Version
There are three different ways to check the user interface of a task or component.
- In the Installed Drivers dialog, check the Driver Version column.
4043022 Rev B 21
- In the Installed Drivers dialog, select the line of the driver and click on the
Details button.
- On the user interface of a task or component, click on About in the Help

menu.
22 4043022 Rev B
3 Chapter 3
Using DCM Macros
Introduction
This chapter describes how to execute the DCM macros using ROSA
NMS.
In This Chapter
 About the DCM Macros ....................................................................... 24
 Installing the DCM Macros ................................................................. 25
 Creating Config Files ............................................................................ 26
 Using DCM Macros .............................................................................. 28
4043022 Rev B 23
Chapter 3 Using DCM Macros
About the DCM Macros

Particular configuration settings of the DCM can be adapted by executing macros
using ROSA’s Macro Component. The Macro Component allows manipulating and
to executing predefined set(s) of macros on one or multiple resources. A macro can
range from a single action on a device to a full script that interacts with several
devices. Macros can have a wide set of parameters such as numbers, strings, devices
or other resources. With the Scheduler tool, the time the macro must be executed can
be determined. The Scheduler supports single shot and recurring macro schedules: a
single shot macro is executed only once at a specified date and time, a recurring
macro schedule follows a schedule that is defined with help of the ROSA Schedule
Database Component.
For more detailed information about the Macro Component please refer to the
Macro Component User’s Guide.
Before DCM macros can be executed, the Macro Component and these macros must
be installed into ROSA NMS. The procedure to install the Macro Component is
described in topic Installing the ROSA 3.0 Drivers on page 3 and in the Macro
Component User's Guide. The procedure to install the DCM Macros is described in
the following topic.
24 4043022 Rev B
Installing the DCM Macros
Installing the DCM Macros

The DCM macros are not installed by default; perform the following steps to install
these macros.
1 Browse to the folder containing the driver files. These drivers can be found on
the ROSA Installation CD-Rom or on the following location:
 ROSA Single User: in the folder \ Program Files \ Cisco \ ROSASingleUser \
Copernicus \ Drivers\ on the hard disk of the PC running the ROSA software.
the driver files are located in the following folder: .. \ Program Files \
Scientific-Atlanta \ ROSASingleUser \ Copernicus \ Drivers \.
 ROSA Client: on the server’s hard disk in the shared folder \ Copernicus \
Drivers
Notes:
- If the \Drivers folder on the server’s hard disk is no longer shared, you can
download all driver files to the hard disk of your client computer. On the
Installed Drivers dialog, click the Get Drivers from Server button. The files
are then copied into the folder .. \ Copernicus \ drivers on your local hard
disk.
- When the macros are downloaded from our FTP server, browse to the
location where you stored these files.
2 Copy the files with .bnm or .rcm extension to the following location:
\ Program Files \ Cisco \ ROSASingleUser \ Copernicus \ MacrosAndScripting
the files must be copied in the following folder: .. \ Program Files \ Scientific-
Atlanta \ ROSASingleUser \ Copernicus \ MacrosAndScripting.
3 Copy the DCM.py file to the following location:
\ Program Files \ Cisco \ ROSASingleUser \ Copernicus \ MacrosAndScripting
\ Scripts
the files must be copied in the following folder: .. \ Program Files \ Scientific-
Atlanta \ ROSASingleUser \ Copernicus \ MacrosAndScripting \ Scripts.
4 Stop and reconnect to the server as described in the ROSA Network
Management System User's Guide.
Result: The DCM macros are added to the list of the Macro Component.
4043022 Rev B 25
Creating Config Files

Particular macros require additional information by uploading a configuration file.
Such file can be created using a standard text editor like Notepad or using Microsoft
Excel. A configuration file is built up in two parts: a Header part and a Data Lines part
(see illustration below).
The header of the configuration file is mandatory and has the following syntax:
Version,1
Note: Version and 1 has to be separated by a comma.

A row in the data lines part consist of a number of parameters each separated by a
comma.
To enhance the readability of the configuration file or to provide additional
information, comment lines can be added. A comment line should be prefixed by a
hash mark (#). The following picture depicts a configuration file with comments.
Since Microsoft Excel is able to import and to create comma-delimited text files, a
configuration file can be created and/or adapted using this spreadsheet application.
Once the file is ready, the file should be saved as a comma-delimited file (CSV
extension).
26 4043022 Rev B
Creating Config Files
The following illustrations show a configuration opened with Microsoft Excel.
4043022 Rev B 27
Using DCM Macros

Handling Service Components Tracking Rules
Adding Service Component Tracking Rules
The DCM.ApplyComponentRules and DCM.ApplyComponentRulesEx macro allow
adding service component tracking rules which are used to keep the content of a
service in an outgoing transport stream constant and to block unnecessary
components. The DCM.ApplyComponentRules macro supports the Component Tag,
PCR, Stream Type, ES PID, ECM PID, and ES ECM PID method to identify a service
component. The DCM.ApplyComponentRulesEx macro, which is an extension to the
DCM.ApplyComponentRules macro, supports the same methods extended with the
ECM CAS ID and ES ECM CAS ID method.
By executing the DCM.ApplyComponentRules or DCM.ApplyComponentRulesEx macro,
service component tracking rules are defined by a configuration file.
Important: When service component tracking rules are configured for a service by a
macro, configuring rules by using the user interface of the DCM for that service is
not longer possible.
Notes
 A service component tracking rule using the ES ECM CAS ID or ES ECM PID
method requires an accompanying parent rule with the same ES output PID in
order to be valid.
 For the ECM CAS ID and ES ECM CAS ID method
(DCM.ApplyComponentRulesEx macro), the DCM needs software package version
7.3 or higher.
Parameters
Before the DCM.ApplyComponentRules or DCM.ApplyComponentRulesEx macro can be
executed, the component needs the knowledge of the following information:
 The DCM device affected by the macro (IDCM_ResId parameter)
 The full path of the configuration file containing the component tracking rule
definitions (strConfigFile parameter)
Note: Defining service component tracking rules using the
DCM.ApplyComponentRules or DCM.ApplyComponentRulesEx macro and using
the user interface of the DCM cannot be combined for the same services.
28 4043022 Rev B
Using DCM Macros
Configuration File
During executing the DCM.ApplyComponentRules or DCM.ApplyComponentRulesEx
macro, the component tracking rule definitions as specified into a configuration file
will be applied by the Macro Component.
Note: The configuration file for the DCM.ApplyComponentRules macro differs from
the configuration file for the DCM.ApplyComponentRulesEx macro. The configuration
file for the DCM.ApplyComponentRulesEx macro is enlarged with the CAS ID
parameter that is used by the ECM CAS ID and ES ECM CAS ID method.
The following illustration shows the syntax of the component tracking rule
definitions.
4,1,225.0.0.1,49410,stream type, , ,Audio,0x81,en4, , ,2,86,pass
1 2 3 4 5 6 7 8 9 10 12 14 15
11 13
1 Input - Card parameter
2 Input - Port parameter
3 Input - IP Address parameter
4 Input - UDP parameter
5 Tracking type parameter
Valid values for DCM.ApplyComponentRules macro: ES PID, PCR, ECM PID, ES
ECM PID, Stream Type, and Component Tag
Valid values for DCM.ApplyComponentRulesEx macro: ES PID, PCR, ECM PID, ES
ECM PID, Stream Type, Component Tag, ECM CAS ID, and ES ECM CAS ID.
6 CAS ID parameter (DCM.ApplyComponentRulesEx macro only)
7 Tag parameter
8 Streamtype parameter
Valid values: Video, Audio, DVB Subtitles, DVB Teletext, Data, and User Defined
9 Streamtype Value parameter
10 Language parameter
11 Input PID parameter
12 ES Output parameter
13 Output SID parameter
14 Output PID parameter
15 Status New parameter
Valid values: pass, and block
Notes
 The Tracking type, Streamtype, and Status New parameter are case insensitive.
4043022 Rev B 29
 When a configuration file for the DCM.ApplyComponentRules macro (without

CAS ID parameter and configuration file version 1) is uploaded for the
DCM.ApplyComponentRulesEx macro, the macro will process the component
tracking rule definitions in the same way as the DCM.ApplyComponentRules
macro.
 For an outgoing transport stream on an ASI Interface Card, both the Input - IP
Address parameter and the Input - UDP parameter should be left empty.
With the exception of the transport stream specification parameters (first 4 columns),
the layout of the DCM_Config file is similar to the Component Tracking Rules table
on the Components page of the user interface of the DCM. For more information
about these parameters, please refer to topic Tracking Rules.
The parameters that must be entered to define a tracking rule depend on the
tracking rule type. The table below shows the parameters that must be entered for
the different rule types.
pe
V eam pe
t
ES PID
SI tpu
In age
ue ty
St mty
Ta D
u
u
us
I
t
ea
pe
O
ng
pu
S
D
g
at
al
r
r
A
Ty
St
La
PI
St
C
ES PID
ES ECM PID
ECM PID
PCR
Streamtype (*)
Comp. Tag
ECM CAS ID
ES ECM CAS ID
(*) only if streamtype is Audio (may also be left empty)
The picture below depicts an example of a comma-delimited text file opened with
Microsoft Excel.
30 4043022 Rev B
Using DCM Macros
Downloading the Service Component Rules from a DCM

The DCM.GetComponentRules macro allows downloading the existing service
component rules from a specified DCM and store them in a CSV formatted file on
the computer running the ROSA NMS Server software.
Requirements: This DCM.GetComponentRules macro requires ROSA NMS version
4.0 or higher, DCM device driver for ROSA NMS version 4.0.7 or higher, and
DCM.py script version 1.20 or higher.
Parameters
For executing the macro, the following information is needed:
 The DCM from which the service component rules must be downloaded
(lDCM_RESID parameter)
 The directory path for the configuration file (strConfigFilePath parameter). The
DCM_Config.csv will be created or overwritten in the specified path. Note that
the directory must already be present.
Removing Service Component Tracking Rules

For removing service component tracking rules, the following macros can be used:
 DCM.RemoveRules: removing tracking rules from a single device
 DCM.RemoveRulesEx: removing tracking rules from multiple devices. The
tracking rules that have to be removed must be defined into a configuration file.
This configuration file is similar as the configuration file used for adding service
component tracking rules, see topic Adding Service Component Tracking Rules on
page 28.
Hint: A configuration file can be uploaded from a device by executing the
DCM.GetComponentRules , see topic Downloading the Service Component Rules from
a DCM on page 31. The rules, which have to remain in the devices, must be
removed from the file.
Parameters
Before the DCM.RemoveRules macro can be executed, the component needs the
knowledge of the following information:
 The DCM (IDCM_ResId parameter) for which service component tracking rules
must be removed
 The slot position of the interface card (ICard parameter) and the number of the
port (IPort parameter) containing the outgoing transport stream to which the
service component tracking rules apply
 When the outgoing transport stream belongs to a GbE port, the destination IP
address (strIPAddress parameter) and UDP port (IUDPPort parameter).
 The SID of the service to which the tracking rules apply (ISID parameter). When
4043022 Rev B 31
this parameter is set to -1, the tracking rules applied to all services of the
specified outgoing transport stream will be removed.
For executing the DCM.RemoveRulesEx macro:
 The full path of the configuration file containing the component tracking rule
definitions (strConfigFile parameter)
 The name of the resource set (Devices parameter) containing the DCM devices
affected by this macro.
GbE Port Settings

Enabling or Disabling Port Mirroring for GbE Ports
Port mirroring for GbE ports on multiple DCM devices can be enabled or disabled
by executing the DCM.SetGbEPortMirrors macro. During executing this macro, the
necessary parameters, which are described in a configuration file, will be applied
into the corresponding DCM devices.
Requirements: This macro needs ROSA NMS version 4.0.10 or higher, DCM device
driver for ROSA VSM version 4.0.25 or higher, and DCM.py script version 1.31 or
higher.
Parameters
For executing this macro, the following information is required:
 The path of the configuration file
Configuration File
The following illustrations show the syntax of the data lines in the configuration file
and an example of a comma-delimited text file opened with Microsoft Excel.
32 4043022 Rev B
Using DCM Macros
Each data line in the configuration file has the following settings:
 IP Address: the IP address of the DCM
 Board: Slot position of the housing in which the card is installed
 Port: Number of the GbE port
 Enable: 0 or 1. 0 means that port mirroring is disabled and 1 means that port
mirroring is enabled.
Switching on or off Auto-negotiation of GbE Ports

Auto-negotiation for GbE ports on multiple DCM devices can be switched on or off
by executing the DCM.SwitchAutoNegotiation macro. During executing this macro,
the necessary parameters, which are described in a configuration file, will be applied
into the corresponding DCM device.
driver for ROSA VSM version 4.0.25 or higher, and DCM.py script version 1.31 or
higher.
Parameters
For executing this macro, the following information is required:
 The path of the configuration file
4043022 Rev B 33
Configuration File
The following illustrations show the syntax of the data lines in the configuration file
and an example of a comma-delimited text file opened with Microsoft Excel.
Each data line in the configuration file has the following settings:
 IP Address: the IP address of the DCM
 Board: Slot position of the housing in which the card is installed
 Port: Number of the GbE port
 Enable: 0 or 1. 0 means that auto-negotiation is switched off and 1 means that
auto-negotiation is switched on.
Importing and Removing PSI/SI Data

Importing PSI/SI Information
Program Specific Information (PSI), Service Information (SI), or Program and System
Information Protocol (PSIP) exported from the DCM or created by means of ROSA's
SI Editor can be uploaded to the DCM by executing the DCM.ImportSIData macro.
34 4043022 Rev B
Using DCM Macros
Note: The PSI/SI is uploaded via the PSIG To MUX interface, therefore a specific
PSIG proxy (: SA Specific) must be configured for the DCM. More information can
be found in topic PSI/SI Generators.
Parameters
To execute the DCM.ImportSIData macro, the Macro Component needs the following
knowledge:
 The DCM (IDCM_ResId parameter) containing the outgoing transport stream to
which PSI/SI must be loaded
 The ON ID (IONID parameter) and TS ID (ITSID parameter) of this outgoing
transport stream
 The PID (IPID parameter) to which PSI/SI must be added
 The path and the name of the file containing the PSI/SI (strSiDataFileName
parameter)
- For DCM software package version lower than 5.0 / DCM Driver up to and
including 3.0.22
If this path is left empty, the table on the specified PID for the specified
transport stream will be removed.
- For DCM software package version higher than or equal to 5.0 / DCM
Driver higher than or equal to 3.0.24
This parameter must always be filled in.
Removing PSI/SI/PSIP Information

The DCM.RemoveSIData macro allows removing MPEG2 and/or DVB-SI tables from
a particular outgoing transport stream.
Requirements: This macro requires DCM device driver for ROSA NMS version
3.0.24 or higher and DCM with software package version 5.0 or higher.
Parameters
To remove PSI/SI from an outgoing transport stream using the DCM.RemoveSIData
macro, the following information is required.
 The DCM (IDCMResID parameter) containing the outgoing transport stream for
which a table must be removed
 The ON-ID (IONID parameter) and TS-ID (ITSID parameter) of this outgoing
transport stream
 The PID (IPID parameter) for which a table must be removed
 The table ID (ITableID parameter), table ON-ID (ITableONID parameter), table
TS-ID (ITableTSID parameter) and table ID Ext (ITableIDExt parameter) to
fully identify which table must be removed. These parameters depend on which
table should be removed. The following table lists these parameters.
4043022 Rev B 35
Table TableID TableONID TableTSID TableIDExt

PAT 0x00 -1 TableTSID -1
CAT 0x01 -1 -1 65535
PMT 0x02 -1 -1 ServiceID
NITa 0x40 -1 -1 NetworkID
NITo 0x41 -1 -1 NetworkID
SDTa 0x42 TableONID TableTSID -1
SDTo 0x46 TableONID TableTSID -1
BAT 0x4A -1 -1 BouquetID
EITp/f a 0x4E TableONID TableTSID ServiceID
EITp/f o 0x4F TableONID TableTSID ServiceID
EITsch a 0x50…0x5F TableONID TableTSID ServiceID
EITsch o 0x60…0x6F TableONID TableTSID ServiceID
Notes
 The PSI/SI is uploaded via the PSIG To MUX interface, therefore a specific PSIG
proxy (SA Specific) must be configured for the DCM.
 Removal of EITp/f a, EITp/f o, EITsch a and EITsch o is only supported in DCM
software package version 5.1 or higher.
Hint: Removing PSI/SI for DCM ESW lower than 5.0 and DCM driver up to and
including 3.0.22 can be done using the DCM.ImportSIData macro.
Starting or Stopping Streaming of Outgoing Transport Streams

Streaming of outgoing transport streams can be activated or stopped by using the
following macros:
 DCM.SwitchStreaming: Activates or stops streaming of a single outgoing
transport stream
 DCM.SwitchStreamingTSWithFile: Activates or stops streaming of multiple
outgoing transport streams. Transport stream identification parameters, which
are specified into a configuration file, are applied during macro execution.
 DCM.switchStreamingTSWithFileForResourceSet: Activates or stops streaming of
multiple outgoing transport streams on multiple DCM devices. Transport stream
identification parameters, which are specified into a configuration file, are
applied during macro execution.
36 4043022 Rev B
Using DCM Macros
Requirements: The DCM.SwitchStreaming macro requires DCM device driver for

ROSA NMS version 3.0.15 or higher and DCM.py script version 1.4 or higher and
the DCM.SwitchStreamingTSWithFile macro needs DCM device driver for ROSA
NMS version 3.0.24 or higher and DCM.py script version 1.10 or higher.
Parameters
To execute a macro, the following information is required:
 The DCM (IDCM_ID or Device parameter) for which an outgoing transport
stream must be activated or stopped
affected by this macro
(DCM.switchStreamingTSWithFileForResourceSet macro only)
 The interface card slot position (ICardNr parameter) and port number (IPortNr
parameter) containing this outgoing transport stream (DCM.SwitchStreaming
macro only)
 The ON ID (IONID parameter) and TS ID (ITSID parameter) of the transport
stream (DCM.SwitchStreaming macro only)
 When the outgoing transport stream belongs to a GbE port, the destination IP
address (strIPAddress parameter) and UDP port (IUDPPort parameter)
(DCM.SwitchStreaming macro only)
 The path and name of the configuration file (File Location parameter)
(DCM.SwitchStreamingTSWithFile and
DCM.switchStreamingTSWithFileForResourceSet macro only)
 The streaming status (IStreamingOn or Streaming parameter)
- 1 : activating
- 0 : stopping
Configuration File
The following illustrations show the syntax of the data lines and an example of a
comma-delimited text file opened with Microsoft Excel.
4043022 Rev B 37
Note: For services on an ASI Interface Card, the IP Address and UDP Port field must
be empty.
Handling the Services Population of an Outgoing Transport Stream

Passing Incoming Services to an Outgoing Transport Stream
The DCM.AddService macro allows passing services to a particular outgoing
transport stream using ROSA's Macro Component. Therefore the following
information is required:
 The DCM containing the outgoing transport stream to which a service must be
passed (lDCM_ID parameter)
 The interface card slot position (IOutputBoard parameter) and port number
(IOutputPort parameter) containing this outgoing transport stream
 The ON-ID (IOutONID parameter) and TS-ID (IOutTSID parameter) of this
outgoing transport stream
 For an outgoing transport stream on a GbE Interface Card, the destination IP
Address (strOutIPAddress parameter) and UDP Port (IOutUDPPort parameter)
of this outgoing transport stream
 The SID (IOutSID parameter) for this outgoing service
38 4043022 Rev B
Using DCM Macros
 The interface card slot position (IInputBoard parameter) and port number
(IInputPort parameter) of the incoming transport stream to which the service
belongs to.
 The ONID (IInONID parameter) and TSID (IInTSID parameter) of this
incoming transport stream
 For an incoming transport stream on a GbE Interface Card, the destination IP
address (strInIPAddress parameter) and UDP port (IInIPAddress parameter) of
this incoming transport stream
 The service identifier (IInSID parameter) of the incoming service that must be
passed to the outgoing transport stream
Requirements: The DCM.AddService macro requires DCM device driver for ROSA
Removing Services from an Outgoing Transport Stream

The DCM.RemoveServices macro allows removing services from a particular outgoing
transport stream using ROSA's Macro Component. Therefore the following
information is required:
 The DCM containing the outgoing transport stream from which a service must
be removed (lDCMID parameter)
 The interface card slot position (IBoardID parameter) and port number (IPortID
parameter) containing this outgoing transport stream
 The ON-ID (IONID parameter) and TS-ID (ITSID parameter) of this outgoing
transport stream
 For an outgoing transport stream on a GbE Interface Card, the destination IP
address (strIPAddress parameter) and UDP Port (IUDPPort parameter) of this
outgoing transport stream
 The SIDs (strSIDs parameter) of the services that must be removed (the SIDs
must be separated by a ; ).
Requirements: The DCM.RemoveServices macro requires DCM device driver for
ROSA NMS version 3.0.17 or higher and DCM.py script version 1.5 or higher.
Starting and Stopping a Splicing Event

To Start a Splicing Event
To start a splicing event, the following macros can be used:
 DCM.startSplice: Triggers a manual Primary to Insertion Channel substitution for a
Splicing Channel on a particular DCM.
 DCM.startSpliceForResourceSet: Triggers a manual Primary to Insertion Channel
4043022 Rev B 39
substitution for a Splicing Channel on multiple DCM devices.

 DCM.editAndStartSplice: Change the Insertion Channel of a Splicing Channel and
triggers a manual Primary to Insertion Channel substitution for this Splicing
Channel on a particular DCM.
 DCM.editAndStartSpliceForResourceSet: Change the Insertion Channel of a Splicing
Channel and triggers a manual Primary to Insertion Channel substitution for this
Splicing Channel on multiple DCM devices.
Requirements: These macros require DCM device driver for ROSA NMS version
3.0.19 or higher and DCM.py script version 1.8 or higher.
Parameters
Before a splicing event macro can be executed, the following information is required:
 DCM.startSplice macro
- The name of the DCM affected by this macro (Device parameter)
- The slot position of the interface card where the Splicing Channel is located
(Board parameter)
- The name of the Splicing Channel for which a Primary to Insertion Channel
substitution must be triggered (Name parameter)
 DCM.startSpliceForResourceSet macro
- The name of the resource set containing the DCM devices affected by this
macro (Devices parameter)
(Board parameter)
- The name of the Splicing Channel for which a Primary to Insertion Channel
 DCM.editAndStartSplice macro
- The name of the Splicing Channel (Splice Name parameter)
- The slot number of the interface card where the Splicing Channel is located
(Board parameter)
- The slot number of the interface card where the new Insertion Channel is
located (InsBoardID parameter)
- The port number of the new Insertion Channel (InsPortID parameter)
- For a new Insertion Channel on a GbE Interface Card, the destination IP
address (InsIPAddress parameter) and UDP Port (InsUDPPort parameter) of
this Insertion Channel
40 4043022 Rev B
Using DCM Macros
- The SID of the new Insertion Channel (InsSID parameter)

 DCM.editAndStartSpliceForResourceSet macro
- The slot number of the interface card where the Splicing Channel is located
(Board parameter)
- The name of the Splicing Channel (SpliceName parameter)
- The slot number of the interface card where the new Insertion Channel is
located (InsBoardID parameter)
- The port number of the new Insertion Channel (InsPortID parameter)
- For a new Insertion Channel on a GbE Interface Card, the destination IP
address (InsIPAddress parameter) and UDP Port (InsUDPPort parameter) of
this Insertion Channel
- The SID of the new Insertion Channel (InsSID parameter)
Notes
 The Splicing Channels has to be configured correctly (Splicing Channel Mode
parameter set to Manual)
 All devices in the resource set for the DCM.startSpliceForResourceSet or
DCM.editAndStartSpliceForResourceSet macro must have the same configuration.
To Stop Splice Events

Stopping a splicing event can be done by executing one of the following macros:
 DCM.stopSplice: Triggers a manual Insertion to Primary Channel substitution for a
Splicing Channel on a particular DCM.
 DCM.stopSpliceForResourceSet: Triggers a manual Insertion to Primary Channel
substitution for a Splicing Channel on multiple DCM devices.
Requirements: These macros require DCM ROSA NMS driver 3.0.19 or higher and
DCM.py script 1.8 or higher.
Parameters
To trigger an Insertion to Primary Channel substitution, the following information is
required:
 DCM.stopSplice macro
(Board parameter)
4043022 Rev B 41
- The name of the Splicing Channel for which an Insertion to Primary Channel
 DCM.stopSpliceForResourceSet macro
(BoardID parameter)
- The name of the Splicing Channel for which an Insertion to Primary Channel
substitution must be triggered (Splice Name parameter)
Notes
 The splicing channels has to be configured correctly (Splicing Channel Mode
parameter set to Manual)
 All devices in the resource set for the DCM.startSpliceForResourceSet or
DCM.editAndStartSpliceForResourceSet macro must have the same configuration.
Logo Insertion
Assigning a Keyer ID to a Logo
The DCM.SetKeyerIDToLogoForResourceSet macro allows assigning a keyer ID to the
logo present in services for particular DCM devices.
Requirements
 This macro requires ROSA NMS version 4.0 or higher, DCM device driver for
ROSA NMS version 4.0.12 or higher, and DCM.py script version 1.23 or higher.
 The configuration file specifying the services should be present on the computer
running the ROSA NMS server software.
Parameters
The following information is required to execute this macro.
 The name of the resource set (Resource Set parameter) containing the DCM
devices affected by this macro
 The slot position of the DCM housing in which the Transcoder Card is installed
(Processor Board ID parameter).
 The name of the logo for which the keyer ID should be set (Logo Cfg. Name
parameter).
 The value for the keyer ID (Keyer ID parameter). This parameter can be set
between 0 and 8. 0 means that the assigned keyer ID will be removed.
 Logo Cfg. Source parameter: 0 or 1. 0 means Local and 1 means SCTE35.
42 4043022 Rev B
Using DCM Macros
 The full path of the configuration file (File Location parameter).

Configuration File: The configuration file that specifies the affected services is
similar to the one for the DCM.setBackupRevertiveModeWithFile macro, see topic
Changing the Service Backup Revertive Mode on page 52.
Modifying the Font Library

The DCM.AddFontLibraryForResourceSet macro allows adding fonts to the font library
of particular DCM devices.
Requirements
 The font file must be present on the computer running the ROSA NMS server
software.
Parameters
The following information is required for executing this macro.
 The name for the font (Font Cfg. Name parameter)
 The path of the font file (File Location parameter)
Modifying the Logo Library

The following macros can be used to modify the logo library of DCM devices:
 DCM.AddToLogoLibraryForResourceSet: Adds logos with specified configuration
to the logo library of the DCM devices that are specified in a resource set.
 DCM.UpdateInLogoLibraryForResourceSet: Updates parameters (like X position, Y
position, opacity...) of logos belonging to the logo library of the DCM devices
that are specified in a resource set. The logo file can only be changed for logos
that were remotely uploaded.
 DCM.DeleteFromLogoLibraryForResourceSet: Removes logos from the logo library
of the DCM devices that are specified in a resource set.
 DCM.SetLogoFileNumberToLogoForResourceSet: Assigns a logo file number to a
specific logo that is present in the logo library of particular DCM devices.
Requirements
 The DCM.AddToLogoLibraryForResourceSet macro needs ROSA NMS version 4.0
or higher, DCM device driver for ROSA NMS version 4.0.10 or higher, and
 The DCM.UpdateInLogoLibraryForResourceSet and
4043022 Rev B 43
DCM.DeleteFromLogoLibraryForResourceSet macro require ROSA NMS version 4.0

or higher, DCM device driver for ROSA NMS version 4.0.10 or higher, and
 The DCM.SetLogoFileNumberToLogoForResourceSet macro requires ROSA NMS
version 4.0 or higher, DCM device driver for ROSA NMS version 4.0.10 or
higher, and DCM.py script 1.23 or higher.
 For the DCM.UpdateInLogoLibraryForResourceSet and
DCM.DeleteFromLogoLibraryForResourceSet macro, the devices in the resource set
must have the same configuration to work.
Parameters
The following information is needed to modify logo library of DCM devices using
macros.
 For the DCM.AddToLogoLibraryForResourceSet and
DCM.UpdateInLogoLibraryForResourceSet macro, the path of the configuration file
(File Location parameter)
 For the DCM.DeleteFromLogoLibraryForResourceSet macro, the name of the logo
that should be removed (Logo Cfg. Name parameter)
 For the SetLogoFileNumberToLogoForResourceSet macro, the name of the logo and
the logo file number (Logo File Number parameter). A number can be given
between 0 and 16. 0 removes the mapping between the logo file number and the
logo.
Configuration Files
 DCM.AddToLogoLibraryForResourceSet macro
During adding logos to the logo library of DCM devices, the settings of the logos
which are specified into a configuration file are offered to the devices. The
following illustrations show the syntax of the data lines and an example of a
44 4043022 Rev B
Using DCM Macros
The following list explains the settings of the logo in a data line of a
configuration file.
- Logo Name: The name for the logo.
- X position: The number of pixels (even number) between the top of the logo
and the top of the video frame.
- Y position: The number of pixels (even number) between the left edge of the
logo and the left edge of the video frame.
- Opacity (%): The amount of opacity the logo must have. This parameter can
be changed in steps of 0.5%. 100% means that the logo is not transparent.
- Default Show: 0 or 1. 1 means that the logo will directly be inserted after
assigning.
- Fade In (frames): The number of frames in which the logo must fade in. A
value can be given between 0 and 300 frames.
- Fade Out (frames): The number of frames in which the logo must fade out. A
- Animated Logo: 0 or 1. 0 for a static logo and 1 for an animated logo.
- Playout Mode: 0 or 1 (for an animated logo only). 0 (normal) means that the
animated logo will be played in forward direction and 1 (palindrome) means
that the animated logo will be played successively in forward direction and
then in reverse direction.
- Loop Count: The number of times the logo will be played. 0 means that the
animated will be played continuously.
- Remote Logo: 0 or 1. 0 means that the logo is locally present and 1 (remote
logo) means that the logo will be downloaded when the logo is activated.
- Url Remote Logo: The URL from where the logo should be downloaded
4043022 Rev B 45
followed by / and file name of the logo

- Logo File Path: The location on the computer running the ROSA NMS
software from where the logo must be loaded followed by \ and the file
name of the logo
 DCM.UpdateInLogoLibraryForResourceSet macro
Changing logo settings using the Macro Component will be done by applying
particular settings which are specified into a configuration file. The following
illustrations show the syntax of the data lines and an example of a comma-
delimited text file opened with Microsoft Excel.
The following list explains the logo settings:

- Existing Logo Name: The name of the logo that is already present in the
library.
- Logo Name: The new name for the logo.
- X position: The number of pixels (even number) between the top of the logo
and the top of the video frame.
- Y position: The number of pixels (even number) between the left edge of the
logo and the left edge of the video frame.
- Opacity (%): The amount of opacity the logo must have. This parameter can
be changed in steps of 0.5%. 100% means that the logo is not transparent.
46 4043022 Rev B
Using DCM Macros
- Default Show: 0 or 1. 1 means that the logo will directly be inserted after
assigning.
- Fade In (frames): The number of frames in which the logo must fade in. A
- Fade Out (frames): The number of frames in which the logo must fade out. A
- Url Remote Logo: The URL from where the new logo should be downloaded
followed by / and file name of the new logo. For logos that are uploaded
from the computer running the ROSA NMS software or when no new logo
must be selected, this parameter should be empty.
Adding and Removing Logos to or from Services

The DCM.AddLogoToServicesForResourceSet macro adds a logo to particular services
of the DCM devices that are specified in a resource set. The
DCM.RemoveLogoFromServicesForResourceSet macro removes the logo from the
particular services of the DCM devices, which are specified in a resource set.
Requirements: These macro need ROSA NMS version 4.0 or higher, DCM device
driver for ROSA NMS version 4.0.12 or higher, and DCM.py script 1.23 or higher.
Parameters
For adding or removing logos from the logo library of DCM devices using ROSA
NMS macros, the following information is required:
 The slot position in the DCM housing of the corresponding Transcoder Card
(Processor Board ID parameter)
 The name of the logo that should be added or removed (Logo Cfg. Name
parameter)
 The path of the configuration file (File Location parameter)
Configuration File: The configuration file containing the services is similar to the
configuration file that is used for the DCM.setBackupRevertiveMode macro, see topic
Replacing Logos
The DCM.ReplaceLogoForResourceSet macro replaces an existing logo by a new logo,
adds this new logo to a particular service, and sets the logo file number and keyer ID
for particular DCM devices.
The operations that will be executed with this macro are:
1 Removes the existing logo from the specified services.
4043022 Rev B 47
2 Removes the existing logo from the logo library.

3 Adds the new logo to the library.
4 Sets the logo file number to this new logo.
5 Adds the new logo to the specified services.
6 Sets the keyer ID to the new logo that is present in the specified services.
Notes
 If one of these operations fails, the macro will proceed with the remaining
operations.
 During executing this macro, the logo information is applied to the services as
specified into configuration files. Note that only the first logo entry in the logo
configuration file will be processed.
Requirements
 This macro requires ROSA NMS version 4.0 of higher, DCM device driver for
 The configuration file with logo information as well as the configuration file that
specifies the services should be present on the computer that runs the ROSA
NMS server software.
Parameters
To execute this macro, the following information is needed.
devices affected by this macro.
 The slot position of the DCM housing in which the Transcoder Card is installed
(Processor Board ID parameter).
 The name of the logo that needs to be replaced (Existing Logo Cfg Name
parameter).
 The full path of configuration file with logo information (Logo Cfg. File Location
parameter)
 The logo file number that must be assigned to the new logo (Logo File Number
parameter). A number can be given between 0 and 16. 0 removes the mapping
between the logo file number and the logo.
 The full path of a configuration file that specifies the services (Services File
Location parameter).
 Keyer ID parameter: The keyer that needs to be set. (Range 0 up to 8)
 Logo Cfg. Source parameter: 0 or 1. 0 means local and 1 means SCTE35.
48 4043022 Rev B
Using DCM Macros
Configuration Files: The configuration file containing the logo information is similar
to the one for the DCM.AddToLogoLibraryForResourceSet macro, see topic Modifying
the Logo Library on page 43 and the configuration file that specifies the services is
similar to the one for the DCM.setBackupRevertiveModeWithFile macro, see topic
Starting Banner/EAS Insertion

The following macros can be used to start a banner or EAS insertion.
 DCM.StartEASForResourceSet: Starts an EAS message on the DCM devices that
are specified in a resource set. The identification parameters of the services
specified into a configuration file are applied during macro execution.
 DCM.StartBannerForResourceSet: Starts a banner on particular services of the
DCM devices that are specified in a resource set.
 DCM.StartBannerInAllServicesForResourceSet: Starts a banner on all the services of
the DCM devices that are specified in a resource set.
Requirements
 These macros require ROSA NMS version 4.0 or higher, DCM device driver for
ROSA NMS version 4.0.10 or higher, and DCM.py script 1.22 or higher.
 For the DCM.StartBannerInAllServicesForResourceSet and
DCM.StartBannerForResourceSet macro, all DCM devices in the resource set must
have the same configuration.
Parameters
The following information is needed to execute a macro:
 For DCM.StartBannerForResourceSet and
DCM.StartBannerInAllServicesForResourceSet macro
- The name of the resource set (Resource Set Name parameter) containing the
DCM devices affected by this macro
- The slot position of the Transcoder Card (Processor Board parameter)
containing the service(s) for which banner insertion must be started
- The name of the banner that should be used (Banner Cfg. Name parameter)
- The text message for the banner (Banner Text parameter)
- The time that the banner must be inserted into the video stream of the
services (Banner timeout parameter expressed in seconds)
- For the DCM.StartBannerForResourceSet macro, the path of the configuration
file (File Location parameter)
 For the DCM.StartEASForResourceSet macro
- The name of the resource set (Resource Set Name parameter) containing the
4043022 Rev B 49

- The SAME code of alert (SAME Code parameter)
- The text message for the alert (Alert Text parameter)
- The time the EAS alert must be inserted into the video streams of the services
(Time Out parameter).
Configuration File
Notes:
 The parameters to specify the service are the identification parameters of the
corresponding incoming service.
 For services on an ASI Interface Card, the IP Address and UDP Port field must
be empty.
Stopping Banner Insertions

To stop an active banner, the following macros can be used:
 DCM.StopBannerForResourceSet: Stops any active banner (and EAS) on the
specified services of the DCM devices that are specified in a resource set. The
identification parameters of the services specified into a configuration file are
applied during macro execution. This configuration file is similar to the
50 4043022 Rev B
Using DCM Macros
configuration file used for starting banner insertion, see topic Starting
Banner/EAS Insertion on page 49.
 DCM.StopBannerInAllServicesForResourceSet: Stops any active banner (and EAS)
on all services of the DCM devices that are specified in a resource set.
 DCM.StopAllBannersForResourceSet: Stops all banners on all services of the DCM
devices that are specified in a resource set. This will stop any active banner (and
EAS) on any Transcoder Card.
Requirements
 The DCM.StopBannerForResourceSet macro needs ROSA NMS version 4.0 or
higher, DCM device driver for ROSA NMS version 4.0.9 or higher, and DCM.py
script version 1.22 or higher.
 The DCM.StopBannerInAllServicesForResourceSet and
DCM.StopAllBannersForResourceSet macro require ROSA NMS version 4.0 or
higher, DCM device driver for ROSA NMS version 4.0.10 or higher, and DCM.py
script version 1.22 or higher.
 All DCM devices in the resource set must have the same configuration.
Parameters
Before executing a macro, the following information may be required:
devices affected by this macro.
 The slot position of the Transcoder Card (Processor Board parameter) containing
the service(s) for which banner insertion must be stopped
(DCM.StopBannerForResourceSet macro only).
Using Macros for Service Backup

Configuring Service Loss Alarm Triggers
The triggers used to activate a Service Loss alarm can be configured using the
following macros:
 DCM.ASIServiceLossTriggers: Changes the Service Loss alarm triggers for a
particular service on an ASI Interface Card of a single DCM.
 DCM.ASIServiceLossTriggersForResourceSet: Changes the Service Loss alarm
triggers for a particular service on an ASI Interface Card of multiple DCM
devices.
 DCM.GBEServiceLossTriggers: Changes the Service Loss alarm triggers for a
particular service on a GbE Interface Card of a single DCM.
4043022 Rev B 51
 DCM.GBEServiceLossTriggersForResourceSet: Changes the Service Loss alarm

triggers for a particular service on a GbE Interface Card of multiple DCM
devices.
Parameters
Before a macro can be executes, the following information is required:
 The name of the device (Device parameter) affected by the
DCM.ASIServiceLossTriggers or DCM.GBEServiceLossTriggers macro
affected by the DCM.ASIServiceLossTriggersForResourceSet or
DCM.GBEServiceLossTriggersForResourceSet macro
 The slot position of the interface card (Board parameter) and the number of the
port (Port parameter) containing the service for which the Service Loss alarm
triggers should be changed
 The SID of this service (Service Id parameter)
 The triggers to be enabled or disabled. When the Enabled Triggers parameter is
set to 0, all triggers will be disabled. When this parameter is set to 1, the triggers
will be enabled or disabled as specified in the corresponding triggers (1 enables
the trigger and 0 disables the trigger).
These triggers are:
- for a GbE Interface Card: UDP Stream Loss alarm (Enable UDP Stream Loss
parameter), Missing in PAT alarm (Enable Missing PAT parameter), PMT
Error alarm (Enable PMT Error parameter), and PID Error alarm (Enable
PID Error parameter)
- for an ASI Interface Card: TS Sync Loss alarm (Enable ASI Sync Loss
parameter), Missing in PAT alarm (Enable Missing PAT parameter), PMT
Error alarm (Enable PMT Error parameter), and PID Error alarm (Enable
PID Error parameter)
Notes:
 The Service Loss - Mode parameter must be set to Specific using the user
interface of the DCM.
 All DCM devices in the resource set must have the same configuration.
Changing the Service Backup Revertive Mode

The following macros can be used to change the service backup revertive mode for
one or more services:
 DCM.setBackupRevertiveMode: Changes the revertive mode for a service on a
52 4043022 Rev B
Using DCM Macros
single DCM.
 DCM.setBackupRevertiveModeForAllServicesOnBoard: Changes the revertive mode
for all services of a particular interface card on a single DCM.
 DCM.setBackupRevertiveModeForAllServicesOnDevice: Changes the revertive mode
for all services on a single DCM.
 DCM.setBackupRevertiveModeForAllServicesOnPort: Changes the revertive mode
for all services of a particular port on a single DCM.
 DCM.setBackupRevertiveModeForAllServicesOnTS: Changes the revertive mode for
all services of a particular transport stream on a single DCM.
 DCM.setBackupRevertiveModeForResourceSet: Changes the revertive mode for a
service on multiple DCM devices.
 DCM.setBackupRevertiveModeForAllServicesOnBoardForResourceSet: Changes the
revertive mode for all services of a particular interface card on multiple DCM
devices.
 DCM.setBackupRevertiveModeForAllServicesOnDeviceForResourceSet: Changes the
revertive mode for all services on multiple DCM devices.
 DCM.setBackupRevertiveModeForAllServicesOnPortForResourceSet: Changes the
revertive mode for all services of a particular port on multiple DCM devices.
 DCM.setBackupRevertiveModeForAllServicesOnTSForResourceSet: Changes the
revertive mode for all services of a particular transport stream on multiple DCM
devices.
 DCM.setBackupRevertiveModeWithFile: Changes the revertive mode for all services
described in the configuration file.
Requirements: DCM.setBackupRevertiveMode and
DCM.setBackupRevertiveModeForResourceSet macros require DCM device driver for
ROSA NMS version 3.0.19 or higher and DCM.py script version 1.8 or higher.
DCM.setBackupRevertiveModeWithFile macro requires DCM device driver for ROSA
Parameters
 The name (Device parameter) of the DCM affected by this macro
 The slot position of the interface card (Board parameter) containing the service(s)
for which the Service Loss alarm triggers should be changed
 The number of the port (Port parameter) containing the service(s) for which the
Service Loss alarm triggers should be changed
4043022 Rev B 53
 The destination IP address (IP Address parameter) and UDP port number (UDP
Port parameter) of the transport stream for which the revertive mode for all
services must be changed
 The SID (Service ID parameter) of the service for which the revertive mode must
be changed
 The revertive mode (Revertive Mode ON or Revertive Mode Enabled
parameter), 1 = enabled and 0 = disabled
The following table shows the parameters for the different macros.
Note: All DCM devices in a ...ResourceSet macro must have the same configuration.
Configuration File
54 4043022 Rev B
Using DCM Macros
Note: For services on an ASI Interface, the IP address and UDP Port field must be
empty.
Triggering a Service Backup Transition

The following macros can be used to trigger a main-to-backup or backup-to-main
service transition:
 DCM.activateMainOrBackupService: Triggers a service backup transition for a
service on a single DCM.
 DCM.activateMainOrBackupServiceForAllServicesOnBoard: Triggers a service
backup transition for all services of a particular interface card on a single DCM.
 DCM.activateMainOrBackupServiceForAllServicesOnDevice: Triggers a service
backup transition for all services on a single DCM.
 DCM.activateMainOrBackupServiceForAllServicesOnPort: Triggers a service backup
transition for all services of a particular port on a single DCM
 DCM.activateMainOrBackupServiceForAllServicesOnTS: Triggers a service backup
transition for all services of a particular transport stream on a single DCM.
 DCM.activateMainOrBackupServiceForResourceSet: Triggers a service backup
transition for a service on multiple DCM devices.
 DCM.activateMainOrBackupServiceForAllServicesOnBoardForResourceSet: Triggers
a service backup transition for all services of a particular interface card on
multiple DCM devices.
 DCM.activateMainOrBackupServiceForAllServicesOnDeviceForResourceSet: Triggers
4043022 Rev B 55
a service backup transition for all services on multiple DCM devices.

 DCM.activateMainOrBackupServiceForAllServicesOnPortForResourceSet: Triggers a
service backup transition for all services of a particular port on multiple DCM
devices.
 DCM.activateMainOrBackupServiceForAllServicesOnTSForResourceSet: Triggers a
service backup transition for all services of a particular transport stream on
multiple DCM devices.
 DCM.activateMainOrBackupServiceWithFile: Triggers a service backup transition
for all services specified in the configuration file.
Parameters
 The slot position of the interface card (Board parameter) containing the service(s)
for which a service backup trigger must be given
 The number of the port (Port parameter) containing the service(s) for which a
service backup trigger must be given
 The destination IP address (IP Address parameter) and UDP port number (UDP
Port parameter) of the transport stream for which a service backup trigger for all
services must be given
 The SID (Service ID parameter) of the service for which a service backup trigger
must be given
 The activate main mode (ActivateMain or Main On parameter), 1 = main active
and 0 = backup active
56 4043022 Rev B
Using DCM Macros
The following table shows the parameters for the different macros.
Note: All DCM devices in a ...ResourceSet macro must have the same configuration.
Configuration File
The following pictures show the syntax of the data lines and an example of a
4043022 Rev B 57
Note: For services on an ASI Interface, the IP address and UDP port field must be
empty.
Hint: For more information concerning configuration files, please refer to topic
Creating a Configuration File on page 26.
Transport Stream Backup

Configuring the TS Loss Triggers
The transport stream loss (TS Loss) alarm that is used to trigger a transport stream
backup transition can be configured by executing the DCM.SetGbETSLossTriggers
macro. During executing this macro, the TS Loss triggers for several transport
streams, as specified into a configuration file, are applied.
driver for ROSA NMS version 4.0.25 or higher, DCM software package version 07.01
or higher, and DCM.py script-1.31 or higher.
Parameters
To execute this macro, the following information is required:
 The name of the DCM that is given during mapping the device in ROSA NMS
(DCM resource parameter).
 The path and name of the configuration file (CSV File name with full path
parameter).
58 4043022 Rev B
Using DCM Macros
Configuration File
The following list describes the settings of an entry.

 Board: The slot position in the housing where the interface card is installed that
receives the corresponding transport stream
 Port: The number of the GbE port that receives this transport stream
 IP Address: The destination IP address of this incoming transport stream
 UDP Port: The UDP port number of this transport stream
4043022 Rev B 59
 Enabled: 0 or 1. 0 means that all individual transport stream triggers are disabled
and 1 means that individual triggers can be set.
 Link Loss: 0 or 1. 0 means that the trigger is enabled and 1 means disabled.
 UDP Loss: 0 or 1. 0 means that the trigger is enabled and 1 means disabled.
 Service Loss: 0 or 1. 0 means that the trigger is enabled and 1 means disabled.
 UDP Stream Loss: 0 or 1. 0 means that the trigger is enabled and 1 means
disabled.
 PAT Error: 0 or 1. 0 means that the trigger is enabled and 1 means disabled.
Triggering a Transport Stream Backup Trigger

To force a main-to-backup or backup-to-main transport stream transition, the
following macros can be used:
 DCM.activateMainOrBackupTS: allows triggering a transition for a single
transport stream.
 DCM.activateMainOrBackupTSWithFile: allows triggering a transition for multiple
transport streams. The transport streams for which a transition must be triggered
should be specified in the configuration file.
 DCM.activateAndMonitorMainOrBackupTSWithFile: starts a transition for multiple
transport streams and a TS in Backup message will be logged on a monitoring
device. The purpose of this macro is having directly feedback whether the main
or backup TS is active. The severity level of the messages that are logged on the
monitoring device is Warning and the behavior Cleared by System. The transport
streams for which a transition must be triggered should be specified in the
configuration file.
To have a successful transition, the backup transport stream(s) for the concerning
input transport stream(s) must properly be configured using the user interface of the
DCM.
Parameters
To execute a macro, the following information is required:
 The interface card slot position (Board parameter) and port number (Port
parameter) containing the transport stream for which a transition must be
triggered (DCM.activateMainOrBackupTS macro only)
 When the transport stream belongs to a GbE port, the destination IP address (IP
Address parameter) and UDP port (UDP Port parameter)
(DCM.activateMainOrBackupTS macro only)
60 4043022 Rev B
Using DCM Macros
 The path of the configuration file (File Location parameter) (...WithFile macros
only)
 The transition status (Main On parameter)
- 1 : main activated (backup-to-main transition)
- 0 : main deactivated (main-to-backup transition)
 The resourceID (Monitor parameter) of the monitoring system on which
messages must be logged.
Configuration File
Note: For services on an ASI Interface Card, the IP address and UDP port field must
be empty.
4043022 Rev B 61
Joining GbE Port Pairs to a Multicast Group

The following macros can be used to join GbE port pairs of a GbE Interface Card to a
multicast group:
 DCM.joinMulticastStream: joins a GbE port to a multicast group.
 DCM.joinMulticastStreamWithFile: joins GbE ports to multicast groups as
specified in the configuration file.
 DCM.joinMulticastStreamWithFileForResourceSet: joins GbE ports to multicast
groups as specified in the configuration file for multiple DCM's.
3.0.30 or higher and, DCM.py script version 1.17 or higher.
Parameters
 The name (DCM Unit parameter) of the DCM affected by this macro
 The name of the resource set (ResourceSet Name parameter) containing the
 The slot position of the GbE Interface Card (Board ID parameter) containing the
GbE port pairs that must be joined
(DCM.joinMulticastStream and DCM.joinMulticastStreamWithFile macro only)
 The ID of the GbE port pair (Port Pair ID parameter), 0 for port pair 1-2 and 2 for
port pair 3-4
(DCM.joinMulticastStream macro only)
 The VLAN ID (VLAN ID parameter) corresponding the VLAN port pair
 The Ip address (Multicast IP Address parameter) of the multicast group
 The source filtering (Filter parameter)
- Include: adds the IP address(es) to the include list of sources. An Include
source list contains the IP addresses from which multicast reception is
allowed.
- Exclude: adds the IP address(es) to exclude list of sources. An Exclude source
list contains the IP addresses from which multicast reception is not allowed.
 The IP address(es) (Source IP Address parameter) that must be added to the
Include or Exclude source list.
62 4043022 Rev B
Using DCM Macros
 The path and name of the configuration file (CSV File name with full path
parameter) (DCM.joinMulticastStreamWithFile and
DCM.joinMulticastStreamWithFileForResourceSet macro only)
Configuration File
Hint: Multiple source IP addresses must be separated by a "/", a range of IP

addresses by a "_", for example: a range between 10.0.0.1 and 10.0.0.10 can be given
by 10.0.0.1_10.
Modifying the Unsolicited IGMP Message Version Parameter

The following macros can be used to modify the Unsolicited IGMP Message Version
parameter of GbE Interface Card:
 DCM.setUnsolicitedIGMPMsgVersion macro: modifies Unsolicited IGMP Message
Version parameter
4043022 Rev B 63
 DCM.setUnsolicitedIGMPMsgVersionForResourceSet macro: Unsolicited IGMP

Message Version parameter for multiple DCM's
Requirements: These macros require ROSA NMS version 4.0 or higher, DCM device
driver for ROSA NMS version 3.0.30 or higher, and DCM.py script version 1.17 or
higher.
Parameters
 The name (DCM Unit parameter) of the DCM affected by this macro
 The slot position of the GbE Interface Card (Board ID parameter)
 The Unsolicited IGMP Message version (IGMP Version parameter), 2 or 3
Retrieving IGMP Settings from Devices

The list with interfaces that are joined to multicast groups can be downloaded from a
DCM. The DCM.RetrieveIGMPSettings macro can be used to fetch the IGMP join
settings of a single DCM and the DCM.RetrieveIGMPSettingsForResourceSet macro for
settings of multiple DCM devices. The IGMP join settings are stored on a specified
location on the computer running the ROSA NMS server software. Note that the full
path must already be present on this computer.
Requirements: The DCM.RetrieveIGMPSettings macro needs ROSA NMS version 4.0
or higher, DCM device driver for ROSA NMS version 4.0.8 or higher for ROSA NMS
and, DCM.py script 1.21 or higher and the DCM.RetrieveIGMPSettingsForResourceSet
macro ROSA NMS version 4.0 or higher, DCM device driver for ROSA NMS version
4.0.8 or higher, and DCM.py script 1.24 or higher.
Parameters
For executing these macros, the Macro Component needs the following information.
 The device (DCM Unit ID parameter) for which the IGMP Join settings must be
downloaded (DCM.RetrieveIGMPSettings macro).
 The name of the ResourceSet (StrResourceSet Name parameter) containing the
DCM devices (DCM.RetrieveIGMPSettingsForResourceSet macro)
 The path where the file should be stored (StrPath parameter).
64 4043022 Rev B
Using DCM Macros
Configuration File
The following picture depicts an example of a DCM_IGMP_Settings.csv file created
by the DCM.retrieveIGMPSettings macro and opened with Microsoft Excel.
The following list describes the settings of an IGMP join entry.

- #Card: Slot position of the housing in which the card is installed.
- Port: 0 or 2. 0 for port pair 1-2 and 2 for port pair 3-4.
- VLAN ID: The VLAN ID to which the port corresponds to.
- Multicast: The multicast IP address to which the port is joined to.
- Filter: Include means that reception is allowed on the source IP addresses and
Exclude means that reception is not allowed on the source IP addresses.
- Source IP addresses: The source IP addresses for which reception is allowed
or not.
4043022 Rev B 65
The picture below shows an example of a DCM_IGMP_Settings.csv file created by

the DCM.RetrieveIGMPSettingsForResourceSet macro.
The entries are arranged by device and each device is indicated by its IP address.
Joining or Leaving Interfaces to or from Multicast Groups

The DCM.ReprogramIGMPSettings macro allows updating the IGMP settings table for
a GbE Interface Card or IP Video Gateway Card. Joining GbE ports to a multicast
group and leaving GbE ports from a multicast group are done according to the data
in the configuration file that is uploaded when the macro is executed.
Requirements
 The configuration file is present on the computer that runs the ROSA NMS
server software.
Parameters
The following information is required to execute this macro.
 The full path of the configuration file (StrFilePath parameter).
66 4043022 Rev B
Using DCM Macros
Configuration File
The data used to update the IGMP table is offered to a DCM by using a
configuration file. The best way to create such configuration file is to download the
settings from the DCM and to modify the retrieved file as described in previous
topic. The following picture depicts an example of such file opened with Microsoft
Excel. The entries are arranged by device and each device is indicated by its IP
address.
The following list describes the settings of an IGMP entry.

 #Card: Slot position of the housing in which the card is installed.
 Port: 0 or 2. 0 for port pair 1-2 and 2 for port pair 3-4.
 VLAN ID: The VLAN ID to which the port corresponds to.
 Multicast: The multicast IP address to which the port is joined to.
 Filter: Include means that reception is allowed on the source IP addresses and
Exclude means that reception is not allowed on the source IP addresses.
 Source IP addresses: The source IP addresses for which reception is allowed or
not.
4043022 Rev B 67
Configuring the D9036 Statmux Controller

Configuring the Statmux Community
For configuring a statmux community for a D9036 statmux application, the
DCM.setupSMCCommunity macro can be used. Note that the statmux community
settings of all D9036 encoders and the DCM(s) (main and backup device) belonging
to the same community must be the same.
driver version 4.0.17 or higher, DCM with software package version 9.00 or higher,
and DCM.py script version 1.27 or higher.
Parameters
The following information is required to execute this macro:
(Resource parameter).
 The slot number of the housing in which the GbE Interface Card is installed that
configured to be the D9036 statmux controller (BoardID parameter).
 The name for the statmux community (Community parameter).
 The multicast IP address for the statmux community (MulticastIP parameter).
The octets of the IP address must be separated by dots.
 UDP port number: The UDP port number for the community (UDPPort
parameter).
Adding Encoders to the Statmux Community

D9036 encoders can be added to the statmux community of a statmux controller by
executing the DCM.addD9036EncoderToSMC macro.
Requirements: This macro requires ROSA NMS version 4.0.9 or higher, DCM device
driver version 4.0.17 or higher, DCM software package version 9.00 or higher, and
DCM.py script-1.27 or higher.
Parameters
The parameters needed to execute the macro are:
(Resource parameter).
 The IP address of the D9036 Encoder (EncoderIPAddress parameter).
Handling Statmux Pools

For creating, updating, and deleting D9036 statmux pools, the following macros can
be used:
68 4043022 Rev B
Using DCM Macros
 DCM.createSMCPool
 DCM.updateSMCPool
 DCM.deleteSMCPool
Parameters
The following information is required to execute a macro.
 For the DCM.createSMCPool and DCM.updateSMCPool macro:
- The name of the DCM that is given during mapping the device in ROSA
NMS (Resource parameter).
- The name for the pool (PoolName parameter). A logical pool name facilitates
the identification of the statmux pool in the application. The length of the
name can be maximum 20 characters.
- The maximum bandwidth for the pool (Bandwidth parameter). This
bandwidth includes the sum of all video, audio, data, VBI, and metadata
component that will be carried in the transport stream.
- The amount of bandwidth that will be allocated for the non video
components of the VSEs line audio, data, PSI/SI/PSIP...
(BandwidthOverhead parameter)
- The maximum of VSEs that can be member of the statmux pool. This
parameter can be set between 1 and 16 (MaxVSECapacity parameter)
- During the statmux process the video bitrate of a VSE fluctuates between the
minimum and maximum bitrate that is assigned to that VSE in the pool. In
some cases, for instance for still picture video, the video encoding engine of
the D9036 is able to produce good quality video with bitrates lower than the
assigned minimum bitrate. When the GuaranteeMinRateMode parameter is
set to 0 (disabled), the encoding video engine of the D9036 is allowed to
produce video with a bitrate lower than this assigned minimum bitrate.
Setting this parameter to 1 enables this feature. Note that this parameter
applies to all VSEs in that pool and can't be set during creating.
 For the DCM.deleteSMCPool macro
- The name of the pool that should be removed from the statmux community
(PoolName parameter).
4043022 Rev B 69
Manipulating the Statmux Pool Population

The VSE population of a statmux pool can be manipulated by executing the
following macros:
 DCM.updateVSEInSMCPool
 DCM.addVSEInSMCPool
 DCM.deleteVSEInSMCPool
Parameters
The parameters needed to execute these macros are:
 For the DCM.updateVSEInSMCPool and DCM.addVSEInSMCPool macro
- The IP address of the D9036 encoder to which the VSE belongs or has to
belong (MgmtIP parameter).
- The name of the statmux pool to which the VSE belongs to or has to belong to
(PoolName parameter).
- The name of the VSE that should be added (VSEName parameter).
- The default bitrate determines the encoding rate of a VSE at which the
encoder starts after power up (DefBitrate parameter). Also, it determines the
rate the encoder settles to in the event of communication errors between the
IP statmux controller and the encoder, or when the IP statmux controller is
disconnected. The sum of the default bitrates for the active VSEs equals the
size of the pool bandwidth less the pool bandwidth overhead and total VSE
reserved bandwidth.
- The MinBitrate parameter determines the lower threshold of the window in
which the bitrate of the VSE can fluctuate during statmux
- The MaxBitrate parameter determines the upper threshold of the window in
which the bitrate of the VSE can fluctuate during statmux.
- The Priority parameter can be set to prioritize which VSE get access to
bandwidth if there is not enough bandwidth available. In normal
circumstances all VSEs will have the same priority setting but if a VSE has
consistently low action content (for instance a talk back show) a lower
priority can be allocated to that VSE, knowing that the VSE can perhaps
afford a reduction in picture quality from time to time. A value can be given
between 0 (lowest priority) and 6 (highest priority) and is by default set to 3.
70 4043022 Rev B
Using DCM Macros
 For the DCM.deleteVSEInSMCPool macro

- The IP address of the D9036 encoder to which the VSE belongs or has to
belong (MgmtIP parameter).
- The name of the pool to which the VSE belongs to (PoolName parameter).
- The name of the VSE that should be removed (VSEName parameter).
Note: If the VSE is not present in the statmux pool then macro will fail with an
error message.
Handling the VSE Backup List of the Statmux Community

The following macros can be used to manipulate the VSE backup list of the statmux
community.
 DCM.createSMCBackupList: Creates VSE entries in the VSE backup list of the
statmux community
 DCM.deleteSMCBackupListForVSE: Removes VSE backup entries from the VSE
backup list.
 DCM.deleteSMCBackupListForD9036: Removes VSE backup entries from the VSE
backup list for all main VSEs belonging to a particular D9036 encoder.
 DCM.deleteAllSMCBackupList: Removes all VSE backup entries from the VSE
backup list.
Requirements: These macros need ROSA NMS version 4.0.9 or higher, DCM device
driver for ROSA NMS version 4.0.17 or higher, DCM software package version 9.00
or higher, and DCM.py script version 1.27 or higher.
Parameters
The following parameters are required to execute the macros.
 For the DCM.createSMCBackupList macro:
- The IP address of the D9036 encoder to which the main VSE belongs to
(MainEncoderIPAddress parameter).
- The name of the main VSE (MainVSEName parameter)
- The IP address of the D9036 encoder to which the backup VSE belongs to
(BackupEncoderIPAddress parameter)
- The name of the VSE that has to act as backup VSE (BackupVSEName
parameter)
4043022 Rev B 71
Note: Both the main and the backup D9036 encoder must be member of the
statmux community.
 For the DCM.deleteSMCBackupListForVSE macro:
- The IP address of the D9036 encoder to which the main VSE belongs to for
which the entry must be deleted (MainEncoderIPAddress parameter)
- The name of the main VSE for which the entry should be deleted
(MainVSEName parameter).
The VSE backup entry will be removes from the VSE backup list that matches the
Main Encoder IP Address and Main Encoder VSE Name parameter.
 For the DCM.deleteSMCBackupListForD9036 macro:
- The IP address of the encoder containing the main VSEs for which the VSE
backup entries should be removed (MainEncoderIPAddress parameter).
All VSE entries with main VSE that belongs to the given encoder will be
removed.
 For the DCM.deleteAllSMCBackupList macro
Generating Test Messages

The DCM.GenerateTestMessage macro allows triggering particular DCM devices to
generate a test message.
Requirements: This macro requires ROSA NMS version 4.0.10 or higher, DCM
device driver for ROSA NMS version 4.0.21 or higher, DCM software package
version 03.00 or higher, and DCM.py script version 1.30 or higher.
Parameters
To execute this macro, the following information is required.
DCM devices
Importing the Device Configuration

For updating the DCM driver with latest information, the configuration of a DCM
can be uploaded using the DCM.LoadFullDeviceConfiguration macro.
72 4043022 Rev B
Using DCM Macros
Requirements: This macro requires ROSA NMS version 4.0.10 or higher, DCM
device driver for ROSA NMS version 4.0.20 or higher, DCM with software package
version 03.00 or higher, and DCM.py script version 1.29 or higher.
Parameters
The following information is required during executing this macro.
(lDCM_RESIS parameter).
Activating Alternate Services

The DCM.SwitchToAlternateSource macro allows activating an alternate service for a
particular outgoing service.
Requirements: This macro requires ROSA NMS version 4.0 or higher, DCM device
driver for ROSA NMS version 4.0.10 or higher, and DCM.py script version 1.22 or
higher.
Parameters
The following information is needed to execute this macro.
 The DCM device on which to operate (DCMUnit parameter)
 The slot position of the DCM housing in which the interface card is installed that
transmit the outgoing service (BoardID parameter).
 The number of the port that transmit this service (PortID parameter).
 The destination IP address of the outgoing transport stream to which this service
belongs to. For a service on an ASI Interface Card, keep this parameter empty (IP
Address parameter).
 The UPD port number of the outgoing transport stream to which this service
belongs to. For a service on an ASI Interface Card, keep this parameter empty
(UDP Port parameter).
 The service identifier of this service (Service ID parameter). This parameter can
be set between 0 and 65535.
 The slot position of the DCM housing in which the interface card is installed that
receives the alternate service (Alternate Src Board ID parameter).
 The number of the port that receives this alternate service (Alternate Src Port ID
parameter).
 The destination IP address of the incoming transport stream to which this
alternate service belongs to (Alternate Src IP Address parameter). For a service
on an ASI Interface Card, keep this parameter empty.(For ASI keep it empty)
 The UPD port number of the incoming transport stream to which this alternate
service belongs to (Alternate Src UDP Port parameter). For a service on an ASI
4043022 Rev B 73
Interface Card, keep this parameter empty.

 The service identifies of this alternate service (Alternate Src Service ID
parameter). This parameter can be set between 0 and 65535.
74 4043022 Rev B
A
Appendix A
Appx auto letter
Customer Information
Introduction
This appendix contains information on obtaining product support.
In This Appendix
 Product Support .................................................................................... 76
4043022 Rev B 75
Appendix A
Customer Information
Product Support
Obtaining Support
IF... Then...
you have general questions about this contact your distributor or sales agent for
product product information or refer to product data
sheets on www.cisco.com.
you have technical questions about this call the nearest Technical Support center or
product Cisco office.
you have customer service questions or call the nearest Customer Service center or Cisco
need a return material authorization office.
(RMA) number
Support Telephone Numbers

This table lists the Technical Support and Customer Service numbers for your area.
Region Centers Telephone and Fax Numbers
North America Cisco Services For Technical Support, call:
Atlanta, Georgia  Toll-free: 1-800-722-2009
United States  Local: 678-277-1120 (Press 2 at the prompt)
For Customer Service, call:
 Toll-free: 1-800-722-2009
 Local: 678-277-1120 (Press 3 at the prompt)
 Fax: 770-236-5477
 Email: customer-service@cisco.com
Europe, Belgium For Technical Support, call:
Middle East,  Telephone: 32-56-445-197 or 32-56-445-155
Africa  Fax: 32-56-445-061
 Telephone: 32-56-445-444
 Fax: 32-56-445-051
 Email: service-elc@cisco.com
Japan Japan  Telephone: 81-3-5908-2153 or +81-3-5908-2154
 Fax: 81-3-5908-2155
Korea Korea  Telephone: 82-2-3429-8800
 Fax: 82-2-3452-9748
 Email: songk@cisco.com
China (mainland) China  Telephone: 86-21-2401-4433
 Fax: 86-21-2401-4455
 Email: xishan@cisco.com
All other Asia Pacific Hong Kong  Telephone: 852-2588-4746
countries & Australia  Fax: 852-2588-3139
 Email: saapac-support@cisco.com
76 4043022 Rev B
Product Support
Region Centers Telephone and Fax Numbers

Brazil Brazil  Telephone: 11-55-08-9999
 Fax: 11-55-08-9998
 Email: fattinl@cisco.com or ecavalhe@cisco.com
Mexico, Mexico For Technical Support, call:
Central America,  Telephone: 52-3515152599
Caribbean  Fax: 52-3515152599
 Telephone: 52-55-50-81-8425
 Fax: 52-55-52-61-0893
 Email: sa-latam-cs@cisco.com
All other Argentina For Technical Support, call:
Latin America countries  Telephone: 54-23-20-403340 ext 109
 Fax: 54-23-20-403340 ext 103
 Telephone: 770-236-5662
 Fax: 770-236-5888
 Email: keillov@cisco.com
4043022 Rev B 77
B
Appendix B
Appx auto letter
Available Macros
Introduction
This appendix provides the list with macros available for the Digital
Content Manager platform.
In This Appendix
 DCM Macros.......................................................................................... 80
4043022 Rev B 79
Appendix B
Available Macros
DCM Macros
The following list gives the macros available for the DCM platform. Each macro is
accompanied with the page of the topic describing the macro.
 DCM.activateAndMonitorMainOrBackupTSWithFile, page 60
 DCM.activateMainOrBackupService, page 55
 DCM.activateMainOrBackupServiceForAllServicesOnBoard, page 55
 DCM.activateMainOrBackupServiceForAllServicesOnBoardForResourceSet, page 55
 DCM.activateMainOrBackupServiceForAllServicesOnDevice, page 55
 DCM.activateMainOrBackupServiceForAllServicesOnDeviceForResourceSet, page 55
 DCM.activateMainOrBackupServiceForAllServicesOnPort, page 55
 DCM.activateMainOrBackupServiceForAllServicesOnPortForResourceSet, page 55
 DCM.activateMainOrBackupServiceForAllServicesOnTS, page 55
 DCM.activateMainOrBackupServiceForAllServicesOnTSForResourceSet, page 55
 DCM.activateMainOrBackupServiceForResourceSet, page 55
 DCM.activateMainOrBackupServiceWithFile, page 55
 DCM.activateMainOrBackupTS, page 60
 DCM.activateMainOrBackupTSWithFile, page 60
 DCM.addD9036EncoderToSMC, page 68
 DCM.AddFontLibraryForResourceSet, page 43
 DCM.AddLogoToServicesForResourceSet, page 47
 DCM.AddService, page 38
 DCM.AddToLogoLibraryForResourceSet, page 43
 DCM.addVSEInSMCPool, page 70
 DCM.ApplyComponentRules, page 28
 DCM.ApplyComponentRulesEx, page 28
 DCM.ASIServiceLossTriggersForResourceSet, page 28
 DCM.createSMCBackupList, page 71
 DCM.createSMCPool, page 68
 DCM.deleteAllSMCBackupList, page 71
80 4043022 Rev B
DCM Macros
 DCM.DeleteFromLogoLibraryForResourceSet, page 43
 DCM.deleteSMCBackupListForD9036, page 71
 DCM.deleteSMCBackupListForVSE, page 71
 DCM.deleteSMCPool, page 68
 DCM.deleteVSEInSMCPool, page 70
 DCM.editAndStartSplice, page 39
 DCM.editAndStartSpliceForResourceSet, page 39
 DCM.GBEServiceLossTriggersForResourceSet, page 51
 DCM.GenerateTestMessage, page 72
 DCM.GetComponentRules, page 31
 DCM.ImportSIData, page 34
 DCM.joinMulticastStream, page 62
 DCM.joinMulticastStreamWithFile, page 62
 DCM.joinMulticastStreamWithFileForResourceSet, page 62
 DCM.LoadFullDeviceConfiguration, page 72
 DCM.RemoveLogoFromServicesForResourceSet, page 47
 DCM.RemoveRules, page 31
 DCM.RemoveRulesEx, page 31
 DCM.RemoveServices, page 39
 DCM.RemoveSIData, page 35
 DCM.ReplaceLogoForResourceSet, page 47
 DCM.ReprogramIGMPSettings, page 66
 DCM.retrieveIGMPSettings, page 64
 DCM.RetrieveIGMPSettingsForResourceSet, page 64
 DCM.setBackupRevertiveMode, page 52
 DCM.setBackupRevertiveModeForAllServicesOnBoard, page 52
 DCM.setBackupRevertiveModeForAllServicesOnBoardForResourceSet, page 52
 DCM.setBackupRevertiveModeForAllServicesOnDevice, page 52
 DCM.setBackupRevertiveModeForAllServicesOnDeviceForResourceSet, page 52
 DCM.setBackupRevertiveModeForAllServicesOnPort, page 52
4043022 Rev B 81
Appendix B
Available Macros
 DCM.setBackupRevertiveModeForAllServicesOnPortForResourceSet, page 52
 DCM.setBackupRevertiveModeForAllServicesOnTS, page 52
 DCM.setBackupRevertiveModeForAllServicesOnTSForResourceSet, page 52
 DCM.setBackupRevertiveModeForResourceSet, page 52
 DCM.setBackupRevertiveModeWithFile, page 52
 DCM.SetGbEPortMirrors, page 32
 DCM.SetGbETSLossTriggers, page 58
 DCM.SetKeyerIDToLogoForResourceSet, page 42
 DCM.SetLogoFileNumberToLogoForResourceSet, page 43
 DCM.setUnsolicitedIGMPMsgVersion, page 63
 DCM.setUnsolicitedIGMPMsgVersionForResourceSet, page 63
 DCM.setupSMCCommunity, page 68
 DCM.StartBannerForResourceSet, page 49
 DCM.StartBannerInAllServicesForResourceSet, page 49
 DCM.StartEASForResourceSet, page 49
 DCM.startSplice, page 39
 DCM.startSpliceForResourceSet, page 39
 DCM.StopAllBannersForResourceSet, page 50
 DCM.StopBannerForResourceSet, page 50
 DCM.StopBannerInAllServicesForResourceSet, page 50
 DCM.stopSplice, page 41
 DCM.stopSpliceForResourceSet, page 41
 DCM.SwitchAutoNegotiation, page 33
 DCM.SwitchStreaming, page 36
 DCM.SwitchStreamingTSWithFile, page 36
 DCM.switchStreamingTSWithFileForResourceSet, page 36
 DCM.SwitchToAlternateSource, page 73
 DCM.UpdateInLogoLibraryForResourceSet, page 43
 DCM.updateSMCPool, page 68
82 4043022 Rev B
DCM Macros
 DCM.updateVSEInSMCPool, page 70
4043022 Rev B 83
C
Appendix C
Appx auto letter
Macro Backup Configuration

Consideration
Introduction
Existing macros have been extended to apply settings on a backup
device if the main device becomes inactive. This means that if there is
a backup device assigned to a main device and the main device is
taken over by this backup device and a macro is executed for this main
device, the same macro should be executed for the backup device as
well. This functionality can only be achieved by adding or changing a
particular registry key. This appendix describes how to change this
registry key.
In This Appendix
 Modifying Registries for Device Backup Purposes.......................... 86
4043022 Rev B 85
Appendix C
Macro Backup Configuration Consideration
Modifying Registries for Device Backup Purposes

To achieve the functionality as described in the introduction of this appendix, the
following registry key should be added or changed (key type should be of
REG_DWORD) on the computer running the ROSA NMS Server software:
HKEY_LOCAL_MACHINE\SOFTWARE\Scientific-
Atlanta\Copernicus\Macro\MacroBUConfig
- Value = 1 means Macro Backup Configuration is considered Value
- Value = 0 means Macro Backup Configuration is not considered
1 Open Regedit on the computer running the ROSA NMS Server software.
2 Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Scientific-Atlanta\Copernicus
3 Add a new key folder Macro under Copernicus.
86 4043022 Rev B
Modifying Registries for Device Backup Purposes
4 Under Macro, add the MacroBUConfig key and assign the value.
5 Close Regedit.
4043022 Rev B 87
Glossary
A
AC
access criteria.
ASI
asynchronous serial interface. Allows the intermittent transfer of data one bit at a time rather
than in a steady stream.
B
BAT
bouquet association table.
C
CAS
conditional access system.
CAT
conditional access table.
CSV
comma-separated values. A data file format supported by many spreadsheet programs, in
which fields are separated by commas. Also referred to as comma delimited.
D
DCM
digital content manager.
DVB
A standard developed by the Digital Video Broadcasting (DVB) Group, which is a European
organization that has authored many specifications for satellite and cable broadcasting of
digital signals. Part of the DVB work has been focused specifically on conditional access.
E
EAS
Emergency Alert System.
4043022 Rev B 89
Glossary
ECM
entitlement control message.
EIS
event information scheduler.
EITa p/f
event information table actual present/following.
EITa sch
event information table actual schedule.
EITo p/f
event information table other present/following.
EITo sch
event information table other schedule.
ES
elementary stream.
F
FTP
file transfer protocol. Allows users to transfer text and binary files to and from a personal
computer, list directories on the foreign host, delete and rename files on the foreign host, and
perform wildcard transfers between hosts.
G
GUI
graphical user interface. A program interface that takes advantage of a computer graphics
capabilities to make the program visually easier to use.
I
ID
identifier.
IGMP
Internet group management protocol. A protocol used to established host memberships in
particular multicast groups on a single network.
IIOP
Internet inter-ORB protocol. A protocol developed to implement CORBA solutions over the
web. It enables browsers and servers to exchange integers, arrays, and more complex objects.
90 4043022 Rev B
Glossary
It is a protocol for communication between an application programming interface (API) and

an external client.
IP
Internet protocol. A standard that was originally developed by the United States Department
of Defense to support the internetworking of dissimilar computers across a network. IP is
perhaps the most important of the protocols on which the Internet is based. It is the standard
that describes software that keeps track of the internetwork addresses for different nodes,
routes, and outgoing/incoming messages on a network. Some examples of IP applications
include email, chat, and Web browsers.
M
MPEG
Motion Picture Experts Group. A joint committee of the International Standards Organization
(ISO) and the International Electrotechnical Commission (EG). This committee develops and
maintains the MPEG specification for a series of hardware and software standards designed
to reduce the storage requirements of digital video and audio. The common goal of MPEG
compression is to convert the equivalent of about 7.7 MB down to under 150 K, which
represents a compression ratio of approximately 52 to 1. Current standards are MPEG-1,
MPEG-2, and MPEG-4.
mux
multiplexer. A device that combines two or more signals into one output.
N
NITa
network information table actual.
NITo
network information table other.
NMS
network management system. A software system designed specifically to monitor a network
and to facilitate troubleshooting.
O
ON ID
original network identifier.
OS
operating system.
P
PAT
program association table.
4043022 Rev B 91
Glossary
PCR
program clock reference.
PID
packet identifier or program identifier.
PMT
program map table. Identifies and indicates the locations of the streams that make up each
service, and the location of the Program Clock Reference fields for a service.
PSI
program specific information.
PSIP
program and system information protocol. (A digital TV data transport standard.)
R
RCDS
remote control and diagnostics system.
ROSA®
RCDS open system architecture.
S
SCTE
Society of Cable Telecommunications Engineers, Inc. A not-for-profit professional
organization formed in 1969 to promote the sharing of operational and technical knowledge
in the field of cable television and broadband communications.
SDTa
service description table actual.
SDTo
service description table other.
SI
system or service information. Tuning information sent from the DNCS to DHCTs which
provides the information that DHCTs need to be able to tune to a particular service.
SPM
statmux pool manager
92 4043022 Rev B
Glossary
T
TS
transport stream.
TS ID
transport stream identifier.
U
UDP
user datagram protocol. A connectionless protocol, like TCP, that runs on top of IP networks.
Unlike TCP/IP, UDP/IP provides very few error recovery services, offering instead a direct
way to send and receive datagrams over an IP network without acknowledgements for
guaranteed delivery.
V
VBI
vertical blanking interval.
VLAN
virtual local area network. A local area network with a definition that maps workstations on
some other basis than geographic location (for example, by department, type of user, or
primary application). The virtual LAN controller can change or add workstations and manage
load balancing and bandwidth allocation more easily than with a physical picture of the LAN.
Network Management System software keeps track of relating the virtual picture of the local
area network with the actual physical picture. VLANs are based on logical instead of physical
connections.
VSE
virtual service encoder.
4043022 Rev B 93
4043022 Rev B 95
Cisco Systems International BV Haarlerbergweg 13-19 Amsterdam, The Netherlands
www.Cisco.com
This document includes various trademarks of Cisco Systems, Inc.
Please see the Trademarks section of this document for a list of the Cisco Systems, Inc.,
trademarks used in this document.
All other trademarks mentioned in this document are the property of their respective owners.
Product and service availability subject to change without notice.
© 2012 Cisco and/or its affiliates. All rights reserved.
April 2012 Printed in USA Part Number 4043022 Rev B

DCM Integration Into ROSA NMS

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

DCM Integration Into ROSA NMS

Загружено:

Авторское право:

Доступные форматы

4043022 Rev B

DCM Integration into ROSA NMS

For Your Safety

4043022 Rev B iii

For Your Safety iii

Chapter 1 Setting Up ROSA NMS 1

Chapter 2 Working with the Graphical User Interfaces 17

Chapter 3 Using DCM Macros 23

4043022 Rev B vii

Importing and Removing PSI/SI Data .................................................................. 34

Appendix A Customer Information 75

Appendix B Available Macros 79

Appendix C Macro Backup Configuration Consideration 85

viii 4043022 Rev B

Introducing ROSA NMS

Installing the ROSA NMS Drivers

To Install the ROSA Drivers

3 Press the Install… button.

 ROSA Device Configuration Shell: in the folder \ Program Files \ Cisco \

ROSA NMS Driver File Name

7 Press the Close button to close the dialog.

The following procedure describes how to reboot the server.

Result: The following confirmation box is displayed.

 Click on the Yes button to reboot the server.

Making Task Instances

To Make a Task Instance

Result: The Make Task dialog is displayed.

4 Press the OK button to confirm.

5 Click on the Close button to close the Installed Drivers dialog.

Creating Authentication Profiles

Adding an Authentication Profile

Result: The Add Authentication Profile dialog appears.

Mapping a DCM into ROSA NMS

To Map a DCM into ROSA NMS

2 Click on the Add... button.

Result: The Map Resources tab is displayed.

Operational Limitations and Errors

Opening the User Interface of a DCM

Result: A new key is added under

Opening the User Interface of a Task or Component

 To Resize the Graphical User Interface

 To Maximize the Graphical User Interface

- On the user interface of a task or component, click on About in the Help

About the DCM Macros

Installing the DCM Macros

Creating Config Files

Note: Version and 1 has to be separated by a comma.

The following illustrations show a configuration opened with Microsoft Excel.

Using DCM Macros

4,1,225.0.0.1,49410,stream type, , ,Audio,0x81,en4, , ,2,86,pass

 When a configuration file for the DCM.ApplyComponentRules macro (without

Downloading the Service Component Rules from a DCM

Removing Service Component Tracking Rules

GbE Port Settings

Switching on or off Auto-negotiation of GbE Ports

Importing and Removing PSI/SI Data

Removing PSI/SI/PSIP Information

Table TableID TableONID TableTSID TableIDExt

Starting or Stopping Streaming of Outgoing Transport Streams

Requirements: The DCM.SwitchStreaming macro requires DCM device driver for

Handling the Services Population of an Outgoing Transport Stream

Removing Services from an Outgoing Transport Stream

Starting and Stopping a Splicing Event