Download - IPE Manual.book(IPE Cover.fm)DVB DSM-CC multiprotocol encapsulation standard. The IPE output is an MPEG-2 transport stream on a DVB MPEG-2 ASI/SPI physical interface. The IPE feeds

Novra IP Encapsulator

Operator’s ManualJan 2011

Page ii

Novra IPE 090-38202-02OM

Please read this entire guideVeuillez lire entièrement ce guideBitte das gesamte Handbuch durchlesenSírvase leer completamente la presente guíaSi prega di leggere completamente questa guida

Important

Please read this entire guide before you install or operate this product. Give particular attentionto all safety statements.

Important

Veuillez lire entièrement ce guide avant d’installer ou d’utiliser ce produit. Prêtez une attentionparticulière à toutes les règles de sécurité.

Zu Beachten

Bitte lesen Sie vor Aufstellen oder Inbetriebnahme des Gerätes dieses Handbuch in seinerGesamtheit durch. Achten Sie dabei besonders auf die Sicherheitshinweise.

Importante

Sírvase leer la presente guía antes de instalar o emplear este producto. Preste especialatención a todos los avisos de seguridad.


Page iii

Notices

Trademark Acknowledgments

Novra is a registered trademark of Novra Technologies, Inc.

The Novra logo is a registered trademark of Novra Technologies, Inc.

All other trademarks shown are trademarks of their respective owners.

Disclaimer

Novra Technologies Inc. assumes no responsibility for errors or omissions that may appear inthis publication. Novra reserves the right to change this publication at any time without notice.

Copyright

©2011 Novra Technologies Inc. All rights reserved. Printed in Canada.

Information in this publication is subject to change without notice. No part of this publicationmay be reproduced or transmitted in any form, by photocopy, microfilm, xerography, or anyother means, or incorporated into any information retrieval system, electronic or mechanical,for any purpose, without the express permission of Novra Technologies Inc.

Safety

For safety information, refer to the separate Safety and Important Safeguards Guide packagedwith this product.

Page iv


Revision History

Date Nature of Revision Release

May 2004

December 2004

August 2005

September 2005

October 2005

February 2006

May 2006

July 2006

October 2006

September 2007

January 2008

May 2008

August 2008

Jan 2011

Initial Release

SI / Replication Update

Additional Transport Stream Manager documentation

Added IPE-410

Added APPLY CONFIGURATION to the TS Manager

Added symbol rate recalculation, IGMP support, NTP client support, and enhanced error reporting

Added DVB-S2 CCM support, and input PID pass through support

Added contact closure update

Added “View Input PID’s...”, updated IPE Status indica-tions, updated IPE-410 external alarm input, and updated Troubleshooting

Added IPE-520

Update the redundancy contact closure pinoutsUpdated fixed key

Applied fixed key to PID Properties

Added route Heart Beat, updated information on the Enable External Input Signal

Add Windows 7 Support

1.0

1.1

1.2

1.3

1.31

1.32

1.33

1.34

1.35

1.36

1.37

1.38

1.39

1.40


Page v

Page vi


Novra IPE 090-38202-02OM Page vii

Preface

Text Conventions

• Text appearing in Courier font indicates characters to be typed in; e.g.type Shell indicates that the word “Shell” must be entered exactly as itappears, with the first letter capitalized.

• Text appearing in Bookman Old Style font indicates a directory path orfilename; e.g. c:\Program Files.

• Text appearing in SMALL CAPS and Century Gothic font in an instructionindicates either a button that must be clicked, a key that must be pressed,a field that must be entered or a particular screen; e.g. BUTTON indicates abutton that must be clicked.

Page viii Preface


Definitions, Abbreviations and Acronyms

10BaseT 10 Mbps, baseband, transmission twisted pairs

100BaseT 100BaseTX100 Mbps, baseband, transmission twisted pairs

ABR Available Bit Rate

ANSI American National Standards Institute

ARP Address Resolution Protocol

ASI Asynchronous Serial Interface

ATM Asynchronous Transfer Mode

ATSC Advanced Television Standards Committee

BAT Bouquet Allocation Table

CA Conditional Access

CACS Conditional Access and Control

CAT Conditional Access Table

CBR Constant Bit Rate

COTS Commercial Off-The-Shelf

CRC Cyclic Redundancy Check

CSS Communications Server System

DAVIC Digital Audio-Visual Council

DS Data Server

DSM-CC Digital Storage Media - Command and Control

DSN Domain Name Server

DVB Digital Video Broadcast

DVB Data Hub Asymmetric Multimedia Information System

DVB-S DVB over Satellite

EIT Event Information Table

GBR Guaranteed Bit Rate

GOP Group Of Pictures

GUI Graphical User Interface

IEC International Electrotechnical Commission

IEEE Institute of Electrical and Electronics Engineers

IGMP Internet Group Management Protocol

IP Internet Protocol

IPE IP Encapsulator

IRD Integrated Receiver Decoder

IPSec IP Security

ISDN Integrated Service Digital Network

ISO International Organization for Standardization

ISP Internet Service Provider

LMDS Local Multipoint Distribution System

MAC Media Access Control


Preface Page ix

MIB Management Information Base

MMDS Microwave Multipoint Distribution System

MPEG-2 Moving Picture Experts Group

NAT Network Address Translation

NIC Network Information Card

NIT Network Information Table

NMI Network Management Interface

NMS Network Management System

NTP Network Time Protocol

NTSC National Television System Community

ODBC Open DataBase Connectivity

OS Operating System

PAL Phase Alternative Line

PAT Program Allocation Table

PBR Peak Bit Rate

PCR Program Clock Reference

PDN Public Data Network

PID Packet IDentifier

PMT Program Map Table

POTS Plain Old Telephone Service

PPP Point-to-Point Protocol

PPTP Point-to-Point Tunnelling Protocol

PS Proxy Server

PSI Program Specific Information

PSTN Public Switched Telephone Network

QoS Quality of Service

RADIUS Remote Authentication Dial In User Service

RCR Return Channel Router

RIP Routing Information Protocol

SCTE Society of Cable Telecommunications Engineers

SDI Serial Digital Interface

SDT Service Description Table

SI Service Information

SMPTE Society of Motion Picture and Television Engineers

SMS Subscriber Management System

SNMP Simple Network Management Protocol

SQL Structure Query Language

ST Stuffing Table

TCP Transmission Control Protocol

TCP/IP Transmission Control Protocol/Internet Protocol

Page x Preface


TDT Time and Date Table

TOT Time Offset Table

UDLR Uni-Directional Link Routing

UDP User Datagram Protocol

UBR Unspecified Bit Rate

URL Uniform Resource Locator

VBR Variable Bit Rate

VPN Virtual Private Network


Preface Page xi

Protocols and Standards

10BaseT IEEE 802.3 10Base-T Standard

100BaseT IEEE 802.3 100Base-T Standard

ANSI American National Standards Institute, web.ansi.org

ARP Address Resolution Protocol

ASI Asynchronous Serial Interface

DAVIC Digital Audio-Visual Council, www.davic.org

DSM-CC ISO/IEC 13818-6

DVB Digital Video Broadcast Project, www.dvb.org

DVB-S ETS 300 421 Digital Satellite Transmission Systems

IEEE Institute of Electrical and Electronic Engineers, www.ieee.org

ISO/IEC International Organization for Standardization, www.iso.ch

IP RFC 791 Internet Protocol, Version 4 (IPv4)

IPSec RFC 2401, Security Architecture for the Internet Protocol

MIB Management Information Base

MMDS DVB (M)MDS ETS 300 748 & ETS 300 749 Digital (Micro-wave) Multipoint Distribution Systems (MDS)

MPEG-2 Moving Picture Experts Group: Generic Coding of Moving Pictures and Associated Audio Information ISO/IEC DIS 13818

ODBC Open DataBase Connectivity

PPP RFC 1661, Point-to-Point Protocol

PPTP Point-to-Point Tunnelling Protocol

RADIUS RFC 2138, Remote Authentication Dial In User Service

RIPv2 Routing Information Protocol, Version 2

SMPTE 325M SMPTE 325M-1999 Opportunistic Data Broadcast Flow Control; RP 206-1999 Opportunistic Data Flow Control Using Ethernet as a Control Channel in an MPEG-2 Trans-port Emissions Multiplex

SNMP RFC 1905, Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)

SQL ISO/IEC 9075:1992, Information Technology Database Lan-guages - SQL & ANSI X3.135-1992, Database Language SQL

TCP RFC 793, Transmission Control Protocol

TCP/IP Transmission Control Protocol/Internet Protocol

Page xii Preface


Novra IPE 090-38202-02OM Page xiii

Contents

Notices iiiTrademark Acknowledgments iiiDisclaimer iiiCopyright iiiSafety iiiRevision History iv

Preface vii

Text Conventions vii

Definitions, Abbreviations and Acronyms viii

Protocols and Standards xi

CHAPTER 1 IPE Overview 1

IPE Specifications 1IPE Models 1Key Features 2Management 2Input Physical Interfaces 2Output Physical Interfaces 3Protocols Supported 3Compliance 3Operating Specifications 3Hardware Specification 4Option Packs 4

Transport Streams 5

Traffic Profiles and PIDs 5Multiprotocol Encapsulation Traffic Profiles 6Remux Channel 7SI Tables 7Opportunistic Data Traffic Profiles 8

Page xiv Contents


Signaling Marker 12ATM Profile 12Forward Link Signalling 13Population ID 13Rate Limiting 13

IPE Management 13Rank 14Mode 14RIP Parameters 14State 15Status 15NTP parameters 16Enable External State Signal 16

External Contact Closure Outputs 17

CHAPTER 2 Installing the IPE 19

Checking the Equipment 19

Facility Interfaces Required 20

Cable Connections 20

Configuring IP Addresses 22Changing IP Addresses 23

Installing the User Interfaces 24Installing the IPE Management Software 24

Connecting to Your Facility 24Installing the IPE Hardware 24

Powering Up for the First Time 25

IPE Interfaces and Routing 26

CHAPTER 3 Transport Stream Management 27

Managing Transport Streams 27

IPE Configuration Interface 28IPE Configuration State 28Applying a Configuration 29Configuration Errors 29

Transport Streams 30Creating a Transport Stream 30Setting Transport Stream Service Information Settings 32View/Modify Transport Stream Parameters 35Deleting a Transport Stream 35

Traffic Profiles 35Creating a Traffic Profile 35View/Modify Traffic Profile Parameters 40Deleting a Traffic Profile 40

PIDs 41Creating a PID 41View PID Parameters 46Modify PID Parameters 47Deleting a PID 47


Contents Page xv

ATM Virtual Channels 48Adding a Virtual Channel 48View/Modify Virtual Channel Parameters 49Deleting a Virtual Channel 49

Routes 49Adding a Route 49View/Modify Route Parameters 51Deleting a Route 51

Database Backup 52Exporting Transport Streams 52Importing Transport Streams 52

CHAPTER 4 Configuring the IPE 55

IPE Control Panel 55Launching IPE Control Panel 55

Configuring the IPE 56Assigning Transport Stream(s) 57Configuring Mode Parameters 58Enable External Input Signal 58Configuring RIP Parameters 59Configuring NTP Parameters 59

Monitoring the IPE 59

IP ENCAPSULATORS Sub-panel 59Real-Time Statistics 62Historical Statistics 67

CHAPTER 5 Maintaining the IPE 71

Visual Inspections 71Air Passages 71Cables 71

Cleaning the Unit 72

CHAPTER 6 Troubleshooting 73

General Troubleshooting Tips 73IPE Control Panel 74Hard Drive Replacement 74

Page xvi Contents


Novra IPE 090-38202-02OM Page 1

CHAPTER 1 IPE Overview

This chapter introduces the IP Encapsulator (IPE) technology. The IPEreceives Ethernet traffic over the 10/100/1000BaseT traffic LAN. The IP data-grams are then encapsulated into a DVB MPEG-2 transport stream, using theDVB DSM-CC multiprotocol encapsulation standard. The IPE output is anMPEG-2 transport stream on a DVB MPEG-2 ASI/SPI physical interface. TheIPE feeds this stream into a multiplexer, or directly into a DVB-S modulator,from which the stream is transmitted over the satellite path to the receiver.DVB-S receivers capture TS packets based on PID numbers. If a receiver isconfigured to listen to a particular PID, then all TS packets sent on the givenPID are captured by the receiver; otherwise, the receiver drops all TS packetsof other PIDs. IP datagrams are extracted and forwarded up through the TCP/IP stack to the end application.

IPE Specifications

The following specifications describe the IPE performance, operating andhardware characteristics.

IPE Models

• IPE-410:

One rack unit high

Flash Hard Disk Drive

• IPE-520:

Two rack units high

High availability platform with redundant power supplies and mirroredhard disk

Expansion PCI slot

Built on highly reliable industrial chassis with Quad Core Intel proces-sor and up to 4 GB of memory.

IPE Overview


Gigabit Traffic and Management NIC’s

Key Features

• Supports up to 8192 simultaneous PIDs

• Advanced scheduling algorithm for bitrate control

• Ten traffic profiles:

Dedicated PID Bundle - Constant Bit Rate (CBR)

Shared PID Bundle - Variable Bit Rate (VBR)

Uncommitted PID Bundle - Unspecified Bit Rate (UBR)

Remux (optional)

Opportunistic (Conditional/Strict)

Uncontrolled Opportunistic

Signaling Marker

ATM Profile

SI Tables

Forward Link Signaling

• 8192 priority levels and 64 precedence levels

• Layer 3 IP routing

• Level 1 multicast routing

• Hardware scrambling option

• PSI/SI tables support

• Output bitrate settings from 1 Kbps to 200 Mbps (±5 bps)

• Latency of 1 millisecond

• Real-time statistics monitoring

• Layer 2/3 ATM routing

Management

• Supports SNMPv2c statistics gathering and standard MIB II informationretrieval

• Hardware WatchDog timer

• Transport Stream Manager graphical user interface (GUI) (remote orlocal)

• IPE Control Panel GUI (remote or local)

Input Physical Interfaces

