02-06-2020 06:11 PM
Hello
ISE 2.2 patch 8
Anyone seen this before? It's happening for EAP-PEAP Wireless authentications (Cisco 8510 Flex 8.3.143.0).
The majority of the time the clients are working and then other times the same client reports failed auth. The wireless client is still running the same code and with the same config. Not sure what triggers this.
It would be nice to know WHAT EXACTLY (and at what stage of the processing) is causing ISE to report this exact error - e.g. is it bad code in the client?? We see a lot of this with a particular wireless device:
In my experience we see other errors when wireless clients "drop off the wifi" during an EAP negotiation - we then usually see re-tries and this error - this would tell me that the client was interrupted during an EAP negotiation.
12916 Expected TLS acknowledge for TLS fragment but received another message