Download - NMX GettingStarted

Transcript

NMX Digital Service ManagerGetting StartedNMX Version 4.4.1

Part Number: MAN-NMXGS-4.4.1Revision A

ii

DisclaimerHarmonic Inc. reserves the right to change any products described herein at any time, and without prior notice. Harmonic assumes no responsibility or liability arising from the use of the products described herein, except as expressly agreed to in writing by Harmonic. The use and purchase of this product does not convey a license under any patent rights, copyrights, trademark rights, or any intellectual property rights of Harmonic. Nothing hereunder constitutes a representation or warranty that using any products in the manner described herein will not infringe any patents of third parties.

Trademark AcknowledgmentsHarmonic and all Harmonic product names are trademarks of Harmonic Inc. All other trademarks are the property of their respective owners.

©Harmonic Inc. 2006ALL RIGHTS RESERVED

Welcome to NMXArchitectural Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1About this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Required Equipment and Information for Configuration . . . . . . . . . . . . . . . . . . . . . 4

Getting StartedSetting up the NMX Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Creating the NMX Database Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Setting the Database Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Deleting Unnecessary Element Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11Setting Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12Starting the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14Stopping the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16Starting NMX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Creating a Network GroupSetting Site Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22Using the Network Group Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23Locking the Network Group for Editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27Changing the Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28Checking Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Table of Contents

iv Table of Contents

Configuring HardwareRemoving a Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Setting Port Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Saving a Device Configuration as a Template . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Connecting DevicesGetting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Connecting Input Devices to Encoders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Connecting Encoders to Remultiplexers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Connecting the Remultiplexer to the MOM Output Device . . . . . . . . . . . . . . . . 46Saving the Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Adding a PSI/SI Input DeviceCreating a PSI/SI Input Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Moving the Input Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Connecting the Input Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Configuring ServicesSetting Service Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Opening the Service Configuration Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Opening the Create New Service Configuration Dialog Box . . . . . . . . . . . . . 56Opening the Edit Service Configuration Dialog Box . . . . . . . . . . . . . . . . . . . 57Setting the Service Configuration Properties . . . . . . . . . . . . . . . . . . . . . . . . . 57

Configuring Input Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Creating an Input Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Adding a Video Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Saving the Video Configuration as a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . 62Adding the First Audio Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Adding the Second Audio Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Creating the Second Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Configuring Output Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Creating an Output Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Adding Programs to the Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Creating a DiviTrackXE Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Creating the Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Setting Stream Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Changing the Pool Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Saving the Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

vTable of Contents

Importing Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78Working in Stream Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

Exporting a Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79Importing a Service Configuration to NMX . . . . . . . . . . . . . . . . . . . . . . . . . . . .80

Provisioning ServicesConnecting Services to the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82

Connecting Audio and Video Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82Connecting PSI Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84Connecting the Output Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84

Provisioning Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85Putting the Devices Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85Activating the Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

Viewing the Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86Viewing a Service Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86Viewing the Streams Flowing Through a Device . . . . . . . . . . . . . . . . . . . . . . .87

Setting the MDM Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

Adding RedundancyConfiguring Nx1 Encoder Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

Adding an Nx1 Switch to the Network Group . . . . . . . . . . . . . . . . . . . . . . . . .90Connecting the Nx1 Switch to the Input Devices . . . . . . . . . . . . . . . . . . . . . .92Adding a Backup Encoder to the Network Group . . . . . . . . . . . . . . . . . . . . . .94Connecting the Nx1 Switch to the Backup Encoder . . . . . . . . . . . . . . . . . . . .95Connecting the Backup Encoder to the MN20 . . . . . . . . . . . . . . . . . . . . . . . .96

Configuring 1x1 Remultiplexer Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97Adding a Backup MN20 to the Network Group . . . . . . . . . . . . . . . . . . . . . . .97Connecting the Primary and Backup MN20s . . . . . . . . . . . . . . . . . . . . . . . . . .98Connecting the PSI Input to the Backup MN20 . . . . . . . . . . . . . . . . . . . . . . . .98Connecting the Encoders to the Backup MN20 . . . . . . . . . . . . . . . . . . . . . . .99Adding an A/B Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101Connecting the MN20s to the A/B Switch . . . . . . . . . . . . . . . . . . . . . . . . . . .102Connecting the A/B Switch to the Output Device . . . . . . . . . . . . . . . . . . . . .103

Protecting Against Data LossBacking up the NMX Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105Restoring the NMX Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107

vi Table of Contents

Creating a VOD NetworkCreating the Headend Network Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Creating the Network Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Creating Video Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Creating Cross Connect Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Creating NSGs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Creating the GTA 9111 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Creating the VOD Serving Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Connecting the Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Creating the Hub Network Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Connecting the Headend to the Hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Configuring the Hub Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Connecting the Proxy to Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Configuring the Headend Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Connecting the Proxy to Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Putting Devices Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Viewing VOD Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Creating a BNG NetworkCreating the BNG Network Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Configuring the BNG Network Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Enabling HHP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Configuring the BNG GbE Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Configuring Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Extracting ASI Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Starting the Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Creating Input Transports From a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Creating Transports Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Setting Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Adding PSI Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Creating the Remaining ASI Input Transports . . . . . . . . . . . . . . . . . . . . . . . . 150Creating the Output Transports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Adding a Program to the Output Transport . . . . . . . . . . . . . . . . . . . . . . . . . 153Creating the Remaining Single Program Transports . . . . . . . . . . . . . . . . . . 154Creating the PSI Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Connecting Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Connecting the Input Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Connecting the Output Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Activating the Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

viiTable of Contents

Managing DM Network CherryPickersCreating a Network Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161

Creating the Network Group Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162Creating Input Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162Adding a CherryPicker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163Adding Cards to the CherryPicker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164Adding a BNG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165Adding a CAS Card to the BNG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166Adding CAS Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168Adding the PSI/SI Input Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170Adding an RF Output Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171

Connect the Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172Configuring Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177

Extracting Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177Starting the Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178Creating Input Transports From a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179Creating the Output Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180Add Programs to the Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181Adding CAS Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182Creating a Rate Shaping Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184

Connecting Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188Connecting the Input Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188

Provisioning Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190Putting the Devices Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190Activating the Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191

Customer SupportContacting Harmonic for Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . .193

viii Table of Contents

Welcome to NMX

NMX Digital Service Manager™ provides configuration, control, monitoring, and fault management for Harmonic components in open digital television broadcast systems. NMX manages and monitors compressed digital video and audio services as well as third-party equipment including switches, matrixes, and modulators.

With NMX, you can create and modify channel lineups in addition to sending the parameters for encoding, multiplexing, scrambling or rate shaping. NMX supports geographically diverse sites through a client/server architecture, and scales to support small or large networks.

Architectural Overview NMX has three main components:

■ Server—consists of all NMX processes, including element managers, Domain Manager, Alarm Manager, and the Object Repository Server (ORS). All internal communication within NMX is done through the ORS. Server configuration is done through the Domain Manager.

■ Client—provides an interface to the NMX server. All configuration and monitoring is done through the client. Clients can run on the server computer or a remote computer. The client is known within NMX as the Digital Service Manager.

2 Welcome to NMX

■ Database—contains all NMX configuration information. The database, known within NMX as the Object Repository, is a Microsoft® SQL Server 2000 catalog. In this release, the database is on the same computer as the NMX server.

In distributed networks, each site with hardware has an NMX server. You must use the server at a site when configuring the equipment at that site. However, you can log in to the server using a client in any location that has network access to the server.

To view the configuration of multiple sites without opening multiple clients, you add remote sites to NMX as proxy sites. Using proxy sites, a single client in one city can monitor multiple NMX servers in other cities. All sites have their own servers that manage their own local devices. The servers at proxy sites communicate independently with a client, and do not manage each other’s devices.

3Welcome to NMX

About this ManualThis manual guides you through setting up and configuring an NMX system for four basic Harmonic networks and includes how to set up a redundancy configuration and back up for the NMX network configurations. The appendixes provide examples for creating a VOD network, creating a BNG network, and managing DM Network CherryPickers™.

Before you begin, you must first install the NMX server and client software. For information on installing, upgrading, and setting up the NMX server and client, see the NMX Digital Service Manager Installation and Startup manual.

The following table describes the information provided by the chapters in this manual.

Chapters Description

1 “Getting Started” Create the NMX database, set system options, and start the NMX server and client.

2 “Creating a Network Group”

Set site properties, use the Network Group wizard to create a network group and view alarms.

3 “Configuring Hardware”

Remove an AAA card from the encoders, set port properties, and save a template.

4 “Connecting Devices”

Connect the devices in the network group.

5 “Adding a PSI/SI Input Device”

Create a PSI/SI input device and connect the input device to the MN20.

6 “Configuring Services”

Create two input services, an output transport, and a DiviTrackXE pool.

7 “Provisioning Services”

Connect streams to the ports they flow through, activate the service configuration, and set the streams to output through the MDM.

4 Welcome to NMX

Required Equipment and Information for ConfigurationTo fully complete the procedures described in this guide, you need the following equipment:

■ NMX server and client, set up as described in the NMX Digital Service Manager Installation and Startup guide

■ Two MV50 encoders, with SIA cards if you are using DiviTrackXE

■ One MN20 remultiplexer, with one ARM card, one MDM card, and one MOM card

■ One Leitch switch, another MV50 encoder, and another MN20 remultiplexer if you want to configure redundancy

■ Two analog or digital video input sources, each with two accompanying audio sources

8 “Adding Redundancy”

Add an Nx1 switch and a backup encoder, add an AB switch and a backup remultiplexer, and connect ports.

9 “Protecting Against Data Loss”

Back up your NMX network configuration by backing up the database.

Appendixes Description

A “Creating a VOD Network”

Create network groups for video-on-demand networks and create links between the network groups and devices.

B “Creating a BNG Network”

Create a BNG network group using a template and configure services for the network group.

C “Managing DM Network CherryPickers”

Create a network group that includes DM Network CherryPickers and then configuring services for the network group.

“Customer Support” Contains Harmonic technical support information.

Chapters Description

5Welcome to NMX

■ A video monitoring device for the MDM

■ An ASI monitoring device for the MOM

■ Nine Harmonic NSGs, one GTA 9111, and other video-on-demand equipment

■ Two Harmonic BNG 6301s

■ One DM3200 CherryPicker

■ One Harmonic BNG 6104 (1G2A-SCR-4QX model)

However, you can easily substitute other equipment if you do not have these devices; for example, you can use MV45 encoders. Additionally, if you just want to practice setting up a network, you can do most of the configuration in this book without any hardware at all.

You also need to gather some information before you begin going through the steps in this guide. To complete the configuration, you need to know:

■ The MAC addresses of the hardware devices

■ The IP addresses you want to assign to the hardware devices

■ The PIDs you want to assign to the services in your network

■ The PSI/SI tables you need to include with services

6 Welcome to NMX

Getting Started

Setting up the NMX DatabaseTo begin using NMX, you must create the database catalog for NMX, then tell NMX to use this database. If you are using a SQL Server database on a computer other than the NMX server computer, or if you changed the default host name of the NMX server computer, set the SQL database server name first.

Creating the NMX Database Catalog

To create the NMX database catalog:

1. On the NMX server computer, double-click the Domain Manager icon.

The Domain Manager login dialog box opens.

2. Accept the default user name and password:

User: Administrator

Password: <no password>

Note: Domain Manager provides user administration tools to configure individual user logins and passwords. Harmonic recommends setting an administrator password and configuring individual user accounts for system security. See the Domain Manager online help for more information.

In This Step:■ Create the NMX

database

■ Set system options

■ Start the NMX server and client

8 Getting Started

Domain Manager tells you that it cannot connect to the database, then opens. Domain Manager can’t connect to the database because the database catalog does not exist yet.

3. In the Domain Manager window, right-click the Domain icon and select Properties from the shortcut window.

The Domain Properties dialog box shows the default settings for the NMX Database, the Statistics Server Database and the Automation Server Database. If you are using the Automation or Statistics server, you can set these properties later.

4. If necessary, in the NMX DB Server field, enter the host name of the SQL Server computer, and click OK.

You need to change the default value for DB Server if:

■ You are using the NMX server as the SQL server, and you changed the default host name of the server.

■ You are using a remote database. If you use a remote database, enter the name of the remote SQL Server.

5. From the Domain Manager Database menu, select Catalog Administrator.

The Database User Login dialog opens.

6. In the login dialog box, enter the SQL system administrator user and password and click OK.

9Getting Started

Harmonic began setting the SQL system administrator password to “harmonic” for computers shipped with NMX version 4.1.0.1 and later. Computers sent with earlier releases did not include a system administrator password. If you received your computer during the 4.1.0.1 release or later, enter:

User Name: sa

Password: harmonic

If you received your computer during an earlier release, and you have not set a system administrator password, leave the password field blank. Harmonic recommends setting a system administrator password if you have not done so.

The Catalog dialog box opens.

7. Click the New button.

8. Make sure the Catalog Type field says NMX, enter a name for the database, and click OK.

Note: By default, NMX expects the database to be named NMXDB, but you can name the database anything you want. If two NMX servers are using different catalogs on the same SQL server, you must give the catalogs unique names.

A DOS window opens, and text scrolls as the catalog is created. When the catalog creation finishes, the DOS window closes.

10 Getting Started

9. Close the Catalog dialog box when the catalog creation finishes.

Setting the Database Catalog

After you have created the catalog, tell NMX what catalog to use.

To set the database catalog:

1. In the Domain Manager window, right-click the Domain icon and select Properties from the shortcut window.

The NMX DB Catalog field shows NMXDB as the default catalog name. If you named the catalog something else, change the name.

2. If necessary, click the ... button beside NMX DB Catalog and select the database catalog you created.

3. Click OK.

4. If you changed the database catalog, you must log in to Domain Manager again.

After you log in, the Domain Manager window should now show a Local Computer icon under the Domain icon and the following server processes:

■ Object Repository Server All internal device communication is done through the ORS.

■ Encoder EM The encoder element manager controls Harmonic encoders.

■ MN20 EM The MN20 element manager controls the Harmonic MN20 remultiplexer.

11Getting Started

■ Alarm Manager—The Alarm Manager collects alarms from network devices.

■ Switch EM—The Switch element manager controls switches in your network.

■ Modulator EM—The modulator element manager controls Radyne modulators and third-party GPI-monitored devices.

■ NSG EM—The NSG element manager controls Harmonic NSGs.

■ BNG EM—The BNG element manager controls the Harmonic BNG.

■ DM Network CherryPicker EM—The CherryPicker element manager controls Terayon DM3200 and DM6400 CherryPickers.

■ Multi-channel EM—The Multi-channel element manager controls Ion, Electra 1000, Electra 5000, DiviCom Audio Encoder, and DDM platforms.

■ Optical Transport EM—The Optical Transport element manager controls Harmonic GIGAlight™10GTA devices and HOA9023 devices.

■ ProStream EM—The ProStream element manager controls the Harmonic ProStream multiplexer.

■ ProView EM—The ProView element manager controls Newtec and Sencore modulators.

Red icons beside the server processes illustrate that they are not currently running.

NMX also provides a DPI Server and an element manager for the MV3550 encoder, but does not automatically include them in the list. See the NMX online help for instructions to add these server processes.

Deleting Unnecessary Element ManagersMost networks do not use all the platforms NMX supports. Although Domain Manager shows most element managers by default, you can delete the element managers you do not need. No examples in this guide use modulators, so we are going to delete the Modulator element manager. You can also delete the element manager for any other platform you do not use.

12 Getting Started

Note: You can only delete an element manager when it is not related to an element in the catalog. NMX displays a warning when you try to delete an element manager with a related element in the catalog.

To delete the Modulator element manager:

1. Right-click the Modulator element manager icon and select Delete from the shortcut menu.

2. Click Yes to confirm that you want to delete this object.

Setting OptionsBefore starting the NMX server, set system options. Many options do not take effect until you restart the server, so set options now so you don’t need to restart later.

Most options are global — once you set them, any client that logs into the server will use these same defaults. However, some options are set on the local computer. A note in the Options dialog box tells you whether the options are local or global.

13Getting Started

The Options dialog box has six tabs:

■ General—Provides default values for network settings, which can save you from entering this information for devices in your network, as well as other properties.

■ SNMP and TCP—NMX uses SNMP to check the status of network devices and collect alarms. Set the polling interval, timeout, and retry.

■ Switch— Provides default COM port settings for switches that you add to a network group.

■ Services—Provides default values for configuring services.

■ Statistics—Provides values used for statistical reporting. This feature requires an additional license.

■ Alarms—Provides values used if you want NMX to forward alarms and other alarm properties.

For now, you can set just the General and SNMP properties. See “Setting Service Options” on page 54 for instructions to configure service options.

To set options:

1. From the Domain Manager Tools menu, select Options.

The Options dialog box opens with the General tab selected by default. The NMX online help has a complete description of the Option fields.

Tip: The NMX online help has a complete description of the Option fields. Click the Help button for more information.

14 Getting Started

2. In the General tab, enter default values as appropriate for your network.

3. Click the SNMP and TCP tab to set these options.

4. When you finish setting the options, click OK to close the dialog box.

Starting the ServerWhen you have finished setting options, start the server. Starting the server launches the DPI server, Bootp, and Tftp daemons.

To start the NMX server:

1. In the tree, right-click the Local PC icon and select Properties from the shortcut menu.

The PC Properties dialog box opens.

15Getting Started

2. Enter the IP address of the NMX server computer from which you are working in the IP Address field or click the ... button to select the IP address.

3. Enter the host name for the server in the PC Name field.

4. Click OK to close the dialog box.

You only need to enter the server IP address once. If you need to start and stop the server in the future, you do not need to enter the IP address.

5. Click the green arrow button in the Domain Manager toolbar to start the NMX server.

The icons beside the server processes turn yellow while the processes initialize, then turn green when started. The toolbar shows a green bullet and Server Running when all the processes have started.

Note: It takes several minutes for the server processes to initialize.

After the server is running, you can close Domain Manager or just minimize it. The server does not stop when you close Domain Manager. You must click the Stop Server button on the toolbar to stop the NMX server. Stopping the server does not stop the Bootp and Tftp daemons.

Caution: The NMX server must be running to perform normal monitoring and management of your network devices. Leave the server running even after you have finished hardware and service configuration.

16 Getting Started

Stopping the Server At times you will need to restart the NMX server after changing settings. To stop the NMX server, click the hand icon on the toolbar or select File, then Stop Server.

Stopping the server does not stop the Bootp and Tftp daemons. Once the server is stopped, click the boot icon to the right of the hand icon to stop the Bootp and Tftp daemons or select File, then Stop Daemons.

Starting NMXNMX clients can run on the NMX server computer or a remote computer. The client provides an interface to the server for configuration and management of the hardware and services in your network.

To open the NMX client:

1. On the server computer or another computer where the NMX client software is installed, double-click the Digital Service Manager icon.

The Login dialog box opens.

Stop servericon

Stop daemonsicons

17Getting Started

2. In the Server field, accept the default IP address if you are working from the server computer, or enter the IP address of the NMX server if you are working from a remote computer.

3. If you have not configured additional users or changed the Administrator password, accept the default user name and password:

User Name: Administrator

Password: <no password>

4. Click OK.

NMX opens and shows Tree and Map View. The Tree View pane contains an icon for the site at the top of the tree, and the Map View pane is empty.

