HAP AC Lite bricked (3rd one?)

Hi

I took delivery of a new tower version of the HAP AC Lite a couple of days ago, was impressed with the tower design, nice looking bit of kit.

I have previously had to return 2 of these that died when upgrading routerOS on them, but thought I’d give the tower version a go … mistake it seems.

Just tried to upgrade it to the latest version 6.38.1 and yet again its died, wifi gone, when I plug it into another of my devices and look at the LAN port its just up and down all the time … netinstall doesnt work, nothing does.

Is there a serious issue with these devices ? it’s really screwed me up with a delivery for a customer tomorrow.

try net-install, i have upgraded a normal version of hap ac lite and the device don’t returned from upgrade procedure

was necessary to do net-install to recover the device

http://wiki.mikrotik.com/wiki/Manual:Netinstall

4th one just died on ROS update.

Cant get it back using netinstall either, just see the port flapping.

Come on Mikrotik, this isn’t a coincident … please let us know what the issue is.

nikc.

  1. how did you upgrade? describe the procedure step by step
  2. what do you mean “died”. do you see it in the winbox neighbours, when plugged into the PC through port 2 ?
  1. how did you upgrade? describe the procedure step by step - via quickset download and install option
  2. what do you mean “died”. do you see it in the winbox neighbours, when plugged into the PC through port 2 ? - Died = never comes back from ROS upgrade. Not visible via Winbox IP neighbors on my CRS and the port is just up and down every 20 seconds. I will try direct ethernet from the PC to port 2.

Which version did you have before, and which one did you upgrade to (which release channel and which version)?

Going from 6.37.4 to 6.38.3.

But it dont think its version specific as the others that have not come back after upgrade will have been different versions.

I tried direct connect to the PC but I still cant netinstall, i can see the port on the PC flapping …

Which packages were installed on device? Was it only RouterOS bundle package?

Have you tried to:

  1. Power off device;
  2. Press and hold reset button;
  3. Power on device;
  4. Release button after 2-3 seconds;
  5. If it boots up, then execute “/system routerboard upgrade” and “/system reboot”

If that did not help, then make sure that you do not make some common mistakes during Netinstall process:
*) Use latest Netinstall
*) Firewall on computer is turned off
*) IP of computer and Netinstall is on same subnet;
*) If you use Windows, then gateway IP address on computer must be specified
*) Other DHCP servers must not be involved
*) Router must be connected on boot interface

To start installation you must power on the router with pressed reset button and wait until it shows up in Netinstall

Hi
I have a mikrotik Hap Lite and i upgrade it to latest version via winbox
after uploading file and reboot, ACT LED is Always On and i cannot connect to it with Winbox .
is there any way to fix this.

https://wiki.mikrotik.com/wiki/Manual:Netinstall

PS. Have you considered reading the above posts first or searching the forum for a solution before posting a rather typical question that have been answered already quadzillion times before?

I get also a flapping port issue. Netistall did not worked. I keeped pressed the button for 5 munites but never come to netinstall. It keeps flapping.
I used eth1 (not the internet port) for netinstall. how much it suppose to press the reset button to go on netinstall?
the issue come after upgrade to 6.41.3.
I think it will be my first mikrotik that bricked for good!

Oddly enough I just encountered a similar situation, HAP ac^2 running all-in-one 6.41.3 (upgraded through /system packages and rebooted).
Later I wanted to get rid of some packages so I scp’ed advanced-tools, dhcp, ipv6, multicast, ntp, routing, security, system & wireless ver. 6.41.3 (ARM) to move from all-in-one to only-a-few-of-them but the device never came back alive.

It’s a few KMs away so I will have to check it later and I will update this post.

edit: Fixed via netinstall