AP-121 stuck with orange lite won't reset, how to recover.

  • 2
  • Question
  • Updated 2 years ago
  • Answered
Device was unpluged while updating and now won't start.
Photo of Fred

Fred

  • 2 Posts
  • 0 Reply Likes

Posted 5 years ago

  • 2
Photo of Jason Zhou

Jason Zhou

  • 18 Posts
  • 13 Reply Likes
Fred,you can try to log in by console, if you can't see"Welcome to Aerohive product" on console, then you may have to install the HiveOS on this device by console. I think it's better for you to call for tech support, they can help you to install
the OS. Hope this may help.
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
I am now curious how this is implemented and how this type of failure might be at all possible, and if it is a design limitation. Are we to assume, therefore, that there is not an active and a passive boot loader and image written to Aerohive's devices?

I have noticed when updating via the console that it erases then writes the boot loader, then erases and writes the boot image.

Were the AP to go offline at the point that the boot loader were being changed, would it be bricked to the point where only JTAG recovery would be possible?

If this were something that I was designing, I would have both an active and passive boot loader and boot image (non-volatile flash memory is cheap these days so we are no longer space contained).

It is conceptually/abstractly possible to achieve an atomic (or close to atomic) update using this approach meaning that it should not be possible to fail in this way:

You simply write the boot loader or image to the passive locations, validate the checksum/signature, and then change the active 'pointer(s)'.

Nick
Photo of Jason Zhou

Jason Zhou

  • 18 Posts
  • 13 Reply Likes
Hi , Nick, you are right. but for AP121 we haven't implemented this active/passive mechanism for bootloader yet. For HiveOS we have backup image to boot if the bootloader is still working, but there is a case that the updated bootloader is not compatible to backup image. Then the backup image cannot be booted. So, for this case, I think the customer may have to make sure if the bootloader is still working, if not we will have to use JTAG recovery, if the bootloader still working, then we can write the compatible image to the device by console. and for your informatiion, our new products AP370/390 have this mechanism of two bootloader to avoid this type of failure.
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Cool! This is a great answer! :)
Photo of Fred

Fred

  • 2 Posts
  • 0 Reply Likes
Jason, I am able to get a login prompt when connected to the console, what is the user name and password? Would you know the command to pull the OS from a USB drive, and where I can get the OS. I tryed admin as a user and aerohive as the password with no luck.
Photo of Jason Zhou

Jason Zhou

  • 18 Posts
  • 13 Reply Likes
Hi, Fred, I think you may have changed your user and password, the default user and password of aerohive AP is "admin""aerohive", now you may have to install the HiveOS in bootloader. We do not support install HiveOS from USB drive. So, you need prepared a tftp/scp server, and download the HiveOS from here:https://support.aerohive.com/login
upload the HiveOS you need to your tftp/scp server, and follow this procedure to install it in bootloader.
1. connect the AP to a console and a network with a tftp server included.
2. plug in.
3. type the space bar to get into bootloader before the 4 seconds counting down is over.just like this, you see the arrow > means you are in the bootloader now.

4. set the tftp server ip unsing command "set_bootparam" you only need to set the TFTP server ip, and boot file location, other setting just press enter and jump.
the set bootparam should be like this:


5. Then you can install the HiveOS image to the device flash, using command "image_flash". it will try to get the OS from the tftp server you set.
6. After the loading and programming is done, use the command "reset" to reboot, your device should be able to start and you can login with the user"admin" and password "aerohive".

Again, I highly recommend you to call our tech support, They can offer more help for this.
Photo of Jason Zhou

Jason Zhou

  • 18 Posts
  • 13 Reply Likes
And if you need password to get into bootloader in step 3, the password is "administrator"
Photo of John Calderwood

John Calderwood

  • 2 Posts
  • 0 Reply Likes
Could the bootloader password have changed for version HiveOS 6.5r3 Honolulu.2530?  I need to reflash a failed rollback to HiveOS 6.4r1g.2138 and the bootloader is rejecting "administrator" as a password. 
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Incidentally, HiveOS 6.5r3 switched to dual images on the AP121/AP141.
The rollback may not have worked correctly, and indeed be supported, because of this.
(Edited)
Photo of John Calderwood

John Calderwood

  • 2 Posts
  • 0 Reply Likes

I only had one that failed to rollback.  I started having access points losing connection to the hivemanager after upgrading to 6.5r3, and I saw at least one with high cpu usage warning.  "Upgrading" back to 6.4r1g fixed all the problems. 

Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Definitely worth doing a root cause analysis of what's happening with a support case, in my opinion. It may be, for example, different resource tradeoffs are kicking in giving you that symptom rather than there being a bug in HiveOS outright.
Photo of danbrady143

danbrady143

  • 5 Posts
  • 1 Reply Like
What is the bootloader password for HiveOS 6.5r3 Honolulu.2530?  "administrator" does not work 
Photo of danbrady143

danbrady143

  • 5 Posts
  • 1 Reply Like
Great stuff...works like a charm. Thanks!
Photo of James Bryant

James Bryant

  • 3 Posts
  • 0 Reply Likes
I know that this is a old thread, but the problem that I seem to be having is whenever I try to enter in the TFTP server info, no matter what I enter in it just repeats the prompts. I am having the same problem. I have a "bricked" 121, and can console into it and can get to where try to reload the firmware, it just rejects anything I enter in for TFTP info. Any thoughts? thanks
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2438 Posts
  • 445 Reply Likes
I suspect that you are filling in incorrect or incomplete information somehow.
Can you post exactly what you are putting in?
(Edited)
Photo of James Bryant

James Bryant

  • 3 Posts
  • 0 Reply Likes
Thanks for the reply. Below is the info that I am putting in. The IP is to my local machine that I have the IP consoled into. I tried the IP of my machine and tried loopback IP just for grins. I didn't know if the brackets matter or not so tried both with or without brackets. I checked and it looks like my TFTP is setup properly, but the same thing happens even if i try to set the IP on the AP  itself. So I'm guessing maybe there is a special format this somehow has to be entered in or some step that I'm just missing? Thanks again




ar7240> set_bootparam
Change boot parameter, ENTER to skip the item
Device IP        : [0.0.0.0]
TFTP Server IP   : [10.62.22.62]
TFTP Server IP   : [10.62.22.62]
TFTP Server IP   : 10.62.22.22
TFTP Server IP   : 127.0.0.1
TFTP Server IP   : [127.0.0.1]
TFTP Server IP   : [10.62.22.62]
TFTP Server IP   : [0.0.0.0]

(Same thing occurs if i try to give ip to ap, promp just repeats)
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2438 Posts
  • 445 Reply Likes
You do not enter the values with brackets.

You do need to enter a Device IP for the AP to use, it cannot be 0.0.0.0.
Photo of James Bryant

James Bryant

  • 3 Posts
  • 0 Reply Likes
Yeah not sure what's going on. I even tried different machines just to make sure there wasn't a problem with the computer I was using. If I try to give the AP an IP no matter what I enter, it just reprompts for the same info. May end up having to do a RMA on this AP. I'm convinced that I'm missing something that is causing the TFTP setting to not stick. 
(Edited)