Harmonic Broadcast Devices

BNG 6000, ProStream 1000, bNSG 9000

Application Note
Redundancy Methods

Document ID: AN-PS1K-1001 Rev. D August 2007

ii

Revision History
Revision A B Date August 2006 April 2007 Description Creating the document By Tova, Along G.

ProStream 1000 - Port redundancy Tova bNSG 9000 - Device and Socket Redundancy in

C D

August 2007 September 2007

ProStream 1000 - Socket redundancy

Tova

ProStream 1000 - Port redundancy Tova, Amit K

Redundancy Overview 1

Redundancy Overview
In order to ensure the continuous transmission of video streams, broadcasting networks employ various protection or redundancy options. The following document describes the redundancy options that NMX (Harmonics Digital Service Manager) provides. The document describes the redundancy options together with the device that supports this option. Thus, this application note informs you of the available redundancy options when using the following devices:

BNG 6000 ProStream 1000 bNSG 9000

This application note also allows you to better plan and construct your broadcasting network. Following is a description of each redundancy method and a table that sums up all the methods discussed in the document.

Device Redundancy
The device redundancy protects the network from a faulty broadcasting device. Redundancy Method - Device Redundancy Harmonic Devices - BNG, ProStream1000, bNSG 9000 Description - The device redundancy is supported in either of the following configurations: Note: bNSG 9000 supports 1:1 Hot redundancy only.

N : 1 redundancy Any number of devices in the network are broadcasting. One device in the network is reserved as a backup device to any of the broadcasting devices. When one of the broadcasting devices fails, NMX may provision the backup device to broadcast instead of the failed device. This method results in relatively long fail-over time.

Device Redundancy 2

Fail-over time estimated range is 10 - 30 seconds, depending on the map size, i.e. the number of services that the device is carrying. When the content is scrambled, the fail-over time is longer. It takes about 30 - 90 seconds to establish the connection with the CA system and scramble all the services. Until this is complete, the content is transmitted as clear. It is possible to configure the device to block services with sensitive content until connection with the CA system is established. (See Scrambling Over-ride in the NMX Help.)

1:1 Hot redundancy

Both the primary and the backup devices are configured the same and are provisioned with the same TSs. However, the backup output ports may be either disabled or blocked by a downstream switch. This redundancy method allows short (up to a few seconds) fail over-time.

Note: In certain networks, when both the primary and the backup devices are broadcasting, conflict may occur. The latter may be prevented by enabling the HHP option. For details, see Harmonic Hello Protocol (HHP) on page 5. When to Use - When short fail-over time is required. Triggering Alarms -The following tables describe the device redundancy triggering alarms raised by NMX and by each device.

Table 1: NMX Alarms - Device Redundancy

NMX Alarms Timeout Offline Hardware Mismatch Port Offline Description NMX issues this alarm when losing connection with the device. NMX issues this alarm when device operates in Offline mode, usually due to maintenance. NMX issues this alarm when its configuration does not match the actual device connected. NMX issues this alarm when detects that a configured port is offline.

Device Redundancy 3

Following is a list of alarms issued by the BNG device. These alarms are by default defined in NMX as Service Affecting and therefore trigger device redundancy:

UC Loss of Input Sync UC Power Supply Failure UC Connection Failure UC PLL1 Problem UCPLL2 Problem UC Internal Communication Error Input GbE Port Failed Output GbE Port Failed

Following is a list of alarms issued by the ProStream 1000 device and that by default are defined in NMX as Service Affecting:

SFP Missing - Port Down Hardware Mismatch (GbE Card) High Temperature Failure (GbE Card) Hardware Failure (ASI Card) High Temperature Failure (GbE Input) CRC Error GbE Link Down GbE SFP Missing (ASI Card) Hardware Failure

Following is a list of alarms issued by the bNSG 9000 device and that by default are defined in NMX as Service Affecting:

GbE Port Failed Master Off State GbE Controller Failure General HW Failure Communication Failure

Device Redundancy 4

PLL1 Failure Pll2 Failure