• Multiple 10/100/1000Base-T Ethernet (RJ45)

• ASI (optional)

• ATM OC-3 (optional)


IPE Overview Page 3

Output Physical Interfaces

• ASI (BNC)

Protocols Supported

• Multi-protocol encapsulation (MPE) with selectable section packing

• TCP/IP, UDP/IP and multicast

• LLC and SNAP (IEEE 802.2) (optional)

• MPEG-2 PSI Tables

• Telnet

• SNMP

• RIPv2

• SMPTE 325M

• NTP

• IGMP

Compliance

• DVB-S: EN 300 421.

• DVB-RCS: EN 301 790

• DVB-S2 CCM: EN 301 790, EN 300 468

• ASI/SPI: Part 9 Interfaces: 50083-9

• MPEG-2 systems: ISO/IEC 13818-1

• MPEG-2 DSM-CC: ISO/IEC 13818-6

• DVB multiprotocol encapsulation: EN301 192

• PCI local bus version 2.1

• Opportunistic Data Broadcast Flow Control: SMPTE 325M

Operating Specifications

The IPE has the following environment requirements:

Temperature

• Operating: 5 to 35°C (40 to 95°F)

• Storage: -20 to 60°C (-4 to 140°F)

Humidity

• Non-condensing operating: 10 to 80%

• Non-condensing storage: 10 to 90%

Shipping Weight

• Model 410: 6 kg (13 lbs)

• Model 520: 19 kg (42 lbs)

IPE Overview


Power Consumption

• Model 410: 55 W (Typical)

• Model 520: 165 W (Typical)

Power Supply

• 120/240 V, 50/60 Hz auto-sensing

Dimensions

• Model 520: HxWxL 9 cm x 48 cm x 70 cm (3.5” x 19” x 27.5”)

• Model 410: HxWxL 4.5 cm x 48 cm x 40 cm (1.75” x 19” x 18”)

Hardware Specification

• Windows XP Embedded operating system or Windows 2000 operatingsystem

• Pentium III, 1.2 Ghz, 256 MB RAM, SBC or Intel Quad Core PIV

• IPi-100 Transport Stream Injector card

Option Packs

The basic IPE comes with the following features:

• Constant Bit Rate (CBR), Variable Bit Rate (VBR) and Unspecified BitRate (UBR) PIDs

• Up to 8192 simultaneous PIDs

• 64 traffic profiles

• An aggregate output multiplexer bitrate of 10 Mbps

• SI/PSI Table Support

• Section packing

• Tiered QoS

• 1:n redundancy

• PID / Profile prioritization

• SMPTE 325M Opportunistic Traffic Profiles including:

Strict

Conditional

Uncontrolled

The following sections describe the option packs available to upgrade fea-tures of the IPE.

Security Option Pack

The Security option pack includes additional security features including DVBscrambling using 56-bit Fixed Key CAS. It also upgrades the aggregate outputmultiplexer bitrate to 50 Mbps and the number of traffic profiles to 64.

Remux Option Pack

The Remux option pack, available with the 520 and 410 models, includes anASI input with PID re-mapping and PID filtering capabilities.


IPE Overview Page 5

ATM Option Pack

The ATM option Pack, available with the 520 model only, provides an OC-3data input with PVC layer 2 or layer 3 routing.

Throughput Options

Throughput is available from 10 Mbps to 200 Mbps in 10 Mbps steps.

Transport Streams

A transport stream is a collection of data services that are grouped into trafficprofiles. Each IPE outputs exactly one transport stream at any one time, andany IPE can be assigned to any transport stream. Refer to ”Chapter 3: Trans-port Stream Management” on page 27 for information on configuring transportstreams.

Virtual Transport Streams

A virtual transport stream is not an actual transport stream, but is used toretrieve tuning parameters from the RMT, which are associated with a particu-lar population identifier. Transport streams with transport stream numbersgreater than 254 are reserved for virtual transport streams. All inactive trans-port streams which have an SI configuration will also be treated as virtualtransport streams.

Traffic Profiles and PIDs

A traffic profile is a collection of services or PIDs. Ten different traffic profiletypes are available:

1. Three Multiprotocol Encapsulation traffic profiles (“Multiprotocol Encapsu-lation Traffic Profiles” on page 6), including:

i. Dedicated PID Bundle (CBR); refer to “Dedicated PID Bundle (CBR)”on page 6.

ii. Shared PID Bundle (VBR); refer to “Shared PID Bundle (VBR)” onpage 6.

iii. Uncommitted PID Bundle (UBR); refer to “Uncommitted PID Bundle(UBR)” on page 6.

2. Remux Channel; refer to “Remux Channel” on page 7.

3. SI Tables; refer to “SI Tables” on page 7.

4. Two Opportunistic Data traffic profiles (“Opportunistic Data Traffic Pro-files” on page 8), including:

i. Opportunistic Session; refer to “Opportunistic Session” on page 8.ii. Uncontrolled Opportunistic; refer to “Uncontrolled Opportunistic” on

page 11.

5. Signaling Marker; refer to “Signaling Marker” on page 12.

6. ATM Profile; refer to “ATM Profile” on page 12.

7. Forward Link Signalling; refer to “Forward Link Signalling” on page 13.

IPE Overview


For information on configuring traffic profiles, refer to “Creating a Traffic Pro-file” on page 35.

Multiprotocol Encapsulation Traffic Profiles

Multiprotocol encapsulation supports data broadcast services that require thetransmission of datagrams, specifically Internet Protocol, via DVB complianttransport streams. The IPE encapsulates IP datagrams within DSM-CC sec-tions, ISO/IEC 13818-6, which are compliant with the MPEG-2 private sectionformat, ISO/IEC 13818-1. The unique stream type and specific DSM-CC sec-tion parameters for IP transport are defined in TS 101 102.The three multiprotocol encapsulation traffic profiles available with the IPE,Dedicated PID Bundle (CBR), Shared PID Bundle (VBR) and UncommittedPID Bundle (UBR), are described in the following sections.

Dedicated PID Bundle (CBR)

A Dedicated PID Bundle is assigned a guaranteed bitrate that is always avail-able to that bundle. For information on configuring Dedicated PID Bundles,refer to “Dedicated PID Bundle (CBR)” on page 37.Once the Dedicated PID Bundle is created, the following three PIDs can becreated and added to the profile:

• Constant bitrate (CBR); refer to “Constant Bitrate (CBR) PID” on page 6.

• Variable bitrate (VBR); refer to “Variable Bitrate (VBR) PID” on page 7.

• Uncommitted bitrate (UBR); refer to “Uncommitted Bitrate (UBR) PID” onpage 7.

Shared PID Bundle (VBR)

A Shared PID Bundle is assigned a guaranteed bitrate that is always availableto that bundle, as well as a peak bitrate which can be utilized by the bundleshould extra bandwidth become available. For information on configuringShared PID Bundles, refer to “Shared PID Bundle (VBR)” on page 37.Once the Shared PID Bundle is created, the following three PIDs can be cre-ated and added to the profile:




Uncommitted PID Bundle (UBR)

An Uncommitted PID Bundle is assigned only a peak bitrate, and thereforeonly utilizes the extra bandwidth that becomes available. For information onconfiguring Uncommitted PID Bundles, refer to “Uncommitted PID Bundle(UBR)” on page 37.Once the Uncommitted PID Bundle is created, an Uncommitted Bitrate (UBR)PID can be created and added to the profile; refer to “Uncommitted Bitrate(UBR) PID” on page 7.

Multiprotocol Encapsulation PIDs

Constant Bitrate (CBR) PID


IPE Overview Page 7

A constant bitrate (CBR) PID is characterized by a guaranteed bitrate. In thecase where the input traffic has a data rate greater than that of the guaranteedoutput bitrate, the data will be buffered. If the buffer becomes full, the packetswill be randomly dropped. A CBR PID can belong to the Dedicated PID Bun-dle, ATM and/or Shared PID Bundle traffic profiles. For information on configuring a CBR PID, refer to “CBR - Constant Bitrate”on page 43.

Variable Bitrate (VBR) PID

In addition to a guaranteed bitrate, a variable bitrate (VBR) PID is also charac-terized by a peak bitrate that is equivalent to that of the corresponding bundle.The bandwidth remaining after CBR guaranteed bitrates have been met isshared between all VBR PIDs belonging to the bundle, based on priority. Inthe case where the input traffic has a data rate greater than that of the outputbitrate, the data will be buffered. If the buffer becomes full, the packets will berandomly dropped. A VBR PID can belong to the Dedicated PID Bundle, ATMan/or Shared PID Bundle traffic profiles.For information on configuring a VBR PID, refer to “VBR - Variable Bitrate” onpage 43.

Uncommitted Bitrate (UBR) PID

An uncommitted bitrate (UBR) PID is characterized by a peak bitrate that isequivalent to that of the corresponding bundle. The bandwidth remaining afterCBR and VBR guaranteed bitrates, and VBR peak bitrates have been met isshared between all UBR PIDs belonging to the bundle, based on priority. Inthe case where the input traffic has a data rate greater than that of the outputbitrate, the data will be buffered. If the buffer becomes full, the packets will berandomly dropped. A UBR PID can belong to the Dedicated PID Bundle, ATMand/or Shared PID Bundle and Uncommitted PID Bundle traffic profiles.For information on configuring a UBR PID, refer to “UBR - UncommittedBitrate” on page 44.

Remux Channel

The Remux Channel profile allows an external transport stream to be mergedinto the outgoing transport stream of the IPE. For information on configuringRemux Channel traffic profiles, refer to “Remux Channel” on page 38.Once the Remux Channel profile is created, a Remux PID can be created andadded to the profile.

Remux PID

A Remux PID maps an incoming PID to an outgoing PID; if the Input PID PassThrough feature is unselected, unmapped PIDs will be dropped. For information on configuring a Remux PID, refer to “Remux Channel” onpage 44.

NOTE Incoming PAT or PMT tables should never be mapped; these tables are gen-erated automatically when an SI Tables profile is created.

SI Tables

The SI Tables profile contains the following dynamically created tables:

IPE Overview


• Program map table (PMT): provides the location of the streams that com-prise a service, as well as the location of the program clock reference(PCR); the PMT does not have a predefined PID as a PMT is dynamicallycreated for each service. A separate PMT is created for each traffic profilein the configuration. The program number for each PMT is the profilenumber of the traffic profile for which it was created.

• Program association table (PAT): contains a listing of the PMT and NITlocations for each service; located on PID 0.

• Conditional access table (CAT): provides information on the conditionalaccess systems or scrambling used in the transport stream; located onPID 1.

• Network information table (NIT): provides information about the physicalnetwork, specifically the network ID; located on PID 16.

• Service description table (SDT): provides descriptive data for a service ina transport stream; located on PID 17.

• RCS Map Table (RMT): provides information about the return channel;the RMT does not have a predefined PID as it is dynamically allocated. APMT, which references the RMT, is also created; the PMT PID is alsodynamically allocated, and the program number is 8190. The RMT is con-structed using the RCS section of the Service Information window withinthe Transport Stream Properties, as well as the addition of Virtual Trans-port Streams, Forward Link Signalling profiles, and population IDs.

• Multicast Map Table (MMT): provides a list of PIDs and multicast routesbelonging to a certain program; the list is empty if no multicast routes existwithin a profile. An MMT is created for each traffic profile in the activetransport stream of a configuration.

These tables provide the information required to aid in the selection of ser-vices within the transport stream, as well as to enable automatic configurationof the receiver to demultiplex and decode the programs within the transportstream.For information on configuring the SI Tables traffic profile, refer to “SI Tables”on page 38.

NOTE If an SI Tables profile is not created, the PID numbers will have to be manuallyentered on each receiver.

Opportunistic Data Traffic Profiles

The SMPTE 325M standard defines a flow control protocol between an Emis-sion Multiplexer and a Data Server that provides opportunistic data broadcast.The two opportunistic data traffic profiles available with the IPE, OpportunisticSession and Uncontrolled Opportunistic, are described in the following sec-tions.

Opportunistic Session

In an Opportunistic Session, the flow of data is controlled by an Emission Mul-tiplexer. The Emission Multiplexer maintains a number of opportunistic buff-ers, from which it draws packets when there is available bandwidth. When theamount of data within the buffers falls below a threshold value, a SMPTE325M message is sent to the IPE. Upon receiving the SMPTE 325M messagefrom the Emission Multiplexer, the IPE fulfills the request with data from thecorresponding opportunistic buffers.


IPE Overview Page 9

The IPE also maintains opportunistic buffers, and thus sends a SMPTE 325Mmessage to the Data Server when the amount of data within the buffers fallsbelow a threshold value. Upon receiving the SMPTE 325M message, theData Server fulfills the request by transmitting the requested number of IPpackets to the IPE, where they are stored in the corresponding opportunisticbuffers. This ensures that the IPE will have the data required to fulfill theEmission Multiplexer’s request. Figure 1 on page 9 depicts the flow of SMPTE 325M messages and data in anOpportunistic Session.

FIGURE 1. Opportunistic Session Traffic Flow.

There are two types of Opportunistic Sessions available:

• Conditional Opportunistic Session

• Strict Opportunistic Session

For information on configuring Opportunistic Sessions, refer to “OpportunisticSession” on page 38.

Conditional Opportunistic Session

A Conditional Opportunistic Session is characterized by a guaranteed bitrateand a peak bitrate. Once the Conditional Opportunistic Session is created, aConditional Opportunistic PID can be created and added to the profile.

Conditional Opportunistic PID

A Conditional Opportunistic PID is characterized by a guaranteed bitrate, anda peak bitrate that is equivalent to that of the corresponding ConditionalOpportunistic Session. If there are no SMPTE 325M requests, then the bitrateof the Conditional Opportunistic PID is the specified guaranteed bitrate. If aSMPTE 325M request is being processed, then the actual bitrate equals theguaranteed bitrate plus the requested bitrate. Therefore, the additional band-width received by a Conditional Opportunistic PID is conditionally based onSMPTE 325M requests. The following Data Server information is required to configure a ConditionalOpportunistic PID:

• PID NUMBER: the assigned PID number

