Controllerless Networks

 View Only
last person joined: yesterday 

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

Adding IAP 505's to IAP 205 clusters. AP Image mismatch

This thread has been viewed 29 times

  • 1.  Adding IAP 505's to IAP 205 clusters. AP Image mismatch

    Posted Dec 04, 2023 12:49 PM

    Greetings,

    I have a number of IAP 205 and 305's managed by Airwave.  I'm unable to add newly purchased AP505's because they go into a boot loop.  Below is the system log of the IAP 505.

    Dec  4 16:02:44  cli[4551]: <341167> <WARN> |AP 20:9c:b4:cd:8e:54@172.22.160.8 cli|  Uplink bond0 type Ethernet, state LOAD->PROBE.
    Dec  4 16:02:44  cli[4551]: <341265> <WARN> |AP 20:9c:b4:cd:8e:54@172.22.160.8 cli|  enable ethernet uplink bond0.
    Dec  4 16:02:44  cli[4551]: <341004> <WARN> |AP 20:9c:b4:cd:8e:54@172.22.160.8 cli|  the ethernet uplink inuse in first time, get ip address.
    Dec  4 16:02:44  cli[4551]: <341167> <WARN> |AP 20:9c:b4:cd:8e:54@172.22.160.8 cli|  Uplink bond0 type Ethernet, state PROBE->UP.
    Dec  4 16:02:44  cli[4551]: <341185> <WARN> |AP 20:9c:b4:cd:8e:54@172.22.160.8 cli|  Retrieving ip address from br0, ip 172.22.160.8, mask 255.255.248.0.
    Dec  4 16:02:44  cli[4551]: <341274> <WARN> |AP 20:9c:b4:cd:8e:54@172.22.160.8 cli|  Update election ip from br0, election ip 172.22.160.8/255.255.248.0.
    Dec  4 16:02:44  cli[4551]: <341004> <WARN> |AP 20:9c:b4:cd:8e:54@172.22.160.8 cli|  build_my_ip_address: update old election ip with new ip
    Dec  4 16:02:44  cli[4551]: <341004> <WARN> |AP 20:9c:b4:cd:8e:54@172.22.160.8 cli|  build_my_ip_address: old ip and new ip same; skipping
    Dec  4 16:02:44  cli[4551]: <341006> <CRIT> |AP 20:9c:b4:cd:8e:54@172.22.160.8 cli|  Sending uplink_up msg to sapd
    Dec  4 16:02:44  cli[4551]: <341006> <CRIT> |AP 20:9c:b4:cd:8e:54@172.22.160.8 cli|  trap uplink info.
    Dec  4 16:02:44  cli[4551]: <341004> <WARN> |AP 20:9c:b4:cd:8e:54@172.22.160.8 cli|  last uplink is null, it's the first uplink, ignore this trap.
    Dec  4 16:02:44  cli[4551]: <341173> <WARN> |AP 20:9c:b4:cd:8e:54@172.22.160.8 cli|  Current uplink set to Ethernet, state UP.
    Dec  4 16:02:44  cli[4551]: <341135> <WARN> |AP 20:9c:b4:cd:8e:54@172.22.160.8 cli|  Master Changed - new 172.22.167.26 old 0.0.0.0 current swarm state 0.
    Dec  4 16:02:45  cli[4551]: <341004> <WARN> |AP 20:9c:b4:cd:8e:54@172.22.160.8 cli|  PMM: cli_process_pwr_change now swarm state is swarm_master_found
    Dec  4 16:02:45  cli[4551]: <341004> <WARN> |AP 20:9c:b4:cd:8e:54@172.22.160.8 cli|  Swarm State Change from Startup to Found
    Dec  4 16:02:45  cli[4551]: <341004> <WARN> |AP 20:9c:b4:cd:8e:54@172.22.160.8 cli|  recv non-3g setup_uplink finished from sapd
    Dec  4 16:02:46  cli[4551]: <341004> <WARN> |AP 20:9c:b4:cd:8e:54@172.22.160.8 cli|  Swarm State Change from Startup to Found
    Dec  4 16:02:48  cli[4551]: <341011> <WARN> |AP 20:9c:b4:cd:8e:54@172.22.160.8 cli|  AP image version mismatch 30 6.5.4.2-6.5.4.2_61807 64
    Dec  4 16:02:48  cli[4551]: <341004> <WARN> |AP 20:9c:b4:cd:8e:54@172.22.160.8 cli|  AP image mismatch, turn off master election
    Dec  4 16:02:48  cli[4551]: <341004> <WARN> |AP 20:9c:b4:cd:8e:54@172.22.160.8 cli|  Slave_start_sync
    Dec  4 16:02:48  cli[4551]: <341004> <WARN> |AP 20:9c:b4:cd:8e:54@172.22.160.8 cli|  Amp_send_request
    Dec  4 16:02:48  cli[4551]: <341004> <WARN> |AP 20:9c:b4:cd:8e:54@172.22.160.8 cli|  AMP is available
    Dec  4 16:02:48  cli[4551]: <341004> <WARN> |AP 20:9c:b4:cd:8e:54@172.22.160.8 cli|  awc_image_sync:
    Dec  4 16:02:48  cli[4551]: <341004> <WARN> |AP 20:9c:b4:cd:8e:54@172.22.160.8 cli|  swarm_url_valid: input url is NULL
    Dec  4 16:02:48  cli[4551]: <341004> <WARN> |AP 20:9c:b4:cd:8e:54@172.22.160.8 cli|  download_image_url: url is invalid
    Dec  4 16:02:53  nanny[4457]: <303074> <ERRS> |AP 20:9c:b4:cd:8e:54@172.22.160.8 nanny|  Process /aruba/bin/radiusd [pid 4917] died: exited with 0x1
    Dec  4 16:02:53  nanny[4457]: <303079> <ERRS> |AP 20:9c:b4:cd:8e:54@172.22.160.8 nanny|  Restarted process /aruba/bin/radiusd, new pid 5049
    Dec  4 16:02:53  nanny[4457]: <303074> <ERRS> |AP 20:9c:b4:cd:8e:54@172.22.160.8 nanny|  Process /aruba/bin/radiusd-term [pid 4918] died: exited with 0x1
    Dec  4 16:02:53  nanny[4457]: <303079> <ERRS> |AP 20:9c:b4:cd:8e:54@172.22.160.8 nanny|  Restarted process /aruba/bin/radiusd-term, new pid 5051
    Dec  4 16:02:55  cli[4551]: <341004> <WARN> |AP 20:9c:b4:cd:8e:54@172.22.160.8 cli|  PMM: cli_process_pwr_change now swarm state is swarm_not_allowed
    Dec  4 16:03:35  cli[4551]: <341004> <WARN> |AP 20:9c:b4:cd:8e:54@172.22.160.8 cli|  PMM: cli_process_pwr_change now swarm state is swarm_not_allowed

    If I understand correctly, the firmware versions must match what's offered by either Airwave or the master-elected IAP, which in my case, is an AP205.  

    Replacing all AP's at one time is not practical for us, since it would accrue downtime.  I'm trying to get a grip on my options.  

    • Remove all AP205's, and replace with AP505's, at which point one would be elected as the master IAP.
    • Upgrade the 205's to the version running on my AP505's (ArubaOS 8.7.1.6)
    • Downgrade my 505's to the version running on AP205's ( ArubaOS 6.5.4.2)

    Thoughts?

    Thanks in advance for your help.



  • 2.  RE: Adding IAP 505's to IAP 205 clusters. AP Image mismatch

    EMPLOYEE
    Posted Dec 04, 2023 02:41 PM

    The 505 is not supported on 6.x code. So, downgrading is not an option.

    The IAP-205 is not supported in 8.x and 8.7 has also reached end of development and support.

    Your end goal should be to replace the IAP-205s and also get the deployed code up to 8.10. You can bring up the 505s on a different broadcast domain so that they create their own IAP cluster.

    ------------------------------
    Josh
    ------------------------------

    Original Message


  • 3.  RE: Adding IAP 505's to IAP 205 clusters. AP Image mismatch

    EMPLOYEE
    Posted Dec 04, 2023 05:07 PM

    Also note that IAP-205s the latest firmware that they support is 6.5.x 



    ------------------------------
    If my post was useful accept solution and/or give kudos.
    Any opinions expressed here are solely my own and not necessarily that of HPE or Aruba.
    ------------------------------

    Original Message


  • 4.  RE: Adding IAP 505's to IAP 205 clusters. AP Image mismatch

    Posted Dec 05, 2023 09:20 AM

    Thanks.  Yes, my end-goal is to replace all of the AP205's in our environment with the 505's.  Unfortunately, due to the physical number and proximity of the AP's in our building, we can't simply remove all 205's and replace with 505's at once, because of the limited labor in doing so along with the downtime required.  So if I make another management VLAN for the 505's, one will become the IAP master.  Would I then be able to integrate this into Airwave along side my existing AP205's?  So essentially I would have two IAP masters; the original one for the 205's and a new elected one on the AP505 broadcast domain?


    Original Message


  • 5.  RE: Adding IAP 505's to IAP 205 clusters. AP Image mismatch

    EMPLOYEE
    Posted Dec 05, 2023 03:51 PM

    Yes, AirWave can manage multiple IAP VCs. You should use a separate group per VC. So, create a new group for your 505s.



    ------------------------------
    Josh
    ------------------------------

    Original Message