Data Exchange Redundancy - AWS Elemental Conductor Live 3

This is version 3.17 of the AWS Elemental Conductor Live 3 documentation. This is the latest version. For prior versions, see the Previous Versions section of AWS Elemental Conductor Live 3 Documentation.

Data Exchange Redundancy

  • Type of redundancy: Protects against network failure.

  • Where: Network failure around the communications about complexity/allocation and delivery of the channel.

Without Redundancy

The encoder sends complexity information to an IP address and the statmux component retrieves that information from that IP address. The statmux component sends allocation information to an IP address and the channel retrieves that information from the IP address. Once the encoder has created the channel, it delivers the content to an IP address. The statmux component retrieves the content from that IP address.


               Image file mpts-data-exchange-no-redundancy.png

With Redundancy

You can set up two sets of these three IP addresses. Communications occur to all addresses simultaneously. If a network failure causes the primary addresses to be unavailable , the statmux falls back to the other addresses.


               Image file mpts-data-exchange-redundancy.png

Procedure

You set up for Data Exchange Redundancy by specifying both a primary and a secondary set of IP addresses. You enter this information on both the SPTS program (the event) and the MPTS.

Create a profile on the AWS Elemental Conductor Live 3 web interface. In the MPTS membership section in the Output Groups, complete both the primary and secondary fields. See Creating a Profile from Scratch.


               Image file mpts-data-exchange-redundancy-procedure.png

The channel handles communications about complexity and delivery over these two sets of destinations – the primary and the secondary. When you start each channel, AWS Elemental Conductor Live 3 includes these addresses in the information it sends to the node.

When you start the MPTS, AWS Elemental Conductor Live 3 instructs the muxer (either the AWS Elemental Statmux node or the node) to also handle communications over the same two sets of destinations.