• DESCRIPTION: text description of the PID

• IP ADDRESS: the Data Server’s management NIC IP address.

• PORT: the port that the Data Server is to receive the SMPTE 325M mes-sages on.

• PROTOCOL: specify whether communication with the Data Server is viaTCP or UDP.

NOTE The PROTOCOL field is set to UDP if KENCAST FAZZTTM is selected as the DATASERVER TYPE.

Data Server

IPE

OpportunisticBuffer

S M P T EMe s s age

IPP ac k e t s

S MP TEMes s age

OpportunisticBufferTS

P ac k e t s

A S I B i tS t ream

EmissionMultiplexer

IPE Overview


• TIMEOUT (MS): specify the period of time after which the IPE will issueanother SMPTE 325M request for packets it has not yet received.

NOTE The TIMEOUT (MS) field is only applicable when NORSAT INTERNATIONAL isselected as the DATA SERVER TYPE; a value of 1 second is recommended.

• DATA SERVER TYPE: specify whether the Data Server application vendor isNorsat International or KenCast FazztTM.

• GUARANTEED BITRATE (BPS): specify the bitrate that is always made availablefor the PID.

• PACKING: specify if section packing is to be implemented for the PID.

For information on configuring a Conditional Opportunistic PID, refer to “Con-ditional Opportunistic” on page 44.

NOTE A Conditional Opportunistic PID is linked to a Data Server and Emission Mul-tiplexer; therefore, the Data Server needs to be aware of the port number, andEmission Multiplexer needs to be aware of the session number, before datacan be transmitted.

Strict Opportunistic Session

A Strict Opportunistic Session is characterized by a bitrate that ranges fromzero, up to the maximum multiplexer bitrate of the IPE as bandwidth becomesavailable. Once the Strict Opportunistic Session is created, a Strict Opportu-nistic PID can be created and added to the profile.

Strict Opportunistic PID

A Strict Opportunistic PID is characterized by a bitrate ranging from zero up tothe maximum multiplexer bitrate of the IPE; i.e. no guaranteed or peak bitrate.If there are no SMPTE 325M requests, the bitrate of the Strict OpportunisticPID is zero. If a SMPTE 325M request is being processed, then the actualbitrate equals the requested bitrate. Therefore, the actual bandwidth receivedby a Strict Opportunistic PID is strictly based on SMPTE 325M requests. The following Data Server information is required to configure a Strict Oppor-tunistic PID:











For information on configuring a Strict Opportunistic PID, refer to “StrictOpportunistic” on page 45.


IPE Overview Page 11

NOTE A Strict Opportunistic PID is linked to a Data Server and Emission Multiplexer;therefore, the Data Server needs to be aware of the port number, and Emis-sion Multiplexer needs to be aware of the session number, before data can betransmitted.


In the Uncontrolled Opportunistic profile, the IPE is not controlled by an Emis-sion Multiplexer. The IPE draws packets from its opportunistic buffers whenthere is bandwidth available to transmit Uncontrolled Opportunistic data.When the amount of data within the buffers falls below a threshold value, aSMPTE 325M message is sent to the Data Server. Upon receiving theSMPTE 325M message, the Data Server fulfills the request by transmittingthe requested number of IP packets to the IPE. They are then stored in thecorresponding opportunistic buffers, thus allowing the IPE to fill the availablebandwidth. Figure 2 on page 11 depicts the flow of SMPTE 325M messagesand data in an Uncontrolled Opportunistic traffic profile.

FIGURE 2. Uncontrolled Opportunistic Traffic Flow.

An Uncontrolled Opportunistic profile is characterized by a bitrate that rangesfrom zero, up to the maximum multiplexer bitrate of the IPE as bandwidthbecomes available. For information on configuring Uncontrolled Opportunistictraffic profiles, refer to “Uncontrolled Opportunistic” on page 39.Once the Uncontrolled Opportunistic profile is created, an UncontrolledOpportunistic PID can be created and added to the profile.

Uncontrolled Opportunistic PID

An Uncontrolled Opportunistic PID is characterized by a bitrate ranging fromzero up to the maximum multiplexer bitrate of the IPE; i.e. no guaranteed orpeak bitrate. The following Data Server information is required to configure an UncontrolledOpportunistic PID:








Data Server

IPE

OpportunisticBuffer

SMPTEMessage

IPPackets

BitStream

IPE Overview





For information on configuring an Uncontrolled Opportunistic PID, refer to“Uncontrolled Opportunistic” on page 45.

NOTE An Uncontrolled Opportunistic PID is linked to a Data Server; therefore, theData Server needs to be aware of the port number before data can be trans-mitted.

Signaling Marker

The Signalling Marker profile transmits empty packets at a precisely con-trolled bitrate and interval, defined in packets per second, on one PID. Thisprofile is useful for system diagnostics as it provides a constant stream ofknown data, without the requirement of having a user logged in. For informa-tion on configuring Signaling Marker traffic profiles, refer to “SignallingMarker” on page 39.Once the Signaling Marker profile is created, a Signaling Marker PID can becreated and added to the profile.

Signaling Marker PID

A Signaling Marker PID must be added to the Signaling Marker profile in orderto transmit empty packets. When creating this PID, PCR insertion can beselected.For information on configuring a Signaling Marker PID, refer to “SignalingMarker” on page 45.

NOTE A maximum of one PID can be added to the Signaling Marker profile.

ATM Profile

The ATM profile enables external ATM packets to be received by the IPEthrough an optional OC-3 interface and multiplexed into the outgoing trans-port stream. In setting up the ATM PID’s and routes, the IPE enables an ATMVirtual Channel (VC) to be mapped through a PID to a receiver MAC address.Two types of routing are supported - layer 2 and layer 3. With Layer 3 routing,each VC has its own routing table. By keeping the routing tables of each IP-to-MAC address independent, it is possible to map to separate VC’s with thesame IP address. With Layer 2 routing, all IP address on a given VC map to asingle MAC address.

For information on configuring ATM Profiles, refer to “ATM Profile” onpage 39.

Once the ATM profile is created, the following three PIDs can be created andadded to the profile:






Once the ATM PID is created, the virtual channel mapping must be specified.The following information is needed to configure the virtual channel within theIPE:

• VCI NUMBER: virtual channel identifier

• DESCRIPTION: text description of the VC

For information on configuring a virtual channel, refer to “ATM Virtual Chan-nels” on page 48.

Forward Link Signalling

The Forward Link Signalling profile is used to create an FLS descriptor in theRMT. The transport stream id, the network id, and the interactive network id ofthe descriptor will correspond to those of the transport stream to which theFLS profile was added. The service id of the descriptor will be the profile num-ber. The population id loop of the descriptor will contain the population idswhich are added to the FLS profile.

Population ID

Population IDs/Masks can be added to traffic profiles and Forward Link Sig-nalling profiles. Each traffic profile within the active transport stream will havea linkage descriptor of type Data Broadcast Service (0x06) in the RMT. EachForward Link Signalling profile within the configuration will have a linkagedescriptor of type Forward Link Signaling (0x81) in the RMT. Both descriptortypes contain all population IDs which have been added to the profile.

Rate Limiting

The IPE offers IP rate limiting on a given route, and, for one-to-one mappingsbetween IP and MAC addresses, MAC rate limiting. When there is a one-to-one mapping between the IP and MAC addresses for a given client, the IPrate limiting is equivalent to MAC rate limiting.

IPE Management

The IPE Control Panel application allows viewing and configuration of the fol-lowing parameters:

• Rank

• Mode

• RIP period

• State

• Status

• NTP server address

• Enable External State Signal

IPE Overview


The following sections describe each of the above listed parameters; for con-figuration procedures for the mode and RIP parameters; refer to “Configuringthe IPE” on page 56.

Rank

In a redundant system, the RANK parameter is used to determine which IPE isactive; the IPE with the lowest rank is active. Only one IPE in a given transportstream can be active at a time, and therefore the remaining IPE units must bepassive. During startup, the RANK value is auto-negotiated between the IPEunits based on the least significant byte of the management IP address.

Mode

The MODE parameter specifies the behavior of the IPE during normal opera-tion and fail-over situations, and can be set to auto, forced-active, forced-pas-sive or latch.

Auto Mode

When the MODE parameter is set to AUTO, the IPE with the lowest rank isactive. Should the active IPE fail, the IPE with the next lowest rank will auto-matically become active. When the failed IPE resumes normal operation, itwill once again become active, and the fail-over unit will once again becomepassive.

Forced-Active Mode

When the MODE parameter is set to FORCED-ACTIVE, the IPE will remain activeregardless of the rank respective to any other IPE units.

Forced-Passive Mode

When the MODE parameter is set to FORCED-PASSIVE, the IPE will remain pas-sive regardless of the rank respective to any other IPE units.

Latch Mode

When the MODE parameter is set to LATCH, the IPE with the lowest rank is ini-tially active. As with AUTO mode, should the active IPE fail, the IPE with thenext lowest rank will automatically become active. However, when the previ-ously failed higher rank IPE resumes normal operation, it does not automati-cally become active again; it remains passive. Likewise, the currently activeIPE will remain active. To re-negotiate which IPE is active based on rank, theLATCH mode must be manually reset.

RIP Parameters

RIP is used to broadcast the route table. RIP messages can be enabled ordisabled via the ENABLED check-box in the IPE CONFIGURATION window of theIPE Control Panel. The PERIOD parameter can also be configured, and isdescribed in the following sections; refer to “Configuring RIP Parameters” onpage 59 for configuration procedures.

RIP Period



The PERIOD parameter specifies the interval that the RIP messages are broad-cast at. It must be in the range of 1 to 36000 seconds.

State

The STATE parameter indicates whether the IPE is active, passive or notresponding.

Active

A state of ACTIVE indicates that the IPE is actively generating the requestedtransport stream.

Passive

A state of PASSIVE indicates that even though the IPE is configured to generatethe transport stream, it is not actively doing so.

Offline

A state of OFFLINE indicates that a network connection with the IPE is notestablished. For troubleshooting information, refer to “Troubleshooting” onpage 73.

Exception

A state of EXCEPTION indicates that there is a problem with the IPE. For moreinformation, refer to “IPE Control Panel” on page 74.

Status

The STATUS parameter indicates the result of the update to the IPE which canbe CONFIGURED, UNCONFIGURED, or CONFIGURING....

Configured

A status of CONFIGURED indicates that the IPE is fully configured to generateits transport stream.

Unsynchronized

A status of CONFIGURING... indicates that the IPE has started, but not yet com-pleted its configuration update. This state will occur during initialization, how-ever, if the IPE remains in the UNSYNCHRONIZED state for a period of tenseconds or longer, refer to “Troubleshooting” on page 73 for troubleshootinginformation.

Unconfigured

A status of UNCONFIGURED indicates that the IPE has been assigned to atransport stream that does not exist in the database. In this state, no configu-ration will have been uploaded to the IPE. The user must either assign theIPE to an existing transport stream, or create a transport stream in the Trans-port Stream Manager (see “Transport Stream Management” on page 27) withthe assigned transport stream ID.

IPE Overview


NTP parameters

NTP is used to retrieve the current time from a time server. NTP requests canbe enabled or disabled via the ENABLED check-box in the IPE CONFIGURATIONwindow of the IPE Control Panel. The NTP SERVER parameter can also be con-figured, and is described in the following sections; refer to “Configuring NTPParameters” on page 59 for configuration procedures.

NTP Server

The NTP SERVER parameter specifies the server address which the NTP clientwill use to make time requests. It can be either an IP address or a host name.

Enable External State Signal

If you IPE-410 is equipped with the necessary hardware, an external alarmsignal can be used to determine which IPE will be active in a dual IPE redun-dancy configuration. With this option selected, the presence of a 12-24Vdcsignal will cause the IPE to be set to the passive state. The absence of thevoltage will bring the IPE back to an active state. The circuit details of the 12-24V input signal are provided below in Figure 3 on page 17.

The 12-24Vdc alarm signal is applied to the 25 pin LPT1 (See Figure 5 onpage 22) on the following pins:

PIn 5: +12 to +24VdcPIn 4: common

NOTE When this option is selected, the operator loses the ability to manually set theIPE state, as well as use 1:N redundancy.

NOTE To use the External State Input signal will require that the ENABLE EXTERNALSTATE SIGNAL box is checked in the IPE Control Panel (ref Figure 23 onpage 57).

NOTE When the External Signal State is enabled, the watchdog relay contact clo-sure will remain open (normal operation) and the IPE output will remainacitve, despite the IPE going passive or active.

NOTE If the External Signal State is NOT enabled, the watchdog contact closurerelay will be set depending on the passive/active state of the IPE and the IPEoutput will be muted when the IPE is in the passive state.

NOTE It is recommended that shielded cabling be used for these connections andthat the shielding is grounded.



FIGURE 3. IPE-410 Alarm Input Circuitry

External Contact Closure Outputs

The IPE-410 is equipped with contact closure outputs that change state whenthe IPE goes between the ACTIVE and PASSIVE states. When the IPE-410 ispowered on and operational, the Relay functions are available on the 25 pinLPT1 connectors as follows:

• PIn 7 - Common

• Pin 8 - Open during normal IPE operation, Closed during IPE alarm condi-tion

• Pin 9 - Closed during normal IPE operation, Open during IPE alarm condi-tion

NOTE You must use a shielded cable for these connections; the shielding must begrounded.

The IPE-520 may be ordered with contact closure outputs that change statewhen the IPE goes between the ACTIVE and PASSIVE states, but this must bespecified at the time or order

IPE Overview



CHAPTER 2 Installing the IPE

This chapter is designed to give step by step instructions on how to install theIPE.

Checking the Equipment

When you receive the IPE, locate the Bill of Materials included with theshipment; it lists the items that should have been received, and reflects theconfiguration options chosen. Ensure that all components listed have beenreceived by checking off each item against the Bill of Materials. If for anyreason not all of the materials listed have been received, contact the vendor.

AVOIDING ELECTROSTATIC DISCHARGES

All active IPE components contain sensitive electronics that can be damagedor degraded by electrostatic discharge (ESD). ESD may result wheninstallation or service personnel fail to ground themselves properly.

When installing or adjusting equipment and connections, ensure installationor service personnel are properly grounded through the use of an ESD wriststrap.

SAFETY AND COMPLIANCE INFORMATION

To ensure compliance with supply voltages, supply currents and safety,emissions and immunity standards, use only the power adapters and cordssupplied with the IPE. Disconnect power cords while moving and installing units.Do not allow any system components to be exposed to moisture, rain,excessive heat or direct sunlight.

!

!

Installing the IPE


Facility Interfaces Required

Management Station

A personal computer, equipped with Windows 2000 SP4 or Windows XP, canbe used to monitor and control an IPE system; this is called the ManagementStation. The Management Station must have 40 megabytes of storage spaceon the hard drive, at least one network interface card and 64 MB of RAM.

NOTE Alternatively, the IPE can be monitored and controlled by connecting akeyboard and mouse directly to the IPE.

Ventilation

Ensure the extra waste heat generated by the IPE is within the capacity of thefacility cooling system. Ensure that the IPE fans are clear of obstructions sothat air can circulate freely to cool internal components.

Security

It is strongly recommend that the equipment is installed in a secure locationaccessible only to authorized personnel, thus reducing the chances of thesystem being brought down accidentally.

Interfaces

The IPE interfaces to the facility at the following connection points; refer toFigure 4 on page 21:

• DVB-ASI output from the IPE to an external multiplexer, modulator orphysical layer converter.

• DVB-ASI input.

• ATM OC3 input.

• Ethernet connections from the IPE to an external router and to a Manage-ment Station.

• Contact closure output.

Cable Connections

The following describes the cable types used to help with identification of thecables, to make connections and to order replacements, if necessary.

Ethernet

Ethernet cabling is eight-conductor category 5 unshielded twisted pair. Eachcable is terminated with an RJ45 connector, is EIA/TIA 568 compliant and isused in 10BaseT and 100BaseTX Ethernet installations. Maximum distanceallowed on these cables is 100 meters.

MPEG-2 Transport Stream

The transport stream is available on an asynchronous serial interface (ASI)output at the back of the IPE. This coaxial cable is a 75-ohm broadcast qualitycable, Belden 8281 or equivalent, terminated with BNC connectors on bothends. The maximum recommended length is 300 meters.


Installing the IPE Page 21

PowerAll power plugs must include a grounding prong.

POWER SAFETY AND COMPLIANCE INFORMATIONPower requirements differ around the world. Use only power adapters andcords supplied with the IPE to ensure compliance with supply voltages andcurrents, safety, emissions and immunity standards.Disconnect power cords while moving and installing units.Do not allow any components of the system to be exposed to moisture, rain,excessive heat or direct sunlight.

FIGURE 4. IPE-410C Rear View.

!

2 3 765 8

69

1 Power Receptacle2 ASI Out 13 ASI Out 24 ASI In : BNC Extender5 USB(2) (Keyboard/Mouse)

6 Video7 Management NIC8 Data NIC9 Watchdog Relay/Alarm Input

4

1

N/A N/A

Installing the IPE


FIGURE 5. IPE-410 Rear View.

Configuring IP Addresses

IPE IP addresses are factory-configured with private test address values.Reconfiguring these addresses may be necessary, depending on yourapplication.

Default IP Addresses

The default IP address for the management NIC is:

• 192.168.3.4 netmask 255.255.255.0

The default IP address fro the data NIC is:

• 192.168.2.4 netmask 255.255.255.0

DO NOT TRY NON-STANDARD SOFTWARE APPLICATIONS, SETTINGS OR

CONFIGURATIONS

The IPE platform is carefully configured and optimized at the factory. Donot install software applications, change environment settings or try anyconfigurations not recommended in this manual.

The management NIC netmask should remain at the factory setting of255.255.255.0. Changing this value may impair the operation of the IPE.

1 2 3 4 587 6

69

1 Power Receptacle2 ON/OFF Switch3 ASI 14 ASI 25 Data NIC

6 Management NIC7 Keyboard/Mouse [note: newer models may use USB connector(s)]8 Video9 Watchdog Relay/Alarm Input10 ASI In

10

!

!



FIGURE 6. Typical Network Connections for the IPE.

Changing IP Addresses

Use the following procedure to change IP addresses.

NOTE To change the IP addresses on the IPE, it is recommended that you connect akeyboard, monitor and mouse to the IPE. Power up the IPE and use thestandard Windows XP commands to change the IP Address of the Trafficnetwork interface, the IP address of the Management network interface, or tochange the gateway address of either.

For example, to change the IP Address of the Management network interface,go to the following Windows XP location:

1. START CONTROL PANEL NETWORK CONNECTIONS

2. Right Click the MANAGEMENT NIC and select PROPERTIES

3. Scroll down to INTERNET PROTOCOL (TCP/IP) and select PROPERTIES

4. Select USE THE FOLLOWING IP ADDRESS and enter the new IP ADDRESS

and SUBNET MASK and/or the GATEWAY ADDRESS

5. Select OK

6. Select OK

The management NIC netmask should remain at the factory setting of255.255.255.0. Changing this value may impair the operation of the IPE.!

Installing the IPE


Installing the User Interfaces

The Management Station requires some software installation, as described inthe following sections. To manage the IPE using the installed managementsoftware, the Management Station must be on the same subnet as themanagement interface of the IPE. Take care to ensure that the IP address youchoose for the Management Station does not conflict with any IPEs on thenetwork.

NOTE The IPE Application CD also contains the following MIBs:

• swi.mib

• swiipe.mib

• swinme.mib

These MIBs can be imported into an SNMP application, in order to monitorthe IPE via SNMP.

Installing the IPE Management Software

This section explains how to install the two key software items on yourManagement Station PC:

• IPE Control Panel

• TS Manager

1. Insert the IPE Installation CD into the CDROM drive of the ManagementStation PC.

2. Run the install wizards for each application, following the on-screeninstructions.

Connecting to Your Facility

Installing the IPE Hardware

Use the following procedure to install the hardware (refer to Figures 5 or 6):

1. Connect a power cord to the IPE.

2. Connect the IPE power cord to the facility mains. Ensure that the voltageand frequency of the facility match the IPE configuration.

3. Connect the 75-ohm BNC terminated patch cord to the ASI output jack 1on the IPE; refer to Figure 6 on page 23.

You can connect this output stream to a DVB/ MPEG ASI compliant devicesuch as:

• A modulator

• A multiplexer

• An interface converter

4. Connect the 75-ohm cable from the IPE to the ASI input connector of theappropriate device in your existing facility. Refer to the documentation ofthat device for proper switch settings or configurations. This cable mustnot exceed 300 metres in length.

5. Connect the two network interface cards (NIC) to the patch cords.

When the cables are connected properly, the green link lights should go on. If



they do not, check the cable for continuity.

Powering Up for the First Time

1. Move the power switch on the unit to ON. The power supply switch islocated at the back of the IPE-410. There is also a power on rocker switchlocated on the front panel of the IPE-410 which must be depressed topower on the IPE. For the IPE-520, the power switch is located on thefront panel in the upper right hand corner, beneath the plastic front bezel.The power LED will light, the fans will start, and the hard drive accesslight will flicker as the IPE boots up.

Installing the IPE


IPE Interfaces and Routing

The IPE has two physical Ethernet interfaces, one for management(192.168.3.4) and one for traffic (192.168.2.4); refer to Figure 6 on page 23.The IPE also contains two virtual IP addresses that are internal, but allow IProuting and address resolution protocol (ARP) to occur in a standard manner:

• The DVB ASI interface on the IPE can be considered as a virtual interfacewith the address 192.168.255.1.

• The encapsulation process itself can be considered as a virtual gatewaywith the address 192.168.255.2 and a dummy MAC of 00-11-22-33-44-55.


CHAPTER 3 Transport Stream Management

This chapter is designed to give step by step instructions on how to managetransport streams, including configuring:

• Transport streams

• Traffic profiles

• PIDs

• ATM Virtual Channels

• Routes

Once a transport stream has been configured, it can then be assigned to anIPE. Refer to “Assigning Transport Stream(s)” on page 57 for instructions onassigning transport streams.

Managing Transport Streams

The Transport Stream Manager application will be used to configure the trans-port streams. To launch the Transport Stream Manager:

1. From the Windows toolbar, select START PROGRAMS NOVRA TRANS-PORT STREAM MANAGER. The MANAGING TRANSPORT STREAMS panel is thenlaunched; refer to Figure 7 on page 28.

2. Windows 7 Support: If the Transport stream Manager is installed on anexternal Windows 7 IPE Configuration PC, then you will need to do thefollowing:

i. Go to the following Folder: C:\Program Files (x86)\Novra Technolo-gies\Transport Stream Manager

ii. Right click on the file: TSManager.exeiii. Select Propertiesiv. Click the Compatibility Tabv. Click the “Run this program in compatibility mode for” checkbox and

select Windows XP (Service Pack 3) from the drop downvi. Click OK

Transport Stream Management


FIGURE 7. MANAGING TRANSPORT STREAMS Panel.

From the LOCAL UPLINK FACILITY tree, the transport streams (refer to “TransportStreams” on page 30), traffic profiles (refer to “Traffic Profiles” on page 35),PIDs (refer to “PIDs” on page 41) and routes (refer to “Routes” on page 49)can be configured and viewed.

IPE Configuration Interface

IPE Configuration State

The Target Agents box at the bottom of Transport Stream Manager displays alist of IPEs and their current state. Each line in the list has either a Green,Red, or Yellow background color. These colors indicate whether or not theconfiguration that is currently loaded in Transport Stream Manager is identicalto the one on the IPE.A Green bar indicates that the loaded configuration is the same as the IPEconfiguration. For example, every IPE line in the list should turn Green follow-ing a successful APPLY CONFIGURATION TO ALL.


Transport Stream Management Page 29

A red bar indicates that the loaded configuration is not the same as the one onthe IPE. Generally the bar will turn red when the Transport Stream Managerconfiguration is edited and green when the configuration is successfullyapplied to the IPE(s). Retrieving a configuration from an IPE is done using theGET CONFIGURATION command. Once Transport Stream Manager has suc-cessfully loaded the configuration, the line for that IPE in the Target Agentslist should turn Green.A yellow bar sometimes indicates an error condition, however it often meansthat the received configuration may not have been properly verified by the IPEyet. Within minutes, the IPE should complete the verification and the bar willturn green. Yellow bars should rarely occur.

Applying a Configuration

Settings entered in Transport Stream Manager must be applied to the IPE(s)in order to take effect. The IPE configuration operations include: GET CONFIG-URATION, APPLY CONFIGURATION, APPLY CONFIGURATION TO ALL, RE-APPLY PREVI-OUS CONFIGURATION. The following steps are required for these operations:

1. To get the current configuration of the selected IPE:

i. Right-click on an IPE in the TARGET AGENTS list in Transport StreamManager, and select GET CONFIGURATION. Select YES when promptedif you are sure you want to get the configuration file from the IPE.

2. To apply the configuration to a selected IPE:

i. Right-click on the selected IPE in the TARGET AGENTS list in TransportStream Manager, and select APPLY CONFIGURATION,

NOTE The operator should take care when applying different configurations to differ-ent IPE’s on the same Management subnet as it is easy to lose track of whichconfiguration you are working on. When changing a IPE configuration, it istherefore recommended that you first retrieve the configuration from the IPEthat is to be updated, make the changes and then apply them.

3. To apply the configuration to all IPEs in the list:

i. Right-click on an IPE in the TARGET AGENTS list in Transport StreamManager, and select APPLY CONFIGURATION TO ALL. Select YES whenprompted if you are sure you want to apply the configuration file to allthe IPE’s.

i.

4. To re-apply the previous configuration on the selected IPE:

i. Right-click on an IPE in the TARGET AGENTS list in Transport StreamManager, and select RE-APPLY PREVIOUS CONFIGURATION.

Configuration Errors

Should there be errors in the configuration, the IPE will return an error file. Apopup window directs the user to the location of this file on the users system.License violations are also included in the error file.

The error file consists of a list of changes that were applied to the IPE. Eachchange is in the form of an Add, Delete, or Modify operation, and contains allof the information necessary to find the error within the configuration tree.Errors are listed directly in the configuration operation in which they were



found. This corresponds directly to the element in the configuration tree con-taining the error. Explanations are provided for each error.

Global errors, which may be applicable to multiple commands, are listed atthe beginning of the error file. These errors include license violations.

Transport Streams

This section describes the steps required to:

• Create a new transport stream

• Set Advanced Transport Stream Properties

• View/modify transport stream parameters

• Delete a transport stream

Creating a Transport Stream

Transport streams are configured in the TRANSPORT STREAM PROPERTIES panel.The following steps describe how to add and configure a new transportstream:

1. In the tree, right click on the LOCAL UPLINK FACILITY icon and select ADDNEW TRANSPORT STREAM from the resulting pop-up menu. The TRANSPORTSTREAM PROPERTIES panel is then launched; refer to Figure 8 on page 31.



FIGURE 8. TRANSPORT STREAM PROPERTIES Panel.

2. For the new transport stream:

i. Enter the transport stream information in the TRANSPORT STREAM NUM-BER, DESCRIPTION, BITRATE (BPS) and MAX PROFILES fields.

ii. In the TRANSMISSION MODE sub-panel, select which transmissionmode the transport stream will implement: SPI (LVDS), ASI BURSTMODE, ASI PACKET MODE (greyed out and not selectable) or ASIPACKET MODE WITH SCRAMBLING.

iii. In the FILLER MODE sub-panel, select which filler type the transportstream will use: SYNCH WORDS WITH NULL PACKETS or SYNCH WORDSONLY.

iv. In the MUX OUTPUT sub-panel, select the output of the mux to be ONor OFF.

v. In the PACKET FORMAT sub-panel, select either 188 BYTE or 204 BYTE forthe packet size.

vi. In the TRANSMISSION STANDARD sub-panel, select either one of the DVBSETTINGS or ATSC.

