VUE Redundancy Cluster (RC) can be created on VTM by editing existing VUE systems and through 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.

   

4. Click the (Menu) button which corresponds to with the desired RC type.

   The menu options appear.

5. Click Add.

   

   The Add Redundancy Cluster window is displayed.

   

6. Complete the following:
   1. Enter a unique Name to be assigned to the RC for identification.

      

   1. Enter the Ingress Stream Rate and Ingres Threshold Limit %(Hot:Hot Only).
      Important: These fields are only application to Hot:Hot RCs. Since they do not apply to Hot:Cold RCs, these fields do not appear when creating or modifying a Hot:Hot RC.

      Field	Description
      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.

      

   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 Virtual IPs (VIP) because the interfaces that a VIP is routed to can change. VIPs however can be used, but their role must be defined as ‘heartbeat'.

      Field	Description
      Heartbeat Interface 1	Primary IP interface to exchange heartbeat signal. Signal exchange is between active and standby server.
      Heartbeat Interface 2	Secondary interface IP to exchange heartbeat signals. Important: CommScope recommends that both HBs be configured on separate interfaces.

   4. If necessary, click the (Menu) button and select Add to add an additional Initial Active server entry. (Hot:Cold Only).
      The number of allowed active servers is determined by the RC Type:

      • Hot Hot: This is a 1:1 redundancy configuration and allows one active server and one standby server.
      • Hot Cold: This is an N:1 redundancy configuration and allows one to ten active servers and one standby server.

      

      Repeat this step for each additional Active Server desired for this RC.

      A new Active Server entry will be added. Repeat step 6.b and 6.c to enter the details for the new Active Server(s).

7. Click on a Heartbeat Interface for the Standby 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 Virtual IPs (VIP) because the interfaces that a VIP is routed to can change. VIPs however can be used, but their role must be defined as ‘heartbeat'.

   Field	Description
   Heartbeat Interface 2	Secondary interface IP to exchange heartbeat signals. Important: CommScope recommends that both HBs be configured on separate interfaces.
   Heartbeat Interface 1	Primary IP interface to exchange heartbeat signal. Signal exchange is between active and standby server.

8. Select the Standby server by clicking on the Initial Standby Server field.

   The Select Candidate Server screen appears. It lists all the possible 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.

   

9. Click Save.