AP121's stuck at HiveOS 6.4r1d

[netadmin21]

I have a HiveManager Connect account and have twelve AP121s. Five of them are stuck on HiveOS 6.4r1d. When I upgrade HiveOS it displays a "Device Update Failed" regardless of HiveOS version I choose.

Can someone please point me to the right direction please? Is there a way to get the appropriate .img file so I can do a manual update of the firmware?

Any help greatly appreciated.

[jerrygen]

The first thing I’d check is whether those five AP121s have enough free space and are still properly communicating with HiveManager. If they consistently fail every HiveOS upgrade while the other seven update normally, I’d also compare their device status, connectivity, and current configuration with a working AP121. https://minecraftofficials.com/

For a manual upgrade, I wouldn’t use an .img file from an unofficial source because the firmware needs to match the AP121 and the HiveOS release. Since these are stuck on 6.4r1d, opening a support case with Extreme/Aerohive would be the safest route; they can provide the correct recovery image and instructions if a manual recovery is required.

[jerrygen]

This issue usually happens when the AP121s are running an older HiveOS version that can’t properly communicate with the newer HiveManager update process. The best way to fix it is to manually upgrade the firmware using the CLI. Connect to the AP via SSH or console, log in, and use the command upgrade ftp://<your_ftp_server>/<firmware_file.img> or upgrade tftp://<server>/<firmware_file.img>. Make sure you’re using a HiveOS version that’s compatible with AP121—usually something like 6.5r3 or 6.6r2 works fine.

You can request the correct .img firmware file from Extreme Networks support or find it in their download portal under the legacy Aerohive section. After uploading and flashing the image manually, reboot the AP and it should reconnect to minecraft apk son sürüm. Once it’s back online, you can continue upgrading from there through the normal process.

[ellsuyina]

The client and server don't support a common SSL protocol version or cipher suite, and due to that, you are facing the error issue ERR_SSL_VERSION_OR_CIPHER_MISMATCH, so for the solution, you can check out the helpful guide at:- https://certera.com/kb/how-to-fix-the-err_ssl_version_or_cipher_mismatch-error/. I found these resources helpful and able to solve the issue quickly. 

[netadmin21]

Thanks for the help. Got 'em going.