MP70 modem keeps dropping internet

AirLink Routers AirLink routers
1

We have several MP70 modems and a few months ago, they started dropping the internet. The problem is that they won’t reconnect on their own until the user hits the reboot button on the modem. It will then go through a reboot cycle and then reconnect. It is happening with almost all our modems now at least once but often more than once in an 8 hour shift. Anyone else having this issue?

Thanks,
Jim

2

I just logged in to the forum to report the same thing. Who is your carrier and what firmware version are you on?

We are on FirstNet with 4.14. I know previous firmware versions had a bug where the SIM enumeration would fail so when it checks if there is a SIM card available in Slot 1 and 2 it wouldn’t detect either one and would just fail to connect. But I am not sure what the problem is now.

I am seeing random internet drops and our dispatch would have to send the reset text message to the device to remotely reset it in order for it to work again.

After upgrading to 4.14 the devices seem to be bricking themselves completely. I can’t even send a reset message to them. The Wi-Fi and Signal indicator light flash red and trying to connect to alms manager fails using the Ethernet cable. I’ve had 2 devices do this in the past month. I’ve sent one out and they replaced the module. I am trying to troubleshoot the second one to see if I can figure out the cause.

3

Thanks for the reply,

We are on 4.14.0.014 with Verizon. I’m curious what is the “reset text message”, that would be handy to know.

Jim

4

This is a little outdated but it has enough to get you started. Text messaging will need to be included with your plan otherwise Verizon will charge you 25c per text if I remember correctly.

https://www.sierrawireless.com/resources/support/airlink/forum/sending_sms_at%20commands.pdf

Once setup you can simply text the word reset to the device’s mobile number and it will initiate a remote restart. If you have the ignition sense / low power timer then the vehicle will have to be on in order for it to complete the reset cycle. If the ignition is off then the device will just power off and not boot up until the ignition is turned back on. The device can send back confirmation after successful restart.

5

Hi jcheverie,

There are some connectivity issues reported on ALEOS 4.14. I have 2 suggestions:

  1. Downgrade to ALEOS older version over AirVantage, I recommend using version 4.12 because no similar behavior was reported on this version.
  2. Wait for the next ALEOS 4.15 and try again. This firmware will be released soon.

Thanks,

1 Like
6

I chose a downgrade option on one modem to the 4.12 but nothing is happening - under “Installing application” the progress bar isn’t moving, I sent a reboot to that modem and it’s still not progressing. I’m told the modem is on…

7

Hi jcheverie,

"Installing application” on AirVantage is not used for this case.

First, you need to make sure all your progress bars are canceled by clicking them then press “Abort”. Then follow these steps below:

  1. On AirVantage, click on Synchronize button (1 in the picture) to start to synchronization job
  2. On gateway, go to ACEmanager → Services - > ALMS → Click Connect button
  3. Wait for a minute, the progress bar of the synchronization job is finished. This step makes sure your device is able to connect to AirVantage.
  4. On AirVantage, click “Upgrade Firmware”(2 in the picture), choose your desired firmware. Then the upgrading job will be created on Airvantage.
  5. On gateway, go to ACEmanager → Services - > ALMS → Click Connect button. At this time, the upgrading job will start.
  6. Wait for the update completion.
    image

Note: The update can take up to 30 minutes to complete, depending on the speed of your network connection.

Thanks,

1 Like
9

Just to let everyone know, I ended up rolling back to 4.12 and it did not correct the issue…Sierra Wireless has enabled a ping monitor on two of our devices which they will then pull the logs on…stay tuned

Jim

10

Same issues here. Downgraded to 4.12 but it shows radio module firmware is out of date and will not grab a connection. Checking with Sierra Rep for any suggestions such as old radio module firmware.

1 Like
11

Thank you for your reply. That was helpful.

12

My pleasure!

Attempting to CC two contacts on this ticket if possible.

Added them to the CC section to see it carries over.

John Blouin <jblouin@sierrawireless.com>; Greg Billings <GBillings@sierrawireless.com>

13

So, we are still having an issue with ALL of our MP70 Modems. They drop the connection (which is normal for our area) but they don’t automatically reconnect. They won’t reconnect until the user physically reboots the modem. We should not have to reboot a modem everytime it loses connection. Sierra wireless engineers came up with a “fix”. They have enabled a ping monitor, when it senses a loss of network it triggers a software reboot of the modem. This will then re-establish network connection. This isn’t right and I don’t understand why our modems started doing this at the start of the summer. This never happened to us before. We have rolled back the firmware and that didn’t help. I’m open for any suggestions. Thanks!!

14

What firmware are you using and who is your cellular provider? I was told that there was an issue with the radio module firmware and the newest ALEOS. Using ATT we needed to use the below and it resolved the issue.

MP70_4.13.0.017.bin
EM7511_01.07.02.00_ATT_002.008_004

15

Any updates? We bought 170 of these routers and have continuous issues with the router losing/dropping connection.

1 Like
16

I seem to have run into the same problem. We have a vehicle-mounted MP70 which occasionally experiences network coverage drop-outs.

After the last drop-out it has failed to re-connect, even after cycling the ignition. Lights on the unit indicate a good signal, but no network connection.

17

Have you found a resolution to this issue?

18

Hi @spdit,
Welcome you to our community!
Could you please share with me some information as below:

  1. What firmware version and radio firmware version are you running?
  2. What network provider are you using? If you replace the current SIM with a new SIM of another operator, does this issue still happen?
  3. Has the issue happened before? Or did you do something on your MP70 that caused this issue?

Thanks,

19

I think I may have hit this same issue on 4.14.0.014. Is this resolve now in 4.16? I’m finding both the network and signal LEDs blink red in unison, while wifi, gps and the admin page are all functioning.

20

Hi @tim ,
Please upgrade your MP70 to ALEOS 4.16 following the link below:
https://source.sierrawireless.com/resources/airlink/software_downloads/mp70/mp70-firmware-list/#sthash.A7wxqNz9.dpbs
Then try again. Do the issue still happens in this case?
If the issue still happens, please let me know so I can help you further.

Thanks,

21

@jerdung

I have lost the admin portal from the device, the https://192.168.13.31:9443 page is no longer responding. I can ping the device successfully but even when I port scan that IP I see SSH & DNS services, but not 9443.

I went to recovery mode and installed 4.16 and rebooted. I ended up at the same state after with no WAN and not able to access the admin page (and now now wifi). I pulled the log from the recovery page and this is what I’m seeing? Do I have a bricked device?

Sep  9 00:01:34 warning ALEOS_EVENTS_dpRptGen: SaveGnssCsmData() calibration data too short: 0
Sep  9 00:01:34 warning ALEOS_EVENTS_dpRptGen: SaveGnssCsmData() calibration data too short: 0
Sep  9 00:01:34 warning ALEOS_EVENTS_dpRptGen: SaveGnssCsmData() calibration data too short: 0
Sep  9 00:01:35 warning ALEOS_EVENTS_dpRptGen: No GNSS Fix. Quality Indicator is 0 and 0 Satellites in Use. 0 seconds passed without fix.
Sep  9 00:01:35 warning ALEOS_EVENTS_dpRptGen: monitorFix : Lost fix at: Fri, 09 Sep 2022 00:01:35 UTC
Sep  9 00:01:35 warning ALEOS_EVENTS_dpRptGen: CheckRmcDate() GPS RMC rollover detected for RMC date 071214
Sep  9 00:01:38 notice ALEOS_FIRMWARE_rmswitchingcheck: getCsmValues Firmware Carrier: NOTSET
Sep  9 00:01:41 notice ALEOS_FIRMWARE_rmswitchingcheck: (qmisdkhelper) Waiting for the Radio Module to be ready
Sep  9 00:01:41 err ALEOS_FIRMWARE_rmswitchingcheck: (qmisdkhelper) Radio module is operating in boot-and-hold mode
Sep  9 00:01:42 err ALEOS_FIRMWARE_rmswitchingcheck: (qmisdkhelper) Radio module is operating in boot-and-hold mode
Sep  9 00:01:42 err ALEOS_FIRMWARE_rmswitchingcheck: (qmisdkhelper) Radio module is operating in boot-and-hold mode
Sep  9 00:01:43 err ALEOS_FIRMWARE_rmswitchingcheck: (qmisdkhelper) Radio module is operating in boot-and-hold mode
Sep  9 00:01:43 err ALEOS_FIRMWARE_rmswitchingcheck: (qmisdkhelper) Radio module is operating in boot-and-hold mode
Sep  9 00:01:44 err ALEOS_FIRMWARE_rmswitchingcheck: (qmisdkhelper) Radio module is operating in boot-and-hold mode
Sep  9 00:01:44 err ALEOS_FIRMWARE_rmswitchingcheck: (qmisdkhelper) Radio module is operating in boot-and-hold mode
Sep  9 00:01:45 err ALEOS_FIRMWARE_rmswitchingcheck: (qmisdkhelper) Radio module is operating in boot-and-hold mode
Sep  9 00:01:45 err ALEOS_FIRMWARE_rmswitchingcheck: (qmisdkhelper) Radio module is operating in boot-and-hold mode
Sep  9 00:01:46 err ALEOS_FIRMWARE_rmswitchingcheck: (qmisdkhelper) Radio module is operating in boot-and-hold mode
Sep  9 00:01:46 err ALEOS_FIRMWARE_rmswitchingcheck: (qmisdkhelper) Radio module not ready.
Sep  9 00:01:49 warning ALEOS_SYSTEM_WDlog: Process UpdateRebootMgr has failed to provide activity feedback 1 time(s) - No activity for 118 seconds
Sep  9 00:01:49 notice ALEOS_SYSTEM_UpdateRebootMgr: Device is not ready, blocking watchdog update attempt