An N:1 redundancy cluster can contain up to 11 VUE application servers, where up to 10 VUE servers operate in active role and a single VUE server operates in the standby role. When configuring a redundancy cluster, you must assign the initial role of each server in a cluster. For more information about high availability in a redundancy cluster, see High availability with redundancy.
During the initial configuration of a Redundancy Cluster (RC), you must configure initial active servers first and then add a standby server. Once the redundancy cluster has been defined, the standby VUE application server can become active in the event when one of the servers fails.
When creating a redundancy cluster, the initial active server can have existing transport stream (TS) and mappings along with ACCP and SDV configuration. The initial standby cannot have any pre-configured transport stream or mappings or ACCP and SDV configuration. Additionally, all interfaces used by the initial active must be VIPs except for PTP. Both active and standby servers PTP IP should be static. The HB can be either static or VIPs. The following is a list of VIPs that must be used when creating a redundancy cluster:
- All ingress/egress IPs
- SDV control plane IP (interface that communicates with ERM)
- SDV data plane IPs (ingress IPs)
- ACCP GCP IP address
You can configure a single VUE server or a redundancy cluster by importing saved configuration data using a JSON file, or by manually entering data. See: