Introduction to Load Balancing¶
Cisco Unified Communications Manager (Unified CM) groups provide both call-processing redundancy and distributed call processing. You can distribute devices, device pools, and Unified CMs among the groups to improve redundancy and load balancing in your system.
A Cisco Unified Communications Manager Group specifies a prioritized list of up to three Unified CMs. The first Unified CM in the list serves as the primary Unified CM for that group, and the other members of the group serve as secondary and tertiary (backup) Unified CMs.
Each device pool has one Unified CM Group that is assigned to it. For example, Group 1 points to Device Pool 1, Group 2 points to Device Pool 2, and Group 3 points to Device Pool 3. When a device registers, it attempts to connect to the primary (first) Unified CM in the group that is assigned to its device pool. If the primary Unified CM is not available, the device tries to connect to the next Unified CM that is listed in the group, and so on.
Load balancing is a manual process on Unified CM requiring you to perform the following tasks:
Add new, custom Unified CM groups and device pools.
Synchronize the groups and device pools into VOSS Automate.
Choose the appropriate group and device pool in the Subscriber or Phone configuration for the site. To create more than one configuration for a site, create at least two Unified CM groups, then associate a device pool to the appropriate Unified CM group.
To determine if load balancing is required for your network, you can check the current device traffic load in Unified CM using the System > Device Pool menu path. When you click on the device configuration information for a specific device pool, the Device Pool Information field lists the number of members in the Device Pool. Compare different device pools to see if the members are evenly divided between pools.
To perform load balancing, see “Load Balancing Using Site Default Device Pool”.