---
title: Dual NIC PUSH Redundancy (Warm Redundancy)
slug: product-features/dual-nic-push-redundancy-warm-redundancy
docTags: 
createdAt: 2024-12-08T19:00:05.225Z
---

::Image[]{src="https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/EePJ9tbzYKkJz9--H8YXM_image.png" size="74" width="887" height="134" position="center" showCaption="false"}

A single source can be configured to PUSH two redundant stream to a single target using two NICs. Provided that the streams from both NICs include the same Stream ID, contention for the input is decided on a first-come first-served basis. If the primary NIC connection is lost, the target Input will automatically accept a new stream (coming from the secondary NIC). As a result, this topology provides source-side NIC redundancy with automated fail-over to a second identical stream. 

## Source Configuration

The following procedure describes how to configure a Zixi Feeder to push a stream through two NICs to a target hosts in a warm redundancy configuration. The procedure does not cover instructions on how to configure the Input into the Zixi Feeder. 

**To configure the primary source node (e.g. Zixi Feeder):**

1. On the **Outputs** page of Zixi Feeder, click the **New Output** button, located in the upper- right end corner of the screen.
2. In the **Name** field, type a new name for the output. 
3. In the **Type** field, select **Push to Broadcaster**.
4. In the **Input Name** field, select the relevant input stream.
5. In the **Program** field, if you have created a filter for the stream, select the relevant program.
6. In the **Stream ID** field, enter a stream ID (alphanumeric). The same Stream ID will be also configured in the target node (Push Input).
7. Optional - in the **Password** field, specify a string to be used at the destination to authenticate that the pushing Broadcaster is allowed to push this stream.
8. In the **Max Bitrate** field, specify the maximum bitrate of the stream. Default: 8000. This is used for internal memory allocation and will not affect the transmitted bitrate. Recommended: double the bitrate of the stream.
9. In the **Max Latency** field, specify the buffer size that Zixi Broadcaster will keep for error correction. For example, 6000 milliseconds would ensure that the stream is protected for six seconds of errors in the network. Default: 6000.
10. Under Links, in the **Host** field, enter the host name or IP of the primary target.
11. In the **Port** field, specify the destination port to listen on for the Push stream (default: 2088).
12. In the **IP** field, select from the drop-down menu, the IP address of the **Primary NIC** (Network Interface Card) in the Source through which the stream will be pushed.
13. Click the** '+'** button to create a secondary link.
14. In the **Host** field, enter the host name or IP of the primary target.
15. In the **Port** field, specify the destination port to listen on for the Push stream (default: 2088).
16. In the **IP** field, select from the drop-down menu, the IP address of the **Secondary NIC** (Network Interface Card) in the Source through which the stream will be pushed.
17. Click **OK**.
    The output is added to the Outputs list and includes a primary and a secondary link. 

## Target Configuration

The following procedures describe how to configure the target Zixi Broadcaster in a warm redundancy configuration. The target is configured with a single input. If this input is unavailable the secondary input will be received. The input must use the same Stream ID that was used to configure the primary and secondary source NICs. 

**To configure the target node (e.g. Zixi Broadcaster):**

1. Click the **Inputs **tab at the top of the secondary Zixi Broadcaster administrative screen
2. Click **New Input **on the upper right hand side of the screen.
3. In the **Stream ID** field, enter the same “Stream ID” as the source outputs. 
4. Select the **Push **option.
5. Configure additional parameters as required. 
6. Click **OK**.

## Cost Considerations

This topology duplicates the source side Zixi node software and hardware components. It does not require doubling the up-link bandwidth, as the backup connection stream is only active in the event that the primary stream fails.

## Latency Considerations

For detailed recovery time details, please contact your Zixi representative.