Beginning in release 8.0, Load Balancing Service configuration applies only to media SBC (M-SBC) clusters in distributed SBC SWe 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.
For SBC Core in virtual environments and M-SBC in particular, when an interface link and the associated interface is up but not the relevant IP addresses, do not execute commands such as "
ip link down" or "
ifconfig". When switchover happens, such command executions can often result in an unequal load distribution among various nodes. If you suspect an unequal load distribution, verify it by executing the command "
show table global callCountStatus".
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 distributed SBC SWe deployment).
To configure the load balancing service on M-SBC:
This configuration applies to a feature that is no longer supported and the configuration is no longer required.