i. The ROUTE HEARTBEAT SETTINGS Subpanel is used to set up a heartbeatping on selected unicast host routes. This heartbeat may be used tokeep the receiver from flushing it’s ARP table when little or no traffic isbeing forwarded to that receiver. Enter the HEARTBEAT FREQUENCY (inseconds) and then select if the Heartbeat is ON or OFF.

NOTE Once the Route Heartbeat is configured, it may be enabled on each unicastroute in the ROUTE PROPERTIES screen (ref Figure 19 on page 50).



3. Click OK. The newly created transport stream, along with the description,are now shown in the LOCAL UPLINK FACILITY tree; refer to Figure 9 onpage 32.

FIGURE 9. New Transport Stream.

Setting Transport Stream Service Information Settings

While creating a transport stream, the user has the option of enteringadvanced transport stream properties. These properties are used by SITables to generate more detailed information about the transport stream.

NOTE Setting these parameters for a particular transport stream is optional.

NOTE SI Tables must be enabled on the transport stream for advanced properties tohave any effect.

The following steps describe how to set advanced transport stream parame-ters:

1. From the TRANSPORT STREAM PROPERTIES panel, click the SERVICE INFORMA-TION button. The TRANSPORT STREAM ADVANCED PROPERTIES panel is thenlaunched; refer to Figure 10 on page 33.



FIGURE 10. TRANSPORT STREAM ADVANCED PROPERTIES Panel.

2. For the transport stream:

i. Enter the advanced transport stream information in the FREQUENCY,ORBITAL POSITION, and NETWORK ID fields.

ii. For ORBITAL POSITION choose either WEST or EAST.iii. For Polarization, choose either LINEAR HORIZONTAL, LINEAR VERTICAL,

CIRCULAR LEFT, or CIRCULAR RIGHT.iv. For Viterbi FEC choose either 1/2, 2/3, 3/4, 5/6 or 7/8.

NOTE The Symbol Rate is recalculated when the CALC button is pressed. It is calcu-lated based on your transport stream mux bitrate, and the selected ViterbiFEC. This button should be used after making changes to either of thesefields.

3. If Return Channel Satellite information is required, perform the following:

i. Enable Return Channel Satellite information by selecting the ENABLERCS checkbox.

NOTE The Roll off, Multiple Input Stream, and Scrambling Sequence fields are spe-cific to the DVB-S2 transmission standard.

NOTE Enabling Return Channel Satellite will automatically enable the RMT andMMT tables in the SI Tables profile.

ii. For the Forward Path Information in the FORWARD PATH subpanel,enter the values for the SATELLITE ID, BEAM ID, NCC ID, LOCAL PATH ID,INTERACTIVE NETWORK ID, and MMT TABLE ID.

NOTE Take care to ensure that the MMT TABLE ID does not conflict with existingtables in the SI stream. The default value for the MMT TABLE ID is 0XC0.



iii. For PATH USAGE, select either COMBINED SIGNAL/DATA PATH, SIGNALONLY, DATA ONLY, or RELEASE DATA PATH.

iv. For the PID/PROGRAM NUMBER SETTINGS, enter the RMT PID NUMBER,RMT - PMT PID NUMBER (PMT PID number for the RMT) and the RMT-PMT PROGRAM NUMBER (PMT program number for the RMT).

NOTE For each of the PID/PROGRAM NUMBER SETTINGS, a default entry of “ “ (blank) or“0” will force the IPE to dynamically generate the PID and/or program num-bers.

4. If Return Path information is required for the Return Channel Satelliteinformation, perform the following:

i. click ADD in the RETURN PATH subpanel to popup the RETURN PATHTRANSPORT STREAM panel; refer to Figure 11 on page 34.

FIGURE 11. RETURN PATH TRANSPORT STREAM PROPERTIES Panel.

ii. For the return path, enter the information for SATELLITE ID, BEAM ID,GATEWAY ID, ORBITIAL POSITION, SUPER FRAME ID, TX FREQUENCY OFFSETand LOCAL PATH ID. For PATH USAGE, select either PRIMARY, SECOND-ARY, or RELEASE SECONDARY.

iii. Click OK to accept the changes; to close the panel without saving thechanges, click CANCEL. The return path information will appear in thelist in the RETURN PATH subpanel on the TRANSPORT STREAM ADVANCEDPROPERTIES panel.

iv. To remove existing return path information, select it from the list in theRETURN PATH subpanel and press the DELETE button. The CONFIRMDELETION window will appear. To confirm the return path deletion clickYES; click NO to keep the return path information.



v. To edit existing return path information, select it from the list in theRETURN PATH subpanel and press the EDIT button. The RETURN PATHTRANSPORT STREAM panel will popup, allowing you to make changes tothe return path properties.

5. Click OK. The transport stream advanced properties will be saved, andyou will be returned to the TRANSPORT STREAM PROPERTIES panel for theselected transport stream.

View/Modify Transport Stream Parameters

With the exception of the TRANSPORT STREAM NUMBER field, the transport streamparameters can be modified:

1. Right click on the transport stream whose properties you would like tomodify, and select TRANSPORT STREAM PROPERTIES from the resulting pop-upmenu.

2. The TRANSPORT STREAM PROPERTIES panel is then launched; note that theTRANSPORT STREAM NUMBER field is greyed out. Modify the appropriatefields and click OK to save the changes; to close the panel without savingthe changes, click CANCEL.

Deleting a Transport Stream

To remove a transport stream:

1. Right click on the transport stream you would like to delete, and selectDELETE TRANSPORT STREAM from the resulting pop-up menu.

2. The CONFIRM DELETION window appears. To confirm the transport streamdeletion click YES; click NO to keep the transport stream.

Traffic Profiles


• Create a new traffic profile

• View/modify traffic profile parameters

• Delete a traffic profile

Creating a Traffic Profile

Traffic Profile parameters are configured in the TRAFFIC PROFILE PROPERTIESpanel. The following steps describe how to add and configure a new trafficprofile:

1. In the tree, right click on the transport stream that you want the traffic pro-file associated with, and select ADD NEW TRAFFIC PROFILE from the result-ing pop-up menu. The TRAFFIC PROFILE PROPERTIES panel is then launched;refer to Figure 12 on page 36.



FIGURE 12. TRAFFIC PROFILE PROPERTIES Panel.

2. For all traffic profile types:

i. The transport stream that you right-clicked on will be shown in theTRANSPORT STREAM field.

ii. Enter the traffic profile information in the PROFILE NUMBER and DESCRIP-TION fields.

3. The TYPE selected will depict which other traffic profile parameters arerequired:

i. For DEDICATED PID BUNDLE (CBR) parameters, refer to “Dedicated PIDBundle (CBR)” on page 37.

ii. For SHARED PID BUNDLE (VBR) parameters, refer to “Shared PID Bun-dle (VBR)” on page 37.

iii. For UNCOMMITTED PID BUNDLE (UBR) parameters, refer to “Uncommit-ted PID Bundle (UBR)” on page 37.

iv. For REMUX CHANNEL parameters, refer to “Remux Channel” onpage 38.

v. For SI TABLES parameters, refer to “SI Tables” on page 38.vi. For OPPORTUNISTIC SESSION parameters, refer to “Opportunistic Ses-

sion” on page 38.vii. For UNCONTROLLED OPPORTUNISTIC parameters, refer to “Uncontrolled

Opportunistic” on page 39.viii. For SIGNALING MARKER parameters, refer to “Signalling Marker” on

page 39.ix. For ATM PROFILE parameters, refer to “ATM Profile” on page 39.



x. For Forward Link Signalling parameters, refer to “Forward Link Sig-nalling” on page 37.

NOTE The DEDICATED PID BUNDLE (CBR) is shown in Figure 12 above for reference.

Dedicated PID Bundle (CBR)

1. From the TYPE drop-down box, select DEDICATED PID BUNDLE (CBR).2. Enter the value for the GUARANTEED BITRATE (BPS) field.

3. For the PID/PROGRAM NUMBER SETTINGS, enter the PMT PID NUMBER, PMTPROGRAM NUMBER and the MMT PID NUMBER.


4. Click OK. The newly created traffic profile will now appear in the LOCALUPLINK FACILITY tree, under the selected transport stream.

The following PID types can now be added to a dedicated PID bundle:

• Constant bitrate (CBR); refer to “CBR - Constant Bitrate” on page 43.

• Variable bitrate (VBR); refer to “VBR - Variable Bitrate” on page 43.

• Uncommitted bitrate (UBR); refer to “UBR - Uncommitted Bitrate” onpage 44.

Shared PID Bundle (VBR)

1. From the TYPE drop-down box, select SHARED PID BUNDLE (VBR).2. Enter the values for the GUARANTEED BITRATE (BPS), PEAK BITRATE (BPS) and

PRECEDENCE fields.




The following PID types can now be added to a shared PID bundle:




Uncommitted PID Bundle (UBR)

1. From the TYPE drop-down box, select UNCOMMITTED PID BUNDLE (UBR).2. Enter the values for the PEAK BITRATE (BPS) and PRECEDENCE fields.


NOTE For each of the PID/PROGRAM NUMBER SETTINGS, a default entry of “ “ (blank) or“0” will force the IPE to auto generate the PID and/or program numbers.




The following PID type can now be added to an uncommitted PID bundle:


Remux Channel

1. From the TYPE drop-down box, select REMUX CHANNEL.

2. Enter the values for the PEAK BITRATE (BPS) and CARD NUMBER fields.

3. Enable or disable the Input PID Pass Through feature. Enabling this fea-ture passes all input PIDs through to the output automatically. No PIDscan be added to this profile when this is enabled.


The following PID type can now be added to a remux channel profile:

• Remux channel; refer to “Remux Channel” on page 44.

NOTE The bitrate which is specified for the remux profile should be high enough toaccommodate the total bitrate of all the PIDs that will be remapped. If thisbitrate is too low, overruns will occur. If the bitrate is much too high, then thePCR in remapped PIDs may fall outside of DVB specified limits.

SI Tables

1. From the TYPE drop-down box, select SI TABLES.

2. Enter the values for the MINIMUM INTERVAL (MS) and GUARANTEED BITRATE(BPS) fields.


NOTE Unless values are specifically input (for the RMT and PMT, for example), thePIDs for the SI Tables are dynamically created.

NOTE If an SI Tables profile is not created, the PID numbers will have to be manu-ally entered on each receiver.

Opportunistic Session

1. From the TYPE drop-down box, select OPPORTUNISTIC SESSION.

2. From the OPPORTUNISTIC TYPE sub-panel, select either CONDITIONAL orSTRICT.

i. For CONDITIONAL: enter the values for the SESSION NUMBER, GUARAN-TEED BITRATE (BPS) and PEAK BITRATE (BPS) fields.

ii. For STRICT: enter the value for the SESSION NUMBER field.

3. For both: enter the value for the LOCAL PORT NUMBER field, and selecteither UDP or TCP for the EMISSION MUX PROTOCOL field.




NOTE For each of the PID/PROGRAM NUMBER SETTINGS, a default entry of “ “ (blank) or“0” will force the IPE to dynamically generate the PID and/or program num-bers.Click OK. The newly created traffic profile will now appear in the LOCAL UPLINKFACILITY tree, under the selected transport stream.

The following PID type can now be added to a conditional opportunistic ses-sion:

• Conditional opportunistic; refer to “Conditional Opportunistic” on page 44.

The following PID type can now be added to a strict opportunistic session:

• Strict opportunistic; refer to “Strict Opportunistic” on page 45.


1. From the TYPE drop-down box, select UNCONTROLLED OPPORTUNISTIC.


NOTE For each of the PID/PROGRAM NUMBER SETTINGS, a default entry of “ “ (blank) or“0” will force the IPE to auto generate the PID and/or program numbers.Click OK.

3. The newly created traffic profile will now appear in the LOCAL UPLINK FACIL-ITY tree, under the selected transport stream.

The following PID type can now be added to an uncontrolled opportunisticprofile:

• Uncontrolled opportunistic; refer to “Uncontrolled Opportunistic” onpage 45.

Signalling Marker

1. From the TYPE drop-down box, select SIGNALING MARKER.

2. Enter the value for the PACKETS PER SECOND field.

3. Select either STANDARD PCR or PCR PLACEHOLDER.


The following PID type can now be added to a Signaling Marker profile:

• Signaling marker; refer to “Signaling Marker” on page 45.


ATM Profile

1. From the TYPE drop-down box, select ATM PROFILE.

2. Enter the values for the GUARANTEED BITRATE (BPS), PEAK BITRATE (BPS) andPRECEDENCE fields.


NOTE For each of the PID/PROGRAM NUMBER SETTINGS, a default entry of “ “ (blank) or“0” will force the IPE to auto generate the PID and/or program numbers.




The following PID types can now be added to an ATM Profile:




Forward Link Signalling

1. From the TYPE drop-down box, select FORWARD LINK SIGNALLING.

2. Enter the required values for the POPULATION ID BASE AND MASK.


No PIDs can be added to an FLS Profile.

Population ID

1. Enter the required values for the POPULATION ID BASE AND MASK.

2. Click ADD. The new Population ID will now appear in the list.

3. Enter the Population ID number to be removed, or click on the relevantline in the Population ID list.

4. Click DELETE. The Population ID will now be removed from the list.

The newly created traffic profile (in this case a Dedicated PID bundle (CBR)),along with the description, are now shown in the LOCAL UPLINK FACILITY tree;refer to Figure 13 on page 40.

FIGURE 13. New Traffic Profile.

View/Modify Traffic Profile Parameters

With the exceptions of the TRANSPORT STREAM NUMBER, TYPE and PROFILE NUM-BER fields, the traffic profile parameters can be modified:

1. Right click on the traffic profile whose properties you would like to modify,and select TRAFFIC PROFILE PROPERTIES from the resulting pop-up menu.

2. The TRAFFIC PROFILE PROPERTIES panel is then launched; note that theTRANSPORT STREAM NUMBER, TYPE and PROFILE NUMBER fields are greyed out.Modify the appropriate fields and click OK to save the changes; to closethe panel without saving the changes, click CANCEL.

Deleting a Traffic Profile

To remove a traffic profile:



