Wireless Access

 View Only
Expand all | Collapse all

Mobility Conductor Multi-version Feature

This thread has been viewed 25 times
  • 1.  Mobility Conductor Multi-version Feature

    Posted Dec 19, 2022 07:22 AM
    Hi guys,

    One of my customers have an existing deployment which consists of 2x Mobility Conductor, 2x 7010 Mobility Controller, 32x AP (AP-207, AP-275, AP-303). All companents are running on 8.10.x, which is the max supported version for AP-207 and AP-275.

    Now, they would like to include another building to the deployment. They have bought another 7010 and AP-615s for this purpose. However, min supported version for AP-615 is 8.11.x. Meaning, there is no common version for AP-600 and AP-207 / AP-275.

    I am planning to use Multi-version feature. I will upgrade Mobility Conductors to 8.11.x, leave my existing cluster (it is located under a folder in the Managed Network main folder) on 8.10.x, and create another cluster (under another folder) with the new 7010 and AP-615s on 8.11.x.

    Has anyone used multi-version feature before? Can I use it in this way? Any point that I need to pay attention to?

    Thanks in advance.


  • 2.  RE: Mobility Conductor Multi-version Feature
    Best Answer

    Posted Dec 19, 2022 02:38 PM
    That is exactly how you should be doing it.  You don't want the AP-615s to ever discover the controller on 8.10.x, however.

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