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 and should not be configured.
The SBC Core supports configuring a Load Balancing Service (LBS) to distribute media requests among M-SBC instances in a cluster.
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 applies only to M-SBC (in a SWe Cloud D-SBC configuration).
% set system loadBalancingService groupName <group_name> privateIpInterfaceGroupName <name>
Load Balancing Service Parameters (M-SBC)
Parameter | Description |
---|---|
groupName | <name> – Domain name of the load balancing group. (1-63 characters) |
privateIpInterfaceGroupName | <name> – Use this parameter to specify the name of the private IP Interface Group the M-SBC/T-SBC uses to communicate to the Media Resource Function (MRF) for this load balancing group. |
To configure the load balancing service on M-SBC:
set system loadBalancingService groupName lbg1.xyz.com privateIpInterfaceGroupName LIF1 commit
This configuration applies to a feature that is no longer supported and the configuration is no longer required.
% set system loadBalancingService groupName <group_name> inviteRetargetMode <disable | redirect> registerRetargetMode <disable | redirect>