NMX has three toolbars: two at the top of the window and one at the bottom. Use the top toolbars for changing views, copying and pasting items, aligning items in a map, and so on. Use the bottom toolbar to create a network group or proxy site, add hardware devices to a network group, and connect devices on a map.

Tree View pane Map View pane

Site icon,

Top toolbars

Bottom toolbar

Menu bar

the top levelof thenetwork tree

Service treeNetwork tree

18 Getting Started

NMX has four separate views:

■ Tree View

■ Map View

■ Tree and Map View

■ Spreadsheet View

Additionally, the service tree has three separate views. Buttons in the top toolbar control the view.

When you configure hardware, most actions can be initiated from both the network tree and the map. The instructions in this guide assume that you are working in Tree and Map View, and usually include instructions to initiate an action from both the tree and the map.

The next chapters in this book describe configuring a basic digital video system with two encoders and an MN20 remultiplexer. If this is the type of network you want to configure, see “Creating a Network Group” on page 19.

If you want to create a VOD network, see “Creating a VOD Network” on page 111.

If you want to create a BNG network, see “Creating a BNG Network” on page 137.

If you want to create a network with Terayon DM Network CherryPickers, see “Managing DM Network CherryPickers” on page 161.

Creating a Network Group

In NMX, a network group is a group of hardware devices that work together to produce one or more digital multiplexed transport streams. You can add physical devices, logical devices, and switches to a network group. NMX uses the concept of physical devices to represent actual hardware managed by NMX, and logical devices to represent devices that may be in your network but are not managed by NMX, or to represent concepts such as an Ethernet cloud or VOD serving area instead of a physical platform.

Switches have both physical and logical characteristics. See the online help for more information about switches.

NMX supports the following physical and logical devices in a network group:

Physical Devices■ Harmonic MV12, MV30, MV40, MV45, MV50, MV100, MV400,

MV450, and MV500 encoders

■ Harmonic DiviCom Multi-channel family of encoders: Ion, Electra 1000, Electra 5000, Electra 5400, Electra 7000, and Audio Encoder

■ MV3550 HD AVC encoders

■ Harmonic MN20 remultiplexer

■ Harmonic ProStream 1000 and ProStream 8000 (Mosaic)

■ Harmonic NSG

In This Step:■ Set site properties

■ Use the Network Group wizard to create a network group

■ View alarms

20 Creating a Network Group

■ Harmonic BNG

■ Harmonic DDM

■ Harmonic GIGAlight GTA 91xx

■ Harmonic HOA9023

■ Harmonic Site Controller

■ Radyne DM240 and DM240 XR modulators and QAM 256 modulators

■ Sencore Advanced Satellite modulator ASM 988A

■ Newtec 2177, 2180, 2277, and 2280 modulators

■ Terayon DM3200 and DM6400 CherryPickers™, CP7220, and CP7600 decoder

■ Third-party devices that are managed through contact closures, including the PVR6000

■ Third-party devices that are managed through SNMP, including the PVS6000.

■ Third-party devices that act as cue trigger devices for digital program insertion (DPI)

■ Switches (A/B, Nx1, NxM generic, and NxM balanced)

Logical Devices■ Input device

■ Output device

■ Video server

■ DWDM

■ VOD serving area

■ Cross Connect device

■ ECM Source device

■ EMM Source device

■ CWS Source device

In most cases, a network group consists of all the hardware at a site. However, if you have an especially large site, you might want to break it into several network groups.

21Creating a Network Group

When you configure a network group, you set only the hardware properties for these devices. Service configuration is done separately.

There are many ways to add hardware to a network group. This chapter describes using the Network Group Wizard to create a small network group containing two input devices, two MV50 encoders, an MN20 remultiplexer, and a MOM output device. We will also monitor output through an MDM, but you do not need to add an MDM output device to the network group. While you might have more hardware in your network group, the steps are the same to create a large group or a small group.

Note: This example uses MV50 encoders and a 5-MRU MN20 remultiplexer. If you have different encoders or a different MN20, set options as appropriate for these devices instead. The instructions are the same for either device.

In the appendices of this manual, you will add other devices to the network group using other methods.

If your network group has switches and backup hardware to support redundancy, you can include those devices when you create the network group with the Network Group Wizard. For simplicity, this chapter describes creating a network group without redundancy. See “Adding Redundancy” on page 89 for instructions to add redundant devices to the network group.

The Network Group Wizard creates hardware devices based on templates you select for each type of device. NMX provides some default templates, which you will use in this example. If your devices are much different from the template, you might want to create your own templates before using the Network Group Wizard, or add devices using another method.

Begin the network group configuration by setting properties for the site. Then use the Network Group Wizard to add hardware to the site.

22 Creating a Network Group

Setting Site PropertiesThe site icon represents the local site where the NMX server is located. All the hardware at this site should be configured in network groups under this site icon.

You can configure and manage equipment and services at remote sites using this NMX client, but you must add those sites to NMX as proxy sites. See the NMX online help for more information about proxy sites.

To set site properties:

1. In Tree View, right-click the site icon and select Properties from the shortcut menu.

The Site Properties dialog box opens.

2. Highlight the site name and enter the name of your site.

3. Optionally, enter a description for the site.

4. Optionally, select a background graphic for your site map.

NMX comes with some background graphics, or you can use a graphic of your own.

5. Click OK.

The site icon in the network tree now shows the new name.

23Creating a Network Group

Using the Network Group WizardTo create a network group using the Network Group Wizard:

1. In NMX, right-click the site icon in the network tree, or right-click anywhere in the blank map pane, and select Network Group Wizard from the shortcut menu.

The Create Network Group dialog box opens.

2. Under Identity Information, enter a descriptive name for the network group, and optionally add a description.

Because this example does not include CAS devices, the default mode, BNG Simulcrypt/Clear, is correct.

3. In the table at the bottom of the dialog box, enter information about the devices in your network.

Each row of the table provides information about a different kind of device. For this example, provide information about encoders, multiplexers, input devices, and output devices.

■ # of Devices. Specifies the quantity of each device in your network group. Enter the following:

MV30/50/100 Encoder (or MV12/40/45): 2

Multiplexer: 1

Input Device: 2

Output Device: 1

24 Creating a Network Group

■ Name Prefix and Starting Count. The name prefix and starting count specify how device icons are labeled on the map and in the network tree. The name prefix is combined with the starting count number to create the full name. For example, if you have three encoders, and you accept the default values for Name Prefix and Starting Count, NMX names the encoders Enc50-1, Enc50-2, and Enc50-3. Accept the default values for these fields.

■ Starting IP. The starting IP is the IP address assigned to the first device of a specific type. Subsequent devices of the same type are given IP addresses that increase by one. For example, if the starting IP address for encoders is 192.168.10.5, and you have three encoders, NMX assigns the following IP addresses to the encoders:

Enc50-1: 192.168.24.5

Enc50-2: 192.168.24.6

Enc50-3: 192.168.24.7

Enter the IP addresses that you want to use for the encoders and remultiplexer. Harmonic recommends using a private IP network.

■ Template. From the drop-down list, select a template of configuration properties for each device. NMX comes with some default templates. After you have set properties for a device, you can save the configuration as a template for later use. For now, use the following default templates or templates appropriate for your devices:

MV50 Encoder: Sys-MV50Encoder

Multiplexer: Sys-Mux-5MRU (3ARM)

Input Device: Sys-Input (1SDV+4A)

Output Device: Sys-Output-MOM (ASI)

Note: MN20 devices can be measured in terms of physical rack-units (RU) or module rack-units (MRU). The 4-RU MN20 contains five module units, while the 3-RU MN20 contains three module units. The MN20 templates distinguish between the two MN20 models using the MRU size.

25Creating a Network Group

The completed dialog box should look something like this:

4. Click Next.

The next dialog box shows you the properties that NMX created for the devices and lets you set more properties.

5. On the Encoder and Multiplexer tabs, enter a MAC address for each device in the table.

Each device must have a unique MAC address.

26 Creating a Network Group

6. Look at the other tables on each tab, and make sure that the settings are correct.

Note: Some properties in the tables are generated from the device template. Don’t worry that the network settings other than IP addresses are incorrect for the encoders and remultiplexer. You will change these values later.

7. Click Finish.

The Creating Network Group message shows you the status of creating the group. When NMX finishes creating the group, a Network Group icon appears in the map view pane and network tree.

Click a tab to see theproperties for thosedevices.

Enter the MAC addressof each device.

27Creating a Network Group

To view the network group:

1. Double-click the Network Group icon in Map View, and click the plus sign next to the network group icon in the network tree to expand the tree.

Icons for the input devices, encoders, multiplexer, and output device appear in the map and in the tree.

2. Click the plus sign next to a device to view the cards in the device.

3. Click the plus sign next to a card to view the ports on the card.

The window should look like this:

Locking the Network Group for EditingBecause multiple NMX clients can log into the server simultaneously, you might find that another user is trying to make changes to a network group at the same time you are. To prevent another user from overwriting your changes, you can lock the network group. When you lock a network group, no one else can access that group until you release the lock, or until you close your client session.

You might not need to worry about other users right now, but locking the network group is a good habit that you’ll want to establish.

28 Creating a Network Group

To lock the network group:

➭ Right-click the network group icon in the tree or map, and select Lock from the shortcut menu.

When you lock a network group, “Locked by me” appears in parentheses beside the network group name.

Note: The Domain Manager Active Sessions pane shows locks in the system. Superusers can release locks set by others. See the Domain Manager online help for more information.

The NMX Standard and Enterprise editions provide locking support. If you do not see Lock on the shortcut menu, your software does not support locking.

Changing the Network SettingsBecause you used default templates to create the MV50s and MN20, the network settings are probably not correct for your network. You can change these settings quickly using the Bulk Update feature in Spreadsheet View.

All the devices in the network should use the same subnet mask, default gateway, and TFTP server.

To change the network settings:

1. In the top NMX toolbar, click the Display Spreadsheet Only button.

Spreadsheet View replaces Tree and Map View. The default display is correct because we have only configured one network group. Later, you can use the drop-down list on the left side of the window to select the network group, and the drop-down list on the right side of the window to select the view.

2. Click in the left-most column (under the green arrow) to select the rows for the encoders and multiplexer.

Display Spreadsheet Only button

29Creating a Network Group

A blue arrow in this column indicates a row is selected.

3. In the Default Gateway column, enter the default gateway for your network in the top row, marked **BULK SET**.

4. Press Enter.

NMX sets the default gateway for the devices you selected.

5. Repeat steps 2 through 4 to set the correct values for Subnet Mask.

Note: The TFTP Server field is probably set to the IP address of the NMX server and disabled. There is an option on the General page of the Options dialog box named “Sync TFTP and EM IP Address” that is enabled by default. If you have not disabled this option, NMX always sets the TFTP Server IP address for a device to the IP address of the element manager for the device. Because all element managers are installed on the NMX server in this release of NMX, the server IP address is the correct address.

6. Click the Save button in the toolbar to save your changes.

7. When you finish, return to Tree and Map view.

Checking AlarmsNMX provides alarm management tools to alert you to potential problems in the NMX network.

2. Select theencoder andremultiplexerrows.

3. Enter the Default GatewayIP address.

30 Creating a Network Group

A bullet beside an icon in the network tree or a background in the map that is any color but green indicates an alarm has been asserted against a device. The color of the bullet or background indicates the severity of the alarm.

Note that the encoders and MN20 in the network group have purple alarm bullets in the network group and purple backgrounds in the map.

To view alarm details:

1. Right-click the site icon in the network tree or map, and select Display Current Alarms from the shortcut menu.

The NMX Alarm Log window opens.

Because you selected the site icon before opening the Alarm Log, you can see alarms for all the devices configured under the site. If you had selected an encoder and then opened the Alarm Log, you would see alarms for just that encoder. Similarly, you can view alarms for just a card in a device, or even just a port on a card. If you have more than one network group, select the network group icon to view alarms for only that network group.

2. Double-click the triangle icon beside an alarm to view details for that alarm.

3. Note the alarm description.

In this example, all three alarms are caused because the devices are offline. The default templates do not set the devices online. To avoid more alarms while you finish the configuration, leave the devices offline for now.

The next step in configuring NMX is setting hardware properties. See “Configuring Hardware” on page 31.

2. Double-click the triangle icon to view details for an alarm.

Configuring Hardware

When you created your network group in the Network Group Wizard, you selected templates for the MV50 encoders and the MN20 remultiplexer. Those templates contained information about the cards in these devices and the ports on those cards.

Because Harmonic devices come in a number of configurations and support various port modes, it is likely that these default templates do not exactly match the hardware in your network. You might need to add or remove a card, change an existing card to a different type, change the output bit rate on a port, or make some other configuration change.

This chapter describes removing a card from a device and setting ASI port properties. You should always configure devices in NMX to exactly match the devices in your network. When you get one device configured exactly right, you can save that device configuration as a template to use to create other devices.

In This Step:■ Remove an AAA card

from the encoders

■ Set port properties

■ Save a template

32 Configuring Hardware

Removing a CardThe default templates you selected when you created the network group use the following configurations.

MV50

■ 2 AAA cards (one in the main board, and one in slot 2) for audio inputs

■ 1 VIA-4 card for video inputs

■ 1 SIA card for DiviTrackXE support

5-MRU MN20

■ 1 MOM card for ASI or M2S output

■ 1 MDM card for decoded audio and video output

■ 3 ARM cards for ASI or M2S inputs

Use one of these methods to see the cards in a device:

➭ Expand the network tree under a device.

➭ Double-click an encoder or multiplexer icon in the tree or map.

NMX numbers the slots in devices as a way to designate which cards are in which slots. When you expand the network tree, slots are named Slot - 001, Slot - 002, Slot - 003 ... Slot - 255. In the backpanel graphic, small numbers in the upper right corner of each slot show the slot number. The numbers in the network tree always match the numbers in the backpanel graphic — that is, Slot - 003 in the network tree is the same as slot 3 in the graphic. Slot 255 is always the main board in Harmonic devices.

When you put devices online in NMX, NMX goes out to the devices and compares their actual configuration to the configuration you have done in NMX. If NMX finds differences, such as an ARM card in a slot where you said there was a MOM card, it sends a Hardware Mismatch alarm.

For the sake of this example, let’s assume that your MV50 encoders only have one AAA card instead of two. If you left the configuration as the template created it, with two AAA cards, you would always have a Hardware Mismatch alarm because NMX would not find a card in that slot.

33Configuring Hardware

To remove the second AAA card in the MV50 encoders:

1. Double-click an MV50 icon in the network tree or map to open the back panel graphic.

Tip: You can also remove cards by expanding the network tree, right-clicking the card in the tree, and selecting Delete from the shortcut menu.

2. Right-click in a blank spot on the AAA card in slot 2.

Be sure to click in a blank spot. If you click on top of a port, the shortcut menu contains a list of options available for the port instead of the card.

Note: You cannot remove the AAA card on the MV50 encoder in slot 4.

3. From the shortcut menu, select Change Card > None to remove the card.

4. Repeat steps 1–3 to remove the AAA card in the other MV50.

AAA card in slot 4AAA card in slot 2

34 Configuring Hardware

Setting Port PropertiesAlthough most ports do not require configuration, you might want to set properties for ASI output ports. The ASI ports on encoders and MOM cards output either ASI or M2S streams. If you select ASI output, there are other properties you might want to set for the output stream.

All Harmonic MV encoders have two redundant ASI output ports. You set properties for the first port only.

To set ASI port properties on the encoder:

1. Open the backpanel graphic for the encoder.

2. Right-click the ASI1 output port and select Properties from the shortcut menu.

The ASI Properties dialog box opens.

3. Leave the mode field set to Fixed ASI because the rest of this example assumes that the encoder outputs an ASI stream.

Fixed ASI is the default mode for MV50 encoders.

4. Optionally, set the interbyte gap, packet size, and data rate.

The maximum data rate is 100 Mbps.

5. Click OK to save the changes and close the dialog box.

35Configuring Hardware

To set ASI port properties on the MN20:

1. Open the backpanel graphic for the encoder.

2. Right-click the 1P port on the MOM card and select Properties from the shortcut menu.

The ASI Properties dialog box opens.

3. Leave the Mode field set to Fixed ASI.

4. Set the interbyte gap and packet size as appropriate for your modulator.

Note: It doesn’t matter what data rate you set here because NMX automatically sets the data rate for the final ASI output port in a network group when it provisions services. NMX sets the port data rate to match the transport bit rate, taking into account the interbyte gap and packet size you set for the port.

5. Click OK to save the changes and close the dialog box.

36 Configuring Hardware

Saving a Device Configuration as a TemplateOnce you configure a device, you can save the configuration and use it when you configure a similar device.

To save a device configuration as a template:

1. Right-click the device icon in the network tree or map, and select Save Template from the shortcut menu.

The Save Template dialog box opens.

2. Select the Use Local Template File or Use Server Template radio button.

Select Use Local Template if you want to save the file to a folder you specify on the local computer. Select Use Server Template if you want to save the template in the server database. Templates saved in the server database are available to all clients who log in to this server. You might want to save a template locally instead of in the database if you want to send the template file to other sites with other servers.

3. If you selected to save the template on the server, enter a name for the template in the New Template Name field, and enter a description of the template in the New Template Description field.

37Configuring Hardware

4. If you select to save the template locally, in the Template File Name list, click the ... button. Browse to the folder where you want to save the template, then enter a name and click Save.

5. Click OK.

The next step in configuring NMX is creating connections between devices. See “Connecting Devices” on page 39.

If you selectthe Local Template Fileradio button,click the ... button to browse to where you want to savethe template.

38 Configuring Hardware

Connecting Devices

After adding the devices that make up your network group, connect the ports on these devices. The connections you make in NMX represent the physical cable connections between devices. You must make sure to connect the devices in NMX exactly as they are connected in your network, or services do not output correctly.

When you connect devices, think about it in terms of upstream devices and downstream devices. You always connect upstream devices to downstream devices, but the same device can be both a downstream and an upstream device. For example, an encoder is usually downstream to an input device, but upstream to a remultiplexer.

The Edit Connections dialog box, which you use to connect devices, shows upstream devices in a tree in the left pane, and downstream devices in a tree in the right pane.

In this chapter, we’ll use the Edit Connections dialog box to make all the connections at once. Using the Edit Connections dialog box, you can easily make one connection or several connections at one time. In the next chapter, we’ll add a PSI input device and connect it using a different method.

In This Step:■ Connect the devices in

the network group

40 Connecting Devices

Getting StartedTo begin connecting devices:

1. Right-click the network group icon in the network tree, or right-click in a blank area of a map.

2. From the shortcut menu, select Network Group Links.

The Edit Connections dialog opens showing all the devices in a network group in two trees. By default, the Display Hierarchy box is checked, and you can expand each device to show the cards in the device and the ports on the card. If you uncheck the Display Hierarchy box, the ports appear under the devices without the cards.

Start connecting devices at the beginning of the stream flow—the input device. In this example, two input devices are connected to two encoders.

41Connecting Devices

Connecting Input Devices to EncodersTo connect the input devices to the encoders:

1. In the left pane, expand the tree under Inp-1 so that you can see everything in the tree under the first input device.

When you expand the output card, you should see four audio ports and one video port.

2. In the right pane, click the plus sign next to Enc50-1, then click the plus signs next to AAA-Mainboard-004, which is the main board AAA card, and VIA4-003, which is the video card on the encoder.

You should see two audio ports under the AAA-Mainboard card and one video port under the VIA4 card.

3. In the left pane, select the Audio-002 port under the Inp-1 output card.

4. In the right pane, select the Audio-001 port under the AAA-Mainboard card.

Note: After you have connected a port, you cannot connect it again except in the following cases: input devices, ECM generators, and EMM generators.

5. Click the Connect button.

The port icons turn blue to show that they are connected, and the connection appears in the table at the bottom of the window.

42 Connecting Devices

6. Now select the Audio-003 port on the input device and the Audio-002 port on the AAA card, and click Connect.

This connection is for the second audio stream.

7. Finally, select the Video-001 port under the Inp-1 output card and the Video-001 port under the VIA4 card, and click Connect.

When you finish, the dialog box looks like this:

3. Select the firstaudio port under

4. Select the firstaudio port under AAA-Mainboard.

5. Click Connect.

The connection appears in the table below.

Input-1.

43Connecting Devices

8. Click the minus sign next to the Inp-1 and Enc50-1 icons to hide these trees.

9. Repeat steps 1—7 to connect Inp-2 to Enc50-2.

Connecting Encoders to RemultiplexersAfter connecting inputs to encoders, connect the encoders to the MN20 remultiplexer.

Note: If you are using DiviTrackXE statistical multiplexing, there are two connections between an encoder and an MN20: one from the mainboard ASI port on the encoder to an ARM card on the MN20, and one from the ARM port on the MN20 to an SIA port on the encoder. However, when you connect ports in NMX, you do not need to configure the connection between the SIA and ARM ports.

To connect the encoders to the MN20 remultiplexer:

1. In the left pane, click the plus sign next to Enc50-1, then click the plus sign next to Slot 255.

2. Now click the plus sign next to MB-255 to expand the tree below the encoder.

MB-255 represents the encoder main board.

3. In the right pane, click the plus sign next to Mux-1, then click the plus sign next to ARM-001.

The ARM-001 icon represents the ARM card in slot 1 of the MN20.

4. Under the encoder in the left pane, select ASI-001.

This is the ASI output stream from the first ASI output port on the encoder main board.

5. Under the remultiplexer in the right pane, select ASI-001 under the ARM card.

This is the first ASI port on the ARM card.

6. Click the Connect button.

The connection appears in the table.

44 Connecting Devices

7. Expand the tree under the Enc50-2 icon in the left pane.

8. Select the ASI-001 icon under Enc50-2, and select ASI-002 under the ARM card on the MN20.

9. Click Connect.

This connects the ASI output from the first ASI output port on the Enc50-2 encoder to the second ASI input port on the ARM card on the MN20.

Note: The ASI input from the second encoder is connected to the same ARM card on the MN20 as the ASI input from the first encoder. An ARM card accepts up to four inputs.

3. Select the ASI-001port under the encoder.

4. Select the ASI-001port under theMux-1 ARM card.

The connection appears in the table.

45Connecting Devices

After connecting the encoders to the MN20, connect the MN20 to the MOM output device.

Note: The MOM output card is installed in the MN20, and there is no physical cable connecting the MN20 to the MOM. This connection represents the MN20 backplane and tells NMX what port is used as the output port.

Connect the ASIoutput from the second encoderto the ASI-002port on the ARMcard.

46 Connecting Devices

Connecting the Remultiplexer to the MOM Output DeviceTo connect the MN20 to the MOM output device:

1. In the left pane, click the plus sign next to Mux-1, then click the plus sign next to the MOM-007 card.

You can see four ASI output ports under the MOM card (Out-1).

2. In the right pane, expand everything under Out-1.

You can see one ASI input port.

3. Select the ASI-001 port under the MOM-007 card on the MN20 and the ASI-001 input port under the output device, and click Connect.

This connection represents an output from the first ASI port on the MOM card. If you are actually outputting from another ASI port on the MOM card, connect that port to the output device instead. If you are outputting streams from more than one port on the MOM, you must add additional output device icons to the network group.

47Connecting Devices

Saving the ConnectionsWhen you finish making all the connections, click OK. NMX takes some time to generate the connections. The finished map looks like this:

After NMX generates the connections, click the Save button in the top toolbar.

If you want NMX to generate PSI for the output transport streams, add a PSI input device to the map. See “Adding a PSI/SI Input Device” on page 49.

If you do not need to include PSI in your output, configure services. See “Configuring Services” on page 53.

Save button

48 Connecting Devices

Adding a PSI/SI Input Device

Most MPEG-2 transport streams contain program specific information (PSI) and service information (SI), a set of tables that describe the contents of the transport stream. NMX can generate PSI/SI and insert it in the outgoing transport stream.

When NMX generates PSI/SI, there is no external PSI/SI input source. However, NMX requires a PSI/SI input device in the network tree and map to represent the flow of PSI/SI.

Creating a PSI/SI Input DeviceCreate a PSI/SI source by adding an input device to NMX.

To add a PSI/SI input device:

1. Click in a blank spot in the map to put the current focus on the map.

2. In the toolbar at the bottom of the window, click the Create Input Device button.

Create Input Device button

In This Step:■ Create a PSI/SI input

device

■ Connect the input device to the MN20

50 Adding a PSI/SI Input Device

3. Move the mouse pointer onto a blank area of the map where you want the new icon to appear, and click the left mouse button.

When you move the pointer onto the map, the pointer changes to a diamond shape like the device icons. When you click the left mouse button, the Create Object dialog box opens.

4. In the Name field, enter a name for the input device such as PSI Input.

5. In the Number of Ports field, leave the default, 1.

6. In the Port 1 Type field, double-click the drop-down list and select M2S.

7. Click OK.

The new input device appears in the tree and on the map.

Moving the Input DeviceIf you do not like the position of the input device on the map, you can drag it to a new location. However, you need to unlock the map first. By default, NMX opens with an icon lock set on the map so no one accidentally moves icons after the map is created.

Note: Don’t confuse the map lock with locking the system for editing. The Lock button in the toolbar only locks and unlocks the icons for moving—it does not prevent other users from working in the network group

To move icons:

1. Click the Lock button in the second toolbar at the top of the window to unlock the icons.

The icons are locked when the button appears depressed.

2. Position the cursor over the icon you want to move.

3. Press and hold the left mouse button while you drag the icon to the new location.

4. Release the mouse button.

Lock button

51Adding a PSI/SI Input Device

Connecting the Input DeviceAfter adding a PSI/SI input device, connect it to the MN20. Even though there is no physical cable connecting the NMX server computer and the MN20, the connection you draw represents NMX sending PSI/SI to the MN20. This connection multiplexes with the transport stream.

Because you are only making one connection this time, you can do the connection a little bit differently.

To connect the PSI/SI device:

1. In the toolbar at the bottom of the NMX window, click the Create New Link button.

The mouse pointer turns into a pen when you position it in the map.

2. Move the mouse pointer on top of the PSI/SI input device, and press and hold the left mouse button while you drag the pointer onto the MN20 icon.

You can see a line being drawn as you drag the pointer onto the remultiplexer.

Create New Link button

Move the mouse pointeron top of the MN20 whileyou hold down the leftmouse button.

52 Adding a PSI/SI Input Device

3. Release the mouse button when the cursor is on top of the MN20 icon.

The Edit Connections dialog box opens. Because you opened the Edit Connections dialog box by connecting two devices, the dialog box shows just the ports on these two devices. Note that ports are named first with the card that contains them, then with the port type and port number.

You can click the Display Hierarchy box to see the cards in these devices with the ports underneath them.

4. In the left pane, click the M2S-001 port on the input device.

5. In the right pane, click the M2S-005 port on the MN20.

6. Click the Connect button.

The connection appears in the table at the bottom of the window.

7. Click OK to close the dialog box.

The next step in configuring NMX is configuring services. See “Configuring Services” on page 53.

Configuring Services

After creating a network group, connecting ports, and adding a PSI device, you have finished the hardware configuration. You can configure services directly in NMX, or use Stream Editor, a standalone application that can run on a different computer. Because the Stream Editor interface is nearly the same as the NMX interface, the instructions in this chapter apply to both applications even though they refer only to NMX. The last section of this chapter describes how to import and export service configuration files if you are working in Stream Editor.

Begin configuring services by specifying how streams are input to your network equipment and how you want them to be output. At this stage, you supply information such as:

■ How analog streams are encoded as MPEG-2 digital streams

■ How programs are combined into output transport streams

■ What PSI/SI is included with the transport stream

For this example, you will create two input channels, which contain one video stream and two audio streams each and an output transport that multiplexes those two channels.

To begin, set options for configuring services.

In This Step:■ Create two input

services

■ Create an output transport

■ Create a DiviTrackXE pool

54 Configuring Services

Setting Service OptionsUse the Options dialog box to set default parameters for creating services. Most service options are set globally, so that any client logging into the server uses these values as defaults, but some options are set only on the local computer. A note in the Options dialog box tells you if the preferences are local or global.

To set service options:

1. From the Tools menu, select Options.

2. Click the Services tab.

Note: To view all the Service tabs, click the right and left arrows.

The Services page has eight additional tabs:

■ Profiles. Sets saved profiles as the default to use when creating new streams. Because you haven’t saved any profiles yet, you cannot set default profiles. However, you can set a profile as the default when you save it. Profiles are saved on the local computer, but you can import them to the server database to make them available to others.

■ Profile Path. Specifies the directory on the local computer to which profiles are saved. This field is read-only.

2. Click the Services tab.

55Configuring Services

■ PSI/SI General. Specifies the PSI/SI tables that NMX automatically adds to an output transport stream, as well as some default stream types. By default, NMX includes one PAT per transport stream and one PMT per program. Check the boxes beside other tables you want to include. If you want to include one PMT per transport instead of per program, see the online help for instructions. Additionally, you can set the default AC-3 and MPEG audio stream type, the minimum PID value that you want to support, specify whether multicast streams should use the same PID, and specify whether to sort by PID in the PMT.

■ PSI/SI Miscellaneous. Sets options for enabling specific PSI/SI tables, using virtual channels, deleting internally generated PSI, and setting the CherryPicker internally generated PSI PID range.

■ SD and HD Bit Rate. Specifies the bit rate range you want to support for SD and HD streams in various modes and in a DiviTrackXE or CherryPicker pool. The rates you set here are used as guidelines only — not default values. If you set a bit rate for a video stream in the encoding properties page or the multiplexing properties page that falls outside the range you set here, the field background turns red to show that the value is outside the specified range. However, NMX does not send an error message as long as the value you set is within the range NMX supports.

■ Service Miscellaneous. Sets options for how many streams are supported in a multiplexing group, whether a stream name automatically changes in the other tree if you change it in one tree, whether NMX displays stream properties in the tree, and various other properties. You can also select the default modulation file to use when creating PSK, IF and RF transports. See the online help for more information about .DDF files.

■ Descriptor Management. Specifies whether you want NMX to automatically add descriptors to a transport or program when certain conditions are met. For example, NMX can automatically add a CA System Descriptor to an output program when an EMM or ECM is added to the program.

Note: See the online help for information about the fields on these pages.

56 Configuring Services

3. Set the service options as appropriate for your site.

4. Click OK.

5. If you changed any options that require restarting the NMX server, restart the server now.

Note: Make sure to save all the configuration you have done so far before shutting down the server.

Opening the Service Configuration Dialog BoxWhen you configure services in NMX, you work in the Service Configuration dialog box. This dialog box has two variations: Create New Service Configuration and Edit Service Configuration. Because you have not yet started a service configuration for the network group, you will begin working in the Create New Service Configuration dialog box. If you close the service configuration and need to finish later, open the Edit Service Configuration dialog box.

Opening the Create New Service Configuration Dialog Box

To open the New Service Configuration dialog box:

1. Click the Output Service View tab at the top of the Network View pane.

NMX shows the Output Service tab by default. If you change the service view to show the input tree or both input and output trees, the tab name changes.

2. If necessary, expand the Site icon to show the network group icon.

3. Right-click the network group icon and select New Service Configuration from the shortcut menu.

1. Click the Output ServiceView tab.

2. Expand the Site icon.

3. Right-click the Network Group icon and select NewService Configuration.

57Configuring Services

The Create New Service Configuration dialog box opens.

Opening the Edit Service Configuration Dialog Box

To open the Edit Service Configuration dialog box:

➭ In the service tree, right-click the Service Configuration icon and select Edit Service Configuration from the shortcut menu.

Setting the Service Configuration Properties

The default service configuration name is New Service Configuration. Change the name to associate the service configuration with the network group, and set other properties if necessary.

To change the service configuration name:

1. Right-click the New Service Configuration icon in the network tree, and select Properties from the shortcut menu.

The General Output Properties dialog box opens.

58 Configuring Services

2. Enter a descriptive name, such as Sample Service Configuration, and press Enter.

3. Optionally, add a description of the service configuration.

4. Do not change the other properties.

The default PSI/SI injection location at the Bundling multiplexer is correct for this example. If you create a network group with two multiplexers and you want to insert PSI at the scrambling/edge multiplexer, you must change the injection location here.

The CAS Mode is read-only and based on the mode set when you created the network group.

5. Click OK.

59Configuring Services

Configuring Input ServicesThe Service Configuration dialog box displays streams in two panes: an input pane on the left, and an output pane on the right. Hierarchical trees organize the information in each pane. The tree hierarchy shows how streams are grouped together at the transport level, program level, and stream level.

The input pane has three default branches under which you add streams: A/V Streams, Transports, and Inserted Data. This example uses A/V streams, which represent the analog or digital streams to be encoded by the encoders in your network, and inserted data, which includes PSI.

Because there are two encoders in the Sample network group, you need to create two input channels. Each input channel contains one video stream and two audio streams.

Creating an Input Channel

To create the first input channel:

1. In the input tree, right-click the A/V Streams icon and select Add Channel from the shortcut menu.

2. In the Channel Name field, enter a descriptive name for the channel, such as HBO.

You do not need to worry about the Advanced options.

3. Leave the Encoder Vendor field set to Harmonic.

Select HD OEM only for streams passing through an MV3550 HD AVC encoder.

60 Configuring Services

4. Click OK.

Adding a Video Stream

The channel appears under the A/V Streams icon.

To add a video stream to the channel:

1. In the input tree, right-click the channel icon and select Add Baseband Video from the shortcut menu.

The Enter Name dialog box opens, with HBO Video as the default name for the video stream.

2. Click OK.

The video stream appears under the channel. If you did not change the default settings in the Options dialog box, the stream bit rate appears beside the stream name, and the letter P to indicate that the stream carries PCR.

3. Right-click the video stream and select Properties from the shortcut menu.

61Configuring Services

The HBO Video General Properties dialog box opens.

4. Click the Encoding icon under the General icon to open the Encoding properties pages.

Note that the Encoding icon is now highlighted to show that you are viewing the encoding properties pages. The encoding properties are separated onto six separate pages:

■ Source

■ Encoding

■ Preprocessing

■ Filters

■ Composite

■ Closed Captioning

Set video properties on each page appropriately for your network. See the online help for more information about each property.

For this example, enable the encoder filters.

5. Click the Filters tab to open the Filters properties page.

6. Check the Override Default Settings Box and check the Noise Reduction box to enable the noise reduction filters.

7. Set each filter as shown in the following figure.

Tip: How to set filters depends on the type and quality of the source material and it is always subjective. See the NMX online help for more information on setting filters.

62 Configuring Services

Saving the Video Configuration as a Profile

When you have finished configuring the video stream, save the configuration as a profile to use when configuring other streams.

1. In the Video Encoding Properties dialog box, click the Save Profile button.

2. Enter a descriptive name for the profile, such as SDVideo.

3. Check the box beside Make this profile the default.

When you set a profile as the default, all new video streams that you add to a channel automatically use this profile.

63Configuring Services

4. Click OK to save the profile.

5. Click OK to close the Video Encoding Properties dialog box.

Adding the First Audio Stream

After you have added a video stream to the channel, add the first audio stream.

To add an audio stream to the channel:

1. Right-click the channel icon and select Add Baseband Audio from the shortcut menu.

The Enter Name dialog box opens, with HBO Audio as the default name for the audio stream.

1. Click the Save Profile button.

2. Enter a descriptive name for the profile.

3. Check Make this profile the default.

64 Configuring Services

2. Change the name of the stream to HBO Audio 1 because there will be two audio streams under this channel.

3. Click OK.

The audio stream appears under the channel.

Tip: When you open the Properties pages for a channel or stream under a channel, the tree on the left side of the Properties dialog box includes all the streams in the channel. Select any item in the tree to view properties for it.

4. Right-click the audio stream and select Properties from the shortcut menu.

The HBO Audio 1 General Properties dialog box opens.

5. Click the Encoding icon to open the Encoding properties pages for the audio stream.

By default, the audio encoding properties are separated on three pages:

■ Source

■ Format

■ Dolby AC-3

If you change the audio format to MPEG-2, AAC, or Dolby E instead of Dolby AC-3, the Dolby AC-3 tab disappears and an MPEG-2, AAC, or Dolby E tab appears instead. If you leave the format set to Dolby AC-3 and choose Compression instead of Pass-Through, an Advanced Dolby AC-3 tab appears.

Set audio properties on each page appropriately for your network. See the online help for information about each property.

For this example, we will change the stream type to Digital.

6. Click the Format tab.

7. In the Format drop-down list, select MPEG-L2.

65Configuring Services

8. Follow the instructions in “Saving the Video Configuration as a Profile” on page 62 to save the audio configuration as a profile and set it as a default. Give the audio profile a descriptive name such as MPEG2Audio.

Adding the Second Audio Stream

Now that you have saved an audio stream as a profile, all future audio streams you create will be configured just like the profile.

To add the second audio stream:

1. Right-click the channel icon and select Add Baseband Audio from the shortcut menu.

2. Change the name to HBO Audio 2, and click OK.

The audio stream appears under the channel. You do not need to do any more configuration for the audio stream unless you want to configure it differently from the first audio stream.

Creating the Second Channel

Because you saved the audio and video stream configurations as profiles and set those profiles as a default, you could make a second channel just like you did the first one. You would not need to set any properties for the audio and video streams unless you wanted them to be configured differently than the streams in the first channel.

4. Click the Encoding iconto open the Audio EncodingProperties pages.

5. Click the Format tab.

6. In the Format drop-downlist, select MPEG-L2.

66 Configuring Services

However, there are other ways to add a channel after you have already added one:

■ Copy the first channel

■ Save the first channel to a file

Use either method to add the second channel.

Copying Channels

To add a channel by copying another channel:

1. Select the channel that you want to copy, and press Ctrl+C.

2. Select the A/V Streams icon, and press Ctrl+V.

The new channel appears under the A/V Streams node. Notice that the channel is named Copy-2 of the original channel name, and the audio and video streams are named Copy-2 of the audio and video stream names. You’ll want to rename these.

3. Right-click the copied channel icon and select Rename from the shortcut menu.

The channel name appears highlighted in blue.

4. Enter a new name for the channel, such as CNN, and press Enter.

5. Repeat steps 3 and 4 to rename the audio and video streams.

Saving Channels to a File

