I'm a little fuzzy on the details prior to my involvement, so here goes.
A friend, significantly more knowledgeable re: IT than I, decided to update his Mikrotik LHG-XL (its not a newer ac device) to the latest release. It had a much older release of a few years ago which I didn't ask what it was but likely 3.22.xx.x. Not realizing that the newer firmware is very specific to the exact device, he sysupgraded to the LHG and not the LHG-XL file. It seemed to take the upgrade, but the node started acting funny (tech term
) but eventually seemed to work. However, it would still not sysupgrade to the LHG-XL file when attempted. He tried to do it via SSH. Same result.
So, I suggested we try using the kernel file and do a fresh install of the latest stable release of 3.24.6.0. We successfully put the image in memory, got a successful ping, and then did the next step of the fresh install of sysupgrade to the 3.24.6.0 per instructions. It would not take the sysupgrade step, the kernel was still in the memory until we killed power.
Tried again, same result.
So we tried an install of older file 2.22.6.0 using the ar71xx firmware. It took that and were successful in bringing the node back with the final step of the sysupgrade to the NOCALL page to input the usual parameters and password.
From there, we tried a sysupgrade in the AREDN UI to ath79 firmware, which I believe was 3.23.12.0. It would not do the sysupgrade and the firmware remained at 3.22.6.0.
It seems that this device would sysupgrade using the ar71xx firmware but not the newer ath79 code. At least it's up and running for now.
I have successfully sysupgraded another LHG-XL from the older ar71xx firmware to the ath79 to the latest stable release, but in steps along the way as newer firmware was released. And also made sure we used the correct LHG-XL file and not the LHG file.
We did not record any snapshots of the data unfortunately.
At a loss as to why it won't sysupgrade to the newer firmware now, but will sysupgrade with the old.
Any thoughts would be appreciated.
In the meantime, he ordered a newer LHG-XL-ac device which should resolve issues in getting on the network without problems and we can troubleshoot at our leisure.
Thanks
Bob
KE6GYD
A friend, significantly more knowledgeable re: IT than I, decided to update his Mikrotik LHG-XL (its not a newer ac device) to the latest release. It had a much older release of a few years ago which I didn't ask what it was but likely 3.22.xx.x. Not realizing that the newer firmware is very specific to the exact device, he sysupgraded to the LHG and not the LHG-XL file. It seemed to take the upgrade, but the node started acting funny (tech term
) but eventually seemed to work. However, it would still not sysupgrade to the LHG-XL file when attempted. He tried to do it via SSH. Same result.So, I suggested we try using the kernel file and do a fresh install of the latest stable release of 3.24.6.0. We successfully put the image in memory, got a successful ping, and then did the next step of the fresh install of sysupgrade to the 3.24.6.0 per instructions. It would not take the sysupgrade step, the kernel was still in the memory until we killed power.
Tried again, same result.
So we tried an install of older file 2.22.6.0 using the ar71xx firmware. It took that and were successful in bringing the node back with the final step of the sysupgrade to the NOCALL page to input the usual parameters and password.
From there, we tried a sysupgrade in the AREDN UI to ath79 firmware, which I believe was 3.23.12.0. It would not do the sysupgrade and the firmware remained at 3.22.6.0.
It seems that this device would sysupgrade using the ar71xx firmware but not the newer ath79 code. At least it's up and running for now.
I have successfully sysupgraded another LHG-XL from the older ar71xx firmware to the ath79 to the latest stable release, but in steps along the way as newer firmware was released. And also made sure we used the correct LHG-XL file and not the LHG file.
We did not record any snapshots of the data unfortunately.
At a loss as to why it won't sysupgrade to the newer firmware now, but will sysupgrade with the old.
Any thoughts would be appreciated.
In the meantime, he ordered a newer LHG-XL-ac device which should resolve issues in getting on the network without problems and we can troubleshoot at our leisure.
Thanks
Bob
KE6GYD