| Nextgen clustering |  Search
|
|
NowSMS Support Forums ⬆ NowSMS NextGen Support ⬆ |
◄ ► |
| Author | Message | |||
| marc bazimon Frequent Contributor Username: Marc_orange Post Number: 106 Registered: 01-2007 |
Hi Nowsms support , Project of swapping windows by Linux is started. The goal for us is to have two MMSC that run on different geographical site. I have some question regarding this : 1) do we have the choice between a actice/active or a master/backup mode for the clustering ? 2) we wanted to use the same DB for both MMSC, but in the case of the active/active clustering, in order to have both MMSC receiving traffic , i Guess we have to install a load balancer before the both MMSC. is there any recomendation by using this method by example with the DR that should be send to the proper MMSC. Using master/backup clustering mode , it will be more easy 3) we have got , around 300 000 subscribers , what are your recomendations for the DB mariadb or mysql ? Thanks before hand for your advices , Br Marc | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8478 Registered: 10-2002 |
Hi Marc, If multiple MMSC nodes are using the same database, they are all active. There is no need to ensure that delivery reports are sent back to the same MMSC node ... all nodes have access to the same processing data. Therefore, there are no special considerations for a load balancer. As for mariadb vs. mysql, we don't have a preference, and would recommend using whichever platform your staff is the most comfortable with. Regards, Bryce | |||
| marc bazimon Frequent Contributor Username: Marc_orange Post Number: 107 Registered: 01-2007 |
Hi Bryce , Thanks for your feedback , From my point of viiew , the load balancer was more for the MMS MO. MMS sent from the network come from the Core Network node ( GGSN or SSR or etc..depending the radio access 2G,3G, 4G, or 5G) so a load sharing must be perform in front of both mmsc in order to distribute equally the incoming traffic to both. This reflection is available if the architecture of MMSC is on active-active. If we run master/backup node , in this case , no need for a load balancer of course. Br Marc | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8479 Registered: 10-2002 |
Hi Marc, Yes, I agree. Sorry if my response was confusing. Let me clarify... I was just saying that there weren't any "special considerations for a load balancer". You were asking about an example of a DR being sent to the proper MMSC. If this were necessary (it is not), then I would consider this to be a special consideration ... the load balancer would need to have some special logic to recognize this requirement. I am not aware of any situation where follow-up requests need to be directed to the same MMSC. Therefore, any load balancer just need to distribute the traffic equally. Regards, Bryce Norwood NowSMS Support | |||
| marc bazimon Frequent Contributor Username: Marc_orange Post Number: 154 Registered: 01-2007 |
Hi Bryce we want to activate the clustering in order to have two redondant MMSC on separate site. in this way , we did build a Mariadb database. is there any recomendation for the volumetry or cpu and RAM. is there any need to add some specific configuration for the DB ? thanks beforehand for your feedback , Have a nice day , Br Marc | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8606 Registered: 10-2002 |
Hi Marc, We have not discovered any specific configuration requirements or recommendations. Regards, Bryce | |||
| marc bazimon Frequent Contributor Username: Marc_orange Post Number: 157 Registered: 01-2007 |
Hi Bryce, hope you are well , we want to deploy the second MMSC in order to have such resilience. so we did build a mariaDB on our testbed. Connection had been successfully done , ad this had been create 16 tables , and sending mms increase the value as you can see below. MariaDB [uammscdb1]> show tables ; +------------------------------+ | Tables_in_uammscdb1 | +------------------------------+ | CONNECTEDMODEMS | | MISC | | MMSCDATA | | MMSCUSERS | | NOWSMSLOG | | SARLock | | SMPPDATA | | SMSIN | | SMSQ | | SMSUSERS | | SMSUSERSQ | | STATCOUNTER | | TOKENS | | USERCREDITS | | USERSTATS | | VASPQ | +------------------------------+ 16 rows in set (0.000 sec) MariaDB [uammscdb1]> select table_schema,table_name,table_rows from information_schema.tables where table_schema='uammscdb1'; +--------------+-----------------+------------+ | table_schema | table_name | table_rows | +--------------+-----------------+------------+ | uammscdb1 | MISC | 4 | | uammscdb1 | SMSQ | 0 | | uammscdb1 | SMPPDATA | 3 | | uammscdb1 | SMSUSERSQ | 0 | | uammscdb1 | USERCREDITS | 0 | | uammscdb1 | SMSIN | 0 | | uammscdb1 | MMSCUSERS | 0 | | uammscdb1 | STATCOUNTER | 7 | | uammscdb1 | NOWSMSLOG | 6 | | uammscdb1 | CONNECTEDMODEMS | 0 | | uammscdb1 | TOKENS | 0 | | uammscdb1 | SARLock | 1 | | uammscdb1 | USERSTATS | 1 | | uammscdb1 | MMSCDATA | 2 | | uammscdb1 | SMSUSERS | 2 | | uammscdb1 | VASPQ | 0 | +--------------+-----------------+------------+ 16 rows in set (0.001 sec) I have question regarding the production site. - Can you give me minimal value for CPU , Storage and memory in case of it become huge on production. ? - As far as i understand the mariadb is also use for configuration files. where is the table that managed configuration? - LOG files are stored also on DB ? thanks before hand for your feedback n Don't hesitate to contact me if you want test some configuration , my testbed is yours. Br Marc | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8618 Registered: 10-2002 |
Hi Marc, As your system is running in an MMSC configuration, the MMSCDATA table will have the largest storage requirement, similar to the size of the MMSCDATA directory structure. That said, there is currently a bug where older log data is not automatically purged, which can cause the log to have rather large storage requirements. This will be fixed in the next update, which will default to retaining log data for 90 days by default, with the ability to override this setting with LogRetainDays=### under the [SMSGW] header in SMSGW.INI. As a temporary solution, to manually prune the log and delete older log entries, we have provided the following example SQL command which removes log data from prior to this year: DELETE FROM NOWSMSLOG WHERE DateTime < '2026-01-01 00:00:00.000'; Configuration files (and shared settings like SSL/TLS certs are stored in the CONFIG table, but there is no need to access directly. Each server has a local copy of SMSGW.INI and MMSC.INI. If the file is updated, the server sees the updated datetimr stamp, and uploads the file to the shared database. Other servers will download the updated copy, checking for updates once per minute. Archived copies of updated config files are saved in the database but there is currently no UI to view them. Regards, Bryce | |||
