Using the lb_status command with two params, the ID of the destination and desired status (0 if you want to disable), this does seem to disable probing though so the destination will stay disabled until you manually set status back to 1 https://opensips.org/docs/modules/3.2.x/load_balancer.html#mi_lb_status ________________________________ From: Users <[email protected]> on behalf of Johan De Clercq <[email protected]> Sent: Tuesday, April 9, 2024 4:01 PM To: OpenSIPS users mailling list <[email protected]> Subject: Re: [OpenSIPS-Users] Load Balancer add destination as probing status
CAUTION: EXTERNAL Can you tell me how to disable a load balancer destination via mi ? On Tue, 9 Apr 2024, 20:02 John Sliney, <[email protected]<mailto:[email protected]>> wrote: Is there currently a way to add a destination to the load_balancer set with a status of disabled but with probing enabled, like the dispatcher table 'state' column allows? I have an osips working as a SIP ingress/egress for Kubernetes traffic and as Asterisk Pods are created they are added to the load_balancer table as destinations, but OpenSIPS will route traffic to them before they're fully ready. I've attempted to automatically mark them as disabled with the mi lb_status command and let the probe enable them, but disabling via mi seems to disable probing as well, so they're never actually enabled. _______________________________________________ Users mailing list [email protected]<mailto:[email protected]> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
