topic Re: Android 8.0 device not able to complete BYOD provisioning in Network Access Control

Android 8.0 device not able to complete BYOD provisioning

Gagandeep Singh — Thu, 16 Nov 2017 18:17:27 GMT

Hi Team,

Just wanted to know if this bug has any resolution yet.

CSCve82104 Byod flows not working in Android 8.0.0

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCve82104/?reffering_site=dumpcr

Customer running ISE 2.2 patch 4. The set up of BYOD works fine for Android 7 but it fails for 8.0

Find below spw.log for failed client running 8.0

2017.11.14 13:48:45 INFO:About to apply random number generator fix, if necessary.

2017.11.14 13:48:45 INFO:Done applying random number generator fix.

2017.11.14 13:48:50 INFO:verion :8.0.0 SDK Level : 26

2017.11.14 13:48:50 INFO:State :START

2017.11.14 13:48:50 INFO:Starting Discovery

2017.11.14 13:48:50 INFO:Starting ISEDiscoveryAsynchTask

2017.11.14 13:48:50 INFO:DHCP Stringipaddr 172.19.87.252 gateway 172.19.87.5 netmask 0.0.0.0 dns1 198.6.1.1 dns2 8.8.8.8 DHCP server 172.19.87.4 lease 86400 seconds

2017.11.14 13:48:50 INFO:DHCP ipaddress172.19.87.252

2017.11.14 13:48:50 INFO:DHCP gateway172.19.87.5

2017.11.14 13:48:52 ERROR:DiscoverAsynchTask

2017.11.14 13:48:52 ERROR:java.net.SocketTimeoutException: failed to connect to /172.19.87.5 (port 80) from /192.0.0.4 (port 37909) after 2000ms

2017.11.14 13:48:52 ERROR:failed to connect to /172.19.87.5 (port 80) from /192.0.0.4 (port 37909) after 2000ms

2017.11.14 13:48:56 ERROR:DiscoverAsynchTask

2017.11.14 13:48:56 ERROR:java.net.SocketTimeoutException: failed to connect to enroll.cisco.com/72.163.1.80 (port 80) from /192.0.0.4 (port 42835) after 2000ms

2017.11.14 13:48:56 ERROR:failed to connect to enroll.cisco.com/72.163.1.80 (port 80) from /192.0.0.4 (port 42835) after 2000ms

2017.11.14 13:48:56 ERROR:Unable to discover ISE Server

2017.11.14 13:48:56 INFO:Internal system error.

Any help would be appreciated.

Regards

Gagan

Re: Android 8.0 device not able to complete BYOD provisioning

hslai — Thu, 16 Nov 2017 18:25:30 GMT

The workaround is the fix, in a way, as ISE posture feed already updated with the new client OS support. If your customer still seeing issue, after updated, please check debug logs on ISE and, if needed, open an ISE ESC case to look further.

Re: Android 8.0 device not able to complete BYOD provisioning

hslai — Thu, 16 Nov 2017 18:28:05 GMT

From the NSA log, it's failing on discovering ISE so not the same bug. I would suggest to try turning off cellular data.

Re: Android 8.0 device not able to complete BYOD provisioning

Gagandeep Singh — Thu, 16 Nov 2017 18:39:51 GMT

Thanks for your time Hsing.

I have spw.log from Android 7 which works fine with the same setup of ISE configuration.

There is no such option in ISE for OS definition to segregate. Ideally it should work for both codes.

Regards

Gagan

Re: Android 8.0 device not able to complete BYOD provisioning

hslai — Thu, 16 Nov 2017 18:50:40 GMT

It's failing discovery so I suggested the only thing I can think of is to turn off the cellular data connection on the endpoint.

Re: Android 8.0 device not able to complete BYOD provisioning

Ruelb2214 — Wed, 24 Jul 2024 05:25:48 GMT

Hi @Gagandeep Singh

I'm facing similar issue, were you able to resolved the issue?

Re: Android 8.0 device not able to complete BYOD provisioning

Gagandeep Singh — Wed, 24 Jul 2024 14:50:20 GMT

Hi,

There may be some Android 8 behaviour change as compared to previous Android 7. Ensure Mobile data is OFF even while on Wifi. I would advise to collect spw.log and open TAC case for further troubleshooting.

* file manager/ Downloads/spw.log or internal/downloads/spw.log