I'm not aware of a specific bug in this version, and I would expect that for whatever reason your client can't communicate to ClearPass if the agent thinks it's healthy but it's not reported to ClearPass. The client needs to communicate to ClearPass in order to report it's status, so clients in quarantine need to have access to ClearPass.
Your Aruba partner or Aruba TAC can assist checking your workflow and see where posting of the updated posture status goes wrong.
ClearPass 6.10 is end of support, and you should consider upgrading to 6.11/6.12. Unlikely to be related to what you see, but important to know, I'd say.
------------------------------
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: Jul 20, 2024 03:29 PM
From: Diax
Subject: Posturing problem
Dear Community
I'm using Clearpass 6.10.8 and I have posturing policies for both MacOS and Windows. Occasionally, macOS users encounter issues where they get stuck in the Quarantine network due to the Clearpass server not showing a HEALTHY status for that client. Monitoring logs indicate the posture status as UNKNOWN. However, OnGuard agent health logs report that everything is fine with a HEALTHY status. Has anyone else experienced this issue, or could it potentially be a bug in this version?