When you save a channel to a file, all the stream configuration for the channel is saved to a .chl file. To create another channel just like the first, you base the new channel on the saved file.

67Configuring Services

Saving to a file is especially useful if you have multiple sites or configure services from multiple computers. After creating a file, you can distribute it to other locations to ensure that all configuration is done alike.

To save a channel to a file:

1. Right-click the channel icon and select Save to File from the shortcut menu.

2. Browse to the folder where you want to save the file.

3. Enter a descriptive name for the channel file and click Save.

To add a channel from a file:

1. Right-click the A/V Streams icon and select Add From File from the shortcut menu.

2. Browse to the folder holding the file.

3. Select the file and click Open.

68 Configuring Services

The new channel appears in the tree with the same name as the channel that was used to create the file.

4. Rename the channel and its audio and video streams to distinguish them from other channels and streams.

Configuring Output ServicesAfter you finish configuring the input channels, configure the output services. You will need to create the transport that the MOM outputs and a DiviTrackXE pool if your encoders support VBR encoding. You do not need to do anything right now to configure the streams output through the MDM.

Creating an Output Transport

Create output transports in the output pane, which is the pane on the right side of the Service Configuration dialog box. When you create a transport, the transport icon is at the top of the tree hierarchy. Because a transport is made up of programs and other data streams, programs and PSI/SI are at the next level in the tree. Under programs are the elementary streams that make up a program, including audio, video, and data streams. Descriptors provide additional information about a transport, program, or elementary stream and can be attached to any of these.

69Configuring Services

To create the output transport:

1. In the output pane, right-click the Service Configuration icon and select Add Transport from the shortcut menu.

2. Enter a descriptive name for the transport in the Transport Name field.

That is actually all you need to do to create the transport, but note a few things:

■ The default output protocol is ASI. NMX also supports DHEI, DS3, IP, PSK, IF, RF, OC-3, and ATM/IP transports.

■ The Multicasted box is checked so that multicasting is enabled. When multicasting is enabled, you can include the same input channels in more than one output transport stream. Although this example does not include configuring multicasting, you could because the MOM output card supports multicasting.

Note: Do not select the Multicasted check box if you output from the MN20 main board.

■ The default Multiplexer Group is correct. If you have more than one multiplexer (or more than one redundant multiplexer pair) per network group, you need to create a different multiplexer group for each multiplexer. If you have only one multiplexer or multiplexer pair per network group, you do not need to change this property.

■ Click the Advanced button to specify whether there is a GPI or SNMP monitored platform in the network group. GPI and SNMP monitored platforms are third-party devices such as

70 Configuring Services

modulators that NMX does not manage, but monitors for alarms. This example does not include a GPI or SNMP monitored platform, so you don’t need to worry about this.

3. Click OK to create the transport icon.

The transport icon is added to the tree, along with icons for the PSI/SI tables and descriptors that you selected in the Options dialog box. If you expand the input tree under the Inserted Data icon in the input tree, then expand the tree under the Internal PSI icon, you will see that NMX automatically added an icon for the PAT table. If you checked any other PSI tables that you wanted to include in the Options dialog box, these tables appear too.

4. In the output tree, right-click the transport icon and select Properties from the shortcut menu.

The Properties dialog box has two tabs: General and Delivery.

5. On the General page, set the Network ID and maximum bit rate for the transport.

The network ID is used during PSI/SI generation and may be important to your set-top boxes. If your set-top boxes use a network ID, set this value to match the value used by your set-top boxes. See the online help for more information.

NMX provisions the output bit rate to the final ASI output port in the network group. In this case, the final ASI output port is the MOM output port.

You do not need to worry about the other fields for this example.

The PSI/SI icons areautomatically added tothe input and outputtrees.

71Configuring Services

6. Set the remaining properties as appropriate for your output transport.

Note that the fields on the Delivery page change when you select the delivery type. See the online help for more information about each field.

7. Click OK to close the dialog box.

Adding Programs to the Transport

After adding the transport stream, add programs to it. The term program is used now instead of channel because the streams have been encoded in MPEG-2 format.

To add programs:

1. Right-click the transport icon on the output pane of the Create New Service Configuration dialog box and select Add Program from the shortcut menu.

The Select Inputs dialog box opens, containing a list of the channels you created in the input tree.

5. Select the delivery typeto see propertiesappropriate to that type.

Output transporticon

72 Configuring Services

Note: If the source stream has been added to a Main Re-encoded Service with the same transport, the stream cannot be selected. ProStream 1000 devices support re-encoding.

2. Check the boxes beside the two channels you created earlier

3. Under Service Type, select Regular Service and click OK.

The programs appear in the output tree under the transport icon.

The output transport configuration could be finished at this point. You can set output properties for each program, but these properties are descriptive and therefore optional. Other things you might want to do include:

■ Configure statistical multiplexing through DiviTrackXE

■ Add descriptors to the output transport

■ Change PIDs in the output transport

See the next section “Creating a DiviTrackXE Pool” for instructions to create a pool. See the NMX online help for instructions to add descriptors and change PIDs.

Go on to “Saving the Service Configuration” on page 77 if you do not need to create a DiviTrackXE pool.

2. Check the boxes beside theinputs you want to includein the transport.

1. Select AddProgram.

73Configuring Services

Creating a DiviTrackXE PoolAfter you have created an output transport, you can create a DiviTrackXE pool to statistically multiplex the video streams in the output transport.

The Harmonic MV40, MV45, MV50, MV100, MV400, and MV450 VBR encoders, used with the MN20 remultiplexer, support DiviTrackXE, a statistical multiplexing program that lets multiple video streams share a pool of bandwidth. Using DiviTrackXE, video streams with complex encoding requirements can "borrow" bandwidth from streams with less complex requirements on a frame-by-frame basis.

This example discusses DiviTrackXE in an ASI environment. Some encoders also support DiviTrackIP™, which is similar to DiviTrackXE but uses an IP environment. DiviTrackMX is a statistical multiplexing application used by DiviCom Ion multi-channel encoders. See the NMX online help for more information about DiviTrackIP and DiviTrackMX.

DiviTrackXE supports a maximum of 24 channels per pool.

Creating the Pool To create a DiviTrackXE pool:

1. Click the Statistical Multiplexing tab at the bottom of the output pane of the Service Configuration dialog box.

2. Right-click the Sample Service Configuration icon and select Add DiviTrackXE Pool from the shortcut menu.

74 Configuring Services

3. Enter a name for the pool.

Because there is only one multiplexer group in this example, the default multiplexer group is correct. If your network contains more than one remultiplexer so that you have created more than one multiplexer group, you must select the appropriate multiplexer group. NMX only lets you add video streams to the pool from transports that are in the multiplexer group you select here.

4. Click OK.

5. Right-click the pool icon and select Add Video from the shortcut menu.

6. Check the boxes beside the two video streams in the output transport and click OK.

The video streams appear under the pool.

1. Click the Statistical

2. Select Add DiviTrackXE Pool.

Multiplexing tab at thebottom of the output pane.

75Configuring Services

Setting Stream Properties

After creating the DiviTrackXE pool, set the multiplexing properties for the video streams.

Tip: DiviTrackXE works more efficiently when streams are allowed to run unconstrained. For more information about improving video quality, see the NMX online help.

To set video stream properties:

1. In the DiviTrack tree, right-click a video stream and select Properties from the shortcut menu.

The Multiplexing Properties dialog box opens.

Check the boxesbeside the streamsyou want to include.

76 Configuring Services

2. Enter the minimum Mbps video stream bit rate in the Min Bit Rate field.

3. Enter the maximum Mbps video stream bit rate in the Max Bit Rate field.

Note: If you enter a bit rate in the Min or Max Bit Rate field and the field background turns red, you entered a value that is outside the recommended DiviTrackXE bit rate range set in the Options dialog. NMX does not consider this an error — you can legally set values between .3 Mbps and 15 Mbps for an SD video stream. The red background is just a reminder that you have set a value that is outside the range in the Options dialog box.

4. Optionally, set a priority for the stream.

MV50 and MV100 encoders support DiviTrackXE priorities.

5. Select the other video stream in the tree on the left side of the dialog box, and set multiplexing properties for it.

6. Click OK.

2. & 3. Set the minimumand maximum bit rates.

77Configuring Services

Changing the Pool Bandwidth

The total bandwidth available to the pool is automatically calculated by adding the nominal bit rates of the video streams you add to the pool. NMX calculates the nominal bit rates based on the minimum and maximum bit rates for a stream and the pool bandwidth. You can change the pool bandwidth manually if necessary.

Tip: See the NMX online help for detailed information about nominal bit rates.

The pool bandwidth must be:

■ Greater than or equal to the sum of the minimum bit rates of the streams in the pool

■ Less than or equal to the sum of the maximum bit rates of the streams in the pool

If you want to set a pool bit rate that is outside these parameters, you must adjust the minimum or maximum bit rates of individual streams before adjusting the pool bandwidth.

To change the pool bandwidth:

1. Right-click the pool icon and select Properties from the shortcut menu.

2. In the Bit Rate field, enter the new pool bit rate in Mbps.

3. Click OK.

Saving the Service ConfigurationNMX does not save the changes you make to the service configuration until you click OK in the New Service Configuration dialog box, or Apply in the Edit Service Configuration dialog box.

To save the service configuration:

➭ Click OK in the Create New Service Configuration dialog box, or click the Apply button in the Edit Service Configuration dialog box.

78 Configuring Services

If you were working in the Edit Service Configuration dialog box, the commands in the command buffer at the bottom of the window move from the Current Changes tab to the Previous Results tab.

The Output Service tab shows the output transport stream.

To view both input and output streams, change the view.

To change the view of the service tree:

1. Click the down arrow beside the Service Views button in the toolbar, and select All Services from the drop-down menu.

The view changes, but the Tree View pane is probably too narrow to show both panes.

2. To expand the Tree View pane, move the mouse pointer over the bar between the Tree View pane and the Map View pane until it turns into a double-arrow.

3. Press and hold the left mouse button while you drag the bar to the right to increase the size of the Tree View pane.

Importing ProfilesWhen you saved the audio and video configurations as profiles, you saved them to the local file system. If you want users who log in to the server from different computers to have access to your profiles, you must import them to the server database.

1. Click the arrow buttonbeside the Service Views button to openthe drop-down menu.

79Configuring Services

Note: You must be working in NMX to import profiles. You can’t do this step in Stream Editor. Additionally, the New Service Configuration or Edit Service Configuration dialog boxes cannot be open.

To import profiles:

1. From the NMX Tools menu, select Import to Server >Templates.

The Import Templates to Server dialog box opens, with default navigation to the Stream Editor Profiles folder on the local computer. A folder for each type of profile is beneath the Stream Editor Profiles folder.

2. Double-click the appropriate folder to view the profiles available in this folder, or navigate to another location if necessary.

3. In the right column, select the profile you want to import, and click Import.

Working in Stream EditorStream Editor provides a convenient way to configure services offline. Because you can run Stream Editor on any Windows 2000 computer, you can do the configuration from any location.

If you start a service configuration in NMX, you can finish the configuration in Stream Editor, or vice-versa. When you work in both NMX and Stream Editor, you export service configurations from NMX so that you can open them in Stream Editor, then import the file you made in Stream Editor back into NMX.

If you configured services in Stream Editor instead of NMX, you must import the service configuration into NMX before you can move on to the next chapter.

Exporting a Service Configuration

If you begin configuring services in NMX and want to finish or update the service configuration in Stream Editor, export the service configuration from NMX so that you have a file to work with in Stream Editor. Files that you export are saved with a .map extension.

80 Configuring Services

To export a service configuration:

1. In the NMX Service View pane, right-click the service configuration icon and select Export Service Configuration from the shortcut menu.

2. Browse to the location where you want to save the file.

3. Enter a descriptive name for the file, and click Save.

NMX saves the service configuration as a file with a .map extension. You can open this file in Stream Editor just like you open any file that you saved in Stream Editor.

Note: When you save a service configuration, NMX asks if you want to apply new unique identifiers to the service configuration or keep the existing identifiers. Each element of a service configuration has a unique identifier in the NMX database. If you save the service configuration with the existing identifiers and import the file back into NMX, all information tied to these identifiers updates immediately, overwriting the existing configuration. If you are using one service configuration as the basis for a different service configuration, save the new configuration with unique identifiers so that you do not overwrite the existing configuration when you import the service configuration to NMX.

Importing a Service Configuration to NMX

When you create or update a service configuration in Stream Editor, Stream Editor saves the configuration as a .map file. To bring the service configuration into NMX, import the file.

To import a service configuration to NMX:

1. In the NMX Service View pane, right-click the network group icon to which you want to add the service configuration and select Import Service Configuration from the shortcut menu.

2. Browse to the location where you saved the .map file created with Stream Editor.

3. Select the file and click Open.

NMX adds the service configuration to the service tree.

The next step in configuring NMX is connecting services to the network. See “Provisioning Services” on page 81.

Provisioning Services

When you have finished configuring services, associate them with the actual hardware in your network. Then activate the service configuration to provision the services on the network hardware.

By connecting services, you associate input streams with input devices and output transports with output devices. When you activate the service configuration, NMX uses the port connections you made for the network group to provision the service from the input device through switches, encoders, and multiplexers, to the output device.

If you have directly connected input devices to encoders to multiplexers to output devices, NMX provisions the services based on these connections. If your network configuration includes large switches that provide multiple provisioning options, NMX chooses the best path based on your service configuration and its associated hardware requirements.

Since this example does not yet include switches, NMX provisions the services based on the hardware connections. Each input device sends two audio streams and a video stream to an encoder. The encoder sends a transport stream that contains the video and audio streams to the remultiplexer. The remultiplexer multiplexes these two transport streams into one transport stream, and outputs this stream through the MOM output device.

You need to tell NMX which input stream is coming from which input device, and which output port you are using.

In This Step:■ Connect streams to the

ports they flow through

■ Activate the service configuration

■ Set the streams to output through the MDM

82 Provisioning Services

Connecting Services to the NetworkBegin service provisioning by associating streams with the ports they flow through.

Note: To complete this task, you must know what inputs are flowing through what input devices. For example, you must know that HBO flows through Input Device 1, while CNN flows through Input Device 2.

Connecting Audio and Video Inputs

To connect audio and video inputs to the network:

1. In the Services tree, right-click the Service Configuration icon, and select Connect Service to Network from the shortcut menu.

The Connect Service to Network dialog box opens. Note that this dialog box has two tabs: Input Services and Output Services. Each page contains two trees: a service tree and a device tree.

2. If necessary, expand the two trees in the Input Service page so you can see the entire contents of the trees.

3. In the Input Services tree, select the CNN Audio 1 stream.

4. In the Input Devices tree, select the Audio-002 port under Inp-2.

83Provisioning Services

5. Click the Add button.

A CNN Audio icon appears under the audio output port icon. This shows that the stream CNN audio flows through the audio output port on Inp-2.

6. Connect the second CNN Audio stream to the second audio port by selecting the CNN Audio 2 stream, then selecting the Audio-003 port on the input device, then clicking Add.

7. Connect the CNN Video stream to the video input port by selecting the CNN Video icon in the Input Services tree, then selecting the Video-001 port under Inp-2, then clicking Add.

When you finish, the dialog box should look like this:

8. Repeat steps 3 through 7 to connect the HBO audio and video streams to the ports on Inp-1.

3. Select CNN Audio 1.

4. Select the Audio-002port under Inp-2.

A CNN Audio 1 iconappears under the Audio-002port to show the connection.

84 Provisioning Services

Connecting PSI Inputs Because NMX creates the PSI/SI tables, there is no actual input device for PSI. However, you created a PSI input device to represent NMX. Connect the internal PSI streams to the PSI input device you created.

Tip: You do not need to select individual PSI streams. Just select the PSI Internal icon.

To connect PSI inputs:

1. In the Input Services tree, expand the Insertion Data icon so that you can see the icons underneath it.

2. Select the PSI-Internal icon.

3. In the Input Devices pane, select the M2S-001 icon under Output Card-001 on the PSI Input device.

4. Click the Add button.

The PSI-Internal icon appears under the M2S-001 icon to show that PSI streams flow through this port.

Connecting the Output Transport

After connecting the input streams, connect the output transport stream and the output channel.

To connect the output streams:

1. In the Connect Service to Network dialog box, click the Output Service tab.

2. If necessary, expand the contents of the trees so that you can see the output transport icon and the ASI-001 port under the MOM Output device.

2. Select the PSI-Internal icon.

3. Select the M2S-001 icon. A PSI Internal iconshows the connection.

85Provisioning Services

3. In the Output Services pane, select the Transport icon.

4. In the Output Devices pane, select the ASI-001 port under the MOM Output device.

5. Click the Add button.

The Transport icon appears under the ASI-001 port icon.

6. Click OK to close the Connect Service to Network dialog box.

Provisioning ServicesAfter you have connected services to the network, activate the service configuration. Activating the configuration provisions the streams on the hardware so that your configuration takes effect.

The devices in your network group must be online for provisioning to occur. If your devices are still offline, put them online now.

Putting the Devices Online

To put devices online:

➭ Right-click the device icon in the network tree or map, and select Online from the shortcut menu. Alternatively, switch to Spreadsheet View, and check the In Service box for each device.

Activating the Service Configuration

To activate the service configuration:

➭ In the NMX Service View tree, right-click the service configuration icon and select Activate Service Configuration from the shortcut menu.

3. Select the Transport icon.

4. Select the ASI-001 icon.

The Transport iconshows the connection.

86 Provisioning Services

Note: If you have more than one service configuration within a network group, only one service configuration can be active at a time.

A status bar at the bottom of the window shows the progress of the provisioning, which can take some time for a large network.

If the activation is successful, the word Active appears in parentheses beside the service configuration icon in the Output Services tree, and the service configuration appears in a bold font. All the icons in Map View should be green. An ASI monitor on the MOM port should see ASI output.

If the activation is unsuccessful, red icons on the map indicate problem areas. View Current Alarms as described in “Checking Alarms” on page 29 to find out the cause of the problems.

Viewing the ProvisioningAfter services have been successfully provisioned, you can quickly see the path a service follows through the network devices, or find out what streams are flowing through what devices.

In this example, the network is so small that you know which encoder compresses which streams and which MN20 outputs which streams. However, in larger redundant networks, NMX might make decisions about which hardware to use, and you cannot always predict the outcome.

Viewing a Service Path

If you want to see what hardware a specific service is provisioned on, synchronize the service with the map to highlight the path the service follows.

87Provisioning Services

To view the path a service follows:

➭ In the service tree, right-click the service that you want to see and select Synchronize Views from the shortcut menu.

Viewing the Streams Flowing Through a Device

NMX also provides a list of the streams flowing through a specific device.

Note: The stream list for an encoder or multiplexer only shows the streams output from that device. Select the link to a device to see the streams input to a device.

To view the streams flowing through a device:

➭ Right-click the device and select Stream List from the shortcut menu.

Setting the MDM OutputsAfter you have provisioned services, you can specify the audio and video streams you want to output through the MDM.

To specify the MDM outputs:

1. Double-click the MN20 icon on the map to open the back panel graphic.

2. Right-click on the MDM card and select Properties from the shortcut menu.

3. Under Monitoring Properties, select the video and audio stream that you want to output through the MDM.

