In this section:
Beginning in release 8.0, Load Balancing Service configuration applies only to media SBC (M-SBC) clusters in distributed SBC SWe Cloud deployments. The M-SBC load balancing distributes media requests among nodes. Load balancing of REGISTER or INVITE requests through retargeting is no longer supported.
The SBC Core supports configuring a Load Balancing Service (LBS) to distribute INVITE and REGISTER details between SBC platforms or D-SBC instances, as applicable.
To disable Load Balancing for a particular zone, refer to Zone - Retarget Support - CLI.
Use the 'show table/system loadBalancingService
...' command to view Load Balancing Service configuration status details. Refer to Show Table System for details.
You must configure Cluster Admin for intra-cluster node communication before configuring a D-SBC signaling port, Load balancing service and DNS group parameters.
Refer to Cluster Admin - CLI for configuration details.
The following Load Balancing Service CLI syntax applies to the following platforms:
% set system loadBalancingService groupName <group_name> inviteRetargetMode <disable | redirect> registerRetargetMode <disable | redirect>
The following Load Balancing Service CLI applies to M-SBC (in a SWe Cloud D-SBC configuration).
% set system loadBalancingService groupName <group_name> privateIpInterfaceGroupName <name>
The following Load Balancing Service parameters apply to the following platforms:
See Load Balancing Service Parameters (M-SBC) table below for M-SBC parameter descriptions.
To configure the load balancing service on S-SBC:
set system loadBalancingService groupName lbg1.xyz.com inviteRetargetMode redirect registerRetargetMode redirect commit
To configure the load balancing service on M-SBC:
set system loadBalancingService groupName lbg1.xyz.com privateIpInterfaceGroupName LIF1 commit