Question 1
During posture validation, I noticed that the anyconnect posture module shows posture failed due to server issue.Once i click the scan again issue got resolved and it is again communicating with the same psn and become compliant.
Has anyone else come across this issue before? If yes, what was the reason and how did you resolve it?
For this i also noticed this bug is mentioned but we are in 3.3 patch 7 and we are also using wildcard certificate with all nodes SAN entry but eventhough it looks similar if i click scan again the same node only mark the endpoint compliant but here in this bug the affected psn completely not working right. CSCvq38085
Question 2
In another case, the anyconnect agent shows compliant but in ISE it shows unknown
I also noticed that the posture report is received in ISE but ISE is not initiating COA.Once I click once i click scan again in the AnyConnect posture window, the issue gets resolved and the endpoint moves to the compliant state.
Note:We enabled posture sync also and the time is 10 seconds.
Has anyone experienced this kind of issue where ISE receives the posture report but doesn’t trigger the CoA automatically?