The Video Stream drop-down list includes all the video streams flowing through the MN20. After you select the video stream, the Audio Stream drop-down list contains the audio streams that are associated with the selected video stream.

If you do not select a video stream, the Audio Stream drop-down list contains a complete list of available audio streams so you can select audio-only channels.

88 Provisioning Services

4. In the On Screen Display drop down list, select whether you want a video monitor to display the video stream or display the audio and video bit rate only.

5. Click Apply, then OK.

You have the option to configure redundancy if necessary. See “Adding Redundancy” on page 89.

If you do not need to configure redundancy, back up your NMX configuration. See “Protecting Against Data Loss” on page 105.

Adding Redundancy

NMX supports Nx1, NxM, and 1x1 redundancy for most platforms. All redundancy configuration is done through the hardware—you do not need to do any additional service configuration.

Configuring Nx1 Encoder RedundancyYou configure encoder redundancy by connecting an Nx1 switch to the input devices and the backup encoder. If a primary encoder fails, the switch sends the input for the failed encoder to the backup encoder. The backup encoder is connected to the primary and backup remultiplexers just like the primary encoders.

Make sure that the backup encoder is configured exactly like the primary encoders, including the same hardware configuration and embedded software version. Begin configuring encoder redundancy by adding an Nx1 switch to the network group.

In This Step:■ Add an Nx1 switch and

a backup encoder

■ Add an AB switch and a backup remultiplexer

■ Connect ports

90 Adding Redundancy

Adding an Nx1 Switch to the Network Group

To add an Nx1 switch to the network group:

1. If necessary, click the arrow at the end of the bottom toolbar to open the switch selections.

The size of the Digital Service Manager window and what icons you have already selected determine which icons are on the bottom toolbar and which are hidden. You might not need to click the arrow to view the Nx1 switch icon.

2. Click the Nx1 switch icon in the bottom toolbar and click again in a blank area of the map beneath the input devices.

The Create Object dialog box opens.

3. Enter a name for the switch and optionally a description.

4. In the Hardware Model field, select the type of switch that is in your network.

Selecting the Hardware Model automatically sets the number of inputs.

5. Complete the rest of the switch fields as follows:

■ Switch Type: Nx1 Type

The switch is an Nx1 switch because it determines which input stream (from Input Device 1 or Input Device 2) to send to the backup encoder.

■ Default Port Type: Audio

Because you have two audio streams and only one video stream, you save some time by setting the default port type to audio.

■ Number of Levels: 3

The number of levels is the number of streams that need to be switched simultaneously. Because each input device sends one video stream and two audio streams, there are three levels.

Nx1 Switch icon.

1. Click the arrow at the end of the toolbar.

91Adding Redundancy

■ Level 1 Port Type: SD Video

■ Level 2 and Level 3 Port Type: Audio

Audio is set by default so you don’t need to change this field.

■ Manual Override: False

When you set Manual Override to True, you must activate a redundancy switch manually. Setting this field to False allows redundancy switches to happen automatically if an alarm occurs that is configured to trigger a redundancy switch.

■ In Service: True

■ COM Port: The COM port on the NMX server computer to which the switch is connected. This value depends on how you have connected the server and the switch.

■ Hardware Address: (Disabled for stub switches) The hardware address of the switch in case several switches are cascaded using an X-bus connection and controlled by the same COM port. Each switch must have a unique hardware address. See the switch documentation for instructions to set the hardware address.

Note: Leitch switches can use a Destination ID instead of Hardware Address. If you want to use the Destination ID for Leitch switches, you must set this preference in the Options dialog box before creating a new switch.

92 Adding Redundancy

The finished dialog box should look something like this:

6. Click OK.

Connecting the Nx1 Switch to the Input Devices

After adding the Nx1 switch to the network group, connect the input devices to the switch. You can connect all the input devices at once, or one at a time. This example shows connecting them one at a time for clarity, but if you have many input devices, it is faster to open the Edit Connections dialog as described in “Connecting Devices” on page 39.

To connect the input devices:

1. Click the Link button in the bottom toolbar.

When you bring the mouse cursor onto the map, it turns into a pen.

2. Position the pen icon on top of the first input device, and press and hold the left mouse button.

3. While holding down the mouse button, drag the pen icon on top of the Nx1 switch icon.

93Adding Redundancy

4. Release the mouse button.

The Edit Connections dialog box opens, showing just the ports on the input device and the Nx1 switch. Note that the Nx1 switch has Level 1 video ports, Level 2 audio ports, and Level 3 audio ports. These ports match the number of inputs and the Level 1, Level 2 and Level 3 port types that you entered when you created the switch.

5. Select the Video-001 port on the input device, select the Level-001 Video-001 port on the switch, and click the Connect button.

Note that this is the same video port that you connected to the encoder. You can tell that the port is already connected because it is blue.

6. Select the Audio-002 port on the input device, select the Level-002 Audio-001 port on the switch, and click the Connect button.

7. Select the Audio-003 port on the input device, select the Level-003 Audio-001 port on the switch, and click the Connect button.

Tip: Make sure to connect the two input audio ports to ports on the switch with different levels.

2. & 3. Press and hold the mouse button to drawa line between thedevices you want toconnect.

94 Adding Redundancy

The audio connections in the Edit Connections dialog box should look something like this:

8. Click OK.

9. Connect the other input device to the switch in the same way, connecting the second input device ports to the Audio-002 port at each level.

Adding a Backup Encoder to the Network Group

After adding the Nx1 switch to the network group, add a backup encoder. Because the backup encoder must be exactly like the primary encoders, copy a primary encoder to quickly add the backup to the network group.

6. & 7. Connect theaudio ports to the first audio port in Level 2and the first audioport in Level 3.

95Adding Redundancy

To add a backup encoder:

1. Right-click a primary encoder in the network tree or map and select Copy from the shortcut menu.

2. Right-click the network group icon or right-click in a blank spot on the map and select Paste from the shortcut menu.

The new encoder appears in the tree and map.

3. Right-click the new encoder icon and select Properties from the shortcut menu.

4. Enter a new name for the encoder, such as Enc50-Backup, and click OK.

Connecting the Nx1 Switch to the Backup Encoder

After adding the backup encoder to the network group, connect the Nx1 switch to the backup encoder. The switch can then send input it receives from an input device connected to a failed encoder to the backup encoder.

To connect the Nx1 switch to a backup encoder:

1. Use the Link button to draw a connection between the Nx1 switch and backup encoder.

2. In the Edit Connections dialog, connect the switch video output port to the VIA4-003 port on the encoder.

3. Connect the switch audio output ports to the main board AAA audio ports.

96 Adding Redundancy

Connecting the Backup Encoder to the MN20

Finally, connect the backup encoder to the MN20. The backup encoder can then send the compressed output stream to the remultiplexer for inclusion in the output transport stream.

To connect the backup encoder to the MN20:

1. Use the Link button to draw a connection between the backup encoder and the MN20.

2. Connect the first ASI output port on the encoder to the third ASI port on the first remultiplexer ARM card.

The ASI outputs from the two primary encoders are already connected to the first two ports on the ARM card.

Connect the ASI-001 port on the encoder to theASI-003 port onthe ARM.

97Adding Redundancy

When you finish configuring Nx1 encoder redundancy, the finished map should look like this:

Configuring 1x1 Remultiplexer RedundancyNMX supports 1x1 redundancy for MN20 remultiplexers using a Universal A/B switch.

Adding a Backup MN20 to the Network Group

To begin configuring 1x1 remultiplexer redundancy, add a backup MN20 to the network group. Because the backup must be exactly like the primary, copy the primary MN20 to quickly add the backup.

To add a backup MN20 to the network group:

1. Right-click the primary MN20 icon in the network tree or map and click the Copy button in the toolbar.

2. Select the network group icon in the network tree or click in a blank area of the map, and click the Paste button in the toolbar.

A new MN20 icon appears in the map.

3. Drag the new icon underneath the Mux-1 icon.

You’ll probably have to move the PSI Input icon out of the way.

4. Right-click the new MN20 icon and select Properties from the shortcut menu.

5. Change the name of the MN20 to something descriptive, such as Backup Mux and click OK.

98 Adding Redundancy

Connecting the Primary and Backup MN20s

After adding the backup MN20 to the network group, add the hot backup link between the primary and backup MN20. The hot backup link tells NMX that the two devices are redundant. Although redundancy switches still occur without this link, service downtime increases.

To connect the primary and backup remultiplexer:

1. Click the Primary Backup Link button in the bottom toolbar.

2. Position the mouse pointer over the primary MN20, and press and hold the left mouse pointer while you drag the cursor onto the backup MN20.

3. Release the mouse button.

A blue arrow is drawn between the two devices.

Connecting the PSI Input to the Backup MN20

Now that you have a backup remultiplexer on the map, you need to connect the PSI input device to it.

To connect the PSI input device to the backup MN20:

1. Use the Link button to draw a connection between the PSI input device and the backup MN20.

2. Connect the M2S port on the input device to the M2S port on the MN20.

Although the port icon is blue because you’ve already connected this port to the primary MN20, NMX lets you connect ports on input devices multiple times.

Primary Backup Link

99Adding Redundancy

When you finish, the map should now look like this:

Connecting the Encoders to the Backup MN20

All Harmonic encoders have two redundant ASI output ports. You have already connected the first ASI output port on each encoder to ports on an ARM card on the primary MN20. Now connect the second ASI port on each encoder to ports on an ARM card on the backup MN20. You can make the connections one by one, like you did for encoder redundancy, or you can make the connections all at once. This example makes the connections all at once, but shows you how to select just the devices you want to connect.

To connect the encoders to the backup MN20:

1. Hold down the shift button while you select the three encoders and the backup MN20.

2. From the Edit menu, select Network Group Links.

The Edit Connections dialog box opens showing just the devices you selected.

3. In the input pane, expand the tree under the first encoder so that you can see the ASI ports under the SMB2 card.

Note that the ASI-001 port is blue because it is already connected to the primary MN20.

4. In the output pane, expand the tree under the backup MN20 so that you can see the ASI ports under the ARM-001 card.

100 Adding Redundancy

5. Connect the ASI-002 port on the encoder to the ASI-001 port on the MN20 ARM card.

6. Expand the tree under the second encoder, and connect the ASI-002 port to the ASI-002 port on the MN20 ARM card.

7. Connect the ASI-002 port on the backup encoder to the ASI-003 port on the MN20 ARM card.

When you finish, the map should look like this:

Connect the ASI-002port on the encoderto the ASI-001port on the ARMcard.

101Adding Redundancy

Adding an A/B Switch When you originally connected devices in the network group, you connected the primary remultiplexer to a MOM output device. Now you have a backup MN20 in the network group, but you still have only one output stream. The only thing that changes if a redundancy switch occurs is that the backup MN20 outputs that stream instead of the primary MN20.

Use an A/B switch to select which MN20 is active.

To add an A/B switch to the network group:

1. Right-click in a blank area of the map, and select Create Switches > AB Switch from the shortcut menu.

2. Position the cursor over the area where you want to place the switch icon, and click the left mouse button.

The Create Object dialog box opens.

3. Enter a name and optionally a description for the switch.

4. Complete the remaining fields as follows:

■ Hardware Model: Select the Universal A/B switch model that you have in your network.

■ Switch Type: 2x1 Type

■ Number of Levels: 1

You need one level because you are outputting one stream from the MN20, an ASI stream through the MOM.

■ Level 1 Port Type: ASI

■ COM Port: The COM port on the NMX server computer to which the switch is connected. This value depends on how you have connected the server and the switch.

■ Hardware Address: (Disabled for stub switches) The hardware address of the switch in case several switches are cascaded using an X-bus connection and controlled by the same COM port. Each switch must have a unique hardware address. See the switch documentation for instructions to set the hardware address.

5. Click OK.

The A/B switch appears in the network tree and map.

102 Adding Redundancy

Connecting the MN20s to the A/B Switch

After adding the A/B switch to the map, connect the primary and backup MN20 to the A/B switch. First, you’ll need to delete the connections between the primary MN20 and the output device.

To connect the remultiplexers to the A/B switch:

1. Select the connection between the primary MN20 and the MOM output device and press Delete.

2. Click Yes when NMX asks if you want to remove the link.

Do not delete the output device—you can still use this later.

3. Use the Link button to draw a connection between the primary MN20 and the A/B switch.

4. In the Edit Connections dialog box, connect the ASI-001 port on the MN20 MOM-007 card to the Level-001 ASI-001 port on the A/B switch.

5. Repeat steps 2–3 to connect the backup MN20 to the A/B switch in the same way, using the second ASI port on the A/B switch.

103Adding Redundancy

Connecting the A/B Switch to the Output Device

To connect the A/B switch to the output devices:

1. Use the Link button to draw a connection between the A/B switch and the MOM output device.

2. Connect the ASI output from the switch to the ASI port on the output device.

The finished map looks like this:

3. Click Save to save the configuration.

The next step in configuring NMX is backing up your finished configuration. See “Protecting Against Data Loss” on page 105.

104 Adding Redundancy

Protecting Against Data Loss

While no one can predict system failure, NMX provides tools to protect against accidental data loss. Regular backups of your NMX configuration are the most important thing you can do to protect your data.

Domain Manager provides database administration tools to back up and restore the database catalog.

Backing up the NMX DatabaseFor data protection, back up the NMX database frequently, especially after configuration changes. By default, Domain Manager is configured to copy the database backup files to the C:\databasebkup directory on the SQL Server computer. When you installed the NMX server software, you might have chosen a different backup location.

Note: You can also use a third-party backup tool to back up the SQL Database. If you do backups with a third-party backup tool, use that same application to restore the database.

You must create the backup directory on the SQL server computer. Database backups fail if this directory does not exist.

In This Step:■ Back up your NMX

network configuration by backing up the database

106 Protecting Against Data Loss

After Domain Manager backs up the database to a folder on the SQL server computer, copy the backup to a remote computer. The backup file should not be on the same computer as the original database file.

To back up the NMX database:

1. From the Domain Manager Database menu, select Backup.

2. If you have not previously saved login information, the Database User Login dialog box opens.

3. In the login dialog box, enter the SQL system administrator user and password.

Harmonic began setting the SQL system administrator password to “harmonic” for computers shipped with NMX version 4.1.0.1 and later. Computers sent with earlier releases did not include a system administrator password. If you received your computer during the 4.1.0.1 release or later, enter:

User Name: sa

Password: harmonic

If you received your computer during an earlier release, and you have not set a system administrator password, leave the password field blank.

4. Optionally, check the box beside Remember login information.

If you check this box, the Database User Login dialog box does not open in the future.

5. Click OK.

The Backup Database dialog box opens.

6. In the List of Catalogs, select the catalog you want to back up.

The List of Catalogs organizes databases by type. The NMX database is under the NMX folder. NMXDB is the default database name, but you may have used another name.

7. In the File Name field, enter a name for the backup file, or select a file in the List of Files box if you want to overwrite an existing backup file with the current backup.

The List of Files field contains a list of all the files in the database backup folder on the SQL server computer.

107Protecting Against Data Loss

Note: If the List of Files field contains a message that says the system cannot find the directory, the backup directory does not exist on the SQL server computer. Close the dialog box, create the folder C:\databasebkup, or create the folder that you specified to use as the backup when you re-installed the software, and open the dialog box again.

8. Click OK.

NMX backs up the database catalog by copying it to the backup directory.

9. Copy the backup file to another network computer so the backup is protected against disk failure on the server computer.

Restoring the NMX DatabaseIn case of data loss or configuration error, you can restore previous configurations by restoring a database backup file. If necessary, copy the backup file to the SQL Server computer. If you are restoring a database catalog that is currently in use, you must disconnect NMX from the database catalog before restoring it.

Select the catalog

Enter a name for the databasebackup file.

you want to back up.

This message tells youthat the backupfolder c:\databasebkupdoes not exist. If yousee the message “FileNot Found,” there are no other backup files.

108 Protecting Against Data Loss

To disconnect from the current database catalog:

1. If necessary, open Domain Manager.

2. Click the red hand icon to stop the server.

3. When the server stops, right-click the Domain icon, and select Properties from the shortcut menu.

4. Delete the contents of the DB Catalog field and click OK.

Deleting the catalog name disconnects NMX from the database catalog. Even though you immediately receive a message that says Domain Manager could not connect to the database, it can take several minutes for this connection to actually close. If you try to restore the database and get an error message, wait several minutes and try again.

To restore the NMX database catalog:

1. From the Database menu, select Restore.

If you have not previously saved login information, the Database User Login dialog box opens.

2. In the login dialog box, enter the SQL system administrator user and password.

Harmonic began setting the SQL system administrator password to “harmonic” for computers shipped with NMX version 4.1.0.1 and later. Computers sent with earlier releases did not include a system administrator password. If you received your computer during the 4.1.0.1 release or later, enter:

User Name: sa

Password: harmonic

If you received your computer during an earlier release, and you have not set a system administrator password, leave the password field blank.

3. Optionally, check the box beside Remember login information.

If you check this box, the Database User Login dialog box does not open in the future.

4. Click OK.

The Restore Database dialog box opens.

109Protecting Against Data Loss

5. In the List of Catalogs pane, select the database catalog that you want to restore.

6. In the List of Files pane, select the backup file that you want to use to restore the catalog.

7. Click OK.

A confirmation dialog box opens.

8. Click Yes to confirm that you want to restore the catalog.

The database catalog is restored.

If you disconnected the active database, connect it before restarting the NMX server.

To restart the server:

1. In Domain Manager, right-click the Domain icon and select Properties from the shortcut menu.

The Domain Properties dialog box opens.

2. In the DB Catalog field, enter the name of the database catalog that you just restored.

3. Click OK to close the dialog box.

4. In the Domain Manager window, click the green arrow icon to restart the server.

5. Select the catalog that you want to restore.

6. Select the backup file that you want to restore from.

110 Protecting Against Data Loss

A

Creating a VOD Network

Large video-on-demand deployments can include thousands of Harmonic NSGs dispersed throughout multiple hubs and headends. One NMX server usually monitors a subset of NSGs, depending on the number of NSGs in the network. How you set up your VOD network in NMX depends on the physical configuration of your hubs and headends.

When you configure a VOD network, many of the devices you add to a network group are logical devices, which are not managed by NMX and may represent a network concept rather than an actual device. For example, a VOD serving area represents a group of customers who receive service from a specific NSG RF or IF output. By adding logical devices to a network group, you can create a view of your entire network and show how the NSG devices fit within the larger network.

In This Step:■ Create network groups

for video-on-demand networks

■ Create links between the network groups and devices

112 Creating a VOD Network

This chapter describes using NMX to configure a VOD network with NSG 9116s based on the following network diagram:

This network includes two sites, a headend and a hub, but the NSGs at both sites are managed by the same NMX server. When you configure VOD networks, create a separate network group for each site.

This network uses a Harmonic GTA 9111 optical transport device at the headend to aggregate the 1 GbE streams coming from the GbE switch to a single 10 GbE stream that is sent to another GTA at the hub. The GTA at the hub receives the 10 GbE stream and separates the single 1 GbE streams to send to the NSGs.

The network diagram shows four connections between the GbE switch and GTA 9111 at the headend because there are four connections between the second GTA 9111 and NSGs at the hub. The GTA does not switch between ports. Data input to port 3 on the GTA at the headend will be output on port 3 on the GTA 9111 at the hub, and so on.

Note that the diagram shows a network connection between the GTA 9111 at the headend to a GTA 9111 in the hub. For VOD networks, you can show this connection by linking network groups.

113Creating a VOD Network

There are also connections between NSGs. Each NSG GbE port receives and transmits, and it is common to cascade NSGs for source distribution purposes. In this diagram, two NSGs are connected to the GTA 9111 and cascaded to a third NSG. This configuration takes advantage of the 1 GbE output from the GTA. Each NSG 9116 supports about 660 MB, so each NSG connected to the GTA uses 660 MB and passes 330 MB to the cascaded NSG.

Multiple NSGs are connected to a headend for redundancy purposes.

Creating the Headend Network GroupThe headend network group includes the following platforms:

■ 3 video servers

■ 1 Cross Connect (representing the GbE switch in the network diagram)

■ 3 NSGs

■ 1 GTA 9111

■ 2 VOD serving areas

Creating the Network Group

Because NMX does not include default templates that are appropriate for all the devices in this network group, create this network group manually instead of using the Network Group wizard.

To create the network group:

1. Right-click the site icon in the network tree and select Create Network Group from the shortcut menu.

114 Creating a VOD Network

2. Enter a descriptive name for the network group, such as Headend.

3. Optionally, enter a description of the network group and select a background graphic.

4. Click OK.

NMX creates the Network Group icon and adds it to the tree and map.

5. Select the network group icon in the tree and press F10 to open the map for the network group.

Creating Video Servers

Next, add video servers to the network group.

To add the first video server:

1. Right-click anywhere in the map and select Create Logical Devices > Video Server from the shortcut menu.

2. Position the cursor, which now looks like a diamond, over an empty spot on the map and click the left mouse button.

The Create Object dialog box opens.

115Creating a VOD Network

3. Optionally, enter a new name and description for the video server.

All other default settings are fine. The dialog box should look like this:

4. Click OK.

NMX adds the video server to the map.

You can add two more video servers the same way you added the first, or copy and paste:

1. Right-click the video server and select Copy from the shortcut menu.

2. Right-click in an empty space on the map and select Paste from the shortcut menu.

NMX adds another video server to the map.

3. Repeat step 2 to add a third video server to the map.

4. Right-click one of the new video servers and select Properties from the shortcut menu.

5. Enter a new name for the video server and click OK.

6. Repeat steps 4 and 5 to rename the other video server.

116 Creating a VOD Network

Creating Cross Connect Devices

Next, create a Cross Connect device to represent the Ethernet switch.

To create a Cross Connect device:

1. Right-click in a blank area of the map and select Create Logical Devices > Cross Connect from the shortcut menu.

2. Position the cursor in the area of the map where you want the Cross Connect icon to appear and click the left mouse button.

The Create Object dialog box opens.

3. In the Type field, select IP Cross Connect.

Note: Drop-down arrows for fields are not visible. Move the cursor to the right-side of a field and press the left mouse button. Click again to make a selection from the list.

4. In the Number of Inputs field, enter the number of input ports on your switch.

A typical switch in this type of network has 12 input and 12 output ports, but you should enter the correct number for your switch.

5. In the Number of Outputs field, enter the number of output ports on your switch.

117Creating a VOD Network

You can leave all the other fields set to their defaults. The dialog box should look like this:

6. Click OK.

You should now have a Cross Connect icon on your map.

Creating NSGs Next, add three NSGs to the network group.

To add the NSGs:

1. Right-click a blank spot in the map and select Create Physical Device from Template from the shortcut menu.

2. In the Type drop-down list, select NSG.

3. Enter a name for the NSG in the Name field.

118 Creating a VOD Network

4. In the Template Name field under the Use Server Template radio button, select Sys-NSG-9116 or the model you have.

5. Click OK.

The NSG icon appears in the map.

6. Copy the NSG to add two more NSGs to the map.

7. Rename the copied NSGs in the NSG Properties dialog box.

3. Enter a name for the

2. Select NSG in the Type drop-down list.

4. Select Sys-NSG-9116

template in the Name field.

or your NSG model.

119Creating a VOD Network

Creating the GTA 9111

Next, add the GTA icon to the map.

To add the GTA:

1. Right-click in a blank area of the map and select Create Physical Devices > Optical Transport from the shortcut menu.

2. Position the cursor over a blank area of the map and press the left mouse button.

3. Optionally, change the name and description of the device.

4. Enter the IP address of the device.

5. Optionally, change the SNMP properties for your network.

The default settings are fine in most cases. The dialog box should look something like this:

6. Click OK.

120 Creating a VOD Network

Creating the VOD Serving Areas

Finally, add the two VOD serving areas to the Headend network group.

To create the VOD serving areas:

1. Right-click in a blank spot in the map and select Create Logical Devices > VOD Serving Area from the shortcut menu.

2. Move the cursor to a blank spot in the map where you want the icon to appear, and press the left mouse button.

The Create Object dialog box opens.

3. In the Number of Ports field, enter 3.

4. Click OK.

5. Repeat steps 1 and 2 to create the second VOD serving area.

Your Headend map should now look like this:

121Creating a VOD Network

Connecting the Devices

Before you begin connecting devices, take another look at the network configuration.

The following connections are required:

■ Video Server-1 to Cross Connect-1

■ Video Server-2 to Cross Connect-1

■ Video Server-3 to Cross Connect-1

■ Cross Connect-1 to NSG-1 and NSG-3

■ Cross Connect-1 to GTA-1 (four connections)

■ GTA-1 to GTA-2

■ NSG-1 to Serving Area-1 and Serving Area-2

■ NSG-2 to Serving Area-1 and Serving Area-2

■ NSG-3 to Serving Area-1 and Serving Area-2

These connections are all straightforward—except for the connection between the GTAs. Because we haven’t made the hub network group yet, don’t worry about this connection right now.

122 Creating a VOD Network

Connect the Video Servers to the Cross Connect

To connect the video servers to the Cross Connect:

1. Right-click in a blank area of the map and select Network Group Links from the shortcut menu.

The Edit Connections dialog box opens.

2. In the tree on the left, right-click the Video Server-1 icon and select Expand All to open the tree beneath the video server.

3. In the tree on the right, expand the tree beneath the Cross Connect-1.

4. Select the first Ethernet port under Video Server-1 and the first Ethernet port under Cross Connect-1.

5. Click Connect.

The connection appears in the table below.

6. In the same way, connect Video Server-2 and 3 to the Cross Connect.

4. Select the firstEthernet portunder Video Server 1 and the

on Cross

5. Click Connect.

The connection appears in the table below.

first Ethernet port

Connect 1.

123Creating a VOD Network

Connect the Cross Connect to the NSGs and GTA

Based on the network diagram, connect Cross Connect-1 to NSG-1, NSG-3, and the GTA.To connect the Cross Connect to the NSGs:

1. In the left pane, open the tree under Cross Connect-1.

2. In the right pane, open the tree under NSG-1.

3. Connect the Ethernet-004 port under the Cross Connect to the GbE-001 port under NSG-1.

4. In the right pane, open the tree under NSG-3, and connect the Ethernet-005 port under Cross Connect-1 to the first GbE port under NSG-3.

Select the firstEthernet port on the Cross Connect.

Select the first GbE port on NSG-1.

124 Creating a VOD Network

To connect the Cross Connect to the GTA:

1. In the right pane, open the tree under the GTA.

2. Connect the Ethernet-006 port under Cross-Connect-1 to the GbE-001 port under the Local Interfaces card on the GTA.

3. Connect the Cross Connect Ethernet ports 7, 8, and 9 to GbE ports 2, 3, and 4.

Connect the Ethernet-006 on theCross Connect tothe GbE-001 port on the GTA.

125Creating a VOD Network

Connect NSG-1 and NSG-3 to NSG-2

In the network diagram, NSG-2 is connected to NSG-1 and NSG-3. It is common to daisy-chain NSGs so that the input received by the first is passed to the second, and so on.

Tip: It may seem wrong to connect an input port to an input port, but remember that the GbE ports both receive and transmit.

To connect NSG-1 and NSG-3 to NSG-2:

1. In the left pane, open the tree beneath NSG-1.

2. In the right pane, open the tree beneath NSG-2.

3. Connect the GbE-003 on NSG-1 port to the GbE-001 port on NSG-2.

4. Now open the tree under NSG-3 in the left pane.

5. Connect the GbE-003 port under NSG-3 to the GbE-002 port under NSG-2.

Connect NSG-1 to NSG-2.

126 Creating a VOD Network

Connect the NSGs to the VOD Serving Areas

To connect the NSGs to the VOD serving areas:

1. Open the trees under NSG-1 in the left pane and VOD Serving Area-1 and Serving Area-2 in the right pane.

2. Connect the first IF output port under NSG-1 to the first IF input port under Serving Area-1.

3. Connect the second IF output port under NSG-1 to the first IF input port under Serving Area-2.

Connect the firstGbE port under NSG-3 to thesecond GbE porton NSG-2.

127Creating a VOD Network

4. Repeat steps 1–3 to connect NSG-2 and NSG-3 to VOD Serving Area-1 and Serving Area-2.

NSG-2 connects to the second IF input port under Service Area 1 and the second IF input port under Service Area 2. NSG-3 connects to the third IF input port under Service Area 1 and the third IF input port under Service Area 2.

5. Click OK.

The Headend network group is now finished. Note that the four connections between the Cross Connect and GTA are represented by one line in the map.

128 Creating a VOD Network

In the headend map, the serving area icons are red because the NSG platforms have a service affecting alarm—they are offline. The serving area icons will turn green when you bring the NSG platforms online.

Creating the Hub Network GroupThe hub network group includes the following platforms:

■ 1 GTA

■ 6 NSGs

■ 3 VOD serving areas

Use the same general procedures to create the hub network group that you used to create the headend network group.

When you create platforms, remember that:

■ VOD Serving Area-3 and Serving Area-4 have 4 input ports

■ VOD Serving Area-5 has 2 input ports

When you connect ports, be sure to connect:

■ GTA-2 to NSG-4, NSG-6, NSG-7, and NSG-9

■ NSG-4 and NSG-6 to NSG-5

■ NSG-7 and NSG-9 to NSG-8

129Creating a VOD Network

■ NSG-4 and NSG-5 to VOD Serving Area-3 and Serving Area-4

■ NSG-6 and NSG-7 to VOD Serving Area-3 and Serving Area-4

■ NSG-8 and NSG-9 to VOD Serving Area-5

When you finish, the hub network group map should look like this:

The VOD serving areas in this map are red because there is a major alarm on the NSGs—they are offline. The serving area icons will turn green when you put the NSGs online.

Connecting the Headend to the Hub

When you configure VOD network groups, you can connect them. The connection between network groups indicates how data flows from equipment at one location to equipment at another.

When you link network groups, the groups appear within each other as proxy network groups. You can then make connections between the proxy icon and the equipment in the network group.

130 Creating a VOD Network

To link the headend to the hub:

1. Select the site icon in the network tree and press F10 to view the site-level map.

2. In the bottom toolbar, click the Create New Link button.

The mouse pointer turns into a pen when you position it in the map.

3. Move the mouse pointer on top of the headend icon, and press and hold the left mouse button while you drag the pointer onto the hub icon.

You can see a line being drawn as you drag the pointer onto the hub.

4. Release the mouse button when you are on top of the hub icon.

An arrow appears between the two icons.

5. Double-click the Headend icon to open the headend map.

An icon named Hub_Proxy is now in the map, probably on top of another icon.

6. Move the hub proxy icon to a free space in the map to the right of the GTA.

Configuring the Hub Proxy

The proxy icon that appears inside a network group when you connect it to another represents the devices in the proxy network group. You can make connections between the proxy icon and other devices in the network group.

Before you can make these connections, you need to set properties for the proxy and specify the type and number of connections.

Create New Link button

131Creating a VOD Network

To set the proxy network group properties:

1. Right-click the proxy network group icon and select Properties from the shortcut menu.

2. In the Type field, select Ethernet.

3. In the Number of Ports field, enter 1.

The Number of Ports fields represents the number of connections between the two network groups. In our network, the GTA sends one stream to the GTA at the hub.

4. Click OK.

Connecting the Proxy to Devices

Now that you have configured ports for the proxy, connect it to devices in the network group.

1. In the bottom toolbar, click the Create New Link button.

2. Draw the connection between the GTA and the Hub_Proxy icon.

The Edit Connections dialog box opens.

3. In the left pane, select the Network Interface (10 GbE) port on the GTA.

4. In the right pane, select the Ethernet port on the Hub Proxy.

132 Creating a VOD Network

5. Click Connect.

6. Click OK.

The finished network map should now look like this:

Connect the NetworkInterface port on theGTA to the Ethernetport on the Proxy.

133Creating a VOD Network

Configuring the Headend Proxy

Now you can finish configuring the hub network group. To begin, set port properties for the headend proxy that appears in the Hub network group.

To configure the headend proxy:

1. Select the Hub network group icon in the network tree and press F10 to open the Hub map.

2. Right-click the Headend_Proxy icon and select Properties from the shortcut menu.

3. In the Type field, select Ethernet.

4. In the Number of Ports field, enter 1.

5. Click OK.

Connecting the Proxy to Devices

Now that you’ve configured ports for the headend proxy, connect it to the GTA-2 device in the network group.

To connect the proxy to devices:

1. Click the Create New Link button in the bottom toolbar and draw the connection between the Proxy and the GTA.

2. Connect the Proxy Ethernet port to the Network Interface (10GbE) port.

3. Click OK.

134 Creating a VOD Network

When you finish, the map should look like this:

Putting Devices Online

To finish the configuration, put the devices online. Because there are many devices, it is quicker to do this in Spreadsheet View.

To put devices online:

1. Click the Spreadsheet View button in the top toolbar.

The Spreadsheet opens with the Hub network group selected by default.

Tip: Use the Bulk Set feature to enter the network information for all the devices at once.

2. Set the Network Address and Physical Address for each NSG and the Network Address for the GTA. See the tip in “Configuring the BNG Network Properties” for more information on using the Bulk Set feature.

3. Check the box under In Service for each device.

135Creating a VOD Network

4. Click Save.

5. From the Network Group drop-down list, select Headend.

6. Set the Network Address and Physical Address for the devices in the Headend network group.

7. Check the In Service box for the devices in the Headend network group, and click Save.

Your VOD network configuration is now finished. Remember to back up your configuration by making a backup of your NMX database. See “Protecting Against Data Loss” on page 105 for instructions.

Viewing VOD StatisticsIf you purchased the NMX statistical reporting tool, NMX creates nightly reports on NSG usage. Additionally, the online statistical reporting tool generates utilization history reports for a given service group or network group, as well as service group comparisons and threshold percentages.

See the NMX online help for more information about NMX reports.

136 Creating a VOD Network

Creating a BNG Network

NMX includes a network group template with 1x1 redundant BNG 6301s. The BNG 6301, which accepts four input ASI streams and outputs one GbE stream, typically receives multiple program transport streams as ASI inputs, and acts as a transmission device to send single program IP transport streams to regional headends.

For this example, you create the BNG network group from the template, then configure services. The nice thing about BNGs is that you don’t need to do much when configuring the input transports—the BNG actually does that for you by reading the PSI included with the input streams.

But it’s not very likely that your BNG inputs will match the BNG inputs used for this example. So we’ll go through the process of extracting inputs, then manually create some inputs for this example.

This example uses four ASI input transports, each with two programs, and eight IP output transports, each with one program. We can assume that the input transports include a PAT for the transport and PMTs for each program. The PMTs will be passed to the output transports with the programs, and a separate transport will carry the PATs.

Note: This network group does not include CAS support. See “Managing DM Network CherryPickers” on page 161 for an example of a network group that includes CAS support.

In This Step:■ Create a BNG network

group using a template

■ Configure services for the network group

138 Creating a BNG Network

Creating the BNG Network GroupTo create the network group:

1. Right-click the site icon and select Create Network Group from Template from the shortcut menu.

2. In the Name field, enter a name for the network group, such as 1x1 BNG.

In the Template Name field under the Use Server Template radio button, make sure the Sys-1x1 BNG NG template is selected.

3. Click OK.

NMX creates the network group, including the platform links.

Configuring the BNG Network Properties

The network group template created the devices in the network group with default network properties. You need to set these properties for your network.

139Creating a BNG Network

To set network properties:

1. Click the Display Spreadsheet Only button in the top toolbar to open Spreadsheet View.

2. Make sure that the BNG network group is selected in the Network Group field.

3. Set the network address, physical address, subnet mask, and identification number for both BNGs.

Use a unique value, such as the device serial number, for the identification number.

Tip: Use the Fill Series Bulk Set feature of Spread Sheet view to set the network address for both BNGs at once if their IP addresses are sequential. Click the left-most column (under the green arrow) to select the BNGs. A blue arrow in this column indicates a row is selected. Click the icon at the right side of the Network Address cell in the Bulk Set row and select Fill Series. Then enter the IP address of the first BNG in this cell. When you press Enter, NMX assigns the IP address to the first BNG and the next IP address to the second BNG. For example, if you entered 192.168.24.200, NMX assigns this IP address to the first BNG, and 192.168.24.201 to the next BNG. You can also use Bulk Set to assign the same subnet mask to each BNG.

4. Check the In Service box for both BNGs and the switch to put these devices online.

Display Spreadsheet button

140 Creating a BNG Network

5. Click the Display Tree and Map View button to return to Tree and Map view.

When the devices come online, the icons turn green in the map.

Enabling HHP In some redundancy switches, NMX may not be able to shut down the GbE output from the primary BNG. For example, if the connection between the BNG and NMX is lost, NMX issues a time-out alarm for the BNG, and provisions the backup BNG with the circuits from the primary. However, the primary BNG may still be operating normally even though it lost communication with NMX. In this case, you now have two BNGs sending the same output.

To prevent this scenario, enable the Harmonic Hello Protocol (HHP) in the BNG Properties dialog box. When you enable HHP, a backup BNG taking over in a redundancy switching event will send a command (over a unique multicast address on the video IP network) to turn off the outputs of the formerly active BNG. During a redundancy switch, the backup BNG assumes all responsibilities of the primary BNG, including sending HHP messages at the same multicast address.

The BNG always listens for HHP packets at the HHP address you specify in NMX. If a primary BNG detects HHP messages sent to its multicast IP address, it immediately “backs off” and stops sending output. This leaves the backup BNG free to operate without the primary BNG sending the same output.

To enable HHP:

1. Right-click the first BNG icon and select Properties from the shortcut menu.

2. Scroll through the BNG properties until you see HHP Properties.

141Creating a BNG Network

3. Set HHP Enable to True, and enter the multicast IP address you want to use to send HHP messages.

4. Click Apply, then OK.

5. Repeat steps 1-3 to enable HHP for the backup BNG.

The primary and backup BNG should both use the same multicast address.

Configuring the BNG GbE Ports

Now that you have set properties for the BNG platforms, set properties for the GbE port on those platforms.

To configure the GbE port:

1. In Map View, double-click the first BNG icon to display the back panel graphic.

