When using the Sim Switch function, the SIM card in slot 2 is not properly activated.
Here below the event logs lines (I have extracted the most relevant ones) for this problem:
1880 Fri Aug 29 10:50:19 2025 daemon.err mobifd: [gsm.modem0] GSM error in “mb_get_active_sim:885” (Request timed out), gsmd_method_id: “108”
1881 Fri Aug 29 10:50:19 2025 daemon.err mobifd: [gsm.modem0] Unable to get active SIM
1884 Fri Aug 29 10:50:32 2025 daemon.err mobifd: [gsm.modem0] GSM error in “mb_get_active_sim:885” (Request timed out), gsmd_method_id: “108”
1887 Fri Aug 29 10:50:45 2025 daemon.err mobifd: [gsm.modem0] Unable to get active SIM
I can provide the whole set of event logs lines if required to get a better understanding of the problem (as new user I cannot attach files here).
If I make SIM2 default and restart the router, it gets connected. It looks like cold boot works, hot switch fails. It seems during hot switches there is no enough time given to this brand of SIM in SIM2 to timely respond to the initialisation process.
Can this be fixed through a firmware upgrade whereas the switch process gives more time to the SIM to respond during the initialisation process?
Thanks for reaching out. The problem is clear, however, you did mention firmware upgrades, that’s why I’d like to ask - what firmware version do you currently have installed on your device? Also, is there any notification of the modem firmware being available for download?
I’ve tested “hot switching” on my own RUTX11 and seems like I have no issues with this. Restarting the device, of course, works as well. When you set the SIM2 to be the primary SIM, under Status → network → mobile does it show the Status of the SIM as “Inserted”?
Thanks for your feedback.
The current firmware is 7.17.2.
I am waiting s few weeks before installing 7.17.3, as it is very recent.
I usually wait for a “stable” version. Exceptionally this time I have installed version 7.17.2 although not a stable version yet, because I saw one of the fixings was related to the SIM Switch feature, although not specifically referring to my problem.
The problem I have identified started when I moved to a new brand as SIM 2. In the past, with another brand of SIM, * had no problem.
I mentioned a possible fixing through the firmware, hoping that the hot switching issue I have described could he solved, assuming it is a timing issue.
Answering to your question about SIM2 being the default SIM, I confirm that in this case the SIM results as inserted and connected.
In short, my guess is that different SIMs have different timings reaction to the router’s modem initialisation quests durind a hot switch.
Interesting, so from what I’ve gathered, the issue seems to only appear with a certain brand of SIM card rather than with any single one of them. Would that be correct?
Could you provide more information on the problematic SIM card? Of course, this information will be for research purposes & to pass the information to the relevant R&D department.
Yes, confirmed: when I changed brand of SIM, I noticed the failing SIM Switch as described above. More info about the new SIM card: the service provider is called Very Mobile, a subsidiary brand of Wind3 in Italy. I don’t know what other details to provide apart from the fact that it seems not able to comply with the “hot” SIM switch initialisation process, while it has no problem when it is the default SIM and the router starts from booting.
I hope the few lines of the logs I have shared can help in identifying the problem. As I cannot upload file here, here below you can see the complete result when I have run logread -f command from SSH after having triggered a SIM Switch from SIM1 to SIM2 (SIM2 is the new SIM with the problem):
root@Teltonika-RUTX11:~# logread -f
1847 Fri Aug 29 10:50:06 2025 kern.notice kernel: SMS received from: +39xxxxxxx (internal modem)
1848 Fri Aug 29 10:50:06 2025 daemon.err urcd: Error: Failed to find ‘ip_block’ object.
1849 Fri Aug 29 10:50:06 2025 daemon.err /usr/sbin/sms_utils: Error: Failed to find ‘ip_block’ object.
1850 Fri Aug 29 10:50:07 2025 daemon.notice netifd: mob1s1a1 (334): Stopping network mob1s1a1
1851 Fri Aug 29 10:50:07 2025 user.notice qmux: Stopping network on device: /dev/cdc-wdm0 cid: 21
1852 Fri Aug 29 10:50:07 2025 daemon.notice netifd: mob1s1a1 (334): Command failed: Not found
1853 Fri Aug 29 10:50:07 2025 user.notice netifd: uqmi -s -d /dev/cdc-wdm0 -t 3000 --set-client-id wds,21 --stop-network 0xFFFFFFFF --autoconnect
1854 Fri Aug 29 10:50:07 2025 user.notice qmux: Freeing cid: 21
1855 Fri Aug 29 10:50:07 2025 user.notice netifd: uqmi -s -d /dev/cdc-wdm0 -t 3000 --set-client-id wds,21 --release-client-id wds
1856 Fri Aug 29 10:50:07 2025 daemon.notice netifd: Interface ‘mob1s1a1_4’ is disabled
1857 Fri Aug 29 10:50:07 2025 daemon.notice netifd: Network device ‘qmimux0’ link is down
1858 Fri Aug 29 10:50:07 2025 daemon.notice netifd: Interface ‘mob1s1a1_4’ has link connectivity loss
1859 Fri Aug 29 10:50:07 2025 daemon.notice netifd: mob1s1a1 (334): “No effect”
1860 Fri Aug 29 10:50:07 2025 daemon.notice netifd: mob1s1a1 (334): Command failed: Permission denied
1861 Fri Aug 29 10:50:07 2025 daemon.notice netifd: Interface ‘mob1s1a1’ is now down
1862 Fri Aug 29 10:50:07 2025 daemon.warn dnsmasq[3567]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
1863 Fri Aug 29 10:50:08 2025 daemon.notice netifd: mob1s1a1_4 (21501): udhcpc: SIOCGIFINDEX: No such device
1864 Fri Aug 29 10:50:08 2025 daemon.notice netifd: mob1s1a1_4 (21501): udhcpc: received SIGTERM
1865 Fri Aug 29 10:50:08 2025 daemon.notice netifd: mob1s1a1_4 (21501): udhcpc: unicasting a release of 100.88.51.65 to 100.88.51.66
1866 Fri Aug 29 10:50:08 2025 daemon.notice netifd: mob1s1a1_4 (21501): udhcpc: sending release
1867 Fri Aug 29 10:50:08 2025 daemon.notice netifd: mob1s1a1_4 (21501): udhcpc: can’t bind to interface qmimux0: No such device
1868 Fri Aug 29 10:50:08 2025 daemon.notice netifd: mob1s1a1_4 (21501): udhcpc: bindtodevice: No such device
1869 Fri Aug 29 10:50:08 2025 daemon.notice netifd: mob1s1a1_4 (21501): udhcpc: entering released state
1870 Fri Aug 29 10:50:08 2025 daemon.notice netifd: mob1s1a1_4 (21501): Command failed: Permission denied
1871 Fri Aug 29 10:50:08 2025 daemon.notice netifd: Interface ‘mob1s1a1_4’ is now down
1872 Fri Aug 29 10:50:08 2025 daemon.info dnsmasq[3567]: read /etc/hosts - 12 names
1873 Fri Aug 29 10:50:08 2025 daemon.info dnsmasq[3567]: read /tmp/hosts/dhcp.cfg01411c - 2 names
1874 Fri Aug 29 10:50:08 2025 daemon.info dnsmasq-dhcp[3567]: read /etc/ethers - 0 addresses
1875 Fri Aug 29 10:50:08 2025 kern.info Mobile data disconnected (internal modem)
1876 Fri Aug 29 10:50:08 2025 daemon.info event_juggler: [7] Log event triggered
1877 Fri Aug 29 10:50:08 2025 daemon.info event_juggler: [7] Event triggered
1878 Fri Aug 29 10:50:09 2025 daemon.info mobifd: [gsm.modem0] Config reload initiated
1879 Fri Aug 29 10:50:10 2025 user.notice qmux: mob1s1a1 teardown successful
1880 Fri Aug 29 10:50:19 2025 daemon.err mobifd: [gsm.modem0] GSM error in “mb_get_active_sim:885” (Request timed out), gsmd_method_id: “108”
1881 Fri Aug 29 10:50:19 2025 daemon.err mobifd: [gsm.modem0] Unable to get active SIM
1882 Fri Aug 29 10:50:23 2025 daemon.err rms_mqtt[9757]: Level: 16, Log: Client 1107048615 sending PINGREQ
1883 Fri Aug 29 10:50:28 2025 daemon.info event_juggler: [8] Action performed
1884 Fri Aug 29 10:50:32 2025 daemon.err mobifd: [gsm.modem0] GSM error in “mb_get_active_sim:885” (Request timed out), gsmd_method_id: “108”
1885 Fri Aug 29 10:50:32 2025 daemon.err mobifd: [gsm.modem0] Unable to get active SIM
logread -f | grep modem1886 Fri Aug 29 10:50:45 2025 daemon.err mobifd: [gsm.modem0] GSM error in “mb_get_active_sim:885” (Request timed out), gsmd_method_id: “108”
1887 Fri Aug 29 10:50:45 2025 daemon.err mobifd: [gsm.modem0] Unable to get active SIM
1888 Fri Aug 29 10:50:58 2025 daemon.err mobifd: [gsm.modem0] GSM error in “mb_get_active_sim:885” (Request timed out), gsmd_method_id: “108”
1889 Fri Aug 29 10:50:58 2025 daemon.err mobifd: [gsm.modem0] Unable to get active SIM
1890 Fri Aug 29 10:51:06 2025 kern.notice IPv4 connectivity started to fail
1891 Fri Aug 29 10:51:10 2025 daemon.err odhcp6c[3432]: Failed to send SOLICIT message to ff02::1:2 (Network unreachable)
1892 Fri Aug 29 10:51:11 2025 daemon.err mobifd: [gsm.modem0] GSM error in “mb_get_active_sim:885” (Request timed out), gsmd_method_id: “108”
1893 Fri Aug 29 10:51:11 2025 daemon.err mobifd: [gsm.modem0] Unable to get active SIM
Thanks for providing the patch of logs. For troubleshooting purposes, we will require more sensitive information from your end, such as the troubleshoot file, which may contain passwords, public IP addresses, serial numbers, and such. To avoid leaking this information, we have sent you a form to fill out, which you will receive in your e-mail inbox that you have registered your account with in the forums. In the Ticket ID field of the form, please enter the ID of this thread, which is 15543.
After the form is filled out, we receive it and we’re able to send you an email, after which you can then reply to it by sending the required files or providing more information.