Broadcast Network Processor

BNP2xr User Guide, Release 3

RGB Networks, Inc.

390 West Java Drive
Sunnyvale, CA 94089
Support Tel: 877-RGB-NETW
Fax: (408) 701-2710
www.rgbnetworks.com
BNP2xr User Guide
Document part number: 250-0035-02-Rev H, BNP2xr User Guide.
Printed 10-18-2010

Copyright 2005-2010 RGB Networks, Inc. All rights reserved worldwide.

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

Notice
RGB Networks provides this document without warranty of any kind, either implied or expressed, including, but not
limited to, the implied warranties of merchantability and fitness for a particular purpose. RGB Networks has made every
attempt to ensure the accuracy and completeness of information in this document at the time of publication. As we
continuously improve and add features to our products, RGB Networks reserves the right to revise this document without
prior notification of such revision or change. Variations in network design or environment are outside the control of RGB
Networks. You may verify product specifications and obtain assistance selecting the appropriate solution for your
situation by contacting RGB Networks.

Trademarks
RGB Networks, VIA, and RDS are trademarks of RGB Networks, Inc. All other company, brand, and product names are
trademarks or registered trademarks of their respective holders. The products described are covered by one or more U.S.
and foreign patents pending.

Patents
US Patents. 6,996,129; 7,046,677. Other US and foreign patents pending.

BNP2xr User Guide document history

Part Number Software Version Release Date Document Changes

250-0035-02 rev B 2.0.3 04/20/2009 Production Release
250-0035-02 rev C 2.1 06/16/2009 • Added Digital Messaging System functionality.
• Modified Output TS configuration.
• Added Reserved PID functionality.
250-0035-02 rev D 2.2 11/06/2009 • Modified Messaging System functionality to include
Advanced Messaging and Logo Overlay.
• Modified Output TS configuration.
• Added Program Descriptor rules.
250-0035-02 rev E 3.0 02/18/2010 • Added Operator, Advanced Messaging, and Logo Overlay
scheduling feature.
• PSIP enhanced grooming configuration.
250-0035-02 rev F 3.0.1 05/07/2010 • Added transparency support for Non-Ascii text.
250-0035-02 rev G 2.9 07/23/2010 Cablevision Support
250-0035-02 rev H 3.1.1 10/18/2010 • Added EBIF support.
• Added AAA User Authentication.
• Enhanced NTP synchronization feature.
• Output TS modification enhancements.
• Added ES-level grooming.
 Table of Contents

Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Document Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Document Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Document Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Graphics Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Chapter 2: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
In This Chapter:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Product Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
BNP2xr Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Grooming, Transrating and Multiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
DPI-Based Ad Splicing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Messaging System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
BNP Deployment Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Program Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Gigabit Ethernet Port Output Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1:1 Chassis-level Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 3: Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
In This Chapter:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Required Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Electrostatic Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Broadcast Network Processor Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
LED Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Port Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
BNP2xr Component Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Rack Mounting the BNP2xr. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Grounding the BNP2xr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
To connect the chassis ground: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Installing SFP Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Connecting AC Power to the BNP2xr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Disconnecting AC Power from the BNP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Connecting DC Power to the BNP2xr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Before Connecting Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Connecting Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Disconnecting DC Power from the BNP2xr . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Connecting External Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Installing the Compact Flash Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

BNP2xr User Guide iii

Table of Contents

Chapter 4: System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

In This Chapter:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Obtaining Java Runtime Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Obtaining JRE from the RGB Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . . 28
Launching the BNP Element Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Using the Element Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Logging In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
BNP Element Manager Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Element Manager Title Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Element Manager Main Menu and Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Status Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Chassis View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Setting the Time Offset Table (TOT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Global Chassis Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
NTP Server Force Sync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Force Sync on Redundant BNP Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Configuring Chassis-level 1:1 Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Forcing Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
1:1 Redundancy Best Practices and Considerations. . . . . . . . . . . . . . . . . . . . . 46
Ethernet Control Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Determining the BNP IP Address for DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
GigE Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Gigabit Ethernet Port Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Removing Port Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Configuring ASI Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Modifying a Port Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Global Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Local Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Messaging System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Messaging Zones. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Logo Overlay Zones. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Messaging System Zone Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Show Program List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Creating Messaging Zone Transport Streams and Output Programs . . . . . . . . 98
SNMP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Configuring an SNMP Trap Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Changing a Community String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Upgrading Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
To Upgrade Software in a Single Chassis Environment . . . . . . . . . . . . . . . . . 100
To Upgrade Software in a Redundant Chassis Environment . . . . . . . . . . . . . . 102
Clearing the Web Start Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
The License Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Purchasing Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Activating a License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Hardware Capacity Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Flash Portability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Regrooming. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

iv BNP2xr User Guide

 Table of Contents

Stopping All Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Rebooting the System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Checking for the BNP Element Manager Version . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Chapter 5: Grooming and PSIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

In This Chapter:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Using the Mapping Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Viewing Program-Level Input Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Viewing ES-Level Input Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Interpreting the Program Status Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Interpreting Elementary Stream Status Icons . . . . . . . . . . . . . . . . . . . . . . . . . 117
Expanding and Collapsing Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Creating Input Transport Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Basic Input Transport Stream Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Multiple IP and UDP Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Managing Input Transport Streams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
GigE Port Transport Stream Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
ASI Port Transport Stream Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Creating MPEG-2 Output Transport Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
ASI Port MPEG-2 Transport Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
GigE Port MPEG-2 Transport Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Advanced Transport Stream Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
SPTS Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
MPTS Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Creating ATSC Output Transport Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Creating SCTE Output Transport Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Creating DVB Output Transport Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Setting Up Network Information Tables (NIT) for DVB. . . . . . . . . . . . . . . . . . . 137
Creating a FAT ASI Port Output Transport Stream . . . . . . . . . . . . . . . . . . . . . . . . . 139
Advanced FAT ASI Transport Stream Settings . . . . . . . . . . . . . . . . . . . . . . . . 142
Creating Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Creating Output Programs Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Program Messaging System Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Modifying and Deleting Streams or Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Modifying Streams or Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Deleting Streams and Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Drag and Drop Grooming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Drag and Drop Grooming Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Viewing Grooming Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Scheduling Grooming - One time event. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Program Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Modes of Program Redundancy Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
To Configure Program Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Manual Recovery Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Elementary Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Creating an Elementary Stream. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Reordering an Elementary Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Elementary Stream Remapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Reserved PIDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

BNP2xr User Guide v

Table of Contents

Dummy PIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Adding an Unreferenced PID as an Elementary Stream . . . . . . . . . . . . . . . . . 183
Elementary Stream Ghost PID Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Unreferenced PID Pass Through. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Unreferenced PID Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Referenced PID Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Managing PMT and ES Descriptors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
To Add a Program Descriptor Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
To Edit a Program Descriptor Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
To Delete a Program Descriptor Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Monitoring Bitrates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Chapter 6: Digital Program Insertion (DPI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

In This Chapter:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Digital Program Insertion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Connecting an Ad Server to the BNP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
SCTE 30 to SCTE 35 Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Chapter 7: ETV Binary Interchange Format (EBIF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

In This Chapter:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Prerequisite Reading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Use Case Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Pre-Bound Ad Splice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Pre-Bound EBIF Passthrough (no DPI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Pre-Bound EBIF Drop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Pre-Bound EBIF Passthrough and Keep During Ad Splice . . . . . . . . . . . . . . . 220
Pre-Bound Network EBIF; Late-Bind EBIF During Ad . . . . . . . . . . . . . . . . . . . 223

Chapter 8: Monitoring the BNP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

In This Chapter:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Selecting the Elements to View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Viewing Alarms and Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Alarms and Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
The Status Bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Chapter 9: Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

In This Chapter:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
LED Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Event Log Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Software Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Contacting RGB Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Searching the RGB Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

Chapter 10: Field-replaceable Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

In This Chapter:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Replacing a Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Removing a Power Supply. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Inserting a Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

vi BNP2xr User Guide

 Table of Contents

Replacing a Gigabit Ethernet Processor (GBP2) Module . . . . . . . . . . . . . . . . . . . . 240

Removing a GBP2 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Replacing a GBP2 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Replacing a Processor Module (PROC2) or an ASI (or ASI2) Module . . . . . . . . . . 242
Removing a PROC2 or ASI (or ASI2) Module . . . . . . . . . . . . . . . . . . . . . . . . . 243
Replacing a PROC2 or ASI (or ASI2) Module . . . . . . . . . . . . . . . . . . . . . . . . . 243

Chapter 11: Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

In This Chapter:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Input Interfaces/Output Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
MPEG Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Video Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Audio Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Elementary Stream Types & Conversions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Digital Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Regulatory Compliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Electrical/Mechanical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Environmental . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

APPENDIX A: Editing the DVB NIT Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

In This Appendix: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
NIT Values Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Naming, Viewing, Deleting and Editing NIT Configuration Files . . . . . . . . . . . . . . . 252
Naming a Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Viewing a Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Deleting a Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Editing a Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Suggestions for Editing the NIT Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
United States. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Canada . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
European Declaration of Conformity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

Glossary> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267

Index> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275

BNP2xr User Guide vii

Table of Contents

viii BNP2xr User Guide

 List of Tables

CHAPTER 1: Introduction
Table 1: Document Conventions ................................................................................................. 2

CHAPTER 2: Overview

CHAPTER 3: Installation
Table 2: LED indicators ............................................................................................................. 15
Table 3: Environmental Requirements ...................................................................................... 19
Table 4: Supported SFPs .......................................................................................................... 22

CHAPTER 4: System Configuration

Table 5: User levels................................................................................................................... 31
Table 6: Element Manager Menus ............................................................................................ 32
Table 7: Element Manager Primary Tabs.................................................................................. 32
Table 8: Chassis information window ........................................................................................ 34
Table 9: Tot Time Offset Window Parameters .......................................................................... 36
Table 10: Global Chassis Configuration Fields ......................................................................... 38
Table 11: Ethernet Control Port Configuration Fields............................................................... 47
Table 12: GigE Port Configuration Fields .................................................................................. 49
Table 13: User Authentication - Global Fields ........................................................................... 56
Table 14: Local User Accounts.................................................................................................. 58
Table 15: User Authentication - Servers - Add/Edit Server Fields............................................. 61
Table 16: User Authentication - Servers - Edit AAA Server Order Fields.................................. 63
Table 17: AAA Server List Example .......................................................................................... 64
Table 18: Messaging Zones subtab .......................................................................................... 66
Table 19: Add / Modify EAS Messaging Zone menu................................................................. 68
Table 20: Crawl Positioning....................................................................................................... 70
Table 21: Operator Messaging tab ............................................................................................ 73
Table 22: Advanced Messaging tab .......................................................................................... 79
Table 23: Logo Overlay Zones subtab ...................................................................................... 87
Table 24: Logo Overlay tab ....................................................................................................... 89
Table 25: Upgrade Software Configuration Fields................................................................... 101

CHAPTER 5: Grooming and PSIP

Table 26: Program Status Icons .............................................................................................. 116
Table 27: Elementary Stream Icons ........................................................................................ 117
Table 28: Input Transport Stream Creation ............................................................................. 119
Table 29: Selecting Multiple IP and UDP ................................................................................ 120
Table 30: Input Transport Stream pop-up menu options......................................................... 122
Table 31: MPEG-2 Output Transport Stream Creation (ASI Port)........................................... 124
Table 32: MPEG-2 Output Transport Stream Creation (MPEG-2, GigE Port)......................... 125
Table 33: Advanced Transport Stream Settings...................................................................... 129
Table 34: ATSC TS Creation: PSIP Table Information Configuration Parameters.................. 131
Table 35: DVB Output Transport Stream Configuration Parameters ...................................... 137
Table 36: Creating a FAT ASI Transport Stream .................................................................... 141

BNP2xr User Guide ix

List of Tables

Table 37: Create Output Program Configuration Parameters ................................................. 146

Table 38: Messaging System Setting window ......................................................................... 148
Table 39: Drag and drop grooming.......................................................................................... 156
Table 40: Configure Program Mapping ................................................................................... 159
Table 41: Service Level Configuration Details......................................................................... 162
Table 42: Configure Elementary Stream Mapping .................................................................. 164
Table 43: Program Redundancy Modes of Operation ............................................................. 169
Table 44: Manage Elementary Streams menu ........................................................................ 177
Table 45: Manage Descriptor Rules fields............................................................................... 198

CHAPTER 6: Digital Program Insertion (DPI)

CHAPTER 7: ETV Binary Interchange Format (EBIF)

CHAPTER 8: Monitoring the BNP

CHAPTER 9: Troubleshooting
Table 1: LED Indications ......................................................................................................... 233
Table 2: Contacting Customer Support ................................................................................... 234

CHAPTER 10: Field-replaceable Units

CHAPTER 11: Specifications

Table 3: Input/Output Interfaces .............................................................................................. 245
Table 4: MPEG Processing ..................................................................................................... 245
Table 5: Video Formats ........................................................................................................... 246
Table 6: Audio Formats ........................................................................................................... 246
Table 7: Elementary Stream Types & Conversions................................................................. 247
Table 8: Digital Broadcast ....................................................................................................... 247
Table 9: Regulatory Compliance ............................................................................................. 248
Table 10: Electrical and Mechanical ........................................................................................ 248
Table 11: Environmental Ranges ............................................................................................ 248
Table 12: Values Supported .................................................................................................... 249

x BNP2xr User Guide

 List of Figures

CHAPTER 1: Introduction
Figure 1, RGB’s Broadcast Network Processor—Model BNP2xr.................................................... 1

CHAPTER 2: Overview
Figure 2, Regional Ad Zone Insertion Illustration ............................................................................ 5
Figure 3, BNP in SCTE-18 Digital EAS application ......................................................................... 6
Figure 4, Example of BNP Grooming of GigE or ASI Input Over GigE Transport Network............. 7
Figure 5, Example of SDV Architecture over GigE Transport Network ........................................... 7
Figure 6, Example of Co-Located ASI Architecture......................................................................... 8
Figure 7, 1:1 Chassis Redundancy using Heartbeat and Virtual IP Failover Mechanism ............. 11

CHAPTER 3: Installation
Figure 8, Front panel (with bezel).................................................................................................. 14
Figure 9, Front panel (without bezel)............................................................................................. 15
Figure 10, LEDs............................................................................................................................. 15
Figure 11, Port mapping and LED indicators................................................................................. 16
Figure 12, Rear panel.................................................................................................................... 16
Figure 13, DC Power Supply ......................................................................................................... 17
Figure 14, BNP2xr chassis, components visible ........................................................................... 18
Figure 15, Front brackets attached................................................................................................ 19
Figure 16, Rack shelf..................................................................................................................... 20
Figure 17, Mounted BNP2xr .......................................................................................................... 20
Figure 18, Grounding terminal, rear of chassis: AC power supply top, DC power supply bottom. 21
Figure 19, Connect AC power ....................................................................................................... 23
Figure 20, Connect DC power ....................................................................................................... 24
Figure 21, Connect the power cables............................................................................................ 25

CHAPTER 4: System Configuration

Figure 22, Enter the IP address of the BNP to access .................................................................. 28
Figure 23, Launch BNP Element Manager window....................................................................... 29
Figure 24, BNP Element Manager login window (Local login, left; AAA server login, right).......... 30
Figure 25, BNP2xr title bar ............................................................................................................ 31
Figure 26, Typical BNP Element Manager status bar ................................................................... 32
Figure 27, Chassis tab................................................................................................................... 33
Figure 28, Choosing ToT Time Offset ........................................................................................... 35
Figure 29, ToT Time Offset Window.............................................................................................. 35
Figure 30, Global chassis configuration ........................................................................................ 37
Figure 31, Apply Force Sync ......................................................................................................... 41
Figure 32, Reboot Password Verification window ......................................................................... 41
Figure 33, Reboot confirmation ..................................................................................................... 41
Figure 34, Force sync for standby NTP server.............................................................................. 42
Figure 35, Ethernet Control Port configuration .............................................................................. 47
Figure 36, GigE Port configuration screen .................................................................................... 48
Figure 37, Mirroring GigE ports ..................................................................................................... 50
Figure 38, ASI Port configuration tab ............................................................................................ 51
Figure 39, Modify Port Name Menu............................................................................................... 52
Figure 40, Modifying the Port Name.............................................................................................. 52

BNP2xr User Guide xi

List of Figures

Figure 41, Port Name Modified...................................................................................................... 52

Figure 42, BNP User Authentication Workflow .............................................................................. 54
Figure 43, User Authentication - Global, AAA disabled ................................................................. 55
Figure 44, User Authentication - Global, AAA enabled ................................................................. 56
Figure 45, User Authentication - Local .......................................................................................... 57
Figure 46, User Authentication - Servers ...................................................................................... 59
Figure 47, Add AAA Server ........................................................................................................... 60
Figure 48, Edit AAA Server ........................................................................................................... 61
Figure 49, Edit AAA Server Order ................................................................................................. 62
Figure 50, Edit AAA Server Order - modified ................................................................................ 62
Figure 51, New server order .......................................................................................................... 63
Figure 52, Server deletion confirmation......................................................................................... 64
Figure 53, Configuration -> Messaging System tab ...................................................................... 66
Figure 54, Messaging Zone pop-up window.................................................................................. 67
Figure 55, Add EAS Messaging window ....................................................................................... 68
Figure 56, Modify EAS Zone ......................................................................................................... 71
Figure 57, Delete Output TS-associated messaging zones .......................................................... 72
Figure 58, Messaging Zone pop-up window.................................................................................. 72
Figure 59, Operator Messaging Zone tab...................................................................................... 73
Figure 60, Advanced Messaging Schedule Window ..................................................................... 76
Figure 61, Modify Operator Messaging Zone ................................................................................ 77
Figure 62, Messaging Zones pop-up window ................................................................................ 78
Figure 63, Advanced Messaging Zone tab .................................................................................... 78
Figure 64, Modify Advanced Zone window.................................................................................... 83
Figure 65, Delete Output TS-associated messaging zones .......................................................... 84
Figure 66, Alpha Channel transparency examples........................................................................ 85
Figure 67, Configuration -> Logo Overlay Zones tab .................................................................... 86
Figure 68, Logo Overlay Positioning ............................................................................................. 88
Figure 69, Logo Overlay Zone pop-up window.............................................................................. 88
Figure 70, Add Logo Overlay Zone tab ......................................................................................... 89
Figure 71, Modify Logo Overlay Zone window .............................................................................. 93
Figure 72, Delete Output TS-associated messaging zones .......................................................... 94
Figure 73, Show Program List Pop-up windows............................................................................ 95
Figure 74, Show Program List window .......................................................................................... 96
Figure 75, Show Program List window - drill down........................................................................ 97
Figure 76, Show Program List pop-up menu ................................................................................. 97
Figure 77, Messaging Zone Icons ................................................................................................. 98
Figure 78, Scroll-over program status ........................................................................................... 98
Figure 79, SNMP configuration window ........................................................................................ 99
Figure 80, Modifying an SNMP Community String ........................................................................ 99
Figure 81, Upgrade Software dialog ............................................................................................ 100
Figure 82, Software Upgrade - Redundant chassis..................................................................... 102
Figure 83, Java control panel ...................................................................................................... 103
Figure 84, The License Manager................................................................................................. 106
Figure 85, Apply regrooming ....................................................................................................... 107
Figure 86, System Shutdown confirmation dialog ....................................................................... 108
Figure 87, Password Verification Prompt .................................................................................... 108
Figure 88, Password Verification Prompt .................................................................................... 109
Figure 89, Reboot dialog ............................................................................................................. 109
Figure 90, About BNP dialog ....................................................................................................... 110

CHAPTER 5: Grooming and PSIP

Figure 91, Grooming-Mapping configuration ............................................................................... 113
Figure 92, Viewing program-level input source ........................................................................... 114
Figure 93, Viewing ES-level input source .................................................................................... 115

xii BNP2xr User Guide

 List of Figures

Figure 94, Existing Mapping........................................................................................................ 118

Figure 95, Collapse Mapping ...................................................................................................... 118
Figure 96, Create GigE Input TS................................................................................................. 119
Figure 97, Selecting multiple UDP/IP ports ................................................................................. 120
Figure 98, Input Transport Streams created ............................................................................... 121
Figure 99, Input Transport Stream pop-up menu - GigE............................................................. 122
Figure 100, Input Transport Stream pop-up menu - ASI ............................................................. 122
Figure 101, Creating output TS (MPEG-2, ASI port)................................................................... 124
Figure 102, Creating output TS (MPEG-2) - GigE port) .............................................................. 125
Figure 103, Create Output TS - ARP field................................................................................... 127
Figure 104, Advanced Transport Stream - SPTS........................................................................ 128
Figure 105, Advance Transport Stream Setting - MPTS............................................................. 129
Figure 106, Create Output TS (ATSC) - ASI Port ....................................................................... 130
Figure 107, Creating output TS (ATSC) - GigE Port ................................................................... 131
Figure 108, Creating output TS (SCTE) - ASI port...................................................................... 133
Figure 109, Creating output TS (SCTE) - GigE port.................................................................... 134
Figure 110, Creating output TS (DVB) - ASI port ........................................................................ 135
Figure 111, Creating output TS (DVB) - GigE port...................................................................... 136
Figure 112, Setup Network Information Table screen................................................................. 138
Figure 113, Using the Editing Feature......................................................................................... 139
Figure 114, Choosing a FAT ASI Transport Stream ................................................................... 140
Figure 115, Create Output Transport Stream (FAT ASI)............................................................. 140
Figure 116, FAT ASI Ports Created ............................................................................................ 142
Figure 117, FAT ASI - Advance Transport Stream Setting ......................................................... 143
Figure 118, Create Output Program popup................................................................................. 144
Figure 119, Create Output Program dialog ................................................................................. 145
Figure 120, Program Messaging System Setting window ........................................................... 148
Figure 121, Modify Input TS - GigE port...................................................................................... 149
Figure 122, Modify Input TS - ASI port........................................................................................ 149
Figure 123, Modify Output TS - GigE port................................................................................... 151
Figure 124, Modify Output TS - ASI port. .................................................................................... 152
Figure 125, Program Pop-Up menu - Modify Program................................................................ 153
Figure 126, Modify Input program - GigE or ASI port.................................................................. 153
Figure 127, Program Name Changed ......................................................................................... 153
Figure 128, Program Pop-Up menu - Modify Program................................................................ 154
Figure 129, Modify Output program - GigE or ASI port ............................................................... 155
Figure 130, Drag input program to output TS.............................................................................. 157
Figure 131, Configure Program Mapping window ....................................................................... 157
Figure 132, Configure Program Mapping window - program to program .................................... 158
Figure 133, ES to Program Drag and Drop ................................................................................. 163
Figure 134, Configure Elementary Stream Mapping window ...................................................... 163
Figure 135, ES Grooming - Reserved PID .................................................................................. 164
Figure 136, Configure ES Mapping - Reserved PID ................................................................... 164
Figure 137, ES Grooming Replacement window ........................................................................ 166
Figure 138, Grooming detail display - TS.................................................................................... 167
Figure 139, Grooming schedule .................................................................................................. 168
Figure 140, Program Redundancy .............................................................................................. 169
Figure 141, Configure Program Mapping - Program Redundancy .............................................. 170
Figure 142, Program Redundancy - Manual Recovery ............................................................... 171
Figure 143, Manage Elementary Streams................................................................................... 172
Figure 144, Manage Elementary Streams - New ........................................................................ 173
Figure 145, Manage Elementary Streams - ES Type choices .................................................... 173
Figure 146, Manage Elementary Streams - Stream Type, drop down ........................................ 174
Figure 147, Manage Elementary Streams - Audio Selection ...................................................... 174
Figure 148, Manage Elementary Streams - Data Selection ........................................................ 174

BNP2xr User Guide xiii

List of Figures

Figure 149, Manage Elementary Streams - PID.......................................................................... 175

Figure 150, Manage Elementary Streams - Dummy ................................................................... 176
Figure 151, Manage Elementary Streams - Preconfigured for PMT ........................................... 176
Figure 152, Reordering an Elementary Stream ........................................................................... 178
Figure 153, ES Reordered........................................................................................................... 179
Figure 154, Dummy PID: Real data stream groomed ................................................................. 180
Figure 155, Manage ES - New ES for Dummy PID ..................................................................... 181
Figure 156, Manage Elementary Streams - Dummy PID fields completed ................................. 182
Figure 157, Dummy Data PID in Grooming -> Mapping window................................................. 182
Figure 158, Choosing a Ghost Program ...................................................................................... 184
Figure 159, Create Ghost Program ............................................................................................. 184
Figure 160, New Program Stream ............................................................................................... 184
Figure 161, Adding an Elementary Stream ................................................................................. 185
Figure 162, Adding an Elementary Stream ................................................................................. 185
Figure 163, New Unreferenced PID ............................................................................................ 185
Figure 164, Ghost Program With Unreferenced PID. ................................................................. 187
Figure 165, Ghost Program Dragged and Dropped to Output TS ............................................... 188
Figure 166, Ghost Program Passed Through............................................................................. 188
Figure 167, Starting Unreferenced PID Mapping ........................................................................ 189
Figure 168, Create Output Transport Stream .............................................................................. 190
Figure 169, Configure Program Mapping Window ...................................................................... 191
Figure 170, Select Elementary Stream Window .......................................................................... 191
Figure 171, Starting Window for Referenced PID Mapping......................................................... 192
Figure 172, Mapping the Transport Stream................................................................................. 193
Figure 173, Manage Elementary Streams ................................................................................... 194
Figure 174, New ES filled In ........................................................................................................ 194
Figure 175, Dummy data PID in Program grayed out ................................................................. 195
Figure 176, Manage ES - Dummy and Reserved status ............................................................. 195
Figure 177, Manage Descriptor Rules pop-up............................................................................. 196
Figure 178, Manage Desriptor Rules window.............................................................................. 196
Figure 179, Add Descriptor Rule window .................................................................................... 197
Figure 180, Add Descriptor Rule - New status ............................................................................ 197
Figure 181, Manage Descriptor Rules - Rules Added ................................................................. 198
Figure 182, Add Descriptor Rule - DEC to HEX toggle ............................................................... 199
Figure 183, Edit Descriptor Rule - Changed status ..................................................................... 200
Figure 184, Manage Descriptor Rules - Rules Deleted ............................................................... 201
Figure 185, Input Monitoring bitrates ........................................................................................... 203
Figure 186, Input bitrate exceeds output ..................................................................................... 204
Figure 187, Input-Output Bit Rate Monitor tab............................................................................. 205

CHAPTER 6: Digital Program Insertion (DPI)

Figure 188, Regional Ad Zone Insertion Illustration .................................................................... 208
Figure 189, Ad server - BNP connection ..................................................................................... 209
Figure 190, SCTE 30 to SCTE 35 Conversion ............................................................................ 209
Figure 191, Configure Program Mapping window - Forward SCTE35 Cue................................. 210

CHAPTER 7: ETV Binary Interchange Format (EBIF)

Figure 1, ETV EBIF Data Source flow ......................................................................................... 212
Figure 2, Pre-bound Ad Splice flow ............................................................................................. 213
Figure 3, Input program (without ETV data) groomed to oTS ..................................................... 214
Figure 4, Configure Program Mapping window - EBIF/EISS Placeholder ................................... 214
Figure 5, Program with placeholders groomed - ESs grayed out................................................ 215
Figure 6, Manage Descriptor Rules - EISS & EBIF additions...................................................... 216
Figure 7, Broadcast EBIF enabled .............................................................................................. 217
Figure 8, Input program (with ETV data) groomed to oTS .......................................................... 217

xiv BNP2xr User Guide

 List of Figures

Figure 9, Configure Program Mapping - EBIF/EISS defaults ...................................................... 218

Figure 10, Program with ETV ESs passed through..................................................................... 218
Figure 11, Broadcast EBIF disabled............................................................................................ 219
Figure 12, Configure Program Mapping - EBIF/EISS unchecked ............................................... 220
Figure 13, Program with ETV ESs dropped ................................................................................ 220
Figure 14, Broadcast EBIF groomed as Splice/Keep.................................................................. 221
Figure 15, Configure Program Mapping - Play through ad.......................................................... 222
Figure 16, Program with ETV ESs passed through (Splice/Keep) .............................................. 222
Figure 17, Pre-bound Network EBIF, late-bind EBIF during ad .................................................. 223
Figure 18, Input program (with ETV data) groomed to oTS; Late-bound .................................... 224
Figure 19, Configure Program Mapping - Play during ad only .................................................... 225
Figure 20, Late-Bind Source Dialog window ............................................................................... 226
Figure 21, Late-Bind Source selected ......................................................................................... 227
Figure 22, Configure Program Mapping window - Late-bound selected ..................................... 227
Figure 23, Program with late-bound ETV ESs ) .......................................................................... 228
Figure 24, View Late-Bind Source in output program ................................................................. 228

CHAPTER 8: Monitoring the BNP

Figure 25, Alarms & Events tab................................................................................................... 230
Figure 26, The status bar ............................................................................................................ 231

CHAPTER 9: Troubleshooting
Figure 27, LED Indicator Locations ............................................................................................. 233
Figure 28, RGB Customer Portal home page ............................................................................. 235
Figure 29, Customer Portal home page - Direct and Reseller .................................................... 235
Figure 30, Knowledge Base search - Direct and Reseller........................................................... 235

CHAPTER 10: Field-replaceable Units

Figure 31, Top view of chassis, with FRUs visible ...................................................................... 237
Figure 32, Power supply handle (AC power supply) ................................................................... 239
Figure 33, Power supply handle (DC power supply) ................................................................... 239
Figure 34, Power supply removal (AC power supply shown at left, DC power supply shown at right)
239
Figure 35, Power supply insertion (AC power supply shown at left, DC power supply shown at right)
240
Figure 36, Front bezel removal ................................................................................................... 241
Figure 37, Loosen the GBP2 module release screws ................................................................. 241
Figure 38, GBP2 module removal ............................................................................................... 242
Figure 39, Loosen the insertion/removal screws......................................................................... 243
Figure 40, Remove the module ................................................................................................... 243
Figure 41, Install the ASI or PROC2 module (ASI shown) .......................................................... 244

CHAPTER 11: Specifications

APPENDIX A: Editing the DVB NIT Table

Figure 42, Window With No Arrays ............................................................................................. 252
Figure 43, Default Array .............................................................................................................. 253
Figure 44, Array2 Added ............................................................................................................. 253
Figure 45, NIT Configuration File Viewed in XML Format ........................................................... 254
Figure 46, Assigning a Name to a Configuration File.................................................................. 254
Figure 47, Delete Confirmation ................................................................................................... 255
Figure 48, Setup Network Information Table screen................................................................... 256
Figure 49, Editing Window .......................................................................................................... 256

BNP2xr User Guide xv

List of Figures

Figure 50, Icon Menu................................................................................................................... 257

Figure 51, Namespace Qualifier Window .................................................................................... 258
Figure 52, Search Window .......................................................................................................... 258
Figure 53, Large Vertical Bar Clicked Fully Compress ................................................................ 259
Figure 54, First Level of Expansion ............................................................................................. 259
Figure 55, Second Level of Expansion ........................................................................................ 260
Figure 56, Third Level of Expansion ............................................................................................ 260
Figure 57, Inserting a Node Before ............................................................................................. 261
Figure 58, Node Inserted Before ................................................................................................. 261
Figure 59, Error Message from Wrong Type of Data Character.................................................. 262
Figure 60, Data Type Mismatch Corrected.................................................................................. 262
Figure 61, Linkage Deleted ......................................................................................................... 263

xvi BNP2xr User Guide

CHAPTER 1

Introduction

RGB's Broadcast Network Processor (BNP) delivers the industry's highest density digital video
solution for grooming, statistical multiplexing, transrating and digital program insertion (DPI). Based
on RGB's flexible, scalable and modular platform, the BNP simplifies and expedites deployments of
advanced video services, simplifies operation and management, and reduces operational and capital
costs.

Receiving input through its Gigabit Ethernet or ASI interfaces, the BNP2xr can statistically multiplex
while performing grooming and digital ad and overlay insertion.

The BNP2xr can receive both standard definition (SD) and high definition (HD) program services, and
can concurrently groom and insert digital ads within the same box.

The BNP is fully MPEG compliant and interoperable with leading cable industry equipment.

The BNP makes configuration more intuitive and simple by providing an easy-to-use Java-based
graphical user interface that can be accessed through a standard Web browser. Configuration can be
performed through SNMP using any standard network management application. The SNMP MIBs are
readily available from the BNP start page.

Figure 1. RGB’s Broadcast Network Processor—Model BNP2xr

This guide describes the installation, configuration, and FRU replacement for the BNP2xr.

Document Organization
This guide is organized as follows:
• Chapter 1, "Introduction," (this chapter) describes the contents and conventions used in the BNP2xr
User Guide.
• Chapter 2, "Overview," provides a detailed description of the BNP2xr and its features.
• Chapter 3, "Installation," describes the tools, precautions, and steps necessary to install the system
in the network.
• Chapter 4, "System Configuration," describes the initial product setup and product configuration
using the Java-based BNP Element Manager.
• Chapter 5, “Grooming and PSIP,” shows you how to set up grooming, transrating, and other
configuration and operational procedures.
• Chapter 6, “Digital Program Insertion (DPI)” describes DPI using the BNP.
• Chapter 7, “ETV Binary Interchange Format (EBIF)” provides an overview of EBIF and typical use
cases for configuration.

BNP2xr User Guide 1

Introduction

• Chapter 8, “Monitoring the BNP,” discusses the methods used to monitor the health of the BNP2xr
and its status in the network.
• Chapter 9, "Troubleshooting," provides information about system status, alarm messages, software
upgrades, and contacting technical support.
• Chapter 10, "Field-replaceable Units," shows you how to replace all field-replaceable units in the
BNP2xr.
• Chapter 11, "Specifications," includes information about system specifications including physical,
environmental, and regulatory and compliance definitions.
• Appendix A, “Editing the DVB NIT Table,” shows you how to edit, make additions to, and delete
items from the NIT table, one of the DVB tables.
• The glossary and index can be used to quickly reference information.

Document Audience
This guide is for system administrators and operators who are responsible for installation and
maintenance of the BNP2xr and for processing network broadcast. You should be familiar with
general video and networking terminology, and should be familiar with basic installation of hardware.

Most importantly, you must be familiar with the basics and principles of broadcast network
processing.

Document Conventions
Table 1 provides an easy way to recognize important information in the text.

Table 1. Document Conventions

When It means:
you see:
Notes are indicated by the icon shown at left, and point out information that may not be part of
the text but provide tips and other helpful advice.

Cautions are indicated by the icon on the left, and let you know that an action may have
undesirable consequences if the instructions are not followed correctly. Cautions also indicate
that failure to follow guidelines could cause damage to equipment or loss of data.
Warnings are indicated by the icon on the left, and indicate that failure to take the necessary
precautions or to follow guidelines could cause harm to equipment and personnel.

Online, clicking any blue link takes you to the item to which the link refers.

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

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

2 BNP2xr User Guide

CHAPTER 2

Overview

This chapter provides an overview of the Broadcast Network Processor 2xr model.

In This Chapter:
• “Product Overview,” next.
• “Product Features” on page 3.
• “BNP2xr Applications” on page 4.
• “BNP Deployment Architecture” on page 6.
• “Redundancy” on page 9.

Product Overview
RGB’s Broadcast Network Processor is a single one-rack-unit device that provides:
• Support of both standard definition (SD) and high definition (HD) program services in either
MPEG-2 or H.264 encoding; in a single rack unit, the BNP simultaneously grooms and inserts
digital ads.
• High density video transrating (rate shaping), statistical multiplexing, grooming and digital.
program insertion (DPI); transrates video streams with impressively high video quality.
• Multiple levels of redundancy support including service level and 1:1 chassis level redundancy.
• Up to 8 Gigabit Ethernet (GigE) interfaces for video input or output, as well as up to 18
asynchronous serial interface (ASI) I/O ports in a single rack unit device.

Product Features
In addition to being software-upgradeable, scalable, and highly reliable, the BNP has the following
features:
• Based on RGB's flexible Video Intelligence Architecture™ (VIA).
• 1 rack unit chassis (1RU), 300W maximum power consumption.
• 8 GigE interfaces standard and up to 18 optional ASI ports.
• Can process MPEG-2 and H.264 program streams over any of its Gigabit Ethernet or ASI inputs,
and route them to any of these interfaces.
• Performs seamless digital ad insertion and program substitution.
• Fully compliant with the SCTE 30 and SCTE 35 standards.
• Fully interoperable ad insertion with SeaChange, Arris, and other industry standard ad servers.
• EBIF support.

BNP2xr User Guide 3

Overview

• Supports multiple levels of redundancy at the chassis, service (program) and Ethernet port level.
• Supports SCTE-18 Digital Emergency Alert Messaging (EAS), which is used to integrate the BNP
with EAS management systems to control the playout of message crawls and audio during an
emergency alert event.
• Supports operator-generated text and graphic messages from the BNP GUI based on digital overlay
technology.
• Graphic overlays can be inserted anywhere on a program (MPEG-2) using the BNP GUI to import
standard graphic files (PNG).
• Supports scheduling for Logo Overlay and Operator Messaging up to one month in advance.
• Supports H.264 grooming and multiplexing in a MPEG-2 TS format.
• Supports “FAT” ASI transport services, multiple program groups over a single TS / ASI interface.
• Support of program substitution of a primary network source with a secondary source based on
SCTE-30 control.
• Supports SCTE-21 to SCTE-20 closed caption conversion.
• A graphical user interface for easy configuration and management.
• ATSC and DVB content support.
• International Time Zones.
• Language-specific GUI support.
• RADIUS/TACACS+ authentication support.

BNP2xr Applications
The BNP delivers the industry’s highest density digital video processing solution for a variety of
applications including:
• Switched digital broadcast grooming, transrating, and statistical multiplexing.
• DPI-based ad insertion.
• Enhanced TV.
• Digital Alert Messaging (including digital EAS, Advanced Messaging, and Logo Overlay
applications).
• Advanced Logo Overlay and Operator Messaging scheduling.

Grooming, Transrating and Multiplexing

Based on RGB’s Video Intelligence Architecture™ (VIA), the BNP’s ability to transrate program
streams with the highest quality is unsurpassed in the industry. The BNP seemlessly grooms multi-
program transport streams (MPTS / MUX) and single-program transport streams (SPTS) on both input
and output ports. It also offers multiple Quality of Service (QoS) priority levels on any MPEG-2
program stream enabling selection of the desired level of transrating.

4 BNP2xr User Guide

 BNP2xr Applications

DPI-Based Ad Splicing

Additionally, the BNP can concurrently groom and seamlessly splice both SD and HD program
streams encoded in either MPEG-2 or H.264 formats. This grooming and splicing capability eliminates
the need to dedicate multiple devices for different functions. The simplified installation, wiring and
configuration reduces system deployment time. The BNP is fully compliant with SCTE 30 and SCTE
35 standards and is interoperable with the leading digital program insertion (DPI) ad servers. This
flexible product can also perform SCTE 30 to SCTE 35 conversion to support digital ad insertion at the
hub. The BNP is an ideal solution for both centrally located DPI systems at the headend facility,
distributed DPI systems, and zoned and targeted ad insertion.

A BNP deployed in a cable digital broadcast video grooming and ad insertion environment is shown in
Figure 2.

DPI / Ad Servers
with Ad Content Zone 1
Ford CNN
BMW Ford
Toyota

Spliced Ads SCTE-30 Zone 2

CNN CNN
Avail BMW

SCTE-35
Splice Cues
Zone 3
CNN
Toyota

Figure 2. Regional Ad Zone Insertion Illustration

Messaging System

Digital EAS and Operator / Advanced Messaging

Leveraging its existing high-density video processing technology, the BNP’s digital Messaging
System capability allows operators to program both digital SCTE-18 Emergency Alert System (EAS)
alerts and operator-generated messages. The Advanced Messaging option allows importing graphics
and text files into the operator crawl message. EAS and Operator / Advanced Messaging alerts are
delivered universally throughout the network, overcoming existing challenges that cable operators face
in supporting analog and digital subscribers with an increasing range of decoding technologies.

The BNP’s Messaging System support can be applied selectively to any MPEG-2 program being
processed. EAS and operator-generated messages are digitally rendered and overlaid directly onto a
program, delivered directly to any digital subscriber set-top box or to analog decoders, and presented
as an overlay alert crawl to viewers. The BNP also supports operator-configurable audio override or
audio stream insertion to complement the text crawl message generated by industry-leading EAS
management vendors for a completely customizable deployment.

BNP2xr User Guide 5

Overview

A BNP in an SCTE-18 digital EAS application is shown below in Figure 3 below.

Digital
Video Services

NTSC
Modulated
EAS
GigE GigE GigE Channels
RGB Digital Decoder and
ENDEC Broadcast Network Processor Modulator
(SCTE-18 SCTE-18 10BT
Compliant ) Digital Video
Messaging Services with
(contains Text Crawl) GigE
EAS Text Crawl
and QAM
Baseband Baseband Digital EAS Audio Override Modulated
Video Audio Audio & Channels
Video QAM Modulator
GigE

Digital Encoder

Figure 3. BNP in SCTE-18 Digital EAS application

Graphic Overlay Insertion

In addition to EAS and operator messaging, the BNP Messaging System Logo Overlay option
supports inserting graphic overlays into any MPEG-2 program being processed. Graphic overlays are
based on importing static graphic Portable Network Graphics (PNG) files. Importing text files is also
supported, meaning that customers can create a library of graphic and text files to routinely use (see
workflow example below). Users can preview the imported PNG files before starting the overlay
insertion.

The location of the insertion is user configurable with positioning anywhere on the display screen
defined by (x,y) screen coordinates based on pixels relating to program resolution (e.g., SD and HD).
Logo overlay files can be created with PNG alpha channels to control transparency effects supported
by the BNP during the insertion of the overlay. Additionally, background transparency support is
available for non-ascii text overlays in order to support foreign markets.

BNP Deployment Architecture

The BNP’s modular and programmable platform is designed to provide operators with full processing
scalability to meet their specific processing requirements today and in the future. The program density
of the BNP is software-configurable and upgradeable, allowing operators to start at lower densities
and upgrade to the full hardware capacity through software licenses as their stream densities and
network needs grow.

This scalability reduces capital costs and allows operators to allocate budgets accordingly. By paying
for processing on an as needed basis, operators can wisely plan budgets based on today’s requirements
and avoid over-allocation to meet future needs. The programmable and upgradeable architecture of the
BNP, as well as its high processing power, eliminates hardware changes and will simplify and expedite
future deployments of new video processing applications.

The BNP supports both ASI and Gigabit Ethernet interfaces, allowing operators who have deployed
Gigabit Ethernet networks to profit from the increased cost-efficiency offered with this transport,
while still providing support for operators with legacy ASI networks. This flexibility enables operators
with ASI networks to continue with their existing infrastructures while providing an upgrade path for a
future transition to an IP-based network.

6 BNP2xr User Guide

 BNP Deployment Architecture

The BNP has eight Gigabit Ethernet interfaces and is scalable to support up to 18 ASI interfaces using
up to three ASI modules. The Gigabit Ethernet interfaces are part of the BNP’s base configuration and
no additional hardware or licensing is required to utilize these ports. Providing added flexibility, each
ASI interface is software configurable as input or output via an easy-to-use graphical user interface.

Figure 4. Example of BNP Grooming of GigE or ASI Input Over GigE Transport Network

The BNP2xr deployed for bulk rate capping in a Switched Digital Video (SDV) architecture is shown
in Figure 5.

Figure 5. Example of SDV Architecture over GigE Transport Network

BNP2xr User Guide 7

Overview

Figure 6 shows how the BNP2xr fits within the network for a centralized system architecture using
ASI interfaces. GigE interfaces could also be used for both input and output in a co-located headend
application.

Figure 6. Example of Co-Located ASI Architecture

Either ASI or GigE interfaces are used for MPEG input or output. Because of the distance, GigE
interfaces are typically used for transport between the headend and the hub/node.

Note: This unit is intended for local (intra-building) connections only and is not designed or
evaluated for direct connections to the public telecommunications/cable distribution system.
Cable and Ethernet connections should be made in accordance to the National Electrical
Code (NEC).
For example, make sure that at least one of the following conditions are met1:
- Cable runs are located in the same building as this unit;
- Any copper cables that run through air between buildings are less than 42m (140ft);
- Cable runs between buildings are in underground conduit, where a continuous metallic
cable shield or a continuous metallic conduit containing the cable is bonded to each
building grounding electrode system.

1. These options are from the US National Electrical Code, Sections 800.10, 800.12, 800.13, 800.31, 800.32, 800.33, and
800.40.

8 BNP2xr User Guide

 Redundancy

Redundancy
Since a single BNP may deliver advanced video services to hundreds or even tens of thousands of
subscribers in a video network, it is critical that the BNP provide a high availability of services. To
achieve such reliability, the BNP supports a multi-level redundancy feature to ensure service
availability and reduce system downtime. With proper configuration, the BNP can provide full chassis
level redundancy. Within each BNP, it provides Gigabit Ethernet port redundancy and a configurable
program service redundancy feature.
There are three distinct, user-configurable redundancy options supported by a BNP. These are:
• Program Redundancy
• Port Redundancy
• 1:1 Chassis Redundancy

The first two redundancies—Program and Port—operate within a single BNP chassis. The third—1:1
Chassis Redundancy—makes use of two BNP chassis.

Program Redundancy
The BNP supports program redundancy, sometimes referred to as service-level redundancy. For this
type of redundancy, when the primary program is gone, the BNP automatically switches to a redundant
or backup program. If any elementary streams are missing from one of the ports, the BNP switches to
the secondary port.

In a program redundancy configuration, a switch to backup occurs when:

• Missing MPTS/SPTS streams are identified by checking the PAT.
• Missing program streams are identfiied by checking the PMT.
• A missing video stream is detected.

You can assign a backup program for every program, and any program can be assigned to backup a
running primary program. The backup program can be another program on the same GigE port or it
can be on a different GigE port in the same chassis.

Program level redundancy is supported such that when there is a groomed program missing, a
designated input program can function as a “standby program” and will take over for the missing
program. The detection of a PAT / PMT missing for over 2 seconds is used as the threshold for the
detection of the missing input program.

For information about Program Redundancy configuration, see “Program Redundancy” on page 168.

Gigabit Ethernet Port Output Mirroring

The BNP supports Gigabit Ethernet port output mirroring within the same chassis. The mirrored port
serves as a standby port in case the primary port fails. The mirroring port must have a unique IP
address configured. The BNP delivers identical streams to both the primary port and the mirrored port
with the same destination IP address and port number, but a different source IP address.

BNP2xr User Guide 9

Overview

The multiplexes output on one GigE are delivered to the mirrored GigE port simultaneously as a fully
operational, redundant output GigE port. Regardless of mirroring, all active GigE ports must have
unique IP addresses assigned.

To set GigE port-level redundancy, see “GigE Port Configuration” on page 48.

1:1 Chassis-level Redundancy

When the ports and global settings are configured to do so, the BNP provides 1:1 redundancy. The
BNP supports hot-standby 1:1 chassis redundancy through heartbeat and virtual IP failover
mechanism.

Heartbeats provide the ability to synchronize failover to a secondary BNP. A heartbeat daemon on the
primary unit will send out unicast heartbeat messages on the management interface every 250
milliseconds.The heartbeat daemon running on the standby BNP listens to the heartbeats coming from
the primary BNP. If the standby BNP does not hear the primary BNP’s, it initiates a failover and takes
ownership. The heartbeat daemon running on the standby BNP checks for heartbeats coming from the
primary BNP over both the normal Ethernet 10/100BaseT management connection and optionally the
eighth Gigabit Ethernet port (GigE 8) connection (when used as a backup to the Ethernet 10/100BaseT
management port).

The LED on the right of the chassis indicates the redundancy role of a chassis: green indicates the
active chassis, and orange indicates a standby chassis.

The standby chassis takes over if the primary (active) chassis fails, if there is a system or module
overheat, failed fan, failed power supply, or missing heartbeat from the primary unit. The formerly
standby (now the active) chassis now becomes configurable through the BNP Element Manager.

Virtual IP addressing is used to support the BNP 1:1 chassis redundancy feature. If the active chassis
fails, the standby assumes the virtual IP address. Network devices communicate with the virtual IP
addresses, not to the physical IP addresses. If the active chassis’ input/output changes, the new setting
will be synchronized to the standby chassis automatically.

GigE 8 can be configured to send heartbeat messages in the initial setting. If the network Ethernet 10/
100 management connection is unplugged, the active chassis remains active. If the input or output
GigE link is down, the active chassis shows a hardware fault and becomes the standby.

The standby chassis does not have any separate licenses. The license usage on the active and standby
chassis is always synchronized; if the standby chassis becomes the active chassis, it assumes the
licenses of the active chassis.

10 BNP2xr User Guide

 Redundancy

Figure 7 illustrates a typical configuration scenario of the BNP hot-standby 1:1 chassis redundancy
feature.

Port 10/100 BaseT

192.168.1.1

Figure 7. 1:1 Chassis Redundancy using Heartbeat and Virtual IP Failover Mechanism

In this example, the primary BNP has a management IP address of 192.168.21.1 and the secondary
BNP has an address of 192.168.21.2. A third IP address in the same subnet 192.168.21.200 is
configured as a virtual IP address. The video server and management workstation will use this virtual
IP address to communicate to the active BNP unit. During the normal course of operation, the primary
BNP assumes the virtual IP address and acts as the active unit. When a failover event happens, the
secondary BNP will take ownership of the virtual IP address and assume the active role. It achieves
this by sending an ARP request to associate the secondary ports’ MAC addresses with the virtual IP
addresses. For information about 1:1 chassis redundancy configuration, see “1:1 Redundancy Best
Practices and Considerations” on page 46.

BNP2xr User Guide 11

Overview

12 BNP2xr User Guide

CHAPTER 3

Installation

This chapter provides the information necessary to install the BNP2xr into a rack. Read this entire
chapter before beginning, and perform the installation in the order described. Chapter 4, “System
Configuration,” describes the configuration procedure.

In This Chapter:
• “Before You Begin,” next.
• “Broadcast Network Processor Components” on page 14.
• “BNP2xr Component Layout” on page 18.
• “Rack Mounting the BNP2xr” on page 18.
• “Grounding the BNP2xr” on page 21.
• “Installing SFP Modules” on page 21.
• “Connecting AC Power to the BNP2xr” on page 22.
• “Connecting DC Power to the BNP2xr” on page 23.
• “Connecting External Ports” on page 26.
• “Installing the Compact Flash Card” on page 26.

Before You Begin

Required Equipment
Be sure that you have the required items listed below before you begin the installation of the BNP2xr.
You will need:
• Populated BNP2xr chassis, including:
- 1 GBP2 module;
- Up to three PROC2 modules;
- AC or DC power supply;
- ASI modules if ordered.
• Compact flash card.
• AC power cord, included if AC power supply is used.
• DC connector cables, if DC power supply is used.
• Front and rear rack mount brackets, included.
• Rack mount bracket screws, included.
• Two M4 grounding nuts, included.
• 8 rack mount screws.

BNP2xr User Guide 13

Installation

• Phillips and slotted screwdrivers.

• 1 ring lug for grounding.
• Ethernet cable long enough to directly connect the BNP2xr and the management workstation.

Electrostatic Precautions

Warning: Whenever computer components are handled (especially during installation), the
equipment can be damaged by the buildup of static electricity. Take precautions before
touching any internal components or boards by wearing an ESD wrist strap or working
on an antistatic mat. Always hold system modules by the edges and avoid touching any
electronic circuitry on the cards.

Broadcast Network Processor Components

This section describes the physical characteristics of the BNP2xr. Before installing, configuring, or
replacing any component of the BNP2xr, please be sure that you understand the chassis and its
components.

Front Panel
Figure 8 shows the front view of the BNP2xr with the bezel in place. When the front bezel is removed,
the RS-232 serial port is visible, as shown in Figure 9.

10/100 BaseT Ethernet Port

GigE Ports 1-8 (SFP)

2 4 6 8
BNP2xr
1 3 5 7

10 GigE Port
(XFP) - Not Used
Compact Flash Card
System LEDs DTI Port -
Not Used

Figure 8. Front panel (with bezel)

Note: The 10 GigE (XFP) and DTI ports are currently not used.

Each BNP2xr has eight GigE ports. These ports can be used for input and output (full-duplex) of video
over IP data streams. The ports, LEDs, and compact flash card are located on the Gigabit Ethernet
Processor-2 (GBP2) module on the front within the chassis enclosure.

For instructions on removing and replacing the GBP-2 module, see “Replacing a Gigabit Ethernet
Processor (GBP2) Module” on page 240.

14 BNP2xr User Guide

 Broadcast Network Processor Components

The RS-232 serial port, highlighted in Figure 9, is used only by field service personnel. Under normal
circumstances you will not need to access this port.

Serial port
Figure 9. Front panel (without bezel)

LED Indicators
The primary Light Emitting Diodes (LEDs) visible on the front of the BNP2xr chassis are shown in
Figure 10. These LEDs indicate the general health of the BNP2xr.

GigE 1-8 Port Status

Cfg/Pwr Fault Backup
(SFPs)
Compact Flash 10/100 BaseT Ethernet Port

Figure 10. LEDs

Table 2 describes the patterns used by the LED indicators.

Table 2. LED indicators

LED Color Indication

CFG/PWR Off No power to chassis
Solid Green Power is OK
Solid Red Chassis is powering up and configuration load is in
progress
Fault Solid Green System main process is in wrong state
Blinking Green System status is OK
Blinking Red/Orange Hardware fault or alarm
Backup Solid Green Active or primary chassis
Solid Red/Orange Standby chassis
Compact flash a Blinking Green FPGA configuration load in progress
Solid Green Compact flash card is OK
Blinking Red Compact flash card not installed
Solid Red Compact flash card error is present
GigE 1-8 Solid Green SFP installed
10/100 BaseT Solid Green Autonegotiated link status
Blinking Yellow Activity

BNP2xr User Guide 15

Installation

Table 2. LED indicators (Continued)

LED Color Indication

AC/DC Power On Solid Green AC/DC Power is on
Indicator Off No input AC/DC Power
(Rear Panel
Figure 12)
On-Board DC Solid Green On-board DC power OK
Power Status Solid Yellow On-board DC power fault
(Figure 13)

a. The compact flash card is necessary for BNP functionality.

Port Mapping
Figure 11 shows the SFP port location mapping scheme. These port numbers correspond with the port
LEDs described in “LED Indicators,” above.

Port number

2 4 6 8

1 3 5 7
12 34 56 78
Port LEDs

Figure 11. Port mapping and LED indicators

Rear Panel

Figure 12 shows the rear view of the BNP2xr with one network processor (PROC2) and three ASI
modules installed. The BNP2xr can be configured with different combinations of modules, depending
on the result you desire.

Network Processor Module (PROC2)

AC PWR
GOOD GOOD LOCK

ASI PROC-2

ASI ASI
100-240V-8.8A,50/60 Hz

ASI Modules

Figure 12. Rear panel

16 BNP2xr User Guide

 Broadcast Network Processor Components

Figure 13 shows the DC power supply

DC Power
Status

INPUT
OK
PWR
OK LOCK

+ + Positive Ground
Input 48V DC 22A

Figure 13. DC Power Supply

Configuration Options for PROC2 Combinations

There are a maximum of four modules in each BNP2xr chassis. At least one processor module card
must be used in the minimum hardware configuration.

The right side of the chassis holds the power supply, including the power connector and fan. The power
supply fan is not replaceable, except as part of the power supply. For details about replacing the
modules and power supply, see Chapter 10, “Field-replaceable Units.”

BNP2xr User Guide 17

Installation

BNP2xr Component Layout

The BNP2xr consists of three main sections: a network interface module—called the Gigabit Ethernet
Processor (GBP-2) module, two to four network processing modules—called PROC2 modules, and
the power supply assembly.

Power supply

PROC2 modules
GBP-2
module

PROC2 modules

Figure 14. BNP2xr chassis, components visible

Rack Mounting the BNP2xr

The BNP2xr is mounted into a standard 19-inch rack using rack mount brackets for both the front and
rear of the system.

When choosing the location for the BNP within a rack, make sure that the BNP2xr will be placed
within the rack evenly, and that the installation will not cause uneven mechanical loading and weight
distribution.

Do not mount the BNP2xr into any rack that obstructs clean air flow either in the front or the rear.
Generally, an aisle of at least 15 inches is the minimum distance to ensure proper air flow.

18 BNP2xr User Guide

 Rack Mounting the BNP2xr

Caution! Be sure that the BNP2xr is mounted in a location that meets the environmental conditions
shown in Table 3.

Table 3. Environmental Requirements

Condition Limits
Storage Temperature -40° to 70° C (-40° to 158° F)
Operating Temperature 0° to 40° C (32° to 104° F)
Humidity 5% to 95% (non-condensing)

To install the BNP2xr into a rack:

1. Using the provided screws, attach the front rack mount bracket to one side of the chassis as shown
in Figure 15.

Figure 15. Front brackets attached

2. Repeat Step 1 on the other side of the chassis.

BNP2xr User Guide 19

Installation

3. Install the chassis rear rack shelf to the rear mounting rails of the rack using two screws on each
side as shown in Figure 16.

Secure shelf to rear rails

Figure 16. Rack shelf

4. Install the BNP2xr chassis in the rack.

The rear edge of the chassis will rest on the rear rack shelf. Secure the front of the chassis to the
rack using two screws on each side, as shown in Figure 17.

Two screws
on each side

Figure 17. Mounted BNP2xr

20 BNP2xr User Guide

 Grounding the BNP2xr

Grounding the BNP2xr

Warning: The BNP2xr must be properly grounded to ensure safe operation. Before you connect
power or turn on the BNP2xr, ground the chassis. This section provides one method of
grounding. There may be others: check your network configuration for details.

To connect the chassis ground:

1. Using a length of wire, terminate one end with a ring lug.
For use with a DC power supply, the grounding wire must be a minimum of 12 AWG.
2. Using the provided M4 nut, install the ring lug on the grounding terminal.
The grounding terminal is at the rear of the BNP2xr chassis, located at the lower left of the power
supply, just beneath the power supply handle.

AC PWR
GOOD GOOD LOCK

Grounding terminal (AC power supply)

100-240V-8.8A,50/60 Hz

INPUT
OK
PWR
OK LOCK

+ + Grounding terminal (DC power supply)

Input 48V DC 22A

Figure 18. Grounding terminal, rear of chassis: AC power supply top, DC power supply bottom

3. Using wire strippers, strip off 3/8 inch of insulation from the other end of the wire.
4. Attach the stripped wire into a grounding hole on the equipment rack.

Installing SFP Modules

For optical output, Small Form Factor 1Gbps (SFP) transceivers comply with the current SFP Multi-
Source Agreement (MSA) Specification.
• GigE interfaces that meet 1000 Base SX specifications support 850 nm wavelengths for distances
up to 550 meters.
• GigE interfaces that meet 1000 Base LX specifications support 1310 nm and 1550 nm wavelengths
for distances up to 70 kilometers.

BNP2xr User Guide 21

Installation

SFPs approved for use with the BNP2xr are based on the Multi-Source Agreement (MSA) and listed in
Table 4:

Table 4. Supported SFPs

Manufacturer Part Number Description

Finisar FTLF1519P1BCL SFP 1550nm GigE optical module
Finisar FCMJ-8521-3 1000BaseT Copper SFP Transceiver
Fiberdyne FGE-SFP-T 1000BaseT Copper SFP Transceiver
Avago ABCU-5710RZ SFP 1550nm GigE optical module

Note: For updates on the latest SFPs and XFPs approved for use with RGB’s products, log in to
RGB’s Customer Portal and search for the following term:

SFP
-or-
XFP

To install an SFP, follow the manufacturer’s instructions. General guidelines to SFP installation
include:
1. Consider your network and cabling requirements and verify that the SFP you are installing is an
approved model as described in Table 4.
2. Insert the SFP into the port.
SFPs are keyed so they can only be installed one way.
3. Slide the SFP into the port until it clicks into place and the LED is activated.

Connecting AC Power to the BNP2xr

Once installed in a rack, connect power to the chassis.

Before you connect power to the chassis, make sure that the circuit, wiring, and connections that you
are using to supply the power will not become overloaded by the BNP2xr(s). For power consumption
details, see “Specifications” on page 245.

Caution! The power cord is the disconnect device for the BNP2xr. There is no power switch: once
connected to the power outlet, the unit powers up immediately.

Connect all ports before connecting power.

To connect AC power to a BNP2xr:
1. Locate the AC power cable included with the BNP2xr chassis.
2. Plug one end of the power cable into the BNP2xr power connector.

22 BNP2xr User Guide

 Connecting DC Power to the BNP2xr

3. The AC power connector is located on the power supply.

Power supply LEDs
AC PWR
GOOD GOOD LOCK

Power connector

100-240V-8.8A,50/60 Hz

Figure 19. Connect AC power

4. Plug the other end of the power cable into the input power source.
The unit should now have power. Check the LEDs to verify that power has been applied. See “LED
Indicators” on page 15 for details.

When the BNP2xr is installed and powered on, verify that the Cfg/Pwr LED is solid green. See “LED
Indicators” on page 15.

Disconnecting AC Power from the BNP

To remove AC power from the BNP, disconnect the power cable from the power source, that is, pull
the plug from the power connector. This is the only way to ensure that the unit is not receiving power.

Connecting DC Power to the BNP2xr

Before Connecting Power

Caution! Only trained personnel should install or replace this equipment.

• Remove all jewelry, including rings, necklaces, and watches. Metal objects will heat up when
connected to power and ground, and can cause serious injury or weld the metal object to the
terminals.
• The protective earth connection should be connected before proceeding with the power connection.
• The power cables should be attached to the breaker.
• Confirm that the DC power source is powered off during installation.
• For a centralized DC power connection, the unit must be installed in a restricted access location in
accordance with Articles 110-16, 110-17, and 110-18 of the National Electrical Code,
ANSI / NFPA 70.
• Damage may occur if the power is connected improperly.

Connecting Power
Caution! Make sure that the safety screw is in the locked position (turned counterclockwise) after the
power supply is installed, but before connecting power (Figure 20). Note that the locked
position may be different than that of similar units. This ensures that the power supply
cannot be accidentally disconnected, causing possible damage.

BNP2xr User Guide 23

Installation

Once installed in a rack, connect power to the chassis.

Before you connect power to the chassis, make sure that the circuit, wiring, and connections that you
are using to supply the power will not become overloaded by the BNP2xr(s). See “Specifications” on
page 245 for power consumption details.
Caution: These are +48V DC power supplies, not -48V. Please connect accordingly.

The two inputs to the DC power supply are +48V inputs. If you wish to have redundant inputs,
connect the inputs to the DC power supply from two different 48V sources. When both 48V inputs are
sourced, the power supply will load share across the inputs, each of the inputs drawing half the total
power. When one 48V input source fails, the other 48V input will draw the full power. If you choose
not to have redundant inputs, connect only one of the two inputs to the DC power supply and leave the
other disconnected.

The DC power supply is configured so that the black (top) cable connects to a -48VDC input and the
red (bottom) cable connects to positive ground. Before connecting any cables, measure the output to
make sure that you are connecting a -48VDC input to the black cable of the power supply.

Connect all ports before connecting power.

To connect DC power to a BNP2xr:

1. Cut the provided DC connector cables to the correct length to reach the BNP2xr from the power
source.
2. The DC power connectors are permanently attached to the power supply. Attach the connector
cables from the power source to the BNP2xr power connectors.

Lock the safety screw

Two cables for 48VDC redundancy

Two cables for ground redundancy

Power connector cables

Connect -48VDC input to black cable
Connect positive ground to red cable

Figure 20. Connect DC power

24 BNP2xr User Guide

 Connecting DC Power to the BNP2xr

3. Attach the other end of the power connector cables into the input power source.
The power cables should be attached to an external UL Listed 20 amp circuit breaker.

Connect to the
DC power source

Figure 21. Connect the power cables

4. To power the unit on, toggle the external circuit breaker to the ON position. There is no circuit
breaker on the BNP2xr.
The unit should now have power. Check the LEDs to verify that power has been applied. See “LED
Indicators” on page 15 for details.
When the BNP2xr is installed and powered on, verify that the Cfg/Pwr LED is solid green. See
“LED Indicators” on page 15.

Disconnecting DC Power from the BNP2xr

To remove DC power from the BNP2xr, toggle the circuit breaker to the OFF position, or remove the
fuse from the fuse panel. This is the only way to ensure that the unit is not receiving power.

BNP2xr User Guide 25

Installation

Connecting External Ports

The BNP2xr chassis has three discrete types of ports. When connecting ports, be sure to use the correct
cabling. This section describes the port types and basic cabling, but the actual cabling requirements
will depend on your specific network configuration and needs.

Fast Ethernet Management Port

The 10/100BaseT Ethernet port is used to communicate with an external console for SNMP
configuration control, maintenance diagnostics, status monitoring, fault notification, and redundancy
switching. The external console can be a workstation on the IP network.

GigE Port
The Ethernet port must be fitted with small-form-factor pluggables (SFPs). See Table 4 for a list of
tested and approved SFPs that can be used with the BNP2xr.

ASI Port
The number of ASI ports in your BNP2xr chassis depends on the number of ASI cards that are
installed. Up to three ASI cards can be installed, each with six ports.

Installing the Compact Flash Card

The BNP2xr uses a compact flash card to load software and save configuration information. You
cannot use your BNP2xr without it.

If the compact flash card was not shipped pre-installed with your BNP, you must install it. Remove the
flash card from the shipping container and install it into the compact flash slot located on the front of
the BNP chassis.

If your compact flash card fails, contact technical support for details about flash repair or replacement.
See page 234 for details on contacting technical support.

Caution! Your license is attached to the compact flash; do not discard it. Even if a CF card fails, keep
the device and contact RGB technical support for instructions on repair or obtaining a
working replacement.

26 BNP2xr User Guide

CHAPTER 4

System Configuration

The BNP is configurable through a Java-based graphical user interface (GUI) available through a
standard Web browser, or through SNMP using standard network management applications. The easy-
to-use interface offers a variety of features that simplify the set-up and operation of the BNP, including
program and transport level drag and drop grooming; simultaneous bit rate analysis of input and output
transport streams and programs; alarms and logs window; scheduled dynamic grooming with start/end
time and calendar entry; redundancy configuration; and full configurability of ASI and Gigabit
Ethernet ports.

This chapter describes how to configure the BNP2xr using the BNP Element Manager. You can also
use the BNP Element Manager to define and manage network processing as described in Chapter 5,
“Grooming and PSIP,” and to monitor the BNP system as described in Chapter 8, “Monitoring the
BNP.”

In This Chapter:
• “Obtaining Java Runtime Environment,” next.
• “Launching the BNP Element Manager” on page 28.
• “Using the Element Manager” on page 30.
• “BNP Element Manager Overview” on page 31.
• “Chassis View” on page 33.
• “Setting the Time Offset Table (TOT)” on page 34.
• “Global Chassis Configuration” on page 37.
• “Ethernet Control Port Configuration” on page 47.
• “GigE Port Configuration” on page 48.
• “Configuring ASI Ports” on page 50.
• “Modifying a Port Name” on page 51.
• “User Authentication” on page 53
• “Messaging System Configuration” on page 65.
• “SNMP Configuration” on page 98.
• “Upgrading Software” on page 100.
• “Clearing the Web Start Cache” on page 103.
• “The License Manager” on page 104.
• “Regrooming” on page 107.
• “Stopping All Services” on page 108.
• “Rebooting the System” on page 108.
• “Checking for the BNP Element Manager Version” on page 110.

BNP2xr User Guide 27

System Configuration

Obtaining Java Runtime Environment

The BNP Element Manager requires that the PC on which it is running have Java™ Runtime
Environment (JRE) v1.6 or higher. If your PC does not have the correct JRE installed, it is available
free from the RGB Customer Portal (see below).

Obtaining JRE from the RGB Customer Portal

To obtain installation instructions and the latest version of JRE that is compatible with the BNP
Element Manager, log in to RGB’s Customer Portal and search for the following term:
Download Java Runtime Environment

Launching the BNP Element Manager

You do not need to install the BNP Element Manager software. It is installed on the BNP at the factory,
and you connect via the IP address of the BNP.
To launch the BNP Element Manager:
1. Open a browser session on the management workstation or on any computer that has access to the
BNP.
The IP address of the workstation being used to access the BNP must be changed to an address on
the same subnet as the BNP chassis.
2. Enter the IP address of the BNP into the browser’s address field. The default IP address is 10.1.1.1.
For easier access, bookmark the URL or set it as the home page.

Figure 22. Enter the IP address of the BNP to access

28 BNP2xr User Guide

 Launching the BNP Element Manager

3. Click the Launch BNP Element Manager link.

Figure 23. Launch BNP Element Manager window

BNP2xr User Guide 29

System Configuration

Once launched, the window displays the Login Window. Log in as described in “Logging In” on
page 30.

Figure 24. BNP Element Manager login window (Local login, left; AAA server login, right)

Using the Element Manager

Use the BNP Element Manager to configure your system, perform grooming and ad insertion, monitor
system status, and upgrade software as needed.

Logging In
1. Once you have launched the BNP Element Manager and clicked the login link at the top of the
page, the login screen appears.
2. The BNP’s IP address automatically populates the IP Address or Host Name field.
3. Select your user account from the User drop-down list, or type the user name if using an AAA
server for authentication.
4. Enter the corresponding password in the Password field.

30 BNP2xr User Guide

 BNP Element Manager Overview

Note: Passwords are case sensitive. To change the password, see “User Authentication” on page 53.
To change an AAA server password, refer to the relevant documentation for the AAA server
being used.

Three levels of user, each with specific access to the system, have permission to use the Element
Manager. If you log in as a user with limited privileges, any option not available to you is grayed
out and cannot be selected. User levels include:

Table 5. User levels

Default
User name Password Permission
User User Logging in as User provides read-only access. You cannot make any changes
to the configuration.
Operator Operator Logging in as Operator provides both read and write access. Operators can
make changes to the configuration. This is the normal login level.
Administrator Admin The Administrator user is typically only used by Field Application Engineers
and Technical Support personnel, however access can be granted to key
headend personnel. The Admin has the highest rights and can change the
password.

5. Click Log In.

By default, the BNP Element Manager now opens to display the Grooming -> Mapping screen.

BNP Element Manager Overview

Element Manager Title Bar

Note: Many of the screens across the BNP Element Manager platform--whether you are using
BNPxr, BNP2xr, or BNP3xr--will appear exactly the same. For this reason, some figures in this
manual will not include the title bar. The BNP2xr model title bars is shown below:

For the BNP2xr model, the title bar looks as follows:

System Name BNP Model IP Address Login Level

Figure 25. BNP2xr title bar

BNP2xr User Guide 31

System Configuration

Element Manager Main Menu and Tabs

Once installed, the BNP Element Manager provides an easy way to configure your BNP system. The
BNP Element Manager contains the following menus and tabs, which are used to access specific
screens:

Table 6. Element Manager Menus

Menu Use
File Exits the BNP Element Manager.
View Refreshes the currently active window and allows you to choose whether the
program and grooming information will be displayed.
Maintenance Upgrade software, enter licensing options, change SNMP strings, set up and edit
Network Information Tables, Time Offset Tables, reboot, system shutdown,
remove chassis redundancy, and regroom.
Help Display online help and application information.

Some primary tabs have subtabs to further refine the view, others use selections that increase the
granularity of the information shown and provide access to further activities. The primary tabs
include:

Table 7. Element Manager Primary Tabs

Tab Use
Grooming Create and map programming, or monitor bit rates in real time.
Alarms & Events Specified events and alarms can be tracked on this tab. Configure the alarms and
events to display only the items you are interested in.
Configuration BNP configuration is performed through the subtabs of the Configuration tab.
These tabs include Global, Ethernet Control Ports, GigE Ports, ASI Ports, User
Authentication, Messaging System, and SNMP Trap.
Chassis The Chassis tab has no subtabs, but provides a quick overview of the status of
the BNP. Clicking a port opens port information and configuration dialogs.

Status Information
The lowest portion of the BNP Element Manager window provides status information. The
information displayed depends on the current selection and status of the BNP.

The left section displays the IP address of the BNP to which the BNP Element Manager is connected.
The right portion of the status bar shows the most recent, highest priority alarm triggered, if one exists.
Alarms are color-coded for fast identification.

Figure 26. Typical BNP Element Manager status bar

32 BNP2xr User Guide

 Chassis View

Chassis View
The BNP Element Manager automatically detects the chassis hardware and provides a graphical
display of the product components and their state, as shown in Figure 27.

By default, the first port is selected. All active ports appear green on the screen. For easy identification,
whenever another port is selected, that port’s icon is shown.

Figure 27. Chassis tab

The information on this screen cannot be changed and is displayed for informational purposes only.
When you move the cursor over a port on the screen, the cursor changes to a hand, indicating a link.
Depending on which port is selected, you can see the information about the 10/100 BaseT port
(Ethernet control), the GigE ports, or the ASI ports. If the selected port is active, it appears green on the
screen. In Figure 27, for example, the Ethernet Control Port is selected and active.

BNP2xr User Guide 33

System Configuration

The information displayed in the main Chassis Information screen is shown in Table 8. This
information is available regardless of whether the BNP selected or is the active or standby unit. For
standby units, however, some configuration options will not be available.

Table 8. Chassis information window

Field Description
Chassis Software Version Version of the software currently installed
Chassis Serial No Serial number for the chassis; useful when troubleshooting or
contacting technical support. The serial number is the same as the
100-BaseT port MAC address.
Chassis Up Time Amount of time that the chassis has been continuously accessible
Inside Chassis Temperature For each processor card, the internal temperature is displayed, allowing
easy determination that the temperature is within acceptable limits
(80° - 90° is normal; if the chassis temperature exceeds 90°, an alarm
is generated)
GBP Serial No Displays the serial number of the Gigabit Processing card.
Graphical view of physical A graphical representation of the front and rear of the chassis
configuration configuration: move the cursor over the port and click to modify
configuration
GigE port information Configuration and addresses of the GigE ports; select the port on the
graphical representation to view the information
Ethernet Control port Configuration and addresses of the Ethernet Control Port; select the
port on the graphical representation to view the information.
ASI Port Information Port, direction, and status; select a port on the representation to see
details about the port.
PROC2 Slot Information Clicking on the card shows: Slot (A, B, C, or D) and Card Serial No.

Setting the Time Offset Table (TOT)

The TOT conveys additional information about summer and winter time periods and gives the local
time offset with respect to UTC for different countries or regions. If the TOT is locally generated, user
interaction is required to define the country or region in which the receiver is operated.
The BNP supports the required DVB tables, including TOT. To set the TOT time offset:

34 BNP2xr User Guide

 Setting the Time Offset Table (TOT)

1. From the Element Manager, select Maintenance -> Setup Time Offset table(TOT) (Figure 28).

Figure 28. Choosing ToT Time Offset

The window of Figure 29 appears

Figure 29. ToT Time Offset Window

BNP2xr User Guide 35

System Configuration

Table 9 explains these parameters.

Table 9. Tot Time Offset Window Parameters

Field Description
Country Code The three character country code.
Region ID The region identifier, with range 0 to 60. If there is only one time zone in the
country, this value is zero. Otherwise, the timezones are numbered from 1
(most easterly) up to 60, (the most westerly).
DST Offset The DST offset: (range is -2:00, -1:30, -1:00, -0:30, 0, +0:30, +1:00, +1:30,
+2:00). The value is 0: when DST is not applicable; otherwise the offset to be
applied to current time when DST is in effect.
For instance, in the US, the local time offset when DST is not in effect is -8,
and when DST is in effect, it is –7. So, the DST offset is +1. polarity is 1 as
time is behind UTC.
Start Time Indicates when DST takes effect in the current year.
End Time Indicates when DST ends in the current year.
Day 1st, 2nd, 3rd or last Sunday.
Month January - December.
Hour 0-23.
Minute 0-59.

2. Enter the required information and click OK.

36 BNP2xr User Guide

 Global Chassis Configuration

Global Chassis Configuration

To view and configure information that is global to the BNP chassis:
1. From the Element Manager, select Configuration -> Global.
The Global chassis configuration window appears.

Figure 30. Global chassis configuration

BNP2xr User Guide 37

System Configuration

2. Use the fields and selection options to change the global configuration variables.
Table 10 describes the Global Configuration values that can be changed.

Table 10. Global Chassis Configuration Fields

Category Field Description/Values

System Time Source Force Sync Click this button to force synchronization between the
(NTP) BNP and the NTP server. This action will prompt for a
reboot of the BNP.
IP Addressa Enter up to 5 IP addresses for the NTP server; the first
(Servers 1-5) field cannot be blank. Enter one per NTP Address
field.
A green circle to the left of the Server number field
represents the active NTP server. The lack of a green
circle would mean the specified server is not active.
Offset (msec) This value shows the difference in milliseconds
between the reference time and the system clock.
Jitter (msec) This value indicates the magnitude of jitter in
milliseconds between several time queries.
Time Zone If Internal is selected, choose the time zone from the
pull-down list
System Name You can assign a unique system name for this BNP.
After you click Apply Configuration, this name will
appear at the top of the screen. In the example shown
the System Name is BNP_AC
System Log Address Enter this IP address to communicate with a Syslog
server.

38 BNP2xr User Guide

 Global Chassis Configuration

Table 10. Global Chassis Configuration Fields (Continued)

Category Field Description/Values

Advanced System Support SCTE 27 SCTE 27 Subtitling defines stream type 0x82 for
Parameters Subtitle (Stream Type program subtitles and subtitling methods. The default
0x82)b value is checked. When unchecked stream type 0x82
is not treated as a subtitle.
Enable SCTE-21 to Checking this box will enable the input program
SCTE-20 Conversionc conversion of SCTE-21 to both SCTE-21 and SCTE-
20 closed captioning formats on the output program.
Enable PSIP Check this box to enable PSIP processing.
processingd
PAL Modee Check this box to optimize BNP processing of Phase
Alternating Line (PAL) content.
• This setting is recommended if most programming
from the BNP uses PAL.
• This setting is not recommended with progressive
content.
Optimize Messaging on Check this box to optimize HD messaging, which:
HDf • Supports 3:1 HD programs per transport stream.
• Reduces the capacity to 4 TS per PROC module.
Enable Transparency for Check this box if you wish to enable transparency
Messaging Systemg filters in the Messaging System tab.
• This box must be checked if you wish to enable
transparency for Operator Messaging, Advanced
Messaging, and Logo Overlay in the Configuration
-> Messaging System tab.
• Checking this box will reduce BNP capacityh.
Chassis Redundancy Chassis Active Status Shows the role of the selected chassis: Primary or
Standby.
Redundancy Switch Interchanges the Primary and Standby in a redundant
configuration.
Redundant Chassis IP Address for the 10/ BNP uses the active/redundant designation for
Configuration 100 failover
• In the Element Manager GUI for the Active
chassis, enter the IP address of the Standby chassis.
• In the Element Manager GUI for the Standby
chassis, enter the IP address of the Active chassis.
IP Address for GigE 8 Enter the IP address of the GigE port if used to pass
(Optional) redundancy information.
• When this port is configured with an IP address,
heartbeat messages will be exchanged on this port.

BNP2xr User Guide 39

System Configuration

Table 10. Global Chassis Configuration Fields (Continued)

Category Field Description/Values

Virtual IP Address Virtual IP Address for Enter the IP address used by the system to manage
Configurationi the 10/100 redundancy
• This address must be the same on both the active
and standby chassis as it is shared by both units.
• This address must be on the same subnet as the
physical IP address.
• Leave blank if no redundancy system is in place
Virtual Gateway for 10/ Enter the IP address of the gateway (default router)
100 that the 10/100 virtual IP should use
• This field is optional.
• This address must be the same on both the active
and standby chassis as it is shared by both units.
Virtual IP Address for For each redundant GigE port, (1 through 8) enter the
GigE (1-8) IP address shared by the redundant ports.
• Each GigE port must be on a separate subnet.
a. It is recommended that at least one NTP server be used with the BNP. An NTP server is required for Digital Program
Insertion (DPI). It is recommended that the NTP server be up and running prior to booting up and / or configuring the pri-
mary NTP server for the BNP. To force a sync with the NTP server, click the Force Sync button.This will prompt for a
reboot of the BNP.
b. Checking or unchecking the SCTE 27 subtitling box requires a mandatory reboot of the BNP. It is recommended that this
flag be configured before any input or output transport stream configuration.
c. Checking or unchecking the SCTE-21 to SCTE-20 Conversion box requires a mandatory reboot of the BNP. It is recom-
mended that this flag be configured before any input or output transport stream configuration.
d. Checking or unchecking the PSIP Processing box requires a mandatory reboot of the BNP. It is recommended that this
flag be configured before any input or output transport stream configuration.
e. Checking or unchecking the PAL Mode box requires a mandatory reboot of the BNP. It is recommended that this flag be
configured before any input or output transport stream configuration.
f. Checking or unchecking the Optimize Messaging on HD box requires a mandatory reboot of the BNP. It is recommended
that this flag be configured before any input or output transport stream configuration.
g. Checking or unchecking the Enable Transparency for Messaging System box requires a mandatory reboot of the BNP. It
is recommended that this flag be configured before any input or output transport stream configuration.
h. Please see the latest Release Notes for details on the impact of enabling transparency for load time and bandwidth on
the BNP.
i. Changing the Virtual IP Address Configuration parameters will require a reboot of the BNP.

3. Click Apply Configuration.

Any time changes are made to a configuration, you must click Apply Configuration to save and
implement the changes.
4. To interchange the active and standby in a redundant configuration, click Redundancy Switch. If
you choose to force redundancy, there will be a service interruption of approximately two seconds.
See “Forcing Redundancy” on page 46.

40 BNP2xr User Guide

 Global Chassis Configuration

NTP Server Force Sync

The BNP can be configured to use up to five NTP servers with which the BNP will attempt to
synchronize. In the event of a significant disparity between the BNP’s time and that of the NTP server,
the BNP may (by design) take a long time to synchronize with the NTP server. You can manually
force a quick synchronization between the server and the BNP.

Forcing a synchronization will prompt for a reboot of the BNP, thus resulting in a service disruption on
non-redundant BNP configurations. Forced NTP synchronization on non-redundant BNP
configurations should be conducted during a maintenance window.

To force synchronization of the BNP with an NTP server, proceed as follows:

1. From the Configuration -> Global menu, click the Force Sync button.
You will be asked if you wish to apply the Force Sync:

Figure 31. Apply Force Sync

2. Click Yes.
The Password Verification window will open.

Figure 32. Reboot Password Verification window

3. Enter the Administrator password and click OK.

The Reboot confirmation window will open:

Figure 33. Reboot confirmation

4. Click Yes to reboot.

BNP2xr User Guide 41

System Configuration

Force Sync on Redundant BNP Systems

To force an NTP server sync in a 1:1 redundancy configuration, proceed as follows:
1. Log into the standby chassis using the physical IP address of the standby BNP.
2. Click on the Configuration -> Global tab.
3. Observe which server is active (a green dot will be next to the active server) and determine if the
Offset value warrants an NTP sync (offset exceeds +/- 15ms)

Figure 34. Force sync for standby NTP server

4. Click the Force Sync button.

You will be asked if you wish to apply the Force Sync (Figure 31 on page 41).
5. Click Yes.
The Password Verification window of Figure 32 on page 41 will open.
6. Enter the Administrator password and click OK.
The Reboot confirmation window of Figure 33 on page 41 will open.
7. Click Yes to reboot the standby BNP.
8. Allow the standby BNP to reboot and return to its available backup status.

42 BNP2xr User Guide

 Global Chassis Configuration

9. Log into the active BNP via its Virtual IP (VIP) address.
10.From the Configuration -> Global window, click the Redundancy Switch button.
The standby chassis now becomes the active chassis, and vice versa.
11. Log into the new standby BNP (formerly, the active chassis) via its physical IP address.
12.Follow steps4 through7 above to Force Sync the new standby BNP.
The new standby BNP will now reboot and return to its available backup status.

BNP2xr User Guide 43

System Configuration

Configuring Chassis-level 1:1 Redundancy

Conditions and Restrictions

1. To setup virtual IP address for the Gigabit Ethernet or 10/100BaseT management interface, you
must first have the valid physical IP address for the Gigabit Ethernet or 10/100 BaseT interface.
2. An ad or video server should only send ads or video streams to the virtual IP addresses.
3. Note that with hot-standby 1:1 chassis redundancy configured with virtual IP failover, unicast
inputs can not be received by both the active BNP and the standby BNP simultaneously. This
means that unicast stream failover will not be immediate and the standby unit will need to initiate
new unicast sessions, which will not allow an immediate failover condition for those streams. As an
alternative, two BNP units without virtual IP coordination could be configured with identical
streams routed to both units running in parallel with the standby unit output muted.
4. Currently, the BNP does not support the Gigabit Ethernet input port level redundancy. The 1:1
chassis level redundancy will cover the Gigabit Ethernet input port failure case. The indication of
the Gigabit Ethernet input port failure includes disconnection of the Gigabit Ethernet cable, loss of
the Gigabit Ethernet link.
5. When a Gigabit Ethernet port delivers only one program and the program is missing for over 2
seconds, the 1:1 chassis failover is used, instead of standby program failover.
6. Active and Standby BNPs must use the same software version.

To Configure Redundancy:
Configure the Standby Chassis first:
1. Log in to the Element Manager of the standby chassis as described in “Logging In” on page 30.
2. If you have not already done so, select the Configuration -> Ethernet Control Port menu and
change the IP Configuration, IP Address, Subnet Mask, and Gateway fields of the standby chassis
to the appropriate parameters for your network. (See “Ethernet Control Port Configuration” on
page 47 for more information). If you are changing any of these parameters, the system must be
rebooted, which you will be prompted to do when clicking Apply Configuration.
3. From the Element Manager of the standby chassis, select Configuration -> Global.
4. Enter the IP Address for 10/100 of the active chassis’ Ethernet control port as described in
Table 10, “Global Chassis Configuration Fields,” on page 38.
5. Enter the Virtual IP Address for 10/100 that will be shared by both active and standby chassis as
described in Table 10, “Global Chassis Configuration Fields,” on page 38.
6. Both active and standby chassis must have the same virtual IP address.
7. Enter the IP address in the Virtual Gateway for 10/100 field that will be shared by both active and
standby chassis as described in Table 10, “Global Chassis Configuration Fields,” on page 38.
8. If you are using a virtual gateway (optional), both active and standby chassis must have the same
virtual gateway.
9. OPTIONAL: If you wish to enable heartbeat messages on the standby chassis, configure the IP
Address for the GigE 8(Optional) field as described in Table 10, “Global Chassis Configuration
Fields,” on page 38.

44 BNP2xr User Guide

 Global Chassis Configuration

Note: If you configure the GigE 8(Optional) field to enable heartbeat messages and you have
directly connected the GigE 8 ports (i.e., you are not using a switch or hub to connect the
ports), you must disable Auto-negotiation for the GigE 8 port on the standby chassis as
described in “GigE Port Configuration” on page 48 for proper chassis functionality.

10.Click Apply Configuration.

11. Wait two minutes for the configuration to be saved. During this time, a change will occur to the
BNP GUI status bar: the addition of an indicator showing Active and Standby BNP IP addresses.
12.Ensure that the standby chassis does not have a license key:
• From the main Element Manager window, select Maintenance -> License Manager.
• Confirm there are no entries in any of the License Key fields as described in “The License
Manager” on page 104.
• If there are entries in either of these fields, please contact RGB technical support for assistance
on how to remove the license keys.
13.Shutdown the standby chassis from the Element Manager’s Maintenance -> Shutdown menu.
14.Turn off the standby chassis.

Configure the Active Chassis next:

1. Log in to Element Manager of the active chassis as described in “Logging In” on page 30.
2. From the Element Manager of the active chassis, select Configuration -> Global.
3. Enter the IP Address for 10/100 of the standby chassis’ Ethernet control port.
4. In the Element Manager configuration for the active chassis, enter the Virtual IP Address for 10/
100 that will be shared by both active and standby chassis’.
5. Both active and standby chassis must have the same virtual IP address.
6. In the Element Manager configuration for the active chassis, enter the IP address in the Virtual
Gateway for 10/100 field that will be shared by both active and standby chassis’.
7. If you are using a virtual gateway (optional), both active and standby chassis must have the same
virtual gateway.
8. Do not configure the IP Address of the GigE 8(Optional) field on the active chassis; this must be
done on the standby chassis.

Note: If you configure the GigE 8(Optional) field to enable heartbeat messages and you have
directly connected the GigE 8 ports (i.e., you are not using a switch or hub to connect the
ports), you must disable Auto-negotiation for the GigE 8 port on the active chassis as
described in “GigE Port Configuration” on page 48 for proper chassis functionality.

9. Click Apply Configuration.

10.Make sure that the active chassis does have a license key.
11. Turn off the active chassis.
12.Turn on the active chassis. Wait for it to fully boot up.
13.Turn on the standby chassis.

BNP2xr User Guide 45

System Configuration

Forcing Redundancy

Caution! Care is needed when selecting this action: forcing a redundancy change will temporarily
(and briefly) interrupt services during the failover process.

To force the current redundancy configuration to change (the secondary will become the active, or vice
versa), click the Redundancy Switch button from the Configuration -> Global tab.

1:1 Redundancy Best Practices and Considerations

The following information must be considered when working with 1:1 chassis-level redundancy:
• The configuration of the standby chassis is not available from the Element Manager while the unit
is a standby unit.
• Because the virtual subnet mask is not configurable, the virtual IP address must be on the same
subnet as the physical chassis IP addresses.
• Any changes to the virtual IP address requires a reboot of the active chassis.
• If the connection to the 10/100 control port on the active is broken, both chassis will have the same
output, unless GigE 8 is configured for heartbeat messages. This can be confusing to the network.
• A heartbeat is also sent through the GigE ports.

46 BNP2xr User Guide

 Ethernet Control Port Configuration

Ethernet Control Port Configuration

There is one Ethernet control port for each BNP. To view and configure the Ethernet Control port:
1. From the Element Manager, select Configuration -> Ethernet Control Port.
The Ethernet Control Port Configuration window appears.

Figure 35. Ethernet Control Port configuration

2. Table 11 describes the variables that can be changed. Depending on whether you choose a static
configuration or DHCP for obtaining an IP address to login, the variables may be different. By
default, a static IP address is used.

Table 11. Ethernet Control Port Configuration Fields

Field Description
IP Configuration Select the source of the BNP boot configuration file from the pull-down menu:
choices include BOOTP/ DHCP or static.
Chassis MAC Address A read-only field that displays the MAC address of the BNP.
Chassis IP Address If static is selected, enter the IP address of the BNP.
Subnet Mask If static is selected, enter the subnet mask of the BNP; you cannot leave this
field blank.
Default Gateway If static is selected, enter the IP address where packets are routed out of the
local network (the default router address).
(Optional) DNS Server If static is selected, enter the IP address of the DNS server being used.

3. Click Apply Configuration to save and load the changes.

BNP2xr User Guide 47

System Configuration

Determining the BNP IP Address for DHCP

If DHCP has been selected to obtain an IP address, the IP address can not be obtained through the
Element Manager. There are three methods you can use to determine the IP address:
1. Connect to the BNP through the serial console and at a prompt type ifconfig eth0.
or
2. If the DHCP server is available, check the MAC and IP mapping on the DHCP server.
or
3. Use a “sniffer” to sniff the network for DHCP traffic.

Note: If you choose DHCP rather than a static IP, you will need the assistance of RGB Networks
customer support. Contact them before you choose DHCP.

GigE Port Configuration

All GigE ports can be configured from the BNP Element Manager. The GigE ports support full duplex
processing of transport streams; this means that the same GigE port can be used for input and output.
The GigE Port configuration screen is shown in Figure 36.

Figure 36. GigE Port configuration screen

48 BNP2xr User Guide

 GigE Port Configuration

To modify a GigE port:

1. From the Element Manager, select Configuration -> GigE Ports.
All GigE ports are shown in a list. For easy identification, the ports appear with a color-coded icon
to recognize active and inactive ports. Active ports are shown in green.
2. Make any necessary changes to the GigE port configuration. Type the changes directly into the
appropriate field for the GigE port being modified.
Table 12 describes the variables that can be changed for each GigE port.

Table 12. GigE Port Configuration Fields

Field Description
Port The GigE port number, listed sequentially.
Status Read-only; the current status of the port.
MAC Address Read-only; the MAC address of the port.
IP Address The IP address for the interface; if no IP address is used, leave the field
empty.
Subnet Mask The subnet mask address.
Gateway The default gateway (default router) to use, if applicable.
Mirrored To If the port is mirrored, the port to which the selected port is mirrored
appears in a read-only field. When you mirror two GigE ports, in the
event of failure of one, the other one takes over without interruption.
Mirroring Click Set to open a dialog, allowing you to mirror this port.
Autonegotiaton Enable or disable autonegotation.

3. Click Apply configuration to apply the changes to your configuration.

Gigabit Ethernet Port Mirroring

Figure 37 shows an example of Gigabit Ethernet port mirroring. Gigabit Ethernet port 5 is mirrored to
Gigabit Ethernet port 4. This means that all traffic on Gigabit Ethernet 6 is copied over to Gigabit
Ethernet 4. The only difference for the traffic coming from Gigabit Ethernet 6 and Gigabit Ethernet 4 is
the source IP address.

To mirror one GigE port to another:

1. From the Configuration -> GigE Ports menu, click the Set button next to the port that is to be mir-
rored.

BNP2xr User Guide 49

System Configuration

2. From the drop down menu that appears, select the desired port to which the current port is to be
mirrored.
There is no need to click Apply Configuration as the mirroring happens as soon as the port is
chosen.

Figure 37. Mirroring GigE ports

This configuration is typically used in Source Specific Multicast deployment with IGMPv3 support.
The two Gigabit Ethernet ports serve as two difference sources for the same video traffic.

Removing Port Mirroring

To remove mirroring from a GigE port, from the GigE port configuration page, locate the mirrored
port and click Remove from the Mirroring column.

Configuring ASI Ports

The ASI ports on each slot can be viewed from the Configuration tab. Only active slots appear on the
tab; inactive slots are not shown. Up to four slots are displayed. For each slot, you can see:
• Port: the port number.
• Status: the current status of the port: Active or Inactive.

50 BNP2xr User Guide

 Modifying a Port Name

• Direction: the direction of dataflow on this port: Input or Output.

Use the pull-down list for direction to select or to change the data flow direction of a specific port.

Figure 38. ASI Port configuration tab

Note: In order for the ASI port to be displayed on the Inputs side of the Grooming -> Mapping
window, the port direction must be Input; in order for the ASI port to be displayed on the
Outputs side of the Grooming -> Mapping window, the port direction must be Output.

Modifying a Port Name

You can modify or change a port name for either a GigE or an ASI port. Proceed as follows.

BNP2xr User Guide 51

System Configuration

1. From the Inputs or Outputs side of the Grooming -> Mapping window, right click the desired
port name. The following pop-up menu appears (Figure 39).

Figure 39. Modify Port Name Menu

2. Choose Modify Port Name. The Modify Port Name menu appears (Figure 40).

Figure 40. Modifying the Port Name

3. Click OK. The modified port name appears (Figure 41).

Modified Port Name

Figure 41. Port Name Modified

52 BNP2xr User Guide

 User Authentication

User Authentication
The User Authentication screen provides a central area from which user control settings can be
edited, added, or deleted. The BNP permits both local and remote user authentication. Remote user
authentication is performed using an authentication, authorization and accounting (AAA) server that
supports RADIUS or TACACS+.

The AAA server handles requests for access to system resources to be configured, allowing
maintenance of user profiles to be performed once for any number of clients. When a client wants to
access a system resource, it must first get permission from the AAA server.

The BNP provides a local user fallback authentication method enabling users to log in when an AAA
server is not available. However, for security and account management reasons, use of AAA is
recommended. All passwords configured for AAA—both remote and local—are encrypted.

BNP2xr User Guide 53

System Configuration

The following workflow (Figure 42) describes the behavior of the authentication process when a user
attempts to login to the BNP.

Start

A B
Element Manager
Login

Use Remote AAA

Use Local
Server to Yes AAA Enabled? No
Authentication
Authenticate User

Remote Remote Local

Authentication No Authentication Yes No Authentication
Success? Failure? Success?

No
Yes

Yes
Remote
Authentication No
C
Timeout? Go to C

Yes

User logged in

Number of
Go to A No Retries Exceeded?

Yes

Generate system Additional AAA

Go to Next
log; Element Yes Servers Available?
AAA Server
Manager menu.

Authentication
Failed.
No Login Rejected.

Yes
Remote Only
Authentication
Enabled in Element
Manager?
Log Error.
Login Failure.

No

stop
Go to B

Figure 42. BNP User Authentication Workflow

54 BNP2xr User Guide

 User Authentication

The tabs available in the User Authentication screen are: Global, Local, and Servers, seen below in
Figure 38.

Global Configuration
The Global tab is used to configure global AAA options for the BNP system. To configure Global
AAA parameters, proceed as follows:
1. From the Element Manager, select Configuration -> User Authentication -> Global.

Figure 43. User Authentication - Global, AAA disabled

2. Check the Enable box to enable and view AAA-related fields.

BNP2xr User Guide 55

System Configuration

The Enable checkbox is used to activate the AAA settings on this screen. If Enable is not checked
(Figure 43) the AAA server-related fields are hidden and local user authentication will be used. If
Enable is checked (Figure 44) a specified AAA server will be used for user authentication.

These fields are hidden

when the Enable box
is unchecked.

Figure 44. User Authentication - Global, AAA enabled

3. Fill in the fields according to the parameters listed in Table 13.

Table 13 describes the fields available on the Global tab of the User Authentication screen:
Table 13. User Authentication - Global Fields

Field Description
Enable Used to enable authentication using AAA. When checked, the remaining fields in this
table will appear.
Default is unchecked.
Number of Retries The number of times the system will try connecting to a remote server before trying
another server in the list
Default is 0. Valid range is from 0 to 2.
Timeout (Sec) The amount of time (in seconds) to wait for a response from the remote server.
Default is 2. Valid range is from 1 to 4.

56 BNP2xr User Guide

 User Authentication

Field Description
Protocol The preferred protocol to use in selecting a server.
Valid options are:
• Radius - Try all RADIUS servers before trying TACACS+ servers.
• TACACS+ - Try all TACACS+ servers before trying RADIUS servers
Default is Radius.
Remote Only Checking this box will require the BNP to use only remote authentication. If enabled
and remote authentication fails or connection with the AAA server is not established,
local authentication is not performed and the user is not logged in.
Default is unchecked.
• At least one AAA server must first be configured before the Remote Only option is
checked and the configuration applied to the BNP. See “Server Configuration” on
page 58 for details on configuring an AAA server.

4. Click the Apply Configuration button to save changes.

Local Configuration
The Local tab permits the Administrator to configure the local user account passwords for the BNP
system. To configure passwords for the local login, proceed as follows:
1. From the Element Manager, select Configuration -> User Authentication - > Local.

Figure 45. User Authentication - Local

BNP2xr User Guide 57

System Configuration

The fields in the Local screen are used to manage the three local user account passwords. These
settings only apply if AAA is disabled or the AAA server is unreachable, and Remote Only is not
enabled.
2. From the User drop down box, select the user whose password you wish to modify.
3. In the Old Password field, type in the existing password for the account.
4. In the New Password field, type in the new password.
5. In the Retype New Password field, retype the new password.

Note: Passwords are case-sensitive. They may be composed of alphanumeric and most special
characters.

Table 14 describes the fields available in the Local screen:

Table 14. Local User Accounts

Field Description
User Read-only access account. No changes to the configuration are allowed.
• Default password is: User
• Passwords are case-sensitive.
Operator Read and write access are allowed for all configuration operations except changing
passwords.
• Default password is: Operator
• Passwords are case-sensitive.
Administrator Full access to the BNP system configuration is allowed.This is the only user account that
is authorized to change passwords.
• Default password is: Admin
• Passwords are case-sensitive.

6. Click the Change Password button to save changes. New passwords will be effective the next time
the user account is used to log into the Element Manager.

Server Configuration
The Servers tab is used to set up and configure AAA servers for the BNP system to use.

58 BNP2xr User Guide

 User Authentication

From the Element Manager, select Configuration -> User Authentication -> Servers.

Figure 46. User Authentication - Servers

The Servers tab lists the currently configured AAA servers that are to be used by the BNP system for
user authentication. From here AAA servers can be added, edited, deleted, or reordered.

Note: When deleting an AAA server, it may be necessary to reorder the list of servers so that the
desired server may be deleted in descending order. For instructions on changing the server
order, see “Server Order Behavior” on page 63.

Adding or Editing AAA Servers

The Edit AAA Server dialog is used both to add new AAA servers or to edit existing AAA servers.
The system allows up to eight AAA servers.

To add a server, proceed as follows:

BNP2xr User Guide 59

System Configuration

1. From the Servers tab, click Add.

The Edit AAA Server window will open:

Figure 47. Add AAA Server

2. Fill out the fields according to the parameters in Table 15.

3. If this server is to be available for the BNP to use when logging in via AAA, you must check the
Enable field.

Note: At least one AAA server must be enabled when the Remote Only option is selected from the
AAA Global Configuration menu. See “Global Configuration” on page 55 for more
information.

4. Click Apply to save changes and add the AAA server.

Editing an AAA Server

To edit an AAA server, proceed as follows:

60 BNP2xr User Guide

 User Authentication

1. From the Servers tab (Figure 46) highlight the desired AAA server to edit and click the Edit but-
ton.
The Edit AAA Server menu will open.

Figure 48. Edit AAA Server

2. Edit the fields according to the parameters listed in Table 15 below.

3. Click the Apply button to save changes and modify the server.

Table 15 describes the fields available in the Edit AAA Server dialog.
Table 15. User Authentication - Servers - Add/Edit Server Fields.

Field Description
IP Address The IP address of the AAA server.
When adding a server, default is blank.
When editing a server, this field is read-only.
Port Enter the TCP port to use on the AAA server. Valid range is: 0 to 65535.
Default for Radius is 1812.
Default for TACACS+ is 49.
Protocol Select the authentication protocol from the drop-down box to use when
communicating with the AAA server. Choose between Radius and TACACS+.
Default is Radius.
Shared Secret Enter the password or passphrase used to authenticate with the AAA server.
Retype Shared Secret Re-enter the password or passphrase used to authenticate with the AAA server.
Enable Check this box to enable the AAA server. If an AAA server is not enabled, it will not
be available for the BNP to use when logging in via AAA.

BNP2xr User Guide 61

System Configuration

Reordering Server List

The Servers tab is used to change the order in which the BNP system looks for AAA servers. To set
the server order, proceed as follows:
1. From the Element Manager, select Configuration -> User Authentication -> Servers.
2. Click on the Set Order button.

Figure 49. Edit AAA Server Order

3. In the Change Order to field, enter the new order of the AAA servers. Table 50 shows an example:

Figure 50. Edit AAA Server Order - modified

62 BNP2xr User Guide

 User Authentication

4. Click Apply to save changes.

The new server order will be displayed in the Servers tab as demonstrated in Figure 51 below:

Figure 51. New server order

Table 16 describes the fields available in the Edit AAA Server Order menu.
Table 16. User Authentication - Servers - Edit AAA Server Order Fields

Field Description
Current Order Displays the current server order. The default server order is the order in which the
AAA servers were added to the list. This field is read-only.
Change Order To The new server order to use.
• Separate each number with one space.
• The same number of servers must be entered that are listed in the Current Order
field. For example, if there are 5 servers listed in the Current Order field, changing
the order to 1 2 4 3 would be invalid; changing the order to 1 2 4 3 5 is valid.

Server Order Behavior

The order in which the system attempts to connect to an AAA server is based on the following:
• The preferred authentication protocol specified in the Protocol field of the User Authentication ->
Global tab;
• The current server order as shown in the Order column of the User Authentication -> Servers tab.

If the preferred authentication protocol is set to Radius, all RADIUS servers will be tried first,
followed by TACACS+ servers. If set to TACACS+, all TACACS+ servers will be tried first, followed
by RADIUS servers.

BNP2xr User Guide 63

System Configuration

For example if four AAA servers have been added to the AAA server list (see Table 17) and the
specified protocol preference is Radius, the order in which the servers are tried is A, D, B, C.

Table 17. AAA Server List Example

Current Server
AAA Server Order Protocol
A 1 RADIUS
B 2 TACACS+
C 3 TACACS+
D 4 RADIUS

Deleting Servers
To delete an AAA server, proceed as follows:
1. From the Element Manager, select Configuration -> User Authentication -> Servers.
2. Select the highest numbered AAA server from the Order column (see Figure 46 on page 59) and
click the Delete button.
The Delete Confirmation window will be displayed:

Figure 52. Server deletion confirmation

3. Select Yes to delete the server.

Note: The Servers tab will only allow deletion of a server in descending order. For example, if there
are four servers in the order of 1, 2, 3, 4, the order in which the servers must be deleted is
4, 3, 2, 1.

To delete a server whose order is not last, reorder the servers to change the desired deletion to
the last number in that order.

64 BNP2xr User Guide

 Messaging System Configuration

Messaging System Configuration

The Configuration -> Messaging System tab allows you to configure parameters for the BNP to
integrate with external messaging systems, insert operator messages directly from the BNP GUI, or
configure the BNP to use external text or graphic files as overlay messages. You can also configure the
BNP to insert a graphics file (PNG) into one or more programs as a digital logo overlay. To configure
these features you must create specific Messaging or Logo Overlay zones under the Messaging
System tab, which are then associated to desired programs through the Grooming -> Mapping tab.
This section describes how to create both Messaging and Logo Overlay zones. See “Show Program
List” on page 94 for instructions on how to associate and enable programs to Messaging or Logo
Overlay zones.

Messaging Zones

Up to ten Messaging Zones can be configured for the BNP. Within each zone, two types can be
configured: EAS or Operator and Advanced. A Messaging Zone may be sent either SCTE-18 alerts
that are used for EAS Messaging, Operator Messaging based on operator-defined text, or Advanced
Messaging created from imported graphics (.PNG) or text files, and advanced text parameters.
 From the Configuration -> Messaging System tab, select the Messaging Zones subtab.

The Messaging Zones subtab (Figure 53) provides a snapshot view of all messaging zones. It also
provides a global parameter associated only with EAS messaging for system-wide configuration of
audio EAS override during DPI.

BNP2xr User Guide 65

System Configuration

Figure 53. Configuration -> Messaging System tab

Table 18 describes the fields available from the Messaging Zones subtab.

Table 18. Messaging Zones subtab

Field Description
Reject EAS audio When checked, the BNP will reject all external SCTE-18 EAS messages with
override during DPI audio override priority for the duration of an ad insertion (text crawling will still
continue).
Zone Index The sequential index number of the created zone.This field is read-only. Up to ten
zones can be added.
Zone Type Displays what type of zone has been created. Choices are: EAS or Operator and
Advanced Messaging.
Zone Status The status of the Messaging Zone. This field is read-only. If the zone is an EAS
(for EAS Messaging Messaging Zone, possible choices are:
Zones) • Enable: EAS Zone is ready for SCTE-18 EAS message.
• Emergency Alert Crawl On: SCTE-18 EAS alert activated, text crawl is
displaying.
• Emergency Alert Audio Override: SCTE-18 EAS alert activated with Priority 15,
emergency audio is playing, text crawl will be present.
• Emergency Alert Video Switch: SCTE-18 EAS alert activated with Priority 15,
emergency video is playing.
Zone Status The status of the Messaging Zone. This field is read-only. If the zone is an
(for Operator or Operator or Advanced Messaging Zone, possible choices are:
Advanced Messaging • Enable: Messaging zone is ready to start Operator messaging or Advanced
zones) Messaging operations.
• Operator Messaging Loaded: Operator message is loaded on the BNP and is
ready to start the operator message.
• Operator Messaging Text On: Operator Alert Message is loaded on the BNP and
crawl text is displaying in the zone.
• Advanced Messaging Loaded: Text or graphic file is loaded on the BNP and
ready to play.
• Advanced Messaging On: Advanced Messaging is loaded on the BNP and
imported graphic and/or text crawl is displaying in the zone
• Scheduled: Operator Messaging or Advanced Messaging has been loaded and
scheduled, but currently is not being played.
Zone Name The name of the zone. This field is read-only and is created when adding or
modifying a new Messaging Zone.
UDP The UDP port used to detect an external SCTE-18 EAS server message. This field
is read-only and is populated when adding or modifying a new EAS Messaging
Zone. If the zone is Operator or Overlay this field will display “N/A”

EAS Messaging Zones

The BNP Digital EAS feature supports the SCTE-18 (2007) “Emergency Alert Messaging for Cable”
standard specification for EAS message control and display, which controls the playout of text
message crawls and audio during an emergency alert event. Using the 10/100 BaseT management
interface, the BNP supports the following SCTE-18 messages:
• EAS text crawl;

66 BNP2xr User Guide

 Messaging System Configuration

• EAS text crawl with audio override;

• Substitute EAS detail channel for the network feed.

The BNP will respond to any EAS alert based on the following SCTE-18-defined alerts:
• Levels 1-14: The BNP delivers a text crawl and allows adherence to the SCTE-18 specification to
override the audio source on defined channel with text information and encoded audio sources from
the EAS system.
• Level 15 (highest priority): The BNP offers user configuration to allow adherence to the SCTE-18
specification to override both video and audio on a detailed channel with the encoded service
provided by the EAS system, or to use the same configuration options for Levels 1-14.
- The BNP will force tune to the detailed channel for H.264 and treat it as a data program.

The BNP communicates with an external EAS management system for messaging zone control
information, including interpretation of FIPS (Federal Information Processing Standards)
announcements. Additionally, user configurable audio muting and audio override of the network
program's audio is supported.

To configure a new EAS Messaging zone:

Note: You must be logged in as the Administrator to add, modify, or delete Messaging Zones
configuration.

1. From the Configuration -> Messaging System tab, click on the Messaging Zones subtab.
2. Right-click anywhere on the white or light blue rows.

Figure 54. Messaging Zone pop-up window

3. Select Add EAS Messaging Zone from the pop-up menu (Figure 54).

BNP2xr User Guide 67

System Configuration

4. The Add EAS Messaging Zone window of Figure 55 opens:

Figure 55. Add EAS Messaging window

5. Fill out the appropriate fields according to your desired configuration.

Table 19 provides a description of the fields available in the Add / Modify EAS Messaging Zone
menu.

Table 19. Add / Modify EAS Messaging Zone menu

Section Field Description

Zone Index Zone Name Assign a unique name for the zone to be created.
This field accepts alphanumeric entries.
Up to ten Messaging Zones may be created; these
may be a mix of EAS or Operator and Advanced
zones.

68 BNP2xr User Guide

 Messaging System Configuration

Table 19. Add / Modify EAS Messaging Zone menu (Continued)

Section Field Description

Port Select desired GigE or ASIa port from the pull down
menu on which detailed channel information
(transport stream) is received for EAS messaging.
IP Address The IP address of the GigE port. Input a valid
multicast IP address on which the detailed channel
transport stream is received for EAS messaging.
(Not required for ASI ports.)
EAS Video Configuration
Source IP Address The IP address of the source from which the GigE
(This defines the EAS port receives data; the source IP address is
video source parameters optional and should only be included for IGMPv3
for substituting over the transport streams. (Not required for ASI ports.)
network program due to
alert status or audio UDP Port Input a valid UDP port on which the detailed
override option.) channel transport stream is received for EAS
messaging. Valid range is from 1 to 65535. (Not
required for ASI ports.)
Program Number Input the program number on which the program
information is received for EAS messaging.
Audio Override Delay (In Specifies the delay of audio splicing of the EAS
Secs) program by x number of seconds. Range is from 0-
255. A setting of 0 specifies no delay.
UDP Port Input the UDP port which will be used to detect an
external SCTE-18 EAS server message. The
typical port number used for this is 5050.
• SCTE-18 zone specific messaging will vary by
UDP port configuration.
• A unique UDP port should be configured for each
EAS zone.
PID Choice of two hexadecimal values as defined by
the SCTE-18 standard. Choose which value
corresponds to your server:
0x1FFB or 0x1FFC

EAS Zone Control Crawl Only Priority Sets the threshold at which program audio will be
Configuration overridden by an external EAS source.
• If the SCTE-18 message is less than or equal to
the value set here, then audio override will not
occur.
• If the SCTE-18 message is higher than this level,
but lower than priority 15, audio override will
occur.
• If the SCTE-18 message is priority 15, then all
output programs configured to receive EAS
messaging are tuned to the emergency channel
and the audio and text crawl is overridden.
• If priority is set to 0, then no SCTE-18 messages
will be set to Crawl Only.

BNP2xr User Guide 69

System Configuration

Table 19. Add / Modify EAS Messaging Zone menu (Continued)

Section Field Description

Crawl Position Select the location on the end user’s TV screen in
which the crawl text will appear. Choices are:
Top, Middle, Bottom.
For details on crawl positioning, see Table 20.
Crawl Speed Select the speed at which text will crawl across the
EAS Crawl Configuration
end user’s TV screen. Choices are:
Fast, Normal, Slow.
Crawl Background Color Select the background color on which the crawl text
will be displayed. Choices are:
Red, Green, Blue, Black.
Start Time Read-only field. Displays the day, date, and time
that the crawl has or will begin. Applies to both
external SCTE-18 EAS server and Operator Alert
messages.
Remaining Time Read-only field. If a limit was placed on the duration
of the alert (either in the Operator-defined Crawl
Duration field or from the external SCTE-18 EAS
server), the time remaining is displayed here.
Event Duration Read-only field. Displays how long the event is to
take place.
EAS Zone Status Current Status This field is read-only and will display one of the
following values:
• Enable
• Emergency Alert Crawl On
• Emergency Alert Audio Override
• Emergency Alert Video Switch
See Table 18 for a complete description of these
values.
Priority Read only field. This field will display the EAS
message priority (1-15).
Alert Text Read only field. Displays the EAS message alert.
a. The applicable ASI port (if selecting) must have been configured as an input port in order to appear in the pull down menu

Table 20, below, describes how the BNP displays crawl positioning with various resolutions:

Table 20. Crawl Positioninga

Horizontal
Resolution Crawl Height Top Middle Bottom
480 SD 48p 32p 208p 384p
576 SD 48p 48p 256p 464p
750 HD 80p 64p 320 576
1080 HD 80p 96p 496p 896p
a. Positioning is in pixels, from top of screen to top of crawl. Crawl Height is also in pixels.

6. Click Apply to save changes and create the messaging zone

70 BNP2xr User Guide

 Messaging System Configuration

To modify an EAS Messaging Zone:

1. From the Messaging System -> Messaging Zones subtab, double-click the EAS messaging zone
you wish to modify, or right-click EAS the zone and select Modify Messaging Zone from the pop-
up menu (Figure 54).
2. The EAS Messaging Zone ([Zone Index]:[Zone Name]) window opens.

Figure 56. Modify EAS Zone

3. Modify the desired fields according to the parameters listed in Table 19.
4. Click Apply to save changes to the messaging zone.

To Delete an EAS Messaging Zone:

1. From the Configuration -> Messaging System -> Messaging Zones menu, highlight and right-
click on the EAS Messaging Zone you wish to delete.
2. Select Delete Messaging Zone from the pop-up menu (Figure 54).
3. If there are no output transport streams associated with the selected zone, you will be asked to
confirm deletion and the zone will be deleted.

BNP2xr User Guide 71

System Configuration

4. If there are output transport streams associated with the selected zone, the following message
appears:

Figure 57. Delete Output TS-associated messaging zones

5. Click Yes to delete the zone and its association to any programs.

Operator and Advanced Messaging Zones

The BNP Messaging System feature supports Operator and Advanced Messaging Zones, which allows
the cable operator to generate a text crawl of up to 400 characters in length directly from the BNP
Element Manager or to specify a text or graphic file as an overlay. Both Operator and Advanced zones
can be associated to individual programs. This capability is only allowed using Administrator login
privileges.

Note: An Advanced Overlay license must be purchased in order to view or configure an Advanced
Messaging Zone. For more information on Advanced Overlay licensing, see “The License
Manager” on page 104.

Note: SCTE-18 EAS messages take precedence over Operator and Advanced Alert Messages. The
latter can not be sent to a program that has an active SCTE-18 message alert. An SCTE-18
message alert sent to a zone will immediately override any current GUI generated alert
message playout.

To configure an Operator Messaging Zone:

Note: You must be logged in as the Administrator to add, modify, or delete Messaging Zone
configuration.

1. From the Configuration -> Messaging System tab, click on the Messaging Zones subtab.
2. Right-click anywhere on the white or light blue rows.

Figure 58. Messaging Zone pop-up window

3. Select Add Operator and Advanced Messaging Zone from the pop-up menu (Figure 58).

72 BNP2xr User Guide

 Messaging System Configuration

4. The Add Operator and Advanced Messaging Zone window of Figure 55 opens.
5. Click the Operator Messaging tab.

Figure 59. Operator Messaging Zone tab

6. Fill out the appropriate fields according to your desired configuration.

Table 21 provides a description of the fields available in the Operator Messaging tab of the Add /
Modify Operator and Advanced Messaging Zone menu.

Table 21. Operator Messaging tab

Section Field Description

Zone Name Zone Name This field is common to both Operator and Advanced
tabs.
Up to ten Messaging Zones may be created; these
may be a mix of EAS or Operator and Advanced
zones.

BNP2xr User Guide 73

System Configuration

Table 21. Operator Messaging tab (Continued)

Section Field Description

Crawl Configuration Crawl Position Select the location on the end user’s TV screen in
which the crawl text will appear. Choices are:
Top, Middle, Bottom.
For details on crawl positioning, see Table 20
Crawl Speed Select the speed at which text will crawl across the
end user’s TV screen. Choices are:
Fast, Normal, Slow.
Crawl Background Color Select the background color on which the crawl text
will be displayed. Choices are:
Red, Green, Blue, Black.
Background Specifies the level of transparency in which the
Transparency Level background color will be displayed. At 0%, the
background color will be opaque; at 100% there will
be no background color.
You may type in any value from 0 to 100 or choose a
value from the drop-down box as follows:
0% (opaque), 25%, 50%, 75%, and 100%
NOTE: This box will not display unless Transparency
was enabled in the Global Configuration window.
Crawl Text, Duration, & Crawl Text Input the desired alert message up to 400
Frequency alphanumeric characters.
Crawl Duration This section provides the following options for the
duration of the text crawl:
• One Cycle: Plays the full message one time all the
way through.
• Play xxx Seconds: Plays the message for the
specified number of seconds (with a 5 second or
one cycle minimum). Message will play for the
duration that is longest: Specified value of seconds
OR one cycle.
• Continuous: Continuously plays message until the
Stop Crawl button is clicked.
Frequency Choose between two options for how often message
is played:
• Once: Plays message once, either for one cycle or
specified number of seconds (see above).
• Hourly: Plays message every hour, either for one
cycle or for specified number of seconds (see
above) from the moment Start is clicked until the
moment Stop is clicked.

74 BNP2xr User Guide

 Messaging System Configuration

Table 21. Operator Messaging tab (Continued)

Section Field Description

Schedule Start The BNP permits you to start a message immediately
or schedule it up to one month ahead.
• Now: Starts play immediately.
• Time: Allows you to schedule start time. Click on
pulldown arrow to display a popup window (seen in
Figure 60) to set start.
Stop • Forever: If message is set to play once (see
Frequency, above) this is the default.
• Time: When Frequency is set to Hourly, the
Scheduler popup is enabled. Click on the pulldown
arrow to display (see Figure 60) and set.
Zone Status Start Time Read-only field. Displays the day, date, and time that
the crawl has or will begin.
Remaining Time Read-only field. If a limit was placed on the duration of
the alert, the time remaining is displayed here.
Event Duration Read-only field. Displays how long the event is to take
place.
Current Status This field is read-only and will display one of the
following values:
• Enable
• Operator Messaging Loaded
• Operator Messaging Text On
• Advanced Messaging Loaded
• Advanced Messaging On
• Scheduled
See Table 18 for a complete description of these
values.
Next Start Time Read-only field. Displays the time that the next round
of messaging will begin.
Overlay Image Read-only field. Applicable to Advanced Messaging
tab. Displays the status of the graphic and/or text
overlay. Possible values are:
• Complete: An image or text file has been uploaded
to the BNP.
• None: No image or text file has been uploaded to
the BNP.

BNP2xr User Guide 75

System Configuration

Table 21. Operator Messaging tab (Continued)

Section Field Description

Show Program List Clicking this button will open the Show Program List
window, which displays all programs associated for
the specified zone.
• This button only appears when modifying a zone,
and not when creating a zone.
Enable Status Update/ Clicking this button will enable real-time polling of the
Disable Status Update Zone Status fields as well as any Operator-defined
Action Buttons at bottom
text crawls.
of screen
• When the Enable Status Update button is clicked
and real-time polling enabled, the button will
change to Disable Status Update. Clicking the
Disable Status Update button will disable real-time
polling.
• This button only appears when modifying a zone,
and not when creating a zone.

7. Click Apply to save changes and create the messaging zone.

To Schedule Messaging in Advance

1. Click the Time button.
2. Click the pulldown arrow in the Time field. The Advanced Messaging Schedule Window
appears.
3. Click the Month, Day and Time fields to schedule the message.
4. Press OK.

Figure 60. Advanced Messaging Schedule Window

To modify an Operator Messaging zone:

1. From the Messaging System -> Messaging Zones subtab, double-click the messaging zone you
wish to modify, or right-click the zone and select Modify Messaging Zone from the pop-up menu
(Figure 54).

76 BNP2xr User Guide

 Messaging System Configuration

2. The Operator and Advanced Messaging Zone ([Zone Index]) window below opens.

Figure 61. Modify Operator Messaging Zone

3. Modify the desired fields according to the parameters listed in Table 19.
4. Click Apply to save changes to the messaging zone.

To configure an Advanced Messaging Zone:

Note: You must be logged in as the Administrator to add, modify, or delete Messaging Zone
configuration.

Note: An Advanced Overlay license must be purchased in order to view or configure an Advanced
Messaging Zone. For more information on Advanced Overlay licensing, see “The License
Manager” on page 104.

1. From the Configuration -> Messaging System tab, click on the Messaging Zones subtab.

BNP2xr User Guide 77

System Configuration

2. Right-click anywhere on the white or light blue rows.

Figure 62. Messaging Zones pop-up window

3. Select Add Operator and Advanced Messaging Zone from the pop-up menu (Figure 62).
4. The Add Operator and Advanced Messaging Zone window of Figure 63 opens.
5. Click the Advanced Messaging tab.

Figure 63. Advanced Messaging Zone tab

78 BNP2xr User Guide

 Messaging System Configuration

6. Fill out the appropriate fields according to your desired configuration.

Table 22 provides a description of the fields available in the Operator Messaging tab of the Add /
Modify Operator and Advanced Messaging Zone menu.

Table 22. Advanced Messaging tab

Section Field Description

Zone Name Zone Name This field is common to both Operator and Advanced
tabs.
Up to ten Messaging Zones may be created; these
may be a mix of EAS, Operator, or Advanced zones.
Crawl Configuration Foreground Color Specifies the foreground color of the imported text file.
Click the Select Color button to choose which color
and color scheme to use.
Background Color Specifies the background color of the imported text
file. Click the Select Color button to choose which
color and color scheme to use.
Crawl Position Select the location on the end user’s TV screen in
which the imported crawl text or graphic will appear.
Choices are:
Top, Middle, Bottom.
For details on crawl positioning, see Table 20
Background Specifies the level of transparency at which the
Transparency Levela background color will be displayed for ASCII and Non-
Ascii text. At 0%, the background color will be opaque;
at 100% there will be no background colorb.
• You may type in any value from 0 to 100 or choose
a value from the drop-down box as follows:
• 0% (opaque), 25%, 50%, 75%, and 100%.
NOTE: This box will not be displayed unless
Transparency was enabled in the Global
Configuration window.
Font Choose the font in which the imported or typed text
should be displayed. Click the Select Font button to
choose font style, size, and attributes.
Crawl Speed Select the speed at which the imported text or graphic
will crawl across the end user’s TV screen. Choices
are:
Fast, Normal, Slow.
Text Input the desired alert message up to 400
alphanumeric characters, or use the Import Text
button to select a text file from the hard drive of the
computer on which the Element Manager is running.
The text file will then be uploaded to the BNP’s
memory.

BNP2xr User Guide 79

System Configuration

Table 22. Advanced Messaging tab (Continued)

Section Field Description

Graphic Displays the name of the .PNG file being used for
overlay crawl. If no file has been specified, this field
will be blank. To select a graphic file as an overlay
crawl, click on the Import Graphic button and choose
a .PNG file from the local computer on which the
Element Manager is running. The graphic will be
uploaded to the BNP’s memory when Apply is clicked.
Preview, Crawl Previewc Allows you to choose in which order the overlay (if
Resolution, Crawl using both text and graphics) will appear. Choose
Duration, and Frequency from:
Graphic+Text: Graphic on the left, text on the right
Text+Graphic: Text on the left, graphic on the right
NOTE: The Background Transparency setting only
applies to the text portion (ASCII or Non-ASCII) of the
overlay.
Crawl Resolution Allows you to choose at which resolution the overlay
will appear. Choose from:
SD (Wx48): Standard definition, width of overlay by 48
pixels in height.
HD (Wx80): High definition, width of overlay by 80
pixels in height.
Crawl Duration This section provides the following options for the
duration of the text crawl:
• One Cycle: Plays the full message one time all the
way through.
• Play xxx Seconds: Plays the message for the
specified number of seconds (with a 5 second or
one cycle minimum). Message will play for the
duration that is longest: Specified value of seconds
OR one cycle.
• Continuous: Continuously plays message until the
Stop Crawl button is clicked.
Frequency Choose between two options for how often message
is played:
• Once: Plays message once, either for one cycle or
specified number of seconds (see above).
• Hourly: Plays message every hour, either for one
cycle or for specified number of seconds (see
above) from the moment Start is clicked until the
moment Stop is clicked.

80 BNP2xr User Guide

 Messaging System Configuration

Table 22. Advanced Messaging tab (Continued)

Section Field Description

Schedule Start The BNP permits you to start a message immediately
or schedule it up to one month ahead.
• Now: Starts play immediately.
• Time: Allows you to schedule start time. Click on
pulldown arrow to display a popup window (seen in
Figure 60) to set start.
Stop • Forever: If message is set to play once (see
Frequency, above) this is the default.
• Time: When Frequency is set to Hourly, the
Scheduler popup is enabled. Click on the pulldown
arrow to display (see Figure 60) and set.
Zone Status Start Time Read-only field. Displays the day, date, and time that
the crawl has or will begin.
Remaining Time Read-only field. If a limit was placed on the duration of
the alert, the time remaining is displayed here.
Even Duration Read-only field. Displays how long the event is to take
place.
Current Status This field is read-only and will display one of the
following values:
• Enable
• Operator Messaging Loaded
• Operator Messaging Text On
• Advanced Messaging Loaded
• Advanced Messaging On
• Scheduled
See Table 18 for a complete description of these
values.
Next Start Time Read-only field. Displays the time that the next round
of messaging will begin.
Overlay Image Read-only field. Displays the status of the graphic
and/or text overlay. Possible values are:
• Complete: An image or text file has been uploaded
to the BNP.
• None: No image or text file has been uploaded to
the BNP.

BNP2xr User Guide 81

System Configuration

Table 22. Advanced Messaging tab (Continued)

Section Field Description

Show Program List Clicking this button will open the Show Program List
window, which displays all programs associated for
the specified zone.
• This button only appears when modifying a zone,
and not when creating a zone.
Enable Status Update / Clicking this button will enable real-time polling of the
Disable Status Update Zone Status fields as well as any Operator-defined
Action Buttons at bottom
text crawls.
of screen
• When the Enable Status Update button is clicked
and real-time polling enabled, the button will
change to Disable Status Update. Clicking the
Disable Status Update button will disable real-time
polling.
• This button only appears when modifying a zone,
and not when creating a zone.
a. The Background Transparency Level setting in the Advanced Messaging tab is applicable only to ASCII and Non-ASCII
text characters. Background Transparency Level is not applied to graphic overlays within text crawls. Alpha Channel
Transparency settings for the graphic overlay, if present in the.PNG file, will be preserved.
b. Please see the latest Release Notes for details on the impact of enabling transparency for load time and bandwidth on
the BNP.
c. When importing a .PNG or .TXT file for the first time, the graphic will appear in the Preview box; however, after the
graphic has been uploaded to the BNP and the Advanced Message tab is closed, the graphic is no longer available for
preview, even though it remains stored in the BNP.

7. Click Apply to save changes and create the messaging zone.

To modify an Advanced Messaging Zone:

1. From the Messaging System -> Messaging Zones subtab, double-click the messaging zone you
wish to modify, or right-click the zone and select Modify Messaging Zone from the pop-up menu
(Figure 54).
2. The Operator and Advanced Messaging Zone ([Zone Index]) window opens.

82 BNP2xr User Guide

 Messaging System Configuration

3. Click on the Advanced Messaging tab.

Figure 64. Modify Advanced Zone window

4. Modify the desired fields according to the parameters listed in Table 21 or Table 22.
5. Click Apply to save changes to the messaging zone.

To Delete an Operator or Advance Messaging Zone:

1. From the Configuration -> Messaging System -> Messaging Zones menu, highlight and right-
click on the Messaging Zone you wish to delete.
2. Select Delete Messaging Zone from the pop-up menu (Figure 58).
3. If there are no output transport streams associated with the selected zone, you will be asked to
confirm deletion and the zone will be deleted.

BNP2xr User Guide 83

System Configuration

4. If there are output transport streams associated with the selected zone, the following message
appears:

Figure 65. Delete Output TS-associated messaging zones

5. Click Yes to delete the zone and its association to any programs.

Operator and Advanced Messaging Zones Best Practices and Considerations

The following guidelines should be used when creating and modifying Operator and Advanced
Messaging zones:
1. Only one type of Messaging Zone (Operator or Advanced) may be loaded or actively playing as a
crawl in each zone.
2. Anytime you wish to make changes to an actively playing or loaded Messaging Zone, you must
stop the active crawl, make the desired changes, apply the changes to load them onto the BNP’s
memory, and start or restart the crawl.
3. If you wish to change an actively playing Messaging Zone from one type to another (e.g., from an
Operator Message to an Advanced Message), follow these guidelines:
• Click the Enable Status Update button and check the current status of the Messaging Zone
(see Table 18 for a description of status messages).
• If the current status of either Operator or Advanced Messaging is ON, stop the crawl by
clicking Stop in the active zone’s subtab.
• Make any changes to the desired subtab (Operator or Advanced).
• Click Apply to load the new message to the BNP’s memory.
• Click the Start button to begin playing the message.
• If the Enable Status Update button has been clicked, the new status will be appear as
[Operator Messaging Text or Advanced Messaging] On in the Current Status field.
4. If you wish to change a loaded but not actively playing Messaging Zone from one type to another
(e.g., from an Operator Message to an Advanced Message), follow these guidelines:
• Ensure the Enable Status Update button has been clicked.

Note: Use caution when opening multiple windows with the Enable Status Update option activated
as multiple GUI queries can place additional processing load on the BNP.

• Confirm the current status of the Messaging Zone (see Table 18 for a description of status
messages) is not ON.
• Make any changes to the desired subtab (Operator or Advanced).
• Click Apply to load the new message to the BNP’s memory.
• If the Enable Status Update button has been clicked, the new status will be appear as
[Operator or Advanced] Messaging Loaded in the Current Status field.

84 BNP2xr User Guide

 Messaging System Configuration

Logo Overlay Zones

Overview
In addition to EAS and operator messaging, the BNP Messaging System Logo Overlay option supports
inserting graphic overlays into any MPEG-2 program being processed. Graphic overlays are based on
importing static graphic Portable Network Graphics (PNG) files. You can preview the imported PNG
files before starting the overlay insertion, but once the graphic has been saved and uploaded to the
BNP, you can only see the name of the last file uploaded.

The location of the logo insertion is user configurable with positioning anywhere on the display screen
defined by (x,y) screen coordinates based on pixels relating to program resolution (e.g., SD and HD).
Additionally, the BNP will support alpha channel transparency inherent in the PNG file’s creation.
logo overlay files can be created with PNG alpha channels to control transparency effects supported by
the BNP during the insertion of the overlay.

Alpha Channel Transparency

In general, a graphics file is composed of three layers, or channels: RGB for red, green, and blue.
Another type of channel may be added to a graphics file to allow for the configuration of transparency
in the pixels when the RGB colors are merged, or layered, one on top of the other. This is known as an
alpha channel. Alpha channels define the importance of each pixel in the layering process so that
certain portions of the image can either be completely or partially masked. This allows for rectangular-
shaped images to appear as irregular-shaped by controlling the pixel opacity, which is important when
overlaying a logo to a TV screen.

PNG files are the most common and advanced file extension for supporting alpha channel
transparency. The BNP will support any transparency mask inherent to the aqlpha channel of a PNG
file as long as the Enable Mask field is checked in the Logo Overlay Zone menu.

Note: The Enable Mask field is only visible when the Enable Transparency for Overlays option is
checked in the Configuration -> Global window.

Below are two examples of PNG files in which alpha channel transparency has been configured for
100% background transparency. In the first example, transparency is not enabled on the BNP; in the
second example, transparency is enabled.

Alpha channel transparency has Alpha channel transparency has been configured
been configured in the PNG file but in the PNG file and enabled on the BNP.
not enabled on the BNP

Figure 66. Alpha Channel transparency examples

BNP2xr User Guide 85

System Configuration

Overlay Zone Configuration

Note: An Advanced Overlay license must be purchased in order to view or configure a Logo Overlay
Zone. For more information on Advanced Overlay licensing, see “The License Manager” on
page 104.

Note: SCTE-18 EAS alerts (highest priority) and Operator and Advanced Alert messages (second
priority) take precedence over Logo Overlays. A Logo Overlay can not be sent to a program
that has an active SCTE-18 message or Operator and Advanced Messaging alert. An SCTE-
18 message alert sent to a zone will immediately override any current GUI generated alert
message playout.

 From the Configuration -> Messaging System tab, click on the Logo Overlay Zones subtab.

The Logo Overlay Zones subtab (Figure 67) provides a snapshot view of all configured Logo
Overlay zones.

Figure 67. Configuration -> Logo Overlay Zones tab

86 BNP2xr User Guide

 Messaging System Configuration

Table 23 describes the fields available from the Messaging Zones subtab.

Table 23. Logo Overlay Zones subtab

Field Description
Zone Index The sequential index number of the created zone.This field is read-only. Up to 32
zones can be added.
Zone Name The name of the zone. This field is read-only and is created when adding or
modifying a new Messaging Zone.
Position Displays the X,Y position (in multiples of 16 pixels) of the logo placement and
whether the X axis is from the Left or Right (L or R) and the Y axis is from Top or
Bottom (T or B).
Zone Status The status of the Logo Overlay Zone. This field is read-only. Possible choices are:
• Enable: Logo Overlay zone is ready to start Logo Overlays.
• Logo Loaded: Logo is loaded on the BNP and is ready to start overlay.
• Logo On: Logo is loaded on the BNP and is currently displaying in the zone.
• Scheduled: Logo has been loaded and scheduled, but currently is not being
displayed.

Recommendations for Logo TV Screen Positioning

In order to simplify logo positioning for both SD and HD programs, the TV screen of either SD or HD
has been divided into 4 quadrants with the X,Y coordinates positioned relative to each corner: On the
X axis, the screen has been divided into left and right from 0 to 960 pixels (based on half the width of a
typical HD 1920 pixel screen). On the Y axis, the screen has been divided into top and bottom from 0
to 540 pixels (based on half the height of a typical HD 1080i screen).

In this manner a static overlay graphic may be accurately positioned regardless of SD or HD as long as
the X, Y coordinates for an SD program do not exceed an SD’s resolution. In order to ensure accurate
positioning, it is recommended that the X, Y coordinates be kept to a relatively low number.

Figure 68 shows an example of Logo Overlay positioning for an HD program (top graphic) and an SD
program (bottom graphic). The X, Y coordinates for the green logo boxes have been set to relatively
low numbers (x=64, y=64) so as to remain positioned closer to the corners of the TV screen for both
HD and SD resolutions. The X, Y coordinates for the blue logo have been set to high numbers (x=900,
y=500). As such, while the logo for an HD resolution of 1920 x 1080i is positioned in the center of the

BNP2xr User Guide 87

System Configuration

screen, the X, Y values are too large for the blue logo to be placed within the bounds of an SD screen
at 720 x 480i resolution.
1920 Pixels

HD Program Top
Top
0 960 0
Y
Logo Logo
Left Top, Left
Right
x=900
y=500
Logo
1080i X
540 540

Left Logo Logo Right

0 0
960
Bottom Bottom
720 Pixels

Top SD Program Top

0 360 0
Y
Logo Logo
Left Right

X, Y coordinates too high for SD.

480i X
240 240
Logo will not be seen on program.
Top, Left
Left Logo Logo Right x=900
y=500
0 0
360 Logo
Bottom Bottom

Figure 68. Logo Overlay Positioning

To configure a Logo Overlay Zone:

Note: You must be logged in as the Administrator to add, modify, or delete Logo Overlay Zone
configuration.

1. From the Configuration -> Messaging System tab, click on the Logo Overlay Zones subtab.
2. Right-click anywhere on the white or light blue rows.

Figure 69. Logo Overlay Zone pop-up window

3. Select Add Logo Overlay Zone from the pop-up menu (Figure 69).

88 BNP2xr User Guide

 Messaging System Configuration

4. The Add Logo Overlay Zone window of Figure 70 opens.

Figure 70. Add Logo Overlay Zone tab

5. Fill out the appropriate fields according to your desired configuration.

Table 24 provides a description of the fields available in the Add Logo Overlay Zone menu.

Table 24. Logo Overlay tab

Section Field Description

Top Section Zone Index Read only field; indicates the index number of the
zone. Up to 32 Logo Overlay zones may be created.
Zone Name Enter a name for a zone. Accepts alphanumeric
characters.

BNP2xr User Guide 89

System Configuration

Table 24. Logo Overlay tab (Continued)

Section Field Description

Logo Configuration X Position (0 to 960) Enter the pixel number (in multiples of 16) where the
(Multiple of 16 pixels) logo will begin for the X position (horizontal) of either
the left or right quadrants of the TV screen.
(X Position) From Left Click this button if the logo’s X position is to start from
the left quadrant of either the top or bottom quadrant.
For example, if the X position were set to 32 and the
From Left button selected, the logo’s left most edge
would start 32 pixels from the left quadrant of either
the top or bottom quadrant (whichever is selected).
(X Position) From Right Click this button if the logo’s X position is to start from
the right quadrant of either the top or bottom
quadrant.
For example, if the X position were set to 32 and the
From Right button selected, the logo’s right most
edge would start 32 pixels from the right quadrant of
either the top or bottom quadrant (whichever is
selected).
Y Position (0 to 540) Enter the pixel number (in multiples of 16) where the
(Multiple of 16 pixels) logo will begin for the Y position (vertical) of either the
top or bottom quadrants of the TV screen.
(Y Position) From Top Click this button if the logo’s Y position is to start from
the top quadrant of either the left or right quadrants.
For example, if the Y position were set to 32 and the
From Top button selected, the logo’s top most edge
would start 32 pixels from the top quadrant of either
the left or right quadrants (whichever is selected).
(Y Position) From Bottom Click this button if the logo’s Y position is to start from
the bottom quadrant of either the left or right
quadrants.
For example, if the Y position were set to 32 and the
From Bottom button selected, the logo’s bottom most
edge would start 32 pixels from the bottom quadrant
of either the left or right quadrants (whichever is
selected).
Enable Mask Check this box if the BNP is to display and support
alpha channel transparency configurations inherent
to the imported graphic. For more information, see
“Alpha Channel Transparency” on page 85.

90 BNP2xr User Guide

 Messaging System Configuration

Table 24. Logo Overlay tab (Continued)

Section Field Description

Zone Status Start Time Read-only field. Displays the day, date, and time that
the crawl has or will begin.
Remaining Time Read-only field. If a limit was placed on the duration
of the alert, the time remaining (in a running-down
counter) is displayed here.
Event Duration Read-only field. Displays how long the event is to
take place.
Current Status This field is read-only and will display one of the
following values:
• Enable
• Logo Loaded
• Logo On
• Scheduled
See Table 23 for a complete description of these
values.
Next Start Time Read-only field. Displays the time that the next round
of messaging will begin.
Logo Import Section Logo Image Displays the location and name of the imported
graphic that has been uploaded to the BNP.
Import Graphic... Click this button to select a PNG file from the local
computer on which the Element Manager is running.
Logo Render Preview When uploading a new graphic to the BNP, it will be
(Max logo image size is displayed here. After the logo has been uploaded
256x176 pixels) (i.e., Apply has been clicked), and the Logo Overlay
window is closed, the graphic will not be displayed
again, however, the file name will still be displayed in
the Logo Image field.
Crawl Duration This section provides the following options for the
duration of the text crawl:
• Play xxx Seconds: Displays the graphic for the
specified number of seconds (with a 5 second or
one cycle minimum). Logo will display for the
duration that is longest: specified value of seconds
OR one cycle.
• Continuous: Continuously displays logo until the
Stop button is clicked.
Crawl Frequency Choose between two options for how often message
is played:
• Once: Displays graphic once or for specified
number of seconds (see above).
• Hourly: Displays graphic every hour, either for one
cycle or for specified number of seconds (see
above) from the moment Start is clicked until the
moment Stop is clicked.

BNP2xr User Guide 91

System Configuration

Table 24. Logo Overlay tab (Continued)

Section Field Description

Schedule Start The BNP permits you to start a message immediately
or schedule it up to one month ahead.
• Now: Starts play immediately.
• Time: Allows you to schedule start time. Click on
pulldown arrow to display a popup window (seen in
Figure 60) to set start.
Stop • Forever: If message is set to play once (see
Frequency, above) this is the default.
• Time: When Frequency is set to Hourly, the
Scheduler popup is enabled. Click on the pulldown
arrow to display (see Figure 60) and set.
Show Program List Clicking this button will open the Show Program List
window, which displays all programs associated for
the specified zone.
• This button only appears when modifying a zone,
and not when creating a zone.
Enable Status Update/ Clicking this button will enable real-time polling of the
Action Buttons at bottom Disable Status Update Logo Overlay Zone Status fields.
of screen • When the Enable Status Update button is clicked
and real-time polling enabled, the button will
change to Disable Status Update. Clicking the
Disable Status Update button will disable real-time
polling.
• This button only appears when modifying a zone,
and not when creating a zone.

To modify a Logo Overlay Zone:

1. From the Messaging System -> Logo Overlay Zones subtab, double-click the zone you wish to
modify, or right-click the zone and select Modify Logo Overlay Zone from the pop-up menu
(Figure 69).

92 BNP2xr User Guide

 Messaging System Configuration

2. The Logo Overlay Zone ([Zone Index: Zone Name]) window opens.

Figure 71. Modify Logo Overlay Zone window

Note: If a Logo Overlay is currently On (click the Enable Status Update button to see real time
status updates of the zone), stop the overlay first before modifying desired parameters.

3. Modify the desired fields according to the parameters listed in Table 24.
4. Click Apply to save and upload new changes to the overlay zone.

To Delete a Logo Overly Zone:

1. From the Configuration -> Messaging System -> Logo Overlay Zones menu, highlight and right-
click on the Logo Overlay Zone you wish to delete.
2. Select Delete Logo Overlay Zone from the pop-up menu (Figure 69).

BNP2xr User Guide 93

System Configuration

3. If there are no output transport streams associated with the selected zone, you will be asked to
confirm deletion of the zone and the zone will be deleted.
4. If there are output transport streams associated with the selected zone, the following message
appears:

Figure 72. Delete Output TS-associated messaging zones

5. Click Yes to delete the zone and its association to any programs.

Messaging System Zone Priority

At any given time there can be only one Messaging System zone active for a particular program, even
though each type of zone (EAS, Operator and Advanced, or Logo Overlay) can be enabled or
associated to a particular program at the same time. If all associated zones have been activated, the
priority of message playout is as follows:
1. EAS Messaging - will always override any Operator-defined crawl or Logo Overlay for the dura-
tion of EAS playout.
2. Operator and Advanced Messaging - will override an active Logo Overlay for the duration of
playout. If playout is continuous and Logo Overlay is also active, then no Logo Overlay will be
seen.
3. Logo Overlay - no override.

As an example, let us assume that a program playing on Channel 2 has all three zones configured with
EAS, Operator and Advanced, and Logo Overlay zones, with a scheduled Operator Messaging text
crawl scheduled to playout one cycle every hour and a continuously active Logo Overlay. During the
time that the Operator Messaging crawl is scheduled to play, the Logo Overlay will not be present,
however, when the crawl has finished its cycle the Logo Overlay will return. If, at any time, an EAS
message is generated, both the Operator crawl and the Logo Overlay (after the crawl has finished) will
be overridden until the EAS messaged has completed its cycle.

Show Program List

Within each Messaging System zone you can view which active programs have been configured and
enabled for messaging services.

Programs Configured for Messaging Services

When a program is groomed from an input source to an output transport stream, you can specify which
Messaging System Settings are configured (or associated) on a per program basis. A program can be
associated with any or all three Messaging zone types (EAS, Operator and Advanced, and Logo
Overlay). For more information on associating programs for Messaging Zones, see “Creating MPEG-
2 Output Transport Streams” on page 123.

94 BNP2xr User Guide

 Messaging System Configuration

Managing Program Activity for Messaging Service Zones

An output program may join or leave a Messaging Service zone at any time, the changes taking effect
the next time a message event starts.
Once a program has been associated with a Messaging Service zone, the program can then be enabled
or disabled for the specified zone either from the Grooming -> Mapping window (see “Creating
MPEG-2 Output Transport Streams” on page 123) or through the Show Program List window.
The Show Program List window displays all output programs across all transport streams on all ports
(GigE and ASI) that are currently enabled for the selected zone. Through this window you can enable
or disable Messaging Service operation for one or all programs in a zone.
There are two ways to view programs associated with Messaging System zones:
1. From the Configuration -> Messaging System -> Messaging Zones or Logo Overlay Zones
menu, highlight the desired zone, right-click, and select Show Program List from the pop-up win-
dow (Figure 73).

Logo Overlay Zones -> Show Program List

Messaging Zones -> Show Program List

Figure 73. Show Program List Pop-up windows

Or:

BNP2xr User Guide 95

System Configuration

2. Click on the Show Program List button from either the Modify Messaging Zone window
(Figure 56, Figure 61, Figure 64) or the Modify Logo Overlay Zone windows (Figure 71).
The Show Program List window for the selected zone will open.

Figure 74. Show Program List window

The Show Program List window will display all transport streams that have programs configured for
the specific Messaging zone. To view the specific programs and whether or not they are enabled for

96 BNP2xr User Guide

 Messaging System Configuration

Messaging Services, you must drill down to the program level in the window by clicking the + icon
next to each listed transport stream.

Figure 75. Show Program List window - drill down

Show Program List Options

• Enable or Disable specific programs for messaging: Highlight, then right-click on desired program
and choose either Enable or Disable from the pop-up menu (Figure 75) or click the Enable or
Disable button at the bottom of the window (Figure 76).

Figure 76. Show Program List pop-up menu

• Enable or Disable all configured programs for messaging: Click the Enable All or Disable All
button at the bottom of the window (Figure 75)
• View Messaging status: View which programs under a specific transport stream are configured only
or configured and enabled for messaging by identifying its associated program icon.
- An icon with a dark brown line under the green arrow is configured but not enabled for
messaging.

BNP2xr User Guide 97

System Configuration

- An icon with a pink line under the green arrow is configured and enabled for messaging.
Messaging configured and enabled program

Messaging configured but disabled program

Figure 77. Messaging Zone Icons

• Refresh Program list: Click the Refresh button at the bottom of the Show Program List window.
(Figure 74).
• Scroll-over Program Status: Scroll over the program name with your mouse to view its current
status.

Figure 78. Scroll-over program status

Creating Messaging Zone Transport Streams and Output Programs

To create a transport stream or output program to use a Messaging Zone, see “Creating MPEG-2
Output Transport Streams” on page 123 and “Creating Programs” on page 144.

SNMP Configuration
The SNMP (Simple Network Management Protocol) tab lets you set the IP addresses for the SNMP
traps. These traps then issue event notifications to the network management station. SNMP is the
network management protocol used in TCP/IP networks. You can use SNMP to monitor and control
network devices as well as manage configurations and collect statistics. You can change the SNMP
information at any time.

You can configure an SNMP trap agent or an SNMP community string.

Configuring an SNMP Trap Agent

Configure an SNMP agent to send traps to an SNMP manager to report significant events. Use either
an in-band or an out-of-band IP interface to manage the system with SNMP. To configure SNMP for
system management with SNMP, assign an IP address to an in-band Ethernet port, then set the
destination IP address to which the traps are forwarded by the system agent.

98 BNP2xr User Guide

 SNMP Configuration

1. From the Element Manager, select Configuration -> SNMP Trap. The SNMP Configuration
window appears.

Figure 79. SNMP configuration window

2. Enter the IP address for each SNMP trap desired: up to eight addresses can be specified. This
indicates up to eight ports.
3. Click Apply Configuration to save your configuration.

Changing a Community String

To change an SNMP community string:
1. From the Element Manager, select Maintenance -> Change SNMP Community String.

Figure 80. Modifying an SNMP Community String

BNP2xr User Guide 99

System Configuration

2. Change either or both the Read and Write strings to the correct values.

Upgrading Software
To upgrade to the latest BNP software, download the software from an FTP server and use the BNP
Element Manager upgrade feature to perform the upgrade. You will receive the specific information
about the upgrade software when you purchase an upgrade, or when you are notified that an upgrade is
available. Upgrade support software includes upgrades for both active and standby units in a
redundant system.

Note: Please contact RGB Networks’ customer support for assistance in performing a software
downgrade process.

To Upgrade Software in a Single Chassis Environment

1. From the main Element Manager menu, select Maintenance -> Software Upgrade.
The Upgrade Software dialog appears.

Figure 81. Upgrade Software dialog

100 BNP2xr User Guide

 Upgrading Software

2. Enter the information required to perform the upgrade as described in Table 25:

Table 25. Upgrade Software Configuration Fields

Field Description
FTP Host Enter the IP address of the FTP server on which the upgrade software
package resides.
User Name Enter the user name needed to access the FTP server.
Password Enter the password for the user name provided above.
Directory and File Name Enter the directory and file name for the upgrade software.
Reboot chassis after To reboot the chassis automatically, enable this feature; otherwise, you will
successful software upgrade have to reboot the chassis manually.

3. Click the Upgrade button to begin the upgrade procedure.

As the software is upgraded, you will see information appear in the Upgrade Log portion of the
dialog. This helps you follow the upgrade progression.
4. After the upgrade is complete and the status shows 100%, the upgrade is installed.
5. If you chose not to auto reboot, manually reboot the system as described in “Rebooting the System”
on page 108.

BNP2xr User Guide 101

System Configuration

To Upgrade Software in a Redundant Chassis Environment

The steps for upgrading software in a redundant chassis environment are slightly different than in a
single chassis scenario. Follow the steps below if you have an active and standby chassis you wish to
upgrade (Figure 82 shows the Software Upgrade menu you will see with a redundant chassis):

Figure 82. Software Upgrade - Redundant chassis

1 Upgrade the Active chassis first

1. From the Maintenance -> Software Upgrade menu, enter the FTP Host, User Name, Password,
Directory and File Name.
2. Select the Both Active and Standby radio button.
3. Uncheck the Reboot chassis after successful software upgrade option.
4. Click the Upgrade button at the bottom of the screen.

2 Shutdown the Standby, then Active chassis next

1. Log into the Standby’s Element Manager via its Virtual IP address and use the Maintenance ->
System Shutdown menu to shutdown the system.
2. Log into the Active’s Element Manager via its Virtual IP address and use the Maintenance ->
System Shutdown menu to shutdown the system.

102 BNP2xr User Guide

 Clearing the Web Start Cache

3 Remove power from the Standby chassis

After shutting down the Standby through the Element Manager, wait one minute (or until the Fault
LED has stopped blinking) and unplug the power cord from the standby chassis.

4 Power cycle Active, then power on Standby chassis

1. Power cycle the active chassis.
2. Wait until the active chassis is accessible through the GUI and output streams are verified.
3. Replace power to the standby chassis and proceed with boot up.

Clearing the Web Start Cache

Any time that you downgrade software, you must clear the cache from the Java Web Start. Older
versions of the Element Manager use Web Start when the BNP Element Manager is started. This is
only needed when you change to a software version lower than the current one.
To clear the Java Web Start cache (on a Windows system):
1. From the Start Menu, select Settings -> Control Panel -> Java.
The Java Control Panel is launched.

Figure 83. Java control panel

BNP2xr User Guide 103

System Configuration

2. In the Temporary Internet Files section, click the Settings button.

The Temporary Files Settings screen appears.
3. Click Delete Files.
4. Ensure that the Application and Applets and Trace and Log Files boxes are checked.
5. Click OK to clear the cache and close the screen.

The License Manager

Overview
There are seven types of licenses for the BNP: Grooming with DPI, Grooming, Messaging System,
Advanced Overlay, Program with DPI, SPTS, and DVB-CA.

Note: The BNP2xr does not support DVB-CA; this feature is supported by the BNP3xr.

The standard Grooming with DPI license enables all product features including grooming, statistical
multiplexing, transrating, DPI (ad insertion), PSIP, all redundancy options, Gigabit Ethernet, and
SCTE 30-to-SCTE 35 conversion.

The Grooming license offers all features except DPI, with the option to add support for these features
with a DPI license upgrade at a later time.

The Messaging System license enables the use of integration with an external digital SCTE-18 EAS
server with the option for Operator-defined message alerts. The Messaging System license must be
used in conjunction with either the Grooming with DPI or the Grooming non-DPI license.

The Advanced Overlay license provides the ability to import external text or graphics for playout, as
well as static logo insertion. The Advanced Overlay license must be used in conjunction with either
the Grooming with DPI or the Grooming non-DPI license. You will also need a Messaging System
liense for the Advanced Overlay feature to work.

The Program with DPI license allows Digital Program Insertion on a per program basis. This license
is used in conjunction with the standard Grooming license and the SPTS license, which enable
grooming, statistical multiplexing, and transrating.

The SPTS license allows only a Single Program Transport Stream to be created on the output.
Functionality is the same as a standard MUX license, however, the creation of an MPTS on the output
is not allowed.

For the BNP3xr model, the DVB-CA license allows DVB Conditional Access on a per TS/MUX
bandwidth basis. This license is available in 4Mbps or 40Mbps increments, and is tracked at the TS
level.

104 BNP2xr User Guide

 The License Manager

Functionality
The determination of whether a transport stream and its bandwidth is assigned to a Grooming/DPI,
Grooming/non-DPI, or Messaging System license is made when you configure an output transport
stream. A transport stream can only be assigned to a license type after the license has been installed.
For more information on configuring various types of output transport streams, see the relevant
sections beginning on page 123 of Chapter 5, "Grooming and PSIP."

BNP licensing is based on the total bandwidth of output multiplexes where each Mux can be MPTS or
SPTS.

An associated license allows the creation of as many Mux or programs as will fit in the licensed
bandwidth. Example: A 40 Mbps Mux allows a MPTS with programs averaging at around 2.5 Mbps,
or 10 CBR SPTS programs at 4 Mbps.

All license keys are tied to the serial number of the compact flash card, which allows flash portability
and access to stored configurations.

Purchasing Licenses

The BNP will be shipped with a license key pre-loaded on the system.

To purchase an upgrade license, submit your request and PO to your reseller or to RGB if you
purchased the product directly. Your request will then be processed and a new license key will be sent
to you.

Please include the serial number of your compact flash card and the current number of licenses you
have for that particular system. RGB will issue a new license key that will be for the total number of
licenses for that system. For example, if you currently have a 4-Mux license (160 Mbps) for a single
BNP and you are ordering two more licenses for this system, RGB will issue a new license key for 6
Muxes (240 Mbps).

If purchasing licenses for multiple systems, you will need to indicate how many licenses per system
with the serial number of the compact flash of each system clearly indicated. RGB will then issue
separate license keys for each system.

Activating a License Key

Once you have received the license key, activate the license as follows:
1. From the main Element Manager menu, select Maintenance -> License.
2. Verify that the current information shown is correct.
3. In the New License Key field, enter the license key (Figure 84).

BNP2xr User Guide 105

System Configuration

Note: There is only one field in which to input a license key; this field is applicable to all types of
licenses.
j

Figure 84. The License Manager

4. Click Apply New License.

The new license is applied, and the updated information now appears in the License Manager.

Figure 84 shows the currently installed license key and Compact Flash ID (serial number).

Hardware Capacity Status

The License Manager also shows hardware capacity information—i.e. the maximum number of
licenses and bandwidth that the system can currently support based on the hardware installed. There
are three fields of information that display the bandwidth status for hardware capacity: Total Installed,
Available License, and Used License.

106 BNP2xr User Guide

 Regrooming

Total Installed shows the number of licenses residing in the compact flash and the resulting potential
bandwidth available in each license category. This number of licenses may exceed your current
hardware capability.

Available License will be based on either the installed licensed bandwidth or hardware capacity
bandwidth, which ever is less. This means that Used Bandwidth + Available Bandwidth will equal
either the Total Installed licensed bandwidth or the Hardware Capacity depending on which one is
lower.

Used License indicates the bandwidth actually in operation.

Flash Portability

One of the advantages of the BNP's licensing structure is flash portability. In the unlikely case that your
system suffers a catastrophic failure and you need to replace the hardware, remove the compact flash
from the old BNP chassis and install it into the new hardware. The new system should now operate just
like the old system as long as the hardware in the new system can support the same configuration. So,
if the failed system had two processor cards with two ASI cards, your new system would need to have
the same hardware to support the same configuration.

Regrooming
Regrooming lets you reset all of the programs that are currently configured in Program Redundancy to
their Active Programs. Once initiated, the command will check to see that the active program has been
restored. If the active program has not been not restored, no change will occur to the current state of the
program.

The Regrooming feature resets all programs with a properly detected primary program available. This
feature cannot be used to regroom a selected stream.

To reset all of the grooming to the active chassis:

1. From the main Element Manager menu, select Maintenance -> Regroom.
2. You are prompted to confirm that you want to reset the grooming. Click Apply regroom.

Figure 85. Apply regrooming

BNP2xr User Guide 107

System Configuration

Stopping All Services

Stopping all services is exactly that: all video services from the BNP are stopped.

Note: The only way to restart video services is to manually reboot the BNP, as described in
“Rebooting the System” on page 108.

1. From the main menu, choose, Maintenance -> System Shutdown.

2. You are prompted for confirmation. Click Yes to stop all video service, or No to cancel the process
and leave all video service running.

Figure 86. System Shutdown confirmation dialog

3. At the prompt, enter your password (Figure 87).

Figure 87. Password Verification Prompt

Note: If you have Administrator privilege, enter your administrator password. If you have Operator
privilege, enter that password. Only Administrators and Operators may shutdown the system.

4. Click OK to shutdown the system.

Note: A system shutdown will power down the BNP and will require a manual reboot of the chassis
in order to power up again.

Rebooting the System

Any time you load a new software image, you must reboot the system. When a power cycle or reboot
is performed, the BNP will retain previously saved configuration settings. Only the parameters of
newly introduced features need to be set when the system is upgraded and rebooted.

The BNP is rebooted using a power cycle or using the BNP Element Manager.

108 BNP2xr User Guide

 Rebooting the System

The BNP does not have a power switch. To power the unit down, disconnect the power cable from the
connector as described in “Replacing a Power Supply” on page 238. To reboot the switch from the
BNP Element Manager:
1. From the main menu, select Maintenance -> Reboot.
2. At the prompt, enter your password (Figure 88).

Figure 88. Password Verification Prompt

Note: If you have Administrator privilege, enter your administrator password. If you have Operator
privilege, enter that password. Only Administrators and Operators may reboot the system.

3. Click OK to proceed with the reboot.

4. The reboot confirmation screen appears, as shown in Figure 89.

Figure 89. Reboot dialog

5. Click Apply reboot.

6. To reboot other units, select the unit and repeat the procedure.

BNP2xr User Guide 109

System Configuration

Checking for the BNP Element Manager Version

To determine the currently installed version of the BNP Element Manager, from the main menu select
Help -> About.

Figure 90. About BNP dialog

110 BNP2xr User Guide

CHAPTER 5

Grooming and PSIP

This chapter describes how to perform grooming and Program and System Information Protocol
(PSIP) tasks on the BNP2xr, using the BNP Element Manager.

In This Chapter:
• “Before You Begin,” next.
• “Using the Mapping Tab” on page 112.
• “Creating Input Transport Streams” on page 119.
• “Managing Input Transport Streams” on page 121.
• “Creating MPEG-2 Output Transport Streams” on page 123.
• “Advanced Transport Stream Settings” on page 127.
• “Creating ATSC Output Transport Streams” on page 129.
• “Creating SCTE Output Transport Streams” on page 133.
• “Creating DVB Output Transport Streams” on page 135.
• “Creating a FAT ASI Port Output Transport Stream” on page 139.
• “Creating Programs” on page 144.
• “Modifying and Deleting Streams or Programs” on page 149.
• “Drag and Drop Grooming” on page 156.
• “Program Redundancy” on page 168.
• “Elementary Streams” on page 172.
• “Elementary Stream Ghost PID Management” on page 186.
• “Managing PMT and ES Descriptors” on page 196.
• “Monitoring Bitrates” on page 202.

Before You Begin

Before you begin performing grooming tasks, complete the general configuration described in Chapter
4, “System Configuration”.

Overview
The Element Manager’s Grooming tab has three subtabs from which you can perform mapping and
view bit rates. The tabs are: Mapping, Input Bitrate Monitor, and Input-Output Bitrate Monitor.
This chapter focusses on the functions in these subtabs.

BNP2xr User Guide 111

Grooming and PSIP

Using the Mapping Tab

The Grooming -> Mapping subtab allows you to:
• Create both input and output transport streams. See “Creating Input Transport Streams” on
page 119.
• Create an output program. See “Creating Output Programs Manually” on page 144.
• Perform drag and drop grooming on individual programs or full transport streams. See “Drag and
Drop Grooming” on page 156.
• Set your program schedule. See “Scheduling Grooming - One time event” on page 167.

To perform the procedures above, from the Element Manager, select Grooming -> Mapping. The
Mapping subtab window appears (Figure 91), displaying existing transport streams, program names,
and elementary streams for input on each appropriate port.

Output information appears only after there is output content. This can be achieved by either creating
an output transport stream or program, or by dragging and dropping input transport streams or
programs to the output.

All GigE ports are shown in the Inputs (left) portion of the window. Active ports are shown with a
green icon, and inactive ports are shown with a gray icon. These are the ports that you configured in
the configuration portion of the BNP as described in “GigE Port Configuration” on page 48.

112 BNP2xr User Guide

 Using the Mapping Tab

You create transport streams which are then picked up and put into the grooming window.

Transport stream

Table information

Program name

Elementary Streams

Figure 91. Grooming-Mapping configuration

Expand or collapse each “container” object (transport stream or program) by either double-clicking the
object or clicking the plus or minus sign to the left of the object name.

Each input transport stream has associated PSIP information where appropriate. Other types of
transport streams may show similar information.

Programs appear under the transport stream in which they arrive (or to which they are outputted), and
the elementary streams appear under the program. Each transport stream has an associated set of
programs and PSIP tables. Each program includes video, audio, and PSIP tables.

Viewing Program-Level Input Source

To view the input source of an output program, proceed as follows:

1. Right-click the desired program on the Outputs (right-hand) side of the screen (Figure 92).
2. From the pop-up box, select View Grooming Source.

BNP2xr User Guide 113

Grooming and PSIP

3. Observe the highlighted grooming source from the Inputs (left-hand) side of the screen (Figure 92).

Highlighted source

Figure 92. Viewing program-level input source

114 BNP2xr User Guide

 Using the Mapping Tab

Viewing ES-Level Input Source

To view the input source of an Elementary Stream (ES), proceed as follows:

1. Expand the desired program whose ES you wish to view on the Outputs (right-hand) side of the
screen (Figure 93).
2. Right-click the desired ES under the program on the Outputs (right-hand) side of the screen
(Figure 93).
3. From the pop-up box, select View Grooming Source.
4. Observe the highlighted grooming source from the Inputs (left-hand) side of the screen (Figure 93).

Highlighted source

Figure 93. Viewing ES-level input source

BNP2xr User Guide 115

Grooming and PSIP

Interpreting the Program Status Icons

All programs on both the Inputs and Outputs sides have program status icons associated with them,
which appear directly to the left of the word Program. These icons represent the program source.
Table 26 shows the name of each icon.

Table 26. Program Status Icons

Symbol Name

Network Program

Messaging Services Configured, Program Disabled

Messaging Services Configured and Program Enabled

Digital Program Insertion (DPI)

Messaging Services Configured with DPI

Encrypted Program

Inactive

116 BNP2xr User Guide

 Using the Mapping Tab

Interpreting Elementary Stream Status Icons

All Elementary Streams (ESs) on both the Inputs and Outputs sides have ES status icons associated
with them, which appear directly under the program when the view is expanded. Table 26 shows the
name of each icon.

Table 27. Elementary Stream Icons

Symbol ES Type Stream Type Description

MPEG2 2 (0x2)
Represents the presence of a video elementary stream
Video H.264 27 (0x1b)
on an input or output program.
SCTE 128 (0x80)
Represents the presence of an audio elementary stream
on an input or output programs.
Available audio options are:
None
MPEG1
Arabic
MPEG2
English
AC-3 (0x06)
French
Audio AC-3 (0x81)
German
AAC (0x0f)
Hindi
HE-AAC (0x11)
Italian
Japanese
Mandarin Chinese
Portuguese
Russian
Spanish
Represents the presence of a data elementary stream
5 with all stream types except:
6 Teletext 5 EBIF
6 Sub Title 5 EISS
Data
7 – 191 192 EBIF
192 192 EISS
193-255 A blue data stream icon can be displayed on either an
input or an output program.
5 EBIF Represents the presence of an EBIF or EISS data
5 EISS elementary stream with the following stream types:
Data
192 EBIF A blue data stream icon can be displayed on either an
192 EISS input or an output program.
Represents the presence of an ES-level groomed data
5 stream with all data stream types except:
6 Teletext 5 EBIF
6 Sub Title 5 EISS
Data
7 – 191 192 EBIF
192 192 EISS
193-255 A green data stream icon can only be displayed on an
output program.
5 EBIF Represents the presence of an ES-level groomed EBIF
5 EISS or EISS data stream:
Data
192 EBIF A green data stream icon can only be displayed on an
192 EISS output program.

BNP2xr User Guide 117

Grooming and PSIP

Expanding and Collapsing Mapping

You can expand and collapse the mapping views. Expanding and collapsing only affect the display;
they do not change the underlying grooming.

Figure 94 shows an example of existing mapping.

Figure 94. Existing Mapping

To collapse mapping, select View -> Collapse Mapping (Figure 95).

Figure 95. Collapse Mapping

118 BNP2xr User Guide

 Creating Input Transport Streams

To restore the expanded mapping view, choose View -> Expand Mapping. The expanded screen of
Figure 94 is restored.

Creating Input Transport Streams

The information required to create a transport stream (TS) depends on whether you are creating a
transport stream on an input port or an output port, and on the type of TS created. Each TS creation
dialog is described here.

Basic Input Transport Stream Creation

To create a new input transport stream:

1. From the Inputs side of the Grooming -> Mapping subtab, choose the input port on which you
want to create the transport stream and right-click.

2. From the pop-up menu that appears select Create Transport Stream.
3. Enter the information about the new input transport stream.

Figure 96. Create GigE Input TS

Table 28 desribes the fields available in the Create Input Transport Stream window.

Table 28. Input Transport Stream Creation

Input Transport Stream Description

GigE Port This is the read-only port ID, and is based on the selected GigE port (GigE 1,
GigE 2, etc.)
TS Name Enter the desired name of the transport stream.
Multicast If this is a multicast stream, check this box to enable multicast.

BNP2xr User Guide 119

Grooming and PSIP

Table 28. Input Transport Stream Creation

Input Transport Stream Description

IP Address The unicast or multicast IP address on which the stream is received.
UDP Port Enter the UDP port to use for transmitting data.
Source IP Address The IP address of the source from which the stream is originating; the source IP
address is optional and should only be included for IGMPv3/SSM transport
streams.
Multiple TS Click this button if you are creating multiple transport streams. You can create
incrementing IP addresses, incrementing UDP ports, or incrementing IP
Addresses and UDP ports simultaneously. See the following paragraphs for
details.

Multiple IP and UDP Creation

If you have chosen to create multiple transport streams, clicking Multiple TS opens the Select
Multiple IP and UDP dialog.

Figure 97. Selecting multiple UDP/IP ports

Table 29. Selecting Multiple IP and UDP

Field Description
Start IP Address A read-only field indicating the starting IP address.
End IP Address A read-only field indicating the ending IP address.
Start UDP A read-only field indicating the starting UDP port number.
End UDP A read-only field indicating the ending UDP port number.
Increment IP Address When checked, the starting IP address will be incremented by one for each
multiple chosen.
Increment UDP When chosen, the UDP port number will be incremented by one for each
multiple chosen.
Increment both IP Address When checked both the IP address and UDP port number will be
and UDP incremented by one for each multiple chosen.
Multiple Number The number of multiple creations, either or both, IPs or UDPs.
Excluded UDP Ports UDP ports that you want excluded from any automatic numbering.

120 BNP2xr User Guide

 Managing Input Transport Streams

1. Choose to increment only the IP address, UDP port, or both simultaneously.

2. Enter the number of multiple creations desired.
3. If you have chosen either UDP or Both, enter any UDP ports to exclude, separated by commas.
4. Click OK to apply the selections and return to the creation window.

Figure 98 shows transport streams configured under a GigE input port:

Figure 98. Input Transport Streams created

Note: Each TSID is a unique number used to identify a transport stream. It is a partition of two 16-
bit hex numbers. The lower 16 bits is the MPEG transport stream ID. The upper 16 bits (0x) is
used strictly internally.

Note: There are no configuration parameters required for creating a transport stream on an input
ASI port. Each input ASI port is automatically configured with one transport stream.

Managing Input Transport Streams

After an input transport stream has been created, various options are available for managing the
stream. The options are slightly different based on whether or not you have selected a GigE port
transport stream or an ASI port transport stream.

GigE Port Transport Stream Options

To view available options for a GigE port, proceed as follows:

1. From the Inputs side of the Grooming -> Mapping window, select a desired transport stream
under a GigE port.
2. Right-click on the transport stream.

BNP2xr User Guide 121

Grooming and PSIP

3. A pop-up menu will appear as follows:

Figure 99. Input Transport Stream pop-up menu - GigE

Table 30 describes the options available from the pop-up menu.

ASI Port Transport Stream Options

To view available options for an ASI port, proceed as follows:

1. From the Inputs side of the Grooming -> Mapping window, select a desired transport stream
under an ASI port.
2. Right-click on the transport stream.
3. The following pop-up menu will appear:

Figure 100. Input Transport Stream pop-up menu - ASI

Table 30 describes the options available from the pop-up menu.

Table 30. Input Transport Stream pop-up menu options

Menu Description
Modify Transport Stream Allows you to modify only the name of the transport stream. If
you wish to modify any other parameter, you must delete the
transport stream and create it again.
Refresh Transport Stream Tables When this option is selected, the internal Program Association
Table (PAT) for this transport stream is invalidated, and the
next incoming PAT will be used for the associated PSIP and
DVB tables for selected transport stream.

122 BNP2xr User Guide

 Creating MPEG-2 Output Transport Streams

Table 30. Input Transport Stream pop-up menu options

Menu Description
Delete Transport Stream (GigE only) Deletes the transport stream and all grooming for associated
output programs.
• Option available for GigE port transport streams only
Recreate Input Transport Stream (ASI only) Deletes the transport stream, all grooming for associated
output programs, and recreates the transport stream with no
associated grooming.
• Option available for ASI port transport streams only
Create Ghost Program Used for created programs with unreferenced PIDs. See
“Adding an Unreferenced PID as an Elementary Stream” on
page 183 for details.
Bitrate Monitor Allows you to monitor bitrates for the selected transport
stream.

Creating MPEG-2 Output Transport Streams

To create a new MPEG-2 output transport stream:
1. From the Outputs side of the Grooming -> Mapping subtab, choose the outport port on which you
wish to create the transport stream and right-click.

2. From the pop-up menu that appears select Create Transport Stream.
The screen will be different if the output port is an ASI (Figure 101) or a GigE port (Figure 102).
3. From the TS Type pull down menu, select MPEG-2.
4. Fill out the remaining fields of the dialog according to the parameters listed in Table 31 or Table 32,
depending on which port is in use.
5. Click OK to save changes and create the transport stream.
The stream now appears in the Grooming -> Mapping window and can be assigned programs.

BNP2xr User Guide 123

Grooming and PSIP

ASI Port MPEG-2 Transport Streams

Figure 101 shows the Create Output Transport Stream window for an ASI port.

Figure 101. Creating output TS (MPEG-2, ASI port)

Table 31. MPEG-2 Output Transport Stream Creation (ASI Port)

Field Description
Port Read-only, shows either ASI or GigE depending on the port selected.
SPTS Check if the output is a single program transport stream (SPTS).
Non-DPI Check this box if the transport stream is to use a Grooming-only (Non-DPI)
license.
TS Name The (optional) name you want to assign to this output transport stream.
Bitrate (Mbps) The bitrate at which the stream is transported.
Unique TS ID Allows you to assign a unique numeric ID to this transport stream.
• When this option is checked, the TS ID value placed in this field will be
reserved as unique for the entire chassis.
• When this option is unchecked, a TS ID value may still be entered,
however the value may be the same as another TS ID as long as that TS
ID’s value has not been reserved as a Unique TS ID.
• Note that each TSID is a unique number used to identify a transport
stream. It is a partition of two 16-bit hex numbers. The lower 16 bits (user-
specified in decimal and converted to hex) is the MPEG transport stream
ID. The upper 16 bits (0x) is strictly used internally.
• Default value is “1” if no value is specified.
• Broadcasters must configure this value with a unique ID to meet FCC
standards.
Reserved Bandwidth Enter any bandwidth value to be reserved from the total bitrate of transport
stream.
Network PID The program ID on which network information is received.
TS Type The type of stream. The type of stream you choose determines what other
information is required. Choices are:
MPEG-2, ATSC, SCTE, or DVB

124 BNP2xr User Guide

 Creating MPEG-2 Output Transport Streams

Table 31. MPEG-2 Output Transport Stream Creation (ASI Port)

Field Description
Enable Messaging System Check this box to allow configuration of Messaging System zones for specific
programs in this transport stream. See “Messaging System Configuration” on
page 65 for information on configuring Messaging Zones.
Advanced Setting Clicking this button will open a new menu that allows you to configure
advanced settings for the selected transport stream. See “Advanced
Transport Stream Settings” on page 127.

GigE Port MPEG-2 Transport Streams

Figure 102 shows the window for a GigE port.

Figure 102. Creating output TS (MPEG-2) - GigE port)

Table 32 describes the parameters fields available in the MPEG-2 Create Output Transport Stream
dialog.

Table 32. MPEG-2 Output Transport Stream Creation (MPEG-2, GigE Port)

Field Description
Port This is read-only and is used for identification purposes.
SPTS Check if the output is a single program transport stream (SPTS).
Non-DPI Check this box if the transport stream is to use a Grooming-only (Non-DPI)
license.
Multicast Check if the output is for multicast operation.
Bitrate (Mbps) The bitrate at which the stream is transported.
Destination IP The IP address to which the output stream is routed.
• If Multicast is checked, this must be a valid multicast IP address.
• If Multicast is unchecked, this must be a valid unicast IP address.
Reserved Bandwidth (Mbps) Enter any bandwidth value to be reserved from the total bitrate of transport
stream.

BNP2xr User Guide 125

Grooming and PSIP

Table 32. MPEG-2 Output Transport Stream Creation (MPEG-2, GigE Port) (Continued)

Field Description
UDP Port Enter the UDP port to use for transmitting data.
TS Name The (optional) name you want to assign to this output transport stream.
Subnet Mask If Multicast is unchecked, enter the subnet mask IP for the unicast IP address
entered in the Destination IP field.
Unique TS ID Allows you to assign a unique numeric ID to this transport stream.
• When this option is checked, the TS ID value placed in this field will be
reserved as unique for the entire chassis.
• When this option is unchecked, a TS ID value may still be entered,
however the value may be the same as another TS ID as long as that TS
ID’s value has not been reserved as a Unique TS ID.
• Note that each TSID is a unique number used to identify a transport
stream. It is a partition of two 16-bit hex numbers. The lower 16 bits (user-
specified in decimal and converted to hex) is the MPEG transport stream
ID. The upper 16 bits (0x) is strictly used internally.
• Default value is “1” if no value is specified.
• Broadcasters must configure this value with a unique ID to meet FCC
standards.
ARP If Multicast is checked, this field is hidden.
If Multicast is unchecked, this box will appear. Unchecking this box will allow
you to disable the use of Address Resolution Protocol (ARP) and to manually
specify a MAC address. See Figure 103.
Network PID The program ID of transport stream packets which contain the network
information table.
MAC Address If Multicast or ARP are checked, this field is read-only.
If Multicast and ARP are unchecked, this field can be modified to include a
hardcoded MAC address to be used to transport this stream. See Figure 103.
TS Type The type of stream. The type of stream you choose determines what other
information is required. Choices are:
MPEG-2, ATSC, SCTE, or DVB.
Multiple TS Click if multiple transport streams are used. See “Multiple IP and UDP
Creation” on page 120 for details.
Enable Messaging System Check this box to allow configuration of Messaging System zones for specific
programs in this transport stream. See “Messaging System Configuration” on
page 65 for information on configuring Messaging Zones.
Advanced Setting Clicking this button will open a new menu that allows you to configure
advanced settings for the selected transport stream. See “Advanced
Transport Stream Settings” on page 127.

126 BNP2xr User Guide

 Advanced Transport Stream Settings

Hidden Fields in Create Output Transport Stream Menu (GigE)

The Create Output Transport Stream menu hides the ARP field when the Multicast box is checked.
Figure 103 shows an example of the ARP field (checked and unchecked) as described in Table 32.

Figure 103. Create Output TS - ARP field

Advanced Transport Stream Settings

The Advanced Setting button from the Create Transport Stream menu provides the following
additional configuration options when creating an output transport stream:

SPTS Advanced Options

Note: These options only apply when configuring a single program transport stream (SPTS) from the
Create Transport Stream window (Figure 101 or Figure 102)

SPTS MPEG-2 Advance Rate Control

This is an MPEG-2 transrating setting for SPTS output transport streams that require more aggressive
rate control due to severe oscillations from the input bitrate.

BNP2xr User Guide 127

Grooming and PSIP

To enable MPEG-2 Advance Rate Control, proceed as follows:

1. From the Create Transport Stream menu, click the Advanced Setting button.
The Advanced Transport Stream Setting window of Figure 104 is displayed.

Figure 104. Advanced Transport Stream - SPTS

2. Check the box next to MPEG-2 Advance Rate Control.

3. Click OK.

MPTS Advanced Options

Note: These options only apply when configuring multiple program transport streams (MPTSs) from
the Create Transport Stream window (Figure 101 or Figure 102)

H.264 Alarm Bitrate Level

This setting can assist in maintaining video quality for MPEG-2 video content in the presence of other
content, such as H.264, which bypasses the BNP’s transrater. This is done by generating an alarm
when H.264 program bandwidth exceeds the percent of the TS bandwidth specified in this setting.

To set the H.264 Alarm Bitrate Level, proceed as follows:

1. From the Create Transport Stream menu, ensure the SPTS option is not checked.

128 BNP2xr User Guide

 Creating ATSC Output Transport Streams

2. Click the Advanced Setting button.

The Advanced Transport Stream Setting window of Figure 105 is displayed.

Figure 105. Advance Transport Stream Setting - MPTS

3. Enter a percent of the the transport stream’s aggregate bandwidth at which an alarm should be
generated. Choices are: 0%, 25%, 50%, 75%, 100%.
4. Click OK.

Table 33 provides a summary of the Advanced Transport Stream Setting window parameters.

Table 33. Advanced Transport Stream Settings

Field Description
SPTS: MPEG-2 Advance Rate Control When checked, the output SPTS is aggressively rate controlled.
MPTS: H.264 Alarm Bitrate Level (Mbps) Specify the percent at which an alarm will be issued when H.264
program bandwidth of the MPTS TS exceeds this level. By
default this rate is set to 50% of the aggregate rate of the entire
transport stream.

Creating ATSC Output Transport Streams

If the selected output transport stream is an ATSC type, additional information is necessary. The upper
portion of the dialog is the same as that of the MPEG-2 type and are described in Table 31 for an ASI
port and Table 32 for a GigE port.

To create a new ATSC output transport stream:

1. From the Outputs side of the Grooming -> Mapping subtab, choose the outport port on which you
want to create the transport stream and right-click.

2. From the pop-up menu that appears select Create Transport Stream.
The screen will be different if the output port is an ASI or a GigE port.

BNP2xr User Guide 129

Grooming and PSIP

3. From the TS Type pull down menu, select ATSC.

The lower portion of both ASI and GigE port screens is used to define the PSIP tables. PSIP tables
are described in Table 34.
4. Fill out the remaining fields of the dialog according to the parameters listed in Table 31 or Table 32,
depending on which port is in use.
5. Click OK to save changes and create the transport stream.
The stream now appears in the Grooming -> Mapping window and can be assigned programs.

Figure 106 shows the window for an ATSC transport stream on an ASI port.

Figure 106. Create Output TS (ATSC) - ASI Port

130 BNP2xr User Guide

 Creating ATSC Output Transport Streams

Figure 107 shows the window for an ATSC transport stream on a GigE port.

PSIP table fields

Figure 107. Creating output TS (ATSC) - GigE Port

Table 34 provides a description of the additional PSIP fields in the bottom portion of the Create
Output Transport Stream window for an ATSC stream on either an ASI or GigE port.

Table 34. ATSC TS Creation: PSIP Table Information Configuration Parameters

PSIP Table Informationa Description

For an ASI port, all fields in the top portion of the Create Output Transport Stream window are the same as
described in Table 31.
For a GigE port, all fields in the top portion of the Create Output Transport Stream window are the same as
described in Table 32.
For ATSC transport types, you must include the information about PSIP tables. The PID values of major and
minor channels are automatically numbered across the multiplex, reducing the chance of conflict.
EIT PID (0-3) The Event Information Table (EIT) packet identifier (PID) values can be set
manually, overriding the PID in the MGT.
EIT PID Interval(ms) This value can be set manually, overriding the PID in the MGT. Value in
milliseconds.

BNP2xr User Guide 131

Grooming and PSIP

Table 34. ATSC TS Creation: PSIP Table Information Configuration Parameters (Continued)

PSIP Table Informationa Description

MGT Interval(ms) The Master Guide Table (MGT) is highest order in the ATSC transport stream
table hierarchy; it also provides program-identification (PID) locations so that
receivers can locate other tables; the MGT can also inform the receiver of
changes or table updates.
Modulation Mode Choose one of the following modes from the pull-down menu:
Analog, SCTE 64 QAM, SCTE 256 QAM, ATSC 8 VSB, and ATSC 16 VSB.
Generate TVCT Check this box to generate TVCT tables instead of CVCT tables. A
Terrestrial Virtual Channel Table (TVCT) is a mandatory PSIP table for
terrestrial broadcast that lists all the virtual channels available in an ATSC
transport stream. This feature is required for broadcasted channels.
• When Modulation Mode is set to ATSC 8 VSB or ATSC 16 VSB, you must
enable this option.
CVCT/TVCT Interval(ms) Specifies the interval in milliseconds at which CVCT/TVCT tables are
generated. If the Generate TVCT option has been enabled, this field sets the
interval for TVCT; if the Generate TVCT option has not been enabled, this
field sets the interval for CVCT.
The Cable Virtual Channel Table (CVCT) provides information about the
channels, such as channel name, navigation identifier, and stream
components.
STT Source The System Time Table (STT) defines the GPS time and the daylight-savings
time indicator to the consumer’s decoder, synchronizing the concept of "now"
between the decoder and the broadcaster. This configuration is not
generated by the BNP and requires a proper source to be valid on the output
transport.
Choose an appropriate value from the pull-down menu. There must be a
valid STT source to be ATSC compliant.
EIT Source Specifies how an EIT table is generated by the BNP.
When Groomed Input (default) is selected, an Event Information Table (EIT)
is generated based on that which is received from the groomed input
program of the ATSC TS.
Choose an appropriate value from the pull-down menu.
RRT Source The Rating Region Table (RRT) source transmits the program rating
information
Choose an appropriate value from the pull-down menu. There must be a
valid RRT source to be ATSC compliant.
a. PSIP (Program and System Information Protocol) is a collection of tables operating within the terrestrial broadcast Trans-
port Stream (TS) of every digital (and sometimes analog) television. PSIP settings are configured as part of the transport
stream.

These tables contain system information and program data:

- System information allows navigation and access of the channels within the DTV transport stream.
- Program data provides necessary information for efficient browsing and event selection.
- Some PSIP tables contain the information to locate digital streams.

If you are not sure of the PSIP guidelines, there are many good references on the Internet, including the ATSC Recom-
mended Practice: Program and System Information Protocol Implementation Guidelines for Broadcasters at http://
www.atsc.org/standards/a_69.pdf

132 BNP2xr User Guide

 Creating SCTE Output Transport Streams

Creating SCTE Output Transport Streams

If the selected output transport stream is an SCTE type, the configurable parameters are the same as
that of the MPEG-2 type and are described in Table 31 for an ASI port and Table 32 for a GigE port.

To create a new SCTE output transport stream:

1. From the Outputs side of the Grooming -> Mapping subtab, choose the outport port on which you
want to create the transport stream and right-click.

2. From the pop-up menu that appears select Create Transport Stream.
The screen will be different if the output port is a GigE or an ASI port.
3. From the TS Type pull down menu, select SCTE.
4. Fill out the remaining fields of the dialog according to the parameters listed in Table 31 or Table 32,
depending on which port is in use.
5. Click OK to save changes and create the transport stream.
The stream now appears in the Grooming -> Mapping window and can be assigned programs.

Figure 108 shows the window for an SCTE transport stream on an ASI port.

Figure 108. Creating output TS (SCTE) - ASI port

BNP2xr User Guide 133

Grooming and PSIP

Figure 108 shows the window for an SCTE transport stream on a GigE port.

Figure 109. Creating output TS (SCTE) - GigE port

134 BNP2xr User Guide

 Creating DVB Output Transport Streams

Creating DVB Output Transport Streams

If the selected output transport stream is a DVB type, additional information is necessary. The upper
portion of the dialog is the same as that of the MPEG-2 type and are described in Table 31 for an ASI
port and Table 32 for a GigE port.

To create a new DVB output transport stream:

1. From the Outputs side of the Grooming -> Mapping subtab, choose the outport port on which you
want to create the transport stream and right-click.

2. From the pop-up menu that appears select Create Transport Stream.
The screen will be different if the output port is a GigE or an ASI port.
3. From the TS Type pull down menu, select DVB.
The lower portion of both ASI and GigE port screens is used to define additional information
relative to Digital Video Broadcast (DVB) and is described in Table 35.
4. Fill out the remaining fields of the dialog according to the parameters listed in Table 31 or Table 32,
depending on which port is in use.
5. Click OK to save changes and create the transport stream.
The stream now appears in the Grooming -> Mapping window and can be assigned programs.

Table 110 shows the window for a DVB transport stream on an ASI port.

Figure 110. Creating output TS (DVB) - ASI port

BNP2xr User Guide 135

Grooming and PSIP

Figure 111 shows the window for a DVB transport stream on a GigE port.

Figure 111. Creating output TS (DVB) - GigE port

136 BNP2xr User Guide

 Creating DVB Output Transport Streams

Table 35 provides a description of the additional fields in the bottom portion of the Create Output
Transport Stream window for a DVB stream on either an ASI or GigE port.

Table 35. DVB Output Transport Stream Configuration Parameters

Field Description
For an ASI port, all fields in the top portion of the Create Output Transport Stream window are the same as
described in Table 31.
For a GigE port, all fields in the top portion of the Create Output Transport Stream window are the same as
described in Table 32.
Network ID Input the Network ID of the current transport stream.
Modulation Mode Use the pull-down menu to select the modulation mode used for the TS.
Choice between SCTE 64 QAM and SCTE 256 QAM.
Original Network ID Input the Network ID from which this stream has originated.
NIT Source Use the pull-down menu to select the source for the network information
table.
TDT/TOT Source Use the pull-down menu to select the source for the time and date table or
the time offset table.
SDT Source Source of the service description table for this transport stream. If you select
N/A then SDT is not generated for this output TS.
EIT Source Source of the Event Information Tabled (EIT) for the programs in this
transport stream. If you select N/A then EIT will not be generated.

Setting Up Network Information Tables (NIT) for DVB

You can generate a NIT table using one of three methods:
• Locally generated, using the NIT editor
• NIT pass through, with editing at the output transport stream.
• Complete pass through of NIT from the input to the output transport stream.

BNP2xr User Guide 137

Grooming and PSIP

This manual describes the first method.

To set up a NIT:
1. From the main Element Manager menu, select Maintenance -> Setup Network Information
Table (NIT).
2. In the NIT window that appears, click Add to add a new NIT or Edit to edit an existing NIT. The
Setup Network Information Table (NIT) appears (Figure 112).

Figure 112. Setup Network Information Table screen

138 BNP2xr User Guide

 Creating a FAT ASI Port Output Transport Stream

3. Highlight an existing table, and choose Edit. The window of Figure 113 appears.

Figure 113. Using the Editing Feature

4. Edit the Network Information Table as described in Appendix A, “Editing the DVB NIT Table”.
5. When you are finished editing, click OK to apply any changes.
6. To view the NIT as an XML file, click View NIT in XML format.
7. To import the NIT from another BNP, click Import NIT File.

Creating a FAT ASI Port Output Transport Stream

You can create a FAT ASI port with up to four groups. Proceed as follows:

BNP2xr User Guide 139

Grooming and PSIP

1. Right click the ASI port on which to create a FAT ASI port (Figure 114).

Figure 114. Choosing a FAT ASI Transport Stream

2. Choose Create Transport Stream (FAT ASI). The window of Figure 115 appears.

Figure 115. Create Output Transport Stream (FAT ASI)

140 BNP2xr User Guide

 Creating a FAT ASI Port Output Transport Stream

3. Enter the value of each parameter as described in Table 36.

Table 36. Creating a FAT ASI Transport Stream

Field Description
Port Read-only, shows either ASI or GigE depending on the port selected.
Non-DPI Check this box if the transport stream is to use a Grooming-only (Non-DPI)
license.
TS Name The (optional) name you want to assign to this output transport stream.
Bitrate (Mbps) The bitrate at which the stream is transported.
Unique TS ID Allows you to assign a unique numeric ID to this transport stream.
• When this option is checked, the TS ID value placed in this field will be
reserved as unique for the entire chassis.
• When this option is unchecked, a TS ID value may still be entered,
however the value may be the same as another TS ID as long as that TS
ID’s value has not been reserved as a Unique TS ID.
• Note that each TSID is a unique number used to identify a transport
stream. It is a partition of two 16-bit hex numbers. The lower 16 bits (user-
specified in decimal and converted to hex) is the MPEG transport stream
ID. The upper 16 bits (0x) is strictly used internally.
• Default value is “1” if no value is specified.
• Broadcasters must configure this value with a unique ID to meet FCC
standards.
Reserved B/W (Mbps) Enter any bandwidth value to be apportioned to the transport stream.
Network PID The program ID on which the stream is received.
TS Type The type of stream. The type of stream you choose determines what other
information is required. Choices are:
MPEG-2, ATSC, SCTE, or DVB
• For information on additional fields for ATSC transport streams, see
Table 34.
• For information on additional fields for DVB transport streams, see
Table 35.
Enable Messaging System Check this box to allow configuration of Messaging System zones for specific
programs in this transport stream. See “Messaging System Configuration” on
page 65 for information on configuring Messaging Zones.
Number of Group The number of groups you want to assign to this port. Choose from 1 to 4.
The default is 4.
Group Name (A-D) The name you want to assign to each group.
Group Bitrate(Mbps) The bitrate, in megabits per second, that you want to assign to groups. The
(A-D) value entered will be applied to all Groups. The total bitrate for all groups
cannot exceed the value in the Bitrate field in the top portion of the window.
Reserved B/W (Mbps) The reserved bandwidth you want to assign for each group. The total
bandwidth for all groups cannot exceed the value in the Reserved B/W field
in the top portion of the window.
Advanced Setting Clicking this button will open a new menu that allows you to confiigure
advanced settings for the selected FAT ASI transport stream. See “Advanced
FAT ASI Transport Stream Settings” on page 142.

BNP2xr User Guide 141

Grooming and PSIP

4. When you are done click OK. Figure 116 shows the result.

Figure 116. FAT ASI Ports Created

Advanced FAT ASI Transport Stream Settings

The Advanced Setting button from the Create Transport Stream (FAT ASI) menu provides the
following additional configuration option when creating a FAT ASI transport stream:

ASI Group H.264 Alarm Bitrate Level

This setting can assist in maintaining video quality for MPEG-2 video content in the presence of other
content, such as H.264, which bypasses the BNP’s transrater. This is done by generating an alarm
when H.264 program bandwidth exceeds the percent of the TS bandwidth specified in this setting.

To set the each group’s H.264 Alarm Bitrate Level, proceed as follows:

142 BNP2xr User Guide

 Creating a FAT ASI Port Output Transport Stream

1. From the Create Transport Stream menu, click the Advanced Setting button.
The Advanced Transport Stream Setting window of Figure 117 is displayed.

Figure 117. FAT ASI - Advance Transport Stream Setting

2. Enter a percent of the transport stream’s aggregate bandwidth at which an alarm should be
generated for each group in the FAT ASI stream. Choices are: 0%, 25%, 50%, 75%, 100%.
3. Click OK.

BNP2xr User Guide 143

Grooming and PSIP

Creating Programs
An input program cannot be created; it must be autodetected from the GigE or ASI port. The only type
of input program that can be manually created is a Ghost Program. See “Elementary Streams” on
page 172 for more information on Ghost Programs.

You can create output programs in one of two ways: manually or by drag and drop grooming. For
either method, the program mapping configuration is the same. You can also schedule programs by
either manual or drag and drop methods.

Creating Output Programs Manually

To create a program manually, follow this procedure:

1. From the outputs side of the Element Manager’s Grooming -> Mapping subtab, select or create
the transport stream under which the new program will appear.

2. Right-click the transport stream name.

Figure 118. Create Output Program popup

3. Select Create Program.

The Create Output Program dialog appears.
The image on the left displays the default Create Output Program dialog when the PIDs Priority
setting is configured for Ad. The image on the right displays the default Create Output Program
dialog when the PIDs Priority setting is configured for Network.

144 BNP2xr User Guide

 Creating Programs

PIDs Priority set to Ad PIDs Priority set to Network

Figure 119. Create Output Program dialog

4. Enter all of the information for the program. Some fields will be read-only.

BNP2xr User Guide 145

Grooming and PSIP

Table 37 describes the fields available in the Create Output Program dialog for manual creation.

Table 37. Create Output Program Configuration Parameters

Category Field Description

Port Port ID Read-only field. The GigE or ASI port on which the program
resides.
IP Address Read-only field. The destination IP address of the transport
stream.
UDP Port Read-only field. UDP port the program uses, based on UDP
port of the transport stream.
TS TS ID Read-only field. The ID number of the transport stream on
which this program streams.
TS Type Read-only field. Indicates the type of transport stream for the
program.
Program / Channel Program Number MPEG number assigned to this program
Info Program Name Name assigned to this program. Output program names
must be unique.
PMT PID Select this option to activate the PMT ID box, into which you
can then enter the PMT ID, or the ID of the program map
table (PMT)
Major Channel Operator-defined channel number: for terrestrial broadcast,
Number the major channel number is limited to the range 1 to 99 for
ATSC digital television or audio services. For cable, major
channel numbers may range from 1 to 999. Only editable
when ATSC is enabled.
Minor Channel Operator-defined minor channel number: any whole number
Number in the range from 0 to 999. Only editable when ATSC is
enabled.
Enable DPIa Select this option to enable DPI for the program only, rather
than the whole TS.
• This option is hidden unless a PROGRAM WITH DPI
license key has been entered in The License Manager.
Allow SCTE 30- to- When checked, enables SCTE 30 to SCTE 35 conversion.
SCTE 35 conversion

146 BNP2xr User Guide

 Creating Programs

Table 37. Create Output Program Configuration Parameters (Continued)

Category Field Description

ETV Configurationb ETV PIDs Priority Indicates the source of EBIF ES data for the duration of the
ad time and provides the option to replace or not replace the
EBIF ESs during ad splicing.
• When Ad is selected, the spliced ad will provide the EBIF
and EISS elementary streams (ESs). If the EBIF and EISS
ESs from the ad do not match the stream type and
descriptors of the network EBIF and EISS ESs, then the
network EBIF and EISS ESs will be dropped. If no EBIF
and EISS data are pre-configured at the output program
or no EBIF and EISS data are present at the output then
the EBIF and EISS ESs form the ad are dropped.
• When Network is selected, the EBIF and EISS ESs from
the ad server will be ignored, even if they are present.
Default is set to Ad.
Play Preference When the ETV PIDs Priority is set to Network, the following
three options will appear in a drop down box:
• Play through ad: any EBIF ES data that is part of the
output program will continue to be played during the ad.
• Drop during ad: any EBIF ES data that is part of the output
program will be dropped during the ad.
• Play during ad only: provides the ability to select the input
EBIF ES source that will be playing only during the ad
time; if an EBIF ES source is not available, the EBIF ES
that currently exists in the output program will be played.
Default setting is Play through ad.
Late-Bind Source This option is only available when the ETV PIDs Priority is
set to Network and the Play Preference is set to Play during
ad only.
• When the above two conditions have been met, an
additional field with ellipses (. . .) will appear. Clicking on
the ellipses will open the Late-Bind Source Dialog window,
which will allow the option to choose a valid pair of EBIF/
EISS ES from the BNP’s input.
Messaging System Messaging System Click this button to open the Program Messaging System
Setting Setting window to configure and enable messaging zones
for the program. See “Program Messaging System Setting,”
below for details.
a. A GROOMING WITH DPI license key (which enables DPI for the TS) cannot co-exist with a PROGRAM WITH DPI
license key.
b. For additional information in ETV configuration including details on various EBIF and EISS use cases, see Chapter 7,
"ETV Binary Interchange Format (EBIF)."

5. Click OK to save the changes and create the program.

Program Messaging System Setting

When the Messaging System Setting button from the Create Output Program menu is clicked, the
Program Messaging System Setting window will open (Figure 120).

BNP2xr User Guide 147

Grooming and PSIP

This setting allows you to configure and enable one of each of the three types of Messaging Zones per
program.

Figure 120. Program Messaging System Setting window

Note: In order to select a zone from each of the three types of zone choices in the Program
Messaging System Setting window, the zones must first be created from the Configuration ->
Messaging System menu as described in “Messaging System Configuration” on page 65 in
Chapter 4.

You may select one of each zone type to configure and enable per program. Only previously created
zones will appear in the drop-down menu. Table 38 describes the fields available in the Program
Messaging System Setting window.

Table 38. Messaging System Setting window

Field Description
EAS Zone Select an EAS zone from the pull-down menu to associate with the
program. See “EAS Messaging Zones” on page 66 in Chapter 4
for additional information.
Click the Enable Zone button next to the selection to enable the
EAS messaging zone for the specified program.
Operator Messaging Zone Select an Operator or Advanced Messaging zone from the pull-
down menu to associate with the program. See “Operator and
Advanced Messaging Zones” on page 72 in Chapter 4 for
additional information.
Click the Enable Zone button next to the selection to enable the
Operator or Advanced Messaging zone for the specified program.
Logo Overlay Zone Select a Logo Overlay zone from the pull-down menu to associate
with the program. See “Logo Overlay Zones” on page 85 in
Chapter 4 for additional information.
Click the Enable Zone button next to the selection to enable the
Logo Overlay zone for the specified program.

148 BNP2xr User Guide

 Modifying and Deleting Streams or Programs

Modifying and Deleting Streams or Programs

Modifying Streams or Programs

If a transport stream or a program configuration needs to be modified, use the main Grooming ->
Mapping window to access the change options:

Modifying Input Transport Streams

The only item that can be modified on an input transport stream is the TS Name.
1. From the inputs side of the Grooming -> Mapping window, select the transport stream that
requires a name change.
2. Right-click on the TS and choose Modify Transport Stream from the popup menu.
The menu to modify an input TS on a GigE port will be similar to Figure 121.

Figure 121. Modify Input TS - GigE port

The menu to modify an input TS on an ASI port will be similar to Figure 122.

Figure 122. Modify Input TS - ASI port.

3. Enter a new name in the TS Name field.

4. Click OK to save changes.

BNP2xr User Guide 149

Grooming and PSIP

Modifying Output Transport Streams - GigE

The fields that can be modified on a GigE output transport stream for all TS Types are as follows:
• TS Name
• Multicast
• Destination IP
• UDP Port
• Subnet Mask
• ARP
• MAC Address
• Enable Message System

The following additional fields may be modified for an ATSC transport stream:
• Generate TVCT
• STT Source
• EIT Source
• RRT Source

The following additional fields may be modified for a DVB transport stream:
• Network ID
• Original Network ID
• NIT Source
• TDT/TOT Source
• SDT Source
• EIT Source

To modify a GigE transport stream, proceed as follows:

1. From the outputs side of the Grooming -> Mapping window, select the GigE transport stream that
requires modification.

150 BNP2xr User Guide

 Modifying and Deleting Streams or Programs

2. Right-click on the TS and choose Modify Transport Stream from the popup menu.
The menu to modify an input TS on a GigE port will be similar to Figure 123.

Figure 123. Modify Output TS - GigE port

3. Make any desired modifications to the editable fields.

4. Click OK to save changes.

Modifying Output Transport Streams - ASI

The fields that can be modified on an ASI output transport stream for all TS Types are as follows:
• TS Name
• Enable Message System

The following additional fields may be modified for an ATSC transport stream:
• Generate TVCT
• STT Source
• EIT Source
• RRT Source

The following additional fields may be modified for a DVB transport stream:
• Network ID
• Original Network ID
• NIT Source
• TDT/TOT Source
• SDT Source
• EIT Source

To modify an ASI transport stream, proceed as follows:

BNP2xr User Guide 151

Grooming and PSIP

1. From the inputs side of the Grooming -> Mapping window, select the ASI transport stream that
requires modification.
2. Right-click on the TS and choose Modify Transport Stream from the popup menu.
The menu to modify an output TS on an ASI port will be similar to Figure 124.

Figure 124. Modify Output TS - ASI port.

3. Make any desired modifications to the editable fields.

4. Click OK to save changes.

Modifying Input Programs

The only field that can be changed on an input program is the Program Name.
1. From the inputs side of the Grooming -> Mapping window, select the program that requires a
name change.

152 BNP2xr User Guide

 Modifying and Deleting Streams or Programs

1. Right-click on the program and choose Modify Program Name from the popup menu.
(Figure 125).

Figure 125. Program Pop-Up menu - Modify Program

The menu to modify an input program on a GigE or an ASI port will be similar to Figure 126.

Figure 126. Modify Input program - GigE or ASI port

2. Enter a new name in the Program Name field.

3. Click OK to save changes.
The Program Name is changed (Figure 127).

Figure 127. Program Name Changed

BNP2xr User Guide 153

Grooming and PSIP

Modifying Output Programs

The fields that can be changed on an output program are as follows:
• Program Name
• Any relevant ETV Configuration fields:
- PIDs Priority
- Play Preference
- Late-Bind Source
• Any relevant Messaging System Setting fields:
- EAS Zone
- Operator Messaging Zone
- Logo Overlay Zone

Note: Any other attributes that you wish to change on a program must be changed on the program’s
Elementary Stream(s).

1. From the outputs side of the Grooming -> Mapping window, select the program that requires a
name change.
1. Right-click on the program and choose Modify Program from the popup menu. (Figure 128).

Figure 128. Program Pop-Up menu - Modify Program

154 BNP2xr User Guide

 Modifying and Deleting Streams or Programs

The menu to modify an output program on a GigE or an ASI port will be similar to Figure 129.

Figure 129. Modify Output program - GigE or ASI port

2. Make any desired modifications to the editable fields.

3. Click OK to save changes.

Deleting Streams and Programs

Deleting grooming items is similar to modifying them.

To delete an item:
1. Navigate to the Grooming -> Mapping window.
2. Select the item to be deleted and right-click.
The options that appear on the right-click menu differ depending on the item selected. In each case,
if the item can be deleted, the Delete option appears on the menu.
3. Choose Delete from the popup menu.
4. Click Yes in the confirmation window to confirm that you want to delete this item.
5. Type the new Program Name and click OK.

BNP2xr User Guide 155

Grooming and PSIP

Drag and Drop Grooming

You can drag and drop transport streams, programs, or data elementary streams. When you drag an
input transport stream to the output transport stream, all of the programs are moved to the new output
stream with it. You can drag a transport stream to a port, or over an existing transport stream. You can
drag a program to a transport stream, or over an existing program. You can also drag an elementary
stream to a program or to an existing elementary stream.

Drag and drop grooming details are shown in Table 39.

Table 39. Drag and drop grooming

When you drag: The grooming behavior:

Transport Stream to Transport Stream Deletes all current programs and replaces them with the
dragged Transport Stream
Transport Stream to GigE Port The entire Transport Stream is copied to the output port
Program to Transport Stream The program is created in the Transport Stream; the
Configure Program Mapping window appears, allowing you
to modify the program mapping information
Program to Program Deletes the existing program and replaces it with the
dragged program
Elementary Stream to Elementary Stream For EBIF, EISS, and regular data streams only; deletes
existing ES and replaces it with the dragged ES. Opens the
Configure Elementary Stream Mapping window. Only
supports replacing the ES, not modification.
Elementary Stream to Program For EBIF, EISS, and regular data streams only; adds the
dragged ES to the program. If the ES already exists in the
program, the dragged ES will replace the existing ES.

Caution! If you replace one transport stream with another, the original will be completely deleted.

Drag and Drop Grooming Options

Following are configuration explanations of the various drop grooming options available from the
Element Manager’s Grooming -> Mapping window.

156 BNP2xr User Guide

 Drag and Drop Grooming

Program to Transport Stream Grooming

1. Drag the desired input program and drop it onto the desired output transport stream.

Figure 130. Drag input program to output TS

All of the PSIP tables and schedules that are part of the program will be set to the specified output
port.
2. As soon as you drop the program, the Configure Program Mapping window appears.

Figure 131. Configure Program Mapping window

3. Make any changes necessary as described in Table 40, below.

If this is a backup program, click the Program Redundancy tab and enter the input ports, transport
streams, and programs. (See “Program Redundancy” on page 168 for details)
4. Click OK to finalize the output program information.

BNP2xr User Guide 157

Grooming and PSIP

Program to Program Grooming

1. Drag the desired input program and drop it into the desired output program.
2. The Configure Program Mapping window appears (Figure 132).

Figure 132. Configure Program Mapping window - program to program

3. Make any changes necessary as described in Table 40 below.

If this is a backup program, click the Program Redundancy tab and enter the input ports, transport
streams, and programs. (See “Program Redundancy” on page 168 for details)
4. Click OK to finalize the output program information.

The descriptions in Table 40 are applicable to both the program-to-transport stream and program-to-
program procedures described above.

Note: If you are using the drag and drop method of program creation and you wish to configure or
enable Messaging System Settings for this program, you must modify the program after drag

158 BNP2xr User Guide

 Drag and Drop Grooming

and drop and then associate zones for the program as described in “Program Messaging
System Setting” on page 147.

Table 40. Configure Program Mapping

Category Field Description

Port Read-only. Specifies the input GigE or ASI port used for the
input program.
The GigE port to use, transport stream ID, program name and
number for both the source and the destination of this program
must be defined. For input streams, you can choose to
Forward SCTE-35 Cue. For output streams, you can enable
and specify PMT PID, and enable SCTE 30 to 35 Conversion.
TS ID Read-only. Specifies the input Transport Stream ID used for
the input program.
Source
Program Number Read-only. Specifies the program number for the input
program.
Program Name Read-only. Specifies the program name (if one was given) for
the input program.
Synchronize input Check this box to synchronize the input program name with the
and output program output program name,
names
Forward SCTE-35 Check this box to forward SCTE-35 cue tones from the input
Cue program.
Port Displays the destination GigE or ASI port of the output port to
which the program will be groomed.
TS ID Displays the destination Transport Stream ID of the output TS
to which the program will be groomed.
Program Number Displays the destination program number of the output
program to which the program will be groomed.
Program Name Displays the destination program name of the output program
name to which the program will be groomed.
Destination PMT PID Select this option to activate the PMT ID box, into which you
can then enter the PMT ID, or the ID of the program map table
(PMT)
Enable DPIa Select this option to enable DPI for the program only, rather
than the whole TS.
• This option is hidden unless a PROGRAM WITH DPI license
key has been entered in The License Manager.
SCTE 30 to 35 When checked, enables SCTE 30 to SCTE 35 conversion.
Conversion

BNP2xr User Guide 159

Grooming and PSIP

Table 40. Configure Program Mapping (Continued)

Category Field Description

ETV PIDs Priority Indicates the source of EBIF ES data for the duration of the ad
time and provides the option to replace or not replace the pre-
bound EBIF ESs during ad splicing.
• When Ad is selected, the spliced ad will provide the EBIF
and EISS elementary streams (ESs). If the EBIF and EISS
ESs from the ad do not match the stream type and
descriptors of the network EBIF and EISS ESs, then the
network EBIF and EISS ESs will be dropped. If no EBIF and
EISS data are pre-configured at the output program or no
EBIF and EISS data are present at the output then the EBIF
and EISS ESs form the ad are dropped.
• When Network is selected, the EBIF and EISS ESs from the
ad server will be ignored, even if they are present.
Default is set to Ad.
Play Preference When the ETV PIDs Priority is set to Network, the following
three options will appear in a drop down box:
ETV Configurationb • Play through ad: any EBIF ES data that is part of the output
program will continue to be played during the ad.
• Drop during ad: any EBIF ES data tha tis part of the output
program will be dropped during the ad.
• Play during ad only: provides the ability to select the input
EBIF ES source that will be playing only during the ad time;
if an EBIF ES source is not available, the EBIF ES that
currently exists in the output program will be played.
Default setting is Play through ad.
Late-Bind Source This option is only available when the ETV PIDs Priority is set
to Network and the Play Preference is set to Play during ad
only.
• When the above two conditions have been met, an
additional field with ellipses (. . .) will appear. Clicking on the
ellipses will open the Late-Bind Source Dialog window,
which will allow the option to choose a valid pair of EBIF/
EISS ESs from the BNP’s input.
Now or Start Time To specify the time the program should start, or to continue
until either manually stopped or to stop at a specified time,
enable these features. If you choose to specify a start or stop
time, enable the feature and type the time directly into the
appropriate field. A check mark appears when the feature is
active.
See “Scheduling Grooming - One time event” on page 167 for
Grooming Schedule additional information.
Never or Stop Time To tell the program the time to start, or to continue until either
manually stopped or to stop at a specified time, enable these
features. If you choose to specify a start or stop time, enable
the feature and type the time directly into the appropriate field.
A check mark appears when the feature is active.
See “Scheduling Grooming - One time event” on page 167 for
additional information.

160 BNP2xr User Guide

 Drag and Drop Grooming

Table 40. Configure Program Mapping (Continued)

Category Field Description

Service Level This sets bit rate adaptation techniques applied to MPEG-2
encoded streams to further enhance bandwidth efficiency.
Valid values for this field are as follows:
• Any integer from -8 to +8
• 0 for off
• Bypass Transratorc
Quality of Service
• Handle as Datad
• No Rateshaping
For additional configuration parameters on each of these
values, see Table 41, “Service Level Configuration Details,” on
page 162.
Max Video Bitrate Sets the limits for the maximum bitrate (in Mbps) for this
program. Choosing a specific max rate will bypass automatic
transrating based on priorities.
For this program input, this category allows stream grooming
by unselecting specific input PIDs.
Input Type Specifies the stream type of the input ESs for this program.
PID Specifies the PID of the input ESs for this program.
Output Type If clicking in the blue space under this field, opens the Select
Elementary Stream window, which will allow you to change the
PID of the chosen ES.
PID If clicking in the blue space under this field, opens the Select
Elementary Stream window, which will allow you to change the
PID of the chosen ES.
Stay Unreferenced If the input program is a Ghost Program, the Stay
Unreferenced option will appear in this section. Check this box
if the PIDs in this stream are to remain unreferenced in any
PSI tables. See “Adding an Unreferenced PID as an
Elementary Stream” on page 183 for more information.
Component PIDs
Treat As Async Data If the input program is a data-only program or all video and
audio streams in the Component PIDs section are unchecked,
the Treat as Async Data option will appear in this section.
Check this box to disable PCR timing information for this
program.
Placeholder ETV If the input program does not contain EBIF and EISS
ESs elementary streams, a drop down box for the Placeholder ETV
ES field will be displayed and editable. This option allows
preconfiguration of an EBIF and EISS ES pair with a stream
type of 5 or 192. When selecting either EBIF/EISS 5 or EBIF/
EISS 192 the system will automatically generate the following:
• 1 new ES with a Preconfigured for PMT setting of Yes for
each EBIF and EISS stream .
(See “Elementary Streams” on page 172.)
• 2 new Descriptor Rules for each new EBIF and EISS ES.
(See “Managing PMT and ES Descriptors” on page 196.)

BNP2xr User Guide 161

Grooming and PSIP

Table 40. Configure Program Mapping (Continued)

Category Field Description

TS Type The type of stream: MPEG-2, ATSC, SCTE, or DVB.
Major Channel Operator-defined channel number: for terrestrial broadcast, the
Number major channel number is limited to the range 1 to 99 for ATSC
digital television or audio services. For cable, major channel
TS Type
numbers may range from 1 to 999. Only editable when ATSC is
enabled.
Minor Channel Operator-defined minor channel number: any whole number in
Number the range from 0 to 999. Only editable when ATSC is enabled.
a. A GROOMING WITH DPI license key (which enables DPI for the TS) cannot co-exist with a PROGRAM WITH DPI
license key.
b. For additional information on ETV configuration including details on various EBIF and EISS use cases, see Chapter 7,
"ETV Binary Interchange Format (EBIF)."
c. This option should not be selected when grooming a DPI-enabled program.
d. This option should not be selected when grooming a DPI-enabled program.

Configure Program Mapping Service Level Configuration Options

The Service Level field allows the assignment of transrating priorities and conditions for each
program. Table 41 provides additional details for configuring the Service Level field.

Table 41. Service Level Configuration Details

QoS Service Level Can DPI be Effect on Video Output

Configuration Video Processing performed? Bandwidth
Transrating Video elementary stream YESa Transrated output video ES
Service Level (ES) is processed through the requires less bandwidth than
Values transrater. input video ES.
• -8: highest transrating,
lowest quality.
• +8: lowest transrating,
highest quality.
No Rateshaping Video ES processing is YESb Output video ES bandwidth will
limited through the transrater vary depending on level of ES
with null packet removal. null packet removal.
• Video quantization level is
unchanged
Bypass Transrater Video ES is not processed YES Output video ES uses the same
through the transrater. bandwidth as input video ES.
• Can not use more than the
• Video can be displayed. bandwidth of output TS.

Handle As Data Video ES is not processed NO Output data ES is treated as

through the transrater. data and will therefore use the
same bandwidth as input video
ES.
• Video cannot be displayed.
• Can not use more than the
bandwidth of output TS.
• Total bandwidth should not
exceed 4Mbps per TS.
a. DPI sessions carry same QOS settings as network.
b. DPI sessions carry same QOS settings as network.

162 BNP2xr User Guide

 Drag and Drop Grooming

Elementary Stream Grooming

You can groom an elementary data stream from the input of a program to another program in the output
or to replace an existing elementary data stream within an output program.

To groom an ES from an input program to an output program, proceed as follows:

1. From the Inputs side of the Grooming -> Mapping window, select either the generic data or the
EBIF / EISS elementary streams you wish to groom.

Note: For information on the various data stream types and their icons, see Table 27 on page 117.

2. Drag the ES to the desired output program on the Outputs side of the Mapping window.

Data ES dragged
onto output Program
Data ES to groom

Figure 133. ES to Program Drag and Drop

The Configure Elementary Stream Mapping window will open.

Figure 134. Configure Elementary Stream Mapping window

All fields in the Configure Elementary Stream Mapping window are read-only except for the
Output Type and corresponding PID value. For a description of the fields in this window as relates
to ES mapping, see Table 42.

BNP2xr User Guide 163

Grooming and PSIP

3. If desired, you can change the PID value of the ES by clicking in the blue space under Output
Type or PID. This will open the following window:

Figure 135. ES Grooming - Reserved PID

4. Enter the desired New Reserved PID.

5. Click OK to save changes.
The new ES PID will be displayed in the Configure Elementary Stream Mapping window.

Figure 136. Configure ES Mapping - Reserved PID

6. Click OK to complete grooming the ES to the output program.

Table 42 describes the fields available in the Configure Elementary Stream Mapping window.

Table 42. Configure Elementary Stream Mapping

Category Field Description

Port Displays the source GigE or ASI port of the elementary
stream’s input program.
TS ID: Displays the source Transport Stream ID of the ES’s input
TS.
Source
Program Number Displays the source program number of the ES’s input
program.
Program Name Displays the source program name of the ES’s input
program.

164 BNP2xr User Guide

 Drag and Drop Grooming

Table 42. Configure Elementary Stream Mapping (Continued)

Category Field Description

Port Displays the destination GigE or ASI port of the output port
to which the ES will be groomed.
TS ID: Displays the destination Transport Stream ID of the output
TS to which the ES will be groomed.
Program Number Displays the destination program number of the output
program to which the ES will be groomed.
Destination Program Name Displays the destination program name of the output
program name to which the ES will be groomed.
PMT PID Displays the Program Map Table PID assigned to the
output program.
SCTE 30 to 35 Displays whether or not SCTE 30 to 35 Conversion has
Conversion been enabled for the output program to which the ES will
be groomed.
Input Type & PID Displays the ES Input Type and PID, Output Type and PID.
Output Type & PID For Input Type, the options that will be seen are as follows:
• Data
• EBIF
• EISS
Component PIDs Click the blue space under Output Type or PID to enter a
reserved PID for this ES.
Treat as Async Data When grooming a data, EBIF, or EISS ES to an output
program, theTreat as Async Data option will always be
enabled.
When data is treated as Async Data, then the timing
information in the data stream is not processed.

To groom an ES from an input program directly onto an output ES, proceed as follows:
1. From the Inputs side of the Grooming -> Mapping window, select either the generic data or the
EBIF / EISS elementary streams you wish to groom.
2. Drag the ES to the desired output ES on the Outputs side of the Mapping window.

Input Data ES to groom Drag input ES to output ES

BNP2xr User Guide 165

Grooming and PSIP

Note: An elementary stream may only be groomed on top of an existing ES-level groomed
elementary stream (not a program-level groomed stream), and the Stream Types of the input
ES and the output ES must match.

The following ES confirmation message will appear:

Figure 137. ES Grooming Replacement window

3. Click Yes to replace the output ES.

Elementary Stream Grooming Icon Colors

When grooming an ES from an input program to an output program or directly onto an output ES, the
icon representing that data stream will be displayed as a green icon on the Outputs side of the
Grooming -> Mapping window.

When grooming a complete program (and therefore all of its ESs) to an output TS or to replace an
existing output program, the icons representing the data ESs will remain a blue icon on the Outputs
side of the Grooming -> Mapping window.

See Table 27 on page 117 for additional information.

Viewing Grooming Details

1. In the Outputs side of the Grooming -> Mapping window, select the transport stream or program
whose details and schedule you want to see.
2. Right-click and select Display Grooming.
The BNP Element Manager will display the currently defined mapping and scheduling window. If
you chose to view grooming for the whole TS, all grooming for the programs in that TS will be

166 BNP2xr User Guide

 Drag and Drop Grooming

displayed; if you chose to view grooming for a specific program, only the grooming for that
program will appear.

Indicates ES-level grooming

Figure 138. Grooming detail display - TS

The presence of ES-level grooming is indicated by a black asterick (*) next to the relevant ES in the
Compnent PIDs section of the Current Program Mapping and Schedule window.
3. Click Refresh to refresh the view, or Cancel to close the window.

Note: In Figure 138, the times specified in the Grooming Schedule section (see Figure 139 for a
sample) are from the NTP server. Your PC that is used for configuration may show a different
time. This “PC time” should be disregarded; the start and stop times you enter will be
referenced to the NTP server.

Scheduling Grooming - One time event

Note: It should be noted that proper use of BNP’s scheduled grooming feature depends on an NTP
server as an accurate timing source. Additionally, when scheduling grooming, only a single
event can be scheduled, rather than an ongoing occurence.

BNP2xr User Guide 167

Grooming and PSIP

To schedule grooming at a specific time for a one-time occurence, perform steps 1 through 4 in the last
section, “Creating Output Programs Manually” above in order to open the Configure Program
Mapping window. Then proceed as follows:
1. From the Configure Program Mapping window, uncheck Now or Start time and click on the
pull-down menu that appears. The following dialog opens:

Figure 139. Grooming schedule

2. If you want to start grooming immediately, click OK. If you want to start at a later time, set the time
and date and then click OK.
3. To set the stop time, uncheck Never or Stop Time. The grooming schedule of Figure 139 appears.
If you don’t want to stop grooming, click OK. To set a stop time, set the time and date for grooming
to stop and click OK.
4. Click OK to apply the mapping to the program.

Program Redundancy
The BNP supports program level redundancy on all the output services. Program level standby is
configurable using the Element Manager. The BNP allows the user to designate any input service as a
“standby program” with the exception of the same service. The BNP returns back to the primary
program from the standby program when the primary program recovers from the interruption.

The health of the standby program will be checked before failover, and the BNP will not perform the
switch if the standby is degraded.

Modes of Program Redundancy Operation

The BNP supports two modes of Program Redundancy operation—one offering automatic recovery
from the backup program to the primary program while the other allows the user to manually select
when the recovery process should occur.

168 BNP2xr User Guide

 Program Redundancy

Table 43 describes the various modes of operation for program redundancy.

Table 43. Program Redundancy Modes of Operation

Category Primary to Backup Backup to Primary

Automatic Failover to Backup Automatic failover operation is based Automatic recovery operation is
Program / Automatic Recovery on two conditions detected, either one based on two conditions detected,
to Primary Program will trigger a failover to the designated both are required to trigger a
backup program: recovery to the primary program:
• Video ES failure detection • Video ES recovery detection
or and
• Missing PAT/PMT detection. • PAT/PMT detection.
Automatic Failover to Backup Automatic failover operation is based Manual recovery operation is
Program / Manual Recovery to on two conditions detected, either one based on the user selecting when
Primary Program will trigger a failover to the designated a single program or all programs
backup program: should be recovered to their
• Video ES failure detection, respective primary programs.

or
• Missing PAT/PMT detection.

Figure 140. Program Redundancy

To Configure Program Redundancy

1. From the Grooming -> Mapping window, drag and drop an input program to either an output
transport stream or an output program.
The Configure Program Mapping window will open.
2. Click the Program Redundancy tab.
3. Check the Specified Program Backup box at the top of the screen.
4. Drill down in the input grooming window and select the program which is to be the backup for the
output program.
5. Under the Selected Program Redundancy Mode section, select whether or not this program is to
act as Automatic Failover / Automatic Recovery or Automatic Failover / Manual Recovery.

BNP2xr User Guide 169

Grooming and PSIP

Figure 140 shows an example of program redundancy in which the backup is selected as GigE 2,
Transport Stream ID 0x5c, and Program Number 1.

Figure 141. Configure Program Mapping - Program Redundancy

Manual Recovery Procedures

The BNP supports the ability to manually switch between the Primary and Backup program. Follow
this procedure for manual recovery:

170 BNP2xr User Guide

 Program Redundancy

1. From the Outputs side of the Grooming -> Mapping window, right-click the desired program and
select Display Grooming from the pop-up menu.
The Current Program Mapping and Schedule window opens (Figure 142).

Figure 142. Program Redundancy - Manual Recovery

2. Select the scheduled program and right-click.

3. From the pop-up menu, select Switch to Backup.

The Switch to Backup option is available when the selected program is already in the Manual
Recovery to Primary Program operation mode. (The Automatic Recovery to Primary Program mode
does not allow staying in the Backup Program.)

Figure 142 above illustrates the Manual Recovery selection for program redundancy operation on
individual programs. This can be used for the Manual Recovery Primary Program procedure following
an Automatic Failure to Backup Program, or for toggling between primary and backup programs for
test purposes.

To recover all programs, from the main Element Manager window, select Maintenance -> Regroom.
See “Regrooming” on page 107 for additional information.

BNP2xr User Guide 171

Grooming and PSIP

Elementary Streams

Creating an Elementary Stream

To add a new elementary stream to an output program:
1. From the Outputs side of the Grooming -> Mapping subtab, select the program to which you
want to add an elementary stream.
2. Right-click and select Manage Elementary Streams from the pop-up window. The window of
Figure 143 appears (The stream entries will vary per program).

Figure 143. Manage Elementary Streams

3. Click Add ES.

4. A new elementary stream entry will appear below the last stream.
By default, the new stream is an AC-3 Audio stream. See Figure 144 for an example.

Note: An ES Type, Stream Type, PID number, Dummy value, and Preconfigured for PMT value
can only be modified when the word “New” appears next to it in the Stream Order column.
Once you click OK to save changes, you will not be able to modify any of these parameters for
this particular stream without deleting the stream and adding it again.

172 BNP2xr User Guide

 Elementary Streams

Stream Order must

display “New” in order
to modify the stream.

Figure 144. Manage Elementary Streams - New

5. Modify the ES Type, Stream Type, PID, and Dummy status (if applicable) by clicking or double-
clicking on each field under the the respective column. (See Table 44 for details.)
For ES Type, a drop down box will be displayed with applicable choices:

Figure 145. Manage Elementary Streams - ES Type choices

BNP2xr User Guide 173

Grooming and PSIP

For Stream Type, if the ES Type is Video, a drop down box will appear with applicable choices:

Figure 146. Manage Elementary Streams - Stream Type, drop down

If the ES Type is Audio, the following selection window will appear:

Figure 147. Manage Elementary Streams - Audio Selection

If the ES Type is Data, the following selection window will appear:

Figure 148. Manage Elementary Streams - Data Selection

174 BNP2xr User Guide

 Elementary Streams

Note: When Stream Type is EBIF, EISS or EBIF and EISS, two new descriptor rules will be
automatically added for each new EBIF or EISS stream. See “Managing PMT and ES
Descriptors” on page 196 for additional information.

For PID, double-clicking the field will render it editable and you can type in the new PID:

Edit PID field.

Convert hex to
decimal

Figure 149. Manage Elementary Streams - PID

Note: When entering a PID you must enter its decimal conversion from its hex listing in the Outputs
side of the Grooming -> Mapping window. For example, if you are creating a Dummy PID
based on an input data stream that has been groomed to a program on an output TS whose
PID is 0xf05 (note, the “0x” portion of the PID is for internal reference only), the decimal
conversion would be as follows:

hex: F05 converts to decimal: 3805.

BNP2xr User Guide 175

Grooming and PSIP

If the ES Type field is Data, clicking on the Dummy field will produce a drop down box with the
choice of Yes or No.

Figure 150. Manage Elementary Streams - Dummy

Clicking on the Preconfigured for PMT field will produce a drop down box with the choice of Yes
or No.

Figure 151. Manage Elementary Streams - Preconfigured for PMT

6. Click OK when you are done modifying the elementary stream to save all changes. The new stream
will be displayed in the Outputs side of the Grooming -> Mapping window.

176 BNP2xr User Guide

 Elementary Streams

Table 44 provides a description of the fields from the Manage Elementary Streams menu.

Table 44. Manage Elementary Streams menu

Field Description
Stream Order Read-only. Displays the order of the stream in the program mapping table
(PMT).
Grooming Status Read-only. Displays whether or not the stream is currently groomed.
ES Type Read-only if changes have been saved (i.e., OK has been clicked).
If the changes to the stream have not yet been applied, clicking this field will
open a drop down menu with the following options from which to choose:
Audio, Data, or Video.
Stream Type Read-only if changes have been saved (i.e., OK has been clicked).
If the changes to the stream have not yet been applied, and depending on
the selection from ES Type, clicking this field will open variable options:
• If Stream Type is Audio, a new window will open allowing you to choose
Audio Type and Language Selection.
• If Stream Type is Dataa, a new window will open with two drop down boxes
as follows:

Stream Type: choice of decimal values from 5 to 255b.

Stream Sub Type: choice of Data, EISS, EBIF, and EBIF and EISS

• If Stream Type is Video, a drop down box will appear with choice of
MPEG2 Video, H.264 Video, or SCTE Video.
PID Read-only if changes have been saved (i.e., OK has been clicked).
If the changes to the stream have not yet been applied, double-clicking this
field allow you to modify the PID associated with the new elementary stream.
• You must enter this value as a decimal conversion of the hex format which
appears in the Grooming -> Mapping window.
Dummy Read-only if stream is groomed; only applicable for data stream.
Clicking this field will bring up a drop down box with the following options:
• Yes: Select this if the elementary stream is a dummy stream and the
associated data stream with the same PID is carried by another program
in the same transport stream.
• No: This is a read-only value which will appear if the PID is “non-dummy”
and therefore treated as a regular stream.
Note: The Preconfigured for PMT and Dummy fields are mutually exclusive;
therefore, when one is set to Yes, the other will be automatically set to No
Preconfigured for PMT Read-only if stream is groomed; applies to all stream types, but most useful
for EBIF / EISS streams.
• Provides the ability to preconfigure the ES by creating associated
descriptor rules, regardless of whether or not the data for the
corresponding ES is present in the MPEG stream. When the
Preconfigured for PMT option is set to Yes, the BNP will not update the
PMT, as the assumption is the data is already included in the PMT.
Note: The Preconfigured for PMT and Dummy fields are mutually exclusive;
therefore, when one is set to Yes, the other will be automatically set to No.
Reserved Read-only. If the stream is a reserved PID, Yes will appear; if the stream is
not a reserved PID, the field will be empty.

BNP2xr User Guide 177

Grooming and PSIP

a. When Stream Type is EBIF, EISS or EBIF and EISS, two new descriptor rules will be automatically added for each new
EBIF or EISS stream. See “Managing PMT and ES Descriptors” on page 196 for additional information.
b. This number appears as hex in the Grooming -> Mapping window; you will need to perform hex to decimal
conversion when selecting this value

Reordering an Elementary Stream

You can reorder an elementary stream to change the order of the stream in the PMT. (If, for example,
you wish to change the order a stream is placed in the PMT when sent to the end-user’s STB.)
1. Highlight the stream you want to reorder (Figure 152).

Stream to be reordered

Figure 152. Reordering an Elementary Stream

178 BNP2xr User Guide

 Elementary Streams

2. Click Up or Down as required to put the stream in its proper place.

Stream reordered

Figure 153. ES Reordered

3. When you are done, click OK.

Elementary Stream Remapping

You can create a reserved PID or select any specific PID from existing output PIDs, while doing
grooming in the Configure Program Mapping screen, as an outgoing PID.

You have the flexibility of selecting any PID value for an outgoing PID. When you select from an
existing PID then it should be of the same ES Type and language (for audio) as the corresponding Input
ES. If there is no exact match then you cannot select that existing output PID.

You can’t create a Reserved PID for Video if there is an existing video PID in the output program on
which you are grooming.

Reserved PIDs

Reserved PIDs allow you to create PIDs under output programs which will maintain PID values and
ES Type and Subtype across reboots and regrooming even when the PID is not groomed. These types
of output elementary streams are called Reserved PIDs.

The Manage Elementary Streams screen can be used to add the ES and to specify its PID and
subtype, as well as the language for the audio ES. The subtype of the reserved video stream will be
overwritten by the input Video Subtype but the PID value will be maintained. You can delete any
reserved ES if it is not groomed from the main screen by right-clicking the ES, and choosing Delete.

BNP2xr User Guide 179

Grooming and PSIP

See “Unreferenced PID Mapping” on page 189 for steps on creating reserved PID mapping.

Dummy PIDs

To configure a Dummy PID:

1. Groom the actual data stream which you wish to create a dummy PID for from an input program to
a desired output program.
In this example, we wish to create a dummy data PID that is associated to the real data stream:
Data [PID: 0x21 Data 0xC2] in Program 6975 BBC HD

Dummy PID will be associated to this Data stream.

Figure 154. Dummy PID: Real data stream groomed

2. Select the program under which you wish to create a Dummy PID, right-click, and select Manage
Elementary Streams from the pop-up menu.
In this example, we will use Program 6904 BBC 1 C1.

180 BNP2xr User Guide

 Elementary Streams

3. From the Manage Elementary Streams window, click the Add ES button.
A new audio ES will appear as the last entry to the list of streams.

Figure 155. Manage ES - New ES for Dummy PID

4. From the ES Type column, change the ES Type from Audio to Data from the drop-down window.

Note: See the section, “Creating an Elementary Stream” on page 172 for complete deails on
manipulating the fields in the Manage Elementary Streams window.

5. From the Data Selection window, select the decimal number that matches the actual data stream’s
hex ID (this is NOT the PID).
In this case, we will choose the number “194” as it matches the hex number “C2” from the data
stream:
Data [PID: 0x21 Data 0xC2] in Program 6975 BBC HD.
6. Double click in the PID column and enter the decimal value that corresponds to the hex value from
the actual data stream.
In this case, we will enter the number “33” as it corresponds to the hex value of “21” in the data
stream:
Data [PID: 0x21 Data 0xC2] in Program 6975 BBC HD.

BNP2xr User Guide 181

Grooming and PSIP

7. From the Dummy column, select Yes from the drop down box to indicate this is a dummy PID.
The Manage Elementary Streams window should now look like this:

Figure 156. Manage Elementary Streams - Dummy PID fields completed

8. Click OK to save changes and add this stream to the Outputs side of the Grooming -> Mapping
window.
The data stream (grayed out to indicate dummy PID reference) with associated dummy PID will
show up under the appropriate program as seen in Figure 157 below.

Dummy Data ES greyed out,

matching with real Data ES

Figure 157. Dummy Data PID in Grooming -> Mapping window

9. Repeat steps Step /2-Step /8 for each additional program (within the same transport stream) under
which you wish to create a dummy PID reference.

182 BNP2xr User Guide

 Elementary Streams

Dummy PID Configuration Guidelines

The following guidelines should be taken into account when configuring data streams that use dummy
PIDs:
1. You cannot configure a Dummy PID data stream unless an actual data stream has been groomed to
a program in the relevent transport stream.
2. You cannot delete a program with a data stream to which other dummy PID streams point.
3. If you are creating multiple dummy PIDs under one program, they must all point to the original data
streams from a single program. You cannot create multiple dummy PIDs in one program that point
to data streams from multiple programs.
4. You can only reference a dummy PID data stream to a data stream in a program that is within the
same transport stream.
5. A dummy data PID referenced in a output program will be used regardless of the input source, such
as the originally groomed network program source, during program redundancy or program
substitution service, or during a DPI ad insertion.
6. You cannot configure the value in an ES as “Yes” for the Dummy field and “Yes” for the
Preconfigure in PMT field at the same time.

Deleting Dummy PIDs

To delete a dummy PID:
1. From the Grooming -> Mapping window, select the dummy PID data stream.
2. Right-click and select Delete.

Adding an Unreferenced PID as an Elementary Stream

You can add an unreferenced PID to an input transport stream. This allows you to manage
unreferenced PID inputs for various applications in the BNP output. Unreferenced PID streams are
those MPEG-2 elementary streams encapsulated in the MPEG-2 SPTS or MPTS, whose PIDs are not
referenced in any PSI (PAT and PMT) tables. These unreferenced PID streams may be purposely
inserted for some special control and applications; they could also result from the stream originator's
error.

Unreferenced PIDs can come from the program inputs from GigE interfaces or from ASI inputs. In
some applications, these unreferenced PIDs need to be routed to the appropriate output GigE ports or
ASI ports as pass-through or with or without the PIDs being remapped. In other cases, these
unreferenced PIDs need to be dropped, either because such unreferenced PIDs are not needed or the
streams are corrupted.

To add an unreferenced PID as an Elementary Stream:

1. From the Inputs side of the Grooming -> Mapping subtab, select the transport stream to which
you want to add an unreferenced PID.

BNP2xr User Guide 183

Grooming and PSIP

2. Right click the transport stream and choose Create Ghost Program from the pop-up window
(Figure 158).

Figure 158. Choosing a Ghost Program

3. . The Create Ghost Program screen of Figure 159 appears.

Figure 159. Create Ghost Program

4. Enter the Ghost Program Name. Click OK. A new program stream appears (Figure 160).

Figure 160. New Program Stream

184 BNP2xr User Guide

 Elementary Streams

Figure 161. Adding an Elementary Stream

5. Right click the new Ghost Program you have created, and choose Add Elementary Stream
(Figure 162).

Figure 162. Adding an Elementary Stream

6. From the pull-down menus, select the Stream Category, Stream Type, and PID.
7. Click OK. The new PID appears (Figure 163).

Figure 163. New Unreferenced PID

BNP2xr User Guide 185

Grooming and PSIP

Elementary Stream Ghost PID Management

Ghost programs and PIDs are extra input and output streams not referenced in a Program Association
Table (PAT). The BNP allows you to manage elementary stream (ES) Ghost PIDs in three ways:
• Unreferenced PID Pass Through. The PID output is unreferenced in the Program Mapping Table
(PMT) nor is there any mapping to any other program or transport stream table. Typical
applications are Data PID transport and grooming.
• Unreferenced PID Mapping. This has no reference in the PMT, but is mapped as a table entry in
the PAT at the transport stream level. This is used in various electronic program guide (EPG)
applications.
• Referenced PID Mapping. The PID output is referenced as a PMT entry. A typical application
might be to associate EPG data with one or more programs.

Unreferenced PIDs streams are those MPEG-2 streams encapsulated in the MPEG-2 SPTS or MPTS
but their PIDs are not referenced in any PSI (PAT and PMT) tables. These unreferenced PID streams
may be purposely inserted for some special control and applications; they could also result from the
stream originator's error.

Unreferenced PIDs can come from the program inputs from GigE interfaces or from ASI inputs. In
some applications, these unreferenced PIDs need to be routed to the appropriate output GigE ports or
ASI ports as pass-through without or with PIDs remapping. In other cases, these unreferenced PIDs
need to be dropped, either because such unreferenced PIDs are not needed or the streams are
corrupted.

The BNP allows you to add and drop the unreferenced PIDs in its inputs from both GigE and ASI
ports.

The BNP can groom the unreferenced PIDs from the inputs to the appropriate output transport stream
(SPTS or MPTS) with or without PID remapping using the GUI configuration for the unreferenced
PIDs.

Unreferenced PIDs associated with program inputs are usually known in advance, so they can be
configured through the GUI for pass-through or drop. The GUI enables the user-configurable
remapping as an output PID for the input unreferenced PID; the output PID can also be referenced in
the output TS when necessary through GUI configuration.

For input ASI ports, the TS is automatically created for the input ASI port. User-configured
unreferenced PID streams are routed based on grooming rules.

The BNP guarantees there is no conflict between the unreferenced PIDs and the referenced PIDs in its
output MPTS or SPTS. If there are unreferenced PIDs causing conflict in the output MPTS or SPTS,
then the groomed unreferenced PID causing the conflict is dropped. This could happen when an
unreferenced PID is not allowed to be remapped for output.

186 BNP2xr User Guide

 Elementary Stream Ghost PID Management

Unreferenced PID Pass Through

To add an unreferenced PID:

1. Start by creating a ghost program with a data ES, and mapping the unreferenced PID from a pro-
gram input such as that shown in Figure 164.

Figure 164. Ghost Program With Unreferenced PID.

BNP2xr User Guide 187

Grooming and PSIP

2. Drag and drop the ghost program from the Inputs side of the Grooming -> Mapping window to
the desired output transport stream. The Configure Mapping Window appears (Figure 165).

Figure 165. Ghost Program Dragged and Dropped to Output TS

3. Note the PID number of the component PID, in this case 115. You will need this when you want to
create a referenced PID mapping.
4. Be sure that the Stay Unreferenced box is checked, and click OK.
The Ghost Program and its Data Transport stream with PID of 0x73 (hex conversion from decimal)
appears on both the input and output (Figure 166) showing the stream has been passed through.

Figure 166. Ghost Program Passed Through

188 BNP2xr User Guide

 Elementary Stream Ghost PID Management

Unreferenced PID Mapping

We start with a window as shown in Figure 167.

Figure 167. Starting Unreferenced PID Mapping

BNP2xr User Guide 189

Grooming and PSIP

1. Highlight the appropriate output port and choose Create Output Transport Stream (Figure 168).

Figure 168. Create Output Transport Stream

2. Enter the Destination IP address and the UDP Port number, choose DVB as the TS Type and click
OK.

190 BNP2xr User Guide

 Elementary Stream Ghost PID Management

3. Drag the Ghost Program from the input of Figure 167 and drop it on the DVB transport stream you
just created. The Configure Program Mapping window (Figure 169) appears.

Figure 169. Configure Program Mapping Window

4. Be sure that the Stay Unreferenced box is checked.

5. Click the empty space to the right of the Component PIDs. The Select Elementary Stream window
of Figure 170 appears.

Figure 170. Select Elementary Stream Window

6. Enter the new reserved PID number and click OK.

7. Click OK in the Configure Program Mapping window. The unreferenced PID is mapped.

BNP2xr User Guide 191

Grooming and PSIP

Referenced PID Mapping

Input Ghost ES PIDs can be groomed by the BNP and referenced as ES PIDs in one or more program
in the output TS. To add a referenced PID to two programs:

Figure 171 shows the starting window with the unreferenced data PID ES created under a Ghost
Program on the input.

Unreferenced data PID

in Ghost Program Output program to
which the Ghost PID
will be referenced.

Figure 171. Starting Window for Referenced PID Mapping

1. Drag and drop the input ghost program (in this case: Ghost-Program-1) to the output transport
stream. Be sure the Stay Unreferenced box is checked (Figure 172).

192 BNP2xr User Guide

 Elementary Stream Ghost PID Management

Note: The ghost program must be groomed to the output TS first (Step 1) before creating a dummy
PID as described in Step 4.

Figure 172. Mapping the Transport Stream

2. Click OK.
The ghost program and its unreferenced PID appear in the Outputs side of the Mapping window.

BNP2xr User Guide 193

Grooming and PSIP

3. Highlight the output program (from Figure 171) you wish to reference the data PID to, right click
and choose Manage Elementary Streams.

Figure 173. Manage Elementary Streams

4. Click Add ES and fill in the new row (Figure 174) as described in “Dummy PIDs” on page 180.
You will need to know the PID reference, which, in this case, is 115. Be sure to select Yes in the
Dummy column.

Figure 174. New ES filled In

194 BNP2xr User Guide

 Elementary Stream Ghost PID Management

5. Click OK.
The new ES will appear under the program. The mapping window shows the same PID in both
programs, with the (dummy) PID in Program 1 grayed out.

Figure 175. Dummy data PID in Program grayed out

Clicking on the program of the grayed out data PID and selecting Manage Elementary Streams
will show the Dummy PID status of Yes and a Reserved PID status of Yes as well:

Figure 176. Manage ES - Dummy and Reserved status

BNP2xr User Guide 195

Grooming and PSIP

Managing PMT and ES Descriptors

The Element Manager provides the ability to create program descriptor rules that the BNP will apply
when it sends out a Program Managment Table (PMT) for a specified output program. The rules allow
for the appending or removal of output stream descriptors on the PMT level and will remain persistent
upon program regrooming.

To manage program descriptor rules, proceed as follows:

1. From the Outputs side of the Grooming -> Mapping window, right-click over the program whose
descriptor rules you wish to modify.
2. Select Manage Descriptor Rules from the pop-up menu.

Figure 177. Manage Descriptor Rules pop-up

The Manage Descriptor Rules window opens.

Figure 178. Manage Desriptor Rules window

196 BNP2xr User Guide

 Managing PMT and ES Descriptors

To Add a Program Descriptor Rule

1. From the Manage Descriptor Rules window, click the Add Rule button.

0x

Figure 179. Add Descriptor Rule window

2. Fill in the fields according to the paramaters described in Table 45 on page 198.
3. Click OK to create the rule.
A “New” status will appear for the descriptor in the Manage Descriptor Rules window. This means
that the new rule has not yet been applied to the BNP.

Figure 180. Add Descriptor Rule - New status

BNP2xr User Guide 197

Grooming and PSIP

4. Click OK in the Manage Descriptor Rules window to apply the new rule change to the BNP,
which will remove the “New” status from the far left of the menu (Figure 181). .

Figure 181. Manage Descriptor Rules - Rules Added

5. Click Cancel to close the window.

Table 45 describes the fields available in the Add Descriptor Rule menu.

Table 45. Manage Descriptor Rules fields

Field Description
TS This field is read-only. Displays the Transport Stream ID and type for which
the rule will apply.
Program This field is read-only. Displays the name of the program for which the rule
will apply.
Name For reference use only when appending (or adding) an output program
descriptor. Do not enter data in this field when removing a descriptor.
Action Specify which action is to occurr for this rule. Choices are:
• Append Descriptor: adds the specified descriptor to the PMT of the output
stream. The descriptor is appended to the end of the program descriptor
loop if the PID is 0, or the ES descriptor loop if the configured PID matches
the elementary stream PID.
• Remove Descriptor: removes the specified descriptor from the PMT of the
output stream. If the BNP doesn’t find a match descriptor in the PMT, no
action is taken.

198 BNP2xr User Guide

 Managing PMT and ES Descriptors

Table 45. Manage Descriptor Rules fields

Field Description
PID Specifies the PID of the stream. Valid range is from 0 to 8190. If the
descriptor is a program descriptor, enter a value of 0. Otherwise, enter the
elementary stream (ES) PID value; the descriptor rule is applied to this ES.
• Clicking the green DEC button in this field will toggle the field from decimal
to hex view.
• Clicking the green HEX button in this field will toggle the field from hex to
decimal view.
• See Figure 182 for an example of the DEC to HEX toggle view.
TAG Specifies the TAG of the stream. First 8 bits of the descriptor packet as
viewed from an MPEG analyzer.
Valid range is from 0 to 255 (decimal) or 0 to FF (hex), up to 8 bits.
• Clicking the green DEC button in this field will toggle the field from decimal
to hex view.
• Clicking the green HEX button in this field will toggle the field from hex to
decimal view.
• See Figure 182 for an example of the DEC to HEX toggle view.
Descriptor Data(Hex Data): Enter the hex value program descriptor to be appended or removed to or
from the PMT of the output stream.
• This value must be an even numbered hex value.
• This value must be an exact match for the program descriptor as known or
discovered through an MPEG analyzer. The BNP will not discover or
display the descriptors from the actual TS.
• When the rule applies to an input stream, the Descriptor Data field is
passed through based on information from the input program.

Figure 182 shows an example of the DEC to HEX toggle view in the Add Descriptor Rule window.

Figure 182. Add Descriptor Rule - DEC to HEX toggle

BNP2xr User Guide 199

Grooming and PSIP

To Edit a Program Descriptor Rule

1. From the Manage Desriptor Rules window, highlight the descriptor rule you wish to edit.
2. Click the Edit Rule button.
The Add Descriptor Rule window will open for the highlighted rule.
3. Edit the fields for the descriptor rule, following the guidelines listed in Table 45.
If the rule you wish to edit has already been applied to the BNP, you will only be able to edit the
Descriptor Data field.
4. Click OK to save changes.
The status field at the far left of the Manage Descriptor Rules window will show a status of
“Changed.”

Figure 183. Edit Descriptor Rule - Changed status

5. Click OK in the Manage Descriptor Rules window apply the new rule change to the BNP,
removing the “New” status from the far left of the menu.
6. Click Cancel to close the window.

To Delete a Program Descriptor Rule

1. From the Manage Descriptor Rules window, highlight the descriptor rule you wish to delete.
2. Click the Delete Rule button.

200 BNP2xr User Guide

 Managing PMT and ES Descriptors

3. You will be asked if you are sure you want to delete the rule.

Figure 184. Manage Descriptor Rules - Rules Deleted

4. Choose Yes.
5. The rule is deleted from the Manage Descriptor Rules window, as well as removed from the BNP.

BNP2xr User Guide 201

Grooming and PSIP

Monitoring Bitrates
The second tab on the Grooming window is used to monitor input bitrates, and the third tab is used to
monitor input-output bit rates. The BNP Element Manager shows real-time bit rates.

To change the information displayed for the second tab, use the buttons on the lower left panel. To
change the information for the third tab, use the selectors across the top of the window. Select a port
and a transport stream.

To select the direction in which to view streaming, move to the upper right of the window. Select
Input, Output, or both. A checkmark appears beside the stream direction. The selected direction
streams appear in the bar graph beside each other for easy comparison. If only one direction is
selected, no comparison is performed.

Input and output bit rates are shown in a bar graph. For the percentage of total output bit rate for each
program, use the lower portion of the window. The bar on the lower right shows the total input rate
compared to the assumed output rate. You can change the output bitrate by typing a new rate into the
Output bitrate field. By default, output bitrate is set to 38.7.

The BNP can simultaneously monitor only 14 programs. If the total selected number of programs
exceeds 15, the programs in the earlier monitoring list will be shifted out, and the new selected
programs will be added to the bottom of the list. The bit rate monitor window only keeps up to 14
programs.

202 BNP2xr User Guide

 Monitoring Bitrates

Each program is shown as a percentage of the total.

Figure 185. Input Monitoring bitrates

Select the port or transport stream from the dropdown menus at the top, and choose input, output, or
quantization level (level at which an analog signal is sampled as determined by the resolution of the
analog-to-digital converter) to view. You can view any or all simultaneously.

BNP2xr User Guide 203

Grooming and PSIP

The bar shows the total input rate compared to the assumed output rate. You can change the output
rate. If the input rate exceeds the output rate, the total estimated transrating is displayed as shown in
Figure 186.

Figure 186. Input bitrate exceeds output

The estimated transrating percentage is computed as follows:

% Rate Control=(input rate - output rate)/input rate

To stop real-time polling and freeze the bar graph, click Stop in the lower right corner. The button
changes to Start when real-time polling is stopped. To restart the polling, click Start.

204 BNP2xr User Guide

 Monitoring Bitrates

Each selected counter displays in a separate graph: in the figure below, the top graph shows output
quantization levels, while the lower graph shows input and output bitrates.

Selectors

Start/Sto
button

Figure 187. Input-Output Bit Rate Monitor tab

BNP2xr User Guide 205

Grooming and PSIP

206 BNP2xr User Guide

CHAPTER 6

Digital Program Insertion (DPI)

This chapter describes digital program insertion and how it relates to the BNP2xr.

In order to perform the steps in this section, you will need either a GROOMING WITH DPI license
key or a PROGRAM WITH DPI license key. See “The License Manager” on page 104 for additional
information.

In This Chapter:
• “Digital Program Insertion,” next.
• “Connecting an Ad Server to the BNP” on page 209.
• “SCTE 30 to SCTE 35 Conversion” on page 209.

Digital Program Insertion

The BNP supports industry standard digital program insertion (DPI) applications, such as program
substitution and ad insertion.

The BNP is fully interoperable with industry compliant ad servers via SCTE 30 interface. When a
successful initialization has been established with the BNP via SCTE 30, Element Manager indicates
such with an arrow icon on the Input/Output window of the Grooming -> Mapping tab.

The BNP is fully compliant to SCTE 30 and SCTE 35 standards. The BNP receives ads along with
SCTE 30 splice messages from an ad server. Receiving these messages triggers the BNP to splice the
ad. The ad is then treated the same as other objects in the BNP configuration.

BNP2xr User Guide 207

Digital Program Insertion (DPI)

A common DPI / ad insertion application deployment using SCTE 30 and 35 (the later carrying in-
band availability cue messages) may be represented by the following regional ad zone insertion
illustration:

DPI / Ad Servers
with Ad Content Zone 1
Ford CNN
BMW Ford
Toyota

Spliced Ads SCTE-30 Zone 2

CNN CNN
Avail BMW

SCTE-35
Splice Cues
Zone 3
CNN
Toyota

Figure 188. Regional Ad Zone Insertion Illustration

Note: It is highly recommended that you use a NTP server with the BNP. An NTP server is required
if you are performing Digital Program Insertion (DPI) and dynamic grooming. You must have
the NTP server up and running prior to booting up your BNP.

Note: When configuring a DPI-enabled program, do not use Bypass Transrator or Handle as Data
Quality of Service levels when grooming a program. See Table 41 on page 162 for additional
information.

208 BNP2xr User Guide

 Connecting an Ad Server to the BNP

Connecting an Ad Server to the BNP

Figure 189 shows how the ad server is connected to the BNP. Other connections may be possible, but
this figure shows the general connection.

Figure 189. Ad server - BNP connection

SCTE 30 to SCTE 35 Conversion

BNP is capable of receiving SCTE 30 messages from an ad server and converting those messages into
an SCTE 35 message.

Figure 190. SCTE 30 to SCTE 35 Conversion

BNP2xr User Guide 209

Digital Program Insertion (DPI)

To enable the SCTE conversion feature:

1. Launch the Element Manager and log in as the administrator.
2. Select the Grooming -> Mapping window
3. Groom an input program to an output transport stream as described in “Drag and Drop Grooming”
on page 156 of Chapter 5, “Grooming and PSIP.”
4. From the Configure Program Mapping window, check the Forward SCTE-35 Cue and SCTE
30 to 35 conversion boxes.

Figure 191. Configure Program Mapping window - Forward SCTE35 Cue

5. Click OK.

Once enabled, the BNP only performs the conversion: no splicing is performed.

210 BNP2xr User Guide

CHAPTER 7

ETV Binary Interchange Format (EBIF)

This chapter describes how the BNP can be configured to process Enhanced Television (ETV) Binary
Interchange Format (EBIF) content for delivery of interactive data in the video processing network.

In This Chapter:
• “Overview,” next.
• “Functionality” on page 211.
• “Prerequisite Reading” on page 211.
• “Use Case Configuration Examples” on page 212.

Overview
The CableLabs EBIF standard provides a solution for the delivery of interactive data to existing set-
top boxes (STBs), including older models of STBs. EBIF condenses interactive applications in order
to use the minimal STB resources available for interactive data delivery. Since ETV can make use of
scant resources, the MSO has the ability to deliver interactive broadcasts and advertisements to the
widest possible audience, including the STB user who still relies on legacy hardware. Because ETV
applications are very compact and can be downloaded to the STB rapidly, the ETV format is
particularly suitable for authoring interactive commercials.

Prerequisite Reading
In order to better understand the Use Cases described in this chapter, you should familiarize yourself
with the concepts and steps described in Chapter 5, “Grooming and PSIP.” In particular, the following
sections will be useful:
• “Viewing ES-Level Input Source” on page 115.
• “Interpreting Elementary Stream Status Icons” on page 117.
• “Creating Programs” on page 144.
• “Drag and Drop Grooming” on page 156.
• “Elementary Streams” on page 172.
• “Managing PMT and ES Descriptors” on page 196.

Functionality
ETV is interpreted by a User Agent: a software application that runs on the set-top box that is installed
remotely by the MSO.

BNP2xr User Guide 211

ETV Binary Interchange Format (EBIF)

When ETV is downloaded to the STB, it uses a pairing of data elementary streams, which consist of
the following:
• ETV Binary Interchange Format (EBIF) data ES — carries the application data.
• ETV Integrated Signaling Stream (EISS) data ES — carries timing signals that trigger events
associated with the application.

ETV applications are typically "bound" (or Pre-bound) to particular pieces of content, and packaged
in a program together with video and audio while being broadcast to the STB. This content can be a
30-second ad or a network stream (a dedicated channel or program with EBIF content coded into it).
Another possible source of ETV data is a local EBIF streamer: a server that provides pre-packaged
EBIF content, allowing the BNP to enhance a video or audio program (network stream or ad) with
additional ETV data. The process of adding EBIF enhancement to an existing network stream or ad is
referred to as Late-binding.

Figure 1 shows the basic ETV data source flow.

DPI Pump
DPI Pump

Ad Insertion

Broadcast Output Mux

Sat. Receiver BNP QAM STB
Sat. Receiver BNP QAM STB

Local EBIF
Local EBIF
Streamer
Streamer

Figure 1. ETV EBIF Data Source flow

Use Case Configuration Examples

The BNP can groom, splice or filter ETV data streams, including, but not limited to, the Use Case
examples listed below:
1. Pre-Bound Ad Splice.
2. Pre-Bound EBIF Passthrough (no DPI).
3. Pre-Bound EBIF Drop.
4. Pre-Bound EBIF Passthrough and Keep During Ad Splice.
5. Pre-Bound Network EBIF; Late-Bind EBIF During Ad.

Note: In all of the following Use Cases (except as specified as “Non-DPI”) it is assumed that the
BNP is configured for DPI. See Chapter 6, “Digital Program Insertion (DPI)” for details on
configuring DPI.

212 BNP2xr User Guide

 Use Case Configuration Examples

Pre-Bound Ad Splice

In pre-bound ad splicing, the input network (or program) stream does not contain ETV data; rather, an
ad containing ETV data ESs is spliced in later. In this case, the BNP would be configured to play the
ad’s ETV streams on the output during the ad splice.

Figure 2 shows an example of pre-bound ad splice.

Pid Type

Video

Audio

EBIF EISS

EBIF Data
Spliced Program

Pid Type
Pid Type
Video
Video DPI Pump
DPI Pump
Audio
Audio
Advertisement EBIF EISS

EBIF Data

Broadcast Output MUX

Sat. Receiver BNP STB
Sat. Receiver BNP STB

Broadcast Program

Pid Type

Video
Local EBIF Audio
Local EBIF
Streamer
Streamer EBIF EISS

EBIF Data

Figure 2. Pre-bound Ad Splice flow

Configuration Steps:
To configure pre-bound ad splice, proceed as follows:
1. From the BNP Element Manager, click on the Grooming -> Mapping tab.
2. Create an output transport stream, if necessary. (See the section that begins with, “Creating MPEG-
2 Output Transport Streams” on page 123 for additional information.)
3. Use the Drag and Drop Grooming feature to groom a desired input program to the desired output
transport stream (oTS), as seen in Figure 3, for example.

BNP2xr User Guide 213

ETV Binary Interchange Format (EBIF)

Note: In this use case, the input program does not contain any ETV elementary streams.

Figure 3. Input program (without ETV data) groomed to oTS

The Configure Program Mapping window will open.

4. In the ETV Configuration section, the PIDs Priority setting should remain at the default of Ad.
5. In the Component PIDs section under Placeholder ETV ESs, select the appropriate type of EBIF
and EISS elementary stream placeholders from the drop down box. The type of ESs selected here
should match those of the ETV ESs in the ad.
6. If necessary, change the PID values of the EISS and EBIF ESs by clicking the blue space under the
Output Type or PID columns next to the appropriate input ES.
Figure 4 shows the Configure Program Mapping window with the above options filled in.

Figure 4. Configure Program Mapping window - EBIF/EISS Placeholder

214 BNP2xr User Guide

 Use Case Configuration Examples

7. Click OK.
The Grooming -> Mapping window will now show the groomed program with two Data EBIF/
EISS ESs grayed out.

Figure 5. Program with placeholders groomed - ESs grayed out

Note: When creating Placeholder ETV ESs, two new descriptor rules with default values will be
created for each ES used as a placeholder. The Descriptor Data information in these rules may
be edited, if necessary. In this case, there will be 4 new descriptor rules (2 for EISS and 2 for
EBIF) that are created in the Manage Descriptor Rules window.

To view the descriptor rules created with the placeholder ESs, proceed as follows:

BNP2xr User Guide 215

ETV Binary Interchange Format (EBIF)

1. From the Outputs side of the Grooming -> Mapping window, right-click on the program you just
groomed and select Manage Descriptor Rules from the pop-up menu.
The Manage Descriptor Rules window will open, showing two descriptor rules for each ES
placeholder:

Figure 6. Manage Descriptor Rules - EISS & EBIF additions

2. Click Cancel to close the Manage Descriptor Rules window.

Pre-Bound EBIF Passthrough (no DPI)

In pre-bound EBIF passthrough on a non-DPI program, the network stream contains the pre-bound
ETV data streams, and the BNP is configured to play the input ETV streams on the output.

216 BNP2xr User Guide

 Use Case Configuration Examples

Figure 7 shows an example of pre-bound EBIF passthrough.

Pid Type Pid Type

Video Video

Audio Audio
DPI Pump
DPI Pump
EBIF EISS EBIF EISS

EBIF Data EBIF Data

Broadcast Output Mux

Sat. Receiver BNP STB
Sat. Receiver BNP STB

Local EBIF
Local EBIF
Streamer
Streamer

Figure 7. Broadcast EBIF enabled

Configuration Steps:
To configure pre-bound EBIF passthrough, proceed as follows:
1. From the BNP Element Manager, click on the Grooming -> Mapping tab.
2. Create an output transport stream, if necessary. (See the section that begins with, “Creating MPEG-
2 Output Transport Streams” on page 123 for additional information.)
3. Use the Drag and Drop Grooming feature to groom a desired input program to the desired output
transport stream (oTS), as seen in Figure 8, for example.

Note: In this use case, the input program does contain two ETV elementary streams.

Figure 8. Input program (with ETV data) groomed to oTS

BNP2xr User Guide 217

ETV Binary Interchange Format (EBIF)

The Configure Program Mapping window will open.

Figure 9. Configure Program Mapping - EBIF/EISS defaults

4. In the ETV Configuration section, leave the PIDs Priority set to the default of Ad.
5. In the Component PIDs section, leave the EISS and EBIF ESs checked. You may change the PID
values or leave them at their defaults.
6. Click OK.
The Grooming -> Mapping window will now show the groomed program with the data EBIF/
EISS ESs passed through to the output.

Figure 10. Program with ETV ESs passed through

218 BNP2xr User Guide

 Use Case Configuration Examples

Pre-Bound EBIF Drop

In pre-bound EBIF drop, the network stream contains pre-bound ETV data streams and the BNP is
configured to not play (to drop) the network ETV streams on the output.
Figure 11 shows an example of pre-bound EBIF where the ETV streams are dropped.

Pid Type Pid Type

Video Video

Audio Audio
DPI Pump
DPI Pump
EBIF EISS

EBIF Data

Broadcast Output Mux

Sat. Receiver BNP STB
Sat. Receiver BNP STB

Local EBIF
Local EBIF
Streamer
Streamer

Figure 11. Broadcast EBIF disabled

Configuration Steps:
To configure pre-bound EBIF to be dropped, proceed as follows:
1. From the BNP Element Manager, click on the Grooming -> Mapping tab.
2. Create an output transport stream, if necessary. (See the section that begins with, “Creating MPEG-
2 Output Transport Streams” on page 123 for additional information.)
3. Use the Drag and Drop Grooming feature to groom a desired input program to the desired output
transport stream (oTS), as seen in Figure 8 on page 217, for example.

Note: In thise use case, the input program does contain two ETV elementary streams.

The Configure Program Mapping window will open.

4. In the ETV Configuration section, leave the PIDs Priority set to the default of Ad.

BNP2xr User Guide 219

ETV Binary Interchange Format (EBIF)

5. In the Component PIDs section, uncheck the EISS and EBIF ESs.
The Configure Program Mapping window will look similar to Figure 12.

Figure 12. Configure Program Mapping - EBIF/EISS unchecked

6. Click OK.
The Grooming -> Mapping window will now show the groomed program with the data EBIF/
EISS ESs dropped from the output.

Figure 13. Program with ETV ESs dropped

Pre-Bound EBIF Passthrough and Keep During Ad Splice

In this example, the network stream contains pre-bound ETV data streams and the ads are un-
enhanced. When the network stream is groomed to the output the BNP is configured to continue
playing (keep) the network ETV streams during ad splices.

220 BNP2xr User Guide

 Use Case Configuration Examples

Figure 14 shows an example of broadcast EBIF groomed as Splice/Keep.

Pid Type

Video

Audio
Spliced Program

Pid Type
Pid Type

Video DPI Pump Video

DPI Pump
Audio Audio

EBIF EISS Advertisement EBIF EISS

EBIF Data EBIF Data

Broadcast Output MUX

Sat. Receiver BNP STB
Sat. Receiver BNP STB

Broadcast Program

Pid Type

Video
Local EBIF Audio
Local EBIF
Streamer
Streamer EBIF EISS

EBIF Data

Figure 14. Broadcast EBIF groomed as Splice/Keep

Configuration Steps:
To configure pre-bound EBIF to play through and be kept during an ad splice, proceed as follows:
1. From the BNP Element Manager, click on the Grooming -> Mapping tab.
2. Create an output transport stream, if necessary. (See the section that begins with, “Creating MPEG-
2 Output Transport Streams” on page 123 for additional information.)
3. Use the Drag and Drop Grooming feature to groom a desired input program to the desired output
transport stream (oTS), as seen in Figure 8 on page 217, for example.

Note: In this use case, the input program does contain two ETV elementary streams.

The Configure Program Mapping window will open.

4. In the ETV Configuration section, click on the PIDs Priority drop-down box and select Network.
When Network is selected in PIDs Priority, the Play Preference drop-down box will be
displayed.

BNP2xr User Guide 221

ETV Binary Interchange Format (EBIF)

5. In the Play Preference drop-down box, leave the setting at the default of Play through ad.
The Configure Program Mapping window will look similar to Figure 15.

Figure 15. Configure Program Mapping - Play through ad

6. Click OK.
The Grooming -> Mapping window will now show the groomed program with the data EBIF/
EISS ESs passed through to the output.

Figure 16. Program with ETV ESs passed through (Splice/Keep)

To verify that the ETV ESs are configured for Play through ad, highlight the program and select
Modify Program from the pop-up menu.

222 BNP2xr User Guide

 Use Case Configuration Examples

Pre-Bound Network EBIF; Late-Bind EBIF During Ad

In this example, the network stream contains pre-bound ETV data streams and a local streamer or
another source (such as another input program) streams another pair of ETV ESs (late-bind source).
The BNP is configured to play the network ETV streams when the network stream is played, then to
switch to the late-bind source during the ad.
Figure 17 shows an example of pre-bound network EBIF and late-bind EBIF during an ad.

Pid Type

Video
Spliced Program
Audio
Pid Type Pid Type

Video Video

Audio Audio
DPI Pump
DPI Pump
EBIF EISS EBIF EISS

EBIF Data EBIF Data

Advertisement

Broadcast Output Mux

Sat. Receiver BNP STB
Sat. Receiver BNP STB

Broadcast Program
Late Bind
Pid Type

Local EBIF Video

Local EBIF
Streamer Audio
Streamer
EBIF EISS

EBIF Data
Pid Type

EBIF EISS

EBIF Data

Figure 17. Pre-bound Network EBIF, late-bind EBIF during ad

Configuration Steps:
To configure a late-bound EBIF ad to play through a pre-bound program, proceed as follows:
1. From the BNP Element Manager, click on the Grooming -> Mapping tab.
2. Create an output transport stream, if necessary. (See the section that begins with, “Creating MPEG-
2 Output Transport Streams” on page 123 for additional information.)
3. Use the Drag and Drop Grooming feature to groom a desired input program to the desired output
transport stream (oTS), as seen in Figure 18, for example.

BNP2xr User Guide 223

ETV Binary Interchange Format (EBIF)

Note: The input program should contain at least two ETV elementary streams and there should be
an additional two ETV ESs available for the late-bound streams.

Additional ETV
ESs to be used for
Late-bound
source

Figure 18. Input program (with ETV data) groomed to oTS; Late-bound

The Configure Program Mapping window will open.

4. In the ETV Configuration section, click on the PIDs Priority drop-down box and select
Network.
When Network is selected in PIDs Priority, the Play Preference drop-down box will be
displayed.

224 BNP2xr User Guide

 Use Case Configuration Examples

5. In the Play Preference drop-down box and select the Play during ad only option.
The Configure Program Mapping window will look similar to Figure 19.

Click the “...”

to select a late-
bind source

Figure 19. Configure Program Mapping - Play during ad only

When the Play during ad only option is selected, the Late Bind Source field will be displayed.
6. Click on the ellipses (. . .) on the right-hand side of the Late Bind Source field to open the Late-
Bind Source Dialog window.

BNP2xr User Guide 225

ETV Binary Interchange Format (EBIF)

Note: This window displays the Inputs side of the Element Manager’s Grooming -> Mapping
window.

Figure 20. Late-Bind Source Dialog window

7. In the Late-Bind Source Dialog window, drill down to the program level.

226 BNP2xr User Guide

 Use Case Configuration Examples

8. Select the desired program with ETV ESs that will be used to play during the ad; this is also called
the late-bound ETV source.

Figure 21. Late-Bind Source selected

9. Click OK to return to the Configure Program Mapping window, which will look similiar to
Figure 22:

Figure 22. Configure Program Mapping window - Late-bound selected

BNP2xr User Guide 227

ETV Binary Interchange Format (EBIF)

10.Click OK to complete the grooming process.

The Grooming -> Mapping window will now show the groomed program with the late-bound data
EBIF/EISS ESs in the output.

Figure 23. Program with late-bound ETV ESs )

To view which late-bound ETV source is configured for Play during ad only, highlight the
program and select Modify Program from the pop-up menu.

Figure 24. View Late-Bind Source in output program

228 BNP2xr User Guide

CHAPTER 8

Monitoring the BNP

This chapter describes information about the system that you can monitor to ensure that the system is
always healthy. The Alarms & Events tab provides system information and health status.

To view other information about the BNP2xr, use the other BNP Element Manager windows. A
complete discussion of the BNP Element Manager begins in “Using the Element Manager” on
page 30.

In This Chapter:
• “Selecting the Elements to View,” next.
• “Viewing Alarms and Events” on page 229.
• “The Status Bar” on page 231.

Selecting the Elements to View

The upper portion of the Alarms & Events tab lets you define the information you want to see on the
screen. You can select as many options as you choose. The information is cumulative. To sort alarms
and events, click the table header. The BNP Element Manager re-sorts the information according to
your selection.

Once you have selected the events to display, click Apply Filter to accept the changes and refresh the
window.

Types of alarms and events that can be displayed include:

• All shows all alarms and events, regardless of severity
• Raised shows all alarms that have been raised, but not cleared
• Cleared shows all alarms that have been raised and cleared
• Critical shows only critical severity alarms; these are alarms that must be dealt with immediately
• Major shows major alarms; these are alarms that may not require immediate intervention but
cannot be allowed to continue indefinitely
• Minor shows minor alarms that will not disrupt the system

Viewing Alarms and Events

After you have set the types of alarms to display, you can tab to Alarms & Events at any time to see the
current state of the system. Figure 25 shows a typical alarms window.

BNP2xr User Guide 229

Monitoring the BNP

For each alarm, you see a description, status, severity, source, cleared time (if the alarm has been
cleared), any comment, and the user who cleared the alarm.

Note: Only those alarms whose levels have been checked (Figure 25) will be displayed. The others
will be hidden until checked.

Cleared events remain in the list for historical purposes.

Figure 25. Alarms & Events tab

Alarms and Events

The following alarms are available:

• Video underflow
• PID missing
• Grooming failed

230 BNP2xr User Guide

 The Status Bar

• Missing input-Missing PAT/PMT, this could be caused by:

• A disconnected cable
• A TS packet missing or lost
• Input GigE not operational
• Cooling system failure
• Failure of ad insertion/splicing

The four severity levels include info, minor, major, and critical.

The Status Bar

The status bar is visible regardless of the tab selected. This ensures that you can see if there are any
critical alarms that need attention. The bottom portion of the window displays the IP address to which
the BNP Element Manager is connected and the highest-priority current alert. The information is
color-coded. A green IP address section indicates that the connection is active.

For alarms, the color-coding is one of the following:

• Green indicates that the alert or event displayed is informational
• Yellow indicates a situation that may need operator action
• Red indicates that an important or critical error has occurred and operator intervention is needed

Figure 26. The status bar

BNP2xr User Guide 231

Monitoring the BNP

232 BNP2xr User Guide

CHAPTER 9

Troubleshooting

This chapter describes error detection and correction procedures.

In This Chapter:
• “LED Indicators,” next.
• “Event Log Analysis” on page 234.
• “Software Upgrade” on page 234.
• “Contacting RGB Customer Support” on page 234.

LED Indicators
The LED indicators are fully described in “LED Indicators” on page 15. These should be your first
line of inquiry if any BNP2xr component is not performing correctly.

GigE 1-8 Port Status

Cfg/Pwr Fault Backup
(SFPs)
Compact Flash 10/100 BaseT Ethernet Port

Figure 27. LED Indicator Locations

Table 1. LED Indications

Indication Possible Solution

An LED indicator for one of the GigE ports is off. Verify that the module is installed correctly and has
power.
The LED indicator for the 10/100 BaseT port is Verify that the module is installed correctly and the 10/
off. 100 BaseT port cable is connected correctly.
The system power LED indicator is off. Verify that the power cord is correctly installed and that
the power is turned on.
The LED indicator for the compact flash is Install a compact flash card.
blinking red
The LED indicator for the compact flash is solid A flash error has occurred or the flash module is
red. corrupted and needs to be reformatted or replaced.

BNP2xr User Guide 233

Troubleshooting

Event Log Analysis

If asked to do so by technical support, access the event log. You will be instructed on this procedure by
the technical support engineer.

Software Upgrade
Use the Element Manager to upgrade any software image of the BNP2xr. See “Upgrading Software”
on page 100 for details about upgrading software.

Contacting RGB Customer Support

Note: For BNP products or software purchased through other distribution partners, please contact
their customer service for product support.

Before you contact Customer Support, have the following information handy:
• Serial number of the AC power supply.
• A clear description of the problem.
• Steps to reproduce the problem, if applicable.

Customers who purchased their product directly from RGB Networks, or have purchased extended
product support directly from RGB Networks should contact Customer Support via one of the
following methods:

Table 2. Contacting Customer Support

Method Details
Phone +1 (877) RGB-NETW (877-742- 6389) or +1 (408) 701-2800
Customer Portal http://support.rgbnetworks.com
Email [email protected]

234 BNP2xr User Guide

 Contacting RGB Customer Support

Searching the RGB Customer Portal

To search the RGB Customer Portal for a specific document or solution, proceed as follows:
1. Log in to the RGB Customer Portal site.

Figure 28. RGB Customer Portal home page

2. From the Customer Portal homepage, click on the Knowledge Base tab:

Direct Customers - RGB Customer Portal home Resellers - RGB Customer Portal home

Figure 29. Customer Portal home page - Direct and Reseller

3. From the Knowledge Base homepage, enter the desired search term in the Search box and tap
the[Enter]key:

Direct Customers - Knowledge Base search Resellers - Knowledge Base search

Figure 30. Knowledge Base search - Direct and Reseller

BNP2xr User Guide 235

Troubleshooting

236 BNP2xr User Guide

CHAPTER 10

Field-replaceable Units

This chapter provides instructions on replacing the Field-replaceable Units (FRUs).

In This Chapter:
• “Overview,” next.
• “Replacing a Power Supply” on page 238.
• “Replacing a Gigabit Ethernet Processor (GBP2) Module” on page 240.
• “Replacing a Processor Module (PROC2) or an ASI (or ASI2) Module” on page 242.

Overview
There are four replaceable units on the BNP2xr, shown in Figure 31. The removal and replacement
procedure is provided for each.
Front of chassis

Power supply

Rear of chassis
GBP2
module
PROC2 Modules

Figure 31. Top view of chassis, with FRUs visible

Always wear an ESD wristband or use an electrostatic mat when working with electronic components.

BNP2xr User Guide 237

Field-replaceable Units

The chassis does not need to be removed from the rack to replace a FRU, but the system must be
powered down before beginning any replacement process.

Warning: Never replace any FRU while the chassis is still connected to the power source.

If replaced items need to be configured, see Chapter 4, “System Configuration.”

Warning: Do not replace any component (such as fuses) not specifically described here. For
replacement beyond the FRU level, contact your technical support representative for
instructions on returning the component. (See “Contacting RGB Customer Support” on
page 234.)

Replacing a Power Supply

The power supply is located on the rear of the BNP2xr chassis. Any time that the chassis is not
receiving adequate power, as indicated by the system LEDs and performance, verify that power is
reaching the chassis.

If power is reaching the power supply but not getting to the system, you might need to replace the
power supply.

Removing a Power Supply

The basic procedure for removing a power supply is similar regardless of whether the power supply is
for AC or DC power.

To remove a failed power supply:

1. Ensure that you have a replacement power supply ready to reinsert.
2. Ensure that there is no power to the unit:
• AC power supply units - Shut down the unit by removing the power cable from the power
supply connector.
• DC power supply units - Toggle the circuit breaker to the OFF position. Disconnect the cables
from the power connector.
3. Loosen the power supply unit by turning the safety screw clockwise.

Note: Turning the screw counterclockwise tightens the screw. Use a slotted screwdriver to tighten or
loosen the screw, then use your fingers to further turn the screw, if necessary.

238 BNP2xr User Guide

 Replacing a Power Supply

4. Firmly grasp the power supply by the handle, shown in Figure 32.
.

Power supply insertion/

removal handle

Safety screw

Power connector

Figure 32. Power supply handle (AC power supply)

Power supply insertion/removal handle

Safety screw

Power connector

Disconnect cables from power connector

Figure 33. Power supply handle (DC power supply)

5. Pull gently but firmly, sliding the power supply out of the bay as shown in Figure 34.

R ea
r of
ch a Re a
ssi s r of
cha
s sis

Figure 34. Power supply removal (AC power supply shown at left, DC power supply shown at right)

BNP2xr User Guide 239

Field-replaceable Units

Inserting a Power Supply

Once you have removed the failed power supply, install a replacement:
1. Remove the replacement power supply from its packing and carefully inspect it for damage.
Do not install a visibly damaged power supply.
2. Slide the replacement power supply into the slot.

R ea
r of
ch a
ssis Rea
r of
cha
ssis

Figure 35. Power supply insertion (AC power supply shown at left, DC power supply shown at right)

3. Turn the screw counterclockwise to tighten it, securing the power supply to the BNP2xr chassis.
4. Connect power to the power supply:
• For AC power supplies, refer to “Connecting AC Power to the BNP2xr” on page 22.
• For DC power supplies, refer to “Connecting DC Power to the BNP2xr” on page 23.

Replacing a Gigabit Ethernet Processor (GBP2) Module

When you have determined that a GBP2 module must be replaced, follow this procedure to remove
and replace the module. You do not need to remove the chassis from its rack mount to replace a
module.

Removing a GBP2 Module

1. Ensure that you have a replacement module available, then shut down the unit by removing the
power cable from the power supply connector.
2. Remove all cabling from the module.

240 BNP2xr User Guide

 Replacing a Gigabit Ethernet Processor (GBP2) Module

3. Grasping it firmly with your fingers, gently remove the bezel on the front of the chassis, as shown in
Figure 36.

Fro
n to
fc
ha
ss
is

Figure 36. Front bezel removal

4. Using a Phillips screwdriver, loosen—but do not remove—the screws that secure both sides of the
GBP2 module to the chassis. They act as handles to assist with the module’s removal.

Loosen the
release screws

Figure 37. Loosen the GBP2 module release screws

BNP2xr User Guide 241

Field-replaceable Units

5. Firmly grasping the screws, slide the GBP2 module out of the bay, as shown in Figure 38.

Figure 38. GBP2 module removal

Replacing a GBP2 Module

After you have removed the failed GBP2 module, replace it with the new one:
1. Grasp the module firmly by the edges only and slide it into the chassis, using the plastic guide rails
to ensure proper seating.
2. Push until the module is firmly seated.
3. Using a Phillips screwdriver, tighten the insertion/removal screws to secure the GBP2 module to
the BNP2xr chassis.
4. Replace the front bezel by snapping it in place.
5. Restore any cabling and power up the unit.

Replacing a Processor Module (PROC2) or an ASI (or ASI2)

Module
Removing and replacing either a PROC2 module or an ASI module uses the same procedure.
• If you are adding a new PROC2 or ASI module to an existing but underpopulated chassis, insert the
card into the next designated slot.
• If you are replacing a failed unit, simply replace that unit regardless of the slot it occupies.

242 BNP2xr User Guide

 Replacing a Processor Module (PROC2) or an ASI (or ASI2) Module

Removing a PROC2 or ASI (or ASI2) Module

1. Shut down the unit by removing the power cable from the power supply connector.
2. Using a Phillips screwdriver, loosen—but do not remove—the insertion/removal screws, shown in
Figure 39.

Loosen the screws

Figure 39. Loosen the insertion/removal screws

3. Using the handles on either side of the module as a grip, gently but firmly slide the module out of
the chassis, as shown in Figure 40.

Re a
r of
cha
ssis

Figure 40. Remove the module

Replacing a PROC2 or ASI (or ASI2) Module

After a PROC2 module has been removed, replace it as soon as possible, or install a blank slot cover to
ensure proper air flow.

If you are leaving an empty slot, any empty slot should be fitted with a blank cover.

BNP2xr User Guide 243

Field-replaceable Units

Caution! ASI or ASI2 modules should always be replaced; no filler should be used.

To install a PROC2 or ASI (or ASI2) module:

1. Firmly hold the card by the edges or the handles and slide it into the chassis, using the plastic guide
rails to ensure proper seating.
2. Press firmly until the module seats in the chassis.

Rea
r of c
has
s is

Figure 41. Install the ASI or PROC2 module (ASI shown)

3. Using a Phillips screwdriver, tighten the insertion/removal screws to attach the card to the chassis.
4. Restore any cabling and power up the unit.
5. Reboot the system as described in “Rebooting the System” on page 108.

244 BNP2xr User Guide

CHAPTER 11

Specifications

This chapter provides the system specifications for the BNP2xr.

In This Chapter:
• “Input Interfaces/Output Interfaces” on page 245.
• “MPEG Processing” on page 245.
• “Video Formats” on page 246.
• “Audio Formats” on page 246.
• “Regulatory Compliance” on page 248.
• “Electrical/Mechanical” on page 248.
• “Environmental” on page 248.

Input Interfaces/Output Interfaces

Table 3. Input/Output Interfaces

Interface Type
Gigabit Ethernet 8 SFP interfaces (copper or optical) configured
Fast Ethernet 1 10/100BaseT control and management interface
ASI Up to 18 ASI ports per chassis
Up to 3 ASI modules with 6 ASI ports each
Software configurable as input or output
213 Mbps data rate/port

MPEG Processing

Table 4. MPEG Processing

MPEG Supported Format

Transrating SD and HD MPEG-2 video streams
VBR and CBR support
QoS - Ability to set priority for the level of transrating desired

BNP2xr User Guide 245

Specifications

Table 4. MPEG Processing (Continued)

MPEG Supported Format

Multiplexing and Table MPEG-2 and MPEG-4 H.264/AVC multiplexing and re-multiplexing
Processing MPTS, SPTS, multicast and unicast support
CBR and VBR support
PID filtering and remapping
PCR restamping and de-jitter
Generation and pass-through of PSIP tables
PAT and PMT generation
DPI Seamless SD and HD splicing
SCTE 30 (DVS-380, DVS-638) and SCTE 35 (DVS-253) compliant
SCTE 30 to SCTE 35 conversion
Text and graphical crawl messages, and graphical logo overlays
SCTE 18 (Emergency Alert message for cable)
SCTE 21 to SCTE 20 conversion
Jitter Tolerance +/- 100 ms

Video Formats

Table 5. Video Formats

Video Supported Format

MPEG Profile and Level MPEG-2 MP@ML (SD) and MP@HL (HD)
MPEG-4 H.264/AVC (all profiles supported)
All SD and HD resolutions SD – 720 x 576, 720 x 480, 704 x 480, 544 x 480, 528 x 480, 352 x 480
HD – 1080i x 1920, 1080i x 1440, 1080i x 1280, 720p x 1280, 480p x 720,
480p x 704, 480p x 640
Frame Rates 24, 25, 29.97, 30, 50, 59.94, 60

Audio Formats

Table 6. Audio Formats

Audio Supported Format

Audio Format Dolby AC-3, MPEG-1 Layer 2 (Musicam) and MPEG-2, MPEG-2 AAC,
MPEG-4 HE-AAC

246 BNP2xr User Guide

 Elementary Stream Types & Conversions

Elementary Stream Types & Conversions

Table 7. Elementary Stream Types & Conversions

Output Transport
Stream (TS) Type Videoa Audiob Data

MPEG2 MPEG2 video (0x2) MPEG1 audio (0x3) 0x5 ~ 0xff

Converts to 0x2 if input video has
MPEG2 audio (0x4)
type 0x80.
ATSC AC-audio (0x81)
H.264 (0x1B)
DVB AC-3 audio (0x6)
AAC (0x0f)
HE-AAC (0x11)
ATSC MPEG2 video (0x2) MPEG1 audio (0x3) 0x5 ~ 0xff
SCTE video (0x80) MPEG2 audio (0x4)
H.264 (0x1B) ATSC AC-audio (0x81)
Converts to 0x81 if input AC-3
audio has type 0x6.
AAC (0x0f)
HE-AAC (0x11)
SCTE SCTE video (0x80) MPEG1 audio (0x3) 0x5 ~ 0xff
Converts to 0x80 if input video has
MPEG2 audio (0x4)
type 0x2.
ATSC AC-audio (0x81)
H.264 (0x1B)
Converts to 0x81 if input AC-3
audio has type 0x6.
AAC (0x0f)
HE-AAC (0x11)
DVB MPEG2 video (0x2) MPEG1 audio (0x3) 0x5 ~ 0xff
Converts to 0x2 if input video has
MPEG2 audio (0x4)
type 0x80.
DVB AC-3 audio (0x6)
H.264 (0x1B)
Converts to 0x6 if input AC-3
audio has type 0x81.
AAC (0x0f)
HE-AAC (0x11)
a. For H.264 video, the stream type will be passed through regardless of input or output TS type.
b. For AAC and HE-AAC audio, the stream type will be passed through regardless of input or output TS type.

Digital Broadcast

Table 8. Digital Broadcast

DVB Supported Format

Digital Broadcast ATSC PSIP, (A/52B, A/53E, A/58, A/65)
DVB (DVB-SI, DVB-SUB, DVB-TXT)

BNP2xr User Guide 247

Specifications

Regulatory Compliance

Table 9. Regulatory Compliance

Regulatory Type Compliance

Safety UL, TUV/GS, cTUVus; UL 60950-1, 1st Edition; CSA C22.2 No. 60950-1-03;
IEC 60950-1:2001 (1st Edition), EN 60950-1:2001+ A11
Electromagnetic FCC Part 15, Class A, EN55022, EN55024; FCC - Title 47 CFR Part 15
Subpart B; Canada - ICES-003,Issue 2, April 1995
Hazardous Substances RoHS-compliant (Restricted use of Hazardous Substances)

Electrical/Mechanical

Table 10. Electrical and Mechanical

Specification Limits
Input Power AC: 100-240 VAC @ 3.0A/1.5A
DC: 48VDC @ 7A
Line Frequency 50-60 Hz
Power consumption 300 W maximum fully loaded at 115 VDC
Dimensions 1RU (1.75"H x 19"W x 23"L) (43.6 H x 433W x 583L mm)
Weight 25 lbs. (11.34 kg)
Cooling Front to back

Environmental

Table 11. Environmental Ranges

Condition Value Range

Storage Temperature -40° C to 70° C
Operating Temperature 0° C to 40° C
Humidity 5% to 95% (non-condensing)

248 BNP2xr User Guide

APPENDIX A

Editing the DVB NIT Table

This appendix shows you how to edit, make additions to, and delete items from the NIT table, one of
the DVB tables. To understand the meaning and context of the various values in the table, consult one
or both of the following documents:
• Digital broadcasting systems for television, sound and data services; Allocation of Service
Information (SI) codes for Digital Video Broadcasting (DVB) systems, ETSI Technical Report, ETR
162, European Telecommunications Standards Institute, October 1995.
• Digital Video Broadcasting (DVB); Specification for Service Information (SI) in DVB systems,
ETSI EN 300 468 V1.5.1 (2003-05), European Telecommunications Standards Institute.

In This Appendix:
• “NIT Values Supported,” next.
• “Naming, Viewing, Deleting and Editing NIT Configuration Files” on page 252.
• “Suggestions for Editing the NIT Table” on page 263.

NIT Values Supported

Table 12 shows the NIT values Mandatory values are indicated with an asterisk (*).

Table 12. Values Supported

NIT Section Value Name Default Range

nit_section network_id 100
Version_ Number 1
*current_next_indicator 1
Array of *name my network Any name
network_name: name
Array of linkage: *Transport stream ID 1 Any value that fits in 16 bits
*original_network ID 129 Any value that fits in 16 bits
*service_id 16642 Any value that fits in 16 bits
*linkage_type 9 Any value that fits in 16 bits
Array of data private1 Array of bytes of hex integers (if type is 8 or 9).
private_data_byte: Else it is char string

BNP2xr User Guide 249

Table 12. Values Supported (Continued)

NIT Section Value Name Default Range

Array of Freqency List *coding_type 2 0 (not defined), 1(Satellite), 2 (cable) and 3
(terrestrial)
*Center_frequency: 3300000 32 bit unsigned integers
*Private_data: private_data_1 32 bit unsigned integer (currently defined
values are) 1 (SES), 2 (BSKYB1), 3(BSKY2),
4(BSKY3) BE (BetaTechnik), 0x6000 (News
DataCom), 0x6001(NDC1), 0x6002(NDC2),
0x6003(NDC3) 0x6004(NDC4),
0x6005(NDC5), 0x6006(NDC6)
0x362275(Irdeto) 0x4E544C(NTL)
0x532D41(SFA) 0x44414E59(NEWS
DATACOM), 0x46524549(NEWS
DATACOM) 0x53415053 (SFA)
Array of Transport *transport stream id 769 Any value that fits in 16 bits
Stream *original network id 1920 Any value that fits in 16 bits
Array of service: id 16398 Any value that fits in 16 bits
type 1 1 to 0x10 and 0x80 to FE 1(digital television
service)
*id 16403 Any value that fits in 16 bits
*type 1 1 to 0x10 and 0x80 to FE 1(digital television
service)
Cable delivery *frequency 6312500 Up to 8 digit (decimals) value in MHz
system: *FEC_Outer 2 4 bit integer 0,1, 2
*modulation 4 8 bit integer (00, 01, 02,03, 04 and 05)
symbol_rate 68750 7 digit (decimals) integer specifying symbols/
second
*FEC_Inner 5 4 bit integer 0 (not defined),1 (1/2 conv code rate),
2(2/3), 3 (3/4), 4 (5/6), 5 (7/8), 6 (8/9), F (no conv
Coding
Satellite Delivery *frequency 1208400 up to 8 digits (decimal) value in GHz
System orbital_position 970 up to 4 digit (decimal) value orbital position. A
decimal occurs after the third character
west_east_flag 0 0 or 1 (0 indicates western, 1 indicates eastern)
polarization 1 0 (linear horizontal), 1 (linear vertical), 2 (circular
left) or 3 (circular right)
modulation 1 0 (not defined), 1 (QPSK), 2 (8 PSK) or 3 (16
QAM)
symbol_rate 220000 7 digit value specifing mega symbol/sec (decimal
(imaginary) occurs after third digit)
FEC_Inner 3 4 bit integer 0 (not defined),1 (1/2 conv code
rate),2 (2/3), 3 (3/4), 4 (5/6), 5 (7/8), 6 (8/9), F(no
conv Coding

250 BNP2xr User Guide

 NIT Values Supported

Table 12. Values Supported (Continued)

NIT Section Value Name Default Range

Terrestrial Delivery centre_frequency 739000000 32 bit integer (expressed in multiple of 10Hz)
System bandwidth 0 0 (8 MHZ), 1 (7 MHZ) or 2 (6 MHZ) (3 bit field)
constellation 2 0 (QPSK), 1 (16 QAM), 2 (64 QAM) (2 bit field)
*hierarcy_information 0 0 (non hierachical),1 (alpha = 1), 2 (alpha = 2), 3
(alpha=4) (3 bit field)
code_rate-HP_stream 0 0 (1/2),1 (2/3), 2 (3/4), 3 (5/6), 4 (7/8) (3 bit field)
code_rate-LP_stream 0 0 (1/2), 1 (2/3), 2 (3/4), 3 (5/6), 4 (7/8) (3 bit field)
*guard_interval 3 0 (1/32), 1 (1/16), 2 (1/8) or 3 (1/4) (2 bit field)
transmission_mode 1 0 (2k mode) or 1 (8k mode) (2 bit field)
*other_frequency_flag 1 0 (no other frequency in use) or 1 (more than one
frequency in use)
Array of Private Data data 1 32 bit unsigned integer (currently defined values
are) 1 (SES), 2 (BSKYB1), 3 (BSKY2), 4 (BSKY3)
BE (BetaTechnik), 0x6000 (News DataCom),
0x6001 (NDC1), 0x6002 (NDC2), 0x6003 (NDC3)
0x6004 (NDC4), 0x6005 (NDC5), 0x6006 (NDC6)
0x362275 (Irdeto) 0x4E544C (NTL) 0x532D41
(SFA) 0x44414E59 (NEWS DATACOM),
0x46524549 (NEWS DATACOM) 0x53415053
(SFA)
Array of Frequency coding_type 2 0 (not defined),1 (Satellite),2 (cable) and 3
List (terrestrial)
Center_Frequency 1300000

BNP2xr User Guide 251

Naming, Viewing, Deleting and Editing NIT Configuration Files

Naming a Configuration File

An opening window with no files named is shown in Figure 42. The default configuration file is
present.

Figure 42. Window With No Arrays

To name a configuration file,

252 BNP2xr User Guide

 Naming, Viewing, Deleting and Editing NIT Configuration Files

1. Click Edit. The default configuration file appears (Figure 43).

Figure 43. Default Array

2. Now enter a name for the file in the Name space, in this case Array2.
3. Click OK.
The configuration file is named as Array2. (Figure 44).

Figure 44. Array2 Added

BNP2xr User Guide 253

 Viewing a Configuration File
You can view an configuration file in XML format.
1. In Figure 44, choose View NIT in XML Format. A window similar to Figure 45 appears.

Figure 45. NIT Configuration File Viewed in XML Format

2. Navigate to where the arrays are stored and click Open. The window of Figure 46 appears.

Figure 46. Assigning a Name to a Configuration File

3. Assign the name you want to the Array. In this example, we chose Array2.

254 BNP2xr User Guide

 Naming, Viewing, Deleting and Editing NIT Configuration Files

Deleting a Configuration File

1. To delete an array, highlight the array to be deleted in Figure 44.
2. Click Delete.
3. The delete confirmation box appears (Figure 47).

Figure 47. Delete Confirmation

4. Click Yes if you want to delete the configuration file

The Array is deleted.

BNP2xr User Guide 255

 Editing a Configuration File
1. Highlight the configuration file you want to edit (Figure 48).

Figure 48. Setup Network Information Table screen

2. Click Edit. The window of Figure 49 appears.

Figure 49. Editing Window

256 BNP2xr User Guide

 Naming, Viewing, Deleting and Editing NIT Configuration Files

Icon Menu

Figure 49 shows the icons appearing at the top of the window.

Remove Node
Move Node Up

Move Node Down

Open Namespace Qualifier Window
Insert Node Before
Find Invalid Node
Insert Node After Search
XML Editor XML Viewer

Figure 50. Icon Menu

BNP2xr User Guide 257

 Figure 51 shows the Namespace Qualifiers window, obtained when you click the Namespace Qualifier
icon

Figure 51. Namespace Qualifier Window

Figure 52 shows the Search window, obtained when you click the Search icon.

Figure 52. Search Window

258 BNP2xr User Guide

 Naming, Viewing, Deleting and Editing NIT Configuration Files

Expanding the NIT Edit Window

The vertical bars shown in the window of Figure 49 are used to toggle between an expanded and
reduced view. through show three layers of expansion. Clicking the large vertical bar compresses the
display as shown in Figure 53.

Figure 53. Large Vertical Bar Clicked Fully Compress

Figure 54 shows the first level of expansion from Figure 49, obtained by clicking all of the small bars
to the right of the large bar.

Figure 54. First Level of Expansion

BNP2xr User Guide 259

 Clicking all of the smaller bars in Figure 54 creates the second level of expansion shown in Figure 55.

Figure 55. Second Level of Expansion

Clicking the smaller bars in Figure 55 creates the third level of expansion shown in Figure 56.

Figure 56. Third Level of Expansion

260 BNP2xr User Guide

 Naming, Viewing, Deleting and Editing NIT Configuration Files

Inserting a Node

To insert a node, select the node and click Insert Node Before (Figure 57).

Figure 57. Inserting a Node Before

Figure 58shows the result.

Figure 58. Node Inserted Before

BNP2xr User Guide 261

 3. In the node that was added, we attempted to change the value of the transport stream to an alpha
value, ‘a.” An error message resulted (Figure 59).

Figure 59. Error Message from Wrong Type of Data Character

4. Using the proper data types we changed the values so they are different from the original ().

Figure 60. Data Type Mismatch Corrected

262 BNP2xr User Guide

 Suggestions for Editing the NIT Table

Deleting a Node

You can delete a node. In the example, highlight the linkage to be deleted and click Remove Node. The
node is deleted (Figure 61).

Figure 61. Linkage Deleted

Suggestions for Editing the NIT Table

The following are some suggestions that may prove helpful in editing the NIT table:
• In editing fields, go to the next tab to apply
• When adding new nodes or fields, it is easiest to right click on the node to be added, then choose
Insert.
• Uncheck optional fields if they are not needed.

BNP2xr User Guide 263

264 BNP2xr User Guide
Information to Users

United States

DECLARATION OF CONFORMITY

Responsible Party Name: RGB Networks, Inc.

Address: 390 West Java Drive
Sunnyvale, CA 94089, U.S.A.
Telephone: (877) 742-6389
Declares that product: Broadcast Network Processor—BNP2xr
Complies with Part 15 of the FCC Rules.

This device complies with Part 15 of the FCC Rules. Operations are subject to the following two conditions:
(1) This device must not be allowed to cause harmful interference; (2) This device must accept any interference
received, including interference that may cause undesired operation.

Modyifying the equipment without RGB Networks’ authorization may result in the equipment no longer
complying with FCC requirements for Class A or Class B digital devices. In that event, your right to use the
equipment may be limited by FCC regulations, and you may be required to correct any interference to radio or
television communications at your own expense.

For Class A Equipment

Note: This equipment has been tested and found to comply with the limits for a Class A digital device,
pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection
against harmful interference when the equipment is operated in a commercial environment. This
equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in
accordance with the instruction manual, may cause harmful interference to radio communications.
Operation of this equipment in a residential area is likely to cause harmful interference in which case
the user will be required to correct the interference at his own expense.

Canada
This Class A digital apparatus complies with Canadian ICES-003.
Avis de conformité à la réglementation d’Industrie Canada.
Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada.

BNP2xr User Guide 265

Information to Users

European Declaration of Conformity

RGB Networks, Inc., declares that the product Broadcast Network Processor, BNP2xr to which this declaration
relates is in conformity with the following standards:
• CISPR 22:2005
• EN55022:2006
• EN55024:1998 + A1:2001 + A2:2003
• EN61000-4-2: ESD immunity
• EN61000-4-3: Radiated RF field immunity
• EN61000-4-4: Immunity to electrical fast transients
• EN61000-4-5: Surge immunity
• EN61000-4-6: RF conducted immunity
• UL / CUL / CB 60950-1 1950

This product follows the provisions of the EMC Directive 2004 / 108 / EC and carries the CE marking
accordingly.
Support Tel: 877-RGB-NETW
FAX: (408) 701-2710

266 BNP2xr User Guide

 Glossary

This glossary defines the acronyms common in the video industry, and used in this guide. It is not all-
inclusive but serves as a reference.

Numeric

3DES Triple Data Encryption Standard. A mode of DES that encrypts data three
times. Three 64-bit keys are used, for an overall key length of 192 bits.

AES Advanced Encryption Standard. AES is a privacy transform for IPSec and
Internet Key Exchange, and is replacing the Data Encryption Standard (DES).
AES offers a larger key size and a variable key length.
Alpha Channel In reference to editing image files, an alpha channel stores selections as
grayscale images. Adding alpha channels to an image allows the creation and
storing of masks in order to manipulate or protect parts of an image.
ARP Address Resolution Protocol. ARP broadcasts a packet containing the IP
address that the sender specifies to all hosts attached to an Ethernet
connection. When the target recognizes that the IP address is its own, it returns
a response.
ASI Asynchronous Serial Interface. ASI extends the functionality from strictly a
video/audio-bounded device to a transport stream-based system that can store
data in either a single program stream or a set of multiple program streams.
ATSC Advanced Television Systems Committee. ATSC is working to coordinate
television standards among different communications media. ATSC is also
developing digital television implementation strategies.

CA Conditional Access. Conditional access is an encryption/decryption

management method by which a broadcaster controls a subscriber's access to
services.
CAS Conditional Access Systems. These are systems that ensure broadcast service
is accessible only to those entitled to access, usually by scrambling or
encrypting the service.
CBR Constant Bit Rate. Constant bit rate encoding ensures that the rate at which a
codec's output is consumed is constant. Because it is the maximum bitrate that
matters, CBR is useful for streaming multimedia content on limited capacity
channels. See also VBR.
CSA Common Scrambling Algorithm.

BNP2xr User Guide 267

Glossary

DCCT Direct Channel Change Table, part of 9 tables in the ATCS PSIP. The DCCT
instructs the receiver to change channels based on viewer preferences,
demographics or geographical location. This table works with a DCCSDT in
the set top box.
DCCSDT DCC Selected Code Change Table, part of 9 tables in the ATCS PSIP.
DES Data Encryption Standard. DES specifies a FIPS approved cryptographic
algorithm as required by FIPS 140-1. Encrypting data converts it to an
unintelligible form called cipher. The cryptographic security of the data
depends on the security provided for the key used to encipher and decipher the
data. Data can be recovered from cipher only by using exactly the same key
used to encipher it.
DET Data Event Table, part of 9 tables in the ATCS PSIP. The DET announces the
data portion of a video/audio/data event when the data event does not match
the exact duration of an video/audio event.
DHCP Dynamic Host Configuration Protocol. DHCP servers let individual computers
on an IP network extract their configurations. DHCP servers have no specific
information about the individual computers until they request the information.
DOCSIS Data Over Cable Service Interface Specifications. Now known as CableLabs
Certified Cable Modems. DOCSIS specifies modulation schemes and the
protocol for exchanging bidirectional signals over cable.
DPI Digital Program Insertion. The digital splicing of one MPEG program
(typically a commercial) into another based on digital cues within the MPEG
transport stream.
DVB Digital Video Broadcast. A European set of defined transmission standards for
digital broadcasting systems.
DWDM Dense Wavelength Division Multiplexing. A fiber-optic transmission
technique using light wavelengths to transmit data parallel-by-bit or serial-by-
character.

EAS Emergency Alert System. An operational structure for national and local
emergency alerts used by broadcast, cable, and wireless cable.
EBIF Enhanced Binary Interchange Format. EBIF standard provides a solution for
the delivery of interactive data to existing set-top boxes (STBs), including
older models of STBs. EBIF condenses interactive applications in order to use
the minimal STB resources available for interactive data delivery
EISS ETV Integrated Signaling Stream data ES — carries timing signals that trigger
events associated with the user-agent application loaded onto the STB.
ECM Entitlement Control Messages.
ECMG ECM Generator.

268 BNP2xr User Guide

 Glossary

EIT Event Information Table, part of 9 tables in the ATCS PSIP. EITs are
associated with a specific virtual channel in the VCT, contain event
information, and point to the location of extended text in the ETT. Each EIT
PID contains 3 hours worth of events per program.
EM Element Manager. The graphical user interface for the BNP.
EMM Entitlement Management Message. A packet containing the information
necessary to decrypt the picture.
EMMG Entitlement Management Message Generator. The component of the
conditional access headend that delivers entitlements to the multiplexers.
EOD Everything-On-Demand.
ES Elementary Stream, an individual audio, video, or data output stream that is
transmitted in a program.
ETT Extended Text Table, part of 9 tables in the ATCS PSIP. ETTs carry longer text
messages than EITs for describing events and virtual channels.
ETV Enhanced Television.

FCC Federal Communications Commission. The agency that regulates

communications services, including cable television, at the Federal level.
FPGA Field Programmable Gate Array. An array of logic gates that can be hardware-
programmed to fulfill user-specified task.
FVOD Free-Video-On-Demand.

GigE Gigabit Ethernet. Ethernet which supports data transfer rates of 1 Gigabit
(1,000 megabits) per second.
GBP /GBP-2 Gigabit Ethernet Processor module.
GUI Graphical User Interface.

HD High Definition. High-resolution digital television combined with Dolby

Digital surround sound (AC-3).
HFC Hybrid Fiber/Coax. A distribution system combining fiber and coax cable. An
HFC system is used to distribute CATV signals into a neighborhood.

BNP2xr User Guide 269

Glossary

IGMP Internet Group Management Protocol. IP hosts use IGMP to register dynamic
multicast group membership. Connected routers discover the group members
using the same protocol.
IP Internet Protocol. The network layer for the TCP/IP Protocol Suite. It is a
connectionless, best-effort packet switching protocol.
ITU International Telecommunication Union. An international organization through
which governments and the private sector coordinate global
telecommunications networks and devices.

JRE Java Runtime Environment. JRE is made up of the Java virtual machine, the
Java platform core classes, and supporting files.

LED Light Emitting Diode. A semiconductor diode that emits light when current
passes through it. LEDs are used as indicators.

MGT Master Guide Table, part of 9 tables in the ATCS PSIP. MGT provides
program-identification (PID) locations so a receiver can find the other tables,
and informs the receiver of changes or table updates.
MIB Management Information Base. MIB defines the variables needed by the
SNMP protocol to monitor and control elements in a network.
MID Mid-plane.
MPEG Moving Pictures Experts Group. The standards group and the standard for
compression and storage of motion video.
MPTS Multi-Program Transport Stream. A combined multiplex of video streams.
MUX Multiplexer. A device that both combines multiple data sources into a single
data stream for transmission, and demultiplexes the single data stream into its
composite forms.

NTP Network Time Protocol. A TCP protocol that assures accurate local time-
keeping with reference to radio and atomic clocks, and can synchronize
distributed clocks within milliseconds.
NTSC National Television System Committee. Committee that defined the current
standard for analog color television in North America, as well as the name for
the standard. The format is 525 lines in 4MHx of video bandwidth.

270 BNP2xr User Guide

 Glossary

OOB Out-Of-Band.

PAT Program Association Table. A table ID that indicates the MPEG-2 SI packet
type.
PCR Program Clock Reference.
PMT Program Map Table. A table ID that indicates the MPEG-2 SI packet type.
PNG Portable Network Graphics. PNG format is used for lossless compression and
for display of images on the web. Unlike GIF, PNG supports 24-bit images and
produces background transparency without jagged edges. PNG format supports
RGB, Indexed Color, Grayscale, and Bitmap mode images without alpha
channels. PNG preserves transparency in grayscale and RGB images.
PSI Program Specific Information, as part of MPEG-2.
PSIP Program and System Information Protocol. PSIP is a collection of nine tables
that allow the DTV transport stream to provide information about a station's
services and programming. These nine tables include:

Master Guide Table (MGT)

System Time Table (STT)
Virtual Channel Table (VCT)
Rating Region Table (RRT)
Event Information Table (EIT)
Extended Text Table (ETT)
Data Event Table (DET)
Directed Channel Change Table (DCCT)
DCC Selected Code Change Table (DCCSDT)

QAM Quadrature Amplitude Modulation. This is the modulation technique used in

systems carrying digital video.
QoS Quality of Service. Guarantees network bandwidth and availability for
applications.

RF Radio Frequency. Television signals are modulated onto RF signals and are
then demodulated by the television tuner.

BNP2xr User Guide 271

Glossary

RTP Real Time Protocol. RTP provides services such as payload type identification,
sequence numbering, time-stamping, and delivery monitoring to real-time
applications.
RU Rack Unit. A common increment of equipment space height. The height of 1
RU is 1.75 inches.

SAP Secondary Audio Program. A way to provide a second audio channel within a
TV broadcast channel. Commonly used for stereophonic sound or bilingual
audio tracks.
SCTE Society of Cable Telecommunications Engineers. An organization that
develops training for cable television installers and engineers and standards for
the cable industry.
SD Standard definition.
SFP Small Form Factor Pluggable. An optical interface that is used in network
switches for Fibre Channel, Gigabit Ethernet and InfiniBand.
SNMP Simple Network Management Protocol. A protocol used to monitor and
control network devices, and to manage configurations, statistics collection,
performance, and security.
SPTS Single Program Transport Stream.
SSM Source Specific Multicast. A way to deliver multicast packets whereby only
packets delivered to a receiver are those that have originated from a specific
source IP address that has been requested by the receiver.
STP Strip Processor. The STP modules (NP and ASI) is one of the units that
comprise the BNP.
STT System Table Time. Allows a broadcaster to present time indicators to the
consumer, ensuring that the time is synchronized.
SVOD Subscription-Video-on-Demand. This is a Video-on-Demand service offered
by subscription, providing viewers with access to select programs from the
libraries of featured cable networks.

TFTP Trivial File Transfer Protocol. TFTP uses UDP and is often used by servers to
boot diskless workstations, X-terminals, and routers.
TS Transport Stream, the result of multiplexes--or combined--audio, video, or
other data content that is packaged and transmitted through the broadcast
network.
TVCT A Terrestrial Virtual Channel Table is a mandatory PSIP table that lists all the
virtual channels available in an ATSC transport stream, and optionally, virtual
channels available in other ATSC transport streams.

272 BNP2xr User Guide

 Glossary

UDP User Datagram Protocol. A connectionless protocol that runs on top of IP

networks. UDP provides a direct way to send information over an IP network.
It is used primarily for broadcasting messages over a network.

VBI Vertical Blanking Interval. A portion of a television signal that carries non-
audio/video data, such as closed-caption text.
VBR Variable Bit Rate. VBR streams vary in bandwidth over time.
VCT Virtual Channel Table, part of 9 tables in the ATCS PSIP. The VCT contains a
list of all the channels that are or will be online, along with their channel name
and number. This table contains the set of data that enables a receiver to tune
and locate the service being broadcast.
VOD Video-on-Demand. Video-on-demand systems allow users to watch video
content over a network as part of an interactive television system, either by
streaming or by download.

XFP 10 Gigabit Small Form Factor Pluggable (SFP). The XFP is a pluggable, hot-
swappable optical interface for 10 Gigabit SONET/SDH, Fibre Channel,
Gigabit Ethernet, and other applications. XFP modules are optical transceivers,
typically 1310nm or 1550nm. Optical XFPs include digital diagnostics.

BNP2xr User Guide 273

Glossary

274 BNP2xr User Guide

 Index

Numerics configure passwords 57

connecting power 22
19-inch rack 18 crawl 5
creating
A transport stream 119, 123, 129, 133, 135
AAA 53 creating multiple TS 120
AAA default IP 61 crossover cable 14
AAA default port 61 Customer Support
AAA default protocol 61 Contacting 234
AAA Protocol 57 CVCT 132
AAA servers 59
Account level D
administrator 58
default gateway 47
user 58
deleting 155
Ad Server 209
streams 155
ad splicing 213
Deleting Servers 64
Adding AAA servers 59
descriptor rules 215
advanced messaging 5
Digital Program Insertion (DPI) 207
air flow 18
document audience 2
Alarms 229
document organization 1
Viewing 229
DPI Based
alpha channel 85 Ad Splicing 5
alpha channels 6, 85
DTV transport stream 132
antistatic mat 14
DVB Transport Stream 135
applying power 22, 23, 24
ASI 6
assumptions 2 E
authentication, authorization and accounting EAS 5
(AAA) 53 audio override 5
audio stream insertion 5
B configuration 65
EBIF 211, 212, 214, 217, 218, 220, 221, 222, 268
bit rate 161 late-bind 223
Bitrates
pre-bind 216, 219, 223
Monitoring 202
pre-bind, network 223
bracket
pre-bind, passthrough 216, 217
rack mount 13
pre-bind, passthrough,keep 220
pre-bind. passthrough, keep 220
C Edit AAA Server 59, 61
cable, crossover 14 Edit AAA Server Order 63
Caution Edit AAA Server window 60
mounting location and environmental Editing AAA servers 59
conditions 19 Editing an AAA server 60
Change Password 58 EISS 212, 214, 218, 220, 222
Change server order 62 electrostatic precautions 14
chassis 3 Element Manager 1, 27, 28, 29, 30, 31, 32, 33, 100,
ground 21 103, 111, 213, 217, 219, 221, 223, 226, 234
IP Address 47 menu descriptions 32
view 33 Element Monitor
Chassis Redundancy 39 reboot with 108
compact flash 15, 16, 26, 233 Element Stream 172
components 14 elementary stream 199
configure Global AAA parameters 55 emergency alert system 5

BNP2xr User Guide 275

Index

Enable 56 chassis 47
enhanced television (ETV) 211 IPaddress
enhanced television binary interchange format determining (with DHCP running) 48
(EBIF) 211
ES 198
ESD 14, 237
J
wrist strap 14 Java 1, 28, 103, 104
Ethernet Control Port 34 JRE 28
Ethernet control port 47
ETV 211, 212, 223 L
configuration 218, 219, 221, 224
placeholder ES 215 late-bind 223
pre-bind 223 source 225, 226, 228
ETV integrated signaling stream (EISS) 212 LED indicator 233
Events 229 LEDs 233
Viewing 229 LEDs, defined 15
Light Emitting Diodes, see LEDs
Local screen 58
F local user account 57
fast Ethernet 26, 47 Local, 55
Field-replaceable Unit see FRU login 30, 31
force redundancy 46 logo overlay 65
Force Sync 42 positioning 87
front bezel 14, 15, 241, 242 zone configuration 86
front panel 14, 15
FRU 238 M
FTP 101
mapping 157
mapping scheme, SFP port 16
G master guide table 132
gateway 47 mat, antistatic 14
GBP menus
installation 240 chassis view 33
GBP module 18 software upgrade 234
GigE 6, 8, 9, 15, 21, 26, 34, 48, 49 message system
IP address 49 operator alert messages 72
GigE ports 112 messaging system
Global 55 configuration 65
Grooming 4, 156, 166 MGT 132
grooming 111 mirroring
ground removing 50
chassis 21 modifying
grounding 13, 14, 21 programs 149
streams 149
module
H GBP module 18
HRC 26 MSO 211
Multiple IP Creation 120
multiple TS creation 120
I Multiple UDP Creation 120
Input Source 113, 115 multiplex 131
installation 22, 23 Multiplexing 4
rack mount 18
requirements 13
installing 13 N
XFPs 22 Network Information Tables (NIT) 137
intended audience 2 Network Information Tables, see NIT
IP Address 39 NIT
IP address 30 nut, M4 21

276 BNP2xr User Guide

 Index

O S
overlay 5 scheduler 157
SCTE 30 5, 207, 209
SCTE 35 5, 207, 209
P SCTE Transport Stream 133
PAL content 39 serial port 14, 15
Panel 14 Server Order Behavior 63
passthrough 216, 217, 220 Servers 55, 59
keep 220 Servers tab 58, 61, 62
passwords 58 service-level redundancy 9
PID 131 services
PNG 6, 85 stopping 108
port set-top boxes (STBs) 211
mapping scheme 16 SFP
port connection mapping schemes 16
connecting ports 26 Shared Secret 61
port mirroring 49 Single Program Transport Stream (SPTS) 124
Portable Network Graphics 6, 85 software upgrade 234
power cord 13 Standby Chassis 42
power cycle 108 Status Bar 231
power supply STB 211, 212
removing and replacing 238 stop service 108
power, applying 22, 24 STP module 18, 243
pre-bind 212, 213, 216, 217, 219, 220, 221, 223 Streams
program descriptors Deleting 155
managing 196 Modifying 149
programs 155 streams
deleting 155 deleting 155
modifying 149 modifying 149
PSIP 113, 132 STT 132
Switched Digital Video (SDV) 7
Q synchronize
input to output 159
Quality of Service (QoS) 4

T
R
tables 132
rack mount 13, 18, 240 TACACS+ 57, 63
bracket 13 TACACS+. 53
RADIUS 53 temperature
Radius 57, 63 operating 19
reboot 32, 101, 108, 109, 244 storage 19
Redundancy 46 Terrestrial Virtual Channel Table 132
redundancy 10, 26 time zone 38
Chassis-level 10 tools required 13
configure 44 transparency 85
force change 46 transport stream
Redundant Chassis Configuration 39 creating 119, 123, 129, 133, 135
regroom transport streams 112
program redundancy 107 Transrating 4
regrooming 107 TVCT 132
regulatory 239
Remote Only 57
Remote user 53 U
Reordering Server List 62 Unreferenced PID 183
requirements for installation 13 user agent 211
RGB 85 User Authentication 55
RRT 132

BNP2xr User Guide 277

Index

V
view
front 14
Virtual IP Address Configuration 40

W
Warning
do not replace fuses 238
replacing FRU while power up 238
use ESD 14
wire strippers 21

X
X Y coordinates 87
XFP
installation 22

278 BNP2xr User Guide