After rebooting the smsgtw robot due to some hardware issues I ticked the box 'Subscribe to Nimsoft alarms' in the smsgtw probe configuration in Infrastructure Manager.
A while later I noticed that the smsgtw-1 queue in the hub was processing tens of thousands of alarms and the smsgtw probe was unable to cope with such high volume of information.
What might have caused this and how can I resolve the issue?
The cause of this problem was that the nas was responsible for sending the SMS messages via Auto-Operator profiles and therefore the smsgtw-1 queue should be configured with SMS subject only. By ticking the box 'Subscribe to Nimsoft alarms' in the smsgtw probe configuration triggered the smsgtw-1 queue to be configured with other subjects:
This causes the queue to receive messages that are not supposed to be sent via SMS.
Deactivate the smsgtw probe, empty the smsgtw-1 queue and untick the box 'Subscribe to Nimsoft alarms' in the smsgtw probe configuration in Infrastructure Manager. Once this is saved you can enable the smsgtw probe again.