ISE 2.2 Patch 2. NSP 2.1.0.42 OSX 10.12.6

gbekmezi-DD · ‎08-02-2017

Supplicant provisioning fails. It APPEARS to be a problem on the client side. I'm not seeing any indications of a problem on ISE (though I could be missing something).

Output from system.log on the client:

Aug 2 22:15:12 georges-mbp Cisco Network Setup Assistant[14853]: grep returned:
   An asterisk (*) denotes that a network service is disabled.
   (1) LPSS Serial Adapter (1)
   (Hardware Port: LPSS Serial Adapter (1), Device: lpss-serial1)

   (2) LPSS Serial Adapter (2)
   (Hardware Port: LPSS Serial Adapter (2), Device: lpss-serial2)
...
   (6) Wi-Fi
   (Hardware Port: Wi-Fi, Device: en0)
...
Aug 2 22:15:12 georges-mbp Cisco Network Setup Assistant[14853]: grep returned:
   Wi-Fi Power (en0): On
Aug 2 22:15:12 georges-mbp Cisco Network Setup Assistant[14853]: grep returned:
   Current Wi-Fi Network: MyNetworkWPA2
Aug 2 22:15:12 georges-mbp Cisco Network Setup Assistant[14853]: getairportnetwork returned: Current Wi-Fi Network: MyNetworkWPA2
Aug 2 22:15:12 georges-mbp Cisco Network Setup Assistant[14853]: grep returned:
   Ethernet is not a recognized network service.
   ** Error: The parameters were not valid.
...
Aug 2 22:15:13 georges-mbp Cisco Network Setup Assistant[14853]: transection id is B866FC04-DDFF-4CA4-8D21-054DD57683CA
Aug 2 22:15:13 georges-mbp Cisco Network Setup Assistant[14853]: 200
Aug 2 22:15:13 georges-mbp Cisco Network Setup Assistant[14853]: {
        "Content-Length" = 0;
        Date = "Thu, 03 Aug 2017 04:15:14 GMT";
        Server = server;
        "Trans-Status" = Error;
   }
Aug 2 22:15:13 georges-mbp Cisco Network Setup Assistant[14853]: inserted certTemplateId 5152bf10-3003-11e4-8fda-005056b814bc to userCertMap

Looking for a hint on where to troubleshoot.

gbekmezi-DD · ‎08-03-2017

I'll follow up since I posted the question. I tried with a second endpoint today and that endpoint failed as well but didn't have the same error in the system.log output so that was just a red herring. I then tried to provision the second endpoint against another PSN in the same deployment and it worked. I restarted the application server on the original PSN and retried provisioning the original laptop and it worked. So it was obviously something on the PSN but I didn't find the root cause.