From this post: "dirty" typically means that some ports between the AP and the controller are blocked, whether it be GRE or papi (udp 8211)."
And some troubleshooting guidance for APs with a dirty-flag in this knowledgebase article.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------
Original Message:
Sent: Feb 21, 2024 05:07 AM
From: EnzoJ
Subject: Issues with release 8.10.0.10 with dirty AP's
Upgraded a cluster of 2x 7210 controllers & virtual mobility conductor from 8.6.0.20 to 8.10.0.10 .
I upgraded already before some clients to 8.10 without any issues.
But this time is the first time to 8.10.0.10 and my AP's come up in 2SID when mine controller is cluster.
Before I hadn't any issue and everything was working fine on 8.6 .
When running on 1 controller everything is working fine. Even if I switch to the other controller.
So connection to AP's should be fine.
My cluster is L2 conntected and verified, already removed the cluster config and re-applied but without succes.
Does anyone have the same problems with version 8.10.0.10 or where must I look?
I opened already a TAC case.