Looks like 8.11.1.2 is even out.... it probably won't hurt to be on the latest in the release train in the case of relatively new APs.
If you can give that a try, you're also in better shape with TAC as you already are at the latest release and can't upgrade further.
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check
for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
Original Message:
Sent: Aug 24, 2023 12:12 PM
From: atran004
Subject: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down
I forgot to mention, these are actually AP655, but we're not currently broadcasting on the 6GHz band that I'm aware of so maybe that's why it doesn't see band 2? The "Allow 6GHz Band" checkbox is unchecked on the Virtual AP profile.
I could maybe try poking around to see about disabling the 6GHz radio and disable band 2 on 6GHz to see if that resolves the problem.
I worked with TAC on the error message and their suggestion was to upgrade to 8.11.1.1.
Original Message:
Sent: Aug 23, 2023 04:49 AM
From: Herman Robers
Subject: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down
My guess would be that the AP535 are configured for 6GHz (band 2), which they don't have a radio for.
Best would be to work with TAC on this as more direct access to the logs and commands would help to effectively find the resolution.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
Original Message:
Sent: Aug 22, 2023 11:50 AM
From: atran004
Subject: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down
Here's a section of the errorlogs and system logs. Both commands are just repeats of this but with different AP's for all 150 lines on both show commands. It shows up at multiple sites so I'm wondering if it's actually a mobility conductor configuration somewhere.
Aug 22 11:42:09 2023 :326268: <ERRS> |AP west-ap05@10.15.251.15 sapd| An internal system error has occurred at file amon.c function amon_get_ant_gain line 4223 error invalid band 2.
Aug 22 11:42:16 2023 :326268: <ERRS> |AP mdf-ap02@10.15.251.60 sapd| An internal system error has occurred at file amon.c function amon_get_ant_gain line 4223 error invalid band 2.
Aug 22 11:42:34 2023 :326268: <ERRS> |AP east-ap01@10.15.251.45 sapd| An internal system error has occurred at file amon.c function amon_get_ant_gain line 4223 error invalid band 2.
Aug 22 11:42:36 2023 :326268: <ERRS> |AP mdf-ap04@10.15.251.24 sapd| An internal system error has occurred at file amon.c function amon_get_ant_gain line 4223 error invalid band 2.
Original Message:
Sent: Aug 21, 2023 03:43 PM
From: kdisc98
Subject: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down
May you share with us.
show log errorlog 150
show log system 150
------------------------------
(*) If i helped you , Please do kudos me as a thank you (*)
Aruba AirHeads - Because mobility matters.
Original Message:
Sent: Aug 20, 2023 04:40 PM
From: Steinar Grande
Subject: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down
After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.2_87606 AP reports Down
same behavior as in the previous two attempts despite the fix,:
Table 6: Resolved Issues in ArubaOS 8.11.1.2
AOS-243042
AOS-245983
AOS-245834
AOS-244676
AOS-243499
Some access points running ArubaOS 8.11.1.0 or later versions
crashed and rebooted unexpectedly. The crash logs listed the
reason for the error as BadPtr: 00000050 PC: anul_aon_flow_
ageout+0xac/0x180 [anul] Warm-reset.
The fix ensures APs work as expected.
Table 6: Resolved Issues in ArubaOS 8.11.1.2
Please anyone, TAC has been unresponsive for 6 month
------------------------------
Steinar
Original Message:
Sent: Apr 10, 2023 12:11 PM
From: Steinar Grande
Subject: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down
- I dowgraded to 8.11.0.1_85785, and
I advise to pull back the 8.11.1.0 version, immediately !!!!!!!!
------------------------------
Steinar
Original Message:
Sent: Apr 09, 2023 03:36 AM
From: Steinar Grande
Subject: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down
AP-535 & 655 with dual interface and LACP, randomly show as Down,
and do not report LLDP Systemname/Negibor name back to switch,
both in eg. 2930F and 6300 switches.in a dual Conductor/Controller env.
In 2930 identefiing Ap's is in use :device-profile name "default-ap-profile"
in 6300 port-access device-profile default-ap-profile
Anyone ?
------------------------------
Steinar
------------------------------