CommScope's COVID-19 Customer & Partner Hub Visit
- Active-Passive – Where a secondary controller service simply monitors an active controller and is only activated upon failure of the primary controller. With this architecture, the value of the overall system is diluted, as the secondary controller is left idle for long periods of time. This design is also less responsive during recovery from controller failures.
- Active-Active – Where a number of controller services act collaboratively to sustain network reliability even upon failure of any one of the controller services. The TCO of this option is much lower because all units are active and recoveries are virtually seamless.
- Because there are multiple controllers within the cluster, a “single-pane-of-glass” interface simplifies network management.
- Geographic redundancy can isolate localized controller failure scenarios and increase the overall reliability.
- Support of both appliance and virtual deployment options have a direct impact on CAPEX and overall network capacities when you select a cluster solution.
- “Cluster balancing” is a smart way to optimize utilization of each cluster element.
- Client license management across a cluster is generally flexible and not bound to any single controller.