You are here

Fail to upgrade MikroTik LHG 5HP XL

12 posts / 0 new
Last post
AC2OG
AC2OG's picture
Fail to upgrade MikroTik LHG 5HP XL
I tried to upgrade my MikroTik LHG 5HP XL from v. 3.22.8.0 to v 3.23.8.0. After 3 min of uploading the new firmware, the device did not terminate the booting, so I entered "http:// localnode.local.mesh:8080" and the device booted with the old firmware. Is there a special procedure to follow in this case?

Leo, AC2OG.
 
K6CCC
K6CCC's picture
Wait longer than 3 minutes.
Wait longer than 3 minutes.
Were you using the "Upload Firmware" from a local file or the "Download Firmware" from an internet source?  Personally I HIGHLY recommend downloading the firmware from the AREDN website to your computer and using the "Upload Firmware" method.
After a fairly short time (less than 30 seconds), the screen should change to indicate the that the firmware update is in progress.  Did it?

 
AC2OG
AC2OG's picture
Wait longer than 3 minutes
 This one was not my first upgrade! I waited more than 3 minutes and the .bin file was saved on my computer  The screen changed indicating the progress of the firmware update for some time and then disappeared. I waited for a further 3 minutes without success, finally, I entered the device with http:// localnode ....... no other choice!
w6bi
w6bi's picture
Dangerous?
If all else fails, you could set the "Dangerous" flag in Advanced Configuration and try it that way:  https://docs.arednmesh.org/en/latest/arednGettingStarted/advanced_config...
K6CCC
K6CCC's picture
Good point Orv.  I had to do
Good point Orv.  I had to do that on one of my LHGs many times.
 
K7EOK
Orv, one detail I'd like

Orv, I'd like clarfication please.  I'm aware of the dangerous upgrade ipk package that can be downloaded to a node and then it will accept a firmware upgrade with no safety checks.  What is the difference between the ipk package and hitting the Dangerous flag in Advanced Config?  If you use the Dangerous flag in Advanced Config to get an update done, can you later hit the on/off flag and turn it off ... unlike the ipk which you have to leave installed?  Are they functionally the same or are they different?

I see the flag turning up on nodes that have 3.23.80 on them, but the flag is not present on 3.22.12.0 ... so my guess is that this doesn't fix the problem of upgrading from 3.22.12.0 on BaseBox and QRT.  Is it the same package loaded as part of default firmware now, but not activated?

Ed
 

w6bi
w6bi's picture
Basebox and QRT

Both Basebox and QRT in the Supported Devices page are flagged with a (1).  Note 1 says:

This device is supported for new installs. It can also be upgraded from 3.22.12.0 after first installing the DangerousUpgrade package to disable the firmware compatibility checks. Proceed with caution. Do not remove this package once installed.

73
Orv W6BI
 

AC2OG
AC2OG's picture
Note (1) is not mentioned for
Note (1) is not mentioned for RBLHG-5HPnD-XL !!!
w6bi
w6bi's picture
Dangerous
That's true, but as Jim K6CCC mentioned he's had to do it frequently for one of his LHGs.
K7EOK
OK, let me try again.
OK, let me try again.

The Dangerous Upgrade Package cannot be uninstalled once installed.

Can the Dangerous Flag in Advanced Configuration in 3.23.8.0 be turned off once it has been used?  Or will that mess things up later?

Ed
 
K6CCC
K6CCC's picture
Can the Dangerous Flag in

Can the Dangerous Flag in Advanced Configuration in 3.23.8.0 be turned off once it has been used? 

The Dangerous setting on the Advanced Config page automatically sets back to off after you do an update.


 
K7EOK
Thank you
Thank you for the clarification.  The Flag in Advanced Settings does not behave long term like the package does.

That's what I needed to know.  73  Ed
 

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer