← Back to Articles
Manually add a redundancy cluster
Last Updated: July 07, 2026

If you want to manually enter the details to configure a VUE server, continue with the procedure.

  1. Login to Element Manager, https://<VPS #2_IP_address>:5557.
  2. Click the RC-SERVER button on the left navigation pane. The Redundancy Clusters/Servers screen is displayed.
  3. Click the Add icon button to add the VUE server or RC. The Add Redundancy Cluster dialog displays.
    Add N:1 redundancy cluster
  4. Enter the necessary details:
    ParameterDescription
    RC TypeChoose the type of RC you want to create.

    hot_hot – Is a 1:1 cluster which consists of only one active server and one standby server.

    hot_cold – Is an N:1 cluster which consists up to ten active servers and one active server.

    RC NameEnter a unique descriptive name.
    Ingress Stream Rate (Kbps)

    (Range 0 – 10000000 Kbps)

    		For alarm notification only (not used for failover determination). Set this to the desired input rate to be notified if the rate falls below this value.
    NOTE: This is applicable only to 1:1 redundancy cluster.
    Ingress Threshold Limit%

    (Range: 0 – 100)

    Indicates the threshold value used to compare the total ingress bandwidth between the active and standby servers. If the active falls below the defined rate of the standby server, the system fails over to the standby server.
    NOTE: Only multicast inputs are received by both active and standby. This includes both manually routed broadcast programs and SDV programs (VOD inputs are not received on the standby). Therefore, when setting a comparison rate, consider the types of inputs being received.
    0 disables comparison and 100 indicates identical ingress rates.
    NOTE: This is applicable only to 1:1 redundancy cluster.
    Suspend Redundancy ClusterCheck this box to suspend automatic failover. Suspend must be selected to modify any cluster parameters. Suspension of a cluster is also recommended when performing a software upgrade. For more information, see Enable or disable suspension on redundancy cluster in VUE 2.5 User Guide.
    Auto FailbackAvailable only when creating N:1 (hot_cold) redundancy cluster. Selecting Auto-Failback ensures that once the Initial Active Server recovers from a failure, the system automatically transitions back from the Standby Server to the Initial Active Server.
    Auto Failback Delay

    (Range: 1-600 seconds)

    		Available only when creating N:1 (hot_cold) redundancy cluster. AutoFailback delay parameter enables you to control the time period to wait before auto-failing back occurs once the Initial Active server has recovered. The AutoFailback Delay can be configured on each RC. You can configure the time period in 1-second increments. By default, the delay is set to 60 seconds.
    Initial Active ServerChoose a VUE server from the drop-down list. Only servers that have not been configured as active or standby servers are available in the drop-down list.

    To create an N:1 RC continue to add the active servers based on your requirements. You can configure up to 10 initial active servers.

    Click Add to continue adding multiple active servers. The added active servers are listed below in the Configured Active and Standby Servers section.

    Heartbeat Interface 1Primary IP interface to exchange heartbeat signal. Signal exchange is between active and standby server. It is recommended to select the static management IP of both active and standby as the main HB interface.

    Click Add to continue to add multiple active servers and their associated HB interfaces. The added active servers and HB interfaces are listed below in the Configured Active and Standby Servers section.

    Heartbeat Interface 2Secondary interface IP to exchange heartbeat signals. It is recommended to have both HBs configured on separate interfaces.
    Suspend Active ServerThough this field is available, it is not functional at this time.
    AddAvailable only when creating N:1 (hot_cold) redundancy cluster.

    Click Add to add the initial standby server and its HB interfaces to the list below in the Configured Active and Standby Servers section.

    ClearAvailable only when you add initial active servers to configure a hot_cold cluster in the Configured Active and Standby Servers section.
Configure standby server
  1. Configure standby server that will be part of the RC.
    NOTE: Ensure that the standby sever has equal or more resources (pipes, no of interfaces, speed of interfaces, names of the interfaces) than the active servers before you configure the cluster.
    ParameterDescription
    Initial Standby ServerChoose a VUE server from the drop-down list.

    The Initial standby server must be compatible with the initial active servers. The initial standby server must have the same or greater number of max pipes (based on memory and cores), and same number of types of interfaces as the initial active server. For interfaces, the standby server must have same interfaces and each interface must have the same or greater Max Speed setting.

    Heartbeat Interface 1Primary IP interface to exchange heartbeat signal. Signal exchange is between active and standby server. It is recommended to select the static management IP of both active and standby as the main HB interface.
    Heartbeat Interface 2Secondary interface IP to exchange heartbeat signals. It is recommended to have both HBs configured on separate interfaces.
    Suspend Standby ServerThough this field is available, it is not functional at this time.
    AddAvailable only when creating N:1 (hot_cold) redundancy cluster.

    Click Add to add the standby server and its associated HB interfaces.

    ClearAvailable only when you add initial standby servers to configure a hot_cold cluster in the Configured Active and Standby Servers section.

    If you assign a standby server with less resources than the active server, then there will be an error generated stating the standby server does not have enough resources. You can clear the standby server and update the requirements accordingly.

  2. Click Submit to confirm and close the Add Redundancy Cluster dialog. or Cancel to exit the operation.
  3. To view the details of any redundancy cluster, click the ellipsis menu More options on the far right of the desired cluster.
    The ellipsis menu for each cluster listed enables you to modify or delete the cluster configuration. For more information, see Add, edit, or delete a standby server.
    NOTE: Only two modification operations are allowed:

    No other modification operation is allowed.

    For detailed information on specific VUE server, see Monitor VUE servers/RCs.

    If configuring an RC and no Standby server is available, perform the following steps to know why a server is not compatible with the initial active server:
    1. Check for the max pipes setting. An initial standby server must have same or greater number of max pipes than initial active server.
    2. Check for the Ethernet interfaces. Typically, initial active will have eth0, eth1, eth2, and eth3 (maybe a bond0 interface also). Make sure the server you want to choose as standby has these same exact interfaces. You can use the I/F Detail option of each server to see interfaces of each server. For more information, see Monitor IP address interface in a VUE server.
    3. If max pipes and interface names are compatible, next check for each interface the max speed listed. Each corresponding interface on the server you want as the initial standby server must have the same max speed or greater as compared to initial active server.