1. Right click on the traffic profile you would like to delete, and select DELETETRAFFIC PROFILE from the resulting pop-up menu.

2. The CONFIRM DELETION window appears. To confirm the traffic profile dele-tion click YES; click NO to keep the traffic profile.

NOTE When a traffic profile is deleted, the PIDs associated with it are automaticallyremoved from the database. Refer to “Deleting a PID” on page 47 for instruc-tions on deleting a PID.

PIDs


• Create a new PID

• View PID parameters

• Modify PID parameters

• Delete a PID

Creating a PID

PIDs are configured in the PID PROPERTIES panel. The following steps describehow to add and configure a PID:

1. In the tree, right click on the traffic profile that you want the PID associ-ated with and select ADD NEW PID from the resulting pop-up menu. ThePID PROPERTIES panel is then launched; refer to Figure 14 on page 42.

NOTE In this example, the CBR - CONSTANT BIT RATE PID is shown below



FIGURE 14. PID PROPERTIES Panel.

NOTE When configuring the PID parameters, it may be useful to note the informationcontained in the TRAFFIC PROFILE INFORMATION sub-panel. This sub-panel listsproperties of the selected traffic profile that the PID is being associated with,including: DESCRIPTION, TYPE, NUMBER OF PIDS, GUARANTEED BITRATE and AVAIL-ABLE BITRATE.

2. For all PID types:

i. The traffic profile that you right-clicked on will be shown in the TRAFFICPROFILE field, and the transport stream that the traffic profile is associ-ated with is shown in the TRANSPORT STREAM field.

ii. Enter the PID information in the PID NUMBER and DESCRIPTION fields.

3. In the PARAMETERS sub-panel, the PID TYPE selected will depict which otherPID parameters are required:

i. For CBR - CONSTANT BITRATE parameters, refer to “CBR - ConstantBitrate” on page 43.

ii. For VBR - VARIABLE BITRATE parameters, refer to “VBR - VariableBitrate” on page 43.

iii. For UBR - UNCOMMITTED BITRATE parameters, refer to “UBR - Uncom-mitted Bitrate” on page 44.

iv. For REMUX CHANNEL parameters, refer to “Remux Channel” onpage 44.

v. For CONDITIONAL OPPORTUNISTIC parameters, refer to “ConditionalOpportunistic” on page 44.

vi. For STRICT OPPORTUNISTIC parameters, refer to “Strict Opportunistic” onpage 45.



vii. For UNCONTROLLED OPPORTUNISTIC parameters, refer to “UncontrolledOpportunistic” on page 45.

viii. For SIGNALING MARKER parameters, refer to “Signaling Marker” onpage 45.

NOTE Unless values are specifically input (for the RMT and PMT, for example), thePIDs for the SI Tables are dynamically created.

CBR - Constant Bitrate

A CBR PID can be associated with the Dedicated PID Bundle (CBR), SharedPID Bundle (VBR) and ATM Profile traffic profile types. In the PARAMETERS sub-panel:

1. From the PID TYPE drop-down box, select CBR - CONSTANT BITRATE.

2. Enter the value for the GUARANTEED BITRATE (BPS) field, and select PACKINGif required.

3. Click OK. The newly created PID will now appear in the LOCAL UPLINKFACILITY tree, under the selected traffic profile.

4. In the DVB SCRAMBLE sub-panel, select either NONE, EVEN or ODD. If EVENor ODD was selected, enter the 8-byte key in the KEY field. The IPE sup-ports a “User Mode” entry of the key (default) or a “DVB Mode” key entry.The “User Mode” will use the key exactly as it is entered into the scram-bled key box. Selecting ADJUST KEY FOR DVB MODE will modify the key sothat byte 4 is calculated based on bytes 1-3 and byte 8 is calculatedbased on bytes 5-7 per the DVB standard.

NOTE Some fixed-key DVB receivers may support the “User Mode” and some maysupport the “DVB Mode”. Novra’s S75 DVB receiver will support both.

VBR - Variable Bitrate

A VBR PID can be associated with the Dedicated PID Bundle (CBR), SharedPID Bundle (VBR) and ATM Profile traffic profile types. In the PARAMETERS sub-panel:

1. From the PID TYPE drop-down box, select VBR - VARIABLE BITRATE.

2. Enter the values for the GUARANTEED BITRATE (BPS), PEAK BITRATE (BPS) andPRIORITY fields, and select PACKING if required.

3. Click OK. The newly created PID will now appear in the LOCAL UPLINKFACILITY tree, under the selected traffic profile.FACILITY tree, under theselected traffic profile.





UBR - Uncommitted Bitrate

A UBR PID can be associated with the Dedicated PID Bundle (CBR), SharedPID Bundle (VBR), Uncommitted PID Bundle (UBR) and ATM Profile trafficprofile types. In the PARAMETERS sub-panel:

1. From the PID TYPE drop-down box, select UBR - UNCOMMITTED BITRATE.

2. Enter the value for the PRIORITY field, and select PACKING if required.




Remux Channel

A Remux Channel PID can be associated with the Remux Channel traffic pro-file type. In the REMUX PARAMETERS sub-panel:

1. Enter the value for the SOURCE PID field.


NOTE Incoming PAT table should never be mapped; This tables are generated auto-matically when an SI Tables profile is created.

Conditional Opportunistic

A Conditional Opportunistic PID can be associated with the ConditionalOpportunistic Session traffic profile type. In the DATA SERVER sub-panel:

1. Enter the values for the IP ADDRESS, PORT, TIMEOUT (MS) and GUARANTEEDBITRATE (BPS) fields, and select PACKING if required.

2. From the PROTOCOL drop-down box, select either TCP or UDP.

3. From the DATA SERVER TYPE drop-down box, select either NORSAT INTERNA-TIONAL or KENCAST FAZZTTM.






Strict Opportunistic

A Strict Opportunistic PID can be associated with the Strict Opportunistic Ses-sion traffic profile type. In the DATA SERVER sub-panel:

1. Enter the values for the IP ADDRESS, PORT and TIMEOUT (MS) fields, andselect PACKING if required.







An Uncontrolled Opportunistic PID can be associated with the UncontrolledOpportunistic traffic profile type. In the DATA SERVER sub-panel:

1. Enter the values for the IP ADDRESS, PORT and TIMEOUT (MS) fields, andselect PACKING if required.






Signaling Marker

A Signaling Marker PID can be associated with the Signaling Marker trafficprofile type:

1. In the SIGNALING MARKER sub-panel, select INSERT PCR if required.





The newly created PID (in this case a CBR), along with the description, arenow shown in the LOCAL UPLINK FACILITY tree; refer to Figure 13 on page 40.

FIGURE 15. New PID.

View PID Parameters

PID parameters can be viewed on the following two panels:

1. PID PROPERTIES panel; refer to “View PID Parameters via PID PROPERTIESPanel” on page 46.

2. TRAFFIC PROFILE PROPERTIES panel; refer to “View PID Parameters via TRAF-FIC PROFILE PROPERTIES Panel” on page 46.

View PID Parameters via PID PROPERTIES Panel

Individual PID parameters can be viewed in the PID PROPERTIES panel, whichcan accessed in the following way:

1. In the LOCAL UPLINK FACILITY tree, right click on the PID you want to viewthe properties of and select PID PROPERTIES from the resulting pop-upmenu.

NOTE The PID PROPERTIES panel also allows you to modify the PID parameters; referto “Modify PID Parameters” on page 47.

View PID Parameters via TRAFFIC PROFILE PROPERTIES Panel

To view the PID parameters for all of the PIDs associated with a traffic profile:

1. In the LOCAL UPLINK FACILITY tree, right click on the traffic profile and selectTRAFFIC PROFILE PROPERTIES from the resulting pop-up menu.

2. The TRAFFIC PROFILE PROPERTIES panel is then launched. The PIDs sub-panel, shown in Figure 16 on page 47, contains PID parameters for all ofthe PIDs associated with the chosen traffic profile.



FIGURE 16. PIDS Sub-panel.

Modify PID Parameters

With the exceptions of the TRANSPORT STREAM, TRAFFIC PROFILE and PID NUMBERfields, the PID parameters can be modified:

1. In the LOCAL UPLINK FACILITY tree right click on the PID whose propertiesyou would like to modify, and select PID PROPERTIES from the resulting pop-up menu.

2. The PID PROPERTIES panel is then launched; note that the TRANSPORTSTREAM, TRAFFIC PROFILE and PID NUMBER fields are greyed out. Modify theappropriate fields and click OK to save the changes; to close the panelwithout saving the changes, click CANCEL.

Deleting a PID

To remove a PID:

1. In the LOCAL UPLINK FACILITY tree, right click on the PID you would like todelete, and select DELETE PID from the resulting pop-up menu.

2. The CONFIRM DELETION window appears. To confirm the PID deletion clickYES; click NO to keep the PID.

NOTE When a PID is deleted, all routes and virtual channels associated with it areremoved from the database automatically. Refer to “Deleting a Route” onpage 51 for instructions on deleting a route. Refer to “Deleting a Virtual Chan-nel” on page 49 for instructions on deleting a Virtual Channel.



ATM Virtual Channels


• Add a new Virtual Channel

• View /modify Virtual Channel parameters

• Delete a Virtual Channel

Adding a Virtual Channel

Virtual Channels are configured in the VIRTUAL CHANNEL PROPERTIES panel. Thefollowing steps describe how to add and configure a new virtual channel:

1. In the LOCAL UPLINK FACILITY tree, right click on the PID that you want thevirtual channel to be associated with and select ADD NEW VIRTUAL CHAN-NEL from the resulting pop-up menu. The VIRTUAL CHANNEL PROPERTIESpanel is then launched; refer to Figure 17 on page 48.

NOTE A Virtual Channel can only be added to a PID that belongs to an ATM Profile.

FIGURE 17. VIRTUAL CHANNEL PROPERTIES Panel

2. For the new virtual channel:

i. The PID that you right-clicked on will be shown in the PID field, thetraffic profile that PID is associated with is shown in the TRAFFIC PRO-FILE field and the transport stream that the traffic profile is associatedwith is shown in the TRANSPORT STREAM field.



ii. Enter the virtual channel information in the VCI NUMBER and DESCRIP-TION fields.

3. Click OK. The newly created virtual channel, along with the description,are now shown in the LOCAL UPLINK FACILITY tree; refer to Figure 18 onpage 49.

FIGURE 18. New Virtual Channel

View/Modify Virtual Channel Parameters

After creation, the virtual channel parameters can be modified:

1. Right click on the virtual channel whose properties you would like to mod-ify, and select VIRTUAL CHANNEL PROPERTIES from the resulting pop-upmenu.

The VIRTUAL CHANNEL PROPERTIES panel is then launched. Modify the appropri-ate fields and click OK to save the changes; to close the panel without savingthe changes, click CANCEL.

Deleting a Virtual Channel

To remove a virtual channel:

1. Right click on the virtual channel you would like to delete, and selectDELETE VIRTUAL CHANNEL from the resulting pop-up menu.

2. The CONFIRM DELETION window appears. To confirm the virtual channeldeletion click YES; click NO to keep the virtual channel.

NOTE When a virtual channel is deleted, the routes associated with it are automati-cally removed from the database. Refer to “Deleting a Route” on page 51 forinstructions on deleting a Route.

Routes


• Add a new route

• View/modify route parameters

• Delete a route

Adding a Route

Routes are configured in the ROUTE PROPERTIES panel. The following stepsdescribe how to add and configure a new route:

1. There are two ways to launch the ROUTE PROPERTIES panel. In the LOCALUPLINK FACILITY tree, right click on:



i. The PID that you want the route to be associated with and select ADDNEW ROUTE from the resulting pop-up menu. The ROUTE PROPERTIESpanel is then launched; refer to Figure 19 on page 50.

ii. The Virtual Channel that you want the route to be associated with andselect ADD NEW ROUTE from the resulting pop-up menu. The ROUTEPROPERTIES panel is then launched; refer to Figure 19 on page 50.

FIGURE 19. ROUTE PROPERTIES Panel.

2. For the new route:

i. The PID that you are adding the route to will be shown in the PID field,the traffic profile that PID is associated with is shown in the TRAFFIC

PROFILE field and the transport stream that the traffic profile is associ-ated with is shown in the TRANSPORT STREAM field. If you are adding anATM route, the Virtual Channel that you are adding the route to will beshown in the VIRTUAL CHANNEL field.

ii. Enter the route information in the IP ADDRESS, NETMASK, MAC ADDRESSand DESCRIPTION fields.

iii. Select ENABLE HEARTBEAT if you wish this route to send out a HeartbeatPing (as was configured in the Transport Stream Properties - ref“TRANSPORT STREAM PROPERTIES Panel.” on page 31)

3. For routes not belonging to an ATM profile:

i. In the CHECK CONTROL drop-down box, select either NONE, CHECKSUMor CRC.



ii. Enter values in the PEAK BITRATE and MAX BURST fields, or leave blank ifnot required. These settings may be used to limit the traffic through-put of the route.

iii. Select LLC SNAP if required.iv. If the PID that the route is associated with has been configured with a

conditional access fixed key, then that key will be displayed in theROUTE PROPERTIES screen as a greyed out entity. The key can bechanged in the PID PROPERTIES screen (ref “PID PROPERTIES Panel.” onpage 42)

4. Click OK. The newly created route, along with the description, are nowshown in the LOCAL UPLINK FACILITY tree; for normal routes, refer toFigure 20 on page 51; for ATM routes, refer to Figure 21 on page 51.

FIGURE 20. New Route.

FIGURE 21. New ATM Route

View/Modify Route Parameters

After creation, all of the route parameters can be modified:

1. Right click on the route whose properties you would like to modify, andselect ROUTE PROPERTIES from the resulting pop-up menu.

The ROUTE PROPERTIES panel is then launched. Modify the appropriate fieldsand click OK to save the changes; to close the panel without saving thechanges, click CANCEL.

Deleting a Route

To remove a route:

1. In the LOCAL UPLINK FACILITY tree, right click on the route you would like todelete, and select DELETE ROUTE from the resulting pop-up menu.

2. The CONFIRM DELETION window appears. To confirm the route deletionclick YES; click NO to keep the route.



Database Backup

Transport streams in the database can be exported to, and imported from, anexternal text file.

NOTE It is important that only files exported from Transport Stream Manager beimported to the database, to ensure that the data format is correct.

Exporting Transport Streams

The user has the option of exporting transport streams individually, or export-ing all transport streams in the database. To export transport streams, performthe following steps:

1. To export all transport streams:

i. Right-click on LOCAL UPLINK FACILITY in Transport Stream Manager,and select SAVE AS.

ii. A dialog box will popup, allowing you to choose the filename andlocation of the exported data. Enter this information, and press OK tosave the transport streams.

2. To export a single transport stream:

i. Right-click on a transport stream in Transport Stream Manager, andselect EXPORT TRANSPORT STREAM.

ii. A dialog box will popup, allowing you to choose the filename andlocation of the exported data. Enter this information, and press OK tosave the transport stream.

NOTE If you choose to save a transport in a file that already exists, data in that filewill be overwritten.

Importing Transport Streams

The user has the option of importing individual transport streams, or importingmultiple transport streams. To import transport streams, perform the followingsteps:

1. To import multiple transport streams:

i. Right-click on LOCAL UPLINK FACILITY in Transport Stream Manager,and select OPEN.

ii. A dialog box will popup, allowing you to choose the filename andlocation of the data to import. Enter this information, and press OK toimport the transport streams.

iii. If a transport stream being imported has a transport stream ID thatalready exists in the database, the imported data will overwrite thedata in the database. Otherwise, it will simply be added to the tree.

2. To replace an individual transport stream:

i. Right-click on a transport stream in Transport Stream Manager, andselect IMPORT TRANSPORT STREAM.

ii. A dialog box will popup, allowing you to choose the filename andlocation of the data to import. Enter this information, and press OK toimport the transport stream.

iii. The transport stream information will be imported.

NOTE The information in the database for the transport stream you right-clicked willbe overwritten, with the exception of the transport stream ID. The transport



stream ID of the imported data need not match the desired target transportstream.


CHAPTER 4 Configuring the IPE

This chapter is designed to give step by step instructions on how to configureand manage the IPE using IPE Control Panel, including:

• Assigning transport streams

• Transport stream parameter configuration

• Statistics and monitoring

IPE Control Panel

The IPE Control Panel application will be used to configure and monitor theIPE units.

Launching IPE Control Panel

1. From the Windows toolbar, select Start Programs Novra IPEControl Panel. The main screen of the IPE Control Panel applicationlaunches; refer to Figure 22 on page 56.

NOTE A list of IPE’s that may be configured will be shown in the IP Encapsulator subpanel. The state and status of a selected IPE will be displayed as indicated in“IPE Management” on page 13.

Configuring the IPE


FIGURE 22. IPE Control Panel.

Configuring the IPE

The IPE can be configured in one of three ways. From the IPE Control Panelmain screen, either:

1. Select the IPE from the IP ENCAPSULATORS sub-panel, then click CONFIG-URE.

2. Right click on the IPE in the IP ENCAPSULATORS sub-panel, then click CON-FIGURE.

3. Double click on the IPE in the IP ENCAPSULATORS sub-panel.

The IPE CONFIGURATION window is then launched; refer to Figure 23 onpage 57.


Configuring the IPE Page 57

FIGURE 23. IPE CONFIGURATION Window.

Assigning Transport Stream(s)

Once a transport stream has been created in Transport Stream Manager, itcan be assigned to an IPE unit(s); refer to ”Chapter 3: Transport Stream Man-agement” on page 27 for setting up transport streams. In the TRANSPORT STREAM sub-panel:

1. In the TRANSPORT STREAM field, enter the number of the transport stream tobe assigned to the IPE.

2. More than one transport stream may be assigned to an IPE. This is use-ful if the IPE is used in a 1:N Redundancy mode and is the standby unitfor several other IPE’s. To asign multiple transport streams to the IPE,select 1:N REDUNDANCY. Additional transport stream assignment optionswill then be displayed; refer to Figure 24 on page 58.

NOTE Selecting 1:N REDUNDANCY will automatically set the MODE to LATCH.

Configuring the IPE


FIGURE 24. 1:N Redundancy Options.

i. To add a transport stream, click ADD. The ADD TRANSPORT STREAMpanel is then launched; refer to Figure 25 on page 58.

FIGURE 25. ADD TRANSPORT STREAM Panel.

ii. Enter the number of the NEW TRANSPORT STREAM, then click OK; clickCANCEL to return to the IPE CONFIGURATION without adding a newtransport stream. The added transport streams are displayed in theTRANSPORT STREAM list.

iii. To delete a transport stream, highlight the transport stream number inthe TRANSPORT STREAM list, then click REMOVE.

iv. To edit a transport stream number, highlight the transport streamnumber in the TRANSPORT STREAM list, then click EDIT.

Configuring Mode Parameters

1. In the MODE sub-panel, select either the AUTO (DEFAULT), ACTIVE, PASSIVEor LATCH radio button.

Enable External Input Signal

1. When the ENABLE EXTERNAL SIGNAL INPUT is selected, the IPEactive/passive state may be controlled by an external signal input (ref“Enable External State Signal” on page 16).

NOTE When this option is selected, the operator loses the ability to manually set theIPE state, as well as use 1:N redundancy.

NOTE When the External Signal State is enabled, the watchdog relay contact clo-sure (ref “Enable External State Signal” on page 16) will remain open (normaloperation) and the IPE output will remain acitve, despite the IPE going pas-sive or active.



NOTE If the External Signal State is NOT enabled, the watchdog contact closurerelay (ref “Enable External State Signal” on page 16) will be set depending onthe passive/active state of the IPE and the IPE output will be muted when theIPE is set passive.

Configuring RIP Parameters

1. In the RIP BROADCAST sub-panel, select ENABLED if you want to enable RIPmessages, then:

i. Enter a value for PERIOD (in seconds); the default value is 15.

NOTE If you do not want RIP enabled, ensure that the ENABLED checkbox is de-selected.

2. Click OK.

Configuring NTP Parameters

1. In the NTP CLIENT CONFIGURATION sub-panel, select ENABLED if you want toenable NTP requests, then:

i. Enter a value for NTP SERVER (an IP address or hostname); the defaultvalue is blank.

NOTE If you do not want NTP enabled, ensure that the ENABLED checkbox is de-selected.

2. Click OK.

NOTE The NTP client will not change by more than 54000 seconds (15 hrs), so a dif-ference exceeding this amount will do nothing.

NOTE Recommended time source: time.nist.gov.

NOTE When using the NTP client, ensure both the Mgmt NIC and the Traffic NIC areconnected.

Monitoring the IPE

IP ENCAPSULATORS Sub-panel

The IP ENCAPSULATORS sub-panel, located on the main screen of the IPE Con-trol Panel, displays a table containing the following information for each IPE inthe system; refer to Figure 26 on page 59:

FIGURE 26. IP ENCAPSULATORS Sub-panel.

Configuring the IPE


• MANAGEMENT IP: the management IP address.

• TRANSPORT STREAM: the number(s) of the assigned transport stream(s).

NOTE For 1:N redundancy, where more than one transport stream is assigned to anIPE, the currently active transport stream is denoted in brackets under theSTATE column.

• MODE: indicates the current mode in which the IPE is running.

• STATE: indicates whether the current state is ACTIVE, PASSIVE, EXCEPTION orOFFLINE.

• RANK: indicates the current rank of the IPE.

• STATUS: indicates whether the current status is UNCONFIGURED, CONFIG-URED, or CONFIGURING....

Version Information

Version information for the IPE software can be accessed in one of two ways:

1. Select the IPE from the IP ENCAPSULATORS sub-panel, then click VERSION.

2. Right click on the IPE in the IP ENCAPSULATORS sub-panel, then click VER-SION in the resulting popup menu.

The VERSION dialog box is then launched; refer to Figure 27 on page 61.



FIGURE 27. VERSION Dialog Box.

Configuration Details

If an IPE has gone into an INCOMPLETE state, additional information regardingthe reason for this can be viewed by entering the DETAILS sub-panel. This canbe accessed in one of two ways:

1. Select the IPE from the IP ENCAPSULATORS sub-panel, then click DETAILS.

2. Right click on the IPE in the IP ENCAPSULATORS sub-panel, then clickDETAILS in the resulting popup menu.

The DETAILS dialog box is then launched; refer to Figure 28 on page 62. Thedialog box will contain a list of possible reasons that the IPE was misconfig-ured, such as details of any license file violation.

Configuring the IPE


FIGURE 28. DETAILS Dialog Box

Real-Time Statistics

The IPE Control Panel displays real-time statistics for:

• Output and input PIDs

• Routes

• MACs

• Output and input transport streams

Output PID, Input PID, Virtual Channel, Route and MAC Statistics

The REAL-TIME STATISTICS sub-panel, located on the main screen of the IPEControl Panel, displays the statistics for output PIDs, input PIDs, ATM VirtualChannels, routes and MACs in either graphical or tabular format.

Add/Remove Items

A single instance of IPE Control Panel can monitor up to a maximum of tenitems simultaneously. To select the list to be monitored:



1. Select the IPE you want to monitor from the IP ENCAPSULATORS sub-panel,then click the ADD/REMOVE button in the REAL-TIME STATISTICS sub-panel.The ADD/REMOVE window appears; refer to Figure 29 on page 63.

FIGURE 29. ADD/REMOVE Window.

2. The OUTPUT PIDS, INPUT PIDS, VCS, ROUTES and MACS available to be mon-itored appear in the AVAILABLE ITEMS sub-panel. The items selected to bemonitored appear in the SELECTED ITEMS sub-panel.

3. To add an item to the SELECTED ITEMS tree, either:

i. Select the item from the AVAILABLE ITEMS tree, then click the > button.ii. Double click on an item in the AVAILABLE ITEMS tree.The selected item will now appear in the SELECTED ITEMS tree.

4. To remove an item from the SELECTED ITEMS tree, either:

i. Select the item from the SELECTED ITEMS tree, then click the < button.ii. Double click on an item in the SELECTED ITEMS tree.

5. To remove all of the items in the SELECTED ITEMS tree, click the << button.

6. When you are done adding/removing items, click OK; To close withoutapplying changes, click CANCEL.

Configuring the IPE


Clear All.jpg

The statistics for the selected items will now be displayed in the REAL-TIME STA-TISTICS sub-panel.

Graphical Display

To display the statistics in graphical format for the IPE that is currentlyselected in the IP ENCAPSULATOR sub-panel:

1. Select GRAPHICAL from the DISPLAY MODE drop-down box in the REAL-TIMESTATISTICS sub-panel (Figure 30 on page 64).

FIGURE 30. REALTIME STATISTICS Sub-panel: Graphical PID Statistics Display.

2. A graph isshown that displays the bitrate, in Mbps, of each selected item. The itemtype, as indicated by the colour of the bar, is indicated in the BAR GRAPHLEGEND window. To launch the BAR GRAPH LEGEND window, click LEGEND;refer to Figure 31 on page 64.

FIGURE 31. BAR GRAPH LEGEND Window.

3. The scale of the graph can be adjusted:

i. Click on the + button to zoom in.



ii. Click on the - button to zoom out.iii. Click on the 1:1 button to return to the initial view.

4. A table is shown that displays the BITRATE and TS PACKETS, in numerical for-mat, for each item selected in the poll list.

Tabular Display

To display the statistics in tabular format for the IPE that is currently selectedin the IP ENCAPSULATOR sub-panel:

1. Select TABULAR from the DISPLAY MODE drop-down box in the REAL-TIMESTATISTICS sub-panel (Figure 32 on page 65).

FIGURE 32. REALTIME STATISTICS Sub-panel: Tabular PID Statistics Display.

2. A table is shown that displays the PACKETS SENT, PACKETS DROPPED, KBSENT, KB DROPPED, BITRATE and TS PACKETS for each item selected in the polllist.

NOTE Not all fields in the table apply to all items; these fields will contain a ‘-’.

NOTE If no statistics are being received for a selected item, the fields in the table forthat item will be blanked out. This may indicate that the item no longer existson the IPE due to a configuration change.

NOTE To clear the counters in the table, click the CLEAR ALL button. This will clearthe displayed counters, however the internal counters on the IPE will not becleared.

View Input PIDs

To automatically display the traffic statistics associated with the ASI inputPID’s in tabular format for the IPE that is currently selected in the IP ENCAPSUL-SATOR sub-panel:

1. Select VIEW INPUT PIDS button in the REAL-TIME STATISTICS sub-panel This willdisplay the traffic statistics of the input PID’s as shown in Figure 33 onpage 66).

Configuring the IPE


FIGURE 33. View Input PID Statistics Sub-panel

Multiplexer Usage

The MULTIPLEXER USAGE sub-panel, located on the main screen of the IPE Con-trol Panel, displays output and input transport stream statistics in graphicalformat; refer to Figure 34 on page 66.

FIGURE 34. MULTIPLEXER USAGE Sub-panel.

The statistics are shown for the IPE that is currently selected in the IP ENCAP-SULATORS sub-panel. A single input bar will be displayed for each input cardpresent on the selected IPE.

Output Transport Stream Statistics

The output transport stream display contains:

1. A colour bar indicating the percentage of payload bitrate.

2. The current payload bitrate out of the total multiplexer bitrate.

A bar colour of green indicates that the output multiplexer is operating nor-mally.

Additionally, the total number of TS packets out for the output multiplexer canbe viewed by placing the mouse over the output transport stream bar. A tool-tip will popup displaying the current TS out packet count.

Input Transport Stream Statistics

Each input display contains:

1. A colour bar indicating the percentage of payload bitrate.

2. The current payload bitrate out of the total multiplexer bitrate.

The colour of the bar indicates the status of the input; refer to Table 1 onpage 67.



TABLE 1. Input Transport Stream Bar Colours.

Additionally, the total number of TS packets in, sync errors and overruns forthe input card can be viewed by placing the mouse over the Input bar. A tool-tip will popup displaying this information.

NOTE If the overruns or sync errors are detected during the current session, the dis-played number of TS packets for the entire input and any monitored inputPIDs on that input card will be preceded by a > (greater than) symbol, to indi-cate that the displayed value may actually be less than the actual value.

Historical Statistics

To view historical statistics for the IPE that is currently selected in the IPENCAPSULATORS sub-panel:

1. Click on the HISTORICAL button in the REAL-TIME STATISTICS sub-panel. TheHISTORICAL STATISTICS window appears (Figure 35 on page 68).

Colour Description

Green Normal operation.

Red A sync error or overrun has occurred; cleared after 5 seconds with no error.

Grey Inactive; no profile set up for the card.

Configuring the IPE


FIGURE 35. HISTORICAL STATISTICS Window.

2. Adjust the REFRESH INTERVAL slide-bar to the desired refresh rate. The TIMEscale of the graph will automatically adjust to the set REFRESH INTERVAL.

3. The items being monitored, and the colour indicating that item on thegraph, are displayed in the LEGEND sub-panel.

4. The BITRATE (MBPS), versus TIME (HH:MM:SS) is displayed in the graph foreach input listed in the LEGEND sub-panel.

5. Clicking CLOSE will exit from the HISTORICAL STATISTICS window, and returnto the IPE Control Panel main screen.

Configuring the IPE



CHAPTER 5 Maintaining the IPE

The IPE requires little maintenance; cleaning and inspection frequencies willvary depending on the location and conditions of use. For best results, set upa cleaning and inspection schedule and adjust the frequency as experiencedictates. For more details on maintenance, refer to the chassis manual pro-vided with the IPE shipment.

NOTE Replacing network interface cards and making other changes in hardwareconfiguration are among maintenance procedures that fall outside the scopeof this manual, and will void the warranty.

Visual Inspections

Air Passages

Inspect the system periodically to ensure that air can pass freely through thecooling vents, fans and air filters. Use a vacuum cleaner to clear away dust orlint that may have accumulated in air passageways and could cause the sys-tem to operate at above normal operating temperatures.

NOTE Vacuum from the dirty side of the filter for maximum cleaning efficiency.

Cables

Ensure that all external IPE cabling is secure, and that excessive cable ten-sion does not place the cables under strain.

Maintaining the IPE


Cleaning the Unit

Use a damp cloth to clean the IPE case. For the label, use a low-lint laboratorytissue and window cleaner.


CHAPTER 6 Troubleshooting

This chapter discusses features that allow you to troubleshoot the IPE, includ-ing:

• General troubleshooting tips.

General Troubleshooting Tips

1. Check all cable connections to ensure they are secure and correctlyhooked up.

2. Check your external power source to ensure the source is stable.

3. If you had any other applications running on your PC while you attemptedto install the Novra monitoring and control software, including anti-virussoftware, close the applications and try again.

4. If you do not see data traffic on a particular PID, ensure you haveassociated an IP route with it. If there is a route associated with that PID,ensure it is the correct route(s). The Transport Stream Manager will giveyou a summary of PIDs and IP routes.

5. Ensure the operating system of the Management Station meets therequirements: Windows 2000™ with at least SP2.

6. Ensure the output multiplexer bitrate you specified matches the bitrate foryour external modulator or remultiplexer.

7. If you cannot access the Transport Stream Manager remotely through theManagement Station, try to access it directly through the IPE itself. If thataccess works, there is something wrong with your Management Stationinstallation or network LAN connection.

8. You may have exceeded the cable length limits; refer to “CableConnections” on page 20 for the cable length limits.

9. If the IPEService.exe service is running at 99% CPU utilization and youhave multiple IPE’s on the same subnet, ensure they do not have thesame name (e.g. IPE-4). Use Start -> Control Panel -> System ->Computer Name to change.

Troubleshooting


IPE Control Panel

The IPE Control Panel also provides information that will aid in troubleshoot-ing.

1. If a mode of Exception appears for the IPE in IPE Control Panel, perform the following tasks:

i. Disconnect all of the connectors, excluding the power cable and Ethernet cables, from the back of the IPE.

ii. Restart the IPE.iii. Verify that the IPE has rebooted correctly by viewing its status in IPE

Control Panel. If a mode of Exception appears for the IPE, contact Novra Customer Support.

iv. Reconnect the cables on the back of the IPE one by one, waiting at least 30 seconds between connections. If the mode changes to Exception after connecting a specific cable, take note of which cable is causing the problem and contact Novra Customer Support.

5. No traffic is being passed by the IPE.

i. Ensure the IPE routes are correctly set up (correct IP address and netmask).

i. Ensure traffic NIC is connected.ii. If RIP is being used to announce routing to upstream devices, ensure

the Enable Rip box is checked. Try un-checking the Enable Rip box and re-checking it.

iii. Try setting the IPE passive and the active.iv. Try changing the Transport Stream number to a unused value. Let the

IPE synchronize on this value (you should see Unconfigured in the Status field. Change the Transport Stream number back to your previ-ously configured value.

v. Contact Novra Support.

Hard Drive Replacement

NOTE This feature is available for the 520 Model IPE only.

Locating a Failure

If one of the two redundant hard drives fails, then the following messagewill appear on the screen: “A disk that is part of a fault-tolerant volumecan no longer be accessed". To determine which hard drive has failed, per-form the following:

1. Click OK to dismiss this warning message.

2. In order to determine which one of the two disks has failed, click Start -> Programs -> Administrative Tools -> Computer Management.

3. Click on Disk Management.

4. The list of disks that is displayed in the bottom right hand corner of the screen which would normally show "DISK 0" "DISK 1" and "CDROM 0" will have one of the disks labelled as “MISSING".

5. If "DISK1" is missing, then you can replace DISK1 and restore the fault-tolerant file system with no interruption in traffic, follow the directions in the section "Replacing DISK1".

6. If "DISK 0" is missing, then you will need to re-start the IPE after DISK0 has been replaced, follow the directions in the section "Replacing DISK0".


Troubleshooting Page 75

Replacing DISK1

To replace DISK1 in the event of a failure, perform the following:

1. In order to remove the failed disk from the chassis, open the front bezel and locate the disk with ID number 1.

2. Remove the disk from the carrier and replace it with a new one, or replace the entire disk/carrier combination. Note that the new disk must be com-pletely empty and must not contain any partitions or any other data.

3. Insert the new disk into the chassis, push the handle all the way to the end. Wait 15 seconds for the new disk to spin up.

4. Press F5 to refresh the disk manager screen, the new disk should now appear in the list and its entire capacity should show up as "Unallocated"

5. Right click on the partition labelled "Failed Redundancy" and select "Remove Mirror"

6. Select the partition labelled as "Missing", click "Remove Mirror" and click "Yes"

7. Right click on the disk labelled as "Missing" and select "Remove Disk"

8. Right click on the disk labelled as "Disk 1" and select "Upgrade to Dynamic Disk" and click "OK"

9. Right click on "C:" and select "Add Mirror"

10. Select "Disk 1" and click "Add Mirror"

11. Click OK

12. Wait until the regeneration reaches 100%

13. Verify that both disks are now labelled as "Healthy".

14. Close the Computer Management window.

Replacing DISK0

To replace DISK1 in the event of a failure, perform the following:

1. In order to remove the failed disk from the chassis, open the front bezel and locate the disk with ID number 0.

2. Remove the disk from the carrier and replace it with a new one, or replace the entire disk/carrier combination. Note that the new disk must be com-pletely empty and must not contain any partitions or any other data.

3. Insert the new disk into the chassis, push the handle all the way to the end

4. Wait 15 seconds for the new disk to spin up.

5. Press F5 to refresh the disk manager screen, the new disk should now appear in the list and its entire capacity should show up as "Unallocated"

6. Right click on the partition labelled "Failed Redundancy" and select "Remove Mirror"

7. Select the partition labelled as "Missing", click "Remove Mirror" and click "Yes"

8. Right click on the disk labelled as "Missing" and select "Remove Disk"

9. Right click on the disk labelled as "Disk 0" and select "Upgrade to Dynamic Disk" and click "OK"

10. Click Start -> Shutdown -> Shutdown -> OK

11. Wait for the IPE to shut down.

12. Press the power switch in the front of the unit to power off the IPE.

Troubleshooting


13. Physically swap DISK0 and DISK1.

14. Power on the IPE.

15. Wait for the IPE to start up.

16. Log in with your name and password.

17. Click Start -> Programs -> Administrative Tools -> Computer Manage-ment.

18. Click on Disk Management.

19. Right click on "C:" and select "Add Mirror"

20. Select "Disk 1" and click "Add Mirror"

21. Click OK

22. Wait until the regeneration reaches 100%

23. Verify that both disks are now labelled as "Healthy".

24. Close the Computer Management window.


Troubleshooting Page 77

Troubleshooting



Index

AAbbreviations viii

Acronyms viii

ASI 20, 26

BBatteries

lithium 19

Boot Drive Switching 74

CCable Connections

Ethernet 20MPEG-2 Transport Stream 20Power 21

Common Tasks 29, 52

Compliance 19

Configuring IP Addresses 22

Changing IP Addresses 23Default IP addresses 22

Connecting to FacilityInstalling Hardware 24

Copyright iii

DDefinitions viii

Definitions, Abbreviations and Acronyms vii

Dimensions 4

Disclaimer iii

DVB ASI interface 26

EEthernet interfaces 26

FFacility Interfaces Management Station

Security 20Ventilation 20

Facility Interfaces Required 20

Management Station 20

Facility interfaces requiredable interfaces 20security 20

Frequent PC Resets 17

GGeneral Troubleshooting Tips 73

Frequent PC Resets 17IPE Control Panel 74Switching the Boot Drive 74Watch Dog Card 17

External Connections 17

HHumidity 3

IInstallation

power mainsconnection 25

InstallingCable Connections 20Checking the Equipment 19

Index


Connecting to Facility 24Facility Interfaces Required 20User Interfaces 24

Management Software 24

Interfaces 26

IP 22, 23

IP addresses 26

IPE Control Panel 55, 74

General Troubleshooting 74Launching 55

IPE-400Configuring 56

Mode Parameters 58RIP Parameters 59

ManagementMode 14Rank 14RIP Parameters 14State 15Status 15

Monitoring 59Historical Statistics 67Real-Time Statistics 62

Specifications 1Compliance 3Hardware 4Input Physical Interfaces 2Key Features 2Management 2Operating 3

Dimensions 4Humidity 3Power Consumption 4Power Supply 4Shipping Weight 3Temperature 3

Option Packs 4ATM 5Remux 4Security 4

Output Physical Interfaces 3Protocols Supported 3

Traffic Profiles and PIDs 5Multiprotocol Encapsulation 6Opportunistic Data 8

Opportunistic Session 8Uncontrolled Opportunistic 11

Remux Channel 7SI Tables 7Signaling Marker 12

Transport Streams 5

LLithium batteries 19

MMAC 26

MaintenanceCleaning the Unit 72Visual Inspections 71

Air Passages 71

Cables 71

Mode 14

Auto 14Configuring Parameters 58Forced-Active 14Latch 14

Mode, IPE-400Forced-Passive 14

Multiprotocol Encapsulation PIDs 6

NNIC 23

OOption Packs 4

ATM 5Remux 4Security 4

PPIDs 41

Creating 41CBR - Constant Bitrate 43Conditional Opportunististic 44Remux Channel 44Signalling Marker 45, 46Strict Opportunistic 45UBR - Uncommitted Bitrate 44Uncontrolled Opportunistic 45VBR - Variable Bitrate 43

Deleting 47Modify Parameters 47Overview

Conditional Opportunistic 9Constant Bitrate (CBR) 6Remux 7Signaling Marker 12Strict Opportunistic 10Uncommitted Bitrate (UBR) 7Uncontrolled Opportunistic 11Variable Bitrate (VBR) 7

View Parameters 46

Power Consumption 4

Power Mains 25

Power Supply 4

Protocols xi

RRank 14

RIPConfiguring Parameters 59

RIP Parameters 14

Period 14, 16Timeout 15

Routes 49


Index Page 81

Adding 49Deleting 51View Parameters 51

Routing 26

SSafety 19

Security 20

Shipping Weight 3

Standards xi

State 15

Active 15Not Responding 15Passive 15

Statistics 62

Graphical Display 64Historical 67Input PID 62MAC 62Multiplexer Usage 66Output PID 62Route 62Tabular Display 65VC 62

Status 15

Synchronized 15Unsynchronized 15

Switching the Boot Drive 74

TTemperature 3

Text Conventions vii

Trademark iii

Traffic Profiles 35

Creating 35ATM Profile 39Dedicated PID Bundle (CBR) 37Opportunistic Session 38Remux Channel 38Shared PID Bundle (VBR) 37SI Tables 38Signalling Marker 39Uncommitted PID Bundle (UBR) 37Uncontrolled Opportunistic 39

Deleting 40Overview 5

Conditional Opportunistic Session 9Multiprotocol Encapsulation 6

Dedicated PID Bundle (CBR) 6PIDs 6Shared PID Bundle (VBR) 6Uncommitted PID Bundle (UBR) 6

Remux Channel 7SI Tables 7Signaling Marker 12Strict Opportunistic Session 10Uncontrolled Opportunistic 11

View/Modify Parameters 40

Transport Stream Manager 27

Transport Streams 30

Assigning 57Creating 30Deleting 35Managing 27Overview 5View/Modify Parameters 35

VVentilation 20

Version Information 60

Virtual ChannelsDeleting 49View/Modify Parameters 49

WWatch Dog Card 17

External Connections 17

Index



NOVRA TECHNOLOGIES, INC.

Head Office900-330 St. Mary AvenueWinnipeg, Manitoba Canada R3C 3Z5Tel: 204-989-4724 Fax: 204-989-4640E-mail: [email protected]

Download - IPE Manual.book(IPE Cover.fm)DVB DSM-CC multiprotocol encapsulation standard. The IPE output is an MPEG-2 transport stream on a DVB MPEG-2 ASI/SPI physical interface. The IPE feeds

Top Related