Controllerless Networks

 View Only

  • 1.  Understanding firmware limitations when mixing AP models

    Posted Jan 20, 2026 10:08 AM

    Hello everyone!

    I guess i have a, for you, quite easy question. 

    In some locations we are using a controllerless setup with mixed AP models. Most of them are still running with AP224 and some AP324 and AP367.

    I am currently looking at the installed firmware to plan future updates. I see that the AP224 can only be upgraded until version 8.6.0.25.

    The other models in this system could go higher to 8.10.0.x (AP324) or 8.13.1.x (AP367).

    So, for my understanding: The conductor in this system is specifing the firmware for every AP? 

    Theoretically, when i get rid of my AP224 and replace them with newer ones, i could change the conductor to a AP324, upgrade them to 8.10.0.x, so every AP runs with this version?

    So, the oldest one defines the firmware for the whole system? Is it possible to run the newest version for each AP inside the system?

    Best regards

    Christoph



    -------------------------------------------


  • 2.  RE: Understanding firmware limitations when mixing AP models

    Posted Jan 20, 2026 02:40 PM

    Hello Christoph,

    You are correct in stating that the oldest AP model's firmware version defines the rest of the whole system. If you have a newer AP model that has a higher firmware that is not compatible for the oldest AP, that old AP will not be able to join the mesh group.

    -------------------------------------------



  • 3.  RE: Understanding firmware limitations when mixing AP models

    Posted Jan 20, 2026 03:41 PM

    The only way to support multiple versions of software with an Instant deployment is to run the APs in separate clusters.



    ------------------------------
    Carson Hulcher, ACEX#110
    ------------------------------



  • 4.  RE: Understanding firmware limitations when mixing AP models

    Posted Jan 21, 2026 02:48 AM

    Thank you two for the answers! Now i am a lot smarter.

    -------------------------------------------

    Original Message


  • 5.  RE: Understanding firmware limitations when mixing AP models

    Posted Jan 26, 2026 04:33 PM

    Also to mention, you need at least one of each model of AP to act as a seed AP for downloading the image and upgrading when joining the cluster. Hence the names added in with the versions for IAPs.



    ------------------------------
    Dustin Burns

    Lead Mobility Engineer @Worldcom Exchange, Inc.

    ACCX 1271| ACMX 509| ACSP | ACDA | MVP Guru 2022-2023
    If my post was useful accept solution and/or give kudos
    ------------------------------

    Original Message


  • 6.  RE: Understanding firmware limitations when mixing AP models

    Posted Jan 27, 2026 02:12 AM

    Exactly. So when you try to add a new AP into existing cluster and it's a new platform, you should manually upgrade it to cluster FW version. Central can upgrade  AP automatically if group FW version is set in the case that you are using it.

    Best, Gorazd



    ------------------------------
    Gorazd Kikelj
    MVP Guru 2025
    ------------------------------

    Original Message


Related Content