[OpenSIPS-Users] need some help using opensips 3.0 cluster module .

[Giovanni Maruzzelli]

Sasmita, how possibly you can do that?
How you then associate a machine with an id?
Would you create a new database field for the MAC of the machine?

-giovanni




On Mon, Sep 2, 2019 at 8:54 AM Sasmita Panda <spanda at 3clogic.com> wrote:

> Hi All ,
>
> In clustering , every opensips node has its own node id .
>
> modparam("clusterer", "my_node_id", 2)
>
> I want to read this value from from the DB . Is this possible or not ? If
> yes ,  how will I do this ?
>
> Please do help me .
>
>
>
> *Thanks & Regards*
> *Sasmita Panda*
> *Senior Network Testing and Software Engineer*
> *3CLogic , ph:07827611765*
>
>
> On Thu, Aug 8, 2019 at 12:44 PM Sasmita Panda <spanda at 3clogic.com> wrote:
>
>> Thank you so much for the explanation  .
>>
>>
>> *Thanks & Regards*
>> *Sasmita Panda*
>> *Senior Network Testing and Software Engineer*
>> *3CLogic , ph:07827611765*
>>
>>
>> On Wed, Aug 7, 2019 at 6:46 PM Liviu Chircu <liviu at opensips.org> wrote:
>>
>>> Sasmita,
>>>
>>> Dialog replication is not meant to work on such a cluster. Since dialogs
>>> retain more
>>> state than registration, they are more sensitive to the IP of the
>>> current node.
>>>
>>> If you want high-availability for dialogs, the basic unit of deployment
>>> shifts from
>>> 1 server to 2 servers (an active/backup pair).  And in order to have the
>>> same IP on
>>> both servers, you must use VRRP-capable software, such as keepalived.
>>>
>>> Deploy as many pairs as needed in each location according to your
>>> traffic volume, and
>>> make sure to give each pair its own Virtual (highly available) IP that
>>> can automatically
>>> move from the active node to the backup in case the former one catches
>>> fire.
>>>
>>> PS: this information should be included in the dialog replication blog
>>> post, so make
>>> sure to read it closely.
>>>
>>> Liviu
>>>
>>> On 8/6/19 1:25 AM, Sasmita Panda wrote:
>>> > | id | cluster_id | node_id | url                  | state |
>>> > no_ping_retries | priority | sip_addr    | flags | description |
>>> > |  1 |          1 |       1 | bin:192.168.0.x:5555 |     1 |
>>> > 3 |       50 | 192.168.0.x | seed  | Node A      |
>>> > |  2 |          1 |       2 | bin:192.168.0.y:5555 |     1 |
>>> > 3 |       50 | 192.168.0.y | seed  | Node B      |
>>> > |  3 |          1 |       3 | bin:192.168.0.z:5555 |     1 |
>>> > 3 |       50 | 192.168.0.z | seed  | Node C
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>


-- 
Sincerely,

Giovanni Maruzzelli
OpenTelecom.IT
cell: +39 347 266 56 18
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20190902/0e08a7cf/attachment.html>