Would like to be able to schedule a reset of the cellular modem each day.
We typically have sensitive equipment communicating though the router’s switch/LAN ports that can corrupt data if disconnected so don’t like to do a scheduled reboot.
Often we’re needing to send a tech out on a service call to reset a cellular modem via the GUI after losing cellular connectivity to InControl.
I think a scheduled reset of the cellular modem would really help getting devices back online without sending a tech.
These devices only have a single cellular connection.
Thanks
This may be a duplicate post. See Peplink | Pepwave - Forum .
Hi Rick, this isn’t a duplicate post.
This is a request to be able to schedule a daily reset of the modem using the command from the hidden menu below versus scheduled reboot of the entire router. The other post is about performing this same cellular reset command after a heath check failure.
Have you logged a ticket for this? If not, get the engineer to grab a diagnostic from the device next time it happens and log it.
Not having to regularly reboot a device is why I started using Peplink in the first place. This feature request seems to be trying to manage the symptoms rather than asking for a cure 
1 Like
Hi Martin, yes many years ago we moved from Cradlepoint/Netcloud to Pepwave/InControl due to the routers locking up and requiring power cycles. We had even started installing 3rd party power rebooting devices to auto-reboot on ping failure.
These are cellular only various MAX-BR1 models (regular, mini, and core) used for very simple outbound M2M data on 120MB data plans and all powered by 12v Telecom UPS units.
We started back with the 3G BR1 models and have about 2200 online in InControl and add about 50 a month.
We probably have 20 or so a week that we have to roll a truck/tech to reboot.
Was never this big of problem in the past and seems to have gotten worse with the 3G shutdown.
Have definitely found that SmartCheck will falsely detect a cellular connectivity failure and disables the connection taking the unit offline. Disabling SmartCheck has fixed quite a few of them and will become the standard.
What troubles me the most about the Pepwaves and cellular connectivity is once they get disconnected for whatever reason the modem quits making any effort to reconnect and the router doesn’t try to reset the cell modem. When logging into a unit that’s offline the cellular connection will just say disconnected with no action. I’d expect to see it acting like when trying to connect with a deactivated SIM where it tries, doesn’t get an IP, fails, then says resetting modem but that doesn’t happen.
We’re spending thousands of dollars weekly rolling trucks/techs to these devices and back looking at adding 3rd party power reboot devices.
As far as Pepwave support unless something has changed I’ve been very disappointed with them even when trying to just RMA a bad out of box device. I found it was much less costly to just replace the device then spend days or weeks troubleshooting with support replacing SIMs, transformers, antennas etc. Never could actually speak to someone and communication would be very slow and delayed. It’s been a while and hopeful maybe this has changed especially with the cost of required PrimeCare.
I guess I should add most of these are out of warranty and are just on standalone InControl renewals except for out latest HW3 models requiring Primecare.
Always appreciate you input and support on these forums. Thanks
Just curious … Apparently some of your devices have been around a while. Even 3G-capable units? Have you updated you cellular modem FW on all? Just thinking …
1 Like
Hi Rick,
So I just went through about 25 of them that we’ve sent techs out to between 3-7 times each to reboot and so far have found every one of them I checked is using the Telit LE910-NA V2 modem with firmware 20.00.504 or 20.00.505.
I started wondering about the modem model because once a tech gets it online I’ll use InControl and Remote Web Admin to disable SmartCheck, update firmware, then update cellular firmware via the support.cgi page and realized all the problem modems I was working on were 20.00.504 or 20.00.505 firmware levels. However updating from 20.00.504 to the latest 20.00.505 hasn’t made any difference on those devices which are BR1-Mini and BR1-Mini Core units.
I’ll need to dig deeper but appears the same models using the Sierra Wireless MC7354 or Qualcomm LE910C4-NF modems aren’t having the problem.
2 Likes
That’s very interesting information.