- N:1 redundancy cluster (hot_cold)
- In an N:1 RC, up to 10 VUE servers can perform in the active role and a single VUE server performs as a standby server. Because an N:1 cluster uses a single standby server to backup N active servers it maintains configuration synchronization with all the N servers. The standby server does not actively process video until there is a failover where it assumes the configuration of the failed active server at that time. This is a hot_cold redundancy cluster.
- 1:1 redundancy cluster (hot_hot)
- In a 1:1 RC, a pair of VUE application servers forms a cluster, in which, one VUE server performs in the active role while the other server is in a standby role. A 1:1 is a hot_hot because there is only one active server to be backed up by the standby server, the standby can assume the active's configuration and be processing video, but not transmitting anything on its outputs.
View RC details
| Field | Description |
|---|---|
| Name | Specifies the name of the redundancy cluster. |
| Server Name | Lists the VUE servers that are part of the redundancy cluster. |
| Management IP | The static IP address of the VUE server. This IP is used by the VUE controller (VPS #2) to communicate with the VUE server. Also, typically used as the heartbeat interface between the two VUE servers in the RC. |
| Initial Role | The initial assigned role of the VUE server when the RC was created. |
| Current Role | The current role of the VUE server in the RC (Active/Standby). For Hot-Hot RCs the possible values are:
For Hot-Cold RCs the possible values are:
|
| Suspend | Indicates if redundancy is suspended for the desired redundancy cluster. Force failover continues to work; however, a standby server will not take over for a failed active server when redundancy is suspended. True – When redundancy is suspended. False – When redundancy is un-suspended. |
| Status | A summary status for each RC. OK – RC is a successful operational state. ERROR – There is one or more issues within the RC. Details on RC Errors or alarms can be viewed on the VUE status screen or on the Server tab. UNKNOWN – VTM is unable to determine the status of the RC from the VUE. For example, VUE might be offline, loss of network communication, and so on. NOTE: In VUE versions
2.3.6-2 and prior, the RC summary status on VTM will always be
reported as UNKNOWN. This is because in
these versions the RC summary status is derived on VUE and
reported in the VUE Element Manager (UI application). When VTM
interfaces with VUE version 2.3.7-x and later, the RC summary
status is obtained from VUE and reported as such in VTM. |
| Config Sync | Indicates the status of the RC with respect to the VUE system. It is either Synchronized or Unsynchronized. |