2. Right-click on top of the GbE1 port, and select Properties from the shortcut menu.

Note: The two GbE ports are redundant, and you cannot configure them separately. In this case, all configuration is done on the GbE1 port.

142 Creating a BNG Network

3. Under Primary Channel, enter the network address, subnet mask, and default gateway for the primary GbE connector.

4. Under Backup Channel, enter the network address, subnet mask, and default gateway for the backup GbE connector.

5. Under Redundancy Information, set the Redundancy Mode to Automatic.

In Automatic mode, NMX automatically switches to the backup GbE channel when it detects a service-affecting alarm on the primary channel. If you leave this field set to Manual, you must make the switch in the Active Channel field.

6. Click Apply, then OK.

7. Repeat steps 1–6 to configure the GbE port on the backup BNG.

That completes the network group configuration.

143Creating a BNG Network

Configuring ServicesNow that you have finished the hardware configuration, configure services for the network group. The 1x1 BNG network group has four ASI inputs and a GbE output. For this example, each ASI stream carries two programs, and each of these programs outputs as a separate transport.

Begin by extracting ASI inputs because this is what you should do when configuring services for your BNG network. Because your actual BNG inputs may or may not be appropriate for use in this example, we’ll also create some ASI inputs manually.

Extracting ASI Inputs The BNG extracts input data by reading PSI tables, PSI and SI tables, or PSIP tables. By default, the BNG reads PSI and SI tables. If you want to change the tables used by the BNG, you can change the Extraction Mode on the BNG Properties page.

For this example, we will leave the default extraction mode. The BNG reads the transport PAT and PMT tables to determine the transport contents. NMX then creates a transport that includes the following data:

■ Transport ID for the transports

■ Program number for programs

■ PID, bit rate, name, and type for elementary streams

You can extract the contents of a single input or all inputs at once. To save time, do it all at once. For the extraction to work, you must have an actual BNG receiving ASI inputs in your network.

Note: If you are working on this example without actual hardware, skip this section, start the service configuration as described in “Starting the Service Configuration” on page 144, then go on to “Creating Transports Manually” on page 145.

To extract the BNG inputs:

1. In the network tree or map, right-click the BNG icon representing the BNG receiving inputs in your network group, and select Extract Inputs from the shortcut menu.

144 Creating a BNG Network

The Extract Inputs dialog box opens and shows you the progress of the extraction. When finished, the dialog box displays the transports in a tree format.

2. Click the Save to File button.

The Save As dialog box opens.

3. Browse to select the folder where you want to save the file, enter a descriptive name for the file, such as BNG-1-inputs, and click Save.

NMX saves the transport data to a file.

Note: Because the redundant BNGs in this example both receive the same input transports, you do not need to extract inputs for the second BNG.

Starting the Service Configuration

Now switch to Service View to begin configuring the input and output services.

To begin the service configuration:

1. Click the Output Service View tab to open the Service tree.

Note: Output Service View is the default view. If you changed the view, your tab may say Input Service View or Service View.

2. Right-click the 1x1 BNG network group icon in the tree and select New Service Configuration from the shortcut menu.

The Create New Service Configuration dialog box opens.

3. Right-click the New Service Configuration icon at the top of the input tree and select Rename from the shortcut menu.

The text is now highlighted for editing.

4. Enter a descriptive name for the service configuration such as 1x1 BNG and press Enter.

The name changes at the top of the input and output trees.

145Creating a BNG Network

Creating Input Transports From a File

Now use the file you created by extracting the BNG inputs to create the input transports.

To create a transport from a file:

1. Right-click the Transport icon in the input tree and select Add From File from the shortcut menu.

The Open dialog box opens with the Templates folder selected by default.

2. Select the file you saved when you extracted the BNG inputs, and click Open.

NMX adds the transports to the input tree. Note that the transport PSI does not provide all stream properties. You might want to change program names or other stream properties. If so, the next sections describe setting properties for programs and streams.

Creating Transports Manually

If you did not extract inputs, you can manually create some ASI input transports to use for this example. If you did extract inputs, you can skip this section or create more transports to use for this example.

To create the first ASI input transport:

1. Right-click the Transports icon in the input tree and select Add Transport from the shortcut menu.

The Select Input Type of New Transport dialog box opens.

146 Creating a BNG Network

2. Enter a name for the transport such as Transport 1, and click OK.

The default injection location at the bundling multiplexer is correct, and you do not need to set any Advanced properties.

3. Right-click the transport icon and select Add Program from the shortcut menu.

The Enter Name for New Program dialog box opens.

4. Enter HBO for the name of the program, and click OK.

The program appears under the transport icon.

Note: The default program properties are fine for this example. If you want to change program properties, right-click the program icon and select Properties from the shortcut menu.

5. Right-click the program and select Add Digital Video from the shortcut menu.

The Enter Name for new HBO Video dialog box opens with HBO Video as the default name.

147Creating a BNG Network

6. Click OK.

7. Right-click the program icon and select Add Digital Audio from the shortcut menu.

8. Click OK to accept the default name, HBO Audio.

9. .Repeat steps 3–8 to add another program, CNN, to the transport.

Setting Properties After adding the audio and video streams, set properties for them.

To set the HBO video properties:

1. Right-click the HBO video icon and select Properties from the shortcut menu.

2. Enter the Stream PID, Stream Type, and Bit Rate.

For this example, you can leave most of these values set to the default. However, if NMX set the HBO video PID to 0x0, you must change this value. The PAT always uses PID 0x0.

Do not close the dialog box when you finish.

Note: If your digital video streams were configured at a variable bit rate, be sure to set the maximum bit rate used by the stream in the Bit Rate field. If you do not set the maximum bit rate, the BNG output transport can be oversubscribed.

148 Creating a BNG Network

To set the HBO audio properties:

1. While you still have the video properties dialog box open, select HBO Audio in the tree on the left side.

2. Set the audio properties as appropriate.

3. Click OK to save the changes and close the dialog box.

When you finish setting the HBO audio and video properties, repeat these steps to set the CNN audio and video properties.

Adding PSI Streams For this example, you are going to pass through the incoming PAT streams, but PMTs are internally generated. If you extracted input transports, there may be a PAT included in the transport. However, you need to delete this PAT and add a data stream instead.

When you include a PAT in an output transport, its PID must be 0x0. We want to create an output transport that carries all four PATs (one from each input transport), but we can’t have four streams with PID 0x0 in the same transport.

To get around this problem, add the PAT stream to the input transport as a data stream instead of a PAT. Since NMX does not generate the PAT, it just sees the stream as data that it passes through. When you use a data stream, you can leave the PID set to 0x0 on the input, but change it on the output so that each PAT has a unique PID.

1. Select HBO Audio

149Creating a BNG Network

To add a data stream:

1. If necessary, right-click the PAT icon in the input transport and select Delete from the shortcut menu.

The PAT is deleted.

2. Right-click the transport icon and select Add Data from the shortcut menu.

3. Enter a descriptive name for the stream, such as Transport 1 PAT, and click OK.

NMX adds the data stream to the transport. Note that the default bit rate for the stream is 2 Mbps — much higher than necessary.

4. Right-click the new data stream and select Properties from the shortcut menu.

5. In the Properties dialog box, change the bit rate to 25 Kbps.

6. If necessary, change the PID to 0x0 because PAT tables always use PID 0.

Note: The default stream type, 13818-1 Private Sections is correct.

7. Click OK.

You’ve now finished the first transport stream.

150 Creating a BNG Network

Creating the Remaining ASI Input Transports

Now that you’ve made one transport, you can make the remaining transports just like you did the first, or you can copy and paste it to create the remaining three transports. You might find that it takes longer to rename the streams in the copied transport than it would take to create a new transport from scratch, but do what you find easiest.

To copy the first transport:

1. Right-click the Transport-1 icon and select Copy from the shortcut menu.

2. Right-click the Transports icon and select Paste.

3. Rename each transport, video, and audio stream to avoid confusion.

When you finish, the input tree should look something like this:

151Creating a BNG Network

Creating the Output Transports

After you have created all the input transports, create the IP output transports. Each transport contains one program.

To create an IP output:

1. Right-click the Service Configuration icon in the output tree and select Add Transport from the shortcut menu.

The Specify Output Type of Transport dialog box opens.

2. Enter a descriptive name for the transport, such as HBO IP TS.

3. In the Output Signal/Protocol drop-down list, select IP.

4. Click OK.

If you did not change the default Options setting, NMX automatically adds a PAT and several descriptors to the transport stream.

5. If necessary, delete the PAT that NMX added.

6. Right-click the transport icon and select Properties from the shortcut menu.

The General Output Properties dialog box has three tabs: General, Delivery, and IP Properties.

7. Set the General Output Properties as necessary:

Note: See the online help for complete General, Delivery, and IP Properties field details.

152 Creating a BNG Network

General Properties

■ Max Bit Rate. This bit rate is the bit rate of the ASI stream output from the ASI monitoring port on the BNG. If you are using the ASI monitoring port, its maximum bit rate is 120 Mbps.

Tip: You can also set properties for the IP transports in Spreadsheet View. You might want to add all the transports first, then switch to Spreadsheet View to set properties.

Delivery Properties

The Delivery properties are relevant only when you generate SI through the source BNG. Because we are not generating SI, we aren’t going to set these properties.

IP Properties

■ Destination IP address. Enter the IP address to which you want to send the transport. The IP address can be a unicast or multicast IP address.

■ Destination UDP Port. Enter the UDP port number at the destination.

■ Time to Live. The number of hops a packet can use to reach its destination plus the number of seconds a packet can live in the network. For example, if you want a packet to use no more than 5 hops and spend no more than 10 seconds reaching its destination, set TTL to 15. Packets that do not reach their destination within the TTL are dropped. Set TTL so that network traffic does not go further than it needs to go or get caught in an endless loop. Enter a value between 1 and 255.

■ Max Transfer Unit. The maximum number of octets in an Ethernet frame. Enter a value between 64 and 1536, or let NMX automatically calculate it when you enter the Number of MPEG Packets.

■ Number of MPEG Packets. The number of MPEG packets. Entering the number of MPEG packets automatically calculates the MTU based on the following equation:

MTU = IP Header (20 Bytes) + UDP Header (8 Bytes) + UDP Payload (Number of Packets x 188)

153Creating a BNG Network

NMX automatically calculates the MTU after you enter the number of packets. You can then manually change the MTU if necessary.

■ Fixed MAC Address. If you entered a unicast Destination IP Address, you can check this box and assign the MAC address manually, or do not check this box and allow the BNG to determine the MAC address using ARP/RARP protocol.

■ Destination MAC Address. If you entered a multicast IP address, the BNG automatically assigns a multicast destination MAC address. If you entered a unicast IP address, enter the destination MAC address if you checked the Fixed MAC box.

8. When you finish setting properties, click OK.

Adding a Program to the Output Transport

To add a program to the output transport:

1. Right-click the transport icon and select Add Program from the shortcut menu.

The Select Inputs dialog box opens. This dialog box contains a list of the programs that you created in the input tree.

2. Check the box beside HBO, and click OK.

The program HBO appears under the HBO transport.

154 Creating a BNG Network

Creating the Remaining Single Program Transports

Create the other seven output transports the same way you created the HBO transport. When you finish, the output tree should look something like this:

Creating the PSI Transport

After you’ve added the transports for each program, create a transport to carry PSI.

1. Create a new IP transport just like you did for the program transports.

2. Delete the PAT that NMX automatically added to the transport.

3. Right-click the transport icon and select Add Stream from the shortcut menu.

The Select Inputs dialog box opens.

4. Check the box beside all four input data streams, and click OK.

155Creating a BNG Network

The data streams appear under the transport. NMX automatically changes the PID of three streams, and leaves one PID set to 0x0.

5. Right-click the data stream with PID 0x0 and select Properties from the shortcut menu.

Note that the PID field has a red background. The red background signifies that the PID value is below the minimum PID set in the Options dialog box.

6. Change the PID to an unused value, but do not click OK.

7. In the tree on the left side of the dialog box, click another data stream to open the properties for this stream.

Click another datastream to viewproperties for thatstream.

156 Creating a BNG Network

8. Continue to change the PIDs as necessary, then click OK in the General Output Properties dialog box.

9. Click OK in the New Service Configuration dialog box to save the changes.

Connecting ServicesWhen you’ve finished configuring services, connect them to the network group hardware.

Connecting the Input Services

To connect the input services to the network:

1. In the Service tree, right-click the service configuration icon and select Connect Service To Network from the shortcut menu.

The Connect Service to Network dialog box opens with the Input Service page opened by default. The Input Service page has two panes: Input Services and Input Devices. You must connect the input services to the ports they flow through.

2. In the Connect Service to Network dialog box, open the tree under the Transports icon in the Input Services pane.

157Creating a BNG Network

3. In the Input Services pane, select Transport 1.

4. In the Input Devices pane, select the ASI port under the first input device.

Of course, when you connect services for real, be sure to select the actual input device used by the selected transport.

5. Click Add.

Transport 1 appears under the ASI port.

6. Repeat steps 3–5 to connect Transports 2–4 to the three other input devices.

3. Select Transport 1in the left pane.

4. Select the ASI port underthe first input device.

5. Click Add.

158 Creating a BNG Network

Connecting the Output Services

To connect the output services:

1. Click the Output Service tab to open the Output Service pane.

2. Expand the tree under the 1x1 BNG Service Config icon to see the output transports.

3. Select the first output transport in the left pane, select the GbE port in the right pane, and click Add.

4. Repeat step 3 to connect each output transport to the GbE port.

You can connect multiple IP outputs to the same port.

Note: You can also connect all the transports at once. Hold down the Shift key while you select the first and last transport—this selects all the transports. Then select the GbE port and click Add.

When you finish the Output Devices pane should look like this:

5. Click OK to save the connections and close the dialog box.

Connect the first output transport to the GbE port.

159Creating a BNG Network

Activating the Service ConfigurationAfter connecting services to the ports they flow through, activate the service configuration to provision services to the devices in the network group.

To activate the service configuration:

➭ Right-click the service configuration icon and select Activate Service Configuration from the shortcut menu.

A dialog box shows the progress. When the provisioning finishes, the word Active appears in parentheses beside the service configuration icon.

Note: If you have more than one service configuration within a network group, only one service configuration can be active at a time.

After you activate the service configuration, you have finished the BNG network configuration. You can see how NMX provisioned streams on each platform by checking the stream list for each device.

To view the streams provisioned to a device:

➭ Right-click a device icon in the network tree or map, and select Stream List from the shortcut menu.

When you finish creating the BNG network, remember to back up your configuration by backing up the NMX database. See “Protecting Against Data Loss” on page 105 for instructions.

160 Creating a BNG Network

Managing DM NetworkCherryPickers

NMX manages the Terayon™ DM3200 and DM6400 CherryPickers. The DM Network CherryPicker supports rate-shaping MPEG streams at a variable or constant bit rate. NMX supports ASI and DHEI inputs to a CherryPicker, and ASI outputs.

You must complete some initial CherryPicker configuration before you can manage the device in NMX. This configuration is described in the Harmonic application note NMX CherryPicker Setup, available from Harmonic Customer Support.

Creating a Network GroupFor this example, you are going to create a network group with one DM3200 CherryPicker that receives ASI and DHEI inputs, and outputs a variable bit rate ASI transport to a BNG, which then sends one scrambled RF output. The BNG generates PSI.

In This Step:■ Create a network

group that includes DM Network CherryPickers

■ Configure services for the network group

162 Managing DM Network CherryPickers

Creating the Network Group Icon

To begin, create the network group icon.

To create the network group icon:

1. Right-click the site icon in the network tree and select Create Network group from the shortcut menu.

2. Enter a descriptive name for the network group such as DM CherryPicker NG, and optionally add a description and background graphic.

The default CAS Mode, DVB Simulcrypt/Clear, is correct.

3. Click OK.

NMX adds the network group to the tree and map.

4. In Map view, double-click the DM CherryPicker NG icon to open the map for the network group, or in Tree view, select the network group icon and press F10.

Creating Input Devices

To begin adding devices to the network group, add ASI and DHEI input devices.

To add the input devices:

1. Right-click in a blank area of the map and select Create Logical Devices > Input Device from the shortcut menu.

The cursor changes to a diamond shape.

2. Position the cursor where you want the input device icon to be located, and press the left mouse button.

The Create Object Dialog box opens.

3. Change the name of the device to ASI Input-1 so you can easily recognize it, and click OK.

NMX adds the input device to the map and tree.

4. Repeat steps 1 and 2 to begin creating the DHEI input.

5. Change the name of the device to DHEI Input-1, and change the Port 1 Type to DHEI.

163Managing DM Network CherryPickers

Note: Drop-down arrows for fields are not visible. Move the cursor to the right-side of a field and press the left mouse button. Click again to make a selection from the list.

6. Click OK.

NMX adds the input device to the map and tree.

Adding a CherryPicker Next, add the CherryPicker to the network group.

Note: When you build a map with the Terayon CherryPicker and want CherryPicker to generate the PSI/SI files, you must clear the Input Transports and Output Transports on the PSI/SI General dialog box of the Services tab found on the Options dialog box.

To add a DM Network CherryPicker to the network group:

1. In the bottom toolbar, click the Create DM Network CherryPicker button, then move the cursor to a blank spot in the map where you want to place the CherryPicker icon.

2. Click the left mouse button.

The Create Object dialog box opens.

Create DM Network CherryPicker button

164 Managing DM Network CherryPickers

3. Set properties for the CherryPicker as appropriate, including the hardware model and IP address.

4. Set the PSI Spooler field to False.

In this example, the downstream BNG is spooling PSI.

5. Leave the Operation Mode field set to Normal because you want NMX to manage the CherryPicker, not just monitor alarms.

Note: NMX does not assign IP addresses to CherryPickers. You must manually assign an IP address to the device as part of the configuration you do before managing a CherryPicker with NMX.

6. When you finish, click OK.

NMX adds the CherryPicker icon to the tree and map.

Adding Cards to the CherryPicker

After you have added the CherryPicker to the network group, add cards. You do not need to do this if your CherryPicker is online and NMX automatically discovers the cards in the device.

To add cards:

1. Double-click the CherryPicker icon in the map to open the back panel graphic.

As you can see, there are no cards in the device. The next steps describe how to add input and output cards for this example, but you should add the appropriate cards for your CherryPicker.

165Managing DM Network CherryPickers

2. Right-click in the blank area of slot 2 (C), and select Create Card > Input ASI DHEI from the shortcut menu.

NMX adds the card to the back panel graphic and tree.

3. Right-click in the blank area of slot 3 (D), and select Create Card > Output ASI DHEI from the shortcut menu.

4. When you finish, close the back panel graphic.

Adding a BNG In this network group, a BNG provides scrambling and PSI insertion for the CherryPicker output, as well as conversion to RF.

To add a BNG:

1. Right-click in a blank area of the map and select Create Physical Device from Template... from the shortcut menu.

The Create Object from Template dialog box opens, with the Sys-BNG-1G2A-XXX-4QX template selected by default. This example uses this template, but you can select the template appropriate for your BNG.

2. Enter a name for the BNG such as BNG-1, and click OK.

NMX adds the BNG to the map and tree.

3. Right-click the BNG icon and select Properties from the shortcut menu.

