Errors from iOS 13 beta testing - ISE

ismaali — Mon, 01 Jul 2019 19:02:23 GMT

My customer is doing IOS 13 beta testing and their VP of IT, is testing an iPad with iPadOS 13. He is not able to connect with either the corporate network or guest network. He said the following is the error from their Cisco ISE:

Failure reason: 12937 Supplicant stopped responding to ISE after sending it the first inner EAP-MSCHAPv2 message

Do you know what does this error means so he can let his team address the issue?

Re: Errors from iOS 13 beta testing - ISE

hslai — Mon, 01 Jul 2019 21:19:11 GMT

Failure reason: 12937 Supplicant stopped responding to ISE after sending it the first inner EAP-MSCHAPv2 message

It means exactly what it says. 😉

We would likely be able to locate an entry with such failures by running a report on "RADIUS Errors" under ISE admin web UI > Operations > Reports > Reports > Diagnostics, and then filtering 12937 on the column "Failure Reason". Pick one of them and click on its details.

Then, we will see "Steps" in the right-half of the report. Scroll down should reveal that ISE prepared EAP-request for inner method proposing PEAP-MSCHAP with challenge but did not get a response back to that request.

Our teams are not supporting beta client software releases in general.

topic Errors from iOS 13 beta testing - ISE in Network Access Control

Errors from iOS 13 beta testing - ISE

Re: Errors from iOS 13 beta testing - ISE