6.5 Honolulu Bootloader password

  • 1
  • Question
  • Updated 2 years ago
I have arround 15AP121 stuck on boot with the message "Bad data CRC". Normaly, when it happened to me I booted from a tftp server from the bootloader but since I've upgrade the APs to the 6.5 version the default password is not working.
Anybody knows the new bootloader password?
Photo of Julián García-Sotoca Pascual

Julián García-Sotoca Pascual

  • 19 Posts
  • 0 Reply Likes

Posted 2 years ago

  • 1
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Hi Julián,

I am curious how this situation has occurred on 15 APs. Can you share any more light on it?

Originally, the AP121 only had a single HiveOS image and if an AP of this model lost power while it was being updated, the boot loader would have to be used to recover it.

On older HiveOS versions, the output of  "show version detail" would therefore show only a single image.

However, we have since switched to a dual HiveOS image on the AP121 so that (in the more recent HiveOS versions where the boot loader is now intentionally inaccessible), this type of corruption should not be occurring on this scale.

Were you updating when this occured? If so, from what version to what version?

Thanks,

Nick
(Edited)
Photo of Julián García-Sotoca Pascual

Julián García-Sotoca Pascual

  • 19 Posts
  • 0 Reply Likes
It happened to me several times. I have some HP switches whose PSU fails randomly and in a few seconds it recovers. It makes the APs to reboot, and when they are rebooting the PSU fails another time. I think that in that point is when I get the corruption. You can see the sequence on my switch logs:
Oct 26 07:03:07 2016 %%10DEVM/2/POWER_FAILED(l): Power PSU1 failed.
Oct 26 07:03:12 2016 %%10DEVM/5/POWER_RECOVERED(l): Power PSU1 recovered.
Oct 26 07:10:16 2016 %%10DEVM/2/POWER_FAILED(l): Power PSU1 failed.
Oct 26 07:10:25 2016 %%10DEVM/5/POWER_RECOVERED(l): Power PSU1 recovered.
Oct 26 07:20:41 2016 %%10DEVM/2/POWER_FAILED(l): Power PSU1 failed.
Oct 26 07:55:35 2016 %%10DEVM/5/POWER_RECOVERED(l): Power PSU1 recovered.
Oct 26 07:55:39 2016 %%10DEVM/2/POWER_FAILED(l): Power PSU1 failed.
Oct 26 07:59:37 2016 %%10DEVM/5/POWER_RECOVERED(l): Power PSU1 recovered.
Oct 26 07:59:41 2016 %%10DEVM/2/POWER_FAILED(l): Power PSU1 failed.
Oct 26 07:59:42 2016 %%10DEVM/5/POWER_RECOVERED(l): Power PSU1 recovered.
Oct 26 07:59:48 2016 %%10DEVM/2/POWER_FAILED(l): Power PSU1 failed.
Oct 26 07:59:52 2016 %%10DEVM/5/POWER_RECOVERED(l): Power PSU1 recovered.
Oct 26 07:59:56 2016 %%10DEVM/2/POWER_FAILED(l): Power PSU1 failed.
Oct 26 07:59:58 2016 %%10DEVM/5/POWER_RECOVERED(l): Power PSU1 recovered.
Oct 26 08:00:15 2016 %%10DEVM/2/POWER_FAILED(l): Power PSU1 failed.
Oct 26 08:00:41 2016 %%10DEVM/5/POWER_RECOVERED(l): Power PSU1 recovered.
Oct 26 08:00:45 2016 %%10DEVM/2/POWER_FAILED(l): Power PSU1 failed.
Oct 26 08:13:41 2016 %%10DEVM/2/POWER_FAILED(l): Power PSU1 failed.
Oct 26 08:17:40 2016 %%10DEVM/5/POWER_RECOVERED(l): Power PSU1 recovered.
Oct 26 08:17:44 2016 %%10DEVM/2/POWER_FAILED(l): Power PSU1 failed.
Oct 26 08:22:19 2016 %%10DEVM/5/POWER_RECOVERED(l): Power PSU1 recovered.
Oct 26 08:22:23 2016 %%10DEVM/2/POWER_FAILED(l): Power PSU1 failed.
Oct 26 08:22:48 2016 %%10DEVM/5/POWER_RECOVERED(l): Power PSU1 recovered.
Oct 26 08:22:53 2016 %%10DEVM/2/POWER_FAILED(l): Power PSU1 failed.
Oct 26 08:24:43 2016 %%10DEVM/5/POWER_RECOVERED(l): Power PSU1 recovered.
Oct 26 08:24:47 2016 %%10DEVM/2/POWER_FAILED(l): Power PSU1 failed.
Oct 26 08:25:18 2016 %%10DEVM/5/POWER_RECOVERED(l): Power PSU1 recovered.
Oct 26 08:25:25 2016 %%10DEVM/2/POWER_FAILED(l): Power PSU1 failed.
Oct 26 08:25:30 2016 %%10DEVM/5/POWER_RECOVERED(l): Power PSU1 recovered.
Oct 26 08:25:35 2016 %%10DEVM/2/POWER_FAILED(l): Power PSU1 failed.
Oct 26 08:25:51 2016 %%10DEVM/5/POWER_RECOVERED(l): Power PSU1 recovered.
Oct 26 08:28:02 2016 %%10DEVM/2/POWER_FAILED(l): Power PSU1 failed.
Oct 26 08:28:03 2016 %%10DEVM/5/POWER_RECOVERED(l): Power PSU1 recovered.
Oct 26 08:28:51 2016 %%10DEVM/2/POWER_FAILED(l): Power PSU1 failed.
Oct 26 08:28:51 2016 %%10DEVM/5/POWER_RECOVERED(l): Power PSU1 recovered.
Oct 26 08:28:55 2016 %%10DEVM/2/POWER_FAILED(l): Power PSU1 failed.
Oct 26 08:28:56 2016 %%10DEVM/5/POWER_RECOVERED(l): Power PSU1 recovered.
Oct 26 08:29:07 2016 %%10DEVM/2/POWER_FAILED(l): Power PSU1 failed.
Oct 26 08:29:10 2016 %%10DEVM/5/POWER_RECOVERED(l): Power PSU1 recovered.
Oct 26 08:29:23 2016 %%10DEVM/2/POWER_FAILED(l): Power PSU1 failed.
Oct 26 08:29:25 2016 %%10DEVM/5/POWER_RECOVERED(l): Power PSU1 recovered.
On that switch I also have a AP1130 that was on 6.8 before the failure and after that it booted on 6.6. I suppose that it boots from a backup image.
As I said before, it happened to me several times and it's faster to flash an image again that request an RMA.
Photo of Bill W.

Bill W.

  • 222 Posts
  • 35 Reply Likes
Unfortunately, it seems they have changed the password and are not giving it out. This has been discussed previously:
https://community.aerohive.com/aerohive/topics/what-is-the-bootloader-password-for-hiveos-6-5r3-honolulu-2530

And I agree with you, flashing an image has saved me plenty of RMA requests over the years.  Hopefully they give it out one day.
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Hi Bill,

Hmm, I think we more need to investigate what is happening here that is allowing this type of corruption to occur with dual images, and if there is anything that we can do to mitigate that.

Thanks,

Nick
(Edited)