ProSBC Applications
Page 1 of 1
ProSBC Applications
Hi,
We have a problem with our customer ProSBC. We have ProSBC in HA. Primary and secondary server. Yesterday apps from primary were in active mode and apps from secondary in standby mode. But at 5:00 there was a connectivity problem between them and apps from Secondary jump into active mode. When connectivity between primary and secondary was OK, then apps on the secondary server still persist in active mode. But we need apps from the primary server in active mode (switch to standby only if servers do not see each other) How to configure this? Because now on primary server apps- tbsip, tbucwriter, toolpack_engine and toolpack_sys_mgr are in standby mode and that is what we don't want. When connectivity is OK apps on primary servers must be in active mode.
FYI, we are running on Version: 3.1.10.
I hope you understand me
Thanks,
We have a problem with our customer ProSBC. We have ProSBC in HA. Primary and secondary server. Yesterday apps from primary were in active mode and apps from secondary in standby mode. But at 5:00 there was a connectivity problem between them and apps from Secondary jump into active mode. When connectivity between primary and secondary was OK, then apps on the secondary server still persist in active mode. But we need apps from the primary server in active mode (switch to standby only if servers do not see each other) How to configure this? Because now on primary server apps- tbsip, tbucwriter, toolpack_engine and toolpack_sys_mgr are in standby mode and that is what we don't want. When connectivity is OK apps on primary servers must be in active mode.
FYI, we are running on Version: 3.1.10.
I hope you understand me
Thanks,
Last edited by ahsanul.moyeen on Thu Apr 01, 2021 9:16 am; edited 1 time in total
Guest- Guest
Re: ProSBC Applications
Hi,
The switchover between the primary and the secondary is automatic and it doesn’t matter the apps are active on which ProSBC.
If you really want to force everything back active on the primary, you can ssh to the secondary and restart toolpack service:
- SSH to the host
- tbtoolpack stop
- tbtoolpack start
On another hand, rel3.1.10 is a very old version and I suggest you upgrade to our latest version rel3.1.117.
It is available here:
https://tbsoftware.s3.ca-central-1.amazonaws.com/3.1.117/TBToolPack-3.1.117.3-Linux-centos7-x86_64-Install
Instruction to upgrade:
https://docs.telcobridges.com/tbwiki/Toolpack:Tsbc_System_Settings_3.1#Package_Upgrade
Best Regards,
The switchover between the primary and the secondary is automatic and it doesn’t matter the apps are active on which ProSBC.
If you really want to force everything back active on the primary, you can ssh to the secondary and restart toolpack service:
- SSH to the host
- tbtoolpack stop
- tbtoolpack start
On another hand, rel3.1.10 is a very old version and I suggest you upgrade to our latest version rel3.1.117.
It is available here:
https://tbsoftware.s3.ca-central-1.amazonaws.com/3.1.117/TBToolPack-3.1.117.3-Linux-centos7-x86_64-Install
Instruction to upgrade:
https://docs.telcobridges.com/tbwiki/Toolpack:Tsbc_System_Settings_3.1#Package_Upgrade
Best Regards,
Guest- Guest
Similar topics
» ClueCon 2019 – Scaling Open Source Applications with SBCs
» Using the blacklist on the ProSBC
» TLS Ciphers available with ProSBC
» ProSBC on Azure
» ProSBC with HyperV
» Using the blacklist on the ProSBC
» TLS Ciphers available with ProSBC
» ProSBC on Azure
» ProSBC with HyperV
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum