Statmux Node 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.

Statmux Node Redundancy

This section applies only to deployments where the nodes act as encoders and a separate AWS Elemental Statmux node acts as a muxer. It does not apply if the node is both the encoder and the muxer.

  • Type of redundancy: Statmux node failure.

  • Where: Node failure that would result in non-creation of the MPTS output.

Without Redundancy

The statmux combines all the channels into one MPTS output. In this example, three different SPTS channels are providing video content to the MPTS.

               Image file mpts-statmux-node-no-redundancy.png

With Redundancy

You can create two identical MPTS outputs on two different AWS Elemental Statmux nodes. Both MPTS outputs retrieve complexity, send allocation, and retrieve content from all IP addresses that have been set up in the encoder. If one MPTS output fails (because the Statmux node fails), the other MPTS output (on the other Statmux node) still functions.

               Image file mpts-statmux-node-redundancy.png


This section applies only deployments that include at least one AWS Elemental Statmux node separate from the nodes. To attain Statmux node redundancy, you create two MPTS outputs (each on a different Statmux node) and set the two MPTS outputs with nearly identical information.

In AWS Elemental Conductor Live 3, create two MPTS outputs. On the Create a New MPTS screen:

  • For each MPTS output, specify a different AWS Elemental Statmux node in the Node field.

  • For the primary MPTS output, go to the Redundancy tab and set Allocation Message Priority to “Primary.”

  • On the secondary MPTS output, go to the Redundancy tab and set Allocation Message Priority to “Secondary.”

                     Image file mpts-statmux-node-redundancy-procedure.png

    The allocation messages that the two outputs send are tagged differently – one with a “p”, the other with an “s”. In this way, the that receives the messages does not get confused over receiving the same message twice – each message name is slightly different.

  • Add the exact same channels to each MPTS.

When you start each MPTS, it retrieves content from the same channel. Both MPTS outputs contain the same channel so both are retrieving from the output location of that channel.