Hello, After reviewing the situation, we were able to rule out that the other VC was a test carried out at the time with the TAC engineers, but the commit was still causing noise. By removing the commit from the stack and removing the equipment from the Aruba central, we were able to resolve the incident.
Thank you for your comments.
-------------------------------------------
Original Message:
Sent: Feb 09, 2026 05:22 PM
From: ariyap
Subject: Delete a commit from Aruba Central
are these two VCs in the same site?
this comes down to knowing your environment. You could have one group for your IAPs but they are all in their separate L2 adjacency and they can then form an instant cluster.
------------------------------
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: Feb 06, 2026 01:36 PM
From: D.T
Subject: Delete a commit from Aruba Central
Currently, there are two VCs in the central unit and the devices appear to be out of sync (one of the VCs is not active and is not the preferred driver). Upon reviewing the device configuration audit, there are two push attempts in the configuration. I would like to know if deleting one of them will cause any problems in the network (deleting the push from the VC that is not active).
adjunt Capture:
As you can see, the first commit is from the previous VC and the second is the current one.
Has anyone had a similar experience?
I would appreciate your support.
-------------------------------------------