Controllerless Networks

 View Only
last person joined: 19 hours ago 

Aruba Instant Wi-Fi: Meet the controllerless Wi-Fi solution that's easy to set-up, is loaded with security and smarts, and won't break your budget.
Expand all | Collapse all

APs not coming up after update

This thread has been viewed 42 times
  • 1.  APs not coming up after update

    Posted Aug 15, 2022 04:38 PM
    I was updating a cluster consisting of three 325's and five 535's from firmware 8.7 to 8.9 using the web interface. After a reboot I also updated the regulatory version.

    Not all APs came back after the update even after waiting about half an hour, so I restarted the ones that were up. After this some more APs came online, but not all and not the same ones as before. Six of the eight were up.

    I rebooted them a second time and this time only four out of eight came up. Any ideas what to do or am I facing a wipe and restore?


  • 2.  RE: APs not coming up after update

    EMPLOYEE
    Posted Aug 15, 2022 05:33 PM

    See if you can ping/ssh into the aps that did not come up.  Login to them and type "show log system"



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



  • 3.  RE: APs not coming up after update

    Posted Aug 15, 2022 06:26 PM
    I managed to login to three APs, one doesn't seem to even get an IP address.

    Here are the system logs for the three, with some name and address info redacted:
    https://pastebin.com/PKNrrR8r
    https://pastebin.com/rsRzvqyA
    https://pastebin.com/PyayJV3c

    Looks like they had some trouble with the DRT update. I was able to get another one back up by shutting down other ones. So seems like there's some conflict.


  • 4.  RE: APs not coming up after update
    Best Answer

    EMPLOYEE
    Posted Aug 15, 2022 06:35 PM
    Make sure you only have a single ethernet, ethernet 0 plugged in, at a time.

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



  • 5.  RE: APs not coming up after update

    Posted Aug 15, 2022 06:40 PM
    All but one are connected to LACP trunk on a 2930 switch. I'll try to disable the other port.


  • 6.  RE: APs not coming up after update

    Posted Aug 15, 2022 07:22 PM
    @cjoseph Thanks for the tip, I got them back up and running by disabling eth1.

    Am I running an unsupported configuration or do I have a faulty configuration? They have been running without issues for a long time, but I do remember having a similar problem the last time the system was updated. Even now half of the APs are still unchanged with both ports enabled and LACP configured on the switch side and they came back up normally after the update. So I'm a bit confused what caused the issue and how to avoid it in the future, while hopefully keeping redundancy and load balancing.


  • 7.  RE: APs not coming up after update

    Posted Sep 08, 2022 05:05 AM
    Are there any references about the correct LACP configuration between Aruba APs and switches to avoid this issue everytime the Instant cluster is updated?


  • 8.  RE: APs not coming up after update

    EMPLOYEE
    Posted Sep 09, 2022 06:54 AM
    I don't see it in the Aruba Instant VRD. Personally I would avoid multi-homing of Instant APs, unless absolutely required.

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



  • 9.  RE: APs not coming up after update

    Posted Sep 09, 2022 07:26 AM
    I found this: https://www.arubanetworks.com/techdocs/Instant_85_WebHelp/Content/instant-ug/wired-port-prof/lacp-support.htm

    It indicates that it's supposed to be supported by default without any configuration needed on the AP side. The example of the switch configuration seems to be from older ArubaOS but looks like a very basic active LACP configuration that should be easily achieved with ProVision CLI.

    Mostly it seems to work fine, it's just during updates that is seems to become a problem. Would be nice to have the extra bandwidth and redundancy since the APs are connected to stacked switches. I guess I just have to make a note of it to disable it during updates.


  • 10.  RE: APs not coming up after update

    EMPLOYEE
    Posted Sep 09, 2022 07:32 AM
    It is definitely supposed to work.  If you can, please open a support case. It is possible that there is an untested scenario causing your issue

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



  • 11.  RE: APs not coming up after update

    Posted Sep 12, 2022 03:43 PM
    I realized that the AP setting for eth1 was "platform default" as I didn't know it might need a change. I still don't as it looks like the LACP bond works somewhat even without changing it and the documentation says LACP should be automatic. But I now changed it to "uplink" on all the APs and at least after a regular reboot it seems to work better.

    I noticed that enabling the eth1 port for one AP seemed to affect another AP bringing it down from the web management view. So perhaps there actually was some kind of conflict or loop in the configuration connection to the swarm which the setting change fixed.

    I still have to test with a firmware update. I'm now running 8.9.0.2. The web UI says "image_check_internal error 001 code 2" when checking for newer version, which as I understand means that a newer version isn't available. I know there's 8.9.0.3 but is it still so new that it hasn't been published to the automatic version check yet?

    Edit: Some of the AP names also included a special character. I removed them just in case they were causing issues.