I have opened case 2018-0314-2209. They need me to capture the below logs. However the problem with that, is that I cannot re-create the issue. It happens randomly. The logs and debugging that needs to be turned on can not be left on. I need to be able to re-create the issue everytime or at least 25-50% of the time to capture the necessary logs. On both my Windows 10 machines, I am unable to recreate the issue. The client side logs are easy to capture, pending they are set to detailed. you can understand why this is somewhat frustrating as it occurs randomly. Logs from VPN appliance - Policy Trace. - IVE TCP Dump - IVE Debug log with event codes - System Snapshot. - All IVE Logs. Pulse (client side debug log) Reference: KB17327 - How to collect the log file from Pulse Secure Desktop client? .Open the Pulse client. 2.File > Logs > Annotate > Type the test without quotes “Secure-Logs”. 3.File > Logs > Log Level > Detail. 4.File > Logs > Save As. To enable Policy Trace Logs on the IVE. In the admin console, choose Maintenance > Troubleshooting > User Sessions > Policy Tracing. In the User field, enter the IVE username of the user you want to trace. In the Realm field, select the user’s realm. Under Events to log, select the types of events you want to <select> to the policy trace log file & also select Pre-Authentication, Authentication & Role-mapping. Click Start Recording. Login as the user to sign into the IVE after you have started recording. Click View Log to see the log entries. Click Stop recording when you have obtained enough information. IVE TCP DUMP In the admin console, choose Maintenance > Troubleshooting > Tools > TCP Dump. Delete the Dump file if you already find any. If we are using both external and internal interface, enable both the IVE ports on which you want to sniff network packet headers. If we are using only internal port, make sure enable internal port to sniff network packet headers. Turn off Promiscuous mode to sniff only for packets intended for the IVE. Click Start Sniffing. Click Stop Sniffing to stop the sniffing process. Click Download to download the file to a network machine IVE debug log and System Snapshot. In the admin console, Maintenance--> Troubleshooting--> Monitoring -> Debug log. Debug log size=50 Debug log level=10 Debug log event codes= ipsec,dhcp Debug logging on. In the admin console, Maintenance--> Troubleshooting--> System Snapshot click on the Take snapshot and save it. In the admin console, Maintenance--> Troubleshooting--> Monitoring--> Save debug log. To save ALL IVE Log file: In the admin console, choose System > Log/Monitoring > Select Event. Click Save All Logs, navigate to the desired network location, enter a file name and then click Save to manually save the log file. thank you Sean
... View more
