[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sr-users
Subject:    Re: [SR-Users] Load balance on HA scenario
From:       Yufei Tao <yufei.tao () gmail ! com>
Date:       2020-10-22 9:43:53
Message-ID: CAJwP0iQGJ4eA562=CVVM+cr9bFsTSxeTzpqdXQ877k4HwBxt1w () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hi Duarte,

I'm not sure if your situation is more complicated than mine. I have two
dispatcher nodes in the HA setup, with real IPs say IPa, IPb. They share a
floating/virtual IP, let's call it VIP.

Both nodes listen to the VIP (not its real IP), and use the VIP as the
dispatcher's socket. In this case the master node which has the VIP can
always send OPTIONS pings fine.

My problem was with the backup node, which doesn't have the VIP so fails to
send OPTIONS pings. Joel Serrano gave a good suggestion: both nodes start
up with polling disabled, and only when a node turns master it enables the
polling. This has solved my problem.

Cheers,
Yufei

[Attachment #5 (text/html)]

<div dir="ltr">Hi Duarte,<div><br></div><div>I&#39;m not sure if your situation is \
more complicated than mine. I have two dispatcher nodes in the HA setup, with real \
IPs say IPa, IPb. They share a floating/virtual IP, let&#39;s call it \
VIP.</div><div><br></div><div>Both nodes listen to the VIP (not its real IP), and use \
the VIP as the dispatcher&#39;s socket. In this case the master node which has the \
VIP can always send OPTIONS pings fine.  </div><div><br></div><div>My problem was \
with the backup node, which doesn&#39;t have the VIP so fails to send OPTIONS pings. \
Joel Serrano gave a good suggestion: both nodes start up with polling disabled, and \
only when a node turns master it enables the polling. This has solved my \
problem.</div><div><br></div><div>Cheers,</div><div>Yufei</div></div>



_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


[prev in list] [next in list] [prev in thread] [next in thread]