Wireless Access

last person joined: 22 hours ago 

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

Upgraded to 6.4.2.10 from 6.3.1.2 and all AP's show Down

This thread has been viewed 0 times

  • 1.  Upgraded to 6.4.2.10 from 6.3.1.2 and all AP's show Down

    Posted Aug 15, 2015 04:06 PM

    I recently Upgraded our 3600 Controller to 6.4.2.10 from 6.3.1.2 and after rebooting into the upgraded partition all of our AP's show down and never reconnect (101 AP's). I'm able to reboot the controller and revert to the 6.3.1.2 partition and all of the AP's come back up just fine.

     

    Has anyone else had this problem?



  • 2.  RE: Upgraded to 6.4.2.10 from 6.3.1.2 and all AP's show Down

    EMPLOYEE
    Posted Aug 15, 2015 04:08 PM
    What model are your APs



    Sent from Mail for Windows 10


  • 3.  RE: Upgraded to 6.4.2.10 from 6.3.1.2 and all AP's show Down

    Posted Aug 15, 2015 04:11 PM

    Sorry. We've got 105's.



  • 4.  RE: Upgraded to 6.4.2.10 from 6.3.1.2 and all AP's show Down

    EMPLOYEE
    Posted Aug 15, 2015 05:07 PM
    When you upgrade type "show log system 50" to see what could be going wrong.


  • 5.  RE: Upgraded to 6.4.2.10 from 6.3.1.2 and all AP's show Down

    Posted Aug 15, 2015 06:27 PM

    I will have to wait until I can boot into the updated partition to view those logs (unless you can share a way to do that while the 6.3 partition is active). 

     

    School started earlier this week so I haven't had any time to dedicate to this until today. I'm not on site so I can't access an AP to console into it. I will do so this Monday and see if I can find anything useful.



  • 6.  RE: Upgraded to 6.4.2.10 from 6.3.1.2 and all AP's show Down

    EMPLOYEE
    Posted Aug 17, 2015 12:13 AM

    hi Mark

    the logs will be lost when you downgraded - no way to retrieve them now. What country code is configured in the ap regulatory domain profile? At least we can check something didnt happen to the regulatory settings which would manifest as all APs down.

    regards

    -jeff



  • 7.  RE: Upgraded to 6.4.2.10 from 6.3.1.2 and all AP's show Down

    EMPLOYEE
    Posted Aug 17, 2015 11:28 AM

    turns out there is a bug in 6.4.2.9 + 6.4.2.10 + 6.3.1.17 that may have also caused this (affects ap 1xx models, it is a slow network buffer leak on the APs caused by client match. Eventually the AP becomes non responsive - it may manifest as all APs down)

     

    Is there any possibility the APs were up for some time and then became down ? At any rate, please dont re-upgrade to 6.4.2.x until 6.4.2.11 is out (soon)

     

    regards

    -jeff

     



  • 8.  RE: Upgraded to 6.4.2.10 from 6.3.1.2 and all AP's show Down

    Posted Aug 15, 2015 05:08 PM

    I upgraded my lab controller (600 series) to 6.4.10 and faced no issue. I also have AP-105 in my setup. Have u connected to the AP console and found anything ambgious?

    @mbayhylle wrote:

    Sorry. We've got 105's.

     



  • 9.  RE: Upgraded to 6.4.2.10 from 6.3.1.2 and all AP's show Down

    Posted Aug 19, 2015 08:51 AM

    Hello!

     

    Might be unrelated, but there was an old bug re-introduced to 6.4.3.3 (and possibly late 6.4.2.x releases)  that prevents the licenses from being accepted... We upgraded to 6.4.3.3 from a previous 6.4.3.x release and was unable to get the AP's up again. Some quick work with Aruba TAC and they added EVAL licences which caused the AP's to start popping back in. The assumption now is that it's related to Centralized licensing, and that disabling and re-enabling this would solve the issue on the current release.. We haven't been able to test the solution yet tho.

     

     



  • 10.  RE: Upgraded to 6.4.2.10 from 6.3.1.2 and all AP's show Down

    Posted Aug 25, 2015 12:27 PM

    All,

     

    We installed a 7205 alongside our 3600 in a Master/Local configuration. In the process we upgraded to 6.4.3.3 and all APs have been reporting without error.

     

    Thanks for all of the input.