Combination: Statmux Node Redundancy with Output Listening - 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.

Combination: Statmux Node Redundancy with Output Listening

This section applies only to deployments that include at least one AWS Elemental Statmux node separate from the nodes.

You can combine Statmux node redundancy with output listening: Two different MPTS outputs (on different AWS Elemental Statmux nodes) create the same MPTS output. However, only one of them ever actually creates and delivers the output. One of the MPTS outputs is set up as the primary MPTS while the other is set up as the secondary.

While the primary statmux is successfully creating output, the secondary statmux is inactive. If Conductor detects that the primary statmux is not creating output, the secondary statmux starts creating it.

Typically, this configuration is used when the downstream system cannot manage input redundancy (where the content is “input” from the point of view of the downstream system), but a highly available input is required.

This setup combines node redundancy with network failure redundancy around the delivery of MPTS output.

               Image file mpts-combo-statmux-output-listening.png

In this scenario, MPTS1 is simultaneously delivering content to the first switch via G4 and the identical content to the second switch via G5. If one of the switches fails, the content is still being delivered via the other switch.

Meanwhile, MPTS2 is listening for traffic on both G4 and G5. If traffic is detected on neither (because the MPTS1 node fails), then MPTS2 begins delivering content, also over G4 and G5. The downstream system retrieves G4 at the first switch. If the first switch fails, the downstream system retrieves either G5 at the second switch.


  • Configure Statmux redundancy as described in the procedure in Statmux Node Redundancy. Configure the two MPTS outputs so that their destination 1 fields point to the same IP address and their destination 2 fields point to the same IP address.

  • Do not configure MPTS output redundancy.

  • Configure output listening (below).

To configure output listening

  1. In the Redundancy tab of the Create a New MPTS dialog, for the primary MPTS output, leave the Output Listening Interval field unchecked.

  2. On the secondary MPTS, check this field and specify an interval.

                     Image file mpts-configure-output-listening.png

Output listening works as follows: When the primary MPTS is started, it starts muxing and delivering output to the MPTS destination. In other words, it behaves normally.

When the secondary MPTS output is started, the MPTS sees that its Output Listening field is checked and therefore does not mux and deliver. Instead, it watches its final destination or destinations (keep in mind that the destinations of both MPTS outputs are identical). If the secondary MPTS output does not detect traffic at either destination for the specified interval, it assumes that the primary MPTS output has failed and it starts muxing and delivering.

If the secondary MPTS re-detects traffic from the primary, it stops muxing.