...

Failover (optional)

Starting with Version 1.0 of just:live & just:play it was possible to configure a Redundant Playout. With Version 2.0 we have added the ability to configure an optional Failover in case the Master Primary Playout Engine fails. failover: The failover control is based on the Engine's status shown in just:connect and can be used in a fully Redundant setup, where a Master Primary and a Redundant Engine is available, but also for Channels where only a Master Primary Engine is available.

Supported

...

AJA Kumo Router

• 16x4 - up to 4 Master Channels.

• 16x16 up to 8 Master Channels using Master-Redundant Engine only, up to 5 Master Channels using Master-Redundant-Failover.

• 32x32 up to 16 Master Channels using Master-Redundant Engine only, at least 10 Master Channels using Master-Redundant-Failover.

Blackmagic Design ATEM Switch

• One device per Master Channel.

• Supports Media Player as the Fallback Source.

Behavior of failover:control

...

Devices

All Devices/Presets which can be configured using the Events tab can be used in case a failover switch is executed. This includes the ability to control video routers, video switches (supports also the ATEM media player), start/stop of just:in, GPI triggers, mail notification and more.

Behavior of the failover control

In case the primary Just Out engine fails, the defined event presets will be executed and failover will switch to:

• The Redundant Engine (if available). Refer to chapter 6. Setup Variants.

• The Failover Signal (in case there is no Redundant Engine available) Refer to chapter 6. Setup Variants.

The Failover Signal can be:

• An additional signal which is added to the AJA KUMO Failover switch.failover hardware

• An additional signal which is added to the Blackmagic ATEM Failover mixer or an image which is stored in one of the ATEM's Media Player.

...

...

The Workflow parameters user interface provides a generic interface which allows the setup of the same functions independent of the hardware used for Failover. Therefore it is possible to define parameters which do not match other settings (for example defining an Email address with an invavlid mail server or configuring conflicting sources.

Setting up failover

...

control

...

...

...

1. Select the desired Channel.

2. Go to the Workflows tab.

3. Click on the Standard Workflow button.
   

   Image Removed

4. Activate the checkbox right in front of Automatic Failover and click the Ok button.
   

   Image Removed

5. The configuration window should appear.
   

   Image Removed

• Destination SDI Port: The SDI destination port you would like to use for the output signal

• Device: 

  • 0 = No device (Email only)

  • 1 = AJA Kumo

  • 2 = BMD ATEM

• Device IP: The IP address of the Failover hardware.

• Fallback Delay: Number of seconds the switch will be delayed, once the fallback signal is the only signal which is available. The value will be usually between 0 and 2 (default is 0)

• Fallback Source: The input port you would like to use for the fallback signal. The fallback signal is a third signal source which will be used in case the Master and the Redundant Engine failed.

• Mail Authenticate:

  • NO = Mailserver does not need authentication.

  • YES = Mailserver needs authentication.

• Mail Enable SSL:

  • YES = the mailserver supports SSL.

  • NO = the mailserver uses TLS or no authentication method.

• Mail Enable TLS:

  • YES = the mailserver is configured to use TLS

  • NO = the mailserver uses SSL or no authentication method.

• Mail From: The Email address which should be used as the sender.

• Mail Host: The address of the mailserver which should be used for the outgoing Email.

• Mail Password: The password which is used to log in to the the mail account.

• Mail Port: The port which is used for the SSL or TLS authentication.

• Mail Recipient: The Email address which should be used as the receiver.

• Mail User Name: The Email address of the mail account you use to send the mails from.

• Master Delay: Number of seconds the switch will be delayed, once the Master signal is available again. The value will be usually between 0 and 10 (default is 8).

• Master Source: The input port you would like to use for the Master signal.

• Send Mail:

  • NO = no Email will be sent.

  • YES = Email will be send every time a switch is executed

• Slave Delay: Number of seconds the switch will be delayed, once the Redundant signal is available again. The value will be usually between 0 and 10 (default is 0).

• Slave Source: The input port you would like to use for the Redundant signal.

Finalize the Configuration

Click on the Ok button to apply the configuration. A Failover Workflow will be added to the list of Workflows, as shown below.

...

1. Starting and Stopping a Workflow:

• Image Removed Starts a Workflow: The status light becomes green.

• Image Removed Stops a Workflow: This allows you to change the parameters of the Workflow.

2. Sprocket: Opens the Workflow parameter window.

3. Workflow Status: Shows the status of the failover:control Workflow.

1. Stop the desired Channel by deactivating the checkbox in front of it. Stopping a Channel will also stop the primary Just Out engine and therefore the final output in case no redundant engine is running.

2. Select the Channel in the Devices & Channels list.

3. Click on the Failover tab.

4. Activate the checkbox right in front of Enable Failover Control.

5. Click Add Events and add those events to the workflow, which you would like to be executed in case the Primary Engine or the Redundant Engine fails, or in case both engines are not running.

...

Workflow Status in the

...

Playout User Interface

The status of the Workflow playout is also shown in the just:live/play user interface.

Master Engine Output is sent to Destination SDI Port

...

Redundant Engine Output is sent to Destination SDI Port

...

Fallback Signal is sent to Destination SDI Port

...

just:live

...

just:play

...