All of our TRB245 devices are installed remotely, and we have to manage them via the mobile interface.
When upgrading from any version to TRB2_R_00.02.06.1 when you keep the settings the following occurs:
Following the reboot for the upgrade, the appears to boot fine, the signal strength LEDs operate as normal, and the connection status LEDs (in my case the 4G one) flashes on and off – the mobile provider can see the device has connected to the network, but it has not established a data connection.
A reboot of the device at this point can do one of three things:
- The device will return to the same state - signal strength LEDs operate as normal, and the connection status LEDs (in my case the 4G one) flashes on and off
- The signal strength LEDs flash on and off together, this repeats until the device is rebooted
- The device works.
In all cases the WebUI and SSH are available via the ethernet port; from within there we can reboot the device, and the state will generally change. Typically after a maximum of three reboots the device is working.
We use Ping/Wget reboot to help with this – however even using this, it makes a firmware upgrade appear to take up to 25 minutes long.
Also, what we have discovered, is that state 2 (The signal strength LEDs flash on and off together) is quite common – this randomly happens on software reboots, and power cycles. If Ping/Wget reboot is enabled, after 10 minutes the device will reboot, and 99% of the time the device will boot normally; however in some instances it will do the same thing, however the Ping/Wget reboot will kick in again, and normally after two reboots its back on line.
