Thanks for the suggestion, but no joy. The config update sync'd, but the allowlist didn't. FWIW, I always assumed that config updates were separate from database updates. Not sure this confirms that assumption since nothing I've tried syncs the allowlist, but I may try it again after this is fixed to find out for sure.
Oddly, IMO anyway, I tried updating the allowlist and that didn't sync it either - even on the MDs that had been up the whole time and were in sync prior to that change. I assumed the issue was with the MD's that had been disconnected, but I'm starting to suspect the MM may not be pushing the allowlist as expected. Everything else seems to be working, and the MDs seem to be able to pull records from the MM. When APs got load balanced after connecting the MD's yesterday, the ones that were not in the allowlist on their assigned MDs got an IKE error, bootstrapped, and them connected just fine. This suggests that the MD was able to learn that AP from the MM. I've seen what happens when it can't, and the AP just reboots continuously.
Original Message:
Sent: Jul 16, 2025 06:20 AM
From: mrww
Subject: Allowlist Synchronization
When you Write memory from the MM it should push down the configs to the MDs. It might be worth making a trivial change just to force the MM to push the config to all the MDs.
Original Message:
Sent: Jul 15, 2025 05:39 PM
From: Chuck_Enfield
Subject: Allowlist Synchronization
We had a bunch of Aruba 8.10 controllers offline for over a month and when we brought them up this morning, we observed the allowlist database wasn't sync'd. Not exactly surprising, but I was a little surprised when they didn't sync later in the day. I don't believe there's a network issue preventing synchronization, and I think if I can get them to sync they'll stay that way. I tried database-synchronize, but that only seems to sync the MM's, and I also tried disabling and reenabling allowlist synchronization. Does anybody know the command to initiate synchronization?