The OOBM interface for the controller is used for mgmt access, so that one is able to reach the controller. But controller uses non OOBM interfaces to communicate with the APs, etc and when you configuration routing protocol it is only for the non-OOBM interfaces.
------------------------------
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:
Sent: May 07, 2025 01:13 PM
From: user43512
Subject: Is it possible to setup the Mobility Conductor to manage a 7205 over the OOBM mgmt interface?
I'm new to ArubaOS and inherited a pair of 7205s and a virtual Mobility Conductor in a network that I recently took over. I noticed is that the devices are managed with the Mobility Conductor using port GE0/0/0 as opposed to the OOBM mgmt interface. Is it possible to change it to the mgmt interface? I manage most of the other network devices in the network using their OOBM was curious if it can be done with a managed 7200 appliance.
Thanks