4. Enter the device ID, MAC Address, IP Address, Subnet Mask, and Default Gateway as appropriate for your network for both Physical Address 1 and Physical Address 2.

Physical Address 1 sets properties for the BNG ETH1 port, which you typically connect to the NMX network.

166 Managing DM Network CherryPickers

Physical Address 2 sets properties for the BNG ETH 2 port, which you typically connect to a CAS network.

The IP addresses you use for the ETH1 and ETH2 ports must be on different subnets.

5. Set other properties as appropriate.

Tip: Click the Help button in the dialog box for more information about the fields in the Properties dialog box.

6. When you finish, click OK.

NMX adds the BNG icon to the tree and map.

Adding a CAS Card to the BNG

When you add the BNG to the network group, NMX discovers the BNG and automatically adds cards to the backpanel graphic. If you are doing this example without actual equipment, you must add a “virtual” CAS card to the BNG. The virtual card provides two Ethernet ports—an SCS port and an EMM port. Although these ports do not actually exist on the BNG back panel (instead, the ETH2 port is typically used to connect to a hub on the CAS network), they provide a logical way to configure information about the CAS components in the network.

Set the Physical Address 1 andPhysical Address 2 properties.

167Managing DM Network CherryPickers

If you do not need to add the CAS Card, skip to step 3.

To add and configure a virtual CAS card:

1. In the map, double-click the BNG icon to open the back-panel graphic.

2. Right-click on the blank space in Slot 255 (Virtual), and select Create Card > CAS.

The CAS card appears in the BNG back panel.

3. Right-click in a blank area of the CAS card and select Properties from the shortcut menu.

The Properties dialog box opens.

4. Set the EIS1 and EIS2 IP addresses and subnet masks as appropriate for your network.

EIS1 is the primary event information server, and EIS2 is the backup.

5. Right-click the SCS port and select Properties from the shortcut menu.

The SCS Port Properties dialog box opens.

6. Set the EIS Port and Crypto Period Duration properties as appropriate.

The Use Backup Channel field is not applicable in this example because there is no BNG redundancy.

7. Click OK to close the dialog box, and then close the BNG back panel graphic.

You do not need to set any properties for the EMM port.

168 Managing DM Network CherryPickers

Adding CAS Devices You provide additional CAS information by adding ECM and EMM Generators to the network group. Although you may use multiple generators, add one ECM Source icon and one EMM Source icon to the network group. You can configure one or more ECM and EMM generators per device.

To add an ECM Source icon:

1. Right-click in a blank area of the map and select Create Logical Devices > ECM Source.

2. Position the cursor on a blank spot in the map and click the left mouse button.

The Create Object dialog box opens.

3. Select the ECM Configuration row.

When you click in this field, a button appears on the right side of the row.

4. Click the ... button to open the ECMG Configuration dialog box.

5. Click the Create New Connection button to add a row to the table.

A button appearswhen you selectthis row.

169Managing DM Network CherryPickers

\

6. Enter the ECMG properties as appropriate for your network.

Tip: The NMX online help has complete ECMG field information. Click the Help button for more information.

7. When you finish, click OK to close the ECMG Configuration dialog box, then click OK to close the Create Object dialog box.

The ECM Source appears in the tree and map.

Next, add an EMM Source to configure the EMM Generator. The EMMG configuration is much like the ECMG configuration.

To create an EMM Source:

1. Right-click in a blank area of the map and select Create Logical Devices > EMM Source.

2. Position the cursor on a blank spot in the map and click the left mouse button.

The Create Object dialog box opens.

3. Select the EMM Configuration row.

When you click in this field, a button appears at the right side of the row.

4. Click the ... button to open the EMMG Configuration dialog box.

Click the Create New Connection button.

NMX adds a row to the table.

170 Managing DM Network CherryPickers

5. Click the Create New Connection button to add a row to the table.

6. Enter the EMMG properties as appropriate for your network.

7. Click OK when you finish.

Adding the PSI/SI Input Device

The BNG generates PSI/SI for the output transport. However, you need to add a PSI/SI input device even though there is no external PSI/SI. NMX requires a PSI/SI input device in the network tree and map to represent the flow of PSI/SI.

To add the PSI/SI input device:

1. Click in a blank spot in the map to put the current focus on the map.

2. In the toolbar at the bottom of the window, click the Create Input Device button.

3. Move the mouse pointer onto a blank area of the map where you want the new icon to appear, and click the left mouse button.

When you move the pointer onto the map, the pointer changes to a diamond shape like the device icons. When you click the left mouse button, the Create Object dialog box opens.

4. In the Name field, enter a name for the input device such as PSI Input-1.

5. In the Number of Ports field, leave the default, 1.

Click the Create New Connection button.

NMX adds a row to the table.

Create Input Device button

171Managing DM Network CherryPickers

6. In the Port 1 Type field, select File.

7. Click OK.

The new input device appears in the tree and on the map.

Adding an RF Output Device

Finally, add an RF output device to complete the network group.

1. In the toolbar at the bottom of the window, click the Create Output Device button.

2. Move the mouse pointer to a blank area of the map where you want the new icon to appear, and click the left mouse button.

When you move the pointer onto the map, the pointer changes to a diamond shape like the device icons. When you click the left mouse button, the Create Object dialog box opens.

3. In the Name field, enter a name for the output device such as RF Output-1.

4. In the Number of Ports field, leave the default, 1.

5. In the Port 1 Type field, select RF.

6. Click OK.

NMX adds the output device to the tree and map. The finished network group should look something like this. Adjust the placement of your icons if necessary.

Create Output Device button

172 Managing DM Network CherryPickers

Connect the DevicesAfter adding the devices in the network group, create the connections between them. These connections represent the physical cabling between devices, as well as the logical flow of CAS data and PSI/SI.

Begin connecting devices by connecting the input devices to the CherryPicker.

To connect the input devices to the CherryPicker:

1. Right-click in a blank spot in the map and select Network Group Links from the shortcut menu.

The Edit Connections dialog box opens.

2. In the left pane, expand the tree under the ASI and DHEI input devices, and in the right pane, expand the tree under the CherryPicker.

3. Select the ASI-001 port under ASI Input-1 and the ASI-001 port under CP-1.

4. Click Connect.

The ports turn to blue to indicate they are connected, and the connection appears in the table at the bottom of the window.

173Managing DM Network CherryPickers

5. Connect the DHEI-001 port under DHEI Input-1 to the DHEI-003 port under CP-1.

When you finish, the input connections look like this.

Next, connect the CherryPicker to the BNG. The CherryPicker outputs an ASI transport.

To connect the CherryPicker to the BNG:

1. In the left pane, expand the tree under the CherryPicker icon, and in the right pane, expand the tree under the BNG icon.

2. Connect the first output ASI port under the CherryPicker to the first input ASI port on the BNG.

174 Managing DM Network CherryPickers

Now connect the BNG to the RF output device.

To connect the BNG to the RF output device:

1. Expand the trees under the BNG on left pane and RF output on the right pane.

2. Connect the first RF output on the BNG to the RF input port on the RF output device.

175Managing DM Network CherryPickers

Now connect the ECM Source and EMM Source to the BNG.

To connect the ECM Source and EMM Source to the BNG:

1. In the left pane, expand the tree beneath the ECM and EMM Source icons.

2. In the right pane, expand the tree beneath the BNG, then under the CAS-255 icon.

3. Connect the SCS-001 port under the ECM Source to the SCS-001 port under the BNG.

4. Connect the EMM-001 port under the EMM Source to the EMM-002 port under the BNG.

Finally, connect the PSI input device to the BNG.

176 Managing DM Network CherryPickers

To connect the PSI input device to the BNG:

1. In the left pane, expand the tree beneath PSI Input-1.

2. In the right pane, expand the tree beneath the BNG Main Board card.

3. Connect the File Port under PSI Input-1 to the File Port under the BNG Main Board.

4. Click OK to close the Edit Connections dialog box.

The map now looks like this.

177Managing DM Network CherryPickers

Configuring ServicesNow that you’ve finished the hardware configuration, configure services. This network group requires one ASI input transport, one DHEI input transport, and one RF output transport. You don’t need to worry about the ASI output from the CherryPicker that is input to the BNG because NMX takes care of this stream transformation.

You also don’t need to create the input transports because the CherryPicker can read the contents of incoming streams from the PSI and create transports for you. This process is called extraction, and it can save you a good bit of time.

Extracting Inputs When you extract inputs, the CherryPicker reads the transport PAT and PMT tables to determine the transport contents. NMX then creates a transport that includes the following data:

■ Transport ID for the transports

■ Program number for programs

■ PID, bit rate, name, and type for elementary streams

You can extract the contents of a single input or all inputs at once. To save time, do it all at once. For the extraction to work, you must have an actual CherryPicker receiving ASI and DHEI inputs in your network.

Note: If you are working on this example without actual hardware, skip this section, start the service configuration as described in “Starting the Service Configuration” on page 178, and then create the input transports manually. See “Creating Transports Manually” on page 145 for instructions to create input transports, or see the online help.

178 Managing DM Network CherryPickers

To extract the CherryPicker inputs:

1. Right-click the CherryPicker icon and select Online from the shortcut menu.

NMX attempts to discover the CherryPicker. The icon turns green if NMX is successful.

2. In the network tree or map, right-click the CherryPicker icon, and select Extract Inputs from the shortcut menu.

The Extract Inputs dialog box opens and shows you the progress of the extraction. When finished, the dialog box displays the transports in a tree format.

3. Click the Save to File button.

The Save As dialog box opens.

4. Browse to the location where you want to save the file, enter a descriptive file name, such as CP-1-inputs, and click Save.

NMX saves the transport data to a file.

Starting the Service Configuration

Now switch to Service View to begin configuring the input and output services.

To begin the service configuration:

1. Click Output Service View to open the Service tree.

Note: Output Service View is the default view. If you changed the view, your tab may say Input Service View or Service View.

2. Right-click the DM CherryPicker NG network group icon and select New Service Configuration from the shortcut menu.

The Create New Service Configuration dialog box opens.

3. Right-click the New Service Configuration icon at the top of the input tree and select Properties from the shortcut menu.

The New Service Configuration General Properties dialog box opens.

179Managing DM Network CherryPickers

4. Enter a descriptive name for the service configuration such as DM CherryPicker.

5. Select the Scrambling/Edge radio button for both Internal PSI/SI Injection and External PSI/SI Injection.

In this network group, the BNG acts as the Scrambling/Edge multiplexer. The BNG generates internal PSI/SI, and the CAS components inject external CAS data.

6. Click OK to close the dialog box.

Creating Input Transports From a File

Now use the file you created by extracting the CherryPicker inputs to create the input transports.

To create a transport from a file:

1. Right-click the Transport icon in the input tree and select Add From File from the shortcut menu.

The Open dialog box opens.

2. Select the file you saved when you extracted the CherryPicker inputs, and click Open.

NMX adds the transports to the input tree. Note that the transport PSI does not provide all stream properties. You might want to change program names or other stream properties. See the online help if you need more information about setting properties.

180 Managing DM Network CherryPickers

Creating the Output Transport

After importing the extracted transports or creating them manually, create an RF output transport with three programs. Your extracted inputs will be different than the inputs in this example, but it does not matter.

To create an output transport:

1. In the right pane, right-click the service configuration icon and select Add Transport from the shortcut menu.

2. Enter a descriptive name for the transport, such as RF-Out-1.

3. In the Output Signal/Protocol field, select RF, then check the Scrambled box, and click OK.

Tip: Don’t forget to check the Scrambled box. If you do, you can change it in Stream Editor, but not in NMX.

NMX adds the transport to the tree.

4. Right-click the transport icon and select Properties from the shortcut menu.

The Transport Properties page opens.

5. Click the Delivery tab to open the Delivery page.

6. Click the Load DDF File button at the bottom of the page.

A .DDF file contains default properties for modulated outputs. Always select the .DDF file before setting other properties.

181Managing DM Network CherryPickers

7. In the Load DDF File dialog box, select the appropriate .DDF file:

■ If your BNG has a blue chassis, select BNG_RF.

■ If your BNG has a gray chassis, select BNG_RF_Rev2.

8. Set the transport properties as appropriate, including the Data Rate.

The default Data Rate, 6 Mbps, is probably not high enough. Increase this rate to something like 20 Mbps.

9. Click OK to close the Load DDF File dialog box, then click OK to close the Transport Properties dialog box.

Add Programs to the Transport

To add programs to the transports:

1. Right-click the transport icon and select Add Program.

2. Check three programs to add to the transport.

5. Click the Delivery tab.

6. Click Load DDF File.

7. Select the DDF fileand click OK.

182 Managing DM Network CherryPickers

3. Click OK.

NMX adds the programs to the transport.

Adding CAS Streams For CAS support, add an ECM and EMM to the output transport. You must add these streams to the Inserted Data node of the input tree before you can add them to the output transport.

To add CAS streams to the input pane:

1. In the left pane, right-click the Inserted Data node and select Add ECM Group from the shortcut menu.

The Select Input Type of New Insertion Data Group dialog box opens.

2. Click OK.

NMX adds an ECM Group icon to the tree.

3. Right-click the ECM Group icon and select Add ECM.

183Managing DM Network CherryPickers

4. Click OK.

NMX adds an ECM icon to the tree.

5. Right-click the ECM icon and select Properties from the shortcut menu.

Tip: The NMX online help has detailed information for the ECM and EMM fields. Click help for more information.

6. Set the ECM properties as appropriate, and click OK.

7. Repeat steps1 through 6 to add the Ethernet CAS Data node to the tree and an EMM.

When you finish, the input tree should look like this.

184 Managing DM Network CherryPickers

To add the ECM and EMM to the output transport:

1. Right-click the output transport icon and select Add ECM from the shortcut menu.

The Select Inputs dialog box opens with the ECM selected by default.

2. Click OK.

NMX adds the ECM to the transport.

3. Right-click the output transport icon and select Add EMM from the shortcut menu.

The Select Inputs dialog box opens with the EMM selected by default.

4. Click OK.

NMX adds the EMM to the transport.

Creating a Rate Shaping Pool

To support rate-shaping, create a rate shaping pool.

To create a rate shaping pool:

1. Click the Statistical Multiplexing tab at the bottom of the output pane.

2. Right-click the DM CherryPicker network group icon and select Add Rate Shaping Pool from the shortcut menu.

185Managing DM Network CherryPickers

The Add Pool dialog box opens.

3. In the Pool name field, enter a descriptive name for the pool.

4. In the Select Output Transport drop-down list, select the transport for which you want to create the pool.

5. If necessary, adjust the Suggested Pool Bit Rate.

NMX calculates the Available TS Bit Rate based on the transport you select and sets this rate as the default Suggested Pool Bit Rate. Harmonic recommends using this bit rate to avoid oversubscription. If you enter a bit rate that exceeds the available bandwidth, NMX warns you and asks if you want to continue.

1. Click the Statistical Multiplexing tab at thebottom of the output pane.

2. Select Add RateShaping Pool.

186 Managing DM Network CherryPickers

6. Select Multiple pools per transport if you want to create more than one rate shaping pool in this transport.

Note: Be sure your CherryPicker license supports multiple pools.

7. Click OK.

NMX adds the rate shaping pool to the tree.

After creating the rate shaping pool, add streams to the pool.

To add video streams to the pool:

1. Right-click the pool icon and select Add Stream from the shortcut menu.

The Select Inputs dialog box opens.

2. Check the three video streams and click OK.

3. Right-click the first video stream and select Properties from the shortcut menu.

The Properties dialog box opens.

4. In the Rate Change section, enter the minimum and maximum rates for the stream.

When you hover the mouse over the Min Bit Rate and Max Bit Rate fields, a tooltip shows the minimum and maximum rates entered in the Options dialog box. If you enter a rate outside these rates, the field background turns red. However, NMX does not send an error if the rate still falls into the range supported by the CherryPicker.

187Managing DM Network CherryPickers

5. Enter the priority of the stream.

Services assigned a higher priority (1-5) are recoded before services assigned a lower priority (6-10).

You do not need to change the Allocate Recoder field. NMX automatically selects SD Recoder or HD Recoder based on the type of video stream. Change this value to None only if you do not want to change the bit rate of this stream.

Note: To prevent recoder over-allocation, verify the recoder licenses that you have on the device before adding services to the pool. NMX does not prevent or check recoder over- allocation.

6. Select the other two video streams in the tree on the left pane of the dialog box and set properties for them.

7. Click OK to close the Multiplexing Properties dialog box.

You are now finished configuring services

➭ Click OK to close the Service Configuration dialog box and save the configuration.

It takes some time for NMX to save the service configuration.

188 Managing DM Network CherryPickers

Connecting ServicesWhen you’ve finished configuring services, connect them to the network group hardware. This tells NMX which streams flow through which ports.

Connecting the Input Services

To connect the input services to the network:

1. In the Service tree, right-click the service configuration icon and select Connect Service To Network from the shortcut menu.

The Connect Service to Network dialog box opens. Note that this dialog box has two tabs: Input Services and Output Services. Each page contains two trees: a service tree and a device tree.

2. If necessary, expand the two trees in the Input Service page so that you can see the entire contents of the trees.

3. In the Input Devices pane, select ASI Input TS under the Transport icon.

4. In the Output Devices pane, select the ASI-001 port under the ASI Input-1 icon.

5. Click Add.

The connection appears under the ASI-001 port.

189Managing DM Network CherryPickers

6. Repeat this procedure to make the following connections:

■ DHEI Input TS to DHEI-001

■ PSI Internal to File Port-001

■ ECM Group to SCS-001

■ Ethernet CAS Data Group to EMM-001

When you finish, the dialog box should look like this:

3. Select ASI Input TS.

4. Select ASI-001.The connection appears under the port.

190 Managing DM Network CherryPickers

To connect the output services:

1. Click the Output Service tab to open the Output Service page.

2. Expand the tree in both panes so you can see the contents.

3. Connect the RF-Out-1 icon to the RF-001 port.

4. Click OK to save the network connections.

Provisioning ServicesAfter you have connected services to the network, activate the service configuration. Activating the configuration provisions the streams on the hardware so that your configuration takes effect.

The devices in your network group must be online for provisioning to occur. If your devices are still offline, put them online now.

Putting the Devices Online

To put devices online:

➭ Right-click the device icon in the network tree or map, and select Online from the shortcut menu.

191Managing DM Network CherryPickers

Activating the Service Configuration

To activate the service configuration:

➭ In the NMX Service View tree, right-click the service configuration icon and select Activate Service Configuration from the shortcut menu.

Note: If you have more than one service configuration within a network group, only one service configuration can be active at a time.

When you finish creating the CherryPicker network, remember to back up your configuration by backing up the NMX database. See “Protecting Against Data Loss” on page 105 for instructions.

192 Managing DM Network CherryPickers

Customer Support

Contacting Harmonic for Technical SupportThe Harmonic Customer Support group is available to help you with any questions or problems you might have regarding Harmonic products. You can reach them at:

E-mail: [email protected]: (408) 490-64771–888–MPEGTWO (673-4896)Fax: (408) 490-6770

Harmonic Inc.549 Baltic WaySunnyvale, California 94089Attn: Customer Support

194 Contacting Harmonic for Technical Support


Top Related