Wireless Access

 View Only
last person joined: 18 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

This thread has been viewed 156 times
  • 1.  After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    Posted Apr 09, 2023 03:37 AM

    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
    ------------------------------


  • 2.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    Posted Apr 10, 2023 10:10 AM

    Looks like TAC time.

    Best, Gorazd



    ------------------------------
    Gorazd Kikelj
    MVP Expert 2023
    ------------------------------



  • 3.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    Posted Apr 10, 2023 10:15 AM

    On going ! L

     

     

    Steinar






  • 4.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    Posted Apr 10, 2023 12:12 PM
    • I dowgraded to  8.11.0.1_85785, and

      I advise to pull back the 8.11.1.0 version, immediately !!!!!!!!


    ------------------------------
    Steinar
    ------------------------------



  • 5.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    Posted Aug 20, 2023 04:41 PM

    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
    ------------------------------



  • 6.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    Posted Aug 21, 2023 12:16 PM

    Hello, 

    I unfortunately don't have a solution to your issues, but I was recently recommended to upgrade to 8.11.1.0 due to some weird error messages I was receiving on our controllers that would supposedly resolve the issues. I'm currently running on 8.11.0.1 SSR_85785 but now I'm hesitant to upgrade.

    Were you recommended to upgrade to 8.11.1.X from TAC for any other issue?




  • 7.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    Posted Aug 21, 2023 03:44 PM

    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.
    ------------------------------



  • 8.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    Posted Aug 22, 2023 11:50 AM

    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.




  • 9.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    EMPLOYEE
    Posted Aug 23, 2023 04:50 AM

    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.
    ------------------------------



  • 10.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    Posted Aug 24, 2023 12:12 PM

    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.




  • 11.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    EMPLOYEE
    Posted Aug 25, 2023 06:38 AM

    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.



    ------------------------------
    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.
    ------------------------------



  • 12.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    Posted Sep 16, 2023 11:38 AM

    Same here. We upgraded our 8.10 instant clusters from 8.10 to 8.11 because of new AP-615 access points. Affected access points are mostly AP-555 and AP-635. The problems occur with different switches:

    • HP 5400r zl2
    • HP 5130 HI
    • HP 5510 HI




  • 13.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    Posted Sep 17, 2023 07:33 AM

    Yes, thanks, 
    and it keeps going on and on, and the error is moved forward all the way trough:
    8.11.1.0
    8.11.1.1 
    8.11.1.2
    and up to now 8.11.2.0.
    It is unclear why the fine core of Aruba engineers is not engaged into this,?
    Aruba TAC is not engaged in a proper manner, making this still unresolved.
    The case has not even been giving its Defect ID !



    ------------------------------
    Steinar
    ------------------------------



  • 14.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    EMPLOYEE
    Posted Sep 17, 2023 05:45 PM
    • Have you tried to escalate the case?
    • Are you focusing on a single access point (the problems could be different for each access point).
    • Have they established any issue, as of yet? (even if it is not solved, they should be able to identify where it is failing.  You might have to connect via bluetooth or wifi console to get the logs before it connects to the network.


    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
    ------------------------------



  • 15.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    Posted Oct 05, 2023 11:12 AM
    Same error yesterday in version 8.11.0.1, with a first new AP 615 where previously we only had 305.
     
    Immediately everything was fine, then in the morning the 5GHz radio was off.
     
    After a full reset of the AP, this morning the 2.4 GHz radio was off, today we performed another full reset and set the HP 5130 HI switch port to high PoE priority, let's wait to see what will happen tomorrow.

    Logs from conytroller:

    Oct  4 07:04:52 2023  sapd[6206]: <326268> <ERRS> |AP APA-XX09-ST315@172.30.130.100 sapd|  An internal system error has occurred at file amon.c function amon_get_ant_gain line 4223 error invalid band 2.
    Oct  4 07:05:55 2023  sapd[6206]: <326268> <ERRS> |AP APA-XX09-ST315@172.30.130.100 sapd|  An internal system error has occurred at file amon.c function amon_get_ant_gain line 4223 error invalid band 2.
    Oct  4 07:06:57 2023  sapd[6206]: <326268> <ERRS> |AP APA-XX09-ST315@172.30.130.100 sapd|  An internal system error has occurred at file amon.c function amon_get_ant_gain line 4223 error invalid band 2.
    Oct  4 07:08:00 2023  sapd[6206]: <326268> <ERRS> |AP APA-XX09-ST315@172.30.130.100 sapd|  An internal system error has occurred at file amon.c function amon_get_ant_gain line 4223 error invalid band 2.
    Oct  4 07:09:02 2023  sapd[6206]: <326268> <ERRS> |AP APA-XX09-ST315@172.30.130.100 sapd|  An internal system error has occurred at file amon.c function amon_get_ant_gain line 4223 error invalid band 2.
    Oct  4 07:10:05 2023  sapd[6206]: <326268> <ERRS> |AP APA-XX09-ST315@172.30.130.100 sapd|  An internal system error has occurred at file amon.c function amon_get_ant_gain line 4223 error invalid band 2.
    Oct  4 07:11:07 2023  sapd[6206]: <326268> <ERRS> |AP APA-XX09-ST315@172.30.130.100 sapd|  An internal system error has occurred at file amon.c function amon_get_ant_gain line 4223 error invalid band 2.
    Oct  4 07:12:10 2023  sapd[6206]: <326268> <ERRS> |AP APA-XX09-ST315@172.30.130.100 sapd|  An internal system error has occurred at file amon.c function amon_get_ant_gain line 4223 error invalid band 2.




  • 16.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    EMPLOYEE
    Posted Oct 05, 2023 11:54 AM

    What switches are you powering these access points with?  The access points require class4 802.11at power:  

    EDIT: https://www.arubanetworks.com/assets/ds/DS_AP610Series.pdf



    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
    ------------------------------



  • 17.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    Posted Oct 06, 2023 04:23 AM

    Yes, HPE 5130-HI JH326A

    IEEE 802.3at Power over Ethernet (PoE+) support simplifies deployment and dramatically reduces installation costs by helping to eliminate the time and cost involved in supplying local power at each access point location

     



  • 18.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    EMPLOYEE
    Posted Oct 06, 2023 05:36 AM

    Did you try downgrading?  Why did you upgrade ?  



    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
    ------------------------------



  • 19.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    Posted Oct 06, 2023 05:41 AM

    We have updated the entire infrastructure to support 615 APs that require 8.11.all done with TAC support.




  • 20.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    EMPLOYEE
    Posted Oct 06, 2023 05:47 AM

    Please engage TAC to troubleshoot your issue.  If you find that you are not getting anywhere, please escalate.  Report back on this thread about your progress.

    The title of this thread is a person who updated from 8.11.0.1 to 8.11.1.0 and has access points down.  You might want to open your own thread with your specific experience so that things do not get confused.



    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
    ------------------------------



  • 21.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    Posted Oct 06, 2023 10:46 AM

    Endless attempts have been made by TAC,

    with ditto log extraction to figure this out for the past 6 months

    with no success, we are still running on 8.11.0.1



    ------------------------------
    Steinar
    ------------------------------



  • 22.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    EMPLOYEE
    Posted Oct 06, 2023 10:51 AM

    @Steinar Grande Have you tried single-connecting the access points that seem to be having problems?  I have a colleague who had a similar issue with a customer and it was due to asymetric switching (not routing, because it had to do with their long cam timer on their switch).



    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
    ------------------------------



  • 23.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    Posted Oct 06, 2023 11:02 AM

    Yes the "first" time, but after the upgrade(no change),

    not tested dissolved the lacp, and then upgrade,

    Be awere it only affecting the  5%, at about 5-10 AP's a time

    for our 100++ ..ich and incude both 2930F, and 6300M switches.. From PoE class 4 to 6 



    ------------------------------
    Steinar
    ------------------------------



  • 24.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    Posted Oct 06, 2023 11:09 AM

    @cjoseph;

     However may you please elaborate some more on long cam timer ?



    ------------------------------
    Steinar
    ------------------------------



  • 25.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    EMPLOYEE
    Posted Oct 06, 2023 11:14 AM

    I apologize.  It was a short cam timer where the switch would not be aware of where to send a frame to an AP, so it would flood the frame and the AP would get a frame twice.  This is a corner case.  Either way, if all of those access points are dual connected, disabling one interface should be part of your troubleshooting.  I am just guessing and this goes along with the principle to simplify as much as possible until the problem is isolated.



    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
    ------------------------------



  • 26.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    Posted Oct 06, 2023 11:21 AM

    Yes, I completely agree, but it will only be a workaround, and only masks the real error..

    and I will never get both interfaces back on :(



    ------------------------------
    Steinar
    ------------------------------



  • 27.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    EMPLOYEE
    Posted Oct 06, 2023 11:25 AM

    You can do this for every device that has the issue and get full functionality of access points that are not working.  You can leave one in that state to determine what is wrong and recover 99% of your services while you do that.



    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
    ------------------------------



  • 28.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    Posted Oct 06, 2023 11:32 AM

    the problem is that it fluctuate, one minute there is one dozen,

    the next minute there is another, and so it goes on.

    There has to be all or none !..  lot of work, .

    And then what?, the upgrade succeeded!, 
    and then, how to pursue an error witch is no more there ?


    ------------------------------
    Steinar
    ------------------------------



  • 29.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    EMPLOYEE
    Posted Oct 06, 2023 11:35 AM

    If the problem only happened when you upgraded, I would downgrade.  If it still happens, the problem is not the code, it could have been changes that were made prior to the upgrade.



    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
    ------------------------------



  • 30.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    Posted Oct 06, 2023 11:38 AM

    It has been at least 10 up/dowgrades !

    Se post nr4.



    ------------------------------
    Steinar
    ------------------------------



  • 31.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    EMPLOYEE
    Posted Oct 06, 2023 11:38 AM

    Question:  Have you enabled SSH on all access points so that TAC can SSH into them, even if they don't contact the controller to collect information?



    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
    ------------------------------



  • 32.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    Posted Oct 06, 2023 11:40 AM

    TAC has have any access they have required for 6 month



    ------------------------------
    Steinar
    ------------------------------



  • 33.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    EMPLOYEE
    Posted Oct 06, 2023 11:51 AM

    I would look back 6 months and see what changes were made to the network to determine what combination of changes could have caused this.



    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
    ------------------------------



  • 34.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    EMPLOYEE
    Posted Oct 06, 2023 11:55 AM

    Quite frankly, if an access point loses connectivity with the controller, the only conclusive way to find out what is wrong with it is to SSH into it (or console).  Please check to make sure SSH was enabled on those access points so that TAC can get what they need.  If it is not enabled, please recommend that to them, because they can only get so far on your network with the information that you give them.  Information collection is key to get to the bottom of this.



    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
    ------------------------------



  • 35.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    Posted Oct 06, 2023 12:05 PM

    Please feel free to look at TAC works hundreds of posts; nested backword from

    Case# 5375652344 to 5372658393 starting at may 2. in the portal. With ditto uploaded logs.



    ------------------------------
    Steinar
    ------------------------------



  • 36.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    Posted Oct 07, 2023 12:12 PM
    This is my thread.

    Med vennlig hilsen
       Steinar Grande





  • 37.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    EMPLOYEE
    Posted Oct 07, 2023 12:19 PM



    That was for @robertoselmi






  • 38.  RE: After upgraded from 8.11.0.1 SSR_85785 to 8.11.1.0 SSR_86591 AP reports Down

    Posted Oct 06, 2023 01:38 PM

    - HP 5400r zl2 supports IEEE 802.3at
    - HP 5130 HI supports IEEE 802.3at 
    - HP 5510 HI supports IEEE 802.3at