Wireless Access

last person joined: yesterday 

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

6.4.2.6 upgrade, AP-103H failing upgrade

This thread has been viewed 0 times

  • 1.  6.4.2.6 upgrade, AP-103H failing upgrade

    Posted Apr 23, 2015 08:20 AM

    We just upgraded to 6.4.2.6 for the OpenSSL patches.  Everything came up except a single AP-103H that we have for testing.  I don't have the special console cable for the AP-103H, but in the short timeframes where I can get it talking to the Controller, it reports that it can't be provisioned because it's running an older (6.4.2.5) image.  It appears to be trying to upgrade, failing, and rebooting ad nausem.

     

    Did I miss that the AP-103H isn't supported on 6.4.2.6 or did this unit just bugger up at the same time we upgraded?  Anyone running 6.4.2.6 with an AP-103H ?   I did the reset procedure with the button, but I have no way of telling if it worked without the console cable.

     

    thanks

    mike

     



  • 2.  RE: 6.4.2.6 upgrade, AP-103H failing upgrade

    Posted Apr 23, 2015 08:43 AM

    Hi,

     

    AP should be able to upgrade to that code, as per my knowledge, there is no such issue with AP 103H or any other AP.

    Let us  try to know what is happening at the back end, share the AP-debug log if possible.

    For your ref:

     

    1. logging level debugging ap-debug <AP name>
    2. show log ap-debug all

     

     

    Please feel free to come back with the above output.



  • 3.  RE: 6.4.2.6 upgrade, AP-103H failing upgrade

    Posted Apr 23, 2015 09:04 AM

    The AP won't provision after being reset, thus there's no ap-debug logs..

     

    (Aruba6000-1) (config) #show log ap-debug all
    Apr 23 09:04:47 :305003:  <INFO> |stm|  AP 00:0b:86:ba:1d:b9 is down
    Apr 23 09:05:06 :305006:  <INFO> |stm|  AP 00:0b:86:ba:1d:b9 rebooted
    Apr 23 09:05:06 :305009:  <INFO> |stm|  AP 00:0b:86:ba:1d:b9 image version mismatch.
    Apr 23 09:05:20 :305003:  <INFO> |stm|  AP 00:0b:86:ba:1d:b9 is down
    Apr 23 09:05:40 :305006:  <INFO> |stm|  AP 00:0b:86:ba:1d:b9 rebooted
    Apr 23 09:05:40 :305009:  <INFO> |stm|  AP 00:0b:86:ba:1d:b9 image version mismatch.
    Apr 23 09:05:54 :305003:  <INFO> |stm|  AP 00:0b:86:ba:1d:b9 is down

     

    thanks

     



  • 4.  RE: 6.4.2.6 upgrade, AP-103H failing upgrade
    Best Answer

    Posted Apr 23, 2015 10:14 AM

    Hi,

     

    We do not have any other option other than consoling the AP and go through the Boot messages. in "show datapath session table" are able to see any traffic over FTP ( TCP -20/21) to and from the AP ? if not check whether the same port (TCP 20/21) is opened in your network or not.

     

    please feel free to come back after the above .



  • 5.  RE: 6.4.2.6 upgrade, AP-103H failing upgrade

    Posted Apr 23, 2015 02:18 PM

    Thanks, this was a false alarm.  The Security Team implemented a new firewall rule that blocked PAPI packets, and it didn't show up until this one AP tried to reprovision after the ArubaOS upgrade..

     

    thanks

    mike