Community discussions

MikroTik App
 
mattiwei
just joined
Topic Author
Posts: 3
Joined: Tue Oct 13, 2020 12:21 pm

wAP R ac upgrade to v7.1beta2 fails

Tue Oct 13, 2020 12:37 pm

Hi,
upgrading/installing wAP R ac with v7.1beta2 fails:

Model: RBwAPGR-5HacD2HnD
Revision: r2
Firmware type: ipq4000L
Factory firmware: 6.44.5
Current firmware: 6.47.4
Upgrade firmware: 6.47.4

configuration: factory default

upgrade via Winbox V3.27:
- upload routeros-7.1beta2-arm.npk to root folder, reboot
=> not visible in Winbox anymore
=> power cycle after 10 minutes. Same behaviour: not visible in Winbox

(after downgrading to 6.47.4 via NetInstall to start over)

upgrade via NetInstall V7.1beta2:
- (verified using Wireshark): TFTP download of the "netinstall-install-image" or what you want to call it OK, finished (5982 packets)
- but nothing more.
- power cycle after 5 Minutes -> not visible in Winbox

The only way to get it back to life is to downgrade again to 6.47.4 using Netinstall.
This is is the second box showing the same behaviour (I returned the first box as I suspected a DOA)

Or did I miss something?

Best regards

Mathias
 
WeWiNet
Member
Member
Posts: 489
Joined: Thu Sep 27, 2018 4:11 pm

Re: wAP R ac upgrade to v7.1beta2 fails

Tue Oct 13, 2020 12:53 pm

Hi, I have that device under that ROS running.

To avoid using wrong firmware file, have you tried to upgrade from within "system"/Packages" ?
You select "development" branch and then check for updates. And then click update..?

I think it is worth trying.

PS: Do you have an LTE module installed? ROS7 uses different way of communicating with LTE module.
Might be worth to remove LTE module if problem persists.
You might want also before moving to ROS7 to set LTE module to MIBM mode...
WeWiNet

**
MTCNA
I like a new challenge, I migrate to ROS7... :? or maybe I am just crazy :lol: !!!
 
mattiwei
just joined
Topic Author
Posts: 3
Joined: Tue Oct 13, 2020 12:21 pm

Re: wAP R ac upgrade to v7.1beta2 fails

Tue Oct 13, 2020 1:49 pm


To avoid using wrong firmware file, have you tried to upgrade from within "system"/Packages" ?
You select "development" branch and then check for updates. And then click update..?

PS: Do you have an LTE module installed? ROS7 uses different way of communicating with LTE module.
Might be worth to remove LTE module if problem persists.
You might want also before moving to ROS7 to set LTE module to MIBM mode...
Hey thanks for your hints!
I did (with the first box) go with the default installation option (Winbox->system/packages). It unfortunately failed too.
And yes: I do have an LTE module: "R11e-LTE6" (firmware R11e-LTE6_V020), that might be the culprit. In general, I do not want get into the position to have the card removed every time before I do upgrades ... unless you are interested to know if the card works after the upgrade...
Regarding MIBM mode: can you give me a tip on how to do this (yes, I googled it, but failed miserably)...

Thanks again

Mathias
 
WeWiNet
Member
Member
Posts: 489
Joined: Thu Sep 27, 2018 4:11 pm

Re: wAP R ac upgrade to v7.1beta2 fails

Tue Oct 13, 2020 1:57 pm

Your LTE FW is also old.

Please do first upgrade the LTE module FW:
 /interface lte firmware-upgrade number=0
Then try again...
WeWiNet

**
MTCNA
I like a new challenge, I migrate to ROS7... :? or maybe I am just crazy :lol: !!!
 
mattiwei
just joined
Topic Author
Posts: 3
Joined: Tue Oct 13, 2020 12:21 pm

Re: wAP R ac upgrade to v7.1beta2 fails

Tue Oct 13, 2020 4:56 pm

I figured out what the problem was.
The title of this post should actually renamed to "wAP R ac with upgraded default configuration does not show up in Winbox after upgrade"...

At some point in time, I connected to the MAC address of the wAP R ac, although it was not showing up in Winbox's neighbor list - that worked...
So it had to be an issue with the /ip neighbor settings... unfortunately, I did not take a screen shot then, but it looked something similar to:
 [admin@MikroTik] > /ip neighbor discovery-settings export
set discover-interface-list=*1000003
I issued
/ip neighbor discovery-settings set discover-interface-list=all
and voilà! The router re-appeared on the neighbor list. Note: I do not think that putting "all" in the settings is best practice. I saw "!dynamic" on other occasions.

Anyway: Thanks for your help! (LTE firmware has been upgraded ;) )

Who is online

Users browsing this forum: dyke, eworm, nannou9, rua and 5 guests