Note: NMX allows you to define whether an alarms is service affecting or not. Configure the alarms with extreme caution according to your preferences and network design. For further details, see NMX Online help. Reverting to Primary - When device redundancy takes place, NMX switches to the primary device only if the primary device is fixed and the backup device fails.

Device Redundancy 5

Harmonic Hello Protocol (HHP)

The Harmonic Hello Protocol allows devices with GbE I/O interface to communicate between them via the video-over-IP network. HHP prevents conflicts between the devices in case NMX loses communication with one of the devices. It prevents devices from streaming out data to the same destination and with identical output configuration which results in conflicts and service interruption. HHP also improves the systems redundancy performance, and shortens the fail-over time. Harmonic Devices - HHP applies to the following Harmonic devices:

BNG 6104(1G2A), 6108, 6202(1G2A), 6301 ProStream 1000 bNSG 9000

When to Use - HHP applies only to GbE I/Os and using this protocol depends on the supported GbE I/Os and device setup:

Table 2: Using HHP

GbE I/O and Device Setup IP in to IP out IP in to QAM-RF out ASI in to IP out IP in to ASI out Always use HHP Always use HHP Always use HHP HHP is unnecessary. Using HHP shortens failover time but makes troubleshooting more complex. Using HHP

Content/Link Redundancy 6

Content/Link Redundancy
The following redundancy methods relate to content redundancy:

GbE port redundancy Input socket redundancy Input program redundancy

These methods protect the network from a fault upstream from the device, and not from a faulty device due to hardware failure. Reverting to Primary - When port, socket or program redundancy takes place, the backup port, socket or program is streaming content unless you manually switch to the primary once it is fixed. NMX does not switch automatically to the primary once it is fixed. The following table compares between the three methods:

Table 3: Content Redundancy

Redundancy Method GbE Port Port/Link Setup Two identical GbE links are connected to two ports, primary and backup Socket Config (IP, UDP) Both links carry identical content (sockets, services) Devices BNG 6104, 6108 6202(1G2A) (input) BNG 6301 (output) ProStream 1000 Socket Two sockets, primary and backup flow over a single GbE link Two different sockets BNG 6104, 6108, 6202(1G2A) bNSG 9000 ProStream 1000 Program Two services, primary and backup flow over any GbE link connected to the device. Links are either identical or distinct Typically, primary and backup services flow over different sockets ProStream1000

Content/Link Redundancy 7

GbE Port Redundancy

Redundancy Method - Port Redundancy Harmonic Devices

BNG with GbE input ports (BNG 6104, 6108 and 6202(1G2A)) BNG with GbE output ports (BNG 6301) ProStream 1000 with port redundancy enabled

Description - The GbE port redundancy is supported in the following configuration:

The BNG device has one logical port with two channels (SFP). When a failure is detected on one of the channels, the backup input/output channel is working. ProStream 1000 - once port redundancy is enabled both channels of the logical port work in redundancy mode and not as two independent ports. When port redundancy is enabled and a failure is detected on one of the channels, the backup input/output channel is working.

When to Use - In case any of the following applies to your broadcasting network:

Input over IP - both channels continuously receive the same input stream. Output over IP - both channels are connected to the same destination, typically through different IP networks.

Triggering Alarms - The triggering alarms are as follows:

Content/Link Redundancy 8

Table 4: BNG/ProStream Alarms - Port Redundancy

BNG/ProStream Alarm GbE CRC Error GbE Master Link Down GbE Master SFP Missing ProStream Only GbE Auto-Negotiation Failed Description The device detects input CRC errors on the GbE input /output card. The device issues this alarm when the cable of the first GbE port is not connected. The device issues this alarm when the SFP connector is missing from the first GbE port. The handshake protocol with the switch failed.

Indicative Alarms - Backup Channel Activated As long as the backup channel is active, the alarm Backup Channel Activated is asserted to inform the user that the primary link is out of order. Escalation - In case both channels (primary and backup) fail, the device issues the alarm Port Failed. NMX handles such an alarm as service affecting and therefore triggers device redundancy. Reverting to Primary - manual only. Note: In DToIP systems where both ProStream devices and encoders are included in the same NMX map, and ProStream port redundancy takes place due to a fault on the switch, also the encoders start streaming via their backup port. When reverting to primary, you must use NMX Spreadsheet view to revert to the primary port of both ProStream devices and encoders.

Content/Link Redundancy 9

Input Socket Redundancy

Redundancy Method - Socket Redundancy Harmonic Devices - BNG (6104 and 6108), bNSG 9000, ProStream 1000 Description - In input socket redundancy the following three conditions should apply:

One access point is defined with two separate IP sockets that is different IP and UDP port combination. Both sockets are streamed in via the same GbE port. One socket is defined as primary and the other as a backup socket.

When the channel detects complete data loss on one socket, it activates the backup socket and tries to receive the same PIDs from the backup socket. When to Use - In case a single channel continuously receives the same input stream over two different sockets. Triggering Alarms - GbE Primary Socket Not Active Indicative Alarms - Backup Socket Activated (indicates that a redundancy switch has taken place.) Escalation - If both primary and backup sockets fail, the device issues the alarm GbE Socket Failed. As a result, NMX activates the Alarm Correlation Mechanism which attempts to resolve the problem upstream from the device. Note: To allow the backup socket to stream out different PIDs, use the Service Reference feature. For details, refer to the NMX Online Help.

Content/Link Redundancy 10

Program Redundancy (for IP-based Services Only)

The program redundancy switch has a unique triggering mechanism. The redundancy switch is triggered by a program underflow and not by an alarm as other redundancy methods. The related alarms only indicate that a redundancy switch has taken place. The user can configure the triggering condition by defining when to activate the redundancy switch:

program underflow program PID underflow

For further information, see NMX Online Help. Redundancy Method - Program Redundancy Harmonic Devices - ProStream 1000 Description - Users can specify two alternative sources for a single output service. In case the primary source fails, the content of this service is streamed from the backup source, to ensure uninterrupted service. Currently, program redundancy applies only to programs that are provisioned in RSS (Reference Service) mode, and flow from IP inputs to IP outputs. When to Use - If your network structure allows sending the same content (service) over multiple IP links using any socket configuration. Triggering Alarms - Redundancy is activated by an underflow of the program or a PID of the program as defined by the user. (See NMX Online Help) Indicative Alarms - Backup Program Activated Service Failure - In case also the backup fails, this alarm is asserted. Escalation - No escalation path

Redundancy Methods - Summary Table 11

Redundancy Methods - Summary Table

The following table lists the redundancy methods available when using NMX system and BNG and/or ProStream 1000 Harmonic devices. In addition, the table lists the alarms that trigger each of the redundancy methods.
Redundancy Method Harmonic Device Triggering Alarms Device
Device Redundancy BNG U/C Sync Loss U/C Power Supply Failure U/C Connection Failure U/C PLL1 Problem U/C PLL2 Problem U/C Internal Communication Problem GbE Port Failed GbE Port SFP Missing GbE Input Socket Buffer Overflow Card Missing Card Mismatch GbE Card Temp. Sense Exceeds Limits GbE Card Hardware Failure ASI Card Temp. Sense Exceeds Limits ASI Card Hardware Failure GbE Port Failed Master Off State GbE Controller Failure General HW Failure Communication Failure PLL1 Failure Pll2 Failure GbE CRC Error GbE Master Link Down GbE Master SFP Missing N.A

NMX
Timeout Offline Hardware Mismatch Port Offline

ProStream 1000

bNSG 9000

GbE Port Redundancy

BNG 6104, 6108, 6202(1G2A), 6301 ProStream 1000

GbE Auto-Negotiation Failed (ProStream 1000 only)

Redundancy Methods - Summary Table 12

Redundancy Method

Harmonic Device

Triggering Alarms Device NMX

N.A

Socket Redundancy

BNG 6104, 6108, 6202(1G2A) bNSG 9000 ProStream 1000 ProStream 1000

GbE Primary Socket Not Active

Program Redundancy

Triggered by program underflow or program PID underflow - configurable by the user.

N.A