← Back to Articles
Modify an existing VUE Redundancy Cluster
Last Updated: July 07, 2026

VUE Redundancy Cluster (RC) can be modified on VTM by editing an existing VUE system that is part of an RC. This can be accessed from the RC-Server tab.

  1. Select Elements > VUE in the navigation bar.
  2. Select a VUE system from the list you would like to add to the RC.
  3. Select the RC-Server tab.
    The RC table is displayed. There are two types displayed:
    Hot-Hot
    1:1 VUE Redundancy Clusters always contain 1 Active Server and 1 Standby Server.
    Hot-Cold
    N:1 VUE Redundancy Clusters contain up to 10 Active Servers and 1 Standby Server.
    RC-Server screen with Hot:Cold Redundancy Cluster example
    RC Server screen with Hot:Cold Redundancy Cluster

    If this VUE is part of an RC already, you will see the other associated VUEs, if any, which are also part of the RC in one of the two RC tables.

Remove VUEs from the RC:
  1. Select the VUE to be removed.
  2. Click the (Menu) button and select Delete.
    The following restrictions apply to removal of a VUE from an RC:
    • You cannot delete an Initially Active server if it is the last one in the cluster.

      If there is a single Initially Active server left in the RC, the RC can be deleted to remove the configuration entirely.

    • You cannot delete an Initial Standby server if it is currently serving in an Active role.

      If you wish to delete the Initial Standby server in an Active role, you must suspend the RC and then perform a force failover to the Initially Active server first and then you can delete the Initial Standby server.

Add additional VUEs to the RC:
  1. Click the (Menu) button which corresponds to with the desired RC type.

    The menu options appear.

  2. Click Add.
    Select Add from the RC cluster table menu

    The Add Redundancy Cluster window is displayed.

    Add Redundancy Cluster screen
    Add Redundancy Cluster window
  3. Complete the following:
    1. Enter a unique Name to be assigned to the RC for identification.
      Enter a name for the Redundancy Cluster
    1. Enter the Ingress Stream Rate and Ingres Threshold Limit % (Hot:Hot only)
      FieldDescription
      Ingress Stream Rate

      (In Kilo bits per second)

      ("Hot Hot" only)

      This is a user specified input bit rate threshold that will generate an alarm should the aggregate stream rate of all input transport streams from all input interfaces on the VUE server drop below this level. This alarm can be independently generate by either the active or standby server. The alarm generating condition does not cause a failover.

      The default value is zero, which disables the alarm notification.

      Ingres Threshold Limit %

      ("Hot Hot" only)

      The allowed rate difference, expressed as a percentage, between the aggregate input stream rate of the active server in comparison to the standby server. If the aggregate rate of data reception on the active server falls below by more than this specified percentage, then an automatic failover occurs.

      For example, if you specify 75% for the Ingress Threshold Limit % and the current aggregate input source stream rate of the standby server is 1000 Kbps, an automatic failover to the standby server occurs when the active server's aggregate input source stream rate drops to 749 Kbps (or 74.9% of the standby server's stream rate).

    2. Select the Active server(s) by clicking on the Server field.

      The Select Candidate Server screen appears. It lists the selectable servers known to the VTM. The available servers for the role selected appear in the top group, Candidate Servers. In a Hot:Cold RC, any Candidate Servers already added to the RC being created do not appear in the Candidate Server list. Other servers which are not possible for this role appear in the bottom group, Non-Candidate Servers.

      Select the desired server from the Candidate Servers.

      Select a Candidate Server
    3. Click on a Heartbeat Interface for the Initial Active server to select a possible interface.
      Important: CommScope recommend you select the static management IP of both active and standby as the main HB interface. It is also strongly recommended that stationary (static) IPs are used for the heartbeat interface. (Typically this would be the management IP address of the VUE server used between the VUE server and the VUE controller for internal communication.) Static IP addresses are recommended over VIPs because the actual IP addresses that VIPs resolve to can change. VIPs however can be used, but their role must be defined as ‘heartbeat'.
      FieldDescription
      Heartbeat Interface 1

      Primary IP interface to exchange heartbeat signal. Signal exchange is between active and standby server.

      Heartbeat Interface 2Secondary interface IP to exchange heartbeat signals.
      Important: CommScope recommends that both HBs be configured on separate interfaces.
Modify attributes of a VUE in the RC:
  1. If the RC is not suspended, click Suspend.

    In order to modify the attributes of any VUE in the RC, the entire RC must be suspended.

    The following fields can now be modified:
    • Initial Active Server
    • Initial Standby Server
    • Heartbeat Interface 1 for all servers
    • Heartbeat Interface 2 for all servers
  2. Click on the desired field(s) and modify the value as needed.
  3. Click Update to confirm the changes.
  4. Click Resume RC to unsuspend the RC with the new configuration.