Hi chuffinwifi,
One possible approach is to create a new AP management VLAN for the access points you want to connect to a different VMC gateway, and configure discovery using ADP layer-2 or DHCP option 43, instead of DNS. Keep in mind that the access points will not be in the same roaming domain, which could lead to roaming issues.
Depending on the number of access points and your specific needs, there may be other design options available, such as using Aruba Central, with or without on-premise gateways. My advice is to discuss the possibilities with your local Aruba Partner.
------------------------------
Marcel Koedijk | MVP Expert 2024 | ACEP | ACMP | ACCP | ACDP | Ekahau ECSE | Not an HPE Employee | Opinions are my own
------------------------------
Original Message:
Sent: Sep 09, 2024 08:02 AM
From: chuffinwifi
Subject: Two VMCs
If we have a single standalone VMC currently in place running 8.10, is it possible to have a second VMC running 8.12 with no redundancy/communication between them?
The 8.10 has AP325s connected which are not support in 8.11+.
The idea is to build a second VMC for all new offices where they will use newer AP models. Slowly migrate off the 8.10 VMC as APs are replaced.
At present AP discovery uses a central DNS aruba-conductor record which might complicate this method, possibly means an office needing to move to the 8.12 VMC has to use local DHCP settings instead as they are higher in the discovery order process.
Is there a